# US 2022/0022115 A1 · Systems and methods for deferred 5g location of a mobile device using a combined amf and lmf based location solution > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2022/0022115 A1 - Document ID: US20220022115A1 - Status: Published application - Kind: A1 - Application number: 17/490,882 - Filed: 2021-09-30 - Published: 2022-01-20 - Earliest claimed: 2018-09-14 - Assignees: QUALCOMM Incorporated - Applicants: QUALCOMM Incorporated - Inventors: Stephen William EDGE - Web page: https://patentgrep.com/patent/US20220022115A1 ## CPC - H04W 36/08: Reselecting an access point - H04W 64/00: Locating users or terminals {or network equipment} for network management purposes, e.g. mobility management - H04W 4/029: Location-based management or tracking services - H04W 8/08: Mobility data transfer - H04W 8/12: between location registers or mobility servers - H04W 36/322: {by location data} - H04W 76/25: Maintenance of established connections - H04W 60/04: using triggered events - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Methods and techniques are described for efficiently supporting periodic and triggered location services for a user equipment (UE) in a Fifth Generation wireless network. A serving core network (CN) node, such as an AMF, receives a request for periodic or triggered location for the UE from another CN entity, such as a GMLC, and transfers the request to a location server, such as an LMF, which initiates and establishes the periodic and triggered location session with the UE. The serving CN node then releases all resources for the location request. The UE monitors for periodic or trigger events and reports each event to a location server which forwards an event report, optionally containing a UE location, to an external client via a CN entity, such as GMLC. The event reporting can be efficient because a serving CN node is not materially involved. ## Claims ### Claim 1 A method for supporting location services for a user equipment (UE) performed by a first location server in a wireless network, the method comprising: receiving a request for a periodic or triggered location for the UE from a first core network (CN) node in the wireless network, wherein the first CN node received the request for the periodic or triggered location for the UE from a different entity; sending the request for the periodic or triggered location to the UE; receiving a confirmation from the UE that the periodic or triggered location was activated in the UE; and sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 2 (depends on 1) The method of claim 1, further comprising: retaining information for the request for the periodic or triggered location after sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE; receiving a plurality of periodic or triggered location event reports from the UE, wherein each of the plurality of periodic or triggered location event reports comprises at least one of location measurements, a location estimate, a type of detected triggering event, or a combination thereof; and sending a plurality of corresponding periodic or triggered location event reports to the different entity. ### Claim 3 (depends on 2) The method of claim 2, further comprising including an indication of sending location event reports to the first location server in the request for the periodic or triggered location sent to the UE. ### Claim 4 (depends on 2) The method of claim 2, further comprising: receiving a periodic or triggered location event report from the UE via a second CN node; sending a location context to a second location server, wherein the location context comprises the periodic or triggered location event report and information for the request for the periodic or triggered location for the UE received from the first CN node; and discarding information and releasing resources for the request for the periodic or triggered location after sending the location context to the second location server. ### Claim 5 (depends on 4) The method of claim 4, further comprising determining the second location server. ### Claim 6 (depends on 4) The method of claim 4, wherein the second location server is more suitable for the periodic or triggered location event report than the first location server. ### Claim 7 (depends on 4) The method of claim 4, wherein the second CN node comprises the first CN node. ### Claim 8 (depends on 1) The method of claim 1, further comprising discarding information and releasing resources for the request for the periodic or triggered location after sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 9 (depends on 8) The method of claim 8, further comprising including an indication of sending location event reports to any location server in the request for the periodic or triggered location sent to the UE. ### Claim 10 (depends on 1) The method of claim 1, further comprising: determining a location of the UE in response to receiving the request for the periodic or triggered location for the UE from the first CN node; and including the location in the confirmation sent to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 11 (depends on 2) The method of claim 2, further comprising: determining a location of the UE in response to receiving a periodic or triggered location event report from the UE; and including the location in a corresponding periodic or triggered location event report sent to the different entity. ### Claim 12 (depends on 2) The method of claim 2, wherein the plurality of periodic or triggered location event reports are received from the UE via a second CN node. ### Claim 13 (depends on 12) The method of claim 12, wherein the second CN node is different to the first CN node. ### Claim 14 (depends on 1) The method of claim 1, wherein the first CN node, the first location server and the different entity are part of a Fifth Generation Core network (5GCN). ### Claim 15 (depends on 14) The method of claim 14, wherein the first CN node is an Access and Mobility Management Function (AMF), the first location server is a Location Management Function (LMF) and the different entity is a Gateway Mobile Location Center (GMLC). ### Claim 16 A first location server in a wireless network 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 at least one processor coupled to the external interface and the at least one memory, the at least one processor configured to: receive a request for a periodic or triggered location for the UE from a first core network (CN) node in the wireless network, wherein the first CN node received the request for the periodic or triggered location for the UE from a different entity; send the request for the periodic or triggered location to the UE; receive a confirmation from the UE that the periodic or triggered location was activated in the UE; and send the confirmation to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 17 (depends on 16) The first location server of claim 16, wherein the at least one processor is further configured to: retain information for the request for the periodic or triggered location after sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE; receive a plurality of periodic or triggered location event reports from the UE, wherein each of the plurality of periodic or triggered location event reports comprises at least one of location measurements, a location estimate, a type of detected triggering event, or a combination thereof; and send a plurality of corresponding periodic or triggered location event reports to the different entity. ### Claim 18 (depends on 17) The first location server of claim 17, wherein the at least one processor is further configured to include an indication of sending location event reports to the first location server in the request for the periodic or triggered location sent to the UE. ### Claim 19 (depends on 17) The first location server of claim 17, wherein the at least one processor is further configured to: receive a periodic or triggered location event report from the UE via a second CN node; send a location context to a second location server, wherein the location context comprises the periodic or triggered location event report and information for the request for the periodic or triggered location for the UE received from the first CN node; and discard information and releasing resources for the request for the periodic or triggered location after sending the location context to the second location server. ### Claim 20 (depends on 19) The first location server of claim 19, wherein the at least one processor is further configured to determine the second location server. ### Claim 21 (depends on 19) The first location server of claim 19, wherein the second location server is more suitable for the periodic or triggered location event report than the first location server. ### Claim 22 (depends on 19) The first location server of claim 19, wherein the second CN node comprises the first CN node. ### Claim 23 (depends on 16) The first location server of claim 16, wherein the at least one processor is further configured to discard information and release resources for the request for the periodic or triggered location after sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 24 (depends on 23) The first location server of claim 23, wherein the at least one processor is further configured to include an indication of sending location event reports to any location server in the request for the periodic or triggered location sent to the UE. ### Claim 25 (depends on 16) The first location server of claim 16, wherein the at least one processor is further configured to: determine a location of the UE in response to receiving the request for the periodic or triggered location for the UE from the first CN node; and include the location in the confirmation sent to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 26 (depends on 17) The first location server of claim 17, wherein the at least one processor is further configured to: determine a location of the UE in response to receiving a periodic or triggered location event report from the UE; and include the location in a corresponding periodic or triggered location event report sent to the different entity. ### Claim 27 (depends on 17) The first location server of claim 17, wherein the plurality of periodic or triggered location event reports are received from the UE via a second CN node. ### Claim 28 (depends on 27) The first location server of claim 27, wherein the second CN node is different to the first CN node. ### Claim 29 (depends on 16) The first location server of claim 16, wherein the first CN node, the first location server and the different entity are part of a Fifth Generation Core network (5GCN). ### Claim 30 (depends on 29) The first location server of claim 29, wherein the first CN node is an Access and Mobility Management Function (AMF), the first location server is a Location Management Function (LMF) and the different entity is a Gateway Mobile Location Center (GMLC). ### Claim 31 A first location server in a wireless network for supporting location services for a user equipment (UE) comprising: means for receiving a request for a periodic or triggered location for the UE from a first core network (CN) node in the wireless network, wherein the first CN node received the request for the periodic or triggered location for the UE from a different entity; means for sending the request for the periodic or triggered location to the UE; means for receiving a confirmation from the UE that the periodic or triggered location was activated in the UE; and means for sending the confirmation to the first CN node that the periodic or triggered location was activated in the UE. ### Claim 32 A non-transitory storage medium including program code stored thereon, the program code is operable to cause at least one processor in a first location server in a wireless network to support location services for a user equipment (UE) comprising: program code to receive a request for a periodic or triggered location for the UE from a first core network (CN) node in the wireless network, wherein the first CN node received the request for the periodic or triggered location for the UE from a different entity; program code to send the request for the periodic or triggered location to the UE; program code to receive a confirmation from the UE that the periodic or triggered location was activated in the UE; and program code to send the confirmation to the first CN node that the periodic or triggered location was activated in the UE.