Patent Application
20130237250
The present invention relates to determination of a mobile device's location in an IP-based wireless telecommunications network. More specifically, the present invention is related to systems and methods for determining a geographical location of a mobile device by retrieving information related to the mobile device from a database, processing the retrieved, information to identify a position, and communicating the position, information to a switch for further handling.
A variety of technologies enable telecommunication services to be offered using internet Protocol (IP). Commonly referred to as Voice over IP, or VoIP, such technologies enable telecommunications on any public or private IP network, including the internet. VoIP technology permits a user to receive IP-based telecommunications services through a variety of devices, including a desktop computer, a notebook computer, an analog handset used in conjunction with a VoIP telephone adapter, a VoIP-enabled handset, or other like device.
Increasingly, mobile devices, such as notebook computers, personal digital assistants (PDAs), wireless handholds, wireless handsets, or other similar devices, are also being enabled to receive IP-based telecommunications services. Such services are provided by enabling the mobile device to communicate with a wireless router and access any IP-based wireless access network, such as a network based on the IEEE 802.16 (WiMAX)s. IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), 802.11 wireless fidelity (Wi-Fi), and Bluetooth standards.
Moreover, dual-mode mobile telecommunications devices may be enabled to communicate with any IP-based wireless access network. For instance, Unlicensed Mobile Access (UMA) technology allows wireless service providers to merge cellular networks, such as Global System for Mobile Communications (GSM) networks, and IP-based wireless networks into one seamless service with one mobile device, one user Interface, and a common set of network services for both voice and data. UMA technology has recently been accepted into release 6 of the 3rd Generation Partnership Project (3GPP) standard in a General Access Network (GAN). With UMA or GAN solutions, subscribers may move between cellular networks and IP-based wireless networks with seamless voice and data session continuity as transparently as they move between cells within the cellular network Seamless in-call handover between the IP-based wireless network and cellular network ensures that the user's location and mobility do not affect the services delivered to the user. Services may be identical whether connected over the IP-based wireless network or the cellular network. UMA technology effectively creates a parallel radio access network, the UMA network, which interfaces to the mobile core network using standard mobility-enabled interfaces. The mobile core network remains unchanged. The common mobile core network makes it possible for the service provider to have full service and operational transparency. The existing service provider Business Support Systems (BSS), service delivery systems, content services, regulatory compliance systems, and Operation Support Systems (OSS) can support the UMA network without change. Service enhancements and technology evolution of the mobile core network apply transparently to both cellular access and UMA.
The present disclosure has identified a number of problems in locating a mobile device on an IP-based wireless telecommunications network and providing location based services to the mobile device. Telecommunications service providers would like to offer location-based services that deliver information specific to the mobile device's current location. Telecommunications service providers also wish to route certain calls, such as 911 or “emergency” calls, to an office that is geographically relevant to the user of a mobile device. The present disclosure has identified the above and other needs for service providers who operate IP-based wireless telecommunications networks to implement systems and methods that determine the mobile device's location on an IP-based wireless telecommunications network.
Non-limiting and non-exhaustive embodiments are described with reference to the following drawings.
The present disclosure now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments for practicing the invention. This disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope to those skilled in the art. Among other things, the present disclosure may be embodied as methods or devices. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.
Briefly stated, the present disclosure relates to a system and method for locating the geographic position of a mobile device when in communication with an IP-based wireless telecommunications network. A wireless connection between the mobile device and the IP-based wireless telecommunications network is established when the mobile device registers with a network controller (NC) through an access point (AP). When a geographical position is needed for the mobile device (e.g., a 911 call), messages are exchanged between the NC and the SMLC, where the SMLC retrieves information from a database that is used to identify the geographic position of the mobile device. The database can store a variety of information related to mobile devices such as: last known position, IP address, MAC address, a mobile or subscriber identifier (such as an International Mobile Subscriber Identity (IMSI)), last CGI, etc. The geographical position is communicated back to the NC, which can then forward the position information to a switch for processing such as for 911 calls.
Example IP-based wireless communication networks include VoIP networks and/or converged wireless networks that include a combination of cellular networks and IP-based wireless telecommunications network (e.g., unlicensed mobile access or UMA network technologies). A mobile device can access a VoIP network via a wireless connection with an access point. A dual-mode wireless telecommunication device can access either a cellular network or an IP-based wireless telecommunications network, such as UMA network, thereby allowing mobile devices to roam voice, data and multimedia communications between conventional cellular networks and wireless local area network access points at home, in the office and at public areas (e.g., hot spots). Calls are transferred between the networks depending on whether the access point is in range or not, permitting users to transparently connect to the fastest or lowest cost network.
The positioning system may be useful when the mobile subscriber issues a 911 emergency call or when a mobile subscriber wishes to receive value added location based services (such as information regarding nearby restaurants, gas stations, entertainment complexes and similar locations of interest). In the case of emergency services the call is routed to a public safety answering point (PSAP) and is forwarded to the proper services. The PSAP receives the caller's phone number and the exact geographic location of the mobile device from which the call was made.
The VoIP system depicted in
When a mobile device accesses an IP-based wireless network, information is initially formatted in the cellular system's native protocol and then encapsulated into Internet Protocol (IP) packets, transmitted to the access point, and communicated over the Internet to the cellular service providers mobile core network. Such transmissions bypass the service provider's existing network of radio towers. Because the same cellular protocols are used in communications involving IP access points as with traditional radio towers, the cellular service provider maintains a large degree of system compatibility even though using an IP-based network. The systems of the cellular service provider that deliver content and handle mobility may not even need to he aware that a subscriber's mobile device is on an IP-based wireless telecommunications network. The system may instead assume the mobile device is on its native cellular network. The IP network is therefore abstracted with respect to the cellular network, regardless of whether the mobile device connects to the cellular network via a base station (for licensed spectrum access) or a wireless access point (for licensed, semilicensed and/or unlicensed spectrum access).
A non-exhaustive list of products and services available on IP-based wireless telecommunications networks includes not only voice services, but also supplementary services like call forwarding and call waiting, text messaging services like SMS, and data-based services like ringtone downloads, game downloads, picture messaging, email and web browsing. Further, since a mobile device is connected to an IP network, a wide variety of data services available over such networks may be provided to the mobile device.
The example cellular telephone network includes one or more cell towers 220 that are configured to accept cellular communications 212 from mobile device 210. The cell towers 220 are connected to a controller (such as a base station controller/radio network controller (BSC/RNC)) 276 via a private network 230. The private network 230 can include a variety of connections such as T1 lines, a wide area network (WAN), a local area network (LAN), various network switches, and other similar components. Cell tower controller 276 controls network communication traffic to the carrier network 290, where all communications are managed. An example carrier network 290 includes a switch (such as a mobile switching center (MSC)) 292, which is configured to control data/call flows, perform load balancing, as well as other functions. A variety of system databases may also be accessed in the carrier network such as, e.g., an operation support subsystem (OSS) database 294, a business support system (BSS) database 296, and a central subscriber database that contains details of a carriers' subscribers (such as a home location register (HLR)) 298, for billing, call logging, etc.
The example IP-based wireless network includes one or more access points (APs) 240 that can accept IP communications 214 from mobile device 210. An access point can be configured as part of a wireless network in one or more locations such as a public network 242, a home network 244, or a private-business network 246. Each access point is coupled to an Internet Protocol (IP) network 250 through a broadband connection. IP packets that carry communications (data, voice, SMS, etc.) are routed from the access points to a security gateway (SGW) 271 through the IP network 250. The security gateway controls access to the network controller (such as a UMA Network Controller (UNC)) 266, which communicates with a database 268 tor logging and/or accessing various data associated with communications. The network controller 266 is also configured to manage access with the carrier network 290 in a similar manner to that performed by the BSC/RNC 276.
Authentication of a request for access by a mobile device over the IP-based network is handled by the security gateway 271, which communicates with an authentication, accounting and authorization (AAA) module 272 as shown in
For the example system 200′ , the signaling path of an IP-based call is routed through the network controller 266 to a mobile switching system (MSS) 280, while the voice bearer path is routed through the network controller 266 to a media gateway (MGW) 282. The signaling portion of a communication governs various overhead aspects of the communication such as, for example, when the call starts, when the call stops, initialing a telephone ring, etc. The voice bearer portion of the communication contains the actual content (either data or voice information) of the communication. The MGW 282 controls the content flow between the service provider and the mobile device 210, while the MSS 280 controls the signaling flow (or controls overhead-related flow) between the service provider and the mobile device 210.
The present disclosure is directed to an interface and a corresponding protocol between NC 266 and SMLC 310. In one example, a mobile subscriber issues a call from mobile device 210. The call is routed to switch 292 via access point 240 and NC 266. A series of messages are executed sequentially to locate the geographic position of mobile device 210. A perform location request (PLRQ) message is sent fern NC 266 to SMLC 310. SMLC 310 sends a positioning request to be retrieved from NC database 268. The NC database 268 provides location information associated with at least one of: a media access control (MAC) address associated with an access point, an identifier associated with mobile device 210, a cell global identity (CGI) associated with mobile device when the call is made, an internet protocol (IP) address associated with the access point, or any other combination thereof. SMLC 310 executes an algorithm to calculate the geographic position of mobile device 210 using the location information retrieved from NC database 268. The calculated position is returned to NC 266 via a perform location response (PLRS) message. NC 266 forwards the calculated location result to switch 292 via the PLRS.
The different pre-standard Lb interface messages and the parameters to support the NC-SMLC Lb interface and the NC database interface messages related to positioning are described in detail below. In each table the presence of specific data is qualified, where M=mandatory, C=conditional, and O=optional An information element identified as conditional means that the element may be included in the message if the optional element located above it is included. For example, referring to Table 2, Location Estimate 1 may be included if mobile device or subscriber identifier is included.
Positioning Request is a message that is sent from the SMLC to the NC. The Positioning Request message requests that the NC return the specific control information. The Positioning Request message contains the following information elements.
Positioning Response is a message that is sent from the NC to the SMLC. The Positioning Response message is a response to the positioning request message. The Positioning Response message contains the following information elements.
Reset is a message that is sent from the NC to the SMLC. The Reset message is sent when the response message contents for a positioning request are invalidated before the positioning procedure was completed. The following are expected cause values for the reset message: failure for other radio related events; supervision timer expired; incorrect serving cell identity; and handover. The Reset message contains the following information elements.
Reject is a message that is sent from the NC to the SMLC. The Reject message is a possible response to the positioning request. The following are expected cause values for the Reject message: congestion; channel mode not supported; positioning procedure not supported; failure for other radio related events; incorrect serving cell identity; and segmentation error. The Reject message contains the following information elements.
Abort is a message that is sent either from the NC to the SMLC, or from the SMLC to the NC. Upon receiving the Abort message, the SMLC or NC aborts the ongoing positioning procedure. The following are expected cause values for the Abort message: failure for other radio related events; supervision timer expired; and loss of signaling connection to MS. The Abort message contains the following information elements.
DB Location Request is a message that is sent from the NC to the NC database. The DB Location Request message requests that the NC database return a location estimation. The DB Location Request message contains the following information elements.
DB Location Response is a message that is sent from the NC database to the NC. The DB Location Response message contains the following information elements.
NC Database Abort is a message that is seat either from the NC database to the NC, or from the NC to the NC database. The NC Database Abort message contains the following information elements.
The SMLC passes a base station subsystem application part-location extraction (BSSAP-LE) connection oriented information message to the NC. The NC contains an embedded BSSLAP-LE message. BSSLAP defines the SMLC-BSS layer 3 protocol. The BSSAP-LE message is transferred using an SCCP connection that was previously established between the SMLC and NC when the positioning request for the target MS was initially sent to the SMLC. The NC recognizes that it is the final destination due to the presence of the embedded BSSLAP message.
When the NC has positioning information for the target mobile subscriber to return the SMLC, the NC sends a BSSAP-LE connection oriented message to the SMLC containing an embedded BSSLAF message. The message is sent using the SCCP connection previously established for locating the target mobile device.
Step 600: The mobile subscriber (MS) registers for access as a wireless device using an IP-based telecommunications network. The registration process is initiated between the MS and the network controller (NC) via the access point (AP). The MS also identifies a wireless radio resource (e.g. a GSM CGI radio resource) and a corresponding MAC address during the registration request. The mobile subscriber dials 911, which is communicated to the NC.
Step 605: The NC forwards the 911 call to the switch for routing. The cell global identity (CGI) associated with the mobile subscriber (MS) are forwarded to the switch for further processing.
Step 610: The switch sends a PLRQ message to the NC based on the received 911 call. The PLRQ includes mobile subscriber information associated with quality of service (QoS), device or subscriber identifier, and an SCCP identifier. The device identifier is registered with the network when the mobile subscriber (MS) accesses the network.
Step 615: The NC forwards the PLRQ to the SMLC. The PLRQ includes QoS, CGI, and device or subscriber identifier information for the mobile device.
Step 620: The SMLC sends a positioning request message to the NC.
Step 625: The NC sends a location request message to the NC database. The location request message includes mobile subscriber information for the device identifier that is associated with the mobile device, a MAC address associated with the access point, and an IP address associated with the access point.
Step 630: The NC database provides one or more locations information to the NC in the form of a location response message, which may include the subscriber's address, access point location and public IP address serving area. The NC database may also provide an uncertainty rating that provides the likelihood that the identified location of the mobile subscriber is accurate.
Step 635: The NC sends a positioning response message to the SMLC, where the positioning response message includes all the locations information from the NC database to the SMLC. The SMLC executes an algorithm to calculate the location of the mobile device using the information received above to get the final latitudinal-longitudinal coordinates and the uncertainty rating.
Step 640: The SMLC returns the calculated location information to the NC via a PLRS message. The PLRS message includes the latitudinal-longitudinal coordinates, the uncertainty rating and the SCCP identifier.
Step 645: The NC forwards the PLRS message with the location information to the switch.
Step 650: The switch communicates an SLR ESRK Request message to the gateway mobile location center (GMLC), which requests a determination of PSAP information based on the location of the mobile device.
Step 655: The GMLC communicates an SLR Ack message, which returns PSAP information with an emergency service routing key (ESRK).
Step 660: The switch routes the call to the proper PSAP based on ESRK received from GMLC.
Step 665: The location of the mobile device is delivered to an application location interlace (ALI) for the PSAP access.
Continuing to decision block 710, a determination is made whether a PLRQ message is received from the NC. If a PLRQ message is not received, processing continues at block 700 where the SMLC waits in an idle state for the PLRQ message. If a PLRQ message is received, processing continues at block 720.
The request is processed at block 720. The SMLC sends a positioning request message to the NC. The NC returns a positioning response message to the SMLC.
Moving to block 730 the parameters are evaluated. The SMLC executes an algorithm to calculate the location of the mobile device using at least one of: the subscriber's address based on the device or subscriber identifier; the access point (AP) location based on the MAC address associated with the access point; the serving area of the IP address associated with the access point; the uncertainty rating for each of the above locations, or any other combination thereof.
Advancing to decision block 740, a determination is made whether to reject the request. If the request is to be rejected, processing continues to block 750 where the request is rejected. Otherwise, processing proceeds to block 760 where the SMLC returns the location information to the NC via a PLRS message.
The NC forwards the PLRQ message to the SMLC at block 820. Continuing to block 830, the NC receives a positioning request message from the SMLC. Advancing to block 840, the NC forwards a location request message to the NC database. Moving to block 850, the NC receives a location response message from the NC database. The location response message includes either: the subscriber's address based on the device identifier associated with the mobile device, the access point location based on the MAC address associated with the access point, the serving area of the IP address associated with the access point; or the uncertainty rating for each of the above locations.
Proceeding to block 860, the NC forwards a positioning response message to the SMLC. Transitioning to block 870, the NC receives a PLRS message from the SMLC. The PLRS message includes the location information for the mobile device (e.g., latitudinal-longitudinal information, uncertainty ratings and SCCPID). The NC forwards the PLRS message with the location information to the switch at block 880.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
This utility patent application claims the benefit under 35 United States Code§119(e) of U.S. Provisional Patent Application No. 60/728,972, which was filed Oct. 21, 2005.
| Number | Date | Country | |
|---|---|---|---|
| 60728972 | Oct 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12089905 | Feb 2009 | US |
| Child | 13753472 | US |
