IP Library Granted Patent US 12,256,319
Granted Patent B2
US 12,256,319 · App. 17/829,674 · Granted Mar 18, 2025

Methods and systems for supporting unified location of a mobile device in a 5G network

Inventors: Stephen William Edge (Escondido, CA); Haris Zisimopoulos (London, GB); Hong Cheng (Basking Ridge, NJ)
Assignee: QUALCOMM Incorporated
H04W48/16G01S5/0263G01S19/48H04W4/029H04W8/12H04W24/10H04W64/003H04W84/042
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,256,319
App. No.
17/829,674
Filed
Jun 1, 2022
Granted
Mar 18, 2025
Kind
B2
Art Unit
2412
USPC
370/329
Abstract

Location services for a user equipment (UE) are supported with a Network Exposure Function (NEF) serving as a focal point for any location request. An entity that needs the location of the UE sends a location request to the NEF in the home PLMN or Visited PLMN for the UE. The location request includes, e.g., a type of location request, a required location accuracy, a required response time or some combination of these. The NEF determines whether to use a Gateway Mobile Location Center (GMLC) or a serving Access and Mobility Management Function (AMF) for the UE to obtain the UE location based on the content of the location request and sends the location request to the GMLC or serving AMF accordingly. Additionally, if the serving AMF is used, a serving base station may obtain the UE location and send the UE location to the serving AMF.

Claims (62)

1. A method for supporting location services for a user equipment (UE) performed by a Gateway Mobile Location Center (GMLC), the method comprising:

receiving from a Network Exposure Function (NEF) a location request for the UE, wherein the NEF received the location request from a second entity and the NEF is in a Public Land Mobile Network (PLMN) that is a Home PLMN (HPLMN) for the UE or a Visited PLMN (VPLMN) for the UE, the location request including a type of location request, a required location accuracy, a required location response time or some combination of these, wherein the NEF determines either the GMLC or a serving Access and Mobility Management Function (AMF) for the UE to obtain a UE location, wherein the NEF selects the GMLC based on: the type of location request, the required location accuracy, or the required location response time, or a combination thereof;

