Periodic location reporting for delayed mobile terminal positioning requests (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 of a wireless device. Location measurement reports are periodically received from an access network node according to a periodic reporting configuration on the access network node for the wireless device. A location estimate is determined based on one or more periodic location measurement reports obtained from an access network node. The location estimate is periodically transmitted to one of a location service (LCS) client or an application function (AF) node.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and in particular to periodic location reporting. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) wireless communication systems. These systems provide a variety of capabilities, including broadband communication between network nodes (such as base stations) and mobile wireless devices (WDs), as well as communication between network nodes and between WDs. 3GPP is also developing standards for sixth-generation (6G) wireless communication networks.

[0003] The following discussion is based on 3GPP TS 23.273 v 18.2.0.

[0004] Delayed location request

[0005] Using a delayed location request, a Location Services (LCS) client or Application Function (AF) sends a location request for a target radio device (or group of target radio devices) to the Public Land Mobile Network (PLMN), expecting to receive a response at some future time (or multiple times) containing an event occurrence indication and location information related to a specific event associated with the target radio device (or group of target radio devices). In 3GPP TS 23.273 v 18.2.0, delayed location requests are only supported for Mobile Terminal Location Request (MT-LR).

[0006] Event Type The following event types are defined for delayed location requests.

[0007] a) Radio Device Availability: Any event in which the 5G Core Network (5GCN) has established contact with the radio device. This event is considered applicable when the radio device is temporarily unavailable due to user inactivity, temporary loss of radio connection, or separation of International Mobile Subscriber Identity (IMSI). The radio device availability event requires only one response to the LCS client / AF, after which the radio device availability event ends.

[0008] b) Area: An event where a wireless device enters, leaves, or remains within a predefined geographic area. At least one type of area event (i.e., entering, leaving, or remaining within an area) can be defined. An LCS client or AF can define a target area as a geographic region or a geopolitical name for a region. A PLMN can transform and define a target area as an identifier for one or more radio cells or tracking areas. An LCS client or AF can request additional checks to confirm that a wireless device is within a pre-configured target area. Area events can be reported only once or multiple times. Area event reports can include an indication that the event occurred. Location estimation can be included in the report. If a wireless device detects an area event but cannot send an event report (e.g., due to network inaccessibility or minimum reporting interval), it can send a report later if possible, regardless of whether the area event still applies to the current wireless device location. Area event reporting is controlled by a minimum reporting time and a maximum reporting time. The minimum reporting time defines the minimum allowed time between consecutive area events. The maximum reporting time defines the maximum time between consecutive reports. When a wireless device sends a report due to the maximum reporting time expiring, the wireless device indicates the maximum reporting time expiring as a trigger event. Maximum reporting time enables AF, LCS clients and Home Gateway Mobile Location Center (HGMLC) to continuously sense whether wireless devices continue to support events in the area (e.g., detecting whether area event reporting may be interrupted due to power failure of wireless devices).

[0009] Note: For more precise use of area events in certain scenarios, such as for smaller target areas, it may be useful if the LCS client / AF requests a location estimate from the wireless device and compares the location estimate with the target area.

[0010] c) Periodic Location: An event defined in the wireless device that causes a periodic timer to expire and activate location reporting. If the wireless device detects a periodic event but is unable to send an event report (e.g., because the wireless device is temporarily unable to access the network), it can send the report later if possible, and then start the periodic timer for the next event. Even with the reporting delay, the reporting duration for periodic location can be equal to the number of requested reports multiplied by the periodic interval.

[0011] d) Motion: An event in which a wireless device moves beyond a predefined straight-line distance from its previous location. Motion events may be reported only once or multiple times. Motion event reports may include an indication of the event occurring. Location estimation may also be included in the report if requested by the LCS client or AF. For consecutive motion event reports, motion is determined relative to the wireless device location corresponding to the immediately preceding event report (including event reports triggered by the expiration of the maximum reporting time). If a wireless device detects a motion event, but the event report is delayed (e.g., due to temporary network access failure), the report may be sent later if possible, regardless of whether the motion event still applies to the current wireless device location. Motion reporting is controlled by a minimum reporting time and a maximum reporting time. The minimum reporting time defines the minimum allowed time between consecutive event reports. The maximum reporting time defines the maximum time between consecutive 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 a triggering event. The maximum reporting time enables the AF, LCS client, and HGMLC to continuously sense whether the wireless device continues to support the motion event (e.g., detecting whether motion event reporting may be interrupted due to a power outage of the wireless device).

[0012] In 3GPP Rel-16, the delayed 5GC-MT-LR procedure for periodic, triggered, and radio device available location events is defined in Clause 6.3 of 3GPP TS 23.273.

[0013] In 3GPP Rel-18, the 5GC-MT-LR multi-location procedure for regulatory location services was introduced in Clause 6.1.3 of 3GPP TS23.273, which provides a low-complexity periodic / multi-location estimation scheme for regulatory use cases only.

[0014] Figure 1A-1C This is an example signaling diagram for delayed 5GC-MT-LR for periodic, triggered, and wireless device available location events.

[0015] 5GC-MT-LR multi-location process for regulatory location services Figure 2 This is a signaling diagram illustrating the extended procedure of the 5GC-MT-LR procedure for the regulatory location service as defined in Clause 6.1.1 of 3GPP TS 23.273.

[0016] This process is applicable to providing LCS clients with multiple location estimates of the target wireless device.

[0017] However, current delayed localization solutions in LCS rely entirely on wireless devices. Performing periodic localization requires the functionality of the wireless device. This reliance on wireless devices complicates the process and consumes limited computing and / or power resources. Summary of the Invention

[0018] Some embodiments advantageously provide methods, systems, and apparatus for periodic location reporting.

[0019] However, as mentioned above, the current delayed location solution in LCS relies entirely on the wireless device. Performing periodic location requires the functionality of the wireless device. This reliance on the wireless device complicates the process. Therefore, an alternative periodic delayed location solution is needed that can operate in a way that is independent of the wireless device. The current location process does not support this even when LCS clients request periodic location reports.

[0020] The existing system is unable to provide periodic location reports (location) to the client.

[0021] Periodic events can be configured for wireless devices to perform delayed location procedures; however, it is not possible to periodically configure and acquire location information.

[0022] Based on one or more embodiments described herein, a novel process is defined (designed) that allows a network (LMF node) to configure periodic location reports from different entities, such as the Next Generation Radio Access Network (NG-RAN) or from wireless devices. In other words, a less complex 3GPP process is beneficial for periodic location event flows. One or more embodiments utilize RAN-defined NR Location Protocol A (NRPPa) periodic measurement reports and LTE Location Protocol (LPP) periodic reports for commercial use cases.

[0023] Alternatives Figure 1A-1C In step 16, the radio device is configured to use the LCS supplemental service for reporting periods. The LMF node can use NRPPa to initiate periodic measurement requests to the NG-RAN, or initiate LPP periodic reports to the radio device according to the required period, such as... Figure 8 As described in step 4. In one or more embodiments, the LMF node can decide, based on the radio device capabilities, whether to initiate periodic measurement requests to the NG-RAN using NRPPa, or to initiate periodic LPP reports to the radio device at the required intervals. In one or more embodiments, the LMF node can use periodically received measurements or location estimates to forward the location estimates to the GMLC using Nlmf_Location_EventNotify. The one or more embodiments described herein have a negligible or no impact on the RAN.

[0024] According to one aspect of this disclosure, a method is provided implemented in a Location Management Function (LMF) node. An access network node is configured to periodically report location measurements for wireless devices, as described herein. Location measurement reports are periodically received from the access network node according to the periodic reporting configuration for wireless devices at the access network node, as described herein. A location estimate is determined based on one or more periodic location measurement reports obtained from the access network node, as described herein. The location estimate is periodically transmitted to either a Location Services (LCS) client or an Application Function (AF) node, as described herein.

[0025] According to one or more embodiments of this aspect, upon receiving a report of the location measurement session termination, a process is initiated to locate the wireless device and reconnect it to the access network node.

[0026] According to one or more embodiments of this aspect, the process is initiated at least in part by requesting the Application Management Function (AMF) node to page the radio device, and terminated on the grounds that the radio device is unavailable or in Radio Resource Control (RRC) idle mode.

[0027] According to one or more embodiments of this aspect, if the location measurement report indicates either an error or no location measurement has occurred, another process for obtaining the location measurement is triggered.

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

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

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

[0031] According to one or more embodiments of this aspect, periodically receiving location measurement reports from an access network node is configured to occur in a first period; and periodically transmitting location estimates to one of the LCS clients or AF nodes is configured to occur in one of the following: the first period; or a second period different from the first period.

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

[0033] According to another aspect of this 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 location measurement reports from the access network node according to the periodic reporting configuration for the wireless device at the access network node; determine a location estimate based on one or more periodic location measurement reports obtained from the access network node; and periodically transmit the location estimate to one of a Location Services (LCS) client or an Application Function (AF) node.

[0034] According to one or more embodiments of this aspect, the LMF node is also configured to initiate a process of locating the wireless device and reconnecting it to the access network node after receiving a report of the location measurement session termination.

[0035] According to one or more embodiments of this aspect, the process is initiated at least in part by requesting the Application Management Function (AMF) node to page the radio device, and terminated on the grounds that the radio device is unavailable or in Radio Resource Control (RRC) idle mode.

[0036] According to one or more embodiments of this aspect, the LMF node is also configured to trigger another process to obtain a location measurement if the location measurement report indicates either an error or no location measurement has occurred.

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

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

[0039] According to one or more embodiments of this aspect, periodic location measurement reports are received via one of the New Radio Positioning Protocol A, NRPPa, or Long Term Evolution (LTE) Positioning Protocol LPP.

[0040] According to one or more embodiments of this aspect, periodically receiving location measurement reports from an access network node is configured to occur in a first period, and periodically transmitting location estimates to one of the LCS clients or AF nodes is configured to occur in one of the following: the first period; or a second period different from the first period.

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

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

[0043] According to one or more embodiments of this aspect, the configuration for an access network node to periodically report location measurements includes: determining the periodic reporting configuration based at least on the radio device capabilities of the radio device, transmitting the periodic reporting configuration to the access network, and the periodic location measurement reports being received via one of the New Radio Positioning Protocol A, NRPPa, or Long Term Evolution (LTE) Positioning Protocol LPP. Attached Figure Description

[0044] A more complete understanding of this embodiment, along with its accompanying advantages and features, will be more readily apparent by referring to the following detailed description and the accompanying drawings, wherein: Figure 1A-1C It is a delayed 5GC-MT-LR signaling diagram for periodic, triggered, and wireless device available location events; Figure 2 This is a signaling diagram illustrating the extended procedure for the 5GC-MT-LR procedure for the regulatory location service as defined in Clause 6.1.1; Figure 3 This is a schematic diagram of an example network architecture based on the principles of this disclosure; Figure 4 According to some embodiments of this disclosure Figure 3 A block diagram of each entity; Figure 5 This is a flowchart of an example process in a node according to some embodiments of this disclosure; Figure 6 This is a flowchart of another example process in a node according to some embodiments of this disclosure; Figure 7 This is a flowchart of an example process in another node of some embodiments of this disclosure; Figure 8 These are signaling diagrams based on some embodiments of this disclosure; Figure 9 This is another signaling diagram according to some embodiments of this disclosure; and Figure 10 This is another signaling diagram according to some embodiments of the present disclosure. Detailed Implementation

