EP1894430B1 - Procede et appareil pour la fourniture de services de localisation avec des flux de messages reduits - Google Patents

Procede et appareil pour la fourniture de services de localisation avec des flux de messages reduits Download PDF

Info

Publication number
EP1894430B1
EP1894430B1 EP06773799.9A EP06773799A EP1894430B1 EP 1894430 B1 EP1894430 B1 EP 1894430B1 EP 06773799 A EP06773799 A EP 06773799A EP 1894430 B1 EP1894430 B1 EP 1894430B1
Authority
EP
European Patent Office
Prior art keywords
location
request
estimate
serving network
center
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.)
Active
Application number
EP06773799.9A
Other languages
German (de)
English (en)
Other versions
EP1894430A1 (fr
Inventor
Stephen W. Edge
Kirk Allan Burroughs
Sven Fischer
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP1894430A1 publication Critical patent/EP1894430A1/fr
Application granted granted Critical
Publication of EP1894430B1 publication Critical patent/EP1894430B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • 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/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • 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
    • 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/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present invention relates generally to communication, and more specifically to techniques for providing location services.
  • a wireless user may utilize the wireless device to browse through a website and may click on location sensitive content.
  • the web server may then query the network for the location of the wireless device.
  • the network may initiate location processing with the wireless device in order to ascertain the location of the wireless device.
  • the network would then return a location estimate for the wireless device to the web server, which may use this location estimate to provide appropriate content to the wireless user.
  • location and “position” are synonymous and are used interchangeably.
  • a message flow (which may also be called a call flow or a procedure) is typically executed in order to obtain a location estimate for the wireless device and to send this location estimate to a client entity (e.g., the web server).
  • Various messages are typically exchanged between one or more network entities, the wireless device, and the client entity for the message flow. These messages ensure that each entity is provided with pertinent information, or can obtain this information from another entity, in order to carry out positioning for the wireless device and/or to deliver the location estimate to the client entity.
  • these messages add to the traffic among the various network entities. The additional traffic may be much greater for periodic location reporting, which periodically provides a location estimate for the wireless device to the client entity.
  • the messages may also extend the response time for sending the location estimate to the client entity, possibly by an unacceptable amount.
  • 3GPP TS 23.271 (v6.11.0), is a technical standard published by the 3rd Generation Partnership Project (3GPP). This standard defines the LoCation Services (LCS) feature in Universal Mobile Telecommunications System (UMTS) and Global System for Mobile communications (GSM), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
  • LCS LoCation Services
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile communications
  • a method of providing location services in accordance with claim 1 an apparatus in accordance with claim 2 and a computer readable medium according to claim 38.
  • LCS location services
  • MT-LR mobile terminated location request
  • MO-LR mobile originated location request
  • a wireless device (which is also called a user equipment (UE)) sends to a visited/serving network a request for periodic reporting of the UE location to a client entity (e.g., an LCS client) and periodic location information.
  • the UE may also send a request to use GMLC short circuit and/or a request to use MO-LR short circuit.
  • GMLC short circuit refers to the exchange of messages directly between a requesting gateway mobile location center (R-GMLC) and the visited network, thereby bypassing a visited GMLC (V-GMLC) associated with the visited network and a home GMLC (H-GMLC) associated with a home network for the UE.
  • MO-LR short circuit refers to the bypass of location processing between the visited network and the HE to obtain a location estimate for the UE.
  • each UE request may be accepted or rejected by various network entities.
  • the UE may send.its location estimate to the visited network, e.g., if this location estimate is available at the UE and if MO-LR short circuit is allowed.
  • the UE may also send an address of the R-GMLC to the visited network, e.g., if GMLC short circuit is allowed.
  • the UE may perform location processing with the visited network if (1) a location estimate was not sent by the UE or (2) a location estimate was sent by the UE but the visited network decides not to use this location estimate.
  • the network may bypass the location processing if a location estimate is sent by the UE and is selected for use.
  • the visited network may send the location estimate for the UE directly to the R-GMLC and bypass the V-GMLC and H-GMLC, e.g., using the R-GMLC address provided by the UE.
  • the GMLC short circuit and MO-LR short circuit save system resources and shorten the response time to provide the location estimate to the LCS client.
  • MO-LR and MT-LR message flows for one-shot location reporting and periodic location reporting are described below.
  • Various aspects and embodiments of the invention are also described in further detail below.
  • FIG. 1 shows a visited network, a home network, and a requesting network.
  • FIG. 2 shows a message flow for MT-LR periodic location reporting.
  • FIG. 3 shows a message flow for MO-LR periodic location reporting.
  • FIG. 4 shows a message flow for one-shot MO-LR.
  • FIG. 5 shows a message flow for one-shot MO-LR with GLMC short circuit.
  • FIG. 6 shows a message flow for one-shot MO-LR with GLMC short circuit and MO-LR short circuit.
  • FIG. 7 shows a message flow for one-shot MT-LR.
  • FIG. 8 shows a message flow for one-shot MT-LR with GLMC short circuit.
  • FIG. 9 shows a message flow for one-shot MT-LR with GLMC short circuit and MO-LR short circuit.
  • FIG. 10 shows another network deployment.
  • FIG. 11 shows a block diagram of various network entities in FIG. 1 .
  • the location reporting techniques described herein may be used for various wireless networks such as a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a network supporting a combination of the aforementioned technologies, a network with wide area network (WAN) coverage as well as wireless local area network (WLAN) coverage, and so on.
  • CDMA network may implement one or more CDMA radio access technologies (RATs) such as Wideband CDMA (W-CDMA), cdma2000, and so on.
  • cdma2000 covers IS-2000, IS-856, and IS-95 standards.
  • a TDMA network may implement one or more TDMA RATs such as Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), and so on. D-AMPS covers IS-136 and IS-54. These various RATs and standards are known in the art. W-CDMA and GSM are described in documents from a consortium named "3rd Generation Partnership Project” (3GPP). cdma2000 is described in documents from a consortium named “3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. For clarity, the techniques are described below for 3GPP-based networks that utilize one or more RATs and one or more networking protocols promulgated by 3GPP.
  • GSM Global System for Mobile Communications
  • D-AMPS Digital Advanced Mobile Phone System
  • 3GPP2 3rd Generation Partnership Project 2
  • a 3GPP-based network may be (1) a Universal Mobile Telecommunication System (UMTS) network that utilizes W-CDMA as the RAT for over-the-air communication and Mobile Application Part (MAP) as the networking protocol for core network functionality or (2) a GSM network that utilizes GSM for over-the-air communication and MAP for core network functionality.
  • UMTS Universal Mobile Telecommunication System
  • MAP Mobile Application Part
  • FIG. 1 shows a 3GPP-based deployment 100 that includes a visited/serving network 102, a home network 104, and a requesting network 106.
  • Visited network 102 is a network that is currently serving a wireless device 120, which is called UE 120 (3GPP terminology) in the following description.
  • Home network 104 is a network with which UE 120 has a subscription.
  • Requesting network 106 is a network via which an LCS client 170 may originate a request for the location of UE 120.
  • Home network 104 may be the same as or different from visited network 102 and may be the same as or different from requesting network 106.
  • Requesting network 106 may be the same as or different from visited network 102.
  • Wireless device 120 may be roaming and may communicate with different visited networks.
  • Each network may be referred to as a public land mobile network (PLMN).
  • PLMN public land mobile network
  • visited network 102 includes a second generation (2G) GSM EDGE Radio Access Network (GERAN) 130a and a third generation (3G) Universal Terrestrial Radio Access Network (UTRAN) 130b.
  • Each Radio Access Network (RAN) 130 provides wireless communication for UEs located throughout the coverage area of the RAN.
  • GERAN 130a communicates with a 2G mobile services switching center (2G-MSC) 140a and/or a 2G serving GPRS support node (2G-SGSN) 140b.
  • UTRAN 130b communicates with a 3G-SGSN 140c and/or a 3G-MSC 140d.
  • Each MSC performs switching functions for circuit-switched calls (e.g., setup, routing, and eventual release of circuit-switched voice and data calls) for UEs within its coverage area.
  • Each MSC may act as a visited MSC (VMSC) and may be an MSC server.
  • VMSC visited MSC
  • Each SGSN performs switching and routing functions for packet-switched calls and packet-switched connections.
  • a gateway mobile location center (GMLC) performs various functions to support location services, interfaces with external LCS clients, and provides services such as subscriber privacy, authorization, authentication, billing, and so on. In a roaming scenario, these functions may be divided between R-GMLC 154, H-MLC 152 and V-GMLC 150.
  • V-GLMC 150 communicates with MSCs 140a and 140d and SGSNs 140b and 140c.
  • a serving mobile location center SMLC
  • the SMLC may communicate with GERAN 130a, UTRAN 130b, 2G-MSC 140a, and so on.
  • the SLMC may in some cases be a physical and/or logical part of the MSC/SGSN or RAN.
  • Home network 104 includes a home GMLC (H-GMLC) 152 and a home location register (HLR)/home subscriber server (HSS) 160.
  • H-GMLC 152 supports location services for home network 104.
  • HLR/HSS 160 stores registration information for UEs (e.g., UE 120) that are subscribers of home network 104.
  • Requesting network 106 includes a requesting GLMC (R-GLMC) 154 that supports location services for requesting network 106.
  • R-GLMC 154 and/or H-GLMC 152 may communicate directly with MSC 140a, SGSN 140b, SGSN 140c, and/or MSC 140d in visited network 102 via appropriate interfaces.
  • An LCS client 170 is a function or an entity that requests location information for LCS targets.
  • An LCS target is a UE whose location is being sought.
  • an LCS client may reside in a network entity or a UE or may be external to both the network and the UE.
  • LCS client 170 communicates with R-GLMC 154.
  • FIG. 1 shows network entities that are pertinent for location services. These network entities are described in 3GPP TS 23.271, entitled “Functional stage 2 description of Location Services (LCS) (Release 6)," in 3GPP TS 25.305, entitled “Stage 2 functional specification of User Equipment (UE) positioning in UTRAN (Release 6),” and in 3GPP TS 43.059, entitled “Functional stage 2 description of Location Services (LCS) in GERAN (Release 6),” all of which are publicly available.
  • 3GPP TS 23.271 entitled “Functional stage 2 description of Location Services (LCS) (Release 6)
  • 3GPP TS 25.305 entitled “Stage 2 functional specification of User Equipment (UE) positioning in UTRAN (Release 6)
  • UE User Equipment
  • GERAN Release 6
  • Networks 102, 104, and 106 in FIG. 1 utilize a control plane to support location services.
  • a control plane (which is also commonly called a signaling plane) is a mechanism for carrying signaling for higher-layer applications and may be implemented with network-specific protocols and signaling messages.
  • a user plane is a mechanism for carrying data for higher-layer applications and employs a user-plane bearer, which is typically implemented with protocols such as User Datagram Protocol (UDP), Transmission Control Protocol (TCP), and Internet Protocol (IP), all of which are well known in the art.
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • the network entities in FIG. 1 may also be referred to by other names in other networks and other location architectures.
  • SUPL Secure User Plane Location
  • a GLMC is called a SUPL location center (SLC)
  • a UE that supports SUPL is called a SUPL enabled terminal (SET)
  • an SMLC is called a SUPL positioning center (SPC).
  • a GLMC may also be called a location center, an LCS server, a location server, a mobile positioning center (MPC), and so on.
  • V-GMLC 150, R-GMLC 154, and H-GMLC 152 may generically be referred to as first, second, and third location centers, respectively, that are associated with different networks.
  • each network may include any collection of network entities that can provide any range of services.
  • UE 120 may be fixed or mobile and may also be called a mobile station, a terminal, a subscriber unit, or some other terminology. UE 120 may also be a cellular phone, a laptop, a personal digital assistant (PDA), a telemetry device, a tracking device, and so on. UE 120 may communicate with one or more base stations in GERAN 130a and/or one or more base stations in UTRAN 130b. UE 120 may also receive signals from one or more satellites 190, which may be part of the Global Positioning System (GPS), the European GALILEO system, or the Russian Glonass system. UE 120 may measure signals from base stations in GERAN 130a and/or UTRAN 130b and/or signals from satellites 190 and may obtain pseudo-range measurements for these base stations and satellites. These measurements may be used to compute a location estimate for the UE.
  • GPS Global Positioning System
  • UTRAN 130b the European GALILEO system
  • satellites 190 may obtain pseudo-range measurements for these base stations
  • a location estimate for UE 120 may be obtained using a UE-based, UE-assisted, or network-based positioning mode.
  • Positioning refers to a functionality that detects or determines a geographical location of a target UE.
  • the location of the UE is determined by the UE, possibly with assistance data from an SMLC.
  • the location of the UE is determined by the SMLC with assistance (e.g., measurements) from the UE.
  • the location of the UE is determined based on information obtained by or already known to the serving network without any special assistance from the UE.
  • the UE-based and UE-assisted modes may utilize various positioning methods such as GPS, assisted GPS (A-GPS), hybrid, advanced forward link trilateration (A-FLT), enhanced observed time difference (E-OTD), observed time difference of arrival (OTDOA), and so on.
  • the network-based mode may utilize various positioning methods such as uplink time of arrival (U-TOA), uplink time difference of arrival (U-TDOA), cell-ID, enhanced cell-ID, and so on. Multiple positioning methods for one or more positioning modes may also be employed in combination.
  • the GPS and A-GPS methods derive a location estimate for the UE based solely on satellite measurements and have high accuracy.
  • the hybrid method derives a location estimate based on both satellite and base station measurements and has high accuracy and high reliability.
  • the A-FLT, E-OTD, and OTDOA methods derive a location estimate based on measurements of base station timing made by the UE and have more intermediate accuracy.
  • the U-TOA and U-TDOA methods derive a location estimate based on measurements of UE timing made by the serving network and have more intermediate accuracy.
  • the cell-ID and enhanced cell-ID methods derive a location estimate based on a cellular network and have coarser accuracy. These various positioning methods are known in the art.
  • the location of UE 120 may be requested by (1) applications running at LCS client 170, which results in mobile terminated location request (MT-LR), and (2) applications (Apps) running at the UE, which results in mobile originated location request (MO-LR).
  • the location of UE 120 may be requested one time, which results in immediate location reporting, or multiple times with a single request, which results in periodic location reporting.
  • Periodic location reporting may be achieved with a periodic MT-LR message flow or a periodic MO-LR message flow.
  • Each location reporting within the periodic location reporting may be achieved with a one-shot MO-LR message flow or a one-shot MT-LR message flow.
  • Periodic location reporting provides a location estimate for the target UE to the LCS client periodically based on periodic location information that indicates when to report the location of UE to the client entity.
  • the periodic location information may be a schedule of reporting events and/or a set of triggering events.
  • the schedule may be given in various formats such as, e.g., a start time, a reporting interval, and one of a stop time, a duration, or a particular number of reports.
  • the triggering events may correspond to, e.g., the UE becoming available, the UE entering or leaving predefined geographic areas, the UE being within the predefined geographic areas, the UE velocity or acceleration exceeding predefined thresholds, the UE location, velocity or acceleration changing by predefined thresholds, and so on.
  • GLMC short circuit and/or MO-LR short circuit may be used for various message flows.
  • GLMC short circuit refers to the exchange of messages directly between R-GMLC 154 and MSC/SGSN 140, thereby bypassing or short circuiting V-GMLC 150 and H-GMLC 152.
  • MO-LR short circuit refers to the bypass of location processing for a one-shot MO-LR message flow or a one-shot MT-LR message flow. The location processing may be short circuited, for example, if a suitable location estimate is provided by the UE and MO-LR short circuit is allowed.
  • GMLC short circuit, MO-LR short circuit, or both types of short circuit may be used to save system resources and to provide a faster response for a location request.
  • FIG. 2 shows a message flow 200 for MT-LR periodic location reporting in which periodic location of target UE 120 is requested by LCS Client 170 external to the wireless networks.
  • LCS client 170 sends to R-GMLC 154 an LCS Service Request message that contains (1) a request for periodic location reporting of UE 120 to LCS client 170 (i.e., a periodic location request) and (2) periodic location information ("periodic loc info") (step 1).
  • R-GMLC 154 verifies the identity of LCS client 170, authenticates the LCS client, and determines whether the LCS client is authorized for the requested location service.
  • R-GMLC 154 determines an identifier of UE 120 and LCS quality of service (QoS) from subscription data for the LCS client, subscription data for the subscriber of UE 120, and/or data supplied by the LCS client. R-GMLC 154 then sends to HLR/HSS 160 a Send Routing Info for LCS message that contains the identifier of UE 120 (step 2). HLR/HSS 160 verifies whether R-GMLC 154 is authorized to request location information for UE 120 and returns to R-GMLC 154 a Send Routing Info for LCS Acknowledgment message that contains the address of H-GMLC 152 (step 3).
  • QoS LCS quality of service
  • R-GMLC 154 If R-GMLC 154 is the H-GMLC, then steps 4, 5, 6 and 14 of message flow 200 are skipped. Otherwise, R-GMLC 154 sends to H-GMLC 152 an LCS Service Request message that contains the periodic location request and other relevant information (step 4).
  • H-GMLC 152 verifies whether R-GMLC 154 is authorized to request location information for UE 120 and, if yes, performs a privacy check based on a privacy profile for the UE subscriber (also step 4). For the privacy check, H-GMLC 152 verifies if LCS client 170 or this type of LCS client is allowed to request periodic location for UE 120 and whether the UE may need to be notified of this request and allowed to accept or reject the request. H-GMLC 152 also assigns a reference ID that is used to associate subsequent location reports with the original periodic location request, if the request is accepted.
  • H-GMLC 152 If H-GMLC 152 does not know the current serving MSC or SGSN of UE 120 and the associated V-GMLC, then H-GMLC 152 sends a Send Routing Info for LCS message to HLR/HSS 160 to request routing information for the UE (step 5). HLR/HSS 160 then returns a Send Routing Info for LCS Acknowledgment message that contains the address of V-GMLC 150 and the address of MSC/SGSN 140 (step 6). Steps 5 and 6 may be skipped if H-GMLC 152 already knows the address of V-GMLC 150. H-GMLC 152 then sends to V-GMLC 150 an LCS Service Request message that contains the periodic location request and other relevant information (step 7).
  • V-GMLC 150 authenticates that the periodic location request from H-GMLC 152 is allowed (also step 7).
  • V-GMLC 150 typically receives the address of MSC/SGSN 140 from H-GMLC 152 but may query HLR/HSS 160 for the MSC/SGSN address if this address is not received from H-GMLC 152.
  • V-GMLC 150 then sends to MSC/SGSN 140 a Provide Subscriber Location message that contains the periodic location request, the UE identifier, the LCS QoS, and/or other relevant information (step 8).
  • the LCS Service Request message sent by R-GMLC 154 in step 4 may each contain (1) the address of R-GMLC 154, if GMLC short circuit is preferred, and (2) an indication as to whether MO-LR short circuit is allowed or preferred.
  • R-GMLC 154, H-GMLC 152, V-GMLC 150, and MSC/SGSN 140 may each accept or reject the use of GMLC short circuit and may each accept or reject the use of MO-LR short circuit.
  • MSC/SGSN 140 may authenticate that the periodic location request is allowed (also step 8). If the periodic location request is allowed, then MSC/SGSN 140 may invoke RAN 130 to perform paging and authentication of UE 120 (step 9). If notification or privacy verification is needed, then UE 120 notifies the wireless user of the periodic location request, queries the user to grant or deny permission, and sends back the privacy verification result indicating whether permission is granted or denied (also step 9). UE 120 may provide its LCS capabilities to RAN 130 and/or MSC/SGSN 140, e.g., whether the UE-based and/or UE-assisted modes are supported by the UE (also step 9).
  • the MSC/SGSN 140 then sends to UE 120 an LCS Periodic Location Invoke message that contains pertinent information for the periodic location request (e.g., the periodic location information, the LCS QoS, the R-GMLC address, the H-GMLC address, the reference ID, an indication to use MO-LR short circuit, and so on) (step 10).
  • the LCS Periodic Location Invoke message may also include (1) a list of PLMNs in which subsequent periodic location reporting is allowed (e.g., MO-LR requests may be originated) and (2) an indication for each PLMN as to whether the PLMN supports periodic location in the RAN. If no list of PLMNs is included, then subsequent MO-LR requests may be restricted to the current serving PLMN.
  • UE 120 then sends to MSC/SGSN 140 an LCS Periodic Location Invoke Acknowledgment message that indicates whether or not the periodic location request is accepted (step 11). If the periodic location request is not accepted but any privacy verification passes, UE 120 would be indicating a willingness to allow periodic location but an inability or unwillingness to directly support it. In that case, MSC/SGSN 140 may still invoke periodic location via RAN 130, if supported. Otherwise, an error response is originated by MSC/SGSN 140 and returned to LCS client 170.
  • MSC/SGSN 140 sends to V-GMLC 150 a Provide Subscriber Location Acknowledgment message that contains relevant information such as whether the periodic location request is accepted, whether GMLC short circuit will be used, and whether MO-LR short circuit will be used (step 12).
  • This message may also convey the list of PLMNs sent to UE 120 in step 10.
  • V-GMLC 150 then sends an LCS Service Response message that contains pertinent information to H-GMLC 152 (step 13).
  • H-GMLC 152 may perform additional privacy check if needed (also step 13) and sends an LCS Service Response message to R-GMLC 154 (step 14).
  • R-GMLC 154 then sends an LCS Service Response message containing relevant information (e.g., whether the periodic location request is accepted) to LCS client (step 15). Periodic location reporting is then performed as indicated by the periodic location information (steps 16a through 16n).
  • FIG. 3 shows a message flow 300 for MO-LR for periodic location reporting in which periodic location of target UE 120 is requested by UE 120 on behalf of LCS Client 170 external to the wireless networks.
  • UE 120 If UE 120 is in an idle mode, then the UE requests a radio connection setup and sends to RAN 130 a Connection Management (CM) Service Request message indicating a request for a call independent supplementary service (step 1).
  • CM Connection Management
  • UE 120 is in a dedicated mode, then the UE sends a CM Service Request on the already established radio connection (also step 1).
  • RAN 130 forwards the CM Service Request message to MSC/SGSN 140 (step 2).
  • MSC/SGSN 140 instigates authentication and ciphering if UE 120 was in the idle mode or returns a Direct Transfer CM Service Accept message if UE 120 was in the dedicated mode (step 3).
  • UE 120 may provide its LCS capabilities to RAN 130 and/or MSC/SGSN 140, e.g., whether the UE-based and/or UE-assisted modes are supported by the UE (also step 3).
  • steps 1 through 3 are for a circuit switched (CS) domain connection setup in which signaling is sent to the MSC. Steps 1 through 3 would be different for a packet switched (PS) domain connection setup.
  • CS circuit switched
  • PS packet switched
  • UE 120 then sends to MSC/SGSN 140 an LCS MO-LR Location Services Invoke message that contains (1) a request for periodic location reporting ofUE 120 to LCS client 170 (i.e., a periodic location request) and (2) pertinent information for the periodic location reporting (step 4).
  • the pertinent information may include any combination of the following:
  • UE 120 may request for permission to use GMLC short circuit and/or MO-LR short circuit for subsequent location reporting events.
  • UE 120 may include (1) a request for permission to use GMLC short circuit and/or (2) a request for permission to use MO-LR short circuit (e.g., if UE 120 supports the UE-based mode) in the LCS MO-LR Location Services Invoke message sent to MSC/SGSN 140 in step 4.
  • any entity among MSC/SGSN 140, V-GMLC 150, H-GMLC 152, R-GMLC 154, and LCS client 170 may accept or reject the UE request for each type of short circuit.
  • MSC/SGSN 140 may request to use GMLC short circuit and/or MO-LR short circuit, e.g., if UE 120 does not request GMLC short circuit and/or MO-LR short circuit or if UE 120 is not permitted to make these requests. Any entity among V-GMLC 150, H-GMLC 152, R-GMLC 154, and LCS client 170 may then accept or reject the MSC/SGSN request for each type of short circuit. In yet another embodiment, MSC/SGSN 140 may indicate a willingness or a capability to support GMLC short circuit and/or MO-LR short circuit without specifically requesting to use these short circuits.
  • Any entity among V-GMLC 150, H-GMLC 152, R-GMLC 154, and LCS client 170 may then accept or reject the willingness or capability to support each type of short circuit.
  • One entity e.g., H-GMLC 152
  • H-GMLC 152 may decide whether to use each type of short circuit if all entities indicate willingness and capability for that short circuit.
  • the use of MO-LR short circuit may be controlled for various reasons such as, e.g., to deal with a lack of trust in either the UE accuracy and reliability or the UE integrity (e.g. spoofing), for billing and subscription issues, and so on.
  • the use of MO-LR short circuit may be allowed if UE 120 is trusted to provide location estimates directly to MSC/SGSN 140 without verification by RAN 130.
  • GLMC short circuit may also be controlled for reasons relating to billing, subscription, privacy, security, and so on.
  • the request to use GMLC short circuit and the request to use MO-LR short circuit may be treated as independent requests.
  • any entity among UE 120, MSC/SGSN 140, V-GMLC 150, H-GMLC 152 and R-GMLC 154 can autonomously decide whether or not to use GLMC short circuit and whether or not to use MO-LR short circuit.
  • MSC/SGSN 140 verifies that UE 120 is authorized for the requested location service based on a subscription profile for the UE (also step 4). If the periodic location request is authorized, then MSC/SGSN 140 sends to V-GMLC 150 a MAP Subscriber Location Report message that contains the periodic location request and the pertinent information (e.g., the periodic location information, the request to use GMLC short circuit, the request to use MO-LR short circuit, and so on) (step 5). V-GMLC 150 then sends an MO-LR Location Information message that contains the periodic location request and the pertinent information to H-GMLC 152 (step 6), which forwards the message to R-GMLC 154 (step 7), which further forwards the periodic location request and the pertinent information to LCS client 170 (step 8).
  • a MAP Subscriber Location Report message that contains the periodic location request and the pertinent information (e.g., the periodic location information, the request to use GMLC short circuit, the request to use MO-LR short circuit, and so on) (step 5).
  • any entity among MSC/SGSN 140, V-GMLC 150, H-GMLC 152, R-GMLC 152, and LCS client 170 can refuse or accept the periodic location request. If this request is accepted (e.g., not refused by any entity), then H-GMLC 152 assigns a reference ID for the periodic location request. In an embodiment, if the periodic location request is accepted, then any entity can reject the request to use GMLC short circuit (if sent) and any entity can reject the request to use MO-LR short circuit (if sent).
  • LCS client 170 sends a response for the UE request(s) to R-GMLC 154 (step 9), which sends its response in an MO-LR Location Information Acknowledgment message to H-GMLC 152 (step 10).
  • H-GMLC 152 sends its response in an MO-LR Location Information Acknowledgment message to V-GMLC 150 (step 11), which sends its response in a MAP Subscriber Location Report Acknowledgment message to MSC/SGSN 140 (step 12).
  • the response sent by each entity incorporates the response received from the preceding entity (if any) and indicates acceptance or rejection of the periodic location request. If the periodic location request is accepted, then the response sent by each entity further indicates acceptance or rejection of the GMLC short circuit request (if sent) and acceptance or rejection of the MO-LR short circuit request (if sent).
  • MSC/SGSN 140 may receive any combination of the following information:
  • the MSC/SGSN 140 sends to UE 120 an LCS MO-LR Return Result message that contains the information received from V-GMLC 150 (step 13).
  • the LCS MO-LR Return Result message may further include (1) a list of PLMNs in which periodic location reporting is allowed and (2) an indication for each PLMN as to whether periodic location reporting is supported by the RANs in the PLMN. If this list of PLMNs is not provided, then subsequent MO-LR requests may be restricted to the current serving PLMN. Any agreement on using GMLC short circuit and/or MO-LR short circuit may be applicable to all of the PLMNs in the list.
  • UE 120 may instigate release of the Connection Management (CM), Mobility Management (MM) or GPRS Mobility Management (GMM), and Radio Resource Control (RR/RRC) connections to the UE (not shown in FIG. 3 ), e.g., if the periodic location request is rejected, or if the list of PLMNs does not include the serving PLMN, or if the serving PLMN was included with a lower priority, or if the first location estimate is not needed yet.
  • CM Connection Management
  • MM Mobility Management
  • GMM GPRS Mobility Management
  • RR/RRC Radio Resource Control
  • UE 120 may initiate reporting of the first location estimate by sending an LCS MO-LR Location Services Invoke message to request transfer of the UE location to LCS client 170 (also not shown in FIG. 3 ). Periodic location reporting is then performed as indicated by the periodic location information (steps 14a through 14n).
  • a sequence of messages may be initially exchanged between R-GMLC 154, H-GMLC 152, V-GMLC 150 and MSC/SGSN 140 for security and privacy and to provide each entity with pertinent information for the periodic location request.
  • GMLC short circuit may thereafter be used to achieve efficient periodic location reporting, as described below.
  • Each of V-GMLC 150, H-GMLC 152, R-GMLC 154, and MSC/SGSN 140 may store or cache pertinent information for the periodic location request from LCS client 170 (for message flow 200 in FIG. 2 ) or from UE 120 (for message flow 300 in FIG. 3 ).
  • the cached information may include, for example, the reference ID for the periodic location request, the addresses of other network entities, the identifier of target UE 120, the periodic location information, indications as to whether GMLC short circuit and/or MO-LR short circuit are allowed, the LCS QoS, and so on.
  • the cached information may be used for subsequent location reporting to provide the UE location information to LCS client 170.
  • the periodic location reporting in steps 16a through 16n of message flow 200 and in steps 14a through 14n of message flow 300 may be performed in various manners.
  • UE 120 initiates a one-shot MO-LR message flow to provide its location estimate to LCS client 170.
  • UE 120 may also initiate an MO-LR message flow whenever needed in order to obtain updated assistance data and/or to compute a new location estimate for itself.
  • R-GMLC 154 initiates a one-shot MT-LR message flow to obtain a location estimate for UE 120 and to send this location estimate to LCS client 170.
  • RAN 130 initiates location processing to provide the location estimate for UE 120 to LCS client 170.
  • the first location reporting event may occur immediately after completing the message exchange to initiate periodic location reporting. The location reporting may continue until one of the following events occurs:
  • FIG. 4 shows a message flow 400 for one-shot MO-LR.
  • UE 120 may use all or part of message flow 400 to (1) request its own location for basic self location, (2) request location assistance data for autonomous self location, (3) request a transfer of the UE location to an LCS client for a transfer to a third party (TTTP), or (4) achieve some other result.
  • UE 120 may also use message flow 400 for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • Steps 1 through 3 of message flow 400 are the same as steps 1 through 3 of message flow 300 in FIG. 3 .
  • UE 120 then sends to MSC/SGSN 140 an LCS MO-LR Location Services Invoke message to request a desired location service (e.g., to request for location of the UE, location assistance data, transfer of the UE location to an LCS client, and so on) (step 4).
  • the LCS MO-LR Location Services Invoke message contains pertinent information such as, e.g., the LCS QoS (e.g., accuracy and response time), the identity of LCS client 170, the address of H-GMLC 152 or R-GMLC 154, the type of assistance data desired, and so on.
  • UE 120 may also provide its location estimate in the LCS MO-LR Location Services Invoke message (not shown in FIG. 4 ), e.g., if this location estimate is available and MO-LR short circuit is allowed or preferred.
  • MSC/SGSN 140 verifies that UE 120 is authorized for the requested location service based on a subscription profile for the UE (also step 4). If the location request is authorized, then MSC/SGSN 140 sends to RAN 130 a Location Request message that contains the type of location information requested, the UE capabilities, and the LCS QoS (step 5). If the MO-LR Location Services Invoke message in step 4 requests a location estimate for UE 120, then RAN 130 selects an appropriate positioning method based on the location request, the required accuracy, and the UE capabilities. RAN 130 then initiates an appropriate message sequence for the selected positioning method (step 6). RAN 130 receives a report with measurements or a location estimate for UE 120 from the UE and/or entities within or associated with the RAN.
  • RAN 130 computes a location estimate for UE 120 if needed and sends to MSC/SGSN 140 a Location Report message that contains the location estimate for the UE (step 7). If the MO-LR Location Services Invoke message in step 4 requests location assistance data for autonomous self-location, then RAN 130 returns assistance data to UE 120 in step 6 and does not return a location estimate in step 7.
  • V-GMLC 150 a MAP Subscriber Location Report message that contains the location estimate for the UE and other relevant information (step 8).
  • V-GMLC 150 then sends to H-GMLC 152 an MO-LR Location Information message that contains the location estimate and relevant information (step 9).
  • H-GMLC 152 then sends an MO-LR Location Information message to R-GMLC 154 (step 10), which in turn sends the location estimate and relevant information to LCS client 170 (step 11).
  • LCS client 170 responds by sending a location information acknowledgment to R-GMLC 154 (step 12).
  • R-GMLC 154 sends to H-GMLC 152 an MO-LR Location Information Acknowledgment message that indicates whether the location estimate has been successfully sent to LCS client 170 (step 13).
  • H-GMLC 152 forwards the MO-LR Location Information Acknowledgment message to V-GMLC 150 (step 14), which sends a MAP Subscriber Location Report Acknowledgment message to MSC/SGSN 140 (step 15).
  • Steps 8 through 15 may be omitted, or some other steps may be performed, for other types of location services requested by UE 120.
  • MSC/SGSN 140 sends to UE 120 an LCS MO-LR Return Result message that contains a location estimate (if requested by the UE) and possibly other relevant information (step 16). MSC/SGSN 140 may instigate release of the CM, MM or GMM, and RR/RRC connections to UE 120, if the UE was previously idle (step 17). Step 17 of message flow 400 may be omitted if UE 120 is in the dedicated mode.
  • FIG. 5 shows a message flow 500 for one-shot MO-LR with GLMC short circuit.
  • Message flow 500 may be used in place of message flow 400 in FIG. 4 if GMLC short circuit is allowed.
  • Message flow 500 may be used for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • Message flow 500 includes a subset of the steps in message flow 400. Steps 1 through 7 of message flow 500 are similar to steps 1 through 7 of message flow 400.
  • the LCS MO-LR Location Services Invoke message sent in step 4 of message flow 500 includes the reference ID for the periodic location request previously initiated, the periodic location information, the address of R-GMLC 154 ("r-gmlc") if GMLC short circuit is allowed, the LCS QoS, and so on.
  • MSC/SGSN 140 may store (e.g., in steps 8 and/or 12 of message flow 200, or in step 12 of message flow 300) information that tells MSC/SGSN 140 that the periodic location reporting has been authorized by R-GMLC 154, H-GMLC 152, and V-GMLC 150.
  • the LCS MO-LR Location Services Invoke message sent in step 4 of message flow 500 may contain information that tells MSC/SGSN 140 that the location reporting (e.g., message flow 500) has been authorized by R-GMLC 154, H-GMLC 152, and V-GMLC 150.
  • the LCS MO-LR Location Services Invoke message may further include the H-GMLC address (even if GMLC short circuit is used) in order to notify V-GMLC 150 and H-GMLC 152 that the periodic location reporting is terminating.
  • MSC/SGSN 140 sends to RAN 130 a Location Request message to request for a location estimate for UE 120 (step 5) and receives from RAN 130 a Location Report message that contains the location estimate (step 7). MSC/SGSN 140 then sends directly to R-GMLC 154, using the R-GMLC address provided by UE 120 or stored by MSC/SGSN 140, a MAP Subscriber Location Report message (as shown in FIG. 5 ) or an MO-LR Location Information message (not shown in FIG. 5 ) that contains the location estimate for the UE and other relevant information (step 8).
  • R-GMLC 154 sends the location information to LCS client 170 (step 11), receives an acknowledgment from the LCS client (step 12), and sends directly to MSC/SGSN 140 a MAP Subscriber Location Report Acknowledgment message (as shown in FIG. 5 ) or an MO-LR Location Information Acknowledgment message (not shown in FIG. 5 ) (step 15).
  • Steps 9, 10, 13 and 14 are short circuited and V-GMLC 150 and H-GMLC 152 are bypassed, which reduces network traffic and improves the response time for sending the location information to LCS client 170.
  • FIG. 6 shows a message flow 600 for one-shot MO-LR with GLMC short circuit and MO-LR short circuit.
  • Message flow 600 may be used in place of message flow 400 in FIG. 4 and message flow 500 in FIG. 5 if GMLC short circuit and MO-LR short circuit are allowed.
  • Message flow 600 may be used for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • Message flow 600 includes a subset of the steps in message flows 400 and 500. Steps 1 through 4 of message flow 600 are similar to steps 1 through 4 of message flow 400. One difference is that the LCS MO-LR Location Services Invoke message sent in step 4 of message flow 600 may include the reference ID for the previously initiated periodic location request, a location estimate for the UE (e.g., if UE-based mode is supported and MO-LR short circuit is allowed), the address of R-GMLC 154, and so on. MSC/SGSN 140 receives the LCS MO-LR Location Services Invoke message, decides to use the location estimate sent by UE 120, and bypasses the location processing in steps 5 through 7.
  • the LCS MO-LR Location Services Invoke message sent in step 4 of message flow 600 may include the reference ID for the previously initiated periodic location request, a location estimate for the UE (e.g., if UE-based mode is supported and MO-LR short circuit is allowed), the address of R-GMLC 154, and so on.
  • MSC/SGSN 140 then sends a MAP Subscriber Location Report message (as shown in FIG. 6 ) or an MO-LR Location Information message (not shown in FIG. 6 ) that contains the location estimate for the UE and other relevant information (e.g., an indication that MO-LR short circuit was used) directly to R-GMLC 154 using the R-GMLC address provided by UE 120 (step 8).
  • MAP Subscriber Location Report message as shown in FIG. 6
  • MO-LR Location Information message not shown in FIG. 6
  • the remaining steps of message flow 600 are as described above for message flow 500 in FIG. 5 .
  • steps 5 through 7 are bypassed for the MO-LR short circuit, which avoids involvement of RAN 130 and reduces over-the-air traffic.
  • steps 9, 10, 13 and 14 are bypassed for the GMLC short circuit, which reduces both network traffic and involvement of V-GMLC 150 and H-GMLC 152. Both types of short circuit improve the response time to send the location information to LCS client 170.
  • FIG. 7 shows a message flow 700 for one-shot MT-LR, which may be used for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • R-GMLC 154 finds the cached information (e.g., the H-GMLC address) for the periodic location request that was previously initiated (step 1).
  • R-GMLC 154 then sends to H-GMLC 152 an LCS Service Request message that contains a request for UE location and relevant information (step 2).
  • H-GMLC 152 finds the cached information (e.g., the V-GMLC address) for the periodic location request (step 3) and sends an LCS Service Request message to V-GMLC 150 (step 4).
  • V-GMLC 150 finds the cached information (e.g., the MSC/SGSN address) for the periodic location request (step 5) and sends a Provide Subscriber Location message (as shown in FIG. 7 ) or an LCS Service Request message (not shown in FIG. 7 ) to MSC/SGSN 140 to request the current location of UE 120 (step 6). MSC/SGSN 140 may authenticate that the location request is allowed (also step 6).
  • the cached information e.g., the MSC/SGSN address
  • LCS Service Request message not shown in FIG. 7
  • MSC/SGSN 140 may authenticate that the location request is allowed (also step 6).
  • MSC/SGSN 140 instigates paging, authentication, and ciphering if UE 120 is in the idle mode (step 7). MSC/SGSN 140 then sends to UE 120 an LCS Location Notification Invoke message to request a location estimate for UE 120 (step 8). UE 120 returns an LCS Location Notification Return Result message (step 9). Location processing may then be performed in steps 10, 11 and 12, e.g., as described above for steps 5, 6 and 7 of message flow 400 in FIG. 4 . MSC/SGSN 140 then sends to V-GMLC 150 a Provide Subscriber Location Acknowledgment message (as shown in FIG. 7 ) or an LCS Service Response message (not shown in FIG.
  • V-GMLC 150 sends an LCS Service Response message to H-GMLC 152 (step 14), which sends an LCS Service Response message to R-GMLC 154 (step 15).
  • R-GMLC 154 then sends location information (e.g., the location estimate for UE 120) to LCS client 170 (step 16).
  • LCS client 170 responds by sending a location information acknowledgment to R-GMLC 154 (step 17).
  • MSC/SGSN 140 may instigate release of the CM, MM or GMM, and RR/RRC connections to UE 120 (step 18).
  • FIG. 8 shows a message flow 800 for one-shot MT-LR with GLMC short circuit.
  • Message flow 800 may be used in place of message flow 700 in FIG. 7 if GMLC short circuit is allowed.
  • Message flow 800 may be used for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • Message flow 800 includes a subset of the steps in message flow 700.
  • R-GMLC 154 finds the cached information (e.g., the MSC/SGSN address) for the periodic location request that was previously initiated (step 1).
  • R-GMLC 154 then sends directly to MSC/SGSN 140 a Provide Subscriber Location message (as shown in FIG. 8 ) or an LCS Service Request message (not shown in FIG. 8 ) that contains a request for UE location and relevant information (step 2).
  • Steps 7 through 12 of message flow 800 are the same as steps 7 through 12 of message flow 700.
  • MSC/SGSN 140 receives a location estimate for UE 120 from RAN 130 and sends to R-GMLC 154 a Provide Subscriber Location Acknowledgment message (as shown in FIG. 8 ) or an LCS Service Response message (not shown in FIG. 8 ) that contains the location estimate for UE 120 (step 13).
  • R-GMLC 154 sends the location information to LCS client 170 (step 16) and receives an acknowledgment from the LCS client (step 17). Steps 3, 4, 5, 6, 14 and 15 are short circuited and V-GMLC 150 and H-GMLC 152 are bypassed for message flow 800.
  • R-GMLC 154 may choose to use message flow 700 rather than message flow 800 in order to notify H-GMLC 152 and V-GMLC 150 that the periodic location reporting is terminating.
  • This notification may be of assistance for billing and security, e.g., steps 2 and 4 of message flow 700 for the final location reporting event may include information regarding the number of successful location transfers to LCS client 170 and whether errors were encountered.
  • FIG. 9 shows a message flow 900 for one-shot MT-LR with GLMC short circuit and MO-LR short circuit.
  • Message flow 900 may be used in place of message flow 700 in FIG. 7 and message flow 800 in FIG. 8 if GMLC short circuit and MO-LR short circuit are both allowed.
  • Message flow 900 may be used for each of the location reporting events in message flow 200 in FIG. 2 and message flow 300 in FIG. 3 .
  • Message flow 900 includes a subset of the steps in message flows 700 and 800.
  • R-GMLC 154 finds the cached information for the periodic location request that was previously initiated (step 1).
  • R-GMLC 154 then sends an LCS Service Request message that contains a request for UE location and relevant information directly to MSC/SGSN 140 (step 2).
  • Steps 7, 8 and 9 of message flow 900 are similar to steps 7, 8 and 9 of message flow 700.
  • the LCS MO-LR Location Services Invoke message sent by UE 120 in step 9 of message flow 900 includes a location estimate for the UE.
  • MSC/SGSN 140 receives this message from UE 120, decides to use the location estimate sent by the UE, and bypasses the location processing in steps 10 through 12.
  • MSC/SGSN 140 then sends a MAP Subscriber Location Report message that contains the location estimate for the UE and other relevant information directly to R-GMLC 154 (step 13).
  • the remaining steps of message flow 900 are as described above for message flow
  • steps 10 through 12 are bypassed for the MO-LR short circuit, which reduces over-the-air traffic and/or signaling traffic in RAN 130 and also reduces delay.
  • steps 3, 4, 5, 6, 14 and 15 are bypassed for the GMLC short circuit, which reduces network traffic and delay.
  • location reporting may be repeated at a specified interval or following the occurrence of certain events. Each location reporting event causes a single location estimate for UE 120 to be sent to LCS client 170. If periodic location reporting is supported by RAN 130, then the location reporting may be repeated at some multiple of the specified interval, with each RAN invocation causing multiple location estimates for UE 120 (obtained by RAN 130) to be sent to LCS client 170.
  • UE 120 may be responsible for ensuring that a location report is sent to R-GMLC 154 at the specified intervals or following specified events even if, in the case of MO-LR short circuit and UE-based mode, the UE cannot obtain a location estimate.
  • UE 120 may initiate an MO-LR request (e.g., message flow 600) at the specified intervals or following specified events but may not include any location estimate (e.g., in step 4 of message flow 600).
  • the location report received by R-GMLC 154 e.g., in step 8 of message flow 600
  • This periodic reporting enables R-GMLC 154 to determine whether UE 120 may have moved out of the coverage of the PLMN(s) within which periodic location reporting is allowed.
  • R-GMLC 154 may make this determination if it receives no location reporting (e.g., in step 8 of message flow 600) for some time period greater (e.g., more than two times greater) than the expected maximum time interval between periodic location reports (e.g., between consecutive instances of step 8 in message flow 600).
  • R-GMLC 154 may cancel the periodic location reporting by sending an LCS Cancel Service request to H-GMLC 152 whenever R-GMLC 154 infers from the absence of periodic location reports that the service may have been terminated.
  • H-GMLC 152 forwards this message to V-GMLC 150, which forwards it to MSC/SGSN 140, which in turn sends an LCS Periodic Event cancellation to UE 120, if UE 120 is reachable.
  • UE 120 terminates the periodic location reporting if (1) UE 120 moves out of coverage of the PLMN(s) within which location reporting is allowed, (2) a conflict with the PLMNs preferred by UE 120 for other services prevents access to the PLMNs assigned for periodic location reporting, (3) an MO-LR request is denied by the current serving PLMN with an indication that the periodic location reporting cannot or can no longer be supported, (4) the UE subscriber terminates the periodic location reporting, or (5) some other termination condition has occurred.
  • UE 120 may detect conditions (1) and (2) if the UE is unable to instigate an MO-LR request for some period of time T, where T may be some multiple of the specified location reporting interval, if fixed, or some multiple of the maximum expected (or maximum allowed) reporting interval otherwise.
  • UE 120 may encounter condition (3) if, e.g., MO-LR short circuit was initially allowed but can no longer be supported by the UE or the current serving PLMN.
  • UE 120 may terminate the periodic location reporting by sending an MO-LR TTTP report without a location estimate, but with a termination cause, to MSC/SGSN 140, which then transfers this indication to V-GMLC 150, H-GMLC 152, and R-GMLC 154. This speeds up notification to the GMLCs and LCS client 170 and allows a specific reason for the termination to be given.
  • each of the message flows in FIGS. 2 through 9 shows a specific sequence of steps.
  • Each message flow may include additional, fewer, or different steps than the steps shown for that message flow.
  • the steps for each message flow may be performed in the order shown in that message flow or in a different order.
  • Each step in each message flow may in general include any number of message exchanges, any type of processing at any entity, and so on.
  • any signaling may be used to exchange pertinent information among the various entities to achieve the functionality described above for location reporting, GMLC short circuit, and MO-LR short circuit.
  • the signaling may comprise messages, packets, indications, flags, or data sent in some other form.
  • the location reporting techniques have been specifically described above for 3GPP-based networks and for a control plane architecture.
  • the techniques may also be used for other networks and other architectures, such as a SUPL architecture and a pre-SUPL architecture promulgated by Open Mobile Alliance (OMA), a 3GPP2 control plane architecture described in IS-881 and 3GPP2 X.S0002, and so on.
  • the short circuit techniques may also be used for circuit-switched (CS) based modes and packet-switched (PS) based modes, although the messages for the message flows may be different.
  • FIG. 10 shows a SUPL deployment 1000 that includes a visited/serving network 1002, a home network 1004, and a requesting network 1006.
  • Visited network 1002 includes a wireless network 1030 and a visiting SUPL location platform (V-SLP) 1050.
  • Wireless network 1030 provides wireless communication for wireless devices located within the coverage area of the wireless network.
  • a wireless device is also called a SUPL enabled terminal (SET).
  • V-SLP 1050 includes a SUPL location center (SLC) 1080 and may include a SUPL positioning center (1082).
  • SLC 1080 is similar to V-GMLC 150 and performs various functions for location services.
  • SPC 1082 is similar to an SMLC and supports positioning for wireless devices.
  • Home network 1004 includes a home SLP (H-SLP) 1052 that supports location services and positioning for home network 1004.
  • Requesting network 1006 includes a requesting SLP (R-SLP) 1054 that supports location services and positioning for LCS clients.
  • V-SLP 1050, R-SLP 1054, and H-SLP 1052 may generically be referred to as first, second, and third location centers, respectively, that are associated with different networks.
  • GMLC short circuit and MO-LR short circuit may be used for SUPL deployment 1000.
  • a wireless device 1020 may send a location estimate directly to R-SLP 1054, which then forwards the location estimate to an LCS client 1070.
  • wireless device 1020 may send a location estimate to H-SLP 1052, which then forwards the location estimate to R-SLP 1054, which further forwards the location estimate to LCS client 1070.
  • FIG. 11 shows a block diagram of various network entities and UE 120 in 3GPP-based network 100 in FIG. 1 .
  • RAN 130 provides wireless communication for visited network 102 and may include multiple base stations or Node Bs.
  • base stations in RAN 130 transmit traffic data, signaling, and pilot to the UEs within its coverage area.
  • These various types of data are processed by a processor 1130 and conditioned by a transceiver 1134 to generate a downlink signal, which is transmitted via an antenna.
  • the downlink signals from one or more base stations in RAN 130 are received via an antenna, conditioned by a transceiver 1124, and processed by a processor 1120 to obtain various types of information for location services.
  • processor 1120 may obtain time of arrival of received signals (which may be used for positioning), decoded messages used for the message flows described above, and so on.
  • Memory units 1122 and 1132 store program codes and data for processors 1120 and 1130, respectively, at UE 120 and RAN 130.
  • UE 120 On the uplink, UE 120 may transmit traffic data, signaling, and pilot to one or more base stations in RAN 130. These various types of data are processed by processor 1120 and conditioned by transceiver 1124 to generate an uplink signal, which is transmitted via the UE antenna.
  • the uplink signal from UE 120 and other UEs are received and conditioned by transceiver 1134 and further processed by processor 1130 to obtain various types of information (e.g., data, signaling, reports, and so on).
  • a communication (Comm) unit 1136 allows RAN 130 to communicate with MSC/SGSN 140.
  • MSC/SGSN 140 includes a processor 1140 that performs processing for MSC/SGSN 140, a memory unit 1142 that stores program codes and data for processor 1140, and a communication unit 1144 that allows MSC/SGSN 140 to communicate with RAN 130 and other network entities via data/core networks 1102.
  • R-GMLC 154 includes a processor 1150 that performs processing for R-GMLC 154, a memory unit 1152 that stores program codes and data for processor 1150, and a communication unit 1154 that allows R-GMLC 154 to communicate with other network entities via data/core networks 1102.
  • each network entity may include one or more processors, memory units, communication units, controllers, and so on.
  • Data/core networks 1102 may include (1) core networks for visited network 102, home network 104, and/or requesting network 106 and/or (2) other private and/or public data networks.
  • the techniques described herein may be implemented by various means.
  • the techniques may be implemented in hardware, software, or a combination thereof.
  • the units used to perform the processing at each entity may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
  • the techniques may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in a memory unit (e.g., memory unit 1122, 1132, 1142, or 1152 in FIG. 11 ) and executed by a processor (e.g., processor 1120, 1130, 1140, or 1150).
  • the memory unit may be implemented within the processor or external to the processor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (38)

  1. Procédé de fourniture de services de localisation pour un équipement utilisateur (UE) (120), l'UE étant en communication avec un réseau de desserte (102) qui est associé à un premier centre de localisation, le procédé comprenant :
    l'obtention, au niveau du réseau de desserte (102), d'une estimation de position pour l'UE (120) ;
    caractérisé en ce que le procédé comprend en outre :
    l'envoi, par le réseau de desserte (102), de l'estimation de position pour l'UE (120) directement à un deuxième centre de localisation en utilisant une adresse du deuxième centre de localisation, court-circuitant ainsi le premier centre de localisation, dans lequel le deuxième centre de localisation est associé à une entité client (170) recevant l'estimation de position pour l'UE (120), dans lequel les premier et deuxième centres de localisation sont associés à des réseaux différents, et dans lequel l'adresse du deuxième centre de localisation est fournie par l'UE ou stockée par le réseau de desserte.
  2. Procédé selon la revendication 1, dans lequel l'obtention de l'estimation de position comprend la réalisation d'un traitement de localisation avec l'équipement utilisateur (UE) (120), si le traitement de localisation est lancé, afin d'obtenir l'estimation de position pour l'UE (120).
  3. Procédé selon la revendication 2, dans lequel l'envoi de l'estimation de position pour l'UE (120) comprend :
    l'envoi de l'estimation de position pour l'UE (120) directement au deuxième centre de localisation et en court-circuitant le premier centre de localisation et un troisième centre de localisation, le troisième centre de localisation étant associé à un réseau mère (104) pour l'UE (120).
  4. Procédé selon la revendication 2, dans lequel le premier centre de localisation est un centre de localisation mobile passerelle visité (V-GMLC) (150), et dans lequel le deuxième centre de localisation est un centre de localisation mobile passerelle demandeur (R-GMLC) (154).
  5. Procédé selon la revendication 2, dans lequel le premier centre de localisation est une plateforme de localisation pour localisation de plan utilisateur sécurisée (SUPL) visitée (V-LSP) (1050), et dans lequel le deuxième centre de localisation est une SLP demandeuse (R-LSP) (1054).
  6. Procédé selon la revendication 2, comprenant en outre :
    la réception, en provenance de l'UE (120), d'une estimation de position pour l'UE (120); et
    l'évitement du traitement de localisation si l'estimation de position reçue en provenance de l'UE (120) est sélectionnée pour être utilisée.
  7. Procédé selon la revendication 2, comprenant en outre :
    la réception, en provenance de l'UE (120), d'une requête d'envoi de l'estimation de position pour l'UE (120) à l'entité client, et dans lequel la réalisation d'un traitement de localisation avec l'UE (120) et l'envoi de l'estimation de position pour l'UE (120) sont effectués en réponse à la requête.
  8. Procédé selon la revendication 2, comprenant en outre :
    la réception, en provenance du deuxième centre de localisation, d'une requête d'envoi de l'estimation de position pour l'UE (120) à l'entité client, et dans lequel la réalisation d'un traitement de localisation avec l'UE (120) et l'envoi de l'estimation de position pour l'UE (120) sont effectués en réponse à la requête.
  9. Procédé selon la revendication 2, comprenant en outre :
    la réception, en provenance de l'UE (120), d'une requête de rapport périodique de localisation de l'UE (120) à l'entité client ; et
    la répétition de la réalisation d'un traitement de localisation avec l'UE (120) et de l'envoi de l'estimation de position pour l'UE (120) directement au deuxième centre de localisation sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client.
  10. Procédé selon la revendication 2, comprenant en outre :
    la réception d'une requête envoyée par l'entité client demandant un rapport périodique de localisation de l'UE (120) à l'entité client ; et
    la répétition de la réalisation d'un traitement de localisation avec l'UE (120) et de l'envoi de l'estimation de position pour l'UE (120) directement au deuxième centre de localisation sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client.
  11. Procédé selon la revendication 2, comprenant en outre :
    la réception d'une requête de court-circuitage du premier centre de localisation ; et
    l'acceptation ou le rejet de la requête de court-circuitage du premier centre de localisation.
  12. Procédé selon la revendication 2, comprenant en outre :
    la réception d'une requête d'évitement du traitement de localisation ; et
    l'acceptation ou le rejet de la requête d'évitement du traitement de localisation.
  13. Procédé selon la revendication 1, comprenant en outre :
    l'échange de signalisation entre l'équipement utilisateur (UE) et le réseau de desserte (102) pour une requête de service de localisation, et dans lequel l'obtention de l'estimation de position comprend la réalisation d'un traitement de localisation avec le réseau de desserte (102), si le traitement de localisation est lancé, afin d'obtenir l'estimation de position pour l'UE (120).
  14. Procédé selon la revendication 13, dans lequel l'échange de signalisation entre l'UE (120) et le réseau de desserte comprend :
    l'envoi de la requête de service de localisation de l'UE (120) au réseau de desserte (102) ; et
    l'envoi d'une adresse du deuxième centre de localisation de l'UE (120) au réseau de desserte (102), et dans lequel l'estimation de position pour l'UE (120) est envoyée par le réseau de desserte (102) directement au deuxième centre de localisation en utilisant l'adresse envoyée par l'UE (120).
  15. Procédé selon la revendication 13, dans lequel l'échange de signalisation entre l'UE (120) et le réseau de desserte comprend la réception, en provenance du réseau de desserte, de la requête de service de localisation.
  16. Procédé selon la revendication 13, dans lequel l'échange de signalisation entre l'UE (120) et le réseau de desserte (102) comprend :
    l'envoi d'une estimation de position pour l'UE (120) au réseau de desserte (102), et dans lequel le traitement de localisation est évité si l'estimation de position envoyée par le réseau de desserte (102) est sélectionnée pour être utilisée.
  17. Procédé selon la revendication 13, comprenant en outre :
    l'envoi, au réseau de desserte, d'une requête de rapport périodique de localisation de l'UE (120) à l'entité client (170) ; et
    la répétition de l'échange de signalisation entre l'UE (120) et le réseau de desserte (102) et de la réalisation d'un traitement de localisation avec le réseau de desserte (102) sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client (170).
  18. Procédé selon la revendication 13, comprenant en outre :
    la réception, en provenance du réseau de desserte (102), d'une requête en provenance de l'entité client (170) demandant un rapport périodique de localisation de l'UE (120) à l'entité client (170) ; et
    la répétition de l'échange de signalisation entre l'UE (120) et le réseau de desserte et de la réalisation d'un traitement de localisation avec le réseau de desserte sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client.
  19. Procédé selon la revendication 13, comprenant en outre :
    l'envoi d'une requête de court-circuitage du premier centre de localisation ; et
    la réception d'une indication d'acceptation ou de rejet de la requête de court-circuitage du premier centre de localisation.
  20. Procédé selon la revendication 13, comprenant en outre :
    l'envoi d'une requête d'évitement du traitement de localisation ; et
    la réception d'une indication d'acceptation ou de rejet de la requête d'évitement du traitement de localisation.
  21. Procédé selon la revendication 1, comprenant en outre :
    la réception, au niveau du deuxième centre de localisation, de l'estimation de position pour l'UE (120) directement en provenance du réseau de desserte (102) ; et
    l'envoi de l'estimation de position pour l'UE (120) du deuxième centre de localisation à une entité client (170).
  22. Procédé selon la revendication 21, comprenant en outre :
    la réception d'une requête de court-circuitage du premier centre de localisation ; et
    l'acceptation ou le rejet de la requête de court-circuitage du premier centre de localisation.
  23. Procédé selon la revendication 21, comprenant en outre :
    l'envoi d'une requête de localisation de l'UE (120) directement au réseau de desserte (102) et en court-circuitant le premier centre de localisation.
  24. Procédé selon la revendication 21, comprenant en outre :
    la réception, en provenance de l'entité client, d'une requête de rapport périodique de localisation de l'UE (120) à l'entité client (170) ;
    l'envoi de la requête de rapport périodique au réseau de desserte (102) ; et
    la répétition de la réception, en provenance du réseau de desserte (102), de l'estimation de position pour l'UE (120) et de l'envoi de l'estimation de position pour l'UE (120) du deuxième centre de localisation à l'entité client (170) sur la base d'information de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client (170).
  25. Procédé selon la revendication 24, comprenant en outre :
    le stockage d'informations pour la requête de rapport périodique ; et
    pour chaque événement de rapport de localisation indiqué par les informations de localisation périodique,
    la récupération des informations stockées pour la requête de rapport périodique, et
    l'envoi d'une requête de localisation de l'UE (120) directement au réseau de desserte (102) et en court-circuitant le premier centre de localisation sur la base des informations récupérées.
  26. Procédé selon la revendication 21, comprenant en outre :
    la réception d'une requête envoyée par l'UE (120) demandant un rapport périodique de localisation de l'UE (120) à l'entité client ;
    l'envoi de la requête de rapport périodique à l'entité client (170) ; et
    la répétition de la réception, en provenance du réseau de desserte (102), de l'estimation de position pour l'UE (120) et de l'envoi de l'estimation de position pour l'UE (120) du deuxième centre de localisation à l'entité client sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client.
  27. Appareil utilisable pour fournir des services de localisation pour un équipement utilisateur (UE) (120), l'UE étant utilisable pour communiquer avec un réseau de desserte (102) qui est associé à un premier centre de localisation, l'appareil comprenant :
    un moyen configuré pour obtenir, au niveau du réseau de desserte (102), une estimation de position pour l'UE (120) ;
    caractérisé en ce que l'appareil comprend en outre:
    un moyen configuré pour envoyer l'estimation de position pour l'UE (120) du réseau de desserte (102) directement à un deuxième centre de localisation en utilisant une adresse du deuxième centre de localisation, court-circuitant ainsi le premier centre de localisation, le deuxième centre de localisation étant associé à une entité client (170) recevant l'estimation de position pour l'UE (120), les premier et deuxième centres de localisation étant associés à des réseaux différents, et l'adresse du deuxième centre de localisation étant fournie par l'UE ou stockée par le réseau de desserte.
  28. Appareil selon la revendication 27, dans lequel le moyen configuré pour obtenir l'estimation de position comprend un moyen configuré pour effectuer un traitement de localisation avec l'équipement utilisateur (UE) (120), si le traitement de localisation est lancé, afin d'obtenir l'estimation de position pour l'UE (120).
  29. Appareil selon la revendication 28, comprenant en outre :
    un moyen configuré pour recevoir une requête de court-circuitage du premier centre de localisation ; et
    un moyen configuré pour accepter ou rejeter la requête de court-circuitage du premier centre de localisation.
  30. Appareil selon la revendication 28, comprenant en outre :
    un moyen configuré pour recevoir en provenance de l'UE (120) une estimation de position pour l'UE (120) ; et
    un moyen configuré pour éviter le traitement de localisation si l'estimation de position reçue en provenance de l'UE (120) est sélectionnée pour être utilisée.
  31. Appareil selon la revendication 27, comprenant en outre :
    un moyen configuré pour échanger de la signalisation entre l'équipement utilisateur (UE) et le réseau de desserte (102) pour une requête de service de localisation, et dans lequel le moyen configuré pour obtenir l'estimation de position comprend un moyen configuré pour effectuer un traitement de localisation avec le réseau de desserte (102), si le traitement de localisation est lancé, afin d'obtenir l'estimation de position pour l'UE (120).
  32. Appareil selon la revendication 31, dans lequel le moyen configuré pour échanger de la signalisation entre l'UE et le réseau de desserte (102) comprend :
    un moyen configuré pour envoyer la requête de service de localisation de l'UE (120) au réseau de desserte (102) ; et
    un moyen configuré pour envoyer une adresse du deuxième centre de localisation de l'UE (120) au réseau de desserte (102), et dans lequel l'estimation de position pour l'UE (120) est envoyée par le réseau de desserte (102) directement au deuxième centre de localisation en utilisant l'adresse envoyée par l'UE (120).
  33. Appareil selon la revendication 31, dans lequel le moyen configuré pour échanger de la signalisation entre l'UE (120) et le réseau de desserte (102) comprend :
    un moyen configuré pour envoyer une estimation de position pour l'UE (120) au réseau de desserte (102), et dans lequel le traitement de localisation est évité si l'estimation de position envoyée au réseau de desserte (102) est sélectionnée pour être utilisée.
  34. Appareil selon la revendication 31, comprenant en outre :
    un moyen configuré pour envoyer une requête de court-circuitage du premier centre de localisation ; et
    un moyen configuré pour recevoir une indication d'acceptation ou de rejet de la requête de court-circuitage du premier centre de localisation.
  35. Appareil selon la revendication 27, l'appareil comprenant en outre ledit deuxième centre de localisation, le deuxième centre de localisation comprenant :
    un moyen configuré pour recevoir l'estimation de position pour l'UE (120) directement en provenance du réseau de desserte (102) ; et
    un moyen configuré pour envoyer l'estimation de position pour l'UE (120) du deuxième centre de localisation à une entité client (170).
  36. Appareil selon la revendication 35, comprenant en outre :
    un moyen configuré pour recevoir une requête de court-circuitage du premier centre de localisation ; et
    un moyen configuré pour accepter ou rejeter la requête de court-circuitage du premier centre de localisation.
  37. Appareil selon la revendication 35, comprenant en outre :
    un moyen configuré pour stocker des informations pour une requête de rapport périodique de localisation de l'UE (120) à l'entité client (170) ;
    un moyen configuré pour déterminer des événements de rapport de localisation sur la base d'informations de localisation périodique indiquant quand envoyer l'estimation de position pour l'UE (120) à l'entité client (170) ;
    un moyen configuré pour récupérer les informations stockées pour la requête de rapport périodique pour chaque événement de rapport de localisation ; et
    un moyen configuré pour envoyer une requête de localisation de l'UE (120) directement au réseau de desserte (102) et en court-circuitant le premier centre de localisation sur la base des informations récupérées.
  38. Support lisible par ordinateur comprenant des instructions qui, lorsqu'elles sont exécutées par un ordinateur approprié, amènent l'ordinateur à mettre en oeuvre un procédé selon l'une quelconque des revendications 1 à 26.
EP06773799.9A 2005-06-21 2006-06-21 Procede et appareil pour la fourniture de services de localisation avec des flux de messages reduits Active EP1894430B1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US69300305P 2005-06-21 2005-06-21
US73733905P 2005-11-14 2005-11-14
US11/471,049 US8792902B2 (en) 2005-06-21 2006-06-19 Method and apparatus for providing location services with short-circuited message flows
PCT/US2006/024374 WO2007002333A1 (fr) 2005-06-21 2006-06-21 Procede et appareil pour la fourniture de services de localisation avec des flux de messages court-circuites

Publications (2)

Publication Number Publication Date
EP1894430A1 EP1894430A1 (fr) 2008-03-05
EP1894430B1 true EP1894430B1 (fr) 2013-05-08

Family

ID=37590288

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06773799.9A Active EP1894430B1 (fr) 2005-06-21 2006-06-21 Procede et appareil pour la fourniture de services de localisation avec des flux de messages reduits

Country Status (5)

Country Link
US (1) US8792902B2 (fr)
EP (1) EP1894430B1 (fr)
CN (1) CN101278574B (fr)
CA (1) CA2612992A1 (fr)
WO (1) WO2007002333A1 (fr)

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070238455A1 (en) * 2006-04-07 2007-10-11 Yinjun Zhu Mobile based area event handling when currently visited network doe not cover area
US7424293B2 (en) 2003-12-02 2008-09-09 Telecommunication Systems, Inc. User plane location based service using message tunneling to support roaming
US7260186B2 (en) 2004-03-23 2007-08-21 Telecommunication Systems, Inc. Solutions for voice over internet protocol (VoIP) 911 location services
US7974639B2 (en) 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
US9154907B2 (en) 2005-06-21 2015-10-06 Qualcomm Incorporated Efficient periodic location reporting in a radio access network
US8660573B2 (en) 2005-07-19 2014-02-25 Telecommunications Systems, Inc. Location service requests throttling
CN100450297C (zh) * 2005-07-25 2009-01-07 华为技术有限公司 一种基于安全的用户平面移动定位方法及系统
US8068056B2 (en) 2005-08-25 2011-11-29 Qualcomm Incorporated Location reporting with secure user plane location (SUPL)
CN100446625C (zh) * 2006-03-20 2008-12-24 华为技术有限公司 扩展的触发定位方法及装置
CN100584093C (zh) 2006-08-15 2010-01-20 华为技术有限公司 一种在移动通信系统中转移用户设备的方法及系统
US8050386B2 (en) 2007-02-12 2011-11-01 Telecommunication Systems, Inc. Mobile automatic location identification (ALI) for first responders
US8185087B2 (en) * 2007-09-17 2012-05-22 Telecommunication Systems, Inc. Emergency 911 data messaging
US9130963B2 (en) 2011-04-06 2015-09-08 Telecommunication Systems, Inc. Ancillary data support in session initiation protocol (SIP) messaging
DE602007014077D1 (de) * 2007-12-21 2011-06-01 Ericsson Telefon Ab L M Verfahren und Vorrichtung zur Bereitstellung differenzierter Dienste in einem Kommunikationsnetz
US9693184B2 (en) * 2008-08-18 2017-06-27 Qualcomm Incorporated Control plane location solution to support wireless access
CN101478718B (zh) * 2008-12-31 2011-05-11 中兴通讯股份有限公司 一种连续定位过程中提高定位系统性能的方法
US9307454B2 (en) 2009-02-09 2016-04-05 Qualcomm Incorporated Method and apparatus for maintaining location continuity for a UE following handover
US9125018B2 (en) * 2009-02-09 2015-09-01 Qualcomm Incorporated Triggered location services
US8942660B2 (en) * 2009-06-05 2015-01-27 Qualcomm Incorporated Method and apparatus for performing handover of an emergency call between wireless networks
US9743228B2 (en) * 2009-06-22 2017-08-22 Qualcomm Incorporated Transport of LCS-related messages for LTE access
CN107071895A (zh) * 2009-08-17 2017-08-18 中兴通讯股份有限公司 终止定位进程的方法与装置
US20110064046A1 (en) * 2009-09-11 2011-03-17 Yinjun Zhu User plane emergency location continuity for voice over internet protocol (VoIP)/IMS emergency services
CN102348280B (zh) * 2010-08-02 2016-05-25 中兴通讯股份有限公司 获取终端位置信息的方法、系统和设备
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
US11678291B2 (en) * 2016-08-21 2023-06-13 Qualcomm Incorporated Methods and systems for support of location for the Internet of Things
US11405863B2 (en) 2016-10-05 2022-08-02 Qualcomm Incorporated Systems and methods to enable combined periodic and triggered location of a mobile device
CN110505674B (zh) * 2018-05-18 2021-01-22 电信科学技术研究院有限公司 一种接入类型选择方法、设备及存储介质
US20230125710A1 (en) * 2020-05-04 2023-04-27 Qualcomm Incorporated Sidelink-assisted positioning

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9519087D0 (en) 1995-09-19 1995-11-22 Cursor Positioning Sys Ltd Navigation and tracking system
US6353743B1 (en) 1997-05-09 2002-03-05 Sony Corporation Positioning system using packet radio to determine position and to obtain information relative to a position
US6453237B1 (en) 1999-04-23 2002-09-17 Global Locate, Inc. Method and apparatus for locating and providing services to mobile devices
US6718177B1 (en) 1999-09-20 2004-04-06 Cellemetry, Llc System for communicating messages via a forward overhead control channel for a programmable logic control device
EP1094619A2 (fr) 1999-10-20 2001-04-25 Sony Corporation Dispositif de réception de signal pour un système GPS et un système de communication mobile
US6313787B1 (en) 1999-11-12 2001-11-06 Motorola, Inc. Method and apparatus for assisted GPS protocol
GB0000528D0 (en) 2000-01-11 2000-03-01 Nokia Networks Oy Location of a station in a telecommunications system
US6975941B1 (en) 2002-04-24 2005-12-13 Chung Lau Method and apparatus for intelligent acquisition of position information
JP3962530B2 (ja) 2000-06-06 2007-08-22 株式会社エヌ・ティ・ティ・ドコモ 位置情報取得方法及び位置情報システム並びに位置情報通知装置及び移動端末
EP1378137B9 (fr) 2001-04-10 2008-10-22 Telefonaktiebolaget LM Ericsson (publ) Procede destine a des comptes-rendus de position differes dans un reseau radio cellulaire
KR20030015577A (ko) 2001-08-16 2003-02-25 주식회사 엘지이아이 이동통신망을 이용한 지역 이탈 감시서비스 제공방법
EP1315389A1 (fr) * 2001-11-16 2003-05-28 Telefonaktiebolaget Lm Ericsson Procédé pour déterminer un récepteur pour des informations de localisation
DE60137088D1 (de) 2001-11-19 2009-01-29 Nokia Corp Bereitstellung von positionsinformationen
GB0128155D0 (en) 2001-11-23 2002-01-16 Nokia Corp Location request control
EP1466492B1 (fr) 2002-01-16 2011-11-09 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Systeme permettant d'ameliorer la manipulation des demandes differees de localisation de terminal d'utilisateur dans un systeme telephonique mobile
US7200380B2 (en) * 2002-03-28 2007-04-03 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US7321773B2 (en) 2002-03-28 2008-01-22 Telecommunication Systems, Inc. Area watcher for wireless network
JP3879615B2 (ja) 2002-07-25 2007-02-14 株式会社デンソー ナビゲーション方法、ナビゲーションシステム、ナビゲーション端末装置
GB0223498D0 (en) * 2002-10-09 2002-11-13 Nokia Corp Provision of information regarding a mobile station
WO2004057905A1 (fr) * 2002-12-11 2004-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Procede et systeme destines au positionnement dans un reseau de communications mobiles
US20040253964A1 (en) * 2003-06-12 2004-12-16 Yinjun Zhu Mobile based area event handling when currently visited network does not cover area
JP4135499B2 (ja) * 2002-12-27 2008-08-20 日本電気株式会社 移動通信システムにおける測位システム並びに測位方法
US20040137918A1 (en) * 2003-01-13 2004-07-15 Tomi Varonen Method and system for locating a mobile terminal
US8374631B2 (en) * 2003-01-15 2013-02-12 Nokia Corporation Provision of location information in a communication system
US7536695B2 (en) 2003-03-28 2009-05-19 Microsoft Corporation Architecture and system for location awareness
CN1268153C (zh) 2003-06-12 2006-08-02 华为技术有限公司 位置业务中目标用户设备上报位置报告的交互方法
CN1276682C (zh) 2003-06-25 2006-09-20 华为技术有限公司 一种向请求端提供目标用户设备位置信息的处理方法
CN1279780C (zh) 2003-06-26 2006-10-11 华为技术有限公司 一种区域变化类位置信息请求的处理方法
CN1276671C (zh) * 2003-07-04 2006-09-20 华为技术有限公司 位置业务中位置信息请求的处理方法
CN1279785C (zh) * 2003-10-10 2006-10-11 华为技术有限公司 一种目标用户设备私密性信息修改后的处理方法
WO2005051033A1 (fr) 2003-11-13 2005-06-02 Nokia Corporation Mecanisme a base ip pour des systemes, des procedes et des dispositifs de service de localisation
CN1277443C (zh) 2003-11-20 2006-09-27 华为技术有限公司 一种周期性位置信息请求的处理方法
US7424293B2 (en) * 2003-12-02 2008-09-09 Telecommunication Systems, Inc. User plane location based service using message tunneling to support roaming
US7660590B2 (en) 2003-12-23 2010-02-09 At&T Mobility Ii Llc Terminal-based server for location tracking
US7016693B2 (en) * 2004-01-06 2006-03-21 Nokia Corporation Method and apparatus for reporting location of a mobile terminal
ATE445975T1 (de) 2004-01-08 2009-10-15 Huawei Tech Co Ltd Abwicklung der positions-informationsanforderung, die von einem benutzergerät eingeleitet wird
FI20040036A0 (fi) 2004-01-13 2004-01-13 Nokia Corp Paikkainformaation tuottaminen vieraillussa verkossa
FI20040037A0 (fi) 2004-01-13 2004-01-13 Nokia Corp Paikkainformaation tuottaminen
SG135187A1 (en) 2004-02-05 2007-09-28 Qualcomm Inc Method and apparatus for performing position determination with a short circuit call flow
US7720461B2 (en) 2004-02-26 2010-05-18 Research In Motion Limited Mobile communications device with security features
KR101119295B1 (ko) 2004-04-21 2012-03-16 삼성전자주식회사 네트워크에 독립적으로 구성된 측위 서버를 이용한이동단말기의 위치결정장치 및 그 방법
US9723087B2 (en) 2004-08-03 2017-08-01 Lg Electronics Inc. User privacy management apparatus and method in mobile communications system
US7974639B2 (en) 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
US8099112B2 (en) 2005-04-18 2012-01-17 Nokia Corporation Network entity, method and computer program product for dynamically changing a request for location information
US9154907B2 (en) 2005-06-21 2015-10-06 Qualcomm Incorporated Efficient periodic location reporting in a radio access network
US8600410B2 (en) 2005-07-28 2013-12-03 Unwired Planet, Llc Wireless network with adaptive autonomous location push
EP1922826B1 (fr) 2005-08-11 2012-11-07 LG Electronics Inc. Procede de positionnement a base de zone dans un systeme de communications mobiles
KR100690877B1 (ko) 2005-08-11 2007-03-09 엘지전자 주식회사 이동통신 시스템에서의 주기적인 위치추적 방법
US8068056B2 (en) 2005-08-25 2011-11-29 Qualcomm Incorporated Location reporting with secure user plane location (SUPL)

Also Published As

Publication number Publication date
US20070004429A1 (en) 2007-01-04
CN101278574A (zh) 2008-10-01
CN101278574B (zh) 2012-10-10
EP1894430A1 (fr) 2008-03-05
US8792902B2 (en) 2014-07-29
CA2612992A1 (fr) 2007-01-04
WO2007002333A1 (fr) 2007-01-04

Similar Documents

Publication Publication Date Title
EP1894430B1 (fr) Procede et appareil pour la fourniture de services de localisation avec des flux de messages reduits
US9549289B2 (en) Efficient periodic location reporting in a radio access network
US8929919B2 (en) Method and apparatus for performing position determination with a short circuit call flow
US8874134B2 (en) Location reporting with secure user plane location (SUPL)
US7421277B2 (en) Method and apparatus for performing position determination with a short circuit call flow
US8185128B2 (en) Method and apparatus for supporting location services with roaming
RU2384021C2 (ru) Эффективная периодическая передача отчетов о местоположении в сети радиодоступа

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080111

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20080606

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006036202

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04Q0007240000

Ipc: H04W0008080000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 8/08 20090101AFI20110525BHEP

RTI1 Title (correction)

Free format text: METHOD AND APPARATUS FOR PROVIDING LOCATION SERVICES WITH SHORTENED MESSAGE FLOWS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 611583

Country of ref document: AT

Kind code of ref document: T

Effective date: 20130515

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006036202

Country of ref document: DE

Effective date: 20130704

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 611583

Country of ref document: AT

Kind code of ref document: T

Effective date: 20130508

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20130508

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130908

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130909

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130819

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130809

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130808

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20140228

26N No opposition filed

Effective date: 20140211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130630

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130630

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130621

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006036202

Country of ref document: DE

Effective date: 20140211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130508

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130621

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20060621

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230320

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230510

Year of fee payment: 18