sending the location request to a Location Management Function (LMF via the serving AMF for the UE;

receiving the UE location or a confirmation of the location request from the LMF, wherein the LMF obtains the UE location by obtaining location measurements or a location estimate from at least one of the UE using a Long Term Evolution (LTE) Positioning Protocol (LPP) or a serving RAN for the UE using a New Radio (NR) Positioning Protocol A (NRPPa); and

sending the UE location or the confirmation of the location request to the NEF.

2. The method of claim 1 , wherein the second entity is an external client, an Application Function (AF) outside the PLMN or a Network Function (NF) inside the PLMN.

3. A Gateway Mobile Location Center (GMLC) for supporting location services for a user equipment (UE) comprising:

an external interface for receiving and sending messages to entities in a network;

at least one memory; and

one or more processors coupled to the external interface, the at least one the memory, the one or more processors configured to:

receive via the external interface from a Network Exposure Function (NEF) a location request for the UE, wherein the NEF received the location request from a second entity and the NEF is in a Public Land Mobile Network (PLMN) that is a Home PLMN (HPLMN) for the UE or a Visited PLMN (VPLMN) for the UE, the location request including a type of location request, a required location accuracy, a required location response time or some combination of these, wherein the NEF determined either the GMLC or a serving Access and Mobility Management Function (AMF) to obtain a UE location, wherein the NEF selects the GMLC based on: the type of location request, the required location accuracy, or the required location response time, or a combination thereof;

send via the external interface the location request to a Location Management Function (LMF) via the serving AMF for the UE;

receive via the external interface the UE location or a confirmation of the location request from the LMF, wherein the LMF obtains the UE location by obtaining location measurements or a location estimate from at least one of the UE using a Long Term Evolution (LTE) Positioning Protocol (LPP) or a serving RAN for the UE using a New Radio (NR) Positioning Protocol A (NRPPa); and

send via the external interface the UE location or the confirmation of the location request to the NEF.

4. The GMLC of claim 3 , wherein the second entity is an external client, an Application Function (AF) outside the PLMN or a Network Function (NF) inside the PLMN.

5. The GMLC of claim 3 , wherein the type of location request comprises a request for periodic or triggered locations of the UE and the one or more processors is further configured to:

receive via the external interface a plurality of additional location reports from the location server, each location report in the plurality of location reports comprising an indication of a trigger event, a location for the UE or both; and

send via the external interface, for each location report, the trigger event, the location or both to the NEF.

6. A method for supporting location services for a user equipment (UE) performed by a serving Access and Mobility Management Function (AMF) for the UE, the method comprising:

receiving from a Network Exposure Function (NEF) a location request for the UE, wherein the NEF receives the location request from a second entity and wherein the NEF is in a Public Land Mobile Network (PLMN) that is a Home PLMN (HPLMN) for the UE or a Visited PLMN (VPLMN) for the UE, the location request including a type of location request, a required location accuracy, a required location response time or some combination of these, wherein the NEF determines either a Gateway Mobile Location Center (GMLC) or the serving AMF for the UE to obtain a UE location, wherein the serving AMF obtains the UE location based on a serving Radio Access Network (RAN) for the UE, wherein the NEF selects the serving AMF based on: the type of location request, the required location accuracy, the required location response time, or a combination thereof;

sending the location request to the serving RAN for the UE;

receiving the UE location or a confirmation of the location request from the serving RAN; and

sending the UE location or the confirmation of the location request to the NEF,

wherein the serving AMF uses a Next Generation Application Protocol (NGAP) to obtain the UE location from the serving RAN.

7. The method of claim 6 , wherein the second entity is an external client, an Application Function (AF) outside the PLMN or a Network Function (NF) inside the PLMN.

8. The method of claim 6 , wherein the serving RAN obtains the UE location based on a current or previous serving cell or a tracking area (TA) for the UE.

9. The method of claim 6 , wherein the serving RAN obtains the UE location based on a serving base station for the UE in the serving RAN, wherein the serving base station obtains the UE location by obtaining location measurements comprising:

location measurements of signals transmitted by the UE;

location measurements obtained by other base stations in the serving RAN of signals transmitted by the UE;

location measurements obtained by the UE of signals transmitted by the serving base station;

location measurements obtained by the UE of signals transmitted by other base stations in the serving RAN;

or some combination thereof.

10. The method of claim 9 , wherein the serving base station is a New Radio (NR) Node B (gNB) or a Next Generation (NG) evolved NodeB (ng-eNB).

11. The method of claim 9 , wherein the serving base station determines the UE location from the obtained location measurements using at least one of Observed Time Difference Of Arrival (OTDOA), round trip signal propagation time (RTT), angle of departure (AOD), angle of arrival (AOA), enhanced cell ID (ECID), Assisted Global Navigation Satellite System (A-GNSS) or Real Time Kinematic (RTK).

12. The method of claim 6 , wherein receiving the location request from the NEF comprises receiving an AMF Event Exposure Subscribe service operation invoked by the NEF towards the serving AMF to request information on the location of the UE.

13. The method of claim 12 , wherein either the serving AMF address is obtained by the NEF querying a Unified Data Management (UDM) in the HPLMN for the UE or the AMF Event Exposure Subscribe service operation invoked by the NEF towards the serving AMF is received via the UDM for the UE.

14. The method of claim 6 , wherein the type of location request comprises a request for periodic or triggered location of the UE and further comprising:

receiving a plurality of additional location reports from the serving RAN, each location report in the plurality of additional location reports comprising an indication of a trigger event, a location for the UE or both; and

sending, for each location report, the trigger event, the location or both to the NEF.

15. A serving Access and Mobility Management Function (AMF) for a user equipment (UE) for supporting location services for the UE, the serving AMF comprising:

an external interface for receiving and sending messages to entities in a network;

at least one memory; and

one or more processors coupled to the external interface and the at least one memory, the one or more processors configured to:

receive via the external interface from a Network Exposure Function (NEF) a location request for a UE, wherein the NEF receives the location request from a second entity and wherein the NEF is in a Public Land Mobile Network (PLMN) that is a Home PLMN (HPLMN) for the UE or a Visited PLMN (VPLMN) for the UE, the location request including a type of location request, a required location accuracy, a required location response time or some combination of these, wherein the NEF determines either a Gateway Mobile Location Center (GMLC) or the serving AMF for the UE to obtain a UE location, wherein the serving AMF obtains the UE location based on a serving Radio Access Network (RAN) for the UE, wherein the NEF selects the serving AMF based on: the type of location request, the required location accuracy, the required location response time, or a combination thereof;

send via the external interface the location request to the serving RAN for the UE;

receive via the external interface the UE location or a confirmation of the location request from the serving RAN; and

send via the external interface the UE location or the confirmation of the location request to the NEF, wherein the serving AMF uses a Next Generation Application Protocol (NGAP) to obtain the UE location from the serving RAN.

16. The serving AMF of claim 15 , wherein the second entity is an external client, an Application Function (AF) outside the PLMN or a Network Function (NF) inside the PLMN.

17. The serving AMF of claim 15 , wherein the serving RAN obtains the UE location based on a current or previous serving cell or a tracking area (TA) for the UE.

18. The serving AMF of claim 15 , wherein the serving RAN obtains the UE location based on a serving base station for the UE in the serving RAN, wherein the serving base station obtains the UE location by obtaining location measurements comprising:

location measurements of signals transmitted by the UE;

location measurements obtained by other base stations in the serving RAN of signals transmitted by the UE;

location measurements obtained by the UE of signals transmitted by the serving base station;

location measurements obtained by the UE of signals transmitted by other base stations in the serving RAN;

or some combination thereof.

19. The serving AMF of claim 18 , wherein the serving base station is a New Radio (NR) Node B (gNB) or a Next Generation (NG) evolved NodeB (ng-eNB).

20. The serving AMF of claim 18 , wherein the serving base station determines the UE location from the obtained location measurements using at least one of Observed Time Difference Of Arrival (OTDOA), round trip signal propagation time (RTT), angle of departure (AOD), angle of arrival (AOA), enhanced cell ID (ECID), Assisted Global Navigation Satellite System (A-GNSS) or Real Time Kinematic (RTK).

21. The serving AMF of claim 15 , wherein the one or more processors is configured to receive the location request from the NEF by being configured to receive an AMF Event Exposure Subscribe service operation invoked by the NEF towards the serving AMF to request information on the location of the UE.

22. The serving AMF of claim 21 , wherein either the serving AMF address is obtained by the NEF querying a Unified Data Management (UDM) in the HPLMN for the UE or the AMF Event Exposure Subscribe service operation invoked by the NEF towards the serving AMF is received via the UDM for the UE.

23. The serving AMF of claim 15 , wherein the type of location request comprises a request for periodic or triggered locations of the UE and the one or more processors is further configured to:

receive via the external interface a plurality of additional location reports from the serving RAN, each location report in the plurality of additional location reports comprising an indication of a trigger event, a location for the UE or both; and

send via the external interface, for each location report, the trigger event, the location or both to the NEF.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 1, 2022
From: EDGE, STEPHEN WILLIAM; ZISIMOPOULOS, HARIS; CHENG, HONG
To: QUALCOMM INCORPORATED
Reel/Frame 060246/0772 →
Continuity (4)
Continuation 16537552 · Aug 10, 2019
Provisional Application 62807222 · Feb 18, 2019
Provisional Application 62718366 · Aug 13, 2018
Related Publication 20220295388A1 · Sep 15, 2022
References Cited (88)
US 6225944B1 · Hayes · 2001 [cited by applicant]
US 8477811B2 · Kitazoe · 2013 [cited by applicant]
US 8588870B1 · Vargantwar · 2013 [cited by applicant]
US 8593956B2 · Tiwari · 2013 [cited by applicant]
US 8712439B2 · Farmer et al. · 2014 [cited by applicant]
US 8942102B2 · Edge et al. · 2015 [cited by applicant]
US 9781259B1 · Kodaypak · 2017 [cited by examiner]
US 9998856B2 · Edge · 2018 [cited by applicant]
US 10080098B1 · Edge · 2018 [cited by applicant]
US 10506543B1 · Edge et al. · 2019 [cited by applicant]
US 10952178B2 · Edge et al. · 2021 [cited by applicant]
US 10959203B2 · Edge et al. · 2021 [cited by applicant]
US 11218933B2 · Edge · 2022 [cited by applicant]
US 20060099961A1 · Duan · 2006 [cited by applicant]
US 20060293066A1 · Edge et al. · 2006 [cited by applicant]
US 20080200182A1 · Shim · 2008 [cited by applicant]
US 20120149325A1 · Titus et al. · 2012 [cited by applicant]
US 20140192737A1 · Belghoul et al. · 2014 [cited by applicant]
US 20150189616A1 · Janakiraman et al. · 2015 [cited by applicant]
US 20160165508A1 · Jin · 2016 [cited by applicant]
US 20180020423A1 · Wang et al. · 2018 [cited by applicant]
US 20180054795A1 · Edge · 2018 [cited by applicant]
US 20180199160A1 · Edge · 2018 [cited by applicant]
US 20180199306A1 · Edge et al. · 2018 [cited by applicant]
US 20180249283A1 · Jiang et al. · 2018 [cited by applicant]
US 20180262868A1 · Edge · 2018 [cited by applicant]
US 20190116483A1 · Ryu et al. · 2019 [cited by applicant]
US 20190182665A1 · Edge · 2019 [cited by applicant]
US 20190357129A1 · Park et al. · 2019 [cited by applicant]
US 20200053638A1 · Edge et al. · 2020 [cited by applicant]
US 20200236644A1 · Gunnarsson et al. · 2020 [cited by applicant]
US 20200367022A1 · Tenny et al. · 2020 [cited by applicant]
US 20210227454A1 · Hou · 2021 [cited by examiner]
US 20220022115A1 · Edge · 2022 [cited by applicant]
CN 101455096A · 2009 [cited by applicant]
CN 102754518 · 2015 [cited by applicant]
CN 103154765 · 2015 [cited by applicant]
EP 1109334A2 · 2001 [cited by applicant]
EP 2790377A1 · 2014 [cited by applicant]
TW 201808043A · 2018 [cited by applicant]
TW 201831011A · 2018 [cited by applicant]
WO 2009089486A1 · 2009 [cited by applicant]
WO WO2009097602 · 2009 [cited by applicant]
WO WO2010071518A1 · 2010 [cited by applicant]
WO WO2011142715A1 · 2011 [cited by applicant]
WO 2012060933 · 2012 [cited by applicant]
WO WO2017078485A1 · 2017 [cited by applicant]
WO WO2017196510A1 · 2017 [cited by applicant]
WO WO2018038798A1 · 2018 [cited by applicant]
WO WO2018085017A1 · 2018 [cited by applicant]
WO WO2018093168 · 2018 [cited by applicant]
WO WO2018129337A1 · 2018 [cited by applicant]
WO WO2018143870 · 2018 [cited by applicant]
Taiwan Search Report—108128654—TIPO—Sep. 6, 2022. [cited by applicant]
Taiwan Search Report—TW109120148—TIPO—Oct. 30, 2023. [cited by applicant]
Ericsson: “Location Service, Alignment Procedures and NF Services”, S2-187768, 3GPP TSG-SA2 Meeting 128-bis, Sophia Antipolis, France, Aug. 20-25, 2018, 9 Pages. [cited by applicant]
Taiwan Search Report—TW108128654—TIPO—Apr. 14, 2023. [cited by applicant]
3GPP TR 23.731: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancement to the 5GC Location Services (Release 16)”, 3GPP Standard; Technical Report; 3GPP TR 2… [cited by applicant]
3GPP TS 23.271, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional Stage 2 Description of LCS (Release 4)”, 3GPP TS 23.271, V4.0.0, Jan. 2001, pp. 1-58, 3GPP Tsg_s… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional Stage 2 Description of Location Services (LCS) (Release 15)”, 3GPP Standard; Technical Specification; 3GPP TS 23… [cited by applicant]
ETSI TS 123 502: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)”, V15.2.0, 3GPP TS 23.502 V15.2.0, Jun. 2018, 311 Pages. [cited by applicant]
European Search Report—EP21193646—Search Authority—Munich—Dec. 10, 2021. [cited by applicant]
Huawei., et al., “Update of Solution 4 “Positioning Operations Considering Different LMF Deployment Scenarios””, S2-185737, SA WG2 Meeting #127bis, May 28-Jun. 1, 2018 Newport Beach, California, USA, (revision of S2-185… [cited by applicant]
Huawei, “Introduction of EDT for eMTC and NB-IoI Enhancements in TS 36.300”, R2-1807880, 3GPP TSG-RAN2 Meeting #102, Busan, Korea, May 21-25, 2018, 12 Pages. [cited by applicant]
Huawei, et al., “Introduction of Early Data Transmission”, 3GPP Draft; 36413_CR1578R4_(REL-15)_R3-183469, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-An… [cited by applicant]
International Search Report and Written Opinion—PCT/US2019/046109—ISA/EPO—Oct. 17, 2019. [cited by applicant]
International Search Report and Written Opinion—PCT/US2020/037034—ISA/EPO—Aug. 28, 2020. [cited by applicant]
International Preliminary Report on Patentability—PCT/US2019/046109 The International Bureau of WIPO—Geneva, Switzerland, Feb. 25, 2021. [cited by applicant]
International Preliminary Report on Patentability—PCT/US2019/051034 The International Bureau of WIPO—Geneva, Switzerland, Mar. 25, 2021. [cited by applicant]
International Preliminary Report on Patentability—PCT/US2019/035225, the International Bureau of WIPO—Geneva, Switzerland, Jan. 7, 2021. [cited by applicant]
International Search Report and Written Opinion—PCT/US2019/035225—ISA/EPO—Sep. 13, 2019. [cited by applicant]
International Search Report and Written Opinion—PCT/US2019/051034—ISA/EPO—Nov. 20, 2019. [cited by applicant]
LG Electronics Inc: “Indication of EDT Support”, R2-1713758, 3GPP TSG-RAN WG2 Meeting #100, (R2-171xxxx), Reno, USA, Nov. 27-Dec. 1, 2017, 2 Pages. [cited by applicant]
Qualcomm Incorporated., et al., “Release Assistance Handling”, S2-185757, SA WG2 Meeting #127bis, May 28-Jun. 1, 2018, Newport Beach, United States, pp. 1-13. [cited by applicant]
Qualcomm Incorporated: “Introducing Early Data Transmission for Control Plane CIoT EPS Optimization”, S2-185153, 3GPP TSG-SA2 Meeting #127bis, Newport Beach, USA, May 28-Jun. 1, 2018, 7 Pages. [cited by applicant]
Qualcomm Incorporated: “Low Power Periodic and Triggered Location for the LMF Based Solution”, 3GPP Draft, S2-183966, WAS S2-183623 (P-CR For TR 23.731 For Low Power Triggered Location for the LMF Based Solution), 3rd G… [cited by applicant]
Qualcomm Incorporated: “Location Reporting Using Control Plane CIOT EPS Optimisation”, 3GPP Draft, 23271 CR0424R2 CIOT EXT (REL-14), S2-170513 (CR 23.271—Location Reporting Using CP)-R6, 3rd Generation Partnership Proje… [cited by applicant]
Qualcomm Incorporated: “Addition of an LMF Based Location Solution”, 3GPP Draft, SA WG2 Meeting #126, S2-182300 (P-CR For TR 23.731 For LMF Based Location Solution)-R3, 3rd Generation Partnership Project (3GPP), Mobile … [cited by applicant]
Qualcomm Incorporated: “Core Network Impacts from EDT”, S2-178485, SA WG2 Meeting #124, Nov. 27-Dec. 1, 2017, Reno, NV, USA, 5 Pages. [cited by applicant]
Qualcomm Incorporated: “Enhancements to Solution 2,” 3GPP Draft; S2-187097 WAS 7012 WAS 6649 (9-CR for TR 23.731 for Enhancements to Solution 2)-R1, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 6… [cited by applicant]
Qualcomm Incorporated, et al., “Deferred 5GC-MT-LR Procedure for Solution 14”, SA WG2 Meeting #129, 3GPP Draft; S2-1810463 P-CR for TR 23.731 for AMF and LMF Deferred Location Solution-R7, 3rd Generation Partnership Pro… [cited by applicant]
Qualcomm Incorporated: “Solution for Key Issue 13: UE Location Information Exposure,” 3GPP Draft; S2-188064_ENA_UE Location Information Exposure, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650,… [cited by applicant]
Qualcomm Incorporated: “Unified Solution for Location Service Exposure,” 3GPP Draft; S2-188083 (P-CR for TR 23.731 for Unified Solution for Location Service Exposure)-R2, 3rd Generation Partnership Project (3GPP), Mobil… [cited by applicant]
Qualcomm Incorporated: “Support for Key Issue on Coexistence with the Location Solution in Release 15”, SA WG2 Meeting #128, 3GPP Draft; S2-186651 (P-CR for TR 23.731 for Support For Key Issue on Coexistence With Rel-15… [cited by applicant]
Vivo., et al., “Solution5 Update: Privacy Check Procedure W.R.T. LMF Based Architecture”, S2-183951, SA WG2 Meeting #127, Apr. 16-20, 2018, Sanya, China, pp. 1-3. [cited by applicant]
Huawei, et al., “LR Handling Based on the Various Priorities”, 3GPP TSG-SA WG2 Meeting #133, S2-1906800, May 13-May 17, 2019, Reno, NV, USA, May 24, 2019, pp. 1-6. [cited by applicant]
Qualcomm Incorporated: “Correction of Routing Identifier for NAS Transfer of LPP Messages”, SA WG2 Meeting #133, S2-1905429, May 13-17, 2019, Reno, Nevada, USA, May 7, 2019, pp. 1-8. [cited by applicant]
Qualcomm Incorporated: “Mobility of Periodic or Triggered Location Between 5GS and EPS”, SA WG2 Meeting #133, S2-1906466, May 13-17, 2019, Reno, Nevada, USA, May 16, 2019, pp. 1-9. [cited by applicant]