CA2620617A1 - System and method for utilizing ip-based wireless telecommunications client location data - Google Patents
System and method for utilizing ip-based wireless telecommunications client location data Download PDFInfo
- Publication number
- CA2620617A1 CA2620617A1 CA002620617A CA2620617A CA2620617A1 CA 2620617 A1 CA2620617 A1 CA 2620617A1 CA 002620617 A CA002620617 A CA 002620617A CA 2620617 A CA2620617 A CA 2620617A CA 2620617 A1 CA2620617 A1 CA 2620617A1
- Authority
- CA
- Canada
- Prior art keywords
- location
- network
- providing
- handheld device
- mobile
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/10—Mobility data transfer between location register and external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Abstract
A location provision facility communicates with a mobile telecommunications device over an IP-based telecommunications network to obtain information that enables the facility to determine a location of the telecommunications device. The facility and/or the telecommunications device store the determined location. In response to requests from location-based applications for the location of the telecommunications device, the facility can provide the location-based applications with the stored or calculated location.
Description
SYSTEM AND METHOD FOR UTILIZING IP-BASED WIRELESS
TELECOMMUNICATIONS CLIENT LOCATION DATA
CROSS-REFERENCE TO RELATED APPLICATION(S) [0001] This application claims the priority of U.S. Provisional Application No.
60/853,086 entitled METHOD AND DELIVERY OF UMA VALUE ADDED LOCATION
SERVICES VIA SUPL, filed October 20, 2006, the entirety of which is hereby incorporated by reference.
TECHNICAL FIELD
TELECOMMUNICATIONS CLIENT LOCATION DATA
CROSS-REFERENCE TO RELATED APPLICATION(S) [0001] This application claims the priority of U.S. Provisional Application No.
60/853,086 entitled METHOD AND DELIVERY OF UMA VALUE ADDED LOCATION
SERVICES VIA SUPL, filed October 20, 2006, the entirety of which is hereby incorporated by reference.
TECHNICAL FIELD
[0002] The present invention is directed generally toward telecommunications and more specifically toward mobile telecommunications devices and services.
BACKGROUND
BACKGROUND
[0003] In this digital age, modern telecommunication service providers and device manufacturers are increasingly relying on public and/or private IP (Internet Protocol) networks, including the Intemet, as a core part of their technology. For example, many telecommunications service providers now offer a suite of Voice over IP
("VoIP") services, as well as various data services, that utilize IP networks and/or IP-based wireless access networks (e.g., access networks based on IEEE 802.16 ("WiMAX"), IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), IEEE 802.11 wireless fidelity ("WiFi"), Bluetooth, ZigBee and similar standards) for at least part of their infrastructure. Likewise, device manufacturers are producing the next generation of mobile devices (e.g. wireless handhelds, wireless handsets, mobile phones, personal digital assistances, notebook computers, and similar devices) that are enabled to send and receive information utilizing IP-based telecommunications services.
In fact, many of today's modern mobile devices are able to function as "dual-mode devices" that take advantage of both cellular network technologies and IP-based technologies.
31419-8036.W000/LEGAL13654627.1 't h (0004] Unlicensed Mobile Access (aftematively referred to as Universal Mobile Access (UMA)) technology has developed as part of this trend to incorporate IP
solutions into mobile device telecommunication systems. UMA technology has recently been accepted into Release 6 of the 3rd Generation Partnership Project (3GPP) and is also referred to as Generic Access Network (GAN) technology. In various implementation schemes, UMA allows wireless service providers to merge cellular networks (such as Global System for Mobile Communications (GSM) networks) and IP-based wireiess networks into one seamless service (with one mobile device, one user interface, and a common set of network services for both voice and data). One goal of UMA is to allow subscribers to move transparently between cellular networks and IP-based wireless networks with seamless voice and data session continuity, much like they can transparently move between cells within the cellular network.
Seamless in-call handover between the IP-based wireless network and the cellular network ensures that the user's location and mobility do not affect the services delivered to the user.
("VoIP") services, as well as various data services, that utilize IP networks and/or IP-based wireless access networks (e.g., access networks based on IEEE 802.16 ("WiMAX"), IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), IEEE 802.11 wireless fidelity ("WiFi"), Bluetooth, ZigBee and similar standards) for at least part of their infrastructure. Likewise, device manufacturers are producing the next generation of mobile devices (e.g. wireless handhelds, wireless handsets, mobile phones, personal digital assistances, notebook computers, and similar devices) that are enabled to send and receive information utilizing IP-based telecommunications services.
In fact, many of today's modern mobile devices are able to function as "dual-mode devices" that take advantage of both cellular network technologies and IP-based technologies.
31419-8036.W000/LEGAL13654627.1 't h (0004] Unlicensed Mobile Access (aftematively referred to as Universal Mobile Access (UMA)) technology has developed as part of this trend to incorporate IP
solutions into mobile device telecommunication systems. UMA technology has recently been accepted into Release 6 of the 3rd Generation Partnership Project (3GPP) and is also referred to as Generic Access Network (GAN) technology. In various implementation schemes, UMA allows wireless service providers to merge cellular networks (such as Global System for Mobile Communications (GSM) networks) and IP-based wireiess networks into one seamless service (with one mobile device, one user interface, and a common set of network services for both voice and data). One goal of UMA is to allow subscribers to move transparently between cellular networks and IP-based wireless networks with seamless voice and data session continuity, much like they can transparently move between cells within the cellular network.
Seamless in-call handover between the IP-based wireless network and the cellular network ensures that the user's location and mobility do not affect the services delivered to the user.
[0005] At an operational level, UMA technology effectively creates a parallel radio access network, the UMA network, which interfaces to the mobile core network using standard mobility-enabled interfaces. For example, UMA can replace a system's GSM
radio technology on the lower protocol layers with a wireless LAN or similar technology.
A call or other communication may be tunneled to the Mobile Switching Center (MSC) of a mobile service provider via an access point (e.g., a WiFi access point connected to a modem via the intemet) and gateway (e.g., a UMA network controller). In many cases, the mobile core network remains unchanged, making it much easier to maintain full service and operational transparency and allowing other aspects of the service infrastructure to remain in place. For example, in many systems that utilize UMA, the existing service provider's business support systems (BSS), service delivery systems, content services, regulatory compliance systems, and operation support systems (OSS) can support the UMA network without change. Ukewise, service enhancements and technology evolution of the mobile core network apply transparently to both cellular access and UMA.
31419-8038.W000JLEGAL13654627.1 -2-c =
radio technology on the lower protocol layers with a wireless LAN or similar technology.
A call or other communication may be tunneled to the Mobile Switching Center (MSC) of a mobile service provider via an access point (e.g., a WiFi access point connected to a modem via the intemet) and gateway (e.g., a UMA network controller). In many cases, the mobile core network remains unchanged, making it much easier to maintain full service and operational transparency and allowing other aspects of the service infrastructure to remain in place. For example, in many systems that utilize UMA, the existing service provider's business support systems (BSS), service delivery systems, content services, regulatory compliance systems, and operation support systems (OSS) can support the UMA network without change. Ukewise, service enhancements and technology evolution of the mobile core network apply transparently to both cellular access and UMA.
31419-8038.W000JLEGAL13654627.1 -2-c =
[0006] As the incorporation of IP solutions, such as UMA, into mobile device telecommunication systems expands, wireless service providers and wireless users may face various obstacles. For example, it can be necessary or desirable to determine the location of a mobile device for various reasons, such as needing to provide it to certain services, such as emergency services that need to know the locafion of the user of the mobile device. Certain mobile devices have incorporated Global Positioning System (GPS) technology that enables determining their locations. However, GPS
technology may not function as desired in certain situations, and other mobile devices may not have incorporated GPS technology. It can still be desirable or necessary to determine the locations of such mobile devices and provide it to certain services.
technology may not function as desired in certain situations, and other mobile devices may not have incorporated GPS technology. It can still be desirable or necessary to determine the locations of such mobile devices and provide it to certain services.
[0007] The need exists for a system that overcomes the above problems, as well as one that provides additional benefits. Overall, the examples herein of some prior or related systems and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems will become apparent to those of skill in the art upon reading the following Detailed Description.
BRIEF DESCRIPTION OF THE DRAWINGS
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 illustrates aspects of a sample network system that allows VolP-based communications in conjunction with a public switched telephone network (PSTN).
[0009] Figure 2 illustrates an example converged wireless network system that combines a cellular network with an IP-based wireless telecommunications network.
[0010] Figure 3 illustrates a location provision facility in accordance with embodiments of the invention.
[0011] Figure 4 is a flow diagram of a process for registering an IP-based telecommunications mobile device.
[0012] Figure 5 is a flow diagram of a process for providing location information of an IP-based telecommunications mobile device to a Location-Based Service (LBS) application.
31418-8036.VY000ILEGAl13654627.1 -3-T k [0013] Figure 6 is a call flow diagram depicting registration of an IP-based telecommunications mobile device.
31418-8036.VY000ILEGAl13654627.1 -3-T k [0013] Figure 6 is a call flow diagram depicting registration of an IP-based telecommunications mobile device.
[0014] Figure 7 is a call flow diagram depicting provisioning of location information of an IP-based telecommunications mobile device to an LBS application.
DETAILED DESCRIPTION
DETAILED DESCRIPTION
[0015] The fo!lowing description provides specific details for a thorough understanding of, and enabling description for, various embodiments of the technology.
One skilled in the art will understand that the technology may be practiced without these details. In some instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the technology. It is intended that the terminology used in the description presented below be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain embodiments of the technology.
Although certain terms may be emphasized below, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
One skilled in the art will understand that the technology may be practiced without these details. In some instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the technology. It is intended that the terminology used in the description presented below be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain embodiments of the technology.
Although certain terms may be emphasized below, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
[0016] Figure 1 and the following discussion provide a brief, general description of suitable environments in which the technology can be implemented. Although not required, aspects of the technology are described in the general context of computer-executable instructions, such as routines executed by a general-purpose computer, e.g., a server computer, wireless device or personal computer. Those skilled in the relevant art wiU appreciate that the technology can be practiced with other communications, data processing, or computer system configurations, including: Internet appliances, hand-held devices (including personal digital assistants (PDAs)), wearable computers, all manner of cellular or mobile phones, multi-processor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, mini-computers, mainframe computers, and the like. Indeed, the terms "computer," "server,"
"host," "host system," and the like are generally used interchangeably herein, and refer to any of the above devices and systems, as we!l as any data processor.
31419-8036.W000/LEGAL13654627.1 -4-[0017] Aspects of the technology may be stored or distributed on computer-readable media, including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. Indeed, computer implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Intemet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme).
1. Sample Network Configurations [0018] Figures 1-3 show sample network system configurations in which aspects of a location provision facility can be implemented in accordance with various embodiments. In general, one purpose of the location provision facility is to provide locations of telecommunications devices to certain services.
"host," "host system," and the like are generally used interchangeably herein, and refer to any of the above devices and systems, as we!l as any data processor.
31419-8036.W000/LEGAL13654627.1 -4-[0017] Aspects of the technology may be stored or distributed on computer-readable media, including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. Indeed, computer implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Intemet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme).
1. Sample Network Configurations [0018] Figures 1-3 show sample network system configurations in which aspects of a location provision facility can be implemented in accordance with various embodiments. In general, one purpose of the location provision facility is to provide locations of telecommunications devices to certain services.
[0019] Figure 1 illustrates aspects of a sample network system 100 that allows VoIP-based communications in conjunction with a public switched telephone network (PSTN) 102. The system 100 includes at least one wireless access point 104.
The access point 104 may be public or private, and may be located, for example, in a subscriber's residence (e.g., home, apartment or other residence), in a public location (e.g., coffee shops, retail stores, libraries, or schools) or in corporate or other private locations. In the sample system of Figure 1, the access point 104 can accept communications 106 from at least one suitably configured telecommunications device 108 (e.g., a VoIP device). Various examples of network technology that may be involved in communicating between the telecommunications device 108 and the access point 104 include the IEEE 802.16 (WiMAX), IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), IEEE 802.11 wireless fidelity (Wi-fi), Bluetooth standards, Zigbee or other similar standards. The access point 104 includes a wireless router 110 and a broadband modem 112 that enable connection to an lntemet 31419-8036.W00011E0AL13654627.1 -5-.
Protocol (IP) network 114. The IP network 114 may comprise one or more public networks, private networks, or combination of public and private networks.
The access point 104 may be public or private, and may be located, for example, in a subscriber's residence (e.g., home, apartment or other residence), in a public location (e.g., coffee shops, retail stores, libraries, or schools) or in corporate or other private locations. In the sample system of Figure 1, the access point 104 can accept communications 106 from at least one suitably configured telecommunications device 108 (e.g., a VoIP device). Various examples of network technology that may be involved in communicating between the telecommunications device 108 and the access point 104 include the IEEE 802.16 (WiMAX), IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), IEEE 802.11 wireless fidelity (Wi-fi), Bluetooth standards, Zigbee or other similar standards. The access point 104 includes a wireless router 110 and a broadband modem 112 that enable connection to an lntemet 31419-8036.W00011E0AL13654627.1 -5-.
Protocol (IP) network 114. The IP network 114 may comprise one or more public networks, private networks, or combination of public and private networks.
[0020] In a communication or set of communications 106, the acx;ess point 104 receives IP packets from the telecommunications device 108. These IP packets are then transported through the IP network 114 to a signaling gateway 116, which in the example of Figure 1, is operated by a telecommunications service provider. At the signaling gateway 116, the IP packets are converted to a traditional phone service signal. The phone service signal is then conveyed to a recipient via the PSTN
102.
102.
[0021] The network system 100 of Figure 1 also includes a call controller 118 that provides call logic and call control functions for communications sent through the system and an application server 120 that provides logic and execution of one or more applications or services offered by the telecommunications service provider, such as applications that implement various access and security rules. In this example, a telecommunication service provider manages both the call controller 118 and the application server 120.
[0022] Figure 2 illustrates a sample network system 200 in which aspects of the location provision facility can be implemented within a cellular telephone-type network.
In general, with respect to the network system described in Figure 2, 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. For example, the various systems of the cellular service provider that deliver content and handle mobility may not even need to be aware that a subscriber's mobile device is on an IP-based wireless telecommunications network. Instead, the various systems of the cellular service provider 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 (e.g., for licensed spectrum access) or a wireless access point (e.g., for licensed, semilicensed and/or unlicensed spectrum access-such as spectrums for IP-based telecommunications).
Likewise, at a protocol level, because the same cellular protocols are used in 31418-6036.w000ILEGAL13654627.1 -6-communications involving the 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.
In general, with respect to the network system described in Figure 2, 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. For example, the various systems of the cellular service provider that deliver content and handle mobility may not even need to be aware that a subscriber's mobile device is on an IP-based wireless telecommunications network. Instead, the various systems of the cellular service provider 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 (e.g., for licensed spectrum access) or a wireless access point (e.g., for licensed, semilicensed and/or unlicensed spectrum access-such as spectrums for IP-based telecommunications).
Likewise, at a protocol level, because the same cellular protocols are used in 31418-6036.w000ILEGAL13654627.1 -6-communications involving the 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.
[0023] Referring to Figure 2, a sample network system 200 combines a cellular telephone network 202 (such as a GSM network) and an IP network 204 in a UMA-type configuration that provides service to the user of a mobile device 206. Such service may include voice services, and also supplementary services like call forwarding and call waiting, text messaging services (e.g., SMS), and data-based services like ringtone downloads, game downloads, picture messaging, email and web browsing. Further, since the mobile device 206 is connected to an IP network, all manner of data services available over such networks may be provided to the mobile device 206.
[0024] In general, the described network system 200 accepts registration requests and communication connections from the mobile device 206. The accepted registration requests can be requests to either the cellular telephone network 202 or to the IP-based network 204. Accordingly, to handle requests to the cellular telephone network 202, the cellular telephone network 202 includes one or more cell towers 208 that are configured to accept cellular communications 210 from the mobile device 206. The cell towers 208 are connected to a base station controller 212 (such as a base station controller/radio network controller (BSC/RNC)) via a private network 214. The private network 214 can include a variety of connections (not shown) such as T1 lines, a wide area network (WAN), a local area network (LAN), various network switches, and other similar components.
[0025] The base station controller 212 controls communication traffic to a carrier core network 216, where all communications are managed (including both cellular and IP-based). Components of the carrier core network 216 in this example include.
a switch (e.g., a mobile switching center or MSC) 218, which is configured to control data/cali flows and perform load balancing, as well as other functions. The carrier core .network 216 may also include a variety of system databases such as an operation support subsystem (OSS) database 220, a business support system (BSS) database 222, and 31419-8036.WOOQILEGAL13654627.1 -7-home location register (HLR) 224 or other central subscriber database that contains details of a carrier's subscribers for billing, call logging, etc.
a switch (e.g., a mobile switching center or MSC) 218, which is configured to control data/cali flows and perform load balancing, as well as other functions. The carrier core .network 216 may also include a variety of system databases such as an operation support subsystem (OSS) database 220, a business support system (BSS) database 222, and 31419-8036.WOOQILEGAL13654627.1 -7-home location register (HLR) 224 or other central subscriber database that contains details of a carrier's subscribers for billing, call logging, etc.
[0026] The sample network system 200 of Figure 2 further includes one or more access points 226 that can accept IP-based communications 228 from the mobile device 206. For example, each access point 226 can be configured as part of a wireless network in one or more locations such as a public network 230, a home network 232, or a private business network 234. Each access point 226 is coupled to the IP
network 204 through, for example, a broadband connection (not shown) such as a DSL
(Digital Subscriber Line) modem, a cable modem, a satellite modem, or any other broadband device.
network 204 through, for example, a broadband connection (not shown) such as a DSL
(Digital Subscriber Line) modem, a cable modem, a satellite modem, or any other broadband device.
[0027] When the mobile device 206 attempts to access the IP network 204 (i.e., to initiate an IP-based communication), information (e.g., data, voice, SMS, etc.) is initially formatted in the cellular system's 202 native protocol and then encapsulated into Internet Protocol (IP) packets, which are transmitted to the access point 226 and routed through the IP network 204 to a security gateway 236. In contrast to non-IP
communication requests, such transmissions bypass the cellular telephone system's 202 existing network of radio towers. The security gateway 236 controls access to a network controller 238, which communicates with a data store 242 for logging and accessing communications data. Thus, one function of the network controller 238 is to manage access to the carrier network 216 when dealing with an IP-based communication (in a similar manner to that performed by the base station controller 212 for a non-IP-based communication).
communication requests, such transmissions bypass the cellular telephone system's 202 existing network of radio towers. The security gateway 236 controls access to a network controller 238, which communicates with a data store 242 for logging and accessing communications data. Thus, one function of the network controller 238 is to manage access to the carrier network 216 when dealing with an IP-based communication (in a similar manner to that performed by the base station controller 212 for a non-IP-based communication).
[0028] In one .example, authentication of a request for access by the mobile device 206 over the IP network 204 is handled by the security gateway 236, which communicates with an authentication, access and authorization (AAA) module 240 that is most likely associated with the carrier network 216. Challenges and responses to requests for access by the mobile device 206 are communicated between the HLR
and the AAA module 240. When authorization is granted, the security gateway communicates the assignment of an IP address to the mobile device 206 that requested access. Once the security gateway 236 passes the IP addnrss to the mobile device 31419-8036, WO00/LEGAL1365462T.1 -8-206, the public IP address assigned to the mobile device 206 is passed to the network controller 238.
and the AAA module 240. When authorization is granted, the security gateway communicates the assignment of an IP address to the mobile device 206 that requested access. Once the security gateway 236 passes the IP addnrss to the mobile device 31419-8036, WO00/LEGAL1365462T.1 -8-206, the public IP address assigned to the mobile device 206 is passed to the network controller 238.
[0029] In another authorization example, upon receiving an identifier from the mobile device 206, the network controller 238 may query the data store 242 to determine if the mobile device 206 is authorized for accessing the IP network 204.
Sample identifiers that may be utilized to determine access include a media access control (MAC) address associated with an access point, a mobile device or subscriber identifier (such as an International Mobile Subscriber Identifier (IMSI)), an Intemet Protocol (IP) address (or "Public IP address") associated with the access point, a fully qualified domain name (FQDN), or other similar types of information. The data store 242 may be a single database, table, or list, or a combination of databases, tables, or lists, such as one for IP addresses 244, one of MAC addresses 246, and one for FQDNs 248. The data store 242 may include 'blocked" identfiers as well as "authorized"
identifiers.
Authorized accesses to the IP-based wireless telecommunications network may be maintained by the network controller 238 in an authorized session table or similar data construct.
Sample identifiers that may be utilized to determine access include a media access control (MAC) address associated with an access point, a mobile device or subscriber identifier (such as an International Mobile Subscriber Identifier (IMSI)), an Intemet Protocol (IP) address (or "Public IP address") associated with the access point, a fully qualified domain name (FQDN), or other similar types of information. The data store 242 may be a single database, table, or list, or a combination of databases, tables, or lists, such as one for IP addresses 244, one of MAC addresses 246, and one for FQDNs 248. The data store 242 may include 'blocked" identfiers as well as "authorized"
identifiers.
Authorized accesses to the IP-based wireless telecommunications network may be maintained by the network controller 238 in an authorized session table or similar data construct.
[0030] In some cases, the signaling portion of a communication (e.g., the portion of the communication that govems various overhead aspects of the communication such as, for example, when the call starts, when the call stops, initiating a telephone ring, etc.) is routed through the network controller 238 to the switch 218, while the voice bearer portion of the communication (e.g., the portion of the communication that contains the actual content (either data or voice information) of the communication) is routed through the network controller 238 to a media gateway 250. In other words, the media gateway 250 controls the content flow between the service provider and the mobile device 206, while the switch 218 controls the signaling flow (or controls overhead-related flow) between the service provider and the mobile device 216.
[0031] Figure 3 illustrates a suitable environment 300 in which the location provision facility can be implemented. As previously described with reference to, e.g., Figures 1 and 2, the access point 104 enables the telecommunications device 108 (e.g., a dual-mode mobile phone that can connect to an existing cellular network and is UMA-31419-8036.W000/LEGAL13854627.1 -9-enabled) to connect to an IP Network 314a. An IP-based wireless telecommunications network (e.g., UMA or GAN) is also connected to the IP Network 314a. The IP-based telecommunications network 320 can be part of a cellular network. The IP-based telecommunications network 320 includes a network controller (e.g., a UMA
Network Controller (UNC), or a GAN Controller (GANC)) 325, which is connected to a serving mobile location center (SMLC) 330 and to a location database 335. The IP-based telecommunications network 320 is also connected to an IP Network 314b. The IP
Networks 314a and 314b can be the same IP network, but are shown as distinct networks for illustrative purposes. A Secure User Plane Location (SUPL) Location Platform (SLP) 340 is connected to the IP Network 314b. A Location-Based Services (LBS) application 345 is connected to the SLP 340. Although the SLP 340 and the LBS
application 345 are depicted as separate from the IP-based telecommunications network 320, the IP-based telecommunications network 320 can include either or both components. For example, the SLP 340 can be included in the IP-based telecommunications network 320. The SMLC 330 and the location database 335 can also be without the IP-based telecommunications network 320. The interactions between the various components depicted as part of the environment 300 are described with reference to, e.g., Figures 4-7.
Network Controller (UNC), or a GAN Controller (GANC)) 325, which is connected to a serving mobile location center (SMLC) 330 and to a location database 335. The IP-based telecommunications network 320 is also connected to an IP Network 314b. The IP
Networks 314a and 314b can be the same IP network, but are shown as distinct networks for illustrative purposes. A Secure User Plane Location (SUPL) Location Platform (SLP) 340 is connected to the IP Network 314b. A Location-Based Services (LBS) application 345 is connected to the SLP 340. Although the SLP 340 and the LBS
application 345 are depicted as separate from the IP-based telecommunications network 320, the IP-based telecommunications network 320 can include either or both components. For example, the SLP 340 can be included in the IP-based telecommunications network 320. The SMLC 330 and the location database 335 can also be without the IP-based telecommunications network 320. The interactions between the various components depicted as part of the environment 300 are described with reference to, e.g., Figures 4-7.
[0032] The location provision facility can be implemented in environments other than the environment 300 depicted. For example, the telecommunications device could be a non-lP-enabled mobile phone (e.g., a non-UMA enabled phone) that connects to an IP-enabled femtocell (e.g., a UMA-enabled femtocell) that is connected to an IP-based telecommunications network (e.g., a UMA network) over an IP
network.
As a second example, the telecommunications device 108 could be an analog telephone that connects to a IP-enabled terminal adaptor (e.g., a UMA-enabled terminal adaptor) that is connected to a IP-based telecommunications network (e.g., a UMA
network) over an IP network. As a third example, the telecommunications device could be an IP-enabled softmobile (e.g., a personal computer having a USB device with an embedded SIM and UMA softphone application) that is connected to an IP-based telecommunications network (e.g., a UMA network) over an IP network. The telecommunications device may also include other devices, such as wearable 31419-8036.W000ILEG14L13654627.1 -10-computers, devices that perform monitoring or tracking functions, and any other device (or combination of devices) that is IP-enabled (e.g., UMA-enabled), either in hardware, software, or a combination of both hardware and software. Therefore, those of skill in the art will understand that various configurations are possible and that the location provision facilify can be implemented in a wide variety of environments.
2. Re4isterincan IP-based Telecommunications Mobile Device [0033] Figure 4 is a flow diagram of a process 400 for registering an IP-based telecommunications mobile device (mobile station (MS)). An MS refers to any wireless device that can access network services over a radio interface. For purposes of illustration, the process 400 is described below in the context of the environment 300 of Figure 3. The process 400 begins at block 405 at which an MS sends a registration request (e.g., a URR_Registration_Request) to the network controller 325. The registration request can include data from the MS 108 that enables a determination of its location. At block 410, the network controller 325 begins the location process by initiafing a location request to the SMLC 330. In some embodiments, the locafion process is begun immediately after verifying IP Security (IPSEC) tunnel information with a signaling gateway (SGW) (not shown in Figure 3). The network controller 325 initiates the location request by sending a Perform Location Request message to the SMLC.
The Perform Location Request message may include a Location Services (LCS) Quality of Service (QoS) information element with the Response Time (RT) parameter set to one of the four valid entries (OOb to 11 b). The network controller 325 can determine the value of the RT parameter based upon a system parameter. In some embodiments the system parameter is named "Registration_PLRQ RT' and has a default value of Olb, thus setfing the RT parameter to 01b ("Low Delay").
network.
As a second example, the telecommunications device 108 could be an analog telephone that connects to a IP-enabled terminal adaptor (e.g., a UMA-enabled terminal adaptor) that is connected to a IP-based telecommunications network (e.g., a UMA
network) over an IP network. As a third example, the telecommunications device could be an IP-enabled softmobile (e.g., a personal computer having a USB device with an embedded SIM and UMA softphone application) that is connected to an IP-based telecommunications network (e.g., a UMA network) over an IP network. The telecommunications device may also include other devices, such as wearable 31419-8036.W000ILEG14L13654627.1 -10-computers, devices that perform monitoring or tracking functions, and any other device (or combination of devices) that is IP-enabled (e.g., UMA-enabled), either in hardware, software, or a combination of both hardware and software. Therefore, those of skill in the art will understand that various configurations are possible and that the location provision facilify can be implemented in a wide variety of environments.
2. Re4isterincan IP-based Telecommunications Mobile Device [0033] Figure 4 is a flow diagram of a process 400 for registering an IP-based telecommunications mobile device (mobile station (MS)). An MS refers to any wireless device that can access network services over a radio interface. For purposes of illustration, the process 400 is described below in the context of the environment 300 of Figure 3. The process 400 begins at block 405 at which an MS sends a registration request (e.g., a URR_Registration_Request) to the network controller 325. The registration request can include data from the MS 108 that enables a determination of its location. At block 410, the network controller 325 begins the location process by initiafing a location request to the SMLC 330. In some embodiments, the locafion process is begun immediately after verifying IP Security (IPSEC) tunnel information with a signaling gateway (SGW) (not shown in Figure 3). The network controller 325 initiates the location request by sending a Perform Location Request message to the SMLC.
The Perform Location Request message may include a Location Services (LCS) Quality of Service (QoS) information element with the Response Time (RT) parameter set to one of the four valid entries (OOb to 11 b). The network controller 325 can determine the value of the RT parameter based upon a system parameter. In some embodiments the system parameter is named "Registration_PLRQ RT' and has a default value of Olb, thus setfing the RT parameter to 01b ("Low Delay").
[0034] The SMLC 330 receives the Perform Location Request from the network controller 325 and at block 415 attempts to determine the location of the MS
108 using location technology algorithms. In some embodiments, the SMLC attempts to determine the location of the MS 108 using methods described in Intemational Application No.
PCT/US2007/066579, entided MOBILE COMPUTING DEVICE GEOGRAPHIC
LOCATION DETERMINATION, filed April 12, 2007 (Attorney Docket No.
31419-8036.wO00ILEGAL13654627.1 -11-31419.8030.WO), the entirety of which is hereby incorporated by reference, and/or the previously-referenced U.S. Provisional Application No. 60/853,086. After attempting to determine the location of the MS 108, the SMLC 330 sends a Perform Location Response message to the network controller 325.
108 using location technology algorithms. In some embodiments, the SMLC attempts to determine the location of the MS 108 using methods described in Intemational Application No.
PCT/US2007/066579, entided MOBILE COMPUTING DEVICE GEOGRAPHIC
LOCATION DETERMINATION, filed April 12, 2007 (Attorney Docket No.
31419-8036.wO00ILEGAL13654627.1 -11-31419.8030.WO), the entirety of which is hereby incorporated by reference, and/or the previously-referenced U.S. Provisional Application No. 60/853,086. After attempting to determine the location of the MS 108, the SMLC 330 sends a Perform Location Response message to the network controller 325.
[0035] After receiving the Perform Location Response message, at block 420 the network controller 325 verifies whether the SMLC 330 successfully determined the location of the MS 108, by checking to see if the Perform Location Response message includes a location response or location estimate. In some embodiments, the location estimate includes the estimated latitude and longitude of the MS 108. If the Perform Location Response message does not include a location estimate (such as the estimated latitude and longitude of the MS 108), the network controller logs an indication of the mobile device or subscriber identity (e.g., an Intemational Mobile Subscriber Identity (IMSI)) of the MS 108, the MAC address of its access point and a timestamp.
The process 400 then continues at block 440, at which the network controller 325 sends a registration rejection message (e.g., a URR_Registration_Reject with an error code of "Geo-Location Unknown") to the MS 108. The process 400 then ends.
The process 400 then continues at block 440, at which the network controller 325 sends a registration rejection message (e.g., a URR_Registration_Reject with an error code of "Geo-Location Unknown") to the MS 108. The process 400 then ends.
[0036] If the SMLC 330 successfully determined the location of the MS 108 (e.g., if the Perform Location Response message includes a location estimate including an estimated latitude and longitude), the process 400 instead continues at block 425, at which the network controller 325 stores the loca8on (e.g., the estimated latitude and tongitude) in the location database 335. The location database 335 can be a Dynamic Host Configuration Protocol (DHCP) server database, a DHCP-like server database, or any standalone database. At block 430 the network controller 325 sends a registration acceptance message (e.g., a URR_Registration Accept) that includes the location to the MS 108. Alternatively, instead of including the location in the registration acceptance message, the network controller 325 can instead obtain the location from the location database 335 and provide it to the MS 108 using DHCP or a protocol that is generally similar to DHCP. For example, another protocol that can be used is the HTTP
Enabled Location Delivery (HELD) protocol. The network controller 325 can provide the location to the MS 108 on a periodic or as-needed basis. For example, as the MS 108 moves, 31419-8036.WOOOVI.EGJU.13654627.1 -12-the network controller 325 can provide the MS 108 with updated locations. At block 435 the network controller MS 108 stores the location and a timestamp indicating the date and time of the storage (or of the location determination). The process 400 then ends.
3. Providing Mobile Device Location Information to an LBS Application [0037] Figure 5 is a flow diagram of a process 500 for providing location information of an IP-based telecommunications mobile device (MS) to an LBS application or value added client over SUPL. An LBS application generally refers to any application that wishes to obtain the location of the MS 108. Examples of LBS applications include, but are not limited to: a friend finder application; a security application; an emergency services application (e.g., E911); a driving directions application; and an advertising services application. For purposes of illustration, the process 500 Is described below in the context of the environment 300 of Figure 3.
Enabled Location Delivery (HELD) protocol. The network controller 325 can provide the location to the MS 108 on a periodic or as-needed basis. For example, as the MS 108 moves, 31419-8036.WOOOVI.EGJU.13654627.1 -12-the network controller 325 can provide the MS 108 with updated locations. At block 435 the network controller MS 108 stores the location and a timestamp indicating the date and time of the storage (or of the location determination). The process 400 then ends.
3. Providing Mobile Device Location Information to an LBS Application [0037] Figure 5 is a flow diagram of a process 500 for providing location information of an IP-based telecommunications mobile device (MS) to an LBS application or value added client over SUPL. An LBS application generally refers to any application that wishes to obtain the location of the MS 108. Examples of LBS applications include, but are not limited to: a friend finder application; a security application; an emergency services application (e.g., E911); a driving directions application; and an advertising services application. For purposes of illustration, the process 500 Is described below in the context of the environment 300 of Figure 3.
(0038] The process 500 begins at block 505, at which the LBS application 345 requests the location of the MS 108 from the SLP 340. As previously noted, the LBS
application 345 and the SLP 340 can both be located within the IP-based telecommunications network 320. In some embodiments, however, only the SLP 340 is located within the IP-based telecommunications network 320, in which case the LBS
Application 345 connects to it via the IP Network 314b. In other embodiments, the LBS
Application 345 is within the IP-based telecommunications network 320 and the is without, and they connect to each other via the IP Network 314b. After receiving the request from the LBS Application 345, at block 510 the SLP 340 initiates a service discovery process and initiates a session with the MS 108. At block 515 the sends to the MS 108 a SUPL INIT message. The SUPL INIT message includes various parameters, such as: 1) Positioning Method, which includes the positioning technology desired by the SLP 340; 2) Notification, which includes instructions to the MS
108 with respect to notification and privacy policies of the LBS application 345; 3) SLP Address, which includes an electronic address of the SLP 340; 4) QoP, which includes the desired Quality of Position (location); 5) SLP Mode, which includes an indication of the proxy mode of the SLP; 6) MAC, which indudes a Message Authentication Code (MAC) which 31418-8036.W000ILEGAL13654627.1 -13-may be used as integrity protection of the SUPL INIT message; and 7) Key Identity, which includes a key identity that identifies a key to be used to verify the MAC.
application 345 and the SLP 340 can both be located within the IP-based telecommunications network 320. In some embodiments, however, only the SLP 340 is located within the IP-based telecommunications network 320, in which case the LBS
Application 345 connects to it via the IP Network 314b. In other embodiments, the LBS
Application 345 is within the IP-based telecommunications network 320 and the is without, and they connect to each other via the IP Network 314b. After receiving the request from the LBS Application 345, at block 510 the SLP 340 initiates a service discovery process and initiates a session with the MS 108. At block 515 the sends to the MS 108 a SUPL INIT message. The SUPL INIT message includes various parameters, such as: 1) Positioning Method, which includes the positioning technology desired by the SLP 340; 2) Notification, which includes instructions to the MS
108 with respect to notification and privacy policies of the LBS application 345; 3) SLP Address, which includes an electronic address of the SLP 340; 4) QoP, which includes the desired Quality of Position (location); 5) SLP Mode, which includes an indication of the proxy mode of the SLP; 6) MAC, which indudes a Message Authentication Code (MAC) which 31418-8036.W000ILEGAL13654627.1 -13-may be used as integrity protection of the SUPL INIT message; and 7) Key Identity, which includes a key identity that identifies a key to be used to verify the MAC.
[0039] At block 520 the MS 108 responds to the SUPL INIT message by sending a SUPL POS INIT message to the SLP 340. The SUPL POS INIT message includes .various parameters, such as: 1) SET capabilities, which includes the capabilities of the MS 108; 2) Requested Assistance Data, which includes requested GPS assistance data;
3) Location ID, which includes the cell information of the MS 108; 4) SUPLPOS, which includes a SUPLPOS message; 5) Ver, which includes a hash'of the SUPL INIT
message; and 6) Position, which includes the location of the MS 108. In some embodiments, the Position parameter includes the location previously stored by the MS
108 at block 435, as well as the timestamp, a location certainty factor, and/or a location confidence factor, and, if the SMLC hadn't successfully determined the location of the MS 108 (e.g., at block 440 of Figure 4), the reason for the failure. At block 525 the SLP
terminates the session with the MS 108 by sending it a SUPL END message. The SUPL END message includes various parameters, such as: 1) Position, which includes the location resuR of the MS 108; 2) Status Code, which includes the status of the message; and 3) Ver, which includes a hash of the SUPL INIT message. At block the SLP 340 provides the location of the MS 108 to the LBS application 345.
The process 500 then ends.
3) Location ID, which includes the cell information of the MS 108; 4) SUPLPOS, which includes a SUPLPOS message; 5) Ver, which includes a hash'of the SUPL INIT
message; and 6) Position, which includes the location of the MS 108. In some embodiments, the Position parameter includes the location previously stored by the MS
108 at block 435, as well as the timestamp, a location certainty factor, and/or a location confidence factor, and, if the SMLC hadn't successfully determined the location of the MS 108 (e.g., at block 440 of Figure 4), the reason for the failure. At block 525 the SLP
terminates the session with the MS 108 by sending it a SUPL END message. The SUPL END message includes various parameters, such as: 1) Position, which includes the location resuR of the MS 108; 2) Status Code, which includes the status of the message; and 3) Ver, which includes a hash of the SUPL INIT message. At block the SLP 340 provides the location of the MS 108 to the LBS application 345.
The process 500 then ends.
[0040] Although described with respect to providing the location of the MS 108 to the LBS application 345 over SUPL, the process 500 can be used to provide the location of any device capable of communicating over a SUPL network to any other device that is also capable of communicating over a SUPL network. Such a device is called a SUPL
Enabled Terminal (SET). Examples of SETs include the previously-mentioned MS
and the LBS application 345, user equipment (UE) in a Universal Mobile Telecommunications System (UMTS), and a personal computer (PC) over an IP-based network.
31419-8ose.wooG/.EGAL136e4627.1 -~4-4. Mobile Device ReQstration [0041] Figure 6 is a call flow diagram 600 depicting the registration of an IP-based telecommunications mobile device (MS). At 605 the MS 108 sends a registration request message to the network controller 325. At 610 the network controller requests a location determination from the SMLC 330. At 615 the SMLC 330 determines the location of the MS 108. At 620 the SMLC 330 returns the location to the network controller 325. At 625 the network controller 325 sends a registration acceptance message with the location to the MS 108. At 630 the MS 108 stores the location. At 635 the SMLC 330 stores the location in the location database 335. At 635 the SMLC 330 (or the network controller 325 or another component, not shown) can also create a mapping between the location and the MAC address of the access point of the MS 108 and store this mapping in the location database 335.
5. Provision of Location Information to LBS AaQications [0042] Figure 7 is a call flow diagram 700 depicting the provision of location information of an IP-based telecommunications mobile device (MS) to an LBS
application. At 705 a service discovery process is initiated. At 710 the LBS
application 345 requests that the SLP 340 provide a location of the MS 108. At 715 the SLP
sends a SUPL INIT message to the MS 108 through the IP-based telecommunications network 320. At 720 the MS 108 sends a SUPL POS INIT message to the SLP 340 through the IP-based telecommunications network 320. At 725 the SLP 340 sends a SUPL END message to the MS 108 through the IP-based telecomrnunications network 320. At 730 the SLP 340 provides the location to the LBS application 345. At 735 a service delivery process is inltiated. The service delivery process can include delivering services from the LBS application 345 to the MS 108. Examples of services include security services, emergency services, advertisements, locating services, directions, etc.
Enabled Terminal (SET). Examples of SETs include the previously-mentioned MS
and the LBS application 345, user equipment (UE) in a Universal Mobile Telecommunications System (UMTS), and a personal computer (PC) over an IP-based network.
31419-8ose.wooG/.EGAL136e4627.1 -~4-4. Mobile Device ReQstration [0041] Figure 6 is a call flow diagram 600 depicting the registration of an IP-based telecommunications mobile device (MS). At 605 the MS 108 sends a registration request message to the network controller 325. At 610 the network controller requests a location determination from the SMLC 330. At 615 the SMLC 330 determines the location of the MS 108. At 620 the SMLC 330 returns the location to the network controller 325. At 625 the network controller 325 sends a registration acceptance message with the location to the MS 108. At 630 the MS 108 stores the location. At 635 the SMLC 330 stores the location in the location database 335. At 635 the SMLC 330 (or the network controller 325 or another component, not shown) can also create a mapping between the location and the MAC address of the access point of the MS 108 and store this mapping in the location database 335.
5. Provision of Location Information to LBS AaQications [0042] Figure 7 is a call flow diagram 700 depicting the provision of location information of an IP-based telecommunications mobile device (MS) to an LBS
application. At 705 a service discovery process is initiated. At 710 the LBS
application 345 requests that the SLP 340 provide a location of the MS 108. At 715 the SLP
sends a SUPL INIT message to the MS 108 through the IP-based telecommunications network 320. At 720 the MS 108 sends a SUPL POS INIT message to the SLP 340 through the IP-based telecommunications network 320. At 725 the SLP 340 sends a SUPL END message to the MS 108 through the IP-based telecomrnunications network 320. At 730 the SLP 340 provides the location to the LBS application 345. At 735 a service delivery process is inltiated. The service delivery process can include delivering services from the LBS application 345 to the MS 108. Examples of services include security services, emergency services, advertisements, locating services, directions, etc.
[0043] In some embodiments, as an altemative to or in addition to sending the SUPL INIT message to the MS 108, the IP-based telecommunications network 320 (e.g., a component thereof) can get the location of the MS 108 by retrieving it from the location database 335. The SUPL INIT message can include a QoP parameter which includes the quality of location of the MS 108 desired by the LBS application 345. If the 31419-8036.W000/LEGAL13654627.1 -95-QoP parameter indicates a desired or acceptable low quality of location (e.g., a coarse location), at 740 the IP-based telecommunications network 320 can get the stored location of the MS 108 from the location database 335 and provide it to the SLP 340, which in tum provides it to the LBS application 345. The IP-based telecommunications network 320 can thus avoid sending the SUPL INIT message to the MS 108. For example, if the LBS application 345 provides weather information, it may only need to determine the location of the MS 108 within several miles, and thus the LBS
application 345 can specify a desired lower quality of location. If the desired quality of location is low, the IP-based telecommunications network 320 may be able to satisfy it by retrieving the location of the MS 108 from the location database 335 and providing the retrieved location to the LBS app 345. Altematively, the IP-based telecommunications network 320 can send the SUPL INIT message to the MS 108 and receive the SUPL POS INIT
message, which includes the position parameter, which includes the location certainty factor and/or the location confidence factor. These factors can be used in determining whether the desired QoP is met.
application 345 can specify a desired lower quality of location. If the desired quality of location is low, the IP-based telecommunications network 320 may be able to satisfy it by retrieving the location of the MS 108 from the location database 335 and providing the retrieved location to the LBS app 345. Altematively, the IP-based telecommunications network 320 can send the SUPL INIT message to the MS 108 and receive the SUPL POS INIT
message, which includes the position parameter, which includes the location certainty factor and/or the location confidence factor. These factors can be used in determining whether the desired QoP is met.
[0044] If instead the QoP parameter indicates a desired high quality of location (e.g., a fine location), the IP-based telecommunications network 320 can request the SMLC 330 (or other system) determine the location of the MS 108 using data from the MS 108 that enables a determination of the location. This enables the IP-based telecommunications network 320 to provide the SLP 340 and the LBS application with a potentially more accurate location of the MS, instead of sending on the location previously-stored by the MS 108 or location database 335, which may not be suitable for a desired high quality of location. For example,* if the LBS application 345 provides advertisements, it may need to determine the location of the MS 108 within a very narrow range (e.g., within or adjacent to a retail location), and thus the LBS
application 345 can specify a desired high quality of location. The desired high quality of location can require the IP-based telecommunications network 320 to obtain fresher data from the MS 108 that enables a more precise determination of its location. A more precise location can be determined using Global Navigation Satellite System (GNSS), GPS, nework-assisted GPS (A-GPS), network measurements, triangulation methods, or any combination of these and/or other location techniques. The more precise location can 31419-8036.W000/LEGAL13654627.1 -16-then be stored in the location database 335, to potentially satisfy future location requests.
application 345 can specify a desired high quality of location. The desired high quality of location can require the IP-based telecommunications network 320 to obtain fresher data from the MS 108 that enables a more precise determination of its location. A more precise location can be determined using Global Navigation Satellite System (GNSS), GPS, nework-assisted GPS (A-GPS), network measurements, triangulation methods, or any combination of these and/or other location techniques. The more precise location can 31419-8036.W000/LEGAL13654627.1 -16-then be stored in the location database 335, to potentially satisfy future location requests.
[0045] The provision of location information of the MS 108 to the LBS
application 345 described with reference to Figure 7 is performed over a user plane (e.g., SUPL, CDMA user plane, etc.). One advantage of performing the provision of location information over a user plane is that a user plane enables the abstraction of many of the underlying network components below the IP layer. This allows an LBS
application to communicate with a MS over an all-IP or generally all-IP connection, which can facilitate requesting and providing location-based services. The Open Mobile Alliance (OMA) is another example of a user plane that provides an abstraction above all protocol layers below the IP layer. Thus, the physical and data link layers of a control plane may be ignored, which facilitates creation and delivery of location-based services.
application 345 described with reference to Figure 7 is performed over a user plane (e.g., SUPL, CDMA user plane, etc.). One advantage of performing the provision of location information over a user plane is that a user plane enables the abstraction of many of the underlying network components below the IP layer. This allows an LBS
application to communicate with a MS over an all-IP or generally all-IP connection, which can facilitate requesting and providing location-based services. The Open Mobile Alliance (OMA) is another example of a user plane that provides an abstraction above all protocol layers below the IP layer. Thus, the physical and data link layers of a control plane may be ignored, which facilitates creation and delivery of location-based services.
[0046] However, the provision of location information of the MS 108 to the LBS
application 345 can also be used over a control plane (e.g., CDMA control plane, WCDMA control plane, GSM/3GPP control plane, etc.), which generally use the circuit-switched wireless signaling layer (e.g., SS7). Those of skill in 'the art will therefore understand that the provision of location information of the MS 108 to the LBS
application 345 can be used over both user plane and control plane architectures.
6. Conclusion [0047j As described above, the location provision facifity includes many features.
For example, it provides services to LBS applications within an IP-based telecommunications architecture. The facility also allows for providing location data to an LBS application over a network employing a user plane such as SUPL. The facility can store location data both in a database associated with an IP-based telecommunications network as well as on the MS. This allows the facility to satisfy requests for location of the MS by retrieving stored location data from the MS, from the database, or from both. When the facility receives a request for more detailed or accurate location data, the facility can calculate a more detailed or accurate location of a MS based upon the request. Location data stored in the database and the MS can be 31418-8036. W000ILEGAL13654627.1 -17-used for LBS applications as well as for other purposes. The facility also provides for other features and advantages.
[0048] Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise," "comprising," and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to.' As used herein, the terms "connected,"
"coupled," or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words "herein," "above," "below," and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word "or," in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
[0049] The above detailed description of embodiments of the system is not intended to be exhaustive or to limit the system to the precise form disclosed above.
While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes, messages or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide altemative or subcombinations. Each of these processes, messages or blocks may be implemented in a variety of different ways. Also, while processes, messages or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples;
alternative implementations may employ differing values or ranges.
31419-8036.W000/LEGAL13654627.1 -18-[0050] The teachings of the methods and system provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments. Some network elements are described herein as performing certain functions. Those functions could be performed by other elements in the same or differing networks, which could reduce the number of network elements.
Alternatively or additionally, network elements performing those functions could be replaced by two or more elements to perform portions of those functions.
[0051] Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the technology can be modified, if necessary, to employ the systems, funcdons, and concepts of the various references described above to provide yet further embodiments of the technology.
[0052] These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain embodiments of the technology, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Acxordingly, the actual scope of the invention encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the invention under the claims.
[0053] While certain aspects of the technology are presented below in certain claim forms, the inventors contemplate the various aspects of the technology in any number of 31419-8036.W0001LEGAL13654627.1 -19-claim forms. For example, while only one aspect of the invention is recited as embodied in a computer-readable medium, other aspects may likewise be embodied in a computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the technology.
31419-8036.W000/LE0AL13654627.1 -20-
application 345 can also be used over a control plane (e.g., CDMA control plane, WCDMA control plane, GSM/3GPP control plane, etc.), which generally use the circuit-switched wireless signaling layer (e.g., SS7). Those of skill in 'the art will therefore understand that the provision of location information of the MS 108 to the LBS
application 345 can be used over both user plane and control plane architectures.
6. Conclusion [0047j As described above, the location provision facifity includes many features.
For example, it provides services to LBS applications within an IP-based telecommunications architecture. The facility also allows for providing location data to an LBS application over a network employing a user plane such as SUPL. The facility can store location data both in a database associated with an IP-based telecommunications network as well as on the MS. This allows the facility to satisfy requests for location of the MS by retrieving stored location data from the MS, from the database, or from both. When the facility receives a request for more detailed or accurate location data, the facility can calculate a more detailed or accurate location of a MS based upon the request. Location data stored in the database and the MS can be 31418-8036. W000ILEGAL13654627.1 -17-used for LBS applications as well as for other purposes. The facility also provides for other features and advantages.
[0048] Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise," "comprising," and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to.' As used herein, the terms "connected,"
"coupled," or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words "herein," "above," "below," and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word "or," in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
[0049] The above detailed description of embodiments of the system is not intended to be exhaustive or to limit the system to the precise form disclosed above.
While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes, messages or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide altemative or subcombinations. Each of these processes, messages or blocks may be implemented in a variety of different ways. Also, while processes, messages or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples;
alternative implementations may employ differing values or ranges.
31419-8036.W000/LEGAL13654627.1 -18-[0050] The teachings of the methods and system provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments. Some network elements are described herein as performing certain functions. Those functions could be performed by other elements in the same or differing networks, which could reduce the number of network elements.
Alternatively or additionally, network elements performing those functions could be replaced by two or more elements to perform portions of those functions.
[0051] Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the technology can be modified, if necessary, to employ the systems, funcdons, and concepts of the various references described above to provide yet further embodiments of the technology.
[0052] These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain embodiments of the technology, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Acxordingly, the actual scope of the invention encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the invention under the claims.
[0053] While certain aspects of the technology are presented below in certain claim forms, the inventors contemplate the various aspects of the technology in any number of 31419-8036.W0001LEGAL13654627.1 -19-claim forms. For example, while only one aspect of the invention is recited as embodied in a computer-readable medium, other aspects may likewise be embodied in a computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the technology.
31419-8036.W000/LE0AL13654627.1 -20-
Claims (25)
1. In a system having multiple wireless handheld devices capable of communicating over both a cellular phone network and one or more internet protocol (IP)-based wireless local area computer networks (WLAN), wherein each IP-based WLAN includes at least one wireless access point for communicating with the handheld devices under a known IP-based WLAN protocol, wherein the IP-based WLAN
protocol differs from a wireless protocol for the cellular phone network, wherein the wireless protocol for the cellular phone network includes multiple layers in a protocol stack including an IP layer, and wherein the handheld devices communicate with at least one server computer via the WLAN, a method associated with the providing of location-based services, comprising:
receiving a registration request from one of the multiple handheld devices, wherein the one handheld device is configured to communicate over the cellular phone network under the wireless protocol and over the WLANs under the WLAN protocol, and wherein the registration request is received for communication over one of the WLANs;
obtaining information regarding a geographic location of the one handheld device registering the one handheld device for communication over the one WLAN, wherein the registering comprises storing the information regarding the geographic location of the one handheld device; and providing the information regarding the geographic location of the one handheld device to a location-based service provider in response to a location request from the location-based service provider, wherein the providing comprises providing the information over a user plane, wherein the user plane employs an abstraction platform configured for delivering services over the cellular phone network, and wherein the abstraction platform permits the location-based service provider to program applications for delivering services over the cellular phone network by ignoring protocol stack layers below the IP layer.
protocol differs from a wireless protocol for the cellular phone network, wherein the wireless protocol for the cellular phone network includes multiple layers in a protocol stack including an IP layer, and wherein the handheld devices communicate with at least one server computer via the WLAN, a method associated with the providing of location-based services, comprising:
receiving a registration request from one of the multiple handheld devices, wherein the one handheld device is configured to communicate over the cellular phone network under the wireless protocol and over the WLANs under the WLAN protocol, and wherein the registration request is received for communication over one of the WLANs;
obtaining information regarding a geographic location of the one handheld device registering the one handheld device for communication over the one WLAN, wherein the registering comprises storing the information regarding the geographic location of the one handheld device; and providing the information regarding the geographic location of the one handheld device to a location-based service provider in response to a location request from the location-based service provider, wherein the providing comprises providing the information over a user plane, wherein the user plane employs an abstraction platform configured for delivering services over the cellular phone network, and wherein the abstraction platform permits the location-based service provider to program applications for delivering services over the cellular phone network by ignoring protocol stack layers below the IP layer.
2. The method of claim 1 wherein the handheld devices employ at least a portion of an Unlicensed Mobile Access (UMA) protocol to communicate with the WLAN, and wherein providing the information over the user plane comprises providing the information over Secure User Plane Location (SUPL).
3. The method of claim 1 wherein the storing comprises locally storing on the one handheld device the information regarding the geographic location of the one handheld device, and wherein the method further comprises:
receiving at the one handheld device a location request for the one handheld device, wherein the location request is from one of multiple location-based service providers, and wherein the location request includes a quality of location parameter;
determining at the one handheld device whether the locally stored information regarding the geographic location of the one handheld device is acceptable based on the quality of location parameter; and, if acceptable, then providing to the location-based service provider the information regarding the geographic location of the one handheld device.
receiving at the one handheld device a location request for the one handheld device, wherein the location request is from one of multiple location-based service providers, and wherein the location request includes a quality of location parameter;
determining at the one handheld device whether the locally stored information regarding the geographic location of the one handheld device is acceptable based on the quality of location parameter; and, if acceptable, then providing to the location-based service provider the information regarding the geographic location of the one handheld device.
4. The method of claim 1 wherein the storing comprises storing the information regarding the geographic location of the one handheld device locally on the one handheld device.
5. The method of claim 1 wherein the storing comprises storing the information regarding the geographic location of the one handheld device in a database coupled to the server computer.
6. The method of claim 1 wherein the storing comprises storing the information regarding the geographic location of the one handheld device both locally on the one handheld device and in a database coupled to the server computer.
7. The method of claim 1, wherein registering further comprises obtaining an electronic address associated with one access point of a WLAN;
associating the information regarding the geographic location of the one handheld device with the electronic address; and storing the associated information.
associating the information regarding the geographic location of the one handheld device with the electronic address; and storing the associated information.
8. The method of claim 1 wherein the storing comprises storing the information regarding the geographic location of the one handheld device locally on the one handheld device, wherein the location request includes a quality of location parameter, and wherein the providing comprises providing the locally stored information to the location-based services provider if acceptable based on the quality of location parameter, or if unacceptable, then computing a new geographic location of the one handheld device and providing the new geographic location in response to the location request.
9. The method of claim 1 wherein the obtaining information, obtaining an electronic address, storing, associating and providing are performed on the one handheld device.
10. The method of claim 1, further comprising receiving a location-based service at the one handheld device directly from the location-based service provider over the WLAN.
11. A system for receiving location-based services at a mobile device, comprising:
means for providing communications at the mobile device based on a Generic Access Network (GAN) protocol;
means for obtaining information associated with a physical location of the mobile device;
means for providing the information regarding the physical location of the mobile device to a location services client in response to a location request from the location services client; and means for receiving content or at least one service from the location services client based at least in part on the provided information regarding the physical location of the mobile device.
means for providing communications at the mobile device based on a Generic Access Network (GAN) protocol;
means for obtaining information associated with a physical location of the mobile device;
means for providing the information regarding the physical location of the mobile device to a location services client in response to a location request from the location services client; and means for receiving content or at least one service from the location services client based at least in part on the provided information regarding the physical location of the mobile device.
12. The system of claim 11, further comprising means for storing the information regarding the physical location of the mobile device.
13. The system of claim 11 wherein the means for providing comprises means for providing the physical location of the mobile device to the location services client over a user plane.
14. The system of claim 13 wherein the means for providing the physical location of the mobile device comprises means for providing the physical location of the mobile device to the location services client over Secure User Plane Location (SUPL).
15. The system of claim 11 wherein the means for providing the information comprises means for providing the physical location of the mobile device to the location services client over a control plane.
16. A computer-readable medium encoded with a computer program to at least assist in providing location-based services for a mobile telecommunications device, the computer program including instructions to perform a method comprising:
obtaining information associated with a geographic location of the mobile telecommunications device, wherein the mobile telecommunications device is configured for voice communications over a cellular network; and for communications over an IP-based network;
during registration of the mobile communication device for communications over the IP-based network, storing the information regarding the geographic location of the mobile telecommunications device; and providing the information regarding the geographic location of the mobile telecommunications device to a location services client in response to a location request from the location services client.
obtaining information associated with a geographic location of the mobile telecommunications device, wherein the mobile telecommunications device is configured for voice communications over a cellular network; and for communications over an IP-based network;
during registration of the mobile communication device for communications over the IP-based network, storing the information regarding the geographic location of the mobile telecommunications device; and providing the information regarding the geographic location of the mobile telecommunications device to a location services client in response to a location request from the location services client.
17. The computer-readable medium of claim 16 wherein the providing comprises providing the information regarding the geographic location of the mobile telecommunications device to a location services client in response to a location request from the location services client over Secure User Plane Location (SUPL).
18. A computer-implemented method associated with location-based services in a mobile telecommunications network, wherein the mobile telecommunications network includes a cellular network, the method comprising:
obtaining information associated with geographic locations of multiple mobile telecommunications devices operating within the mobile telecommunications network, wherein the mobile telecommunications devices are configured for voice communications over the cellular network, and wherein the mobile telecommunications devices are also configured for voice communications over Internet Protocol (IP)-based wireless local area networks (WLANs);
registering the mobile communications devices for voice communications over one or more IP-based WLANs;
storing the information associated with geographic locations of multiple mobile telecommunications devices; and providing the information regarding the physical location of the mobile telecommunications device in response to received requests.
obtaining information associated with geographic locations of multiple mobile telecommunications devices operating within the mobile telecommunications network, wherein the mobile telecommunications devices are configured for voice communications over the cellular network, and wherein the mobile telecommunications devices are also configured for voice communications over Internet Protocol (IP)-based wireless local area networks (WLANs);
registering the mobile communications devices for voice communications over one or more IP-based WLANs;
storing the information associated with geographic locations of multiple mobile telecommunications devices; and providing the information regarding the physical location of the mobile telecommunications device in response to received requests.
19. The method of claim 18 wherein the mobile telecommunications devices employ an Unlicensed Mobile Access (UMA) protocol.
20. The method of claim 18, further comprising updating the information associated with geographic locations of multiple mobile telecommunications devices as the mobile telecommunications devices move about the cellular and wireless local area networks, wherein the updating is performed in a Dynamic Host Configuration Protocol (DHCP)-like manner.
21. A system for providing location data for each of multiple wireless handsets operating within a telecommunications network, the system comprising:
a server computer configured to:
receive a request for a location of one of the multiple wireless handsets, wherein the request includes at least one parameter;
if acceptable based on the parameter, provide first information associated with a geographic location of the one wireless handset, wherein the first information associated with the geographic location of the one wireless handset is stored at the handset; and otherwise, determining and providing second information associated with the geographic location of the one wireless handset, wherein the second information associated with the geographic location of the one wireless handset has a higher quality than the first information associated with the geographic location of the one wireless handset.
a server computer configured to:
receive a request for a location of one of the multiple wireless handsets, wherein the request includes at least one parameter;
if acceptable based on the parameter, provide first information associated with a geographic location of the one wireless handset, wherein the first information associated with the geographic location of the one wireless handset is stored at the handset; and otherwise, determining and providing second information associated with the geographic location of the one wireless handset, wherein the second information associated with the geographic location of the one wireless handset has a higher quality than the first information associated with the geographic location of the one wireless handset.
22. The system of claim 21, further comprising:
a location database coupled to the server computer; and, wherein the server computer is further configured to:
obtain information associated with geographic locations of multiple wireless handsets operating within the telecommunications network; and, store in the location database the information associated with geographic locations of multiple wireless handsets.
a location database coupled to the server computer; and, wherein the server computer is further configured to:
obtain information associated with geographic locations of multiple wireless handsets operating within the telecommunications network; and, store in the location database the information associated with geographic locations of multiple wireless handsets.
23. The system of claim 21 wherein the higher quality comprises more recent or more accurate information associated with the geographic location of the one wireless handset.
24. The system of claim 21 wherein the server computer is further configured to provide information associated with the geographic location of the one wireless handset to the one wireless handset.
25. The system of claim 24 wherein the information is provided to the one wireless handset in a Dynamic Host Configuration Protocol (DHCP)-like manner.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US85308606P | 2006-10-20 | 2006-10-20 | |
US60/853,086 | 2006-10-20 | ||
PCT/US2007/082136 WO2008051929A2 (en) | 2006-10-20 | 2007-10-22 | System and method for utilizing ip-based wireless telecommunications client location data |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2620617A1 true CA2620617A1 (en) | 2008-04-20 |
Family
ID=39325313
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002620617A Abandoned CA2620617A1 (en) | 2006-10-20 | 2007-10-22 | System and method for utilizing ip-based wireless telecommunications client location data |
Country Status (3)
Country | Link |
---|---|
US (3) | US8953567B2 (en) |
CA (1) | CA2620617A1 (en) |
WO (1) | WO2008051929A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2544468B1 (en) * | 2010-08-16 | 2020-11-11 | ZTE Corporation | Region access platform, mobile positioning method and system |
Families Citing this family (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7623857B1 (en) * | 2005-10-21 | 2009-11-24 | At&T Intellectual Property I, L.P. | Intelligent pico-cell for transport of wireless device communications over wireline networks |
EP1938488B1 (en) | 2005-10-21 | 2015-09-09 | T-Mobile, USA, Inc | System and method for determining device location in an ip-based wireless telecommunications network |
EP2014111B1 (en) | 2006-04-13 | 2017-09-06 | T-Mobile USA, Inc. | Mobile computing device geographic location determination |
US8326296B1 (en) | 2006-07-12 | 2012-12-04 | At&T Intellectual Property I, L.P. | Pico-cell extension for cellular network |
EP2084917B1 (en) | 2006-10-20 | 2019-05-01 | T-Mobile USA, Inc. | System and method for determining a subscriber's zone information |
CA2620249C (en) | 2006-10-20 | 2016-04-19 | T-Mobile Usa, Inc. | Two stage mobile device geographic location determination |
US8953567B2 (en) * | 2006-10-20 | 2015-02-10 | T—Mobile USA, Inc. | System and method for utilizing IP-based wireless telecommunications client location data |
US9985817B2 (en) * | 2006-11-14 | 2018-05-29 | Tp Lab, Inc. | System and method for a universal phone number service |
US8798639B2 (en) | 2007-01-17 | 2014-08-05 | Qualcomm Incorporated | Method and apparatus for using historic network information for determining approximate position |
US9066199B2 (en) | 2007-06-28 | 2015-06-23 | Apple Inc. | Location-aware mobile device |
US8385946B2 (en) | 2007-06-28 | 2013-02-26 | Apple Inc. | Disfavored route progressions or locations |
US8108144B2 (en) | 2007-06-28 | 2012-01-31 | Apple Inc. | Location based tracking |
US9109904B2 (en) | 2007-06-28 | 2015-08-18 | Apple Inc. | Integration of map services and user applications in a mobile device |
US8311526B2 (en) | 2007-06-28 | 2012-11-13 | Apple Inc. | Location-based categorical information services |
US8290513B2 (en) | 2007-06-28 | 2012-10-16 | Apple Inc. | Location-based services |
US8059631B2 (en) * | 2007-07-13 | 2011-11-15 | Phybridge, Inc. | Location system and method for assisting emergency services in identifying the physical location of an IP telephony user |
US8977294B2 (en) | 2007-10-10 | 2015-03-10 | Apple Inc. | Securely locating a device |
US9661481B2 (en) * | 2007-11-15 | 2017-05-23 | Open Invention Network, Llc | System, method, and computer-readable medium for indirect routing of mobile-originated SMS messages for a mobile station attached with an IP-femtocell system |
EP2073582A1 (en) * | 2007-12-20 | 2009-06-24 | Mitsubishi Electric R&D Centre Europe B.V. | Method for controlling the operation of a base station of a wireless cellular telecommunication network |
US8626223B2 (en) | 2008-05-07 | 2014-01-07 | At&T Mobility Ii Llc | Femto cell signaling gating |
US9250092B2 (en) | 2008-05-12 | 2016-02-02 | Apple Inc. | Map service with network-based query for search |
US8719420B2 (en) | 2008-05-13 | 2014-05-06 | At&T Mobility Ii Llc | Administration of access lists for femtocell service |
US8094551B2 (en) | 2008-05-13 | 2012-01-10 | At&T Mobility Ii Llc | Exchange of access control lists to manage femto cell coverage |
US8743776B2 (en) | 2008-06-12 | 2014-06-03 | At&T Mobility Ii Llc | Point of sales and customer support for femtocell service and equipment |
US8620255B2 (en) | 2008-06-16 | 2013-12-31 | Qualcomm Incorporated | Method and apparatus for supporting emergency calls and location for femto access points |
US8516001B2 (en) * | 2008-06-24 | 2013-08-20 | Microsoft Corporation | Context platform |
US8369867B2 (en) | 2008-06-30 | 2013-02-05 | Apple Inc. | Location sharing |
US8719208B2 (en) | 2008-10-29 | 2014-05-06 | Microsoft Corporation | Certainty factor decay |
US8180368B2 (en) | 2008-11-11 | 2012-05-15 | Trueposition, Inc. | Femto-cell location by direct methods |
US8200239B2 (en) * | 2008-11-11 | 2012-06-12 | Trueposition, Inc. | Femto-cell location by proxy methods |
JP5440511B2 (en) * | 2008-12-26 | 2014-03-12 | 日本電気株式会社 | COMMUNICATION SYSTEM, FEMTO CELL BASE STATION, AND COMMUNICATION METHOD |
US8984615B2 (en) * | 2009-04-08 | 2015-03-17 | At&T Mobility Ii, Llc | Web to IMS registration and authentication for an unmanaged IP client device |
US8670748B2 (en) | 2009-05-01 | 2014-03-11 | Apple Inc. | Remotely locating and commanding a mobile device |
US8718592B2 (en) * | 2009-05-15 | 2014-05-06 | T-Mobile Usa, Inc. | Mobile device location determination using micronetworks |
US8311557B2 (en) * | 2009-05-15 | 2012-11-13 | T-Mobile Usa, Inc. | Facility for selecting a mobile device location determination technique |
US8930438B2 (en) | 2009-06-17 | 2015-01-06 | Apple Inc. | Push-based location update |
US20110002239A1 (en) * | 2009-07-06 | 2011-01-06 | Muthaiah Venkatachalam | Determining the Location of a Femtocell |
US8619735B2 (en) * | 2009-07-16 | 2013-12-31 | Blackberry Limited | Methods and apparatus to register with external networks in wireless network environments |
CN102036162A (en) * | 2009-09-24 | 2011-04-27 | 中兴通讯股份有限公司 | Location system, method and terminal |
US8510801B2 (en) | 2009-10-15 | 2013-08-13 | At&T Intellectual Property I, L.P. | Management of access to service in an access point |
US9119028B2 (en) | 2010-04-14 | 2015-08-25 | Qualcomm Incorporated | Method and apparatus for supporting location services via a Home Node B (HNB) |
US10383166B2 (en) | 2010-04-14 | 2019-08-13 | Qualcomm Incorporated | Method and apparatus for supporting location services via a home node B (HNB) |
US8472974B2 (en) | 2010-04-28 | 2013-06-25 | T-Mobile Usa, Inc. | Location continuity service for locating mobile devices using multiple access networks including wireless telecommunication networks |
US9094927B2 (en) | 2010-04-28 | 2015-07-28 | T-Mobile Usa, Inc. | Location continuity service for locating mobile devices using multiple access networks including wireless telecommunication networks |
CN102316444B (en) * | 2010-07-06 | 2016-06-29 | 中兴通讯股份有限公司 | A kind of system and method that subscriber equipment is carried out service quality control |
US8600403B2 (en) | 2010-12-03 | 2013-12-03 | Qualcomm Incorporated | Method and apparatus for configuring and locating a home base station |
US8824678B2 (en) * | 2011-04-05 | 2014-09-02 | Broadcom Corporation | MAC address anonymizer |
US8819499B2 (en) * | 2011-06-09 | 2014-08-26 | At&T Mobility Ii Llc | Sending network reject/error codes from a terminal adaptor to terminal equipment through an at command interface |
US8868101B2 (en) * | 2011-08-26 | 2014-10-21 | Qualcomm Incorporated | Secure user plane location (SUPL) redirection and mobile location protocol (MLP) tunneling to a discovered SLP |
US8949307B2 (en) | 2011-11-15 | 2015-02-03 | Google Inc. | Cloud-to-device messaging for application activation and reporting |
US9215694B2 (en) | 2011-12-22 | 2015-12-15 | Qualcomm Incorporated | Reference signals design for time tracking in LTE-A |
US9622027B2 (en) | 2012-06-15 | 2017-04-11 | Qualcomm Incorporated | Systems and methods for network centric WLAN location of a mobile device |
US9052896B2 (en) * | 2012-07-20 | 2015-06-09 | Facebook, Inc. | Adjusting mobile device state based on user intentions and/or identity |
KR101634916B1 (en) | 2012-11-01 | 2016-06-29 | 인텔 코포레이션 | Network assisted device-to-device discovery for peer-to-peer applications |
US9271135B2 (en) | 2013-03-15 | 2016-02-23 | T-Mobile Usa, Inc. | Local network alert system for mobile devices using an IMS session and Wi-Fi access point |
WO2014210250A1 (en) * | 2013-06-28 | 2014-12-31 | Intel Corporation | Network assisted device-to-device discovery for peer-to-peer applications |
FR3009159B1 (en) * | 2013-07-26 | 2017-06-23 | Inst Mines Telecom | METHOD FOR PROCESSING GEOLOCATION DATA |
US10033723B2 (en) | 2013-12-18 | 2018-07-24 | At&T Intellectual Property I, L.P. | Methods, devices, and computer readable storage devices for authenticating devices having non-SIM based clients |
US10694332B2 (en) * | 2014-06-03 | 2020-06-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Establishing the location of unmanaged network access points |
US10217120B1 (en) | 2015-04-21 | 2019-02-26 | Videomining Corporation | Method and system for in-store shopper behavior analysis with multi-modal sensor fusion |
US9838991B1 (en) | 2016-08-15 | 2017-12-05 | At&T Intellectual Property I, L.P. | Method and apparatus for managing mobile subscriber identification information according to registration requests |
US9924347B1 (en) | 2016-09-14 | 2018-03-20 | At&T Intellectual Property I, L.P. | Method and apparatus for reassigning mobile subscriber identification information |
US9814010B1 (en) | 2016-09-14 | 2017-11-07 | At&T Intellectual Property I, L.P. | Method and apparatus for utilizing mobile subscriber identification information with multiple devices based on registration requests |
US9843922B1 (en) * | 2016-09-14 | 2017-12-12 | At&T Intellectual Property I, L.P. | Method and apparatus for utilizing mobile subscriber identification information with multiple devices based on registration errors |
US9906943B1 (en) | 2016-09-29 | 2018-02-27 | At&T Intellectual Property I, L.P. | Method and apparatus for provisioning mobile subscriber identification information to multiple devices and provisioning network elements |
US9918220B1 (en) | 2016-10-17 | 2018-03-13 | At&T Intellectual Property I, L.P. | Method and apparatus for managing and reusing mobile subscriber identification information to multiple devices |
US10070303B2 (en) | 2016-11-11 | 2018-09-04 | At&T Intellectual Property I, L.P. | Method and apparatus for provisioning of multiple devices with mobile subscriber identification information |
US9913143B1 (en) * | 2016-11-28 | 2018-03-06 | Amazon Technologies, Inc. | Auto-provisioning device |
US10070407B2 (en) | 2016-12-01 | 2018-09-04 | At&T Intellectual Property I, L.P. | Method and apparatus for using active and inactive mobile subscriber identification information in a device to provide services for a limited time period |
US10136305B2 (en) | 2016-12-01 | 2018-11-20 | At&T Intellectual Property I, L.P. | Method and apparatus for using mobile subscriber identification information for multiple device profiles for a device |
US10341842B2 (en) | 2016-12-01 | 2019-07-02 | At&T Intellectual Property I, L.P. | Method and apparatus for using temporary mobile subscriber identification information in a device to provide services for a limited time period |
US10231204B2 (en) | 2016-12-05 | 2019-03-12 | At&T Intellectual Property I, L.P. | Methods, systems, and devices for registering a communication device utilizing a virtual network |
US10897468B1 (en) * | 2018-12-12 | 2021-01-19 | Amazon Technologies, Inc. | Region management for distirbuted services in provider networks |
US11716772B1 (en) | 2021-09-24 | 2023-08-01 | T-Mobile Usa, Inc. | Rapid prototyping of an internet of things device, such as a device for communicating with a wireless cellular network |
Family Cites Families (190)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6301242B1 (en) | 1998-07-24 | 2001-10-09 | Xircom Wireless, Inc. | Communication system with fast control traffic |
US5724660A (en) | 1995-06-07 | 1998-03-03 | At&T Wireless Services, Inc. | Method and apparatus for locating a mobile station by comparing calculated location area with GPS coordinates |
US7714778B2 (en) | 1997-08-20 | 2010-05-11 | Tracbeam Llc | Wireless location gateway and applications therefor |
US6236365B1 (en) | 1996-09-09 | 2001-05-22 | Tracbeam, Llc | Location of a mobile station using a plurality of commercial wireless infrastructures |
US7903029B2 (en) | 1996-09-09 | 2011-03-08 | Tracbeam Llc | Wireless location routing applications and architecture therefor |
US6249252B1 (en) | 1996-09-09 | 2001-06-19 | Tracbeam Llc | Wireless location using multiple location estimators |
US6002679A (en) | 1996-12-31 | 1999-12-14 | Lucent Technologies Inc. | Method for assigning feature sets on virtual private telecommunications networks |
JPH10239416A (en) | 1997-02-28 | 1998-09-11 | Nec Home Electron Ltd | Present position measuring system |
US6671514B1 (en) | 1997-10-16 | 2003-12-30 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for location positioning a mobile station in a CDMA cellular system |
US6161018A (en) | 1998-02-27 | 2000-12-12 | Motorola, Inc. | Method and system for estimating a subscriber's location in a wireless communication system service area |
US6222483B1 (en) | 1998-09-29 | 2001-04-24 | Nokia Mobile Phones Limited | GPS location for mobile phones using the internet |
US6321092B1 (en) | 1998-11-03 | 2001-11-20 | Signal Soft Corporation | Multiple input data management for wireless location-based applications |
US6119012A (en) | 1998-11-13 | 2000-09-12 | Ericsson Inc. | Method and system for dynamically and periodically updating mobile station location data in a telecommunications network |
US6947398B1 (en) | 1998-11-13 | 2005-09-20 | Lucent Technologies Inc. | Addressing scheme for a multimedia mobile network |
US20040198386A1 (en) | 2002-01-16 | 2004-10-07 | Dupray Dennis J. | Applications for a wireless location gateway |
US6184829B1 (en) | 1999-01-08 | 2001-02-06 | Trueposition, Inc. | Calibration for wireless location system |
US6782264B2 (en) * | 1999-01-08 | 2004-08-24 | Trueposition, Inc. | Monitoring of call information in a wireless location system |
US6104712A (en) | 1999-02-22 | 2000-08-15 | Robert; Bruno G. | Wireless communication network including plural migratory access nodes |
US6463288B1 (en) | 1999-03-18 | 2002-10-08 | Ericsson Inc. | System and method for monitoring positioning requests for mobile subscribers |
CN100387030C (en) | 1999-05-28 | 2008-05-07 | 基础能源公司 | Wireless transceiver network employing node-to-node data messaging |
AU4548400A (en) | 1999-06-08 | 2000-12-28 | Sony International (Europe) Gmbh | Geolocation of mobile devices |
US6603976B1 (en) | 1999-08-03 | 2003-08-05 | Ericsson, Inc. | Architecture for TOA positioning with LMU control functionality in BSC |
FI109863B (en) | 2000-01-26 | 2002-10-15 | Nokia Corp | Locating a subscriber terminal in a packet switched radio system |
US6603977B1 (en) | 2000-02-04 | 2003-08-05 | Sbc Properties, Lp | Location information system for a wireless communication device and method therefor |
US6252545B1 (en) | 2000-02-04 | 2001-06-26 | Lucent Technologies Inc. | Enhancement of signal-detection capability of GPS systems |
US6603978B1 (en) | 2000-03-24 | 2003-08-05 | Ericsson Inc. | Accurate GPS time estimate based on information from a wireless communications system |
US6684250B2 (en) | 2000-04-03 | 2004-01-27 | Quova, Inc. | Method and apparatus for estimating a geographic location of a networked entity |
GB0015365D0 (en) | 2000-06-22 | 2000-08-16 | Nokia Networks Oy | Location services interworking with intelligent network |
US7487112B2 (en) | 2000-06-29 | 2009-02-03 | Barnes Jr Melvin L | System, method, and computer program product for providing location based services and mobile e-commerce |
FI108372B (en) | 2000-06-30 | 2002-01-15 | Nokia Corp | Method and apparatus for position measurement |
ES2251339T3 (en) | 2000-08-09 | 2006-05-01 | Telefonaktiebolaget Lm Ericsson (Publ) | METHOD OF ESTABLISHMENT OF OPERATING PARAMETERS OF A MOBILE STATION DEPENDING ON THE POSITION, CORRESPONDING STATION AND ISSUER TO ISSUE POSITION INFORMATION. |
US6711417B1 (en) * | 2000-08-16 | 2004-03-23 | Sprint Spectrum, L.P. | Interface using an ISH and a service manager |
US8996698B1 (en) * | 2000-11-03 | 2015-03-31 | Truphone Limited | Cooperative network for mobile internet access |
JP3964126B2 (en) | 2000-11-24 | 2007-08-22 | 三菱電機株式会社 | Wireless terminal and home agent |
US20030009385A1 (en) | 2000-12-26 | 2003-01-09 | Tucciarone Joel D. | Electronic messaging system and method thereof |
US20040122730A1 (en) | 2001-01-02 | 2004-06-24 | Tucciarone Joel D. | Electronic messaging system and method thereof |
US6801778B2 (en) | 2001-01-31 | 2004-10-05 | Ericsson Inc. | Efficient location of mobile radiotelephones using cellular and GPS information |
US7715849B2 (en) | 2001-02-28 | 2010-05-11 | Nokia Corporation | User positioning |
US6968195B2 (en) | 2001-03-01 | 2005-11-22 | Openwave Systems Inc. | Enhanced PDE selection |
US7912185B2 (en) | 2001-03-09 | 2011-03-22 | Celphinder Technologies, Inc. | System and method for providing the precise location of a cell phone making an emergency call |
US20040102196A1 (en) | 2001-04-06 | 2004-05-27 | Mikko Weckstrom | Location method and system |
US6665611B1 (en) | 2001-06-19 | 2003-12-16 | Cisco Technology, Inc. | System for discovering and maintaining geographic location information in a computer network to enable emergency services |
US20030032404A1 (en) | 2001-08-07 | 2003-02-13 | Wager Garrick T. | Service zone management system & method |
GB0121030D0 (en) | 2001-08-30 | 2001-10-24 | Nokia Corp | Location services |
US7336668B2 (en) * | 2001-09-24 | 2008-02-26 | Christopher Lyle Adams | Communication management system with line status notification for key switch emulation |
US7304985B2 (en) * | 2001-09-24 | 2007-12-04 | Marvin L Sojka | Multimedia communication management system with line status notification for key switch emulation |
US20040076157A1 (en) * | 2001-09-24 | 2004-04-22 | Teleware, Inc. | Multimedia communication management system with line status notification for key switch emulation |
US20030058844A1 (en) * | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Communication management system with lines status notification and single button dialing for key switch emulation |
NO20020290D0 (en) | 2002-01-18 | 2002-01-18 | Ericsson Telefon Ab L M | Procedure for roaming on mobile networks |
US7606938B2 (en) | 2002-03-01 | 2009-10-20 | Enterasys Networks, Inc. | Verified device locations in a data network |
US8923191B2 (en) | 2002-04-17 | 2014-12-30 | Northrop Grumman Systems Corporation | Internet protocol collaborative mobility |
US7623871B2 (en) | 2002-04-24 | 2009-11-24 | Qualcomm Incorporated | Position determination for a wireless terminal in a hybrid position determination system |
US7246178B2 (en) * | 2002-05-07 | 2007-07-17 | Nortel Networks Limited | Methods and systems for changing a topology of a network |
EP1506688B1 (en) | 2002-05-07 | 2007-05-02 | Koninklijke Philips Electronics N.V. | Wireless communications arrangements with location based services |
JP4864321B2 (en) | 2002-06-14 | 2012-02-01 | エヌエックスピー ビー ヴィ | Method for processing location data within a mobile device, and mobile device having improved location data processing capabilities |
US7158500B2 (en) * | 2002-06-28 | 2007-01-02 | Siemens Communications, Inc. | Method and apparatus for mobile location center to mobile location center communication in the packet-switched domain |
EP1416745A1 (en) | 2002-10-31 | 2004-05-06 | Siemens Aktiengesellschaft | Localisation method |
US7660588B2 (en) | 2002-10-17 | 2010-02-09 | Qualcomm Incorporated | Method and apparatus for improving radio location accuracy with measurements |
US7640008B2 (en) * | 2002-10-18 | 2009-12-29 | Kineto Wireless, Inc. | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
US7369859B2 (en) * | 2003-10-17 | 2008-05-06 | Kineto Wireless, Inc. | Method and system for determining the location of an unlicensed mobile access subscriber |
US7349698B2 (en) | 2002-10-18 | 2008-03-25 | Kineto Wireless, Inc. | Registration messaging in an unlicensed mobile access telecommunications system |
US7526800B2 (en) | 2003-02-28 | 2009-04-28 | Novell, Inc. | Administration of protection of data accessible by a mobile device |
KR100493107B1 (en) | 2003-01-06 | 2005-06-02 | 삼성전자주식회사 | Zone base service supporting method to mobile communication for high rate packet data service |
CN1276620C (en) | 2003-01-10 | 2006-09-20 | 华为技术有限公司 | Method for providing location based service for WLAN user |
US7103333B2 (en) | 2003-01-16 | 2006-09-05 | Research In Motion Limited | System and method of exchanging identification information for mobile stations |
US20040203915A1 (en) | 2003-01-22 | 2004-10-14 | Van Diggelen Frank | Method and apparatus for locating a mobile receiver having a position cache |
JP2006524443A (en) | 2003-02-04 | 2006-10-26 | エスケーテレコム カンパニー リミテッド | Method and system for evaluating performance of position determination of mobile communication terminal using wireless communication network and A-GPS method |
WO2004075579A2 (en) * | 2003-02-14 | 2004-09-02 | Roamware, Inc. | Signaling and packet relay method and system including general packet radio service (“gprs”) |
US7734760B2 (en) | 2003-02-14 | 2010-06-08 | Intel Corporation | Estimating the location of a network client using a media access control address |
WO2004075598A1 (en) * | 2003-02-18 | 2004-09-02 | Roamware, Inc. | Providing multiple msisdn numbers in a mobile device with a single imsi |
US20040166856A1 (en) | 2003-02-21 | 2004-08-26 | Jarko Niemenmaa | Location system |
US7133498B2 (en) | 2003-04-18 | 2006-11-07 | At&T Corp. | Method for confirming end point location of calls |
US20040224702A1 (en) | 2003-05-09 | 2004-11-11 | Nokia Corporation | System and method for access control in the delivery of location information |
US20040240430A1 (en) * | 2003-05-27 | 2004-12-02 | Innomedia Pte Ltd. | IP gateway for hybrid circuit switched and IP based mobile wireless telephone system |
ES2237991B1 (en) | 2003-06-13 | 2006-10-16 | Universitat Politecnica De Catalunya | PROCEDURE FOR MANAGING PETITIONS IN A LOCATION SYSTEM THAT USES A NETWORK OF CELLULAR COMMUNICATIONS FOR PROVISION. |
US8971913B2 (en) | 2003-06-27 | 2015-03-03 | Qualcomm Incorporated | Method and apparatus for wireless network hybrid positioning |
US20050066044A1 (en) | 2003-06-30 | 2005-03-24 | Hemant Chaskar | IP-based location service within code division multiple access network |
US20050059415A1 (en) | 2003-09-16 | 2005-03-17 | Siemens Information And Communication Mobile, Llc | Wireless network capable of allowing coincident mobile terminating location request and mobile originating transactions |
US7313143B1 (en) | 2003-09-26 | 2007-12-25 | Itt Manufacturing Enterprises, Inc. | Method for diversity site group operations in air/ground communications |
KR100557080B1 (en) | 2003-09-29 | 2006-03-03 | 삼성전자주식회사 | Apparatus and method for locating mobile terminals |
EP1673953A2 (en) * | 2003-10-01 | 2006-06-28 | LAIRD, Mark, D. | Wireless virtual campus escort system |
US7333774B2 (en) | 2003-10-07 | 2008-02-19 | The Board Of Trustees Of The Leland Stanford Junior University | Method of optimizing wireless communication links using stored channel characteristics of different locations |
US7436789B2 (en) | 2003-10-09 | 2008-10-14 | Sarnoff Corporation | Ad Hoc wireless node and network |
US7050773B2 (en) | 2003-10-10 | 2006-05-23 | Motorola, Inc. | Wireless broadcast service quality indicator and method |
US7283822B2 (en) * | 2003-10-17 | 2007-10-16 | Kineto Wireless, Inc. | Service access control interface for an unlicensed wireless communication system |
US20050130673A1 (en) * | 2003-11-14 | 2005-06-16 | Magesh Annamalai | Systems and methods for determining the position of a mobile unit |
US20050105496A1 (en) | 2003-11-19 | 2005-05-19 | Cognio, Inc. | System and Method for Integrated Wireless WAN/LAN Location of a Device |
WO2005051025A1 (en) * | 2003-11-20 | 2005-06-02 | Research In Motion Limited | Seamless call switching in a dual mode environment |
US7228141B2 (en) | 2003-12-23 | 2007-06-05 | Cisco Technology, Inc. | Providing location-specific services to a mobile node |
US8046000B2 (en) | 2003-12-24 | 2011-10-25 | Nortel Networks Limited | Providing location-based information in local wireless zones |
FI20040037A0 (en) | 2004-01-13 | 2004-01-13 | Nokia Corp | Providing position information |
US7707039B2 (en) | 2004-02-15 | 2010-04-27 | Exbiblio B.V. | Automatic modification of web pages |
US7812860B2 (en) | 2004-04-01 | 2010-10-12 | Exbiblio B.V. | Handheld device for capturing text from both a document printed on paper and a document displayed on a dynamic display device |
US8099104B2 (en) * | 2004-02-26 | 2012-01-17 | Telcordia Licensing Company Llc | Location based services for integrated cellular and LAN networks |
US7177399B2 (en) | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
US7272500B1 (en) | 2004-03-25 | 2007-09-18 | Avaya Technology Corp. | Global positioning system hardware key for software licenses |
US9137771B2 (en) | 2004-04-02 | 2015-09-15 | Qualcomm Incorporated | Methods and apparatuses for beacon assisted position determination systems |
US8145182B2 (en) | 2004-05-07 | 2012-03-27 | Interdigital Technology Corporation | Supporting emergency calls on a wireless local area network |
US7446655B2 (en) | 2004-06-18 | 2008-11-04 | Qualcomm Incorporated | Tracking lost and stolen mobile devices using location technologies and equipment identifiers |
US7319878B2 (en) | 2004-06-18 | 2008-01-15 | Qualcomm Incorporated | Method and apparatus for determining location of a base station using a plurality of mobile stations in a wireless mobile network |
FI20040978A0 (en) * | 2004-07-13 | 2004-07-13 | Nokia Corp | System, Method, Web Objects, and Computer Programs to Manage Dynamic Host Configuration Policy Frame Configuration |
US7184746B2 (en) | 2004-07-13 | 2007-02-27 | Lucent Technologies Inc. | Method and apparatus for providing network support for a wireless emergency call |
ATE552708T1 (en) | 2004-07-16 | 2012-04-15 | Bridgeport Networks | PRESENCE DETECTION AND HANDOVER FOR CELLULAR AND INTERNET PROTOCOL TELEPHONE |
US20060014548A1 (en) | 2004-07-16 | 2006-01-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Determination of mobile terminal position |
US8032156B2 (en) | 2004-09-07 | 2011-10-04 | Qualcomm Incorporated | Procedure to increase position location availabilty |
US7610011B2 (en) | 2004-09-19 | 2009-10-27 | Adam Albrett | Providing alternative programming on a radio in response to user input |
AU2005292243B2 (en) | 2004-10-01 | 2011-03-10 | Telecommunication Systems, Inc. | Off board navigation solution |
US7277712B2 (en) | 2004-11-17 | 2007-10-02 | At&T Mobility Ii, Llc | Method and system for providing location information for emergency services |
US7433673B1 (en) | 2004-12-17 | 2008-10-07 | Sprint Spectrum L.P. | Method and system for providing location information for a wireless local area network (WLAN) |
US7280826B2 (en) | 2005-02-01 | 2007-10-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, system and apparatus for providing security in an unlicensed mobile access network or a generic access network |
US7974639B2 (en) * | 2005-02-04 | 2011-07-05 | Qualcomm Incorporated | Method and apparatus for performing position determination with a short circuit call flow |
US7593728B2 (en) | 2005-02-07 | 2009-09-22 | Samsung Electronics Co., Ltd. | Private wireless communication system and method for controlling mobile station using the same |
GB0503927D0 (en) * | 2005-02-25 | 2005-04-06 | Nokia Corp | Location services in a communication system |
EP1864530B1 (en) | 2005-03-29 | 2010-03-03 | Swisscom AG | Method for performing location-specific services, broadcasting unit and mobile receiving device |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US7613155B2 (en) * | 2005-04-30 | 2009-11-03 | Lg Electronics Inc. | Terminal, system and method for providing location information service by interworking between WLAN and mobile communication network |
JP2008546358A (en) | 2005-06-09 | 2008-12-18 | インターオーピー・テクノロジーズ・エルエルシー | Karaoke ringback tone and system and method for karaoke ringtone |
US8694008B2 (en) | 2005-06-16 | 2014-04-08 | At&T Mobility Ii Llc | Multi-mode handset services |
US7336962B2 (en) | 2005-06-17 | 2008-02-26 | Nextel Communications Inc. | System and method for position equipment dusting in search and rescue operations |
US9154907B2 (en) * | 2005-06-21 | 2015-10-06 | Qualcomm Incorporated | Efficient periodic location reporting in a radio access network |
US8589532B2 (en) * | 2005-06-24 | 2013-11-19 | Qualcomm Incorporated | Apparatus and method for determining WLAN access point position |
JP2009500896A (en) * | 2005-06-30 | 2009-01-08 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Method and apparatus for multi-mode conversation over a wireless network |
EP2456259B1 (en) | 2005-07-25 | 2014-04-16 | Telefonaktiebolaget L M Ericsson (publ) | Means and method for improving the handover characteristics of radio access networks |
US10178522B2 (en) * | 2005-08-02 | 2019-01-08 | Qualcomm Incorporated | VoIP emergency call support |
WO2007017735A1 (en) * | 2005-08-05 | 2007-02-15 | Nokia Corporation | Location services for and about mobile nodes |
GB0517064D0 (en) | 2005-08-19 | 2005-09-28 | Nokia Corp | Mobile access network server |
US7245900B1 (en) | 2005-08-24 | 2007-07-17 | Sprint Spectrum L.P. | Method and system for using basic service set identifiers (BSSIDs) for emergency services routing |
US7904096B2 (en) | 2005-09-06 | 2011-03-08 | O2Micro International Limited | GPS application using network assistance |
US20070061242A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Implicit searching for mobile content |
US20070073722A1 (en) | 2005-09-14 | 2007-03-29 | Jorey Ramer | Calculation and presentation of mobile content expected value |
US20070073718A1 (en) | 2005-09-14 | 2007-03-29 | Jorey Ramer | Mobile search service instant activation |
US20070060114A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Predictive text completion for a mobile communication facility |
US9471925B2 (en) | 2005-09-14 | 2016-10-18 | Millennial Media Llc | Increasing mobile interactivity |
US8229914B2 (en) | 2005-09-14 | 2012-07-24 | Jumptap, Inc. | Mobile content spidering and compatibility determination |
US20070061245A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Location based presentation of mobile content |
US20070061317A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Mobile search substring query completion |
US20070061303A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Mobile search result clustering |
US20070073719A1 (en) | 2005-09-14 | 2007-03-29 | Jorey Ramer | Physical navigation of a mobile search application |
US20070288427A1 (en) | 2005-09-14 | 2007-12-13 | Jorey Ramer | Mobile pay-per-call campaign creation |
US20070239724A1 (en) | 2005-09-14 | 2007-10-11 | Jorey Ramer | Mobile search services related to direct identifiers |
US9076175B2 (en) | 2005-09-14 | 2015-07-07 | Millennial Media, Inc. | Mobile comparison shopping |
US7676394B2 (en) | 2005-09-14 | 2010-03-09 | Jumptap, Inc. | Dynamic bidding and expected value |
US20070061246A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Mobile campaign creation |
US20070061198A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Mobile pay-per-call campaign creation |
US20070192318A1 (en) | 2005-09-14 | 2007-08-16 | Jorey Ramer | Creation of a mobile search suggestion dictionary |
US20070073717A1 (en) | 2005-09-14 | 2007-03-29 | Jorey Ramer | Mobile comparison shopping |
US20080009268A1 (en) | 2005-09-14 | 2008-01-10 | Jorey Ramer | Authorized mobile content search results |
US20070198485A1 (en) | 2005-09-14 | 2007-08-23 | Jorey Ramer | Mobile search service discovery |
US20070061247A1 (en) | 2005-09-14 | 2007-03-15 | Jorey Ramer | Expected value and prioritization of mobile content |
US8145183B2 (en) | 2005-09-23 | 2012-03-27 | University Of South Florida | On-demand emergency notification system using GPS-equipped devices |
EP1938488B1 (en) | 2005-10-21 | 2015-09-09 | T-Mobile, USA, Inc | System and method for determining device location in an ip-based wireless telecommunications network |
US8165606B2 (en) | 2005-12-22 | 2012-04-24 | Kyocera Corporation | Apparatus, system, and method for location information management in a portable communication device |
US7620404B2 (en) * | 2005-12-22 | 2009-11-17 | Pascal Chesnais | Methods and apparatus for organizing and presenting contact information in a mobile communication system |
US20070155489A1 (en) | 2005-12-30 | 2007-07-05 | Frederic Beckley | Device and network enabled geo-fencing for area sensitive gaming enablement |
US20090005061A1 (en) | 2005-12-30 | 2009-01-01 | Trueposition, Inc. | Location quality of service indicator |
US7466986B2 (en) | 2006-01-19 | 2008-12-16 | International Business Machines Corporation | On-device mapping of WIFI hotspots via direct connection of WIFI-enabled and GPS-enabled mobile devices |
US8059801B2 (en) | 2006-01-20 | 2011-11-15 | Preferred Voice, Inc. | Telephone communications system, a method of delivering content to a calling party and a method of distributing information to a calling party |
US20070178913A1 (en) | 2006-01-27 | 2007-08-02 | Nokia Corporation | Method, apparatus and computer program product for self-learning location method selection logic |
US7688261B2 (en) | 2006-03-15 | 2010-03-30 | The Boeing Company | Global position system (GPS) user receiver and geometric surface processing for all-in-view coherent GPS signal PRN codes acquisition and navigation solution |
US8571043B2 (en) * | 2006-03-16 | 2013-10-29 | Sonus Networks, Inc. | Using a single point code to represent multiple switching devices |
US7747568B2 (en) * | 2006-04-07 | 2010-06-29 | Microsoft Corporation | Integrated user interface |
EP2014111B1 (en) | 2006-04-13 | 2017-09-06 | T-Mobile USA, Inc. | Mobile computing device geographic location determination |
WO2008006077A2 (en) | 2006-07-07 | 2008-01-10 | Skyhook Wireless Inc. | Systems and methods of gathering information from wlan- enabled access points to estimate position of a wlan positioning device |
US8849297B2 (en) | 2006-07-14 | 2014-09-30 | Qualcomm Incorporated | Call establishment and maintenance in a wireless network |
US8271004B2 (en) | 2006-08-08 | 2012-09-18 | Mikael Vinding | User generated dynamic mobile service |
US20080045236A1 (en) | 2006-08-18 | 2008-02-21 | Georges Nahon | Methods and apparatus for gathering and delivering contextual messages in a mobile communication system |
US20080076429A1 (en) | 2006-09-08 | 2008-03-27 | Futurewei Technologies, Inc. | System for control, management, and transmission for soft handoff in an ofdma-based communication system |
US8204502B2 (en) | 2006-09-22 | 2012-06-19 | Kineto Wireless, Inc. | Method and apparatus for user equipment registration |
US8588813B2 (en) | 2006-10-03 | 2013-11-19 | Alcatel Lucent | Apparatus, and associated method, for estimating the location of a GAN-capable mobile station |
US8953567B2 (en) | 2006-10-20 | 2015-02-10 | T—Mobile USA, Inc. | System and method for utilizing IP-based wireless telecommunications client location data |
CA2620249C (en) | 2006-10-20 | 2016-04-19 | T-Mobile Usa, Inc. | Two stage mobile device geographic location determination |
EP2084917B1 (en) | 2006-10-20 | 2019-05-01 | T-Mobile USA, Inc. | System and method for determining a subscriber's zone information |
US20080254810A1 (en) | 2006-12-05 | 2008-10-16 | Kenny Fok | Methods and Apparatus for Location Determination In A Wireless Communication Device |
US8731610B2 (en) | 2006-12-13 | 2014-05-20 | Samsung Electronics Co., Ltd. | Method for adaptive user interface in mobile devices |
WO2009104721A1 (en) | 2008-02-21 | 2009-08-27 | 日本電気株式会社 | Method and system of efficiently using mobile terminal context |
WO2009135191A1 (en) | 2008-05-02 | 2009-11-05 | Xtify, Inc. | Location-based services platform |
US8620255B2 (en) | 2008-06-16 | 2013-12-31 | Qualcomm Incorporated | Method and apparatus for supporting emergency calls and location for femto access points |
KR20110063819A (en) | 2008-09-04 | 2011-06-14 | 파워웨이브 코그니션, 인크. | Applications for a mobiel broadband, routable internet |
US8195121B2 (en) | 2008-09-15 | 2012-06-05 | T-Mobile Usa, Inc. | Method and system for establishing messaging communication with a service provider, such as a PSAP (public safety answering point) |
WO2010052496A1 (en) | 2008-11-04 | 2010-05-14 | The University Court Of The University Of Edinburgh | Improvements to assisted positioning systems |
US8538815B2 (en) | 2009-02-17 | 2013-09-17 | Lookout, Inc. | System and method for mobile device replacement |
US8320344B2 (en) | 2009-02-27 | 2012-11-27 | T-Mobile Usa, Inc. | System and method for provisioning telecommunications services between an access point and a telecommunications network and providing a missing information notification |
US8213957B2 (en) | 2009-04-22 | 2012-07-03 | Trueposition, Inc. | Network autonomous wireless location system |
US8718592B2 (en) | 2009-05-15 | 2014-05-06 | T-Mobile Usa, Inc. | Mobile device location determination using micronetworks |
US8311557B2 (en) | 2009-05-15 | 2012-11-13 | T-Mobile Usa, Inc. | Facility for selecting a mobile device location determination technique |
US8838132B2 (en) | 2009-08-12 | 2014-09-16 | Qualcomm Incorporated | Enhanced positioning assistance data for reduced signaling |
US8611326B2 (en) | 2009-09-03 | 2013-12-17 | Apple Inc. | Location histories for location aware devices |
US8509731B2 (en) | 2009-11-06 | 2013-08-13 | Research In Motion Limited | Location determination for mobile devices in emergency situations |
US8755816B2 (en) | 2009-12-30 | 2014-06-17 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for position determination in a cellular communications system |
US20140045596A1 (en) | 2012-08-07 | 2014-02-13 | Lawrence Cameron Vaughan | Methods and systems for determining the location of online gaming clients |
-
2007
- 2007-10-22 US US12/446,454 patent/US8953567B2/en active Active
- 2007-10-22 CA CA002620617A patent/CA2620617A1/en not_active Abandoned
- 2007-10-22 WO PCT/US2007/082136 patent/WO2008051929A2/en active Application Filing
-
2014
- 2014-11-21 US US14/550,901 patent/US9820089B2/en active Active
-
2017
- 2017-11-13 US US15/810,568 patent/US10869162B2/en active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2544468B1 (en) * | 2010-08-16 | 2020-11-11 | ZTE Corporation | Region access platform, mobile positioning method and system |
Also Published As
Publication number | Publication date |
---|---|
US20150181375A1 (en) | 2015-06-25 |
US10869162B2 (en) | 2020-12-15 |
US20110200022A1 (en) | 2011-08-18 |
US8953567B2 (en) | 2015-02-10 |
US20180070204A1 (en) | 2018-03-08 |
WO2008051929A3 (en) | 2008-08-14 |
US9820089B2 (en) | 2017-11-14 |
WO2008051929A2 (en) | 2008-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10869162B2 (en) | System and method for utilizing IP-based wireless telecommunications client location data | |
US8693454B2 (en) | Mobile computing device geographic location determination | |
CA2619642C (en) | System and method for determining device location in an ip-based wireless telecommunications network | |
US10419875B2 (en) | System and method for determining a subscriber's zone information | |
CA2620249C (en) | Two stage mobile device geographic location determination | |
US8290510B2 (en) | System and method for SUPL held interworking | |
US8301160B2 (en) | System and method for SUPL roaming using a held client | |
US9479897B2 (en) | SUPL-WiFi access point controller location based services for WiFi enabled mobile devices | |
WO2011120404A1 (en) | Location method, device and system for secure user plane location enabled terminal | |
WO2010102242A2 (en) | System and method for indicating a subscriber's zone within converged telecommunications networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |