Method and apparatus for data collection with defined periodicity of reporting messages

Abstract

According to an aspect, there is provided a method for execution by a first network node (e.g. RAN node). The method involves sending, to a second network node (e.g. AMF node), a request (e.g. first NGAP message) for ground truth information (e.g. location information and time stamp) for at least one served User Equipment (UE). The method also involves receiving a response including either the ground truth information for the at least one served UE or an indication that the ground truth information cannot be provided. The solution enables the RAN to trigger a request specific to one or more UE or specific to radio conditions or to reference signal configuration for data collection for the purpose of achieving training or monitoring data for an AI / ML assisted model. The solution can be applied to collection of training / monitoring data for served UEs.

Description

[0001] P113017WG01

[0002] - 1 -

[0003] METHOD AND APPARATUS FOR DATA COLLECTION WITH DEFINED PERIODICITY OF REPORTING MESSAGES

[0004] Related Applications

[0005] [1] This patent application claims priority from US provisional patent application no. US 63 / 758,002 filed on February 13, 2025, which is incorporated by reference in its entirety.

[0006] Field of the Disclosure

[0007] [2] This disclosure relates to mobile communication systems, and more particularly to mobile communication systems enabling data collection for positioning of a User Equipment (UE) in a defined area.

[0008] Background

[0009] [3] None of the material in the background section should be interpreted to be Applicant’s admitted prior art.

[0010] AI / ML model based positioning

[0011] [4] A new use case addressed by 3rd Generation Partnership Project (3GPP) is that Artificial Intelligence I Machine Learning (AI / ML) model can be used for UE positioning. A UE or a Next Generation Node B (gNB), depending on capability, can have a trained model stored inside the device, or have an untrained AI / ML that can be trained on-the-fly to either produce measurements that are to localize a UE within a radio access network (RAN) coverage area or directly predict / determine the UE location by exploiting the measurements performed by the UE or gNB on reference signals such as positioning reference signal (PRS), sounding reference signal (SRS) etc. within a RAN coverage area.

[0012] [5] Measurements predicted / determined by the gNB by exploiting an AI / ML model can be defined as, but not limited to:

[0013] • gNB Rx-Tx time difference: It is defined as T9NB-RX - T9NB-TX.P113017WG01

[0014] - 2 - Where:

[0015] o TgNB-Rx is the positioning node received timing of uplink subframe #i containing SRS associated with UE, defined by the first detected path in time. It is measured on SRS signals received from the UE. o TgNB-Tx is the positioning node transmit timing of downlink subframe #j that is closest in time to the subframe #i received from the UE.

[0016] • UL Relative Time of Arrival (UL RTOA): It is defined as the beginning of subframe i containing SRS received in positioning node j, relative to the configurable reference time. For example, nodel (e.g., base station etc) measures the reception time of signals transmitted by the UE with respect to a reference time.

[0017] AI / ML Assisted network positioning

[0018] [6] In this mode, the positioning measurements are performed by the gNB by using an AI / ML model. After completion, the positioning measurements are then reported to the location server. The location server upon receiving measurements determines the location of the UE within the RAN coverage area. The location server depending on the need may forward the UE location to another node within the network to facilitate provisioning of UE location information to the application layer or the third party that is interested or has requested the positioning of UE within the RAN coverage area for further action to be taken.

[0019] Related aspects in Release 19 WID for AI / ML positioning

[0020] [7] 3GPP Work Item Description (WID) [3] of R19 has the following Information on Work Item:

[0021] • Positioning accuracy enhancements, encompassing [RAN1 / RAN2 / RAN3]: o Direct AI / ML positioning:

[0022] ■ (1stpriority) Case 1: UE-based positioning with UE-side model, direct AI / ML positioning

[0023] ■ (2ndpriority) Case 2b: UE-assisted / LMF-based positioning with LMF-side model, direct AI / ML positioning

[0024] ■ (1stpriority) Case 3b: NG-RAN node assisted positioning with LMF- side model, direct AI / ML positioningP113017WG01

[0025] - 3 - o AI / ML assisted positioning

[0026] ■ (2ndpriority) Case 2a: UE-assisted / LMF-based positioning with UE- side model, AI / ML assisted positioning

[0027] ■ (1stpriority) Case 3a: NG-RAN node assisted positioning with gNB- side model, AI / ML assisted positioning

[0028] o Specify necessary measurements, signalling / mechanism(s) to facilitate LCM operations specific to the Positioning accuracy enhancements use cases, if any

[0029] o Investigate and specify the necessary signalling of necessary measurement enhancements (if any)

[0030] o Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE for relevant positioning sub use cases

[0031] o Note: RAN1 will not discuss any proposals targeting 2ndpriority issues in Q4 of 2024.

[0032] NG-RAN Architecture

[0033] [8] Referring now to Figure 1 , shown is a block diagram of an example Next Generation Radio Access Network (NG-RAN) 101. This Figure is a reproduction of Figure 6.1-1 of 3GPP Technical Specification (TS) 38.401 entitled “NG-RAN; Architecture description” Version 18.3.0 dated 2024-09-21 (hereinafter “3GPP TS 38.401”), which illustrates the overall architecture of the NG-RAN 201. The NG-RAN 101 has a set of gNBs 102,103 connected to a 5th Generation Core 104 (5GC) through an NG interface. 3GPP TS 38.401 describes the overall NG-RAN architecture.

[0034] [9] A disaggregated gNB may have a gNB-Central Unit 105 (CU) and one or more gNB-Distributed Unit(s) 106a-b (DU(s)). The gNB-CU 105 and each gNB-DU 106a-b are connected via an F1 interface. As shown in Figure 1, this F1 interface is responsible for possible information and control signaling from a Packet Data Convergence Protocol (PDCP) entity located in the CU and a Radio Link Control (RLC) entity located in the DU.P113017WG01

[0035] - 4 - Positioninq architecture

[0036]

[0010] Before Release 16, Long Term Evolution (LTE) based positioning was the prevalent RAT based positioning solutions available. Starting from Release 16 specification, positioning is also supported in New Radio (NR). Referring now to Figure 2, shown is a block diagram of an example positioning architecture with NG-RAN 201. The interactions between a gNB of the NG-RAN 201 and a LIE 202 is supported via the Radio Resource Control (RRC) protocol, while the location node interfaces with the UE 202 via the LTE positioning protocol (LPP). LPP is a common protocol to both NR and LTE. LMF 204 is the location node in NR which is coupled to the NG-RAN 201 via AMF 203. There are also interactions between the location node 304 and the gNB via the NR Positioning Protocol a (NRPPa) protocol.

[0037]

[0011] The positioning architecture in Figure 2 will also be used to support AI / ML based positioning. Release 19 work on introducing AI / ML based positioning will not only exploit the legacy protocol but will also rely on already defined / existing reference signals that are used for positioning.

[0038]

[0012] The problem of data collection for training and / or monitoring purposes for the case of AI / ML assisted positioning, namely for the case where an AI / ML model is hosted at the RAN to infer positioning measurements is still unresolved in 3GPP.

[0039] Summary of the Disclosure

[0040]

[0013] According to an aspect, there is provided a method for execution by a first network node (e.g. RAN node). The method involves sending, to a second network node (e.g. AMF node), a first request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The method also involves receiving the periodic data reporting messages (e.g. NGAP messages or NRPPa messages) of the UE.

[0041]

[0014] In accordance with an embodiment of the application, the first request indicates periodicity for periodic data reporting messages, and thus the periodic data reporting messages can be received in accordance with the periodicity as indicated by the first request message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node mightP113017WG01

[0042] - 5 -for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0043]

[0015] In some implementations, upon a change of SRS configuration, the first network node sends a message (e.g. NGAP message or NRPPa message) indicating the change of SRS configuration. The change of SRS configuration can be used in generating UE position. Therefore, by conveying the change of SRS configuration, the updated UE location can be matching a current SRS configuration in distance and time. This could improve accuracy in the reporting of the updated UE location.

[0044]

[0016] In some implementations, upon determining to stop receiving the periodic data reporting messages, the first network node sends a data collection termination command message (e.g. NGAP message). In some implementations, the first network node receives a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

[0045]

[0017] In some implementations, the first request includes a UE identifier to identify which UE the periodic data reporting is associated with and / or which UE the first request message is associated with. The first request can also have other suitable information.

[0046]

[0018] According to another aspect, there is provided a non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a first network node (e.g. RAN node), configure the first network node to implement a method as summarized above.

[0047]

[0019] According to another aspect, there is provided a first network node (e.g. RAN node). The first network node has a network interface configured to communicate with other network nodes, and control circuitry coupled to the network interface. The control circuitry is configured to send, to a second network node (e.g. AMF node) over the network interface, a first request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The control circuitry is also configured to receive the periodic data reporting messages (e.g. NGAP messages or NRPPa messages) of the UE over the network interface.P113017WG01

[0048] - 6 -

[0020] In accordance with an embodiment of the application, the first request indicates periodicity for periodic data reporting messages, and thus the periodic data reporting messages can be received in accordance with the periodicity as indicated by the first request message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0049]

[0021] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0050]

[0022] According to another aspect, there is provided a method for execution by a second network node (e.g. AMF node). The method involves receiving, from a first network node (e.g. RAN node), a first request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The method also involves selecting a third network node (e.g. LMF node) for the periodic data reporting. The method also involves sending, to the third network node, a second request message for periodic data reporting based on the first request message.

[0051]

[0023] In accordance with an embodiment of the application, the first request message indicates periodicity for periodic data reporting messages, and the second request message indicates the periodicity that was indicated by the first request message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0052]

[0024] In some implementations, the second network node receives, from the first network node, a message (e.g. NGAP message or NRPPa message) indicating a change of SRS configuration, and conveys the change of SRS configuration to the third network node. The change of SRS configuration can be used in generating UE position. Therefore, by conveying the change of SRS configuration, the updated UE location can be matching a current SRS configuration in distance and time. This could improve accuracy in the reporting of the updated UE location.P113017WG01

[0053] - 7 -

[0025] In some implementations, the second network node receives, from the third network node, first periodic data reporting messages (e.g. NGAP messages) of the UE responsive to the second request message, and sends, to the first network node, second periodic data reporting messages (e.g. NGAP messages) corresponding to the first periodic data reporting messages. In other implementations, periodic data reporting messages are sent from the third network node to the first network node.

[0054]

[0026] In some implementations, the second network node receives, from the first network node, a data collection termination command message (e.g. NGAP message), informs the third network node to terminate the first periodic data reporting messages, and terminates the sending of the second periodic data reporting messages. In some implementations, the second network node determines that location information for the UE can no longer be provided, and sends, to the first network node, a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

[0055]

[0027] According to another aspect, there is provided a non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a second network node (e.g. AMF node), configure the second network node to implement a method as summarized above.

[0056]

[0028] According to another aspect, there is provided a second network node (e.g. AMF node). The second network node has a network interface configured to communicate with other network nodes, and control circuitry coupled to the network interface. The control circuitry is configured to receive, from a first network node (e.g. RAN node) over the network interface, a first request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The control circuitry is also configured to select a third network node (e.g. LMF node) for the periodic data reporting. The control circuitry is also configured to send, to the third network node over the network interface, a second request message for periodic data reporting based on the first request message.

[0057]

[0029] In accordance with an embodiment of the application, the first request message indicates periodicity for periodic data reporting messages, and the second request message indicates the periodicity that was indicated by the first requestP113017WG01

[0058] - 8 -message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0059]

[0030] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0060]

[0031] According to another aspect, there is provided a method for execution by a third network node (e.g. LMF node). The method involves receiving, from a second network node (e.g. AMF node), a second request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The method also involves sending, to a first network node (e.g. RAN node) or the second network node, periodic data reporting messages.

[0061]

[0032] In accordance with an embodiment of the application, the second request message indicates a periodicity for periodic data reporting messages, and the periodic data reporting messages are sent in accordance with the periodicity as indicated by the second request message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0062]

[0033] In some implementations, the third network node receives, from the second network node, a message (e.g. NGAP message or NRPPa message) indicating a change of SRS configuration. The change of SRS configuration can be used in generating UE position. Therefore, by receiving the indication of the change of SRS configuration, the updated UE location can be matching a current SRS configuration in distance and time. This could improve accuracy in the reporting of the updated UE location.

[0063]

[0034] In some implementations, the third network node terminates the sending of the periodic data reporting messages upon receiving an indication to do so. In some implementations, the third network node determines that location information for the UE can no longer be provided, and sends, to the first network node or the second networkP113017W001

[0064] - 9 -node, a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

[0065]

[0035] According to another aspect, there is provided a non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a third network node (e.g. LMF node), configure the third network node to implement a method as summarized above.

[0066]

[0036] According to another aspect, there is provided a third network node (e.g. LMF node). The third network node has a network interface configured to communicate with other network nodes, and control circuitry coupled to the network interface. The control circuitry is configured to receive, from a second network node (e.g. AMF node) over the network interface, a second request message (e.g. NGAP message) for periodic data reporting for at least one User Equipment (UE). The control circuitry is also configured to send, to a first network node (e.g. RAN node) or the second network node over the network interface, periodic data reporting messages.

[0067]

[0037] In accordance with an embodiment of the application, the second request message indicates a periodicity for periodic data reporting messages, and the periodic data reporting messages are sent in accordance with the periodicity as indicated by the second request message. In this way, the first network node can continuously receive an updated UE location according to a defined periodicity. The first network node might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.

[0068]

[0038] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0069]

[0039] According to another aspect, there is provided a method for execution by a third network node (e.g. LMF node). The method involves receiving, from a first network node (e.g. RAN node), a measurement report message for a UE (User Equipment). The method also involves determining a location for the UE based on the measurement report message. Finally, the method involves sending, to the first network node, requested positioning data in response to the measurement report message.P113017W001

[0070] - 10 -

[0040] In some implementations, the requested positioning data is sent in a New Radio Positioning Protocol a (NRPPa) message.

[0071]

[0041] According to another aspect, there is provided a non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a third network node (e.g. LMF node), configure the third network node to implement a method as summarized above.

[0072]

[0042] According to another aspect, there is provided a third network node (e.g. LMF node). The third network node has a network interface configured to communicate with other network nodes, and control circuitry coupled to the network interface. The control circuitry is configured to receive, from a first network node over the network interface, a measurement report message for a UE (User Equipment). The control circuitry is also configured to determine a location for the UE based on the measurement report message. Finally, the control circuitry is configured to send, to the first network node over the network interface, requested positioning data in response to the measurement report message.

[0073]

[0043] In some implementations, the control circuitry is also configured to implement a method as summarized above.

[0074]

[0044] Other aspects and features of the present disclosure will become apparent, to those ordinarily skilled in the art, upon review of the following description of the various embodiments of the disclosure.

[0075] Brief Description of the Drawings

[0076]

[0045] Embodiments will now be described with reference to the attached drawings in which:

[0077] Figure 1 is a block diagram of an example NG-RAN;

[0078] Figure 2 is a block diagram of an example positioning architecture with NG-RAN;

[0079] Figure 3 is a block diagram of a communication system, in accordance with an embodiment of the disclosure.P113017W001

[0080] - 11 - Figure 4 is a sequence drawing of a method of enabling data collection of user equipment with defined periodicity of reporting messages;

[0081] Figure 5 is a sequence drawing of another method of enabling data collection of user equipment with defined periodicity of reporting messages according to an AMF-centric implementation; and

[0082] Figure 6 is a sequence drawing of another method of enabling data collection of user equipment with defined periodicity of reporting messages according to an LMF-centric implementation.

[0083] Detailed Description of Embodiments

[0084]

[0046] It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and / or methods may be implemented using any number of techniques. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended embodiment along with their full scope of equivalents.

[0085] Introduction

[0086]

[0047] Referring now to Figure 3, shown is a block diagram of a communication system 300, in accordance with an embodiment of the disclosure. The communication system 300 has UEs 340a-c capable of accessing a network 302, which might for example be a 5G network or some other network. The network 302 has several network nodes including a first network node 310, a second network node 320, a third network node 330, and may have other network nodes 350 as well.

[0087]

[0048] The first network node 310 has a network interface 315 configured to communicate with other nodes of the communication system 300, a CRM 319, and control circuitry 316 coupled to the network interface 315 and the CRM 319. In some implementations, the control circuitry 316 includes a processor 317 that executes software, which can stem from a memory 318. However, other implementations are possible and are within the scope of this disclosure. The first network node 310 can have additional components, but these are not shown for simplicity. In someP113017W001

[0088] - 12 -implementations, the first network node 310 is a RAN node, such as the gNB as depicted in Figure 2. Other implementations are possible.

[0089]

[0049] The second network node 320 has a network interface 325 configured to communicate with other nodes of the communication system 300, a CRM 329, and control circuitry 326 coupled to the network interface 325 and the CRM 329. In some implementations, the control circuitry 326 includes a processor 327 that executes software, which can stem from a memory 328. However, other implementations are possible and are within the scope of this disclosure. The second network node 320 can have additional components, but these are not shown for simplicity. In some implementations, the second network node 320 is an AMF node, such as the AMF as depicted in Figure 2. Other implementations are possible.

[0090]

[0050] The third network node 330 has a network interface 335 configured to communicate with other nodes of the communication system 300, a CRM 339, and control circuitry 336 coupled to the network interface 335 and the CRM 339. In some implementations, the control circuitry 336 includes a processor 337 that executes software, which can stem from a memory 338. However, other implementations are possible and are within the scope of this disclosure. The third network node 330 can have additional components, but these are not shown for simplicity. In some implementations, the third network node 330 is an LMF node, such as the LMF as depicted in Figure 2. Other implementations are possible.

[0091]

[0051] The problem of data collection for training and / or monitoring purposes for the case of AI / ML assisted positioning, namely for the case where an AI / ML model is hosted at the RAN to infer positioning measurements is still unresolved in 3GPP.

[0092]

[0052] The control circuitry 316 of the first network node 310, the control circuitry 326 of the second network node 320, and the control circuitry 336 of the third network node 330 implement a method of enabling data collection of user equipment 340a-340c with defined periodicity of reporting messages. Such operation by the control circuitries 316, 326, and 336 will be described below with reference to Figure 4. Although the method of Figure 4 is described below with reference to the communication system 300 shown in Figure 3, it is to be understood that the method ofP113017WG01

[0093] - 13 - Figure 4 is applicable to other communication systems. In general, the method of Figure 4 is applicable to any appropriately configured communication system.

[0094]

[0053] At step 401, the first network node 310 sends, to the second network node 320, a first request message (e.g. NGAP message) for periodic data reporting for at least one UE 340a-c. Notably, the first request message indicates periodicity for periodic data reporting messages.

[0095]

[0054] At step 402, the second network node 320 selects a third network node (e.g. LMF node) for the periodic data reporting. Subsequently, at step 403, the second network node 320 sends, to the third network node 330, a second request message for periodic data reporting based on the first request message. Notably, the second request message indicates the periodicity that was indicated by the first request message. Therefore, the third network node 330 becomes aware of the periodicity specified by the first network node 310 for periodic data reporting messages.

[0096]

[0055] At step 404, there is a positioning procedure. Note that the positioning procedure may be ongoing despite not being shown that way. At steps 405a-c, the third network node sends the periodic data reporting messages (e.g. NGAP messages or NRPPa messages) of the UE. Note that the periodic data reporting messages are sent according to the periodicity specified by the first network node 310. Although only three periodic data reporting messages are shown at steps 405a-c, it is to be understood that there can be numerous data reporting messages.

[0097]

[0056] In some implementations, the periodic data reporting messages are sent to the first network node 310 without the second network node 320 acting as an agent for those messages. In other implementations, the periodic data reporting messages are sent to the second network node 320, which in turn forwards the periodic data reporting messages (or derivative thereof) to the first network node 310.

[0098]

[0057] In this way, the first network node 310 can continuously receive an updated UE location according to a defined periodicity. The first network node 310 might for example subscribe to receiving the updated UE location over a period of time to help improve training data sets at an NG-RAN AI / ML model.P113017W001

[0099] - 14 -

[0058] It is possible that, during the periodic data reporting, there may be a change in SRS configuration. In such scenario, the change in SRS configuration can be conveyed from the first network node 310 to the third network node 330 (normally via the second network node 320). The change of SRS configuration can be used in generating UE position. Therefore, by conveying the change of SRS configuration, the updated UE location can be matching a current SRS configuration in distance and time. This could improve accuracy in the reporting of the updated UE location.

[0100]

[0059] In the illustrated example, the first two periodic data reporting messages at steps 405a and 405b are reporting UE location based on an initial SRS configuration, and the third periodic data reporting message at step 405c is reporting the UE location based on the changed SRS configuration. Thus, the periodic data reporting is dynamic according to changes in the SRS configuration.

[0101]

[0060] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 317 of the first network node 310, implement a method as described herein. The non-transitory computer readable medium can be the memory 318 and / or the CRM 319 of the first network node 310 shown in Figure 3, or some other non-transitory CRM.

[0102]

[0061] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 327 of the second network node 320, implement a method as described herein. The non-transitory computer readable medium can be the memory 328 and / or the CRM 329 of the second network node 320 shown in Figure 3, or some other non-transitory CRM.

[0103]

[0062] According to another embodiment of the disclosure, there is provided a non-transitory CRM having recorded thereon statements and instructions that, when executed by the processor 337 of the third network node 330, implement a method as described herein. The non-transitory computer readable medium can be the memory 338 and / or the CRM 339 of the third network node 330 shown in Figure 3, or some other non-transitory CRM.P113017WG01

[0104] - 15 -

[0063] Examples of a non-transitory CRM include memory, an SSD (Solid State Drive), a hard disk drive, a CD (Compact Disc), a DVD (Digital Video Disc), a BD (Blu-ray Disc), a memory stick, etc. Other non-transitory CRMs are also possible.

[0105]

[0064] The illustrated examples described herein focus on software implementations. However, other implementations are possible and are within the scope of this disclosure. Other implementations can include additional or alternative hardware components, such as any appropriately configured FPGA (Field-Programmable Gate Array), ASIC (Application-Specific Integrated Circuit), and / or microcontroller, for example. Thus, the control circuitry 316 of the first network node 114, the control circuitry 326 of the second network node 320, and the control circuitry 316 of the first network node 310 can instead be implemented with any suitable combination of hardware, software and / or firmware.

[0106]

[0065] The embodiments described herein can be applicable but not limited to 3GPP NR. Hence a base station (BS), can be a NR gNB, or 6G-RAT base station, or any other device with similar function. A CN node can be the AMF or any other CN function involved with communication for positioning. A Location Management Service can be any function in charge of UE positioning.

[0107]

[0066] In this application the communication between a first network node, the positioning function (LMF) and second network node, the RAN, is described. However, the methods described herein apply equally to the associated communication between a gNB-Cll and a gNB-Dll within the same gNB as first network node and second network node, respectively.

[0108]

[0067] Further example details are provided in the following sections. It is to be understood that the following sections are very specific and are provided merely for exemplary purposes, such that other implementations are possible and within the scope of the disclosure.

[0109]

[0110]

[0068] The RAN requests via a first message, e.g. over NGAP, towards the CN, e.g. the AMF, for assistance data that can be used as ground truth for inferred metrics (e.g. location information, or measurements from which the location can be derived, andP113017WG01

[0111] - 16 -time stamp) for a single UE, or for a list of UEs. A UE is identified by identifiers assigned to the UE over the signalling connection between the RAN and the CN, e.g. NGAP UE IDs in the NGAP message. The novelty is that the RAN indicates the periodicity over which the data is to be provided.

[0112]

[0069] Disclaimer: The methods in this invention are applicable to any communication system where the RAN and the CN communicate to achieve positioning of a user equipment. For reason of simplicity, the methods described in this application use the example framework of a 5G network, where an NG-RAN communicates with a 5G core network.

[0113]

[0070] Afterwards, two solutions can take in place to report periodic assistance information to RAN.

[0114] Solution 1: AMF Centric Solution

[0115]

[0071] Referring now to Figure 5, shown is a sequence drawing of another method of enabling data collection of user equipment with defined periodicity of reporting messages according to an AMF-centric implementation. By way of overview, this is a procedure for periodic reporting of UE location based NG-RAN triggered NGAP request to AMF, with cases of termination command from NG-RAN (step 13), and failure indication from AMF (step 15).

[0116]

[0072] At step 1, a UE has been configured by the RAN with UL SRS transmission. At step 2, the RAN determines that it is to collect data for the UE. Reasons for such request could be that the RAN needs to collect data for one or more specific UL RS configurations, e.g. SRS configurations, for which e.g. the RAN does not have sufficient amounts of data.

[0117]

[0073] At step 3, the RAN sends a request to the AMF for periodic data reporting. At step 4, the AMF confirms to the gNB that periodic data reporting of assistance data (e.g. positioning ground truth) can take place. This may occur by means of a message from the AMF to the RAN, in response to the request of step 3.

[0118]

[0074] Upon selecting an LMF at step 5, the AMF triggers a request to the LMF at step 6 for periodic reporting of assistance data, e.g. the current UE location orP113017W001

[0119] - 17 -measurements from which the UE location can be derived. This may happen by means of a new procedure or by means of enhancements to existing procedures, where the request would include the requested periodicity for the location reporting to the RAN. For example, this may happen by sending a Nlmf_Location_DetermineLocation service operation request message to LMF. The message is enhanced with an indication of the requested periodicity.

[0120]

[0075] At step 7, the LMF confirms that periodic reporting of the requested data (e.g., UE position), can take place by sending a confirmation message back to the AMF. This can be a new message or enhancements of an existing one.

[0121]

[0076] The LMF performs positioning procedures and it derives the requested data for the requested periodicity. Other actions can be performed as well. See steps 8 though 11.

[0122]

[0077] At step 12, at the expiration of each reporting period corresponding to the reporting periodicity requested, the LMF sends a new message, e.g. the Nlmf_Location_DetermineLocation_Report message, towards the AMF. The message includes the requested data, e.g. current location of the UE / requested ground truth as well as information concerning the time such data, e.g. the UE position, correspond to.

[0123]

[0078] At step 13, the AMF returns the requested data / ground truth / UE location to the NG-RAN periodically, respecting the requested periodicity, via a new NGAP message, e.g. the Data Collection Report Message.

[0124]

[0079] If there is a change happening to the SRS transmission or measurements during the course of positioning within the reporting periodicity:

[0125] • If the LMF invokes, during step 3, SRS based positioning methods (e.g., UL- TDOA), the NG-RAN indicates the updated SRS configuration and / or SRS measurements used for AI / ML training to the LMF via an NRPPa message with dedicated information.

[0126]

[0080] In case the NG-RAN decides to terminate periodic reporting of the requested data at step 14, then at step 15 it sends a new NGAP message to the AMF, e.g. the DATA COLLECTION TERMINATION COMMAND. At step 16, the AMF thenP113017W001

[0127] - 18 -sends a new message, e.g. the Nlmf_Location_DetermineLocation_Cancel message, to the LMF to stop the periodic UE positioning computing.

[0128]

[0081] In case the AMF stopped, for any reason, providing the periodic data, e.g. UE location information at step 17, then at step 18 the AMF sends a new NGAP message, e.g. the DATA COLLECTION FAILURE INDICATION message, to the RAN, indicating the reasons for which the reporting was stopped, e.g. with an appropriate cause value.

[0129]

[0082] Note: In solution 1, the AMF executes temporary UE ID and Permanent UE ID mapping between gNB and LMF. This enables to identify the user at the LMF, from the temporary UE identities provided by the RAN to the AMF at the time of periodic data collection request. At the same time, this allows the AMF to associated the UE data provided by the LMF to the temporary identifiers associated to the UE context at the RAN, and signal the UE data to the RAN in a way that they are mapped to the correct temporary UE IDs.

[0130] Example Embodiments for AMF-centric solution of periodic data collection reporting

[0131]

[0083] NG-RAN embodiments:

[0132] • In one embodiment, the NG-RAN indicates the periodicity over which it requests data to be received to the AMF in a NGAP message for data collection request.

[0133] • In one embodiment, the NG-RAN indicates the changes of SRS configuration to AMF in an NGAP message, indicating the new SRS configuration used for AI / ML training.

[0134] • In one embodiment, the NG-RAN indicates the changes of SRS configuration to LMF in an NRPPa message, e.g. the POSITIONING INFORMATION UPDATE message, indicating the new SRS configuration used for data collection. The LMF takes it into account to derive new UE position.

[0135] • In one embodiment, the NG-RAN decides to stop receiving the UE location / data and sends an NGAP message such as a DATA COLLECTION TERMINATION COMMAND message to AMF to stop the periodic reporting.P113017W001

[0136] - 19 - • In a separate embodiment, the NG-RAN may receive a message from AMF, e.g.

[0137] the DATA COLLECTION FAILURE INDICATION message over NGAP, indicating that the periodic reporting has been terminated, and can no longer be provided with an appropriate value.

[0138]

[0084] AMF embodiments:

[0139] • In one embodiment, the AMF receives a request for periodic reporting of UE location from NG-RAN via the NGAP DATA COLLECTION REQUEST message, and sends a NGAP message, such as the DATA COLLECTION RESPONSE message to NG-RAN confirming the start of periodic reporting process.

[0140] • In one embodiment, the AMF selects and invokes an appropriate LMF to start positioning the UE with the requested periodicity.

[0141] • In one embodiment, the AMF keeps reporting the UE position that is received from LMF to NG-RAN in a message such as the DATA COLLECTION REPORT message following the requested periodicity.

[0142] • In one embodiment, when the AMF receives the NGAP DATA COLLECTION TERMINATION COMMAND message, it terminates the reporting and indicates the LMF to terminate the positioning session of the UE via a new message, e.g. the Nlmf_Location_DetermineLocation cancel message.

[0143] • In one embodiment, when the AMF can no longer provide any UE location, due to e.g., positioning failure, it sends a NGAP message such as the DATA COLLECTION FAILURE INDICAITON message to NG-RAN with information concerning the reason for the failure, e.g. with a cause value .

[0144]

[0085] LMF embodiments:

[0145] • In one embodiment, the LMF receives a request from AMF of providing the UE location to AMF at a requested periodicity within a new message such as the Nlmf_Location_DetermineLocation request message. If the LMF accepts, it sends an Nlmf_Location_DetermineLocation Response message that confirms the start of periodic reportingP113017W001

[0146] - 20 - • In one embodiment, the LMF provides the requested data / UE location to AMF in a new message, such as the Nlmf_Location_DetermineLocation Report message.

[0147] • In one embodiment, when the LMF receives the Nlmf_Location_DetermineLocation request Cancel message it terminates UE positioning.

[0148] Solution 2: LMF Centric Solution

[0149]

[0086] Referring now to Figure 6, shown is a sequence drawing of another method of enabling data collection of user equipment with defined periodicity of reporting messages according to an LMF-centric implementation. By way of overview, this is a procedure for periodic reporting of UE location based NG-RAN triggered NGAP request to AMF, and LMF providing the UE location to NG-RAN via NRPPa, with cases of termination command from NG-RAN (step 14), and failure indication from LMF (step 16).

[0150]

[0087] At step 1, a UE has been configured by the RAN with UL SRS transmission. At step 2, the RAN determines that it is to collect data for the UE. Reasons for such request could be that the RAN needs to collect data for one or more specific UL RS configurations, e.g. SRS configurations, for which e.g. the RAN does not have sufficient amounts of data.

[0151]

[0088] At step 3, the RAN sends a request to the AMF for periodic data reporting. At step 4, the AMF selects an appropriate LMF that can report periodic UE location to the requesting NG-RAN, and at step 5 the AMF sends a reply message to the RAN, e.g. a Data Collection Confirm message.

[0152]

[0089] At step 6, the AMF uses a new or existing message, e.g. the Nlmf_Location_DetermineLocation, to trigger the request to LMF. At step 7, the LMF invokes NRPPa based periodic positioning method and responds with a new or existing message, e.g. Nlmf_Location_DetermineLocation, to the AMF to confirm that the periodic reporting accepted.

[0153]

[0090] Once the UE is positioned, the LMF provides the UE location to NG-RAN in an NRPPa message periodically. See steps 8 and 9.P113017WG01

[0154] - 21 -

[0091] At step 10, the NG-RAN provides an NRPPa measurement report to the LMF including a UE identifier, e.g., the l-RNTI, to identify the UE for which the report is associated to. At steps 11 and 12, based on this report and l-RNTI, the LMF provides the computed UE location to the NG-RAN. Note that the message from the RAN to the LMF containing the temporary UE identity for the UE may be generated once, or every time the identity is changed, or in a periodic way.

[0155]

[0092] At step 13, if the NG-RAN is unable to provide anymore periodic measurements, or the data request is decided to be terminated fora UE, then at step 14 the NG-RAN sends an NRPPa message to the LMF to stop the reporting with l-RNTI of the UE for which the reporting should be stopped.

[0156]

[0093] At step 15, if the LMF cannot provide the requested data for the UE, then at step 16 the LMF sends a failure message over NRPPa to NG-RAN including the I-RNTI of the UE.

[0157]

[0094] Note: In solution 2, the LMF is to receive from AMF in Nlmf_Location_DetermineLocation service operation the temporary UE ID (l-RNTI) beside permanent UE ID (SUPI) in order to make mapping between IDs. The LMF shall use temporary UE ID when location estimation is sent to NG-RAN via NRPPa message.

[0158] Example Embodiments for LMF-centric solution of periodic data collection reporting

[0159]

[0095] NG-RAN embodiments:

[0160] • In one embodiment, the NGRAN sends the request for data collection with periodicity in a new NGAP message to AMF.

[0161] • In an embodiment, the NG-RAN receives the requested data in a new NRPPa message periodically

[0162] • In one embodiment, the NG-RAN includes a UE identifier, e.g., l-RNTI in the NRPPa message to LMF to indicate for which UE the periodic measurement report is associated to.

[0163] • In one embodiment, the NG-RAN includes a UE identifier, e.g., l-RNTI in the NRPPa message to LMF to indicate for which UE the request for UE location reporting is associated to.P113017WG01

[0164] - 22 -

[0096] AMF embodiments:

[0165] • In one embodiment, once the AMF confirms the LMF selection and the start of the periodic positioning session, it sends a new message, such as the NGAP DATA COLLECTION CONFIRM message to NG-RAN

[0166]

[0097] LMF embodiments:

[0167] • In one embodiment, the LMF provides the requested data / UE location to NG- RAN in the requested periodicity in a new NRPPa message.

[0168] • In one embodiment, when the LMF receives a periodic measurement report form NG-RAN, it updates the UE location based on this new report and sends the requested data in a new NRPPa message to NG-RAN.

[0169] • In one embodiment, the LMF sends a failure indication to NG-RAN indicating termination of UE location reporting for a UE identified by its l-RNTI.

[0170] Further Discussion

[0171]

[0098] To ensure that there is a one-to-one mapping between SRS measurement and UE position, and therefore to be able to form AI / ML training data sets or to be able to have monitoring data for each AI / ML inference process at RAN in support of positioning, the NG-RAN will request for periodic reporting of UE position from AMF, indicating the periodicity of the data reporting. The NG-RAN also indicates to CN (AMF and / or LMF) the updated SRS configuration and measurements for AI / ML training / monitoring purposes, which would be used to generate the updated UE position.

[0172]

[0099] Potential benefits realized by one or more embodiments:

[0173] • solutions described herein enable the NG-RAN to subscribe to receiving UE location over a period of time which would help improving the training data sets at NG-RAN AI / ML model.

[0174] • The NG-RAN continuously receives an updated UE location matching to the current SRS configuration in distance and time.

[0175] Previous approaches might not realize these benefits.P113017W001

[0176] - 23 -

[0100] US Provisional Application No. 63 / 740,432 filed on December 31, 2024, which is hereby incorporated by reference in its entirety and hereinafter referred to as “the ‘432 application”, describes new methods for an NG-RAN to trigger a data collection request to the AMF via the NG Access Protocol (NGAP) and for the AMF to provide the requested data after obtaining the UE position from the LMF. In particular, the ‘432 application has focused on solutions for obtaining ground truths / labels on demand, where the gNB can trigger a request whenever it determines that data from a certain UE is useful for training purposes.

[0177]

[0101] However, for the use case of AI / ML positioning, an on-demand request for training data may not be enough, since the gNB can support collection of SRS transmissions from the UE in periodic, aperiodic and semi-persistent ways. Namely, the RAN can collect the inputs based on which a set of training data will be formed or based on which AI / ML based inference will be carried out in periodic, aperiodic and semi-persistent ways.

[0178]

[0102] Thus, for adapting to the different changes of SRS transmission, which could be collected and updated over long periods of time, the NG-RAN will need to obtain ground truth data (corresponding to the UE position or to measurements from which it can be derived) continuously, to match with the SRS measurements collected from the UE’s UL transmission. This continuous or semi-persistent way of collecting data is so far not available and it is a problem because it does not allow creating training data set for input metrics collected at different time instances during a given period of time, as well as it prevents monitoring inferred positioning metrics at the RAN, which are inferred at different time instances during a given period of time.

[0179]

[0103] Also, requesting each time for training data from the AMF 210 via NGAP may be considered too onerous in terms of signalling, as it increases the interactions between different network nodes: TRP / gNB 110, AMF 210, LMF 310. Therefore, another problem is how to ensure that, in case of prolonged reporting of positioning data from the LMF 310 to the RAN 110, the signalling solution is not too processing and signalling intensive.P113017WG01

[0180] - 24 - Technical Specification Impact

[0181]

[0104] Below are potential spec impacts to 3GPP TS 38.413 entitled “NG-RAN; NG Application Protocol (NGAP)” version 18.3.0 dated 2024-09-21. It is to be understood that this section is very specific for exemplary purposes, and that other implementations are possible.

[0182] DATA COLLECTION REQUEST

[0183] This message is sent by the NG-RAN node to request data collection from the AMF over the NG interface for one UE.

[0184] Direction: NG-RAN node

[0185]

[0186]

[0187] DATA COLLECTION REPORT

[0188] This message is sent by the AMF to provide ground truth information to the NG-RAN over the NG interface in the requested periodicity.

[0189] Direction: AMF NG-RAN node

[0190] > >

[0191]

[0192] P113017W001

[0193] - 25 - DATA COLLECTION FAILURE INDICATION

[0194] This message is sent by the AMF to indicate that the AMF can no longer provide the requested periodic information.

[0195] Direction: AMF NG-RAN node

[0196]

[0197] DATA COLLECTION TERMINATION COMMAND

[0198] This message is sent by the NG-RAN to abort the report of periodic UE location reporting.

[0199] Direction: NG-RAN node

[0200]

[0201]

[0202]

[0105] Numerous modifications and variations of the present disclosure are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the disclosure may be practised otherwise than as specifically described herein.

Claims

P113017W001- 26 - Claims:

1. A method for execution by a first network node, comprising:sending, to a second network node, a first request message for periodic data reporting for at least one UE (User Equipment, wherein the first request message indicates periodicity for periodic data reporting messages; andreceiving the periodic data reporting messages of the UE, in accordance with the periodicity as indicated by the first request message.

2. The method of claim 1 , further comprisingupon a change of SRS (Sounding Reference Signal) configuration, sending a message indicating the change of SRS configuration.

3. The method of claim 1 or claim 2, further comprising:upon determining to stop receiving the periodic data reporting messages, sending a data collection termination command message.

4. The method of claim 1 or claim 2, further comprising:receiving a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

5. The method of any one of claims 1 to 4, wherein the first request message includes a UE identifier to identify which UE the periodic data reporting is associated with and / or which UE the first request message is associated with.

6. The method of any one of claims 1 to 5, wherein the first network node comprises a RAN (Radio Access Network) node, and the second network node comprises an AMF (Access and Mobility Management Function) node.

7. A non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a first network node, configure the first network node to implement a method according to any one of claims 1 to 6.P113017W001- 27 - 8. A first network node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to:send, to a second network node over the network interface, a first request message for periodic data reporting for at least one UE (User Equipment), wherein the first request message indicates periodicity for periodic data reporting messages; andreceive the periodic data reporting messages of the UE over the network interface, in accordance with the periodicity as indicated by the first request message.

9. The first network node of claim 8, wherein the control circuitry is further configured to implement a method according to any one of claims 2 to 6.

10. A method for execution by a second network node, comprising:receiving, from a first network node, a first request message for periodic data reporting for at least one UE (User Equipment), wherein the first request message indicates periodicity for periodic data reporting messages; andselecting a third network node for the periodic data reporting; andsending, to the third network node, a second request message for periodic data reporting based on the first request message, wherein the second request message indicates the periodicity that was indicated by the first request message.

11. The method of claim 10, comprising:receiving, from the first network node, a message indicating a change of SRS (Sounding Reference Signal) configuration; andconveying the change of SRS configuration to the third network node.

12. The method of claim 10 or claim 11, further comprising:receiving, from the third network node, first periodic data reporting messages of the UE responsive to the second request message; andP113017W001- 28 - sending, to the first network node, second periodic data reporting messages corresponding to the first periodic data reporting messages.

13. The method of claim 12, further comprising:receiving, from the first network node, a data collection termination command message;informing the third network node to terminate the first periodic data reporting messages; andterminating the sending of the second periodic data reporting messages.

14. The method of claim 12, further comprising:determining that location information for the UE can no longer be provided;sending, to the first network node, a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

15. The method of any one of claims 10 to 14, wherein the first network node comprises a RAN (Radio Access Network) node, the second network node comprises an AMF (Access and Mobility Management Function) node, and the third network node comprises an LMF (Location Management Function) node.

16. A non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a second network node, configure the second network node to implement a method according to any one of claims 10 to 15.

17. A second network node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to:P113017W001- 29 - receive, from a first network node over the network interface, a first request message for periodic data reporting for at least one UE (User Equipment), wherein the first request message indicates periodicity for periodic data reporting messages; andselect a third network node for the periodic data reporting; andsend, to the third network node over the network interface, a second request message for periodic data reporting based on the first request message, wherein the second request message indicates the periodicity that was indicated by the first request message.

18. The second network node of claim 17, wherein the control circuitry is further configured to implement a method according to any one of claims 12 to 15.

19. A method for execution by a third network node, comprising:receiving, from a second network node, a second request message for periodic data reporting for at least one UE (User Equipment), wherein the second request message indicates a periodicity for periodic data reporting messages; andsending, to a first network node or the second network node, periodic data reporting messages, in accordance with the periodicity as indicated by the second request message.

20. The method of claim 19, comprising:receiving, from the second network node, a message indicating a change of SRS (Sounding Reference Signal) configuration; andwherein the change of SRS configuration is used in generating UE position.

21. The method of claim 19 or claim 20, comprising:terminating the sending of the periodic data reporting messages upon receiving an indication to do so.P113017W001- 30 - 22. The method of claim 19 or claim 20, further comprising:determining that location information for the UE can no longer be provided;sending, to the first network node or the second network node, a data collection failure message indicating that the periodic data reporting has been terminated or can no longer be provided.

23. The method of any one of claims 19 to 22, wherein the first network node comprises a RAN (Radio Access Network) node, the second network node comprises an AMF (Access and Mobility Management Function) node, and the third network node comprises an LMF (Location Management Function) node.

24. A non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a third network node, configure the third network node to implement a method according to any one of claims 19 to 23.

25. A third network node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to:receive, from a second network node over the network interface, a second request message for periodic data reporting for at least one UE (User Equipment), wherein the second request message indicates a periodicity for periodic data reporting messages; andsend, to a first network node or the second network node over the network interface, periodic data reporting messages, in accordance with the periodicity as indicated by the second request message.

26. The third network node of claim 25, wherein the control circuitry is further configured to implement a method according to any one of claims 21 to 23.P113017W001- 31 - 27. A method for execution by a third network node, comprising:receiving, from a first network node, a measurement report message for a UE (User Equipment);determining a location for the UE based on the measurement report message; andsending, to the first network node, requested positioning data in response to the measurement report message.

28. The method of claim 27, wherein the requested positioning data is sent in a New Radio Positioning Protocol a (NRPPa) message.

29. The method of claim 27 or claim 28, wherein the first network node comprises a RAN (Radio Access Network) node, and the third network node comprises an LMF (Location Management Function) node.

30. A non-transitory CRM (computer readable medium) having recorded thereon statements and instructions that, when executed by a processor of a third network node, configure the third network node to implement a method according to any one of claims 27 to 29.

31. A third network node, comprising:a network interface configured to communicate with other network nodes;control circuitry coupled to the network interface and configured to receive, from a first network node over the network interface, a measurement report message for a UE (User Equipment); determine a location for the UE based on the measurement report message; and send, to the first network node over the network interface, requested positioning data in response to the measurement report message.

32. The third network node of claim 31 , wherein the control circuitry is further configured to implement a method according to claim 28 or claim 29.

Images