[0045] Before describing the exemplary embodiments in detail, it should be noted that these embodiments primarily relate to combinations of apparatus components and processing steps associated with periodic location reporting. Therefore, in the accompanying drawings, components are indicated by conventional symbols where appropriate, and only those specific details relevant to understanding the embodiments are shown so as not to obscure this disclosure due to details that would be obvious to those skilled in the art who would benefit from the description herein. Throughout the specification, the same numerals refer to the same elements.

[0046] The relational terms used herein, such as “first” and “second,” “top” and “bottom,” are used only to distinguish one entity or element from another, and do not necessarily require or imply any physical or logical relationship or order between these entities or elements. The terms used herein are used only to describe particular embodiments and are not intended to limit the concepts described herein. The singular forms “a,” “an,” and “the” used herein also include the plural forms unless the context clearly indicates otherwise. Further understanding is that the terms “comprising,” “including,” “including,” and / or “comprising” as used herein indicate the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0047] In the embodiments described herein, the term "communication" and the like can be used to refer to electrical or data communication, which may be achieved, for example, through physical contact, induction, electromagnetic radiation, radio signals, infrared signals, or optical signals. Those skilled in the art will understand that multiple components can interoperate, and modifications and variations in the implementation of electrical and data communication are possible.

[0048] In some embodiments described herein, the terms “coupled,” “connected,” etc., may be used herein to indicate a connection, although not necessarily a direct one, and may include wired and / or wireless connections.

[0049] As used herein, the term "network node" can refer to any type of network node included in a radio network, and may also include base stations (BS), radio base stations, base transceiver stations (BTS), base station controllers (BSC), radio network controllers (RNC), g node Bs (gNB), evolved node Bs (eNB or eNodeB), node Bs, multi-standard radio (MSR) radio nodes (such as MSR BS), multi-cell / multicast coordination entities (MCE), integrated access and backhaul (IAB) nodes, relay nodes, donor node control relays, radio access points (AP), transmission points, transmission nodes, remote radio units (RRU), remote radio heads (RRH), core network nodes (e.g., mobility management entities (MME), ad hoc network (SON) nodes, coordination nodes, location nodes, MDT nodes, etc.), external nodes (e.g., third-party nodes, nodes outside the current network), nodes in distributed antenna systems (DAS), spectrum access system (SAS) nodes, network element management systems (EMS), etc. Network nodes may also include test equipment. The term “radio node” as used in this article can also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0050] In some embodiments, the non-limiting terms “wireless device (WD)” or “user equipment (UE)” are used interchangeably. A WD as used herein can be any type of wireless device capable of communicating with network nodes or other WDs via radio signals, such as a wireless device (WD). A WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smartphone, an embedded laptop (LEE), a laptop computer mount device (LME), a USB dongle, a client device (CPE), an Internet of Things (IoT) device, or a narrowband Internet of Things (NB-IoT) device, etc.

[0051] Furthermore, in some embodiments, the generic term "radio network node" is used. It can be any type of radio network node, including base stations, wireless base stations, base transceivers, base station controllers, network controllers, RNCs, evolved Node Bs (eNBs), Node Bs, gNBs, multi-cell / multicast coordination entities (MCEs), IAB nodes, relay nodes, access points, wireless access points, remote radio units (RRUs), and remote radio heads (RRHs).

[0052] Please note that although terms from a particular wireless system, such as 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be construed as limiting the scope of this disclosure to those systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Global Microwave Access Interoperability (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the concepts covered in this disclosure.

[0053] Please also note that the functions performed by wireless devices or network nodes as described herein can be distributed across multiple wireless devices and / or network nodes. In other words, the functions of network nodes and wireless devices described herein are not limited to being performed by a single physical device, but can actually be distributed across multiple physical devices.

[0054] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It should also be understood that the terms used herein shall be interpreted as consistent with their meaning in the context of this specification and the relevant field, and shall not be interpreted in an idealized or overly formal manner unless expressly defined herein.

[0055] Some of the embodiments described herein provide periodic location reports.

[0056] Referring again to the accompanying drawings, the same elements are indicated by the same reference numerals. Figure 3 A schematic diagram of a communication system 10 according to an embodiment is shown, such as a 3GPP-type cellular network supporting standards such as LTE and / or NR (5G), comprising an access network 12 (such as a radio access network) and a core network 14. The access network 12 includes multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first radio device (WD) 22a located in coverage area 18a is configured to wirelessly connect to or be paged by a corresponding network node 16a. A second WD 22b located in coverage area 18b can wirelessly connect to a corresponding network node 16b. Although multiple WDs 22a and 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is located within the coverage area or a single WD is connected to the corresponding network node 16. It should be noted that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0057] Furthermore, it is envisioned that WD22 can communicate simultaneously with more than one network node 16 and more than one type of network node 16, and / or be configured to communicate individually. For example, WD22 can have dual connectivity with LTE-enabled network nodes 16 and the same or different network nodes 16 supporting NR. For example, WD22 can communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0058] Communication system 10 may include an intermediate network 30 that communicates with access network 12 via connection 26. Intermediate network 30 may be a combination of one or more of a public network, a private network, or a hosted network. If present, intermediate network 30 may be a backbone network or the Internet. In some embodiments, intermediate network 30 may include two or more subnets (not shown).

[0059] Figure 3 The communication system as a whole enables connectivity between the various 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 request unit 34). LMF node 15 is configured to include indication unit 32, which is configured to perform one or more LMF node 15 functions as described herein. Node 17 is configured to include request unit 34, which is configured to perform one or more node 17 functions as described herein.

[0060] Now refer to Figure 4 The description describes an example implementation of WD 22, network node 16, LMF node 15, and node 17 discussed in the preceding paragraphs according to one embodiment. The communication system 10 also includes network node 16, which is provided in the communication system 10 and includes hardware 58 enabling it to communicate with one or more entities within the system 10. Hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections with interfaces of different communication devices in the communication system 10; and a radio interface 62 for establishing and maintaining at least one wireless connection 64 with WD 22 located within the coverage area 18 served by network node 16. Radio interface 62 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. Connection 66 may be direct or may be via the core network 14 of the communication system 10 and / or via one or more intermediate networks 30 outside the communication system 10.

[0061] In the illustrated embodiment, the hardware 58 of network node 16 also includes processing circuitry 68. Processing circuitry 68 may include processor 70 and memory 72. Specifically, in addition to or replacing the processor (e.g., a central processing unit) and memory, processing circuitry 68 may also include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) for executing instructions. Processor 70 may be configured to access (e.g., write to and / or read from) memory 72, which may include any type of volatile and / or non-volatile memory, such as 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).

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

[0063] The communication system 10 also includes the aforementioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the current coverage area 18 of the WD 22. The radio interface 82 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0064] The hardware 80 of the WD 22 also includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. Specifically, in addition to, or in lieu of, a processor (e.g., a central processing unit) and memory, processing circuitry 84 may also include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) for executing instructions. Processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any type of volatile and / or non-volatile memory, such as 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).

[0065] Therefore, WD 22 may also include software 90, which is stored, for example, in memory 88 of WD 22, or in external memory accessible to WD 22 (e.g., a database, storage array, network storage device, etc.). Software 90 may be executed by processing circuitry 84. Software 90 may include a client application 92. Client application 92 can be used to provide services to human or non-human users through WD 22. In providing services to users, client application 92 may respond to requests for user data. Client application 92 may interact with users to generate the user data it provides.

[0066] 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, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD 22 described herein. WD 22 includes memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may contain instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22.

[0067] The communication system 10 also includes an LMF node 15, which is provided in the communication system 10 and includes hardware 94 that enables it to communicate with network node 16. Hardware 94 may include a communication interface 66 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 10. Communication interface 66 may be configured to facilitate connections 66 with network node 16 and / or one or more other entities in system 10.

[0068] In the illustrated embodiment, the hardware 94 of LMF node 15 also includes processing circuitry 98. Processing circuitry 98 may include processor 100 and memory 102. Specifically, in addition to or replacing the processor (e.g., a central processing unit) and memory, processing circuitry 98 may also include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits) for executing instructions. Processor 100 may be configured to access (e.g., write to and / or read from) memory 102, which may include any type of volatile and / or non-volatile memory, such as 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). Therefore, network node 16 also has software 104, which is internally stored, for example, in memory 102, or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by external connections to LMF node 15. Software 104 may be executed by processing circuitry 98. 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 executed, for example, by LMF node 15. Processor 100 corresponds to one or more processors 100 for performing the functions of LMF node 15 described herein. Memory 102 is configured to store the data, program software code, and / or other information described herein. In some embodiments, software 104 may include instructions that, when executed by processor 100 and / or processing circuitry 98, cause processor 100 and / or processing circuitry 98 to perform the processes described herein concerning LMF node 15. For example, processing circuitry 98 for LMF node 15 may include instruction unit 32 configured to perform one or more LMF node 15 functions described herein.

[0069] The communication system 10 may include node 17, which includes 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 of the node 17 functions as described herein. In some embodiments, the internal operation of network node 16, WD 22, and LMF node 15 may be as follows: Figure 4 As shown, and independently, the surrounding network topology can be Figure 3 shown.

[0070] The wireless connection 64 between WD22 and network node 16 conforms to the teachings of the embodiments described in this disclosure. More precisely, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user wait times, relaxed file size limits, improved responsiveness, and extended battery life.

[0071] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon one or more embodiments. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured and / or its processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from WD 22.

[0072] In some embodiments, WD 22 is configured to and / or include a radio interface 82 and / or processing circuitry 84, which is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16.

[0073] although Figure 3 and Figure 4 The diagram shows various "units" (such as instruction unit 32 and request unit 34) located within their respective processors, but it is conceivable that these units could be implemented such that a portion of them is stored in corresponding memories within the processing circuitry. In other words, these units could be implemented in hardware or as a combination of hardware and software within the processing circuitry.

[0074] Figure 5 This is a flowchart of an example process in LMF node 15 according to some embodiments of this disclosure. One or more blocks described herein may be performed by one or more elements of network node 16, such as one or more of processing circuitry 98 (including indication unit 32), processor 100, and / or communication interface 96. LMF node 15 is configured to periodically receive (block S100) location measurements from wireless device 22 based on periodic location reports from wireless device 22, as described herein. LMF node 15 is configured to determine (block S102) a location estimate based on the location measurements, as described herein. LMF node 15 is configured to indicate the location estimate (block S104) to one of the location service (LCS) client or application function (AF) nodes.

[0075] According to some embodiments, LMF node 15 is also configured to initiate periodic measurement requests to network nodes using NR Location Protocol A (NRPPa).

[0076] According to some embodiments, LMF node 15 is also configured to initiate Long Term Evolution (LTE) Positioning Protocol (LPP) periodic reports to wireless devices to periodically receive location measurements based on the periodic positioning reports.

[0077] Figure 6 This is a flowchart of another process in LMF node 15 according to some embodiments of this disclosure. One or more blocks described herein may be performed by one or more elements of network node 16, such as one or more of processing circuitry 98 (including indication unit 32), processor 100, and / or communication interface 96. LMF node 15 is configured (block S106) to configure access network node 16 to periodically report location measurements for wireless device 22, as described herein. LMF node 15 is configured to periodically receive location measurement reports from access network node 16 based on the periodic reporting configuration for wireless device 22 at the access network node (block S108), as described herein. LMF node 15 is configured to determine a location estimate based on one or more periodic location measurement reports obtained from access network node 16 (block S110), as described herein. LMF node 15 is configured to periodically transmit the location estimate (block S112) to one of location service (LCS) client or application function (AF) nodes, as described herein.

[0078] According to one or more embodiments, LMF node 15 is also configured to initiate a process of locating the wireless device and reconnecting it to access network node 16 after receiving a report of the location measurement session termination, as described herein.

[0079] According to one or more embodiments, the process is initiated at least in part by requesting an Application Management Function (AMF) node to page the wireless device 22, and terminated on the grounds that the wireless device 22 is unavailable or in Radio Resource Control (RRC) idle mode.

[0080] According to one or more embodiments, LMF node 15 is also configured to trigger another process to obtain a location measurement if the location measurement report indicates either an error or no location measurement has occurred.

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

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

[0083] According to one or more embodiments, periodic location measurement reports are received via either the New Radio Positioning Protocol A (NRPPa) or the Long Term Evolution (LTE) Positioning Protocol (LPP).

[0084] According to one or more embodiments, periodically receiving location measurement reports from access network node 16 is configured to occur in a first period, and periodically transmitting location estimates to one of the LCS clients or AF nodes is configured to occur in one of the following: the first period; or a second period different from the first period.

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

[0086] Figure 7 This is a flowchart of an example process in node 17 according to some embodiments of this disclosure. One or more blocks described herein may be executed by one or more elements of node 17, such as one or more of processing circuitry 98 (including request unit 34), processor 100, and / or communication interface 96. Node 17 is configured to request (block S 114) a location report from wireless device 22, wherein the report is received according to a first period, as described herein. Node 17 is configured to receive (block S 116) a location report from wireless device 22 according to the first period of the report, as described herein.

[0087] Node 17 is also configured to periodically request location based on wireless device motion modification. Node 17 is a Location Services (LCS) client or Application Function (AF) node.

[0088] The general process flow of the arrangements of this disclosure has been described and examples of hardware and software arrangements for implementing the processes and functions of this disclosure have been provided. The following sections provide details and examples of arrangements for periodic location reporting.

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

[0090] Figure 8-9 These are signaling diagrams based on some embodiments of this disclosure. Specifically, Figure 8-9This relates to 3GPP TS 23.273, specifically to the delay 5GC-MT-LR of periodic positioning events using NRPPa periodic measurements or LPP periodic reporting as described herein according to one or more embodiments of this disclosure. References to 3GPP TS 23.273 in the following description may refer to versions of 3GPP TS 23.273 modified and / or altered according to one or more embodiments of this disclosure. The following will describe... Figure 8-9 Each step in the process.

[0091] Step 1. Perform delayed 5GC-MT-LR steps 1-13 as described in Clause 6.3.1 of 3GPP TS 23.273. The AF or LCS client or NF triggers a periodic location event. Additionally, as described herein, the LCS service request provides the periodic location report type, the time interval between consecutive location reports, and the total number of reports.

[0092] However, this step has been updated or modified so that LCS clients can also request location at specific intervals (e.g., every 160 milliseconds, every 1 second, etc.). This allows for tracking use cases. Clients can frequently obtain updates and track objects. Clients can also modify the periodic requests based on the moving speed of the wireless device 22 and the latency involved in obtaining the results.

[0093] Step 2. LMF node 15 executes one or more positioning procedures, as described in step 15 of Clause 6.3.1 of 3GPP TS 23.273. Based on the radio device capability information received in this step and based on the configuration, LMF node 15 determines to perform NRPPa periodic measurements.

[0094] In addition to the content described in the traditional process, the purpose of this step is to obtain the capabilities of wireless device 22. Based on the capabilities of wireless device 22, wireless device 22 may not support LCS supplemental services for periodic events, so the only option is to execute the new process.

[0095] Step 3. Delay 5GC-MT-LR steps 18-21 as described in Clause 6.3.1 of 3GPP TS 23.273, with the following changes: - Add the NRPPa period indicator to steps 18-20 to indicate that the periodic position estimate is generated based on the NRPPa periodic measurement. (H) The GMLC stores the NRPPa period indicator.

[0096] Figure 8 Step 4 or Figure 9Steps 4-1 to 4-2. Based on the capability information of the radio device 22 received in step 2, LMF node 15 executes an NRPPa periodic measurement request (based on clause 6.11.2 of 3GPP TS 23.273) and / or an LPP periodic report (based on clause 6.11.1 of 3GPP TS 23.273) or an NRPPa periodic measurement E-CID measurement initiation (clause 8.2.1.1 of 3GPP TS 38.455). LMF node 15 uses the time interval between consecutive location reports and the total number of reports received in step 1 to set the period and / or set the NRPPa periodic reporting procedure. Furthermore, according to one or more embodiments, LMF node 15 periodically receives location estimates or measurements from the radio device 22 via LPP, or periodically receives measurements from the NG-RAN via NRPPa. LMF node 15 uses location-related measurements to calculate the location estimate.

[0097] Steps 4-3 to 4-4: NG-RAN returns an E-CID measurement initiation response (section 8.2.1.2 in TS 38.455).

[0098] Steps 4-5 to 4-6: LMF node 15 periodically receives E-CID measurement reports from NG-RAN (Section 8.2.3.2 of TS 38.455). LMF node 15 uses the measurement information to calculate the positioning results.

[0099] NRPPa (3GPP TS 38.455) supports NG-RAN sending measurement reports periodically if requested by LMF node 15. In this case, NG-RAN will perform measurements according to the requested period and send the measurement results to LMF node 15.

[0100] Table 1

[0101] Table 1 is based on Clause 9.1.1.1 of 3PP TS 38.455. LPP (3GPP TS 37.355) defines that wireless device 22 can support periodic reporting of certain positioning methods. For example, " Periodic reporting indicating that the target device supports E-CID measurements This indicates that wireless device 22 can periodically provide measurement data to LMF node 15, which can use this data to periodically calculate positioning estimates.

[0102] PeriodicalReportingCriteria ::=SEQUENCE { reportingAmountENUMERATED { ra1, ra2, ra4, ra8, ra16, ra32, ra64, ra-Infinity DEFAULT ra-Infinity, reportingIntervalENUMERATED { noPeriodicalReporting,ri0-25, ri0-5, ri1, ri2, ri4, ri8, ri16, ri32, ri64 } The above standard is based on Clause 6.4.2 of 3GPP TS 37.355. 5. LMF node 15 invokes the Nlmf_Location_EventNotify service operation, as described in step 28 of Clause 6.3.1 of 3GPP TS 23.273, to periodically transmit location information to the VGMLC or (H)GMLC according to one or more embodiments described herein. However, this step has been updated or modified to obtain the periodic location of wireless device 22.

[0103] 6. Delay 5GC-MT-LR step 29 as described in section 6.3.1 of 3GPP TS 23.273.

[0104] 7a.: Delay 5GC-MT-LR step 30a and perform it as described in Clause 6.3.1 of 3GPP TS 23.273.

[0105] 7b-l: Delay 5GC-MT-LR step 30b-l as described in Clause 6.3.1 of 3GPP TS 23.273.

[0106] 7b-2: Delayed 5GC-MT-LR step 30b-2 is performed as described in Clause 6.3.1 of 3GPP TS 23.273. The client will periodically provide the location.

[0107] 7c: Delay 5GC-MT-LR step 30c as described in section 6.3.1.

[0108] The steps between steps 4-3 and 7c can be performed periodically.

[0109] LMF node 15 calls Namf_EventExposure_Subscribe before step 4 (e.g., 4-1) to receive events about NG-RAN changes from the service AMF using “RAN_Node” as a location filter.

[0110] When LMF node 15 receives an error message from NG-RAN (e.g., due to the radio device moving to another NG-RAN node, or radio device 22 being released to CM-IDLE mode), causing the NG-RAN node to be unable to provide measurement results, LMF node 15 considers that NRPPa periodic reporting has been terminated by NG-RAN. LMF node 15 may consider the event notifications from AMF that LMF node 15 has subscribed to as described above, and re-trigger the request for NR-periodic reporting.

[0111] Cancellation of periodic event reporting by AF, NF, external LCS clients, or GMLC Cancellation of periodic event reporting by AF, NF, or external LCS clients or GMLC based on NRPPa periodic measurements shall be performed as described in 6.3.3, with the following changes: - Based on the NRPPa cycle indication provided by VGMLC in step 4-1, steps 4-3 to 4-6 are not executed. (That is, the relevant procedures of wireless device 22 are not executed.) - In step 4-2, when LMF node 15 receives Namf_Location_CancelLocation, LMF node 15 stops NRRPa periodic measurement reporting and unsubscribes from AMF events by requesting E-CID measurement termination (section 8.2.4.2 in 3GPP TS 38.455).

[0112] Further examples: • LCS clients can send a message to stop periodic reporting, or they can change the period.

[0113] • Wireless device 22 may send a failure message to LMF node 15, indicating that wireless device 22 is unable to perform periodic measurements or location reporting. In this case, either wireless device 22 or LMF node 15 may abort the process.

[0114] • LMF node 15 can choose a different period than the LCS client: If the LCS client requests location every 1 second, LMF node 15 can configure a period of 200ms to the radio device 22, acquire 5 measurement samples, and then provide the final output to the client based on averaging / filtering. LMF node 15 can change the period based on whether the location service quality (QoS) is satisfied in terms of accuracy. However, the limitation is that the period selected by LMF node 15 must always be less than the period it receives from the client configured for LPP radio device 22.

[0115] • LMF node 15 can also determine the period based on the type of wireless device 22; if the type of wireless device 22 is low-power high-precision or (reduced capability) Redcap wireless device 22, they may have power limitations, in which case LMF node 15 can provide power limitation information to LCS clients through the AMF node.

[0116] • The LCS client can also negotiate the cycle interval with the NW (GMLC / LMF / AMF) based on the type of wireless device 22 (e.g., wireless device 22 capabilities, power limitations).

[0117] • Period configuration also depends on transmission latency. Therefore, if the end-to-end message signaling latency is 1 second in a certain deployment, periods shorter than 1 second are not allowed or prohibited.

[0118] LMF Change Process The LMF change procedure supports changing the serving LMF node 15 during the delayed 5GC-MT-LR procedure for periodic location events based on NRPPa periodic measurements. Changes to LMF node 15 may be initiated due to a new NG-RAN or a new serving AMF.

[0119] Figure 10 This is another example signaling diagram for LMF node 15 of the periodic event change service, based on NRPPa periodic measurements, according to one or more embodiments of this disclosure.

[0120] Step 1A. An NG-RAN or AMF change occurs, for example due to radio device mobility in CM-CONNECTED state. The (new) AMF can trigger an event notification to LMF node 15 (e.g., based on event subscriptions as described above). When an AMF changes, the new AMF receives all event subscriptions from the old AMF. If LMF node 15 has subscribed to the NG-RAN change event as described above, the new AMF informs LMF node 15 of the new AMF address, and LMF node 15 initiates an NRPPa periodic E-CID measurement to the new serving AMF.

[0121] Step 2A. [Conditions] LMF1 (e.g., LMF node 15-1) may evaluate and determine that it is unsuitable or unable to support the current UE NG-RAN location, and determine that LMF2 (e.g., LMF node 15-2) is a more suitable LMF node 15. LMF1 may already have information about LMF2, such as from previous NRF discovery or local configuration; otherwise, LMF1 will perform a query. LMF1 selects a new LMF based on the NG-RAN location and other information listed in Section 5.1.

[0122] Step 3A. [Conditions] LMF1 calls Nlmf_Location_LocationContextTransfer to LMF2 to request a service operation to provide the current location context of the radio device. This service operation includes the AMF identifier and all information previously received by LMF1 for periodic location requests, which, according to this procedure, comes from the AMF or the previous serving LMF node 15. LMF2 calls Namf_EventExposure_Subscribe to receive events from the serving AMF regarding NG-RAN changes.

[0123] Step 4A. [Conditions] LMF2 notifies LMF1 of the location context transmission operation result. LMF2 initiates NRPPa periodic E-CID measurement.

[0124] Step 5A. [Condition] LMF1 releases all resources of this process and unsubscribes.

[0125] Therefore, one or more embodiments described herein relate to "periodic location reporting" that efficiently utilizes NRPPa periodic measurements and / or LPP periodic reporting already supported in the RAN specification to provide LCS clients with periodic outputs regarding the location of wireless devices. The SA2 LCS procedure is defined for calculating more continuous (periodic) location estimates.

[0126] Complex delayed location processes may not be primarily implemented on the radio device side, but LPP can, while NRPPa relies solely on the RAN. Because one or more embodiments described herein have low or no dependence on radio devices, they provide a solution that can operate on most or all radio devices deployed in a 5G network. The LMF node 15 can determine conventional delayed periodic location events based on radio device capabilities and internal configuration, or it can perform one or more embodiments as described herein.

[0127] One or more embodiments described herein provide one or more of the following advantages: - Provides lower latency.

[0128] - Provide solutions that are independent of wireless devices.

[0129] - Low complexity.

[0130] - It can provide periodic location reports to LCS clients or AF.

[0131] - Enables tracking of related use cases Some examples Example A1. Location Management Function, LMF, Node 15 is configured as follows: According to the periodic location reporting configuration of the wireless device 22, position measurements are periodically received from the wireless device 22; and A position estimate is determined based on the position measurement; and The location estimate is indicated to one of the location service, LCS, client or application function, AF, or node.

[0132] Example A2. Based on the LMF node 15 of Example A1, wherein the LMF node 15 is also configured to initiate periodic measurement requests to network nodes using NR Positioning Protocol A, NRPPa.

[0133] Example A3. According to Example A1, LMF node 15, wherein the LMF node 15 is further configured to initiate Long Term Evolution, LTE, Location Protocol, LPP, Periodic Report to the wireless device 22 to periodically receive location measurements based on the Periodic Location Report.

[0134] Example B1. A method implemented in the location management function, LMF, node 15, which includes: According to the periodic location reporting configuration of the wireless device 22, position measurements are periodically received from the wireless device 22; and A position estimate is determined based on the position measurement; and The location estimate is indicated to one of the Location Service (LCS) clients or the Application Function (AF) nodes.

[0135] Example B2. The method of Example B1 also includes using NR Positioning Protocol A, NRPPa, to initiate periodic measurement requests to network node 16.

[0136] Example B3. The method according to Example B1 further includes initiating a Long Term Evolution (LTE), Location Protocol, LPP, Periodic Report to the wireless device 22 to configure periodic reception of location measurements based on the Periodic Location Report.

[0137] Example C1. Node 17 is configured as follows: Request a location report from wireless device 22, the report having a first cycle; and Location reports are received from the wireless device 22 according to the first cycle of the report.

[0138] Example C2. According to node 17 of example C1, wherein node 17 is further configured to modify the period of the requested location based on the movement of the wireless device.

[0139] Example C3. Based on node 17 of example C1, where the node is a location service, LCS, client or application function, AF, node.

[0140] Example D1. A method implemented in a node, which includes: Request a location report from wireless device 22, the report having a first cycle; and Location reports are received from wireless device 22 according to the first cycle of the report.

[0141] Example D2. The method of Example D1 also includes modifying the period of the requested location based on the movement of the wireless device.

[0142] Example D3. Following the method of Example D1, where the node is a location service, LCS, client or application function, AF, node.

[0143] Those skilled in the art will understand that the concepts described herein can be embodied in methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein can take the form of purely hardware embodiments, purely software embodiments, or embodiments combining software and hardware, collectively referred to herein as “circuit” or “module.” Any process, step, action, and / or function described herein can be performed by or associated with a corresponding module, which can be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can also take the form of a computer program product located on a tangible computer-readable storage medium containing computer-executable computer program code. Any suitable tangible computer-readable medium can be used, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0144] This document describes several embodiments with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It should be understood that each block in 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 can be provided to a processor of a general-purpose computer (thus creating a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to generate a machine such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, can create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0145] These computer program instructions may also be stored in a computer-readable storage medium or storage medium that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions / actions specified in the flowchart and / or block diagram boxes.

[0146] 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, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions / actions specified in the flowchart and / or block diagram boxes.

[0147] It should be understood that the functions / actions shown in the boxes may not be in the same order as those shown in the operating instructions. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or sometimes in reverse order, depending on the functions / actions involved. While some diagrams include arrows on the communication path to indicate the primary communication direction, it should be understood that communication may occur in the opposite direction to the arrows shown.

[0148] Computer program code used to perform the conceptual operations described herein may be written in an object-oriented programming language such as Python, Java®, or C++. However, computer program code used to perform the operations of this disclosure may also be written in a conventional procedural programming language such as the “C” programming language. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., connected to the Internet via an Internet service provider).

[0149] This document, in conjunction with the foregoing description and accompanying drawings, discloses numerous different embodiments. It should be understood that describing and illustrating every combination and sub-combination of these embodiments verbatim would result in excessive repetition and confusion. Therefore, all embodiments can be combined in any manner and / or combination, and this specification (including the accompanying drawings) should be understood as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein, as well as the ways and processes of making and using them, and should support the claims for any such combinations or sub-combinations.

[0150] The abbreviations that may be used in the foregoing description include: 5GC 5G core LCS Location Service MO-LR initiates a location request. MT-LR Mobile Termination Location Request Those skilled in the art will understand that the embodiments described herein are not limited to those specifically shown and described above. Furthermore, unless otherwise stated above, all drawings are not to scale. Based on the foregoing teachings, various modifications and variations can be made without departing from the scope of the appended claims.

Claims

1. A method implemented in a location management function LMF node (15), the method comprising: Configure (S106) the access network node (16) to periodically report location measurements for the wireless device (22); According to the periodic reporting configuration for the wireless device (22) at the access network node (16), a location measurement report is periodically received from the access network node (16) (S108). Based on one or more periodic location measurement reports obtained from the access network node (16), a location estimate is determined (S110); and The location estimate is periodically transmitted (S112) to one of the location service LCS clients or application function AF nodes.

2. The method according to claim 1, further comprising, upon receiving a report of location measurement session termination, initiating a process of locating the wireless device (22) and reconnecting it to the access network node (16).

3. The method of claim 2, wherein the process is initiated at least in part by requesting an Application Management Function (AMF) node to page the wireless device (22); and The location measurement session is terminated if the wireless device (22) is unavailable or in Radio Resource Control (RRC) idle mode.

4. The method according to any one of claims 1 to 3, further comprising, if the location measurement report indicates either an error or no location measurement has occurred, triggering another process to obtain the location measurement.

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

6. The method according to any one of claims 1 to 5, wherein the configuration in which the access network node (16) periodically reports location measurements comprises: The periodic reporting configuration is determined at least based on the wireless device capabilities of the wireless device (22); as well as The periodic report configuration is transmitted to the access network.

7. The method according to any one of claims 1 to 6, wherein the periodic location measurement report is received via one of the New Radio Positioning Protocol A, NRPPa, or Long Term Evolution (LTE) Positioning Protocol LPP.

8. The method according to any one of claims 1 to 7, wherein the periodic reception of location measurement reports from the access network node (16) is configured to occur at a first period; and The periodic transmission of the location estimate to one of the LCS clients or AF nodes is configured to occur in one of the following ways: The first cycle; or The second cycle is different from the first cycle.

9. The method according to any one of claims 1 to 8, wherein the access network node (16) is one of eNodeB, eNB or gNodeB, gNB.

10. A location management function LMF node (15) is configured as follows: Configure the access network node (16) to periodically report location measurements for the wireless device (22); According to the periodic reporting configuration for the wireless device (22) at the access network node (16), location measurement reports are periodically received from the access network node (16); A location estimate is determined based on one or more periodic location measurement reports obtained from the access network node (16); as well as The location estimate is periodically transmitted to either the Location Service (LCS) client or the Application Function (AF) node.

11. The LMF node (15) of claim 10, wherein the LMF node (15) is further configured to, upon receiving a report of termination of the location measurement session, initiate a process of locating the wireless device (22) and reconnecting it to the access network node (16).

12. The LMF node (15) of claim 11, wherein the process is initiated at least in part by requesting the Application Management Function (AMF) node to page the wireless device (22); and The location measurement session is terminated if the wireless device (22) is unavailable or in Radio Resource Control (RRC) idle mode.

13. The LMF node (15) according to any one of claims 10 to 12, wherein the LMF node (15) is further configured to trigger another process to obtain the location measurement if the location measurement report indicates either an error or no location measurement has occurred.

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

15. The LMF node (15) according to any one of claims 10 to 14, wherein the configuration in which the access network node (16) periodically reports location measurements includes: The periodic reporting configuration is determined at least based on the wireless device capabilities of the wireless device (22); as well as The periodic report configuration is transmitted to the access network.

16. The LMF node (15) according to any one of claims 10 to 15, wherein the periodic location measurement report is received via one of the New Radio Positioning Protocol A, NRPPa, or Long Term Evolution LTE Positioning Protocol LPP.

17. The LMF node (15) according to any one of claims 10 to 16, wherein the periodic reception of location measurement reports from the access network node (16) is configured to occur at a first period; and The periodic transmission of the location estimate to either the LCS client or the AF node is configured to occur in one of the following ways: The first cycle; or The second cycle is different from the first cycle.

18. The LMF node (15) according to any one of claims 10 to 17, wherein the access network node (16) is one of eNodeB, eNB or gNodeB, gNB.

19. A computer-readable storage medium (102) comprising instructions that, when executed by a processing circuit (98), cause the processing circuit (98) to perform a method comprising: Configure the access network node (16) to periodically report location measurements for the wireless device (22); According to the periodic reporting configuration for the wireless device (22) at the access network node (16), location measurement reports are periodically received from the access network node (16); A location estimate is determined based on one or more periodic location measurement reports obtained from the access network node (16); as well as The location estimate is periodically transmitted to either the Location Service (LCS) client or the Application Function (AF) node.

20. The computer-readable storage medium (102) of claim 19, wherein the configuration in which the access network node (16) periodically reports location measurements comprises: The periodic reporting configuration is determined at least based on the wireless device capabilities of the wireless device (22); as well as The periodic report configuration is transmitted to the access network; as well as The periodic location measurement reports are received via one of the New Radio Positioning Protocol A, NRPPa, or Long Term Evolution (LTE) Positioning Protocol LPP.

Images