Periodic location reporting for deferred mobile terminated location request (mt-LR)

Abstract

A method, system and apparatus are disclosed. According to some embodiments, a method implemented in a location management function, LMF, node, is provided. An access network node is configured to periodically report location measurements for a wireless device. Reports of location measurements according to the periodic reporting configuration at the access network node for the wireless device are periodically received from the access network node. Location estimates are determined based on the one or more periodic reports of location measurements obtained from the access network node. The location estimates are periodically transmitted to one of a Location Services, LCS, client or Application Function, AF, node.

Description

[0001] PERIODIC LOCATION REPORTING FOR DEFERRED MOBILE TERMINATED LOCATION REQUEST (MT-LR)

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to periodic location reporting.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] The below discussion is based on 3GPP TS 23.273 v 18.2.0.

[0007] Deferred Location Request

[0008] With a deferred location request, a location services (LCS) client or application function (AF) sends a location request to a public land mobile network (PLMN) for a target wireless device (or group of target wireless devices) and expects to receive a response containing the indication of event occurrence and location information if requested for the target wireless device (or group of target wireless devices) at some future time (or times), which may be associated with specific events associated with the target wireless device (or group of target wireless devices). In 3GPP TS 23.273 v 18.2.0, only deferred location requests for a Mobile Terminated Location Request (MT-LR) may be supported.

[0009] Types of event

[0010] The following types of events are defined for a deferred location request. a) Wireless device availability: Any event in which the 5thgeneration core network (5GCN) has established contact with the wireless device. This event is considered to be applicable when the wireless device is temporarily unavailable due to inaction by the user, or for temporary loss of radio connectivity or international mobile subscriber identity (IMSI) detach and so on. The wireless device Available event only requires one response to an LCS client / AF and after this response, the wireless device Available event is concluded. b) Area: An event where the wireless device enters, leaves or remains within a predefined geographical area. At least one type of area event can be defined (i.e. entering, leaving or remaining within the area). The LCS client or AF may define the target area as a geographical area or as a geopolitical name of an area. The PLMN may translate and define the target area as the identities of one or more radio cells or tracking areas. The LCS client or AF may request an additional check about whether the wireless device is located within the provisioned target area. The area event may be reported one time only, or multiple times. The area event report may contain an indication of the event occurrence. The location estimate may be included in the report. If an area event is detected by the wireless device but an event report cannot be sent (e.g., because the wireless device cannot access the network or due to a minimum reporting interval), a report may be sent later when possible irrespective of whether the area event still applies for the current wireless device location. Area event reporting is controlled by a minimum and a maximum reporting time. The minimum reporting time defines the minimum allowed time between successive area events. The maximum reporting time defines the maximum time between successive reports. When a wireless device sends a report due to the expiration of the maximum reporting time, the wireless device indicates the expiration of the maximum reporting time as the trigger event. The maximum reporting time enables the AF, LCS client and home gateway mobile location centre (HGMLC) to remain aware of continuing support by the wireless device for the area event (e.g., to detect if area event reporting may have been aborted due to wireless device power off).

[0011] NOTE: To achieve more precise usage of area event in some scenario, e.g., for small target area, it may be useful if LCS Client / AF requests wireless device location estimate and compares the location estimate with the target area. c) Periodic Location: An event where a defined periodic timer expires in the wireless device and activates a location report. If a periodic event is detected by the wireless device but an event report cannot be sent (e.g., because the wireless device cannot access the network temporarily), a report may be sent later when possible and the periodic timer for the next event may then be started. The reporting duration for periodic location may equal the requested number of reports multiplied by the periodic interval even when reports are delayed. d) Motion: An event where the wireless device moves by more than some predefined straight line distance from a previous location. The motion event may be reported one time only, or multiple times. The motion event report may contain an indication of the event occurrence. A location estimate may be included in the report if requested by the LCS client or AF. For successive motion event reports, motion is determined relative to the wireless device location corresponding to the immediately preceding event report (including an event report triggered by expiration of the maximum reporting time). If a motion event is detected by the wireless device but an event report is deferred (e.g., because the wireless device cannot access the network temporarily), a report may be sent later when possible irrespective of whether the motion event still applies to the current wireless device location. Motion reporting is controlled by a minimum and a maximum reporting time. The minimum reporting time defines the minimum allowed time between successive event reports. The maximum reporting time defines the maximum time between successive reports. When a wireless device sends a report due to expiration of the maximum reporting time, the wireless device indicates expiration of the maximum reporting time as the trigger event. The maximum reporting time enables the AF, LCS client and HGMLC to remain aware of continuing support by the wireless device for the motion event (e.g., to detect if motion event reporting may have been aborted due to wireless device power off).

[0012] In 3GPP Rel-16 Deferred 5GC-MT-LR Procedure for Periodic, Triggered and wireless device Available Location Events has been defined in clause 6.3 of 3GPP TS 23.273.

[0013] In 3 GPP Rel-18 5GC-MT-LR multiple location procedure for the regulatory location service has been introduced in clause 6.1.3 of 3GPP TS 23.273 providing a less complex periodic / multiple location estimate targeting only regulatory use cases.

[0014] FIGs. 1A-1C are an example signaling diagram of Deferred 5GC-MT-LR for periodic, triggered and wireless device available location events.

[0015] 5GC-MT-LR multiple location procedure for the regulatory location service

[0016] FIG. 2 is a signaling diagram that illustrates an extension procedure of 5GC-MT- LR procedure for the regulatory location service defined in clause 6.1.1. of 3GPP TS 23.273.

[0017] This procedure is applicable for providing multiple location estimates of the target wireless device to LCS client. However, current Deferred Location solution in LCS depends fully on the wireless device. Wireless device functionality is a required to execute periodic location. The wireless device dependent solution makes this procedure complex, which uses limited computing resources and / or power resources.

[0018] SUMMARY

[0019] Some embodiments advantageously provide methods, systems, and apparatuses for periodic location reporting.

[0020] However, as discussed above, current Deferred Location solution in LCS depends fully on the wireless device. Wireless device functionality is a required to execute periodic location. The wireless device dependent solution makes this procedure complex. There is a need for an alternative periodic deferred location which can operate in a wireless device agnostic way. Even when an LCS client requests for periodic positioning report, the current positioning flow does not support that.

[0021] It is not possible to provide periodic positioning report (location) to the client in existing systems.

[0022] It is possible to configure a periodic event for a wireless device for deferred positioning procedure; however, it is not possible to configure and obtain positioning periodically.

[0023] According to one or more embodiments described herein, a new procedure is defined (designed) which allows the network (LMF node) to configure periodic positioning report from different entities such as next generation-radio access network (NG-RAN) or from the wireless device. That is, it would be beneficial to have a less complex 3GPP procedure for periodic location event procedures. One or more embodiments leverage RAN defined NR positioning protocol A (NRPPa) periodic measurement report and LTE positioning protocol (LPP) periodic reporting for commercial use cases.

[0024] Instead of configuring the wireless device for reporting periodicity using LCS supplementary service in step 16 of FIGs. 1A-1C, LMF node may initiate Periodic Measurement Request toward NG-RAN using NRPPa or initiate Ipp periodical Reporting towards the wireless device by the required periodicity as described in step 4 in FIG. 8. In one or more embodiments, LMF node based on wireless device capabilities may decide to initiate Periodic Measurement Request toward NG-RAN using NRPPa or initiate Ipp periodical Reporting towards the wireless device by the required periodicity. In one or more embodiments, LMF node may use periodically received measurements or locations estimates to forward location estimates to GMLC using Nlmf_Location_EventNotify. One or more embodiments described herein may have negligible or no impact on RAN.

[0025] According to one aspect of the present disclosure, a method implemented in a location management function, LMF, node is provided. An access network node is configured to periodically report location measurements for a wireless device, as described herein. Reports of location measurements according to the periodic reporting configuration at the access network node for the wireless device are periodically received from the access network node, as described herein. Location estimates are determined based on the one or more periodic reports of location measurements obtained from the access network node, as described herein. The location estimates are periodically transmitted to one of a Location Services, LCS, client or Application Function, AF, node, as described herein.

[0026] According to one or more embodiments of this aspect, after receiving a report that a location measurement session is terminated, a procedure to locate and reconnect the wireless device to the access network node is initiated.

[0027] According to one or more embodiments of this aspect, the procedure is initiated at least in part by requesting that an application management function, AMF, node page the wireless device, and the location measurement session is terminated based on the wireless device being unavailable or in a radio resource control, RRC, idle mode.

[0028] According to one or more embodiments of this aspect, if the report of the location measurement indicates that one of an error occurred or no location measurement occurred, another procedure to obtain the location measurements is triggered.

[0029] According to one or more embodiments of this aspect, a request is received, from the LCS client, for periodic reporting of location measurements for the wireless device, and the configuration of the access network node to periodically report location measurements is in response to the request.

[0030] According to one or more embodiments of this aspect, the configuration of the access network node to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device, and transmitting the periodic reporting configuration to the access network.

[0031] According to one or more embodiments of this aspect, the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp. According to one or more embodiments of this aspect, the periodic receiving, from the access network node, of reports of location measurements is configured to occur at a first periodicity; and the periodically transmitting the location estimates to one of the LCS client or the AF node is configured to occur at one of: the first periodicity; or a second periodicity different from the first periodicity.

[0032] According to one or more embodiments of this aspect, the access network node is one of an eNodeB, eNB, or a gNodeB, gNB.

[0033] According to another aspect of the present disclosure, a location management function, LMF, node is configured to: configure an access network node to periodically report location measurements for a wireless device; periodically receive, from the access network node, reports of location measurements according to the periodic reporting configuration at the access network node for the wireless device; and determine location estimates based on the one or more periodic reports of location measurements obtained from the access network node; and periodically transmit the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

[0034] According to one or more embodiments of this aspect, the LMF node is further configured to, after receiving a report that a location measurement session is terminated, initiate a procedure to locate and reconnect the wireless device to the access network node.

[0035] According to one or more embodiments of this aspect, the procedure is initiated at least in part by requesting that an application management function, AMF, node page the wireless device, and the location measurement session is terminated based on the wireless device being unavailable or in a radio resource control, RRC, idle mode.

[0036] According to one or more embodiments of this aspect, the LMF node is further configured to, if the report of the location measurement indicates that one of an error occurred or no location measurement occurred, trigger another procedure to obtain the location measurements.

[0037] According to one or more embodiments of this aspect, the LMF node is further configured to receive a request, from the LCS client, for periodic reporting of location measurements for the wireless device, and the configuration of the access network node to periodically report location measurements being in response to the request.

[0038] According to one or more embodiments of this aspect, the configuration of the access network node to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device; and transmitting the periodic reporting configuration to the access network.

[0039] According to one or more embodiments of this aspect, the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

[0040] According to one or more embodiments of this aspect, the periodic receiving, from the access network node, of reports of location measurements is configured to occur at a first periodicity, and the periodically transmitting the location estimates to one of the LCS client or the AF node is configured to occur at one of: the first periodicity; or a second periodicity different from the first periodicity.

[0041] According to one or more embodiments of this aspect, the access network node is one of an eNodeB, eNB, or a gNodeB, gNB.

[0042] According to another aspect of the present disclosure, a computer readable storage medium comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform a method is provided. The method comprises configuring an access network node to periodically report location measurements for a wireless device, periodically receiving, from the access network node, reports of location measurements according to the periodic reporting configuration at the access network node for the wireless device, determining location estimates based on the one or more periodic reports of location measurements obtained from the access network node and periodically transmitting the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

[0043] According to one or more embodiments of this aspect, the configuration of the access network node to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device and transmitting the periodic reporting configuration to the access network, and the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

[0044] BRIEF DESCRIPTION OF THE DRAWINGS

[0045] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0046] FIGS. 1A-1C are a signaling diagram of Deferred 5GC-MT-LR for periodic, triggered and wireless device available location events;

[0047] FIG. 2 is a signaling diagram that illustrates an extension procedure of 5GC-MT- LR procedure for the regulatory location service defined in clause 6.1.1;

[0048] FIG. 3 is a schematic diagram of an example network architecture according to the principles in the present disclosure;

[0049] FIG. 4 is a block diagram of various entities of FIG. 3 according to some embodiments of the present disclosure;

[0050] FIG. 5 is a flowchart of an example process in a node according to some embodiments of the present disclosure;

[0051] FIG. 6 is a flowchart of another example process in a node according to some embodiments of the present disclosure;

[0052] FIG. 7 is a flowchart of an example process in another node according to some embodiments of the present disclosure;

[0053] FIG. 8 is a signaling diagram according to some embodiments of the present disclosure;

[0054] FIG. 9 is another signaling diagram according to some embodiments of the present disclosure; and

[0055] FIG. 10 is another signaling diagram according to some embodiments of the present disclosure.

[0056] DETAILED DESCRIPTION

[0057] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to periodic location reporting. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0058] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0059] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0060] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0061] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node. In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0062] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0063] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0064] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0065] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0066] Some embodiments described herein provide periodic location reporting. Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0067] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0068] The communication system 10 may may include intermediate network 30 that is in communication with access network 12 via connection 26. Intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0069] The communication system of FIG. 3 as a whole enables connectivity between one entities in system 10. Core network 14 may include one or more core network nodes such as location management function (LMF) node 15 (including indication unit 32) and node 17 (including requesting unit 34). A LMF node 15 is configured to include an indication unit 32 which is configured to perform one or more LMF node 15 functions as described herein. A node 17 is configured to include a request unit 34 which is configured to perform one or more node 17 functions as described herein.

[0070] Example implementations, in accordance with an embodiment, of the WD 22, network node 16, LMF node 15 and node 17 discussed in the preceding paragraphs will now be described with reference to FIG. 4. The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with one or more entities in system 10. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0071] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0072] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16.

[0073] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0074] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0075] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22. In providing the service to the user, the client application 92 may provide user data in response to the request data. The client application 92 may interact with the user to generate the user data that it provides.

[0076] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22.

[0077] The communication system 10 further includes LMF node 15 provided in a communication system 10 and including hardware 94 enabling it to communicate with network node 16. The hardware 94 may include a communication interface 96 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10. The communication interface 60 may be configured to facilitate a connection 66 to network node 16 and / or one or more other entities in system 10.

[0078] In the embodiment shown, the hardware 94 of LMF node 15 further includes processing circuitry 98. The processing circuitry 98 may include a processor 100 and a memory 102. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 98 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 100 may be configured to access (e.g., write to and / or read from) the memory 102, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 104 stored internally in, for example, memory 102, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the LMF node 15 via an external connection. The software 104 may be executable by the processing circuitry 98. The processing circuitry 98 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by LMF node 15. Processor 100 corresponds to one or more processors 100 for performing LMF node 15 functions described herein. The memory 102 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 104 may include instructions that, when executed by the processor 100 and / or processing circuitry 98, causes the processor 100 and / or processing circuitry 98 to perform the processes described herein with respect to LMF node 15. For example, processing circuitry 98 of the LMF node 15 may include indication unit 32 configured to that is configured to perform one or more LMF node 15 functions described herien.

[0079] Communication system 10 may include node 17 that comprises the same or similar hardware and software as LMF node 15. However, node 17 may include request unit 34 configured to perform one or more node 17 functions as described herein.

[0080] In some embodiments, the inner workings of the network node 16, WD 22, and LMF node 15 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

[0081] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0082] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0083] In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0084] Although FIGS. 3 and 4 show various “units” such as indication unit 32, and request unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0085] FIG. 5 is a flowchart of an example process in an LMF node 15 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 98 (including the indication unit 32), processor 100, and / or communication interface 96. LMF node 15 is configured to periodically receive (Block S100) location measurements from a wireless device 22 according to a periodic positioning report configuration of the wireless device 22, as described herein. LMF node 15 is configured to determine (Block S102) location estimates based on the location measurements, as described herein. LMF node 15 is configured to indicate (Block S104) the location estimates to one of a Location Services (LCS) client or Application Function (AF) node.

[0086] According to some embodiments, the LMF node 15 is further configured to initiate a periodic measurement request toward a network node using a NR Positioning Protocol A (NRPPa).

[0087] According to some embodiments, the LMF node 15 is further configured to initiate a Long Term Evolution (LTE) Positioning Protocol (Ipp) periodical reporting toward the wireless device for periodically receiving location measurements according to the periodic positioning report configuration.

[0088] FIG. 6 is a flowchart of another process in a LMF node 15 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 98 (including the indication unit 32), processor 100, and / or communication interface 96. LMF node 15 is configured to configure (Block S106) an access network node 16 to periodically report location measurements for a wireless device 22, as described herein. LMF node 15 is configured to periodically receive (Block S108), from the access network node 16, reports of location measurements according to the periodic reporting configuration at the access network node for the wireless device 22, as described herein. LMF node 15 is configured to determine (Block SI 10) location estimates based on the one or more periodic reports of location measurements obtained from the access network node 16, as described herein. LMF node 15 is configured to periodically transmit (Block SI 12) the location estimates to one of a Location Services, LCS, client or Application Function, AF, node, as described herein. According to one or more embodiments, the LMF node 15 is further configured to, after receiving a report that a location measurement session is terminated, initiate a procedure to locate and reconnect the wireless device to the access network node 16, as described herein.

[0089] According to one or more embodiments, the procedure is initiated at least in part by requesting that an application management function, AMF, node page the wireless device 22, and the location measurement session is terminated based on the wireless device 22 being unavailable or in a radio resource control, RRC, idle mode.

[0090] According to one or more embodiments, the LMF node 15 is further configured to, if the report of the location measurement indicates that one of an error occurred or no location measurement occurred, trigger another procedure to obtain the location measurements.

[0091] According to one or more embodiments, the LMF node 15 is further configured to receive a request, from the LCS client, for periodic reporting of location measurements for the wireless device 22, and the configuration of the access network node 16 to periodically report location measurements being in response to the request.

[0092] According to one or more embodiments, the configuration of the access network node 16 to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device 22, and transmitting the periodic reporting configuration to the access network 12.

[0093] According to one or more embodiments, the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

[0094] According to one or more embodiments, the periodic receiving, from the access network node 16, of reports of location measurements is configured to occur at a first periodicity, and the periodically transmitting the location estimates to one of the LCS client or the AF node is configured to occur at one of: the first periodicity; or a second periodicity different from the first periodicity.

[0095] According to one or more embodiments, the access network node 16 is one of an eNodeB, eNB, or a gNodeB, gNB.

[0096] FIG. 7 is a flowchart of an example process in a node 17 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of node 17 such as by one or more of processing circuitry 98 (including the request unit 34), processor 100 and / or communication interface 96. Node 17 is configured to request (Block S 114) reporting of positioning of a wireless device 22, where the reporting is at a first periodicity, as described herein. Node 17 is configured to receive (Block SI 16) the reporting of positioning from the wireless device 22 according to the first periodicity of reporting, as described herein.

[0097] Node 17 is further configured to modify the periodicity of the requested positioning based on wireless device motion. Node 17 is an Location Services (LCS) client or Application Function (AF) node.

[0098] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for periodic location reporting.

[0099] Some embodiments provide periodic location reporting. One or more functions described below may be performed by one or more entities of communication system 10 described above. For example, one or more functions described below may be performed by one or more elements of LMF node 15 such as one or more of processing circuitry 98, processor 100, indication unit 32, etc. In another example, one or more functions described below may be performed by one or more elements of node 17 (e.g., LCS client or AF node) described above.

[0100] FIGs. 8-9 are signaling diagrams according to some embodiments of the present disclosure. In particular, FIGs. 8-9 relates to 3GPP TS 23.273 and specifically to Deferred 5GC-MT-LR for periodic location events using NRPPa Periodic Measurement or Ipp periodical Reporting as described herein in accordance with one or more embodiments of the present disclosure. Reference to 3GPP TS 23.273 in the description below may refer to a version of of 3GPP TS 23.273 as modified and / or changed according to one or more embodiments of the present disclosure. Various steps in FIGs. 8-9 are described below.

[0101] Step 1. Deferred 5GC-MT-LR steps 1-13 are executed as described in clause 6.3.1 of 3GPP TS 23.273. AF or LCS clients or NF triggers periodic location event. Further, as described herein, the LCS Service Request provides periodic location reporting type and the time interval between successive location reports, and the total number of reports.

[0102] The step however is updated or modified in that the LCS client can also request positioning in certain periodicity (e.g., every 160ms, every Is, etc.). This allows tracking use cases. The client can get frequent updates and track the object. The client may also modify the periodicity request depending upon how rapidly the wireless device 22 is moving and depending upon the latency involved in obtaining the result. Step 2. LMF node 15 performs one or more of the positioning procedures as it is described in step 15 in clause 6.3.1 of 3GPP TS 23.273. LMF node 15, based on wireless device capability information received in this step and based on configuration, decides to perform NRPPa Periodic Measurements.

[0103] Purpose of this step, besides what is described in legacy procedure, is to get wireless device 22 capabilities. Based on wireless device 22 capabilities, the wireless device 22 probably does not support LCS Supplementary service for periodic event so the only option is to execute the new procedure.

[0104] Step 3. Deferred 5GC-MT-LR steps 18-21 are executed as described in clause 6.3.1 of 3GPP TS 23.273 with the following changes:

[0105] - The NRPPa periodic indication is added to step 18-20 to indicate Periodic Location Estimates are generated based on NRPPa Periodic Measurement. (H)GMLC stores NRPPa periodic indication.

[0106] Step 4 of FIG. 8 or Steps 4-1 to 4-2 of FIG. 9. LMF node 15, based on wireless device 22 capability information received in step 2, performs NRPPa Periodic Measurement Request (based on clause 6.11.2 in 3GPP TS 23.273) and / or Ipp periodical Reporting (based on 6.11.1 in 3GPP TS 23.273) or NRPPa Periodic Measurement E-CID Measurement Initiation (clause 8.2.1.1 in 3GPP TS 38.455). LMF node 15 uses the time interval between successive location reports, the total number of reports received in step 1 to setup periodicity and / or to setup NRPPa periodical report procedure. Further, according to one or more embodiments, LMF node 15 periodically receives location estimates or measurement from wireless device 22 via Ipp or periodically receive measurements from NG-RAN via NRPPa. Location related measurements used by LMF node 15 to calculate location estimates.

[0107] Steps 4-3 to 4-4: NG-RAN returns with E-CID Measurement Initiation Response (clause 8.2.1.2. in TS 38.455).

[0108] Steps 4-5 to 4-6:. LMF node 15 is receiving E-CID Measurement Report from NG- RAN periodically (clause 8.2.3.2 in TS 38.455). LMF node 15 uses Measurement Information to calculate Location Result.

[0109] NRPPa (3GPP TS 38.455) supports NG-RAN sending Measurement Reports periodically if LMF node 15 requested that. In this case, NG-RAN will execute measurement at the requested periodic and sends the measurement result to LMF node 15. Table 1

[0110] Table 1 is based on clause 9.1.1.1 of 3PP TS 38.455

[0111] LPP (3GPP TS 37.355) defines that wireless devices 22 can support periodicalReporting for certain positioning methods. For example “indicates that the target device supports periodicalReporting ofE-CID measurements .” This indicates that wireless device 22 can provide measuremetns periodically to LMF node 15 which is used by LMF node 15 to calaculate positioning estimates periodically. PeriodicalReportingCriteria ::= SEQUENCE { reportingAmount ENUMERATED { ral, ra2, ra4, ra8, ral6, ra32, ra64, ra-Infinity

[0112] } DEFAULT ra-Infinity, reportinginterval ENUMERATED { noPeriodicalReporting, riO-25, ri0-5, ril, ri2, ri4, ri8, ril 6, ri32, ri64

[0113] }

[0114] The above criteria is based on clause 6.4.2 of 3GPP TS 37.355

[0115] 5. LMF node 15 invokes Nlmf_Location_EventNotify service operation as described in step 28 in clause 6.3.1 of 3GPP TS 23.273 in order to transfer location information to VGMLC or (H)GMLC periodically according to one or more embodiments described herein. However, the step is updated or modified to obtain the periodical positioning of the wireless device 22.

[0116] 6. Deferred 5GC-MT-LR steps 29 is executed as described in clause 6.3.1 of 3GPP TS 23.273.

[0117] 7a.: Deferred 5GC-MT-LR steps 30a is executed as described in clause 6.3.1 of 3GPP TS 23.273.

[0118] 7b-l: Deferred 5GC-MT-LR steps 30b-l is executed as described in clause 6.3.1 of 3GPP TS 23.273.

[0119] 7b-2: Deferred 5GC-MT-LR steps 30b-2 is executed as described in clause 6.3.1 of 3GPP TS 23.273. The client is periodically provided the location.

[0120] 7c: Deferred 5GC-MT-LR steps 30c is executed as described in clause 6.3.1.

[0121] Steps between step 4-3 and 7c may be executed periodically.

[0122] LMF node 15 before step 4 (e.g., 4-1) invokes Namf_EventExposure_Subscribe to receive events from serving AMF about NG-RAN change using “RAN_Node” as LocationFilter.

[0123] When LMF node 15 receives from NG-RAN error causes (e.g., due to wireless device mobility to another NG-RAN node or wireless device 22 is released to CM-IDLE mode) that NG-RAN node is unable to provide the measurement results then LMF node 15 considers that the NRPPa periodic reporting is terminated by NG-RAN. The LMF node 15 may re-trigger a request for NR — a periodical reporting, considering the event notification from AMF which is subscribed by the LMF node 15 as described above.

[0124] Cancellation of Reporting of Periodic Events by an AF, an NF or External LCS Client or GMLC

[0125] Cancellation of Reporting of Periodic Events by an AF, an NF or External LCS Client or GMLC based on NRPPa Periodic Measurement executed as described in 6.3.3 with the following changes:

[0126] Steps from 4-3 to 4-6 are not executed based on NRPPa periodic indication provided by VGMLC in step 4-1. (i.e., wireless device 22’s related procedures are not executed)

[0127] When in step 4-2 LMF node 15 receives Namf_Location_CancelLocation, LMF node 15 stops NRRPa periodic measurement report by requesting E-CID Measurement Termination (clause 8.2.4.2 in 3GPP TS 38.455) and unsubscribe for AMF event. Further Embodiments:

[0128] • An LCS client may send an abort message for periodical reporting or may change the periodicity.

[0129] • The wireless device 22 may send a failure message to the LMF node 15 that the wireless device 22 is unable to perform periodical measurement or location reporting. In such case either the wireless device 22 or LMF node 15 may abort the procedure

[0130] • The LMF node 15 may select different periodicity than the LCS client: If LCS client requests positioning every Is, the LMF node 15 may configure the periodicity of 200ms to the wireless device 22 and could obtain 5 measurement samples and provide final output based upon averaging / filtering to the client. The LMF node 15 may change the periodicity depending upon if the positioning QoS in terms of accuracy is being met or not. However, the constraint is that LMF node 15 may always select periodicity less than what it has received from the client for the LPP wireless device 22 configuration.

[0131] • The LMF node 15 may also determine the periodicity based upon the wireless device 22 type; if the wireless device 22 type is low power high accuracy or (Reduced capability) Redcap wireless device 22 they may have a power constraint and in such case, the LMF node 15 may provide the power constraint issue to the LCS client via AMF node.

[0132] • The LCS client may further negotiate the periodical interval based upon wireless device 22 type (e.g., wireless device 22 capability, power constraint) with the NW (GMLC / LMF / AMF).

[0133] • The periodicity configuration is also dependent upon the transport delay. So, if in a certain deployment, the end to end message signal delay is Is then a periodicity less than Is is disallowed or prohibited.

[0134] LMF Change Procedure

[0135] The LMF Change procedure supports change of a serving LMF node 15 during a deferred 5GC-MT-LR procedure for Periodic Location Events based on NRPPa Periodic Measurement. LMF node 15 change may be initiated due to new NG-RAN or new serving AMF.

[0136] FIG. 10 is a diagram of another example signaling diagram for changing of a serving LMF node 15 for periodic events based on NRPPa Periodic Measurement according to one or more embodiments of the present disclosure. Step 1A. NG-RAN or AMF change happens, e.g., due to wireless device mobility in CM-CONNECTED state. The (new) AMF may trigger the event notification towards LMF node 15 (e.g., based on the event subscription as described above). When there is a change of AMF, the new AMF receives all event subscriptions from old AMF. The new AMF informs LMF node 15 about the new AMF address if the LMF node 15 has subscribed for the NG-RAN change event as described above and the LMF node 15 performs NRPPa Periodic E-CID Measurement Initiation towards new serving AMF.

[0137] Step 2A. [Conditional] LMF1 (e.g., LMF node 15-1) may evaluate and determine that it is unsuitable or unable to support location for the current UE NG-RAN and determine LMF2 (e.g., LMF node 15-2) as being a more suitable LMF node 15. LMF1 may already have LMF2 information, e.g., from previous NRF discovery or locally configured, otherwise LMF1 queries. LMF1 selects new LMF based on NG-RAN location based and other information as listed in clause 5.1.

[0138] Step 3 A. [Conditional] LMF1 invokes an Nlmf_Location_LocationContextTransfer Request service operation towards LMF2 to provide the current location context of the wireless device. The service operation includes the AMF identity and all the information originally received by LMF1 for the periodic location request either from the AMF or from an earlier serving LMF node 15 according to this procedure. LMF2 invokes Namf_EventExposure_Subscribe to receive events from serving AMF about NG-RAN change.

[0139] Step 4A. [Conditional] LMF2 informs LMF1 of the location context transfer operation results. LMF2 performs NRPPa Periodic E-CID Measurement Initiation.

[0140] Step 5 A. [Conditional] LMF1 releases all resources for the procedure and unsubscribe.

[0141] Therefore, one or more embodiments described herein relates to “Periodical Positioning Reporting” that utilizes NRPPa Periodic Measurement and / or Ipp periodical Reporting already supported in RAN specification in an efficient way so that the LCS client can be provided with periodical output on the location of wireless device. An SA2 LCS procedure is defined to calculate a more consecutive (periodic) location estimate.

[0142] The complex deferred location procedure may not be implemented mostly on wireless device side, but Ipp is, and NRPPa has only RAN dependency. Since one or more embodiments described herein has less dependency on the wireless device or is wireless device agnostic, one or more embodiments described herein provide a solution which can operate in most or all wireless devices which are deployed in a 5G network. LMF node 15 based on wireless device capabilities and internal configuration can decide the legacy deferred periodic location event or one or more embodiments can be executed as described herein.

[0143] One or more embodiments described herein provides one or more of the following advantages: providing lower latency. proving a wireless device agnostic solution.

[0144] Complexity is lower.

[0145] Periodic location report can be provided to LCS client or AF.

[0146] Tracking related use cases can be enabled

[0147] Some Examples

[0148] Example Al. A location management function, LMF, node 15 configured to: periodically receive location measurements from a wireless device 22 according to a periodic positioning report configuration of the wireless device 22; and determine location estimates based on the location measurements; and indicate the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

[0149] Example A2. The LMF node 15 of Example Al, wherein the LMF node 15 is further configured to initiate a periodic measurement request toward a network node using a NR Positioning Protocol A, NRPPa.

[0150] Example A3. The LMF node 15 of Example Al, wherein the LMF node 15 is further configured to initiate a Long Term Evolution, LTE, Positioning Protocol, Ipp, periodical reporting toward the wireless device 22 for periodically receiving location measurements according to the periodic positioning report configuration.

[0151] Example BL A method implemented in a location management function, LMF, node 15 , the method comprising: periodically receiving location measurements from a wireless device 22 according to a periodic positioning report configuration of the wireless device 22; and determining location estimates based on the location measurements; and indicating the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

[0152] Example B2. The method of Example Bl, further comprising initiating a periodic measurement request toward a network node 16 using a NR Positioning Protocol A, NRPPa. Example B3. The method of Example Bl, further comprising initiating a Long Term Evolution, LTE, Positioning Protocol, Ipp, periodical reporting toward the wireless device 22 for periodically receiving location measurements according to the periodic positioning report configuration.

[0153] Example Cl. A node 17 configured to: request reporting of positioning of a wireless device 22, the reporting being at a first periodicity; and receive the reporting of positioning from the wireless device 22 according to the first periodicity of reporting.

[0154] Example C2. The node 17 of Example Cl, wherein the node 17 is further configured to modify the periodicity of the requested positioning based on wireless device motion.

[0155] Example C3. The node 17 of Example Cl, wherein the node is an Location Services, LCS, client or Application Function, AF, node.

[0156] Example DI. A method implemented in a node, the method comprising: requesting reporting of positioning of a wireless device 22, the reporting being at a first periodicity; and receiving the reporting of positioning from the wireless device 22 according to the first periodicity of reporting.

[0157] Example D2. The method of Example DI, further comprising modifying the periodicity of the requested positioning based on wireless device motion.

[0158] Example D3. The method of Example DI, wherein the node is an Location Services, LCS, client or Application Function, AF, node.

[0159] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0160] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0161] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0162] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0163] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0164] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0165] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0166] Abbreviations that may be used in the preceding description include:

[0167] 5GC 5G Core

[0168] LCS Location Services

[0169] MO-LR Mobile Originated Location Request

[0170] MT-LR Mobile Terminated Location Request

[0171] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method implemented in a location management function, LMF, node (15), the method comprising: configuring (S106) an access network node (16) to periodically report location measurements for a wireless device (22) ; periodically receiving (S108), from the access network node (16), reports of location measurements according to the periodic reporting configuration at the access network node (16) for the wireless device (22); determining (SI 10) location estimates based on the one or more periodic reports of location measurements obtained from the access network node (16); and periodically transmitting (SI 12) the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

2. The method of Claim 1, further comprising, after receiving a report that a location measurement session is terminated, initiating a procedure to locate and reconnect the wireless device (22) to the access network node (16).

3. The method of Claim 2, wherein the procedure is initiated at least in part by requesting that an application management function, AMF, node page the wireless device (22); and the location measurement session is terminated based on the wireless device (22) being unavailable or in a radio resource control, RRC, idle mode.

4. The method of any one of Claims 1-3, further comprising, if the report of the location measurement indicates that one of an error occurred or no location measurement occurred, triggering another procedure to obtain the location measurements.

5. The method of any one of Claims 1-4, further comprising receiving a request, from the LCS client, for periodic reporting of location measurements for the wireless device (22); and the configuration of the access network node (16) to periodically report location measurements being in response to the request.

6. The method of any one of Claims 1-5, wherein the configuration of the access network node (16) to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device (22); and transmitting the periodic reporting configuration to the access network.

7. The method of any one of Claims 1-6, wherein the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

8. The method of any one of Claims 1-7, wherein the periodic receiving, from the access network node (16), of reports of location measurements is configured to occur at a first periodicity; and the periodically transmitting the location estimates to one of the LCS client or the AF node is configured to occur at one of: the first periodicity; or a second periodicity different from the first periodicity.

9. The method of any one of Claims 1-8, wherein the access network node (16) is one of an eNodeB, eNB, or a gNodeB, gNB.

10. A location management function, LMF, node (15) configured to: configure an access network node (16) to periodically report location measurements for a wireless device (22); periodically receive, from the access network node (16), reports of location measurements according to the periodic reporting configuration at the access network node (16) for the wireless device (22); determine location estimates based on the one or more periodic reports of location measurements obtained from the access network node (16); and periodically transmit the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

11. The LMF node (15) of Claim 10, wherein the LMF node (15) is further configured to, after receiving a report that a location measurement session is terminated,initiate a procedure to locate and reconnect the wireless device (22) to the access network node (16).

12. The LMF node (15) of Claim 11, wherein the procedure is initiated at least in part by requesting that an application management function, AMF, node page the wireless device (22); and the location measurement session is terminated based on the wireless device (22) being unavailable or in a radio resource control, RRC, idle mode.

13. The LMF node (15) of any one of Claims 10-12, wherein the LMF node (15) is further configured to, if the report of the location measurement indicates that one of an error occurred or no location measurement occurred, trigger another procedure to obtain the location measurements.

14. The LMF node (15) of any one of Claims 10-13, wherein the LMF node (15) is further configured to receive a request, from the LCS client, for periodic reporting of location measurements for the wireless device (22); and the configuration of the access network node to periodically report location measurements being in response to the request.

15. The LMF node (15) of any one of Claims 10-14, wherein the configuration of the access network node (16) to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device (22); and transmitting the periodic reporting configuration to the access network.

16. The LMF node (15) of any one of Claims 10-15, wherein the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

17. The LMF node (15) of any one of Claims 10-16, wherein the periodic receiving, from the access network node (16), of reports of location measurements is configured to occur at a first periodicity; andthe periodically transmitting the location estimates to one of the LCS client or the AF node is configured to occur at one of: the first periodicity; or a second periodicity different from the first periodicity.

18. The LMF node (15) of any one of Claims 10-17, wherein the access network node (16) is one of an eNodeB, eNB, or a gNodeB, gNB.

19. A computer readable storage medium (102) comprising instructions which, when executed by processing circuitry (98), cause the processing circuitry (98) to perform a method, the method comprising: configuring an access network node (16) to periodically report location measurements for a wireless device (22); periodically receiving, from the access network node (16), reports of location measurements according to the periodic reporting configuration at the access network node (16) for the wireless device (22); determining location estimates based on the one or more periodic reports of location measurements obtained from the access network node (16); and periodically transmitting the location estimates to one of a Location Services, LCS, client or Application Function, AF, node.

20. The computer readable storage medium (102) of Claim 19, wherein the configuration of the access network node (16) to periodically report location measurements comprises: determining the periodic reporting configuration based at least on wireless device capability of the wireless device (22); and transmitting the periodic reporting configuration to the access network; and the periodic reports of location measurements are received via one of a New Radio Positioning Protocol A, NRPPa, or Long Term Evolution, LTE, Positioning Protocol, 1pp.

Images