WO2024077459A1

WO2024077459A1 - Method, apparatus and computer program

Info

Publication number: WO2024077459A1
Application number: PCT/CN2022/124467
Authority: WO
Inventors: Mao Cai; Rajesh Babu NATARAJAN
Original assignee: Nokia Shanghai Bell Co., Ltd.; Nokia Solutions And Networks Oy
Priority date: 2022-10-10
Filing date: 2022-10-10
Publication date: 2024-04-18

Abstract

There is provided an apparatus comprising means for: receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

Description

METHOD, APPARATUS AND COMPUTER PROGRAM

FIELD

The present application relates to a method, apparatus, system and computer program and in particular but not exclusively to determining and reporting a location of a target user equipment.

BACKGROUND

A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email) , text message, multimedia and/or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

In a wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems comprise public land mobile networks (PLMN) , satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN) . Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.

A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and/or receive communications on the carrier.

The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio) . Other examples of communication systems are the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP) .

SUMMARY

According to an aspect, there is provided a first network device comprising means for: receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

The one or more trigger conditions may comprise one or more of: a network mobility event associated with the target user equipment occurs; a determined movement of the user equipment is more than a threshold amount; a time duration has passed since a previous response was sent.

The one or more location accuracy requirements may comprise at least a first accuracy requirement and a second accuracy requirement, wherein the second accuracy requirement is more precise than the first accuracy requirement.

Each of the one or more responses may comprise one of: the information identifying the determined location of the target user equipment and an indication that a response is an intermediate response; or the information identifying the determined location of the target user equipment and an indication that a response is a final response.

The first network device may comprise one of: gateway mobile location centre, a location retrieval function, or a network exposure function. The client device may comprise one of: an external client, public safety answering point, an application function, or a network exposure function. The second network device may comprise an access and mobility management function or an access node.

According to an aspect, there is provided a second network device comprising means for: receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

The first network device may comprise one of: gateway mobile location centre, a location retrieval function, or a network exposure function. The second network device may comprise an access and mobility management function or an access node. The third network device may comprise a location management function.

According to an aspect, there is provided a third network device comprising means for: receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

Determining the location of the target user equipment may comprise selecting a positioning method based on the one or more location accuracy requirements.

The one or more trigger conditions may comprise one or more of: a network mobility event associated with the target user equipment occurs; a determined movement of the user equipment is more than a threshold amount; or a time duration has passed since a previous response was sent.

The one or more trigger conditions may comprise a time duration, and the third network device may comprise means for: determining that movement of the user equipment is greater than a threshold amount and reducing the time duration; or determining that movement of the user equipment is less than a threshold amount and increasing the time duration.

Determining the location of the target user equipment may comprise: determining the location of the target user equipment based on the first accuracy requirement; and sending, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is an intermediate response.

Determining the location of the target user equipment may comprise: determining the location of the target user equipment based on the second accuracy requirement; and sending, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is a final response.

The second network device may comprise an access and mobility management function or an access node. The third network device may comprise a location management function.

According to an aspect, there is provided a first network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to: receive, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, send, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receive, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and send, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a second network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to: receive, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, send, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receive, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and send, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a third network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the third network device at least to: receive, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determine the location of the target user equipment based on the one or more location accuracy requirements; and send, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

The at least one processor and at least one memory may cause the third network device to select a positioning method based on the one or more location accuracy requirements.

The one or more trigger conditions may comprise a time duration, and the at least one processor and at least one memory may cause the third network device to: determine that movement of the user equipment is greater than a threshold amount and reduce the time duration; or determine that movement of the user equipment is less than a threshold amount and increase the time duration.

The at least one processor and at least one memory may cause the third network device to: determine the location of the target user equipment based on the first accuracy requirement; and send, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is an intermediate response.

The at least one processor and at least one memory may cause the third network device to: determine the location of the target user equipment based on the second accuracy requirement; and send, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is a final response.

According to an aspect, there is provided a method performed by a first network device, the method comprising: receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a method performed by a second network device, the method comprising: receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a method performed by a third network device, the method comprising: receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

The one or more trigger conditions may comprise a time duration, and the method may comprise: determining that movement of the user equipment is greater than a threshold amount and reducing the time duration; or determining that movement of the user equipment is less than a threshold amount and increasing the time duration.

According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by a first network device, cause the first network device to perform at least the following: receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by a second network device, cause the second network device to perform at least the following: receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by a third network device, cause the third network device to perform at least the following: receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

The one or more trigger conditions may comprise a time duration, and the computer readable medium may comprise instructions which, when executed by the third network device, cause the third network device to perform: determining that movement of the user equipment is greater than a threshold amount and reducing the time duration; or determining that movement of the user equipment is less than a threshold amount and increasing the time duration.

According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method according to any of the preceding aspects.

In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.

DESCRIPTION OF FIGURES

Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

Figure 1 shows a representation of a network system according to some example embodiments;

Figure 2 shows a representation of a control apparatus according to some example embodiments;

Figure 3 shows a representation of an apparatus according to some example embodiments;

Figure 4 shows methods according to some examples;

Figure 5 shows a procedure according to some examples;

Figure 6 shows a procedure according to some examples; and

Figure 7 shows a procedure according to some examples.

DETAILED DESCRIPTION

In the following certain embodiments are explained with reference to mobile communication devices capable of communication via a wireless cellular system and mobile communication systems serving such mobile communication devices. Before explaining in detail the exemplifying embodiments, certain general principles of a wireless communication system, access systems thereof, and mobile communication devices are briefly explained with reference to Figures 1, 2 and 3 to assist in understanding the technology underlying the described examples.

Figure 1 shows a schematic representation of a 5G system (5GS) . The 5GS may be comprised by a terminal or user equipment (UE) , a 5G radio access network (5GRAN) or next generation radio access network (NG-RAN) , a 5G core network (5GC) , one or more application function (AF) and one or more data networks (DN) .

The 5G-RAN may comprise one or more gNodeB (GNB) or one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. The 5GC may comprise the following entities: Network Slice Selection Function (NSSF) ; Network Exposure Function; Network Repository Function (NRF) ; Policy Control Function (PCF) ; Unified Data Management (UDM) ; Application Function (AF) ; Authentication Server Function (AUSF) ; an Access and Mobility Management Function (AMF) ; and Session Management Function (SMF) .

Figure 2 illustrates an example of a control apparatus 200 for controlling a function of the 5GRAN or the 5GC as illustrated on Figure 1. The control apparatus may comprise at least one random access memory (RAM) 211a, at least on read only memory (ROM) 211 b, at least one

processor

212, 213 and an input/output interface 214. The at least one

processor

212, 213 may be coupled to the RAM 211a and the ROM 211 b. The at least one

processor

212, 213 may be configured to execute an appropriate software code 215. The software code 215 may for example allow to perform one or more steps to perform one or more of the present aspects. The software code 215 may be stored in the ROM 211 b. The control apparatus 200 may be interconnected with another control apparatus 200 controlling another function of the 5GRAN or the 5GC. In some embodiments, each function of the 5GRAN or the 5GC comprises a control apparatus 200. In alternative embodiments, two or more functions of the 5GRAN or the 5GC may share a control apparatus.

Figure 3 illustrates an example of a terminal 300, such as the terminal illustrated on Figure 1. The terminal 300 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’s mart phone’ , a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle) , a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (IoT) type communication device or any combinations of these or the like. The terminal 300 may provide, for example, communication of data for carrying communications. The communications may be one or more of voice, electronic mail (email) , text message, multimedia, data, machine data and so on.

The terminal 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 3 transceiver apparatus is designated schematically by block 306. The transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

The terminal 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute an appropriate software code 308. The software code 308 may for example allow to perform one or more of the present aspects. The software code 308 may be stored in the ROM 302a.

The processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 304. The device may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

In some network implementations, location services (LCS) may be employed to determine the location of one or more target UEs. 3GPP TS 23.273 describes some examples of procedures that may be used to determine the location of a target UE.

In some applications, it may be beneficial to obtain consecutive location estimates for a target UE.For example, where a regulatory client, including emergency and/or lawful interception, requires the location of a target UE. To obtain consecutive location estimates for a target UE, some examples may use a Periodic Deferred Location Request procedure, such as that specified in TS 23.273.

However, the example periodic deferred location procedure requirements specified in TS 23.273 may not be suitable for regulatory services. For example, due to its feature dependencies on UE capabilities, complexity and extensive impact to the system (all the nodes involved in LCS may be impacted) , the Deferred Location Request procedure provided in TS 23.273 may not be desirable for an operator to apply for regulatory services, and there may be a need to enhance the Location Immediate Request over Multilayer Protocol and/or System Block Information.

While some procedures specified in TS 23.273 may be applied for regulatory location services, they may not support multiple responses for a single request, i.e. they may not support consecutive location estimates without having to repeatedly request the UE location, which may be inefficient.

Some examples may address one or more of these issues.

Reference is made to Figures 4a-c, which show methods according to some examples.

Reference is made to Figure 4a, which shows a method that may be performed by a first network device, such as but not limited to a GMLC, LRF or NEF.

At 400, a method comprises receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements.

At 401, the method comprises, based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements.

At 402, the method comprises receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment.

At 403, the method comprises sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

Reference is made to Figure 4b, which shows a method that may be performed by a second network device, such as but not limited to an AMF or AN (e.g. RAN) .

At 404, a method comprises receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements.

At 405, the method comprises, based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements.

At 406, the method comprises receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment.

At 407, the method comprises sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

Reference is made to Figure 4c, which shows a method that may be performed by a third network device, such as but not limited to a LMF.

At 408, a method comprises receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements.

At 409, the method comprises, in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements.

At 410, the method comprises sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

In some examples, a request for the location of a target UE, such as an LCS service request, may comprise information indicating a type of event and/or a minimum time interval between motion event reports or an interval of each period if multiple reports are requested.

The information indicating the type of event may comprise information indicating whether the event is motion, periodic, or a trigger of emergency call event on UE side. For example, a location management function, or other network function, may provide location reports to the GMLC within the interval specified by the information, or provide multiple reports when a motion event associated with the target UE detected. This may assist the GMLC in selecting a more accurate or most recent result according to LCS request context.

In some examples, where network measurements are allowed in regulatory requests, a motion event may be ignored or can be coarsely triggered by Mobility Events from AMF. Intervals of periodic reports may be scheduled in the LMF.

In some examples, when the LMF observes that position of the UE changes significantly (i.e. more than a threshold amount) between two periodic reports (i.e. over a series of reports) , then LMF may reduce the periodic timer to get more accurate positioning of the fast moving UE.Similarly, when the LMF observes that position of the UE has not changed significantly (i.e. less than a threshold amount) between two periodic reports (over a series of reports) , then LMF may increase the periodic timer to optimize signalling during the positioning procedure.

In some examples, when multiple event reports are requested, the information may indicate a minimum time interval between motion event reports or interval of each period. Thus, in some examples, the request may indicate how often the LMF is to report the location of a target UE, in addition to immediately reporting the location of the target UE.

In some examples, after the LMF receives the request for the location of the target UE, the LMF may send a supplementary Request to the UE. The supplementary request may be sent over the User Plane (for example with LPP/LPPe messages) or via the serving AMF over Control Plane. The supplementary request may comprise a supplementary services LCS Triggered Invoke request. The supplementary request may comprise invoking a Namf_Communication_N1 N2MessageTransfer service operation.

The UE may provide a response to the request comprising information indicating a location of the UE. In some examples, configuration for event trigger may be configured at the UE.

For example, during the positioning session, Location Positioning Protocol (LPP) transactions may be carried out between LMF and UE. The LMF may obtain multiple results (i.e. multiple location estimates) during the LPP transactions according to the delay/response time of different positioning methods.

In some examples, for each of multiple results according to the event trigger, the LMF may provide a current location of the UE and timestamp of the location estimate. For example, the LMF may invoke an Nlmf_Location_EventNotify service operation towards GMLC to report the current location of the UE.

The GMLC may send the current location of the UE and timestamp of the location estimate received from the LMF to an external location services client.

For the next event detection (for example after the interval expires or motion of the UE that had triggered within the emergency call or lawful interception session is detected) , the processes described above may be repeated. In some examples, when the emergency call is terminated by the UE, the UE may trigger a Cancel location operation, for example by sending a message to the LMF to request cancellation of the location session.

Reference is made to Figure 5, which shows a procedure according to some examples.

In the example of Figure 5, an external client, such as an emergency service client or other application function, is requesting the location of a user equipment. The external client may interface with a network function, such as a GMLC, Location Reference Function (LRF) or Network Exposure Function (NEF) . It should be understood that, while Figure 5 and the description below references a GMLC, any suitable network function or device, such as a LRF or NEF, may perform the steps performed by the GMLC. Similarly, while Figure 5 and the following description makes reference to a Location Management Function (LMF) , it should be understood that any suitable network function or device may perform the steps performed by the LMF.

The example procedure may be applicable to a request from an LCS client for a current and/or intermediate location of a target UE. The procedure may assume that the LCS client is authorised to use the location service and no privacy verification is required.

At 501, the external location services client may send a request to the GMLC for a location for a target UE.

The request may comprise information identifying the target UE, for example a GPSI or an SUPI. The request may comprise the required QoS and Supported GAD shapes. If location information is required for more than one UE, the steps following below may be repeated. In such cases the GMLC may verify whether the number of Target UEs in the LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If Maximum Target UE Number is exceeded, the GMLC may reject the LCS request. In this case, the steps 502-510 may be skipped, and then GMLC may respond to the client with proper error cause in the step 511.

At 502, the GMLC may obtain information identifying the current serving AMF of the target UE. For example, as shown in Figure 5, the GMLC may send a request to the home UDM of the target UE.

For example, the GMLC may invoke a Nudm_UECM_Get service operation towards the home UDM of the target UE. The GMLC may determine the target UE based on the GPSI or SUPI comprised in the information received at 501. In some examples, GMLC may use a Nudm_SDM_Get service operation to retrieve the SUPI of the target UE as defined in 3GPP TS 23.502, clause 5.2.3.3.2.

At 503, the UDM may return the network addresses of the current serving AMF of the target UE.

At 504 the GMLC may request the current serving AMF to provide the current location of the target UE.

For example the GMLC may invoke the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The request may include the information identifying the target UE, such as the SUPI. The request may comprise the client type of the requesting external client. The request may comprise the required QoS and Supported GAD shapes.

At 506, the AMF may select an LMF based on the received request and optionally based on information locally available to the AMF. For example the AMF may select the LMF as defined in clause 5.1 of TS 23.273. The LMF selection may take the access node currently serving the UE into account. The selection may use a NRF query.

At 507, the AMF may send a request to the selected LMF for the current location of the target UE.

For example, the AMF may invoke the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the UE. The request may include one or more of: an LCS Correlation identifier, the serving cell identity of the Primary Cell in the Master RAN node and the Primary Cell in the Secondary RAN node when available based on Dual Connectivity scenarios, and the client type. The request may comprise an indication if UE supports LPP, the required QoS, UE Positioning Capability if available and Supported GAD shapes. The request may also include an identity of the AMF.

At 508, based on the request received at 507, the LMF may perform one or more positioning procedures to determine a geographical location of the target UE.

The LMF may perform any suitable procedure to determine the location, for example the procedure described in clauses 6.11.1, 6.11.2 and/or 6.11.3 of TS 23.273. For example the LMF may use the Namf_Communication_N1 N2MessageTransfer service operation to the transfer of a Network Positioning message to the serving access node (gNB or NG-eNB) for the target UE. The LMF may optionally determine a location in local coordinates.

In some examples, when the LMF is configured to periodically report the position (i.e. is configured to trigger periodically) , the LMF may use an internal timer to perform the positioning procedures at each interval.

In some examples, when the LMF is configured to report the position if the UE moves significantly (i.e. is configured to trigger based on UE motion) , the LMF may use Mobility Events from the AMF (for example as described in clause 4.15.4.2 of 3GPP TS 23.502) to detect the mobility and start the positioning procedures.

In some example, when the LMF observes that position of the UE changes significantly between two periodic reports (over a series of reports) , the LMF may reduce the periodic timer to get more accurate positioning of the fast moving UE. Similarly, if the LMF observes that position of the UE has not changed significantly between two periodic reports (over a series of reports) , then LMF may increase the periodic timer to optimize the signalling during positioning procedure.

In some examples, for example as shown at 508a in Figure 5, the LMF may send multiple intermediate reports to GMLC. The GMLC may forward the multiple intermediate reports to the LCS Client.

At 509, the LMF may send a response to the AMF comprising the current location of the target UE.

For example, the LMF may send a Nlmf_Location_DetermineLocation Response towards the AMF. The response may comprise information indicating a UE Positioning Capability if the UE Positioning Capability is received in step 508. The information may comprise an indication that the UE’s capabilities are non-variable and not received from AMF in step 507. The response may include one or more of: an LCS Correlation identifier, the location estimate, the age and accuracy of the location estimate, and information about the positioning method and the timestamp of the location estimate.

At 510, the AMF may send a location service response to the requesting client comprising the current location of the UE.

For example the AMF may send a Namf_Location_ProvidePositioningInfo Response towards the GMLC/LRF to return the current location of the UE. The response may include one or more of:the location estimate, the age and accuracy of the location estimate, information about the positioning method and the timestamp of the location estimate. The AMF may store the UE Positioning Capability in UE context when received from LMF.

At 511, the GMLC may send the location service response to the external location services client.

Reference is made to Figure 6, which shows a procedure according to some examples.

In the example of Figure 6, an external client, such as an emergency service client, is requesting the location of a user equipment. An event may trigger the network to request the location of the user equipment. For example, the event may relate to UE motion and/or periodic triggering, for example during an emergency call event on UE side.

It should be understood that, while Figure 6 and the description below references a GMLC, any suitable network function or device, such as a LRF or NEF, may perform the steps performed by the GMLC. In some examples, for a roaming UE, the GMLC may be a home-GLMC. Similarly, while Figure 6 and the following description makes reference to a Location Management Function (LMF) , it should be understood that any suitable network function or device may perform the steps performed by the LRF.

At 601, the external location services client or the AF may send a request to the GMLC for location reporting for periodic, triggered or UE available location events.

In some examples, the request may be sent via the NEF. The events may include an emergency call event.

In some examples the request may be sent as described for step 1 in clause 6.1.2 of TS 23.273 with the differences described herein.

The LCS Service Request may provide the type of periodic or triggered location reporting being requested and associated parameters.

In some examples, for periodic location, the LCS Service Request may include at least one of:time interval between successive location reports, the total number of reports or location QoS. The LCS Service Request may also include a scheduled location time for the first periodic location report.

In some examples, for area event reporting, the LCS Service Request may include at least one of: the target geographical area, whether the event to be reported is the UE being inside, entering into or leaving the target area, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS) , or whether only one location report is required or more than one. In some examples, when the target area is expressed by a local coordinate system or a geopolitical name, the GMLC may convert the target area to a geographical area expressed by a shape as defined in TS 23.032.

In some examples, for motion event reporting, the LCS Service Request may include at least one of: the threshold linear distance, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS) , or whether only one location report is required or more than one.

At 601 b-1, the AF may invoke the Nnef_EventExposure_Subscribe service operation to the NEF. At 601 b-2, the NEF may forward the request to the GMLC. The NEF may assign a LDR refence number locally and sends it to GMLC.

At 602, the GMLC may verify UE privacy requirements as for step 2 in clause 6.1.2 of TS 23.273. The GMLC may also subscribe to and receive notification of UE privacy profile updates according to steps 0 and 4 of clause 6.12.1 of TS 23.273.

At 603, the GMLC may query the UDM for the AMF address and, in the case of roaming, a VGMLC address as for step 3 in clause 6.1.2 of TS 23.273.

In some examples, the GMLC may also query the HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271. The deferred EPC-MT-LR procedure for Periodic and Triggered Location described in clause 9.1.19 of TS 23.271 or the EPC-MT-LR procedure for the UE availability event described in clause 9.1.15 of TS 23.271 may then be performed instead of the steps 604-631 described below –for example if the HSS returns an MME address but the UDM does not return an AMF address.

At 604, for a roaming UE, the HGLMC may invoke the Ngmlc_Location_Provide Location Request service operation to forward the location request to the VGMLC as described for step 4 of in clause 6.1.2 of TS 23.273. The HGMLC may obtain a VGMLC address if not received at step 603. The HGMLC may also include a contact address for the HGMLC (for example a Notification Target Address, such as a URI) and an LDR reference number (for example a Notification correlation ID) to be used for event reporting at

steps

620 and 629. The LDR reference number may be either allocated by HGMLC based on predefined rule (e.g. operator's policy if the location request is received in step 601a) or allocated by NEF (e.g. if the location request is received in step 601 b) .

Step 604 may be omitted if the UE is not a roaming UE.

At 605, the GMLC (either the HGLMC or VGMLC) may invoke the Namf_Location_ProvidePositioningInfo Request service operation to forward the location request to the serving AMF, for example as described for step 5 in clause 6.1.2 of TS 23.273.

The request may include the GMLC contact address and LDR reference number. The LDR reference number may be allocated by GMLC based on predefined rule (e.g. operator′s policy if the location request is received in step 601a) , or allocated by NEF (e.g. if the location request is received in step 601 b) . For area event reporting, the target geographical area may be converted into a corresponding list of cell and/or tracking area identities.

At 606-608, when the AMF supports a deferred location request, the AMF may return an acknowledgment to the external LCS client, via the GMLC and, in the case of roaming, the VGMLC, indicating that the request for deferred location was accepted. The VGMLC, when used, may optionally release resources for the deferred location request at this point.

At 609, if the UE is not currently reachable (e.g. is using discontinuous reception or power save mode) , the AMF may wait for the UE to become reachable.

In some examples, in the event of mobility of the UE to another AMF or to EPC when the UE becomes reachable, the old AMF may return an event indication to the GMLC as at

steps

619 and 620. The event indication may include the address of the new serving AMF or MME if known. If a new serving AMF or MME is not known, the GMLC may repeat step 603 to query the UDM and HSS for the new AMF or MME address. If a new AMF address is received, the GMLC may restart the procedure from step 604.

At 610, when the UE is reachable and in CM IDLE state, the AMF may initiate a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 to establish a signalling connection with the UE.

In some examples the AMF may decide to cancel the location request before the UE becomes reachable (e.g. due to lack of resources or due to a timeout on the UE becoming reachable) or when the UE becomes reachable (e.g. if the AMF executes NAS level congestion control on the UE, or for other reasons) . The AMF may then skip steps 610-618 and proceed to step 619 to return an indication of location cancelation to the VGMLC or GMLC.

At 611-612, the AMF may perform steps 7-8 in clause 6.1.2 TS 23.273 to notify the UE of the location request and verify privacy requirements if required by the location request received at step 605 and supported by the UE. The AMF may include in the notification to the UE the type of deferred location request in the case of periodic or triggered location.

At 613, the AMF may select an LMF as described for step 6 in clause 6.1.1 of TS 23.273. The selection may take into account the type of deferred location request (e.g. whether periodic or triggered) and any parameters for the deferred location request (e.g. the number of event reports required and/or the duration) .

At 614, the AMF may invoke the Nlmf_Location_DetermineLocation Request service operation towards the LMF to initiate a request for deferred UE location.

For a request for periodic or triggered location, the service operation may include the information received in step 604 or step 605 including one or more of: the GMLC contact address, LDR reference number, UE Positioning Capability if available and any scheduled location time. The request may include a list of allowed access types for event reporting at step 622.

For a request for the UE available location event, the GMLC contact address and LDR reference number may not be included.

The service operation may include an LCS Correlation identifier, the AMF identifier, the serving cell identity, the client type and may include an indication if UE supports LPP, the required QoS and Supported GAD shapes.

At 615, the LMF may perform one or more positioning procedures, for example as described in clause 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 or as described for step 8 in clause 6.1.1 of TS 23.273.

During this step, the LMF may request and obtain the UE positioning capabilities (e.g. which may indicate the type (s) of periodic and triggered location supported by the UE and the access types supported by the UE for event reporting) . The LMF may obtain the UE location -e.g. for a request for the UE available location event or when an initial location is requested for periodic or triggered UE location. For a request for the UE available location event, the LMF may skip

steps

616 and 617.

At 616, when periodic or triggered location or emergency call event was requested, the LMF may send a supplementary services LCS Periodic-Triggered Invoke Request to the UE via the serving AMF by invoking the Namf_Communication_N1 N2MessageTransfer service operation.

The LCS Periodic-Triggered Location Invoke may include the location request information received from the AMF at step 614, including at least one of the GMLC contact address, LDR reference number or any scheduled location time. The LCS Periodic-Triggered Location Invoke may also include a deferred routing identifier, which for example can be the identification of the LMF when the LMF will act as a serving LMF or a default LMF identification otherwise.

The LCS Periodic-Triggered Location Invoke may indicate the allowed access types for event reporting at step 625 (e.g. one or more of NR, E-UTRA connected to 5GC, non-3GPP access connected to 5GC, any of the RAT Types specified for NR satellite access) . The LCS Periodic-Triggered Location Invoke may include embedded positioning message (s) which may indicate certain location measurements (or a location estimate and the timestamp of the location estimate if available) at step 624 for each location event reported (e.g. based on the positioning capabilities of the UE obtained in step 614 and the allowed access types) . The indicated location measurements may be allowed or required location measurements.

As part of NAS transport of the LCS Periodic-Triggered Location Invoke from the serving AMF to the UE, the serving AMF may include an immediate routing identifier in the NAS transport message containing an LCS Correlation identifier -e.g. according to clause 6.11.1 of TS 23.273.

In some examples, the deferred routing identifier may be global (e.g. an IP address, UUID or URI) or may be local. The deferred routing identifier may be used for routing in step 625. The immediate routing identifier included by the AMF in step 615 may be used for routing in step 617.

At 617, when the request in step 616 can be supported, the UE may return a supplementary services acknowledgment to the LMF. The acknowledgement may be transferred via the serving AMF using the immediate routing identifier. The acknowledgement may be delivered to the LMF using an Namf_Communication_N1 MessageNotify service operation.

At 618, the LMF may invoke the Nlmf_Location_DetermineLocation Response service operation towards the AMF to respond to the request at step 614.

In some examples, for a request for the UE available location event, the response may include UE location information obtained at step 615. The LMF may then releases resources associated with the positioning session.

In some examples, for a periodic or triggered location request, the response may include at least one of: UE location information obtained at step 615, a confirmation of whether periodic or triggered location was successfully activated in the UE according to

steps

616 and 617, or the identification of the LMF in the case of successful activation with a serving LMF.

The LMF may retain state information and resources for later steps if the LMF acts a serving LMF. The LMF may provide the achieved Location QoS Accuracy in step 615, which in some examples may be provided if the multiple QoS class was used in the location request.

In some examples, if the UE cannot support the periodic and triggered location request, the service operation returned to the AMF may include a suitable error cause.

The service operation may include the UE Positioning Capability if the UE Positioning Capability is received in step 615. The service operation may include an indication that the UE capabilities are non-variable and not received from AMF in step 614.

At 619, the AMF may invoke the Namf_Location_EventNotify service operation towards the GMLC (for example VGMLC for roaming UE or HGMLC for non-roaming UE) . The AMF may include any UE location information received at step 618 and, for periodic or triggered location, may include a confirmation of whether or not periodic or triggered location was successfully activated in the target UE.

The VGMLC, if used, may be the same VGMLC used in

steps

605 and 606 or may be a different VGMLC. In the case of a different VGMLC, the AMF may include the HGMLC contact address and LDR reference number. The AMF may include the LMF identification and the achieved Location QoS Accuracy if received at step 618. The AMF may then release all resources for the location request and cease support for the procedure.

At 620, for a roaming UE, The VGMLC may forward the response received at step 619 to the HGMLC using the HGMLC contact address received at step 619 (for a different VGMLC) or received and stored at step 604 (for the same VGMLC) . The VGMLC may include the LDR reference number and any LMF identification that was received. The VGMLC may then release all resources for the location request and cease support for the procedure.

Step 620 may be skipped for a non-roaming UE

As an optional procedure for a roaming UE, instead of performing

steps

619 and 620, the AMF may invoke the Namf_Location_EventNotify service operation directly towards the HGMLC (e.g. if a VGMLC is not used or if the VGMLC ceases support after step 608) .

At 621, the GMLC may forward the response to the external LCS client or AF (for example via the NEF) . If the location request at step 601 was for the UE available location event, the procedure may terminate here and further steps may not be performed.

At 622, when UE triggers an emergency call, the configured trigger event may be detected. Based on the detection of the trigger event, the UE may perform a UE triggered service request as defined in clause 4.2.3.2 of TS 23.502 if in CM-IDLE state in order to establish a signalling connection with the AMF.

In some examples the UE may send a supplementary services event report message to the LMF, which may be transferred via the serving AMF (which may be different to the original serving AMF for steps 614-616) . The event report may be delivered to the LMF using an Namf_Communication_N1 MessageNotify service operation.

At 623, the UE sends an event report to the LMF. The event report may indicate the type of event being reported (e.g. whether a normal event or expiration of the maximum reporting interval or emergency call event) and may include embedded positioning message (s) . The embedded messages may include UE location measurements or location estimate and the timestamp of the location estimate if available .

The UE may include the deferred routing identifier received in step 616 in message (e.g. the NAS Transport message) used to transfer the event report from the UE to the AMF. The AMF may forward the event report to either the serving LMF or any suitable LMF based on whether the deferred routing identifier indicates a particular LMF or any (default) LMF. If a different LMF than the serving LMF is used, the procedure in clause 6.4 of TS 23.273 may be used. The UE may include one or more of the GMLC contact address, the LDR reference number, whether location estimates are to be reported and if so the location QoS in the event report and any scheduled location time indicated at step 616 for periodic reporting.

In some examples, when forwarding the event report message to the LMF in step 635, the AMF may include the deferred routing identifier received in step 623 as the LCS Correlation Identifier. The deferred routing identifier can assist a serving LMF in identifying the periodic or triggered location session if the same serving LMF had assigned the deferred routing identifier at step 616 or can indicate to the LMF that it is acting as a default LMF.

In some examples, the scheduled location time included at step 622 may equal T + (N-1) *P, where T is the initial Scheduled Location Time, N is the Report Number (N≥1) and P is the time interval between successive periodic events.

When the LMF receives the event report at 623, and if it can handle this event report, the LMF may update the status of event reporting (e.g. the number of event reports so far received from the UE and/or the duration of event reporting so far) .

At 624, the LMF may return a supplementary services acknowledgment for the event report to the UE. The acknowledgment may optionally include a new deferred routing identifier indicating a new serving LMF or a default (any) LMF.

If the UE does not receive any response from the LMF after a predefined time, i.e. the current LMF does not support the deferred location request (for temporary or permanent reasons) or due to some radio access failures, the UE may re-send the report one or more times. If the UE sends the repeated event report more than a predefined maximum resending time and the UE still does not receive any response from AMF, the UE may stop resending the report and reserve the event report, then record a corresponding flag to indicate that a report has been sent unsuccessfully. When the UE performs location update and detects the PLMN is changed, if the flag has been set, the UE may send the report to the corresponding AMF, and the flag may be cleared upon a success of the sending.

In some examples, a deferred routing identifier may be included in the event report acknowledgment at step 624 may be used to change the serving LMF (e.g. if a UE moves into an area or to an access type that is better supported by a different LMF or if the serving LMF is overloaded) or to enable a default LMF to become a serving LMF.

At 625, the LMF may perform one or more of the positioning procedures, such as those described in clause 6.11.1, 6.11.2 and 6.11.3 of TS 23.273 and as described for step 8 in clause 6.1.1 and step 12 in clause 6.1.2 of TS 23.273.

In some examples, the LMF may perform the position procedure when a location estimate is needed for event reporting. The LMF may determine the UE location using the location measurements and/or location estimate (s) obtained at this step and/or received at step 623. The LMF may also determine the timestamp of the location estimate. In case the event trigger is related to UE initiated emergency call, then LMF may perform network based positioning procedure to determine the UE location for reliability.

In some examples, a precondition for the positioning procedure, for example as per clause 6.11.1 of TS 23.273, may be that an LCS Correlation identifier assigned by the serving AMF has been previously passed to the LMF. The LCS Correlation identifier may be used, for example as per steps 1, 3, 6 and 7 in clause 6.11.1 of TS 23.273, to ensure that during a positioning session between the LMF and UE, positioning response messages from the UE are returned by the AMF to the correct LMF and carrying an indication (the LCS Correlation identifier) which can be recognized by the LMF.

To provide this capability, in step 625, the LMF may assign a Correlation identifier indicating the LMF (and optionally a positioning session) for use, for example as per step 1 in clause 6.11.1 of TS 23.273. To enable an AMF to distinguish a Correlation identifier assigned by an LMF (used in this procedure) from a Correlation identifier assigned by the AMF (used otherwise for clause 6.11.1) , the two types of Correlation identifier may be selected from different ranges, with or without a flag.

At 626, in the case of a roaming UE, the LMF may select a VGMLC (which may be different to the VGMLC for steps 603-608 and steps 619-621) . The LMF may then invoke an Nlmf_Location_EventNotify service operation towards the selected GMLC with an indication of one or more of: the type of event being reported, the (H) GMLC contact address and LDR reference number, the identification of the LMF if this is a serving LMF, or any location estimate and the timestamp of the location estimate (if available) obtained at step 625. If multiple QoS class was used in the initial location request, the LMF may provide the achieved Location QoS Accuracy in step 625.

In some examples, in the case of a roaming UE, the LMF may select the VGMLC for step 626 using a NRF service or using configuration information in the LMF or may use the same VGMLC as for steps 603-608 (e.g. if the LMF acts as a serving LMF and received the VGMLC address from the AMF as part of step 614) .

At 627, UE, for a roaming UE, the VGMLC may invoke an Ngmlc_Location_EventNotify service operation to forward the information received in step 626 (e.g. including the type of event being reported, the LDR reference number and possibly the LMF identification) to the HGMLC, which may identify the periodic and triggered location request from the LDR reference number.

Step 627 may be skipped for a non-roaming UE.

In some examples, as an optional procedure for a roaming UE, instead of performing

steps

626 and 627, the LMF may invoke the Nlmf_Location_EventNotify service operation directly towards the HGMLC.

In some examples, in the event of mobility of the UE to an access network for which event reporting is not allowed (e.g. an access network in EPS) or if the UE is otherwise unable to send event reports (e.g. due to being powered off) , the GMLC may not receive event reports at step 626 or step 627 at fixed intervals for periodic location or at intervals equal to or less than the maximum reporting interval for triggered location. In such a case, the GMLC may cancel the periodic or triggered location reporting, for example using the procedures defined in clause 6.3.3 of TS 23.273. The UE may also cancel the periodic or triggered location reporting either locally or using a procedure such as that defined in clause 6.3.2 of TS 23.273 once the UE can access an access network that is allowed for event reporting.

At 628, the GMLC may identify the periodic and triggered location request received in step 601 (for example using the LDR reference number received in step 626 or step 627) .

The GMLC may send the type of event being reported and any location estimate and the timestamp of the location estimate (if available) and used positioning methods to the external LCS client or AF (for example via the NEF) . The GMLC may also send the LDR reference number to LCS client. The GMLC may also verify UE privacy requirements before reporting the event and any location to the external LCS client or AF. If multiple QoS class was used in the initial location request, the LMF may provide the achieved Location QoS Accuracy in step 625.

At 629, the UE may continue to monitor for further periodic or trigger events and may instigate steps 622-628 each time a trigger event is detected.

In some examples, the Le interface (NEW/AF GMLC/LCS Client interface) may support multiple location response (MLR) .

In some examples the Le interface may reuse the MLP report defined in OMA MLP 3.3～3.5, clause 5.2.3.2. The Le interface may also reuse the subscription and notification mechanism of NEF interface. Both options may use asynchronous HTTP support, which may utilize a HTTP server deployed at client side.

In order to allow for synchronous invocation defined by LIR description in clause 4.1a. 4 TS 23.273, server push defined in HTTP/2 (referred in clause 4.9.5 of TS 29.501 and clause 5.2.5 of TS 29.500) may be used to enhance the Le interface 3GPP SBI and OMA MLP cases/protocols.

Reference is made to Figure 7, which shows a procedure according to some examples.

At step 701, the AF or LCS client may send an MLP or subscribe request to the NEF or GMLC. The MLP and the nef_eventExposure_subscribe request may contain an indication for a current and intermediate response, such as a ‘CURRENT_AND_INTERMEDIATE’ request type, to accept MLR within on LCS session.

At step 702, the NEF/GMLC may perform UE and/or network based motion/periodic trigger based positioning, for example using any of the previously described methods.

At step 703 and step 703. x, GMLC/NEF may use server push of HTTP/2 for one or multiple INTERMEDIATE response (s) . The response may use a tag to show whether this is INTERMEDIATE or FINAL response.

At step 704, the AF/LCS Client may handle one or multiple INTERMEDIATE response (s) with QoP satisfied or not satisfied.

At steps 705-706, the NEF or GMLC may send a FINAL response to the AF or LCS client, which may handle the FINAL response, for example as defined in TS 23.273.

Thus examples have been described whereby an external client may request a location of a target UE according to one or more requirements. The network may process the request and provide one or more responses including information identifying a location of the target UE to the client. The target UE location may be determined based on one or more trigger conditions, such as a periodicity, or mobility/movement event relating to the target UE.

In some examples, there is provided an apparatus comprising means for performing any of the abovementioned steps. For example, in some examples there is provided a first device comprising means for: receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

In some examples, the first device may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to: receive, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements; based on the received request, send, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements; receive, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and send, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

In some examples there is provided a second device comprising means for: receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

In some examples, the second network device may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to: receive, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements; based on the received request, send, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements; receive, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and send, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.

In some examples there is provided a third network device comprising means for: receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

In some examples the third network device may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the third network device at least to: receive, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements; in response to determining that the one or more trigger conditions are satisfied, determine the location of the target user equipment based on the one or more location accuracy requirements; and send, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.

The client device may comprise one of: an external client, a public safety answering point (PSAP) , an application function (AF) , or a network exposure function (NEF) . The first device may comprise one of: a gateway mobile location centre (GMLC) , a location retrieval function (LRF) or a network exposure function (NEF) . The second device may comprise one of: an access and mobility management function (AMF) or an access node (AN) . The third device may comprise a location management function (LMF) .

It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

It is noted that whilst some embodiments have been described in relation to 5G networks, similar principles can be applied in relation to other networks and communication systems. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

In general, the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. ”

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

The embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.

The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) , application specific integrated circuits (ASIC) , FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

Embodiments of the disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

The scope of protection sought for various embodiments of the disclosure is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the disclosure.

The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of this invention as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

A first network device comprising means for:

receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements;

based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements;

receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and

sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
The first network device of claim 1, wherein the one or more trigger conditions comprise one or more of:

a network mobility event associated with the target user equipment occurs;

a determined movement of the user equipment is more than a threshold amount;

a time duration has passed since a previous response was sent.
The first network device of claim 1 or 2, wherein the one or more location accuracy requirements comprises at least a first accuracy requirement and a second accuracy requirement, wherein the second accuracy requirement is more precise than the first accuracy requirement.
The first network device of any of claims 1 to 3, wherein each of the one or more responses comprise one of:

the information identifying the determined location of the target user equipment and an indication that a response is an intermediate response; or

the information identifying the determined location of the target user equipment and an indication that a response is a final response.
The first network device of any of claims 1 to 4, wherein:

the first network device comprises one of: gateway mobile location centre, a location retrieval function, or a network exposure function;

the client device comprises one of: an external client, public safety answering point, an application function, or a network exposure function; and

the second network device comprises an access and mobility management function or an access node.
A second network device comprising means for:

receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements;

based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements;

receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and

sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
The second network device of claim 6, wherein the one or more trigger conditions comprise one or more of:

a network mobility event associated with the target user equipment occurs;

a determined movement of the user equipment is more than a threshold amount;

a time duration has passed since a previous response was sent.
The second network device of claim 6 or 7, wherein the one or more location accuracy requirements comprises at least a first accuracy requirement and a second accuracy requirement, wherein the second accuracy requirement is more precise than the first accuracy requirement.
The second network device of any of claims 6 to 8, wherein each of the one or more responses comprise one of:

the information identifying the determined location of the target user equipment and an indication that a response is an intermediate response; or

the information identifying the determined location of the target user equipment and an indication that a response is a final response.
The second network device of any of claims 6 to 9, wherein:

the first network device comprises one of: gateway mobile location centre, a location retrieval function, or a network exposure function;

the second network device comprises an access and mobility management function or an access node; and

the third network device comprises a location management function.
A third network device comprising means for:

receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements;

in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and

sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.
The third network device of claim 11, wherein determining the location of the target user equipment comprises selecting a positioning method based on the one or more location accuracy requirements.
The third network device of claim 11 or 12, wherein the one or more trigger conditions comprise one or more of:

a network mobility event associated with the target user equipment occurs;

a determined movement of the user equipment is more than a threshold amount;

a time duration has passed since a previous response was sent.
The third network device of claim 13, wherein the one or more trigger conditions comprises the time duration, and wherein third network device comprises means for:

determining that movement of the user equipment is greater than a threshold amount and reducing the time duration; or

determining that movement of the user equipment is less than a threshold amount and increasing the time duration.
The third network device of any of claims 11 to 14, wherein the one or more location accuracy requirements comprises at least a first accuracy requirement and a second accuracy requirement, wherein the second accuracy requirement is more precise than the first accuracy requirement.
The third network device of claim 15, wherein determining the location of the target user equipment comprises:

determining the location of the target user equipment based on the first accuracy requirement; and

sending, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is an intermediate response.
The third network device of claim 15 or 16, wherein determining the location of the target user equipment comprises:

determining the location of the target user equipment based on the second accuracy requirement; and

sending, to the second network device, a response comprising the information identifying the determined location of the target user equipment and an indication that the response is a final response.
The apparatus of any of claims 11 to 17, wherein:

the second network device comprises an access and mobility management function or an access node; and

the third network device comprises a location management function.
A first network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device at least to:

receive, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements;

based on the received request, send, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements;

receive, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and

send, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
A second network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device at least to:

receive, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements;

based on the received request, send, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements;

receive, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and

send, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
A third network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the third network device at least to:

receive, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements;

in response to determining that the one or more trigger conditions are satisfied, determine the location of the target user equipment based on the one or more location accuracy requirements; and

send, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.
A method performed by a first network device, the method comprising:

receiving, from a client device, a location request for a target user equipment, wherein the request comprises an indication for supporting one or more intermediate responses, one or more trigger conditions for the one or more intermediate responses, and one or more location accuracy requirements;

based on the received request, sending, to a second network device, a request to provide the location of the target user equipment, wherein the request comprises the one or more trigger conditions and the one or more location accuracy requirements;

receiving, from the second network device, one or more responses comprising information identifying the location of the target user equipment; and

sending, to the client device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
A method performed by a second network device, the method comprising:

receiving, from a first network device, a request to provide a location of a target user equipment, wherein the request comprises a one or more trigger conditions for one or more intermediate responses and one or more location accuracy requirements;

based on the received request, sending, to a third network device, a request for information identifying the location of the target user equipment, wherein the sent request comprises the one or more trigger conditions and one or more location accuracy requirements;

receiving, from the third network device, one or more responses comprising information identifying the location of the target user equipment; and

sending, to the first network device, one or more responses comprising information identifying the location of the target user equipment and an indication of whether the sent one or more responses comprise an intermediate response or a final response.
A method performed by a third network device, the method comprising:

receiving, from a second network device, a request for information identifying a location of a target user equipment, wherein the sent request comprises one or more trigger conditions and one or more location accuracy requirements;

in response to determining that the one or more trigger conditions are satisfied, determining the location of the target user equipment based on the one or more location accuracy requirements; and

sending, to the second network device, one or more responses comprising information identifying the determined location of the target user equipment.