WO2024110081A1 - Data collection and reporting in a wireless communication system - Google Patents

Abstract

A network entity for wireless communication configured to: receive a request for collecting data from at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes; and transmit a configuration message to a network function serving the set of UEs or the set of RAN nodes, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency.

Description

DATA COLLECTION AND REPORTING IN A WIRELESS COMMUNICATION SYSTEM

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to data collection and reporting in a wireless communication system.

BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0003] Some wireless communications system may support artificial intelligence and machine learning (AI/ML) operations. A network communication device, such as a base station may be configured with AI/ML models or equipped with circuitry (e.g., antennas, antenna panels, radios, and the like) that support AI/ML operations. Additionally, or alternatively, a user communication device, such as a UE may be configured with AI/ML models or equipped with circuitry (e.g., antennas, antenna panels, radios, and the like) that support AI/ML operations. The network communication device or the user communication device, or both, may support AI/ML operations to improve reliability of wireless communications, reduce latency of the wireless communication, or decrease power consumption by the network communication device or the user communication device, among other benefits. [0004] In some cases, the network communication device or the user communication device, or both, may support AI/ML operations to improve on channel state information (CSI) reporting (e.g., using spatial-frequency domain CSI compression using two-sided Al model, or time domain CSI prediction using UE sided models). In some other cases, the network communication device or the user communication device, or both, may support AI/ML operations to improve on beam management (e.g., using AI/ML to derive beam prediction accuracy information). In other cases, the network communication device or the user communication device, or both, may support AI/ML operations to improve positioning measurement and reporting accuracy within a wireless communication system (e.g., using AI/ML to improve accuracy of location measurements).

[0005] Some wireless communications systems may include network functions, such as network data analytics functions (NWDAF), to collect data to support positioning measurement and reporting accuracy, and may be part of a core network, for example, in 5G systems. For example, a location management function (LMF) may be used by location services (LCS) to provide positioning related data associated with a user communication device. The positioning related data may be provided via a user plane connection between the user communication device and the LMF. The LMF may indicate to the user communication device to use the user plane for positioning with the information to establish a secure connection. One or multiple positioning messages may be exchanged (e.g., transferred, forwarded, transmitted, outputted) between the user communication device and the LMF via the secure connection. In some cases, a UE route selection policy (URSP) may be used by the user communication device to determine how to route the positioning messages. In general, existing methods may not provide or specify a procedure or framework for collecting radio specific data usable to support the new AI/ML functionality.

[0006] It is desirable to further improve on data collection to support AI/ML for 5G and radio access technologies beyond 5G.

SUMMARY [0007] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be constmed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0008] Some implementations of the method and apparatuses described herein may further include a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a request for collecting data from at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes; and transmit a configuration message to a network function serving the set of UEs or the set of RAN nodes, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency. The configuration message may comprise both the UE configuration information and the RAN configuration information. A “set” is defined as comprising one or more of the entities of the set. Hence, the set of the UEs comprises one or more UEs, and the set of RAN nodes comprises one or more RAN nodes. The term “serving” is used herein to mean configured to provide one or more services over the wireless communication system. [0009] The at least one processor can be configured to cause the network entity to implement a radio data collection and coordination function (RDCCF) of a core network (CN). The RDCCF may be a new network function (NF) of the CN or may for example be a new part of the existing Data Collection Application Function (DCAF) of the CN. The at least one processor is configured to implement the RDCCF to receive the request and to send the configuration message to the network function (e.g. to an access and mobility function, AMF, of the CN).

[0010] The at least one processor is further configured to cause the network entity to determine the network function based on at least one of an area served by the network function; one or more UEs served by the network function; and one or more RAN nodes served by the network function. For example, the RDCCF can determine the AMF that serves an area that at least partly overlaps a target area indicated in the request, or determines the AMF that serves one or more UEs/RAN nodes indicated in the request.

[0011] The at least one processor can be configured to cause the network entity to determine the first and/or second indication of one or more data types from a data identifier (e.g. a Data ID or Event ID) comprised by the request. The data identifier may map to one or more data types and/or specific radio measurements.

[0012] The at least one processor can be configured to cause the network entity to determine the set of UEs and/or the set of RAN nodes from a target area indicator comprised by the request. The request may comprise an indicator of a specific target area, and a data type relating to UE measurements but without identifying the UEs to perform the measurements. The network entity, e.g. through the RDCCF, may then identify the set of UEs from the target area. For example, the network entity can send a UE information request to the network function (typically an AMF) and be configured to receive UE information from the network function, wherein the UE information comprises UE identifiers of the set of UEs (to be configured for data collection). [0013] The UE configuration information may further comprises one or more of: a location indication for configuring the UE to report a location at which the data was generated; a quality indication for configuring the UE to report an indication of a quality of the data that is reported; and a timestamp indication for configuring the UE to report a timestamp associated with each data point or set of the collected data. The RDCCF can configure the UE to report radio specific data as well as location, quality and time relating to the radio specific data.

[0014] When the request is for collecting data for a UE, the RAN configuration information can comprise assistance information for configuring the RAN node to provide additional pilot signals to one or more UEs for collecting and reporting data. The RDCCF can configure the RAN node to assist the UE in the data collection, regardless of whether the RAN node is also being configured for collecting data.

[0015] The at least one processor can be configured to cause the network entity to include the UE configuration information in a UE data collection and reporting protocol (UDCRP). The UDCRP is a new protocol for configuring and reporting data. For example, the UDCRP can be used to configure the UE to report data to the RDCCF via the AMF.

The UDCRP protocol can be included within a container that comprises header information (e.g. within an Information Element Identifier, IEI), which specifies that the contents of the container include UDCRP protocol information.

[0016] The at least one processor can be configured to cause the network entity to include the RAN configuration information in a RAN data collection and reporting protocol (RDCRP). The RDCRP is a new protocol for configuring and reporting data. For example, the RDCRP can be used to configure the RAN node to report data to the RDCCF via the AMF. The RDCRP protocol can be included within a container that comprises header information (e.g. within an Information Element Identifier, IEI), which specifies that the contents of the container include RDCRP protocol information [0017] The request may comprise location information relating to a target area for data collection, and the at least one processor can be configured to cause the network entity to determine the network function based on the location information and to send to the network function a request for UE information to identify the set of UEs served by the network function. For example, the RDCCF can determine the AMF based on the location information.

[0018] Some implementations of the method and apparatuses described herein may further include a network entity for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a configuration message for at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes to collect data, wherein the configuration message comprises: a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency; for the or each UE, send the UE data container to the UE; and for the or each RAN node, send the RAN data container to the RAN node. The configuration message may comprise both the UE configuration information and the RAN configuration information.

[0019] The network entity can be configured to implement an access and mobility function (AMF) of a core network (CN). The AMF may be the network function determined by the RDCCF as described above.

[0020] The at least one processor can be configured to send the UE data container to the UE within a non-access stratum (NAS) message and to send the RAN data container to the RAN node within an N2 message. For example, the AMF can send the NAS message in the N2 message to the RAN node, and the NAS message is then forwarded, e.g. over a Uu interface, to the UE from the RAN node. [0021] The at least one processor can be configured to cause the network entity to: receive a request for collecting data from the set of UEs and/or from the set of RAN nodes; determine a network function for determining a data collection configuration; send the request to the network function; and receive from the network function the configuration message. The network function may be the RDCCF implemented by the network entity described above.

[0022] Some implementations of the method and apparatuses described herein may further include a core network (CN) in a wireless communication network, comprising: a radio data collection and coordination function (RDCCF) configured to receive a request for collecting data from at least one of a set of user equipments (UEs) and a set of Radio Access Network (RAN) nodes; an access and mobility management function (AMF) serving the set of UEs and/or the set of RAN nodes; wherein the RDCCF is configured to send a configuration message to the AMF, wherein the configuration message comprises: a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency; wherein the AMF is configured to receive the configuration message and to, for the or each UE, send the UE data container to the UE, and, for the or each RAN node, send the RAN data container to the RAN node. The RDCCF and AMF may be implemented by the network entities described above.

[0023] The AMF can be configured to send the UE data container in a non-access stratum (NAS) message and the RAN data container in a N2 message. The NAS message may be sent to the UE via the RAN node by including the NAS message in the N2 message.

[0024] Some implementations of the method and apparatuses described herein may further include a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a data collection message comprising a UE data container comprising data collection configuration information within a UE data collection and reporting protocol, wherein the data collection configuration information comprises a first indication of one or more data types and a first indication of a reporting frequency; collect data of the one or more data types; and report the data at the reporting frequency using the UE data collection and reporting protocol.

[0025] The at least one processor can be configured to cause the UE to extract the UE data collection and reporting protocol from the data container; and extract the UE data collection configuration information from the UE data collection and reporting protocol. The data collection message may be a non-access stratum (NAS) message.

[0026] The at least one processor can be further configured to cause the UE to collect and report physical layer (layer 1) and link layer (layer 2) related data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0028] Figure 2 illustrates a data collection framework in accordance with aspects of the present disclosure.

[0029] Figure 3 illustrates a data collection framework in accordance with aspects of the present disclosure.

[0030] Figure 4 illustrates a process of collecting positioning related data using a LMF in accordance with aspects of the present disclosure.

[0031] Figure 5 illustrates a data collection framework comprising a radio data collection and coordination function (RDCCF) in accordance with aspects of the present disclosure.

[0032] Figure 6 illustrates data collection and reporting protocols for data collection for a UE and RAN via a control plane in accordance with aspects of the present disclosure. [0033] Figure 7 illustrates a signaling flowchart of a process for collecting data in accordance with aspects of the present disclosure.

[0034] Figure 8 illustrates a signaling flowchart of a process for reporting collected data in accordance with aspects of the present disclosure.

[0035] Figure 9 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0036] Figure 10 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0037] Figure 11 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.

[0038] Figure 12 illustrate a method performed by a UE in accordance with aspects of the present disclosure.

[0039] Figure 13 illustrate a method performed by a NE in accordance with aspects of the present disclosure.

[0040] Figure 14 illustrate a method performed by a NE in accordance with aspects of the present disclosure.

[0041] Figure 15 illustrate a method performed by a core network (CN) in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

In order to support AI/ML operations, a suitable framework for collecting data in a wireless communication system is required. The collected data can be used to train an AI/ML model on a network communication device configured for AI/ML operations.

[0042] Existing technology only supports reporting data that has been collected from one or more applications (apps) in a UE, whereas for New Radio (NR) the data should be reported by the vendor specific modem in the UE. Data from the modem of the UE may be data relating to the physical layer (layer 1) and/or data related to the link layer (layer 2). [0043] Also, the granularity of reporting data is currently per “Event ID”, which may not be practical or sufficient for supporting the new AI/ML operations in the wireless communication system. Event IDs are network based identifiers and cannot be used to report radio specific data. For example, a network event ID is an Event ID for UE mobility that denotes the AMF to report whether a UE is present in the location area supported by the AMF. It is not possible to use an Event ID for reporting a single radio data measurement (e.g. Received Signal Strength Indicator, RSSI).

[0044] Another potential problem with the existing data collection framework is that radio specific data collection from the Radio Access Network (RAN) is not supported. To provide further support for some AI/ML operations, measurement data and reporting directly from a RAN node may be required. Whilst the LMF currently provides some data collection functionality, the LMF procedure is limited to positioning related information and cannot be used generally for other types of data. In addition, whilst the LMF can allow data collection from the RAN via a control plane, data collection via the user plane is not supported when the RAN reports measurements.

[0045] The present disclosure aims to overcome at least some of these problems by providing a new data collection framework for supporting AI/ML radio. This framework may define how the UE and/or RAN are configured to report radio measurements and how such measurements are collected and where the data is stored.

[0046] To do this, the present disclosure provides a new data collection function, which is referred to herein as the Radio Data Collection and Coordination Function (RDCCF) for collecting NR related data from UE or RAN. The RDCCF may be a new part of the existing DCCF/DCAF functionality or may be part of the RAN node.

[0047] Embodiments of the present disclosure can provide more flexibility and increased data collection functionality, which may be particularly useful for AI/ML purposes.

[0048] Aspects of the present disclosure are described in the context of a wireless communications system. [0049] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102 (e.g. RAN nodes), one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0050] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0051] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0052] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0053] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0054] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0055] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0056] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106). The CN 106 may comprise an access and mobility function (AMF) serving the UE 104 (i.e. providing one or more services to the UE in an area covered by the AMF). For example, the AMF may communicate with the UE 104 via the NE 102 (e.g. a RAN node). The AMF may communication with the NE 102 over the N2 interface, and the NE 102 may relay messages from the AMF to the UE 102 over the Uu interface using RRC signaling. [0057] The CN 106 may comprise one or more NEs configured to implement one or more respective network functions. For example, the CN may comprise an NE configure to implement a RDCCF, and an NE configured to implement an AMF.

[0058] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0059] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., .=Q) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., jU=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0060] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0061] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /r=0, jU=l , /r=2, jU=3, /r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0062] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0063] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0064] Figure 2 illustrates a data collection framework in accordance with aspects of the present disclosure. The NWDAF provides analytic output to one or more Analytics Consumer Network Functions (NFs) or Application Functions (AFs) or OAM based on Data Collected from one or more Data Producer NFs and/or AFs and/or OAM.

[0065] The DCCF (Data Collection and Coordination Function) receives data collection requests from data collection consumers (e.g. the NWDAF and other NFs) to retrieve data from one on more network functions or from UEs. The consumer requests data by including one or more "Event IDs" where the Event ID denotes the type of data (e.g. UE mobility data) and the type of NF where data is requested.

[0066] For data collection from the UE currents the procedure allows data collection from applications running in the UE. The data collection request from the NWDAF or other NF may trigger the Application Function (AF) to collect data from the UE Application. The procedure for data collection from UE applications is described in 3GPP TS 26.531. A UE Application (which supports providing data to an AF) is configured by the Advanced Services Platform (ASP) with the Application ID to use in the communication with the AF and then the UE Application is configured per Application ID with the following information:

The address of the AF to contact.

The parameters that the UE Application is authorized to provide to the AF.

The authentication information to enable the UE Application to verify the authenticity of the AF that requests data.

[0067] Figure 3 illustrates a data collection framework in accordance with aspects of the present disclosure. In particular Figure 3, illustrates reporting data from a UE application in a UE.

[0068] In one approach, which may be referred to as “direct data collection”, a data collection client collects data from one or more Applications running in the UE. The Data Collection Client then reports the Data to the DCAF (Data Collection Application Function) which then forwards the data to the NWDAF or DCCF (Data Collection and Coordination Function).

[0069] In another approach, which may be referred to as “indirect data collection”, the data collection client is located in the cloud and collects data directly from the Application in the cloud. The AF provisions the data collection client with parameters to be reported according to the "Event ID" requested by the data collection consumer.

[0070] Figure 4 illustrates a process of collecting positioning related data using a LMF in accordance with aspects of the present disclosure. For the Location Services (LCS) architecture, the Location Management Function (LMF) collects positioning related data from the UE and the RAN via the control plane by providing positioning related data in a container.

[0071] Figure 5 illustrates a data collection framework comprising a radio data collection and coordination function (RDCCF) in accordance with aspects of the present disclosure. A method of data collection using this framework may comprise the following steps: [0072] An RDCCF receives a request to collect NR related radio data. The data collection request may be received by a service based interface (SBI) service (e.g. Ndccf service) or via Operations, Administration, and Maintenance (0AM) configuration or from a UE/UE-side node. In one embodiment, a UE/UE-side model sends a data collection request for data by leveraging the existing framework, where the UE/UE-side contacts the DCAF for NR related data. For example, the UE may be triggered internally to collect data to train an ML model. In one embodiment, the trigger may be received by an ML model training client in the UE. The UE may then send the request to the DCAF/RDCCF via the R2 interface (as illustrated in Figure 3). In one embodiment, the request for data collection to the DCAF/RDCCF may be received by an LMF. In such a scenario, the LMF may request data from the RDCCF (e.g. to obtain historical data).

[0073] The data collection request may include an indication of one or more UEs, or a Cell ID, or a target area. Where the data collection request comprises a target area, the RDCCF can determine one or more UEs for data collection by requesting UE information from an AMF. For example, the RDCCF can identify an AMF having a service area at least partially overlapping the target area, and can send a UE information request to that AMF.

[0074] The data collection request may include one or more Event IDs or a Data ID, where each Event ID or Data ID corresponds to a type of data to report. For example, an Event ID or Data ID may indicate CSI measurements, in response to which the RDCCF provides a configuration for collecting CSI measurement data from UE(s) and RAN. In an alternative embodiment, separate identifiers may correspond to CSI measurements from UE and a separate identifier corresponding to reporting CSI measurements from RAN.

[0075] The data collection request may include further requirements and/or metadata regarding how the data should be collected. For example, the further requirements and/or metadata may indicate the required resolution of the data, how often the data should be collected, one or more criteria on sending the data, a requirement for the location information at which the data was generated to be reported, whether the quality of the data is to be reported, timestamp associated to each of the data points/sets, which are to be collected.

[0076] The data collection request may also comprise an indication of the type of data, e.g., the type of radio measurements, CSI Reference Signals (CSI-RS) Reference Signal Received Power (RSRP), or Positioning Reference Signals (PRS) RSRP„ other received signal strength metrics, e.g., RSRQ, RSSI pertaining to any supported or new communication or positioning signal or channel or RS (reference signal).

[0077] The RDCCF may send a message to another network node (e.g., the RAN node or location server) asking it to perform a specific task. This task may be helpful in collection of data, (e.g., sending more pilot signals so the UE can better measure the channel state information). In one embodiment the RDCCF may include within the configuration information to the RAN, assistance information on when to perform a specific task (e.g. sending more pilot signals).

[0078] The RDCCF can provide first (UE) configuration information, for data to be collected by a UE, in a UE data container, and provide second (RAN) configuration information, for data to be collected by a RAN node, in a RAN data container. The configuration(s) may be based on the Event ID/Data ID requested by a consumer and/or based on the request received by the UE/UE-side via R2. The configuration(s) may include information regarding the “further requirements” in the data collection request received by the RDCCF. The first configuration information is for configuring the UE to collect and report data in accordance with the data collection request. The second configuration information is for configuring the RAN node to collect and report data in accordance with the data collection request.

[0079] The RDCCF can determine the AMF serving the target area or the UEs and send the data container(s) in a data collection configuration message to the AMF. The RDCCF may send the data collection configuration message via an Namf service. The data collection configuration message may be an SBI request for data collection and configuration.

[0080] The AMF can receive the data collection configuration message from the RDCCF and extract the data container(s) with the configuration information.

[0081] The AMF can send the configuration information to an appropriate RAN node. The RAN node may be for collecting data as indicated in the data collection request and/or as indicated in the data collection configuration message. Alternatively or in addition, the RAN node may be serving one or more UEs for collecting data as indicated in the data collection request and/or as indicated in the data collection configuration message. The AMF can send the configuration information by including the data container(s) in an N2 message to the RAN node. The N2 message may comprise one or more of: a UE data container within a non-access stratum (NAS) message; and a RAN data container within the N2 message;

[0082] The RAN node can send the UE configuration information to the UE. For example, the UE sends the NAS message via the Uu interface between the UE and the RAN (using Radio Resource Control, RRC, signalling) to the UE.

[0083] A data reporting client in the RAN node can use the RAN data container to identify the parameters and the type of data to report. The data reporting client can report measurements within the RAN data container in the uplink.

[0084] A data reporting client in the UE can use the UE data container to identify the parameters and the type of data to report. The data reporting client can report measurements within the UE Data Container in the uplink.

[0085] The RDCCF can store the data in a database (e.g. in the Analytical Data Repository Function, ADRF).

[0086] In another aspect of the embodiment, the RDCCF may support unsolicited requests to collect radio data. This may be in the form of implicit indications or prior (pre-)configurations regarding the time in which to autonomously trigger the collection of radio data by the various network entities/UEs.

[0087] The UE data container can comprise a protocol that is used between the UE and RDCCF, which is referred to herein as the UE data collection and reporting protocol (UDCRP). The protocol allows for configuration, provisioning and reporting of data to the RDCCF. The protocol can be transparent to other network functions in the path (e.g. the AMF). For example, the UDCRP protocol is included within a container that includes header information (e.g. within an IEI - Information Element Identifier) that defines that the contents include UDCRP protocol information.

[0088] The RAN data container can comprise a protocol that is used between the RAN node and RDCCF, which is referred to herein as the RAN data collection and reporting protocol (UDCRP). The protocol can be transparent to other network functions in the path (e.g. the AMF). The protocol allows for configuration, provisioning and reporting of data to the RDCCF. The protocol is transparent to other network functions in the path (i.e. AMF). For example, the RDCRP protocol is included within a container that includes header information (within an IEI) that defines that the contents include RDCRP protocol information.

[0089] The containers comprising the UDCRP and RDCRP can be transparent to any intermediate nodes (e.g. the AMF) between the UE/RAN and RDCCF.

[0090] In the case of the collection of measurement data for CSI-feedback or beam management, the RDCCF may collect any one or more of the following radio measurement data, for example for training of the model:

UE Measurement Data: o Radio Access Technology (RAT)-dependent Measurements:

■ Channel State Information for each subcarrier

■ Preferred precoder for each subcarrier/subband for each layer

■ The preferred rank and Channel Quality Indicator (CQI) for each subcarrier/subband

■ Ll-RSRP/ Received Signal Strength Indicator (RS SI) measurements for each of all or selected the beams/ beam pairs ■ The accuracy of the measurements or the selected precoder

■ The noise/interference level

■ Resolution of the data

■ Quantization related information, RAT-independent Measurements:

■ Time of the measurements

■ Location of the measurements

■ Bluetooth Received Signal Strength (RSS) measurements including RSSI

■ WLAN (WiFi) measurements including RSSI and Round Trip Time (RTT) information

■ IMU Sensor measurements including gyroscope, accelerometer and so forth.

■ Information regarding the UE conditions, e.g., speed, indoor/outdoor, line of sight/ not line of sight

■ Barometric sensor measurements

Next Generation (NG)-RAN node Data: Cell/site/ sector of the collected data Information regarding the cell condition during the data collection, e.g., cell load Location of the RAN node The Tx beam-ID associated with certain RSRP measurements The angle/azimuth associated with each beam-ID Information regarding the pilots transmitted.

[0091] The radio measurements data mentioned above may each be identified by a data identifier or name. In another embodiment a data identifier or name may map to a group of multiple radio measurements.

[0092] In the case of the collection of positioning measurement data, the RDCCF may collect the following radio measurement data based on the node performing measurements:

UE Measurement Data: RAT -dependent Measurements : ■ DL/SL Reference Signal Time Difference (RSTD) (DL-based or SL-based measurements)

■ DL/SL PRS Time of Arrival (TOA) (DL-based or SL-based measurements)

■ DL/SL PRS RSRP (DL-based or SL-based measurements)

■ DL/SL PRS RSRPP (DL-based or SL-based measurements)

■ UE Rx-Tx time difference (DL-based or SL-based measurements)

■ SS-RSRP(RSRP for Physical Resource Manager, RRM), SS- Reference Signal Received Quality (RSRQ)(for RRM), CSLRSRP (for RRM)

■ CSLRSRQ (for RRM), SS-RSRP (for RRM) (DL-based measurements)

■ DL/SL Carrier phase measurements (DL-based or SL-based measurements)

■ DL/SL Carrier phase difference measurements (DL-based or SL-based measurements)

■ DL Enhanced Cell ID (E-CID)

■ LTE E-CID

■ SL Physical Sidelink Shared Channel (PSSCH) RSRP,

■ DL PRS RSSI (Received Signal Strength Indicator)

■ LTE Observed Time Difference of Arrival (OTDOA) measurements RAT-independent Measurements

■ A-GNSS measurements including common assistance data, which may be applicable to any GNSS constellation, e.g., Galileo, GPS, GLONASS, etc., generic assistance data for a specific GNSS constellations or periodic GNSS assistance data that is used to provide GNSS control information on a periodic basis to the UE/device.

■ Bluetooth RSS measurements including RSSI

■ WLAN (WiFi) measurements including RSSI and RTT information

■ Inertial Measurement Unit (IMU) Sensor measurements including gyroscope, accelerometer and so forth.

■ Barometric sensor measurements

NG-RAN node measurements: UL- Relative Time of Arrival (RTOA) (UL-based measurement) UL Sounding Reference Signal (SRS) RSRP (UL-based measurement) o UL SRS RSRPP (UL-based measurement) o gNB Rx-Tx time difference measurements (UL-based measurement) o UL- Angle of Arrival (AoA) (UL-based measurement) o UL Carrier phase measurements (UL-based measurements) o UL Carrier phase difference measurements (UL-based measurements) o UL NR E-CID o LTE E-CID

[0093] The positioning measurement data mentioned above may each be identified by a data identifier or name. In another embodiment a data identifier or name may map to a group of multiple radio measurements data.

[0094] In one aspect of the embodiment, the above radio measurement data may be collected via the location server, e.g., LMF or it may be collected directly from the node performing the measurements, e.g., base station/NG-RAN node or UE.

[0095] Figure 6 6 illustrates data collection and reporting protocols for data collection for a UE and RAN via a control plane in accordance with aspects of the present disclosure. As can be seen, in this embodiment, the protocols are transparent to the network functions in the path (i.e. the AMF). The UDCRP 601 allows communication between the UE 602 and RDCCF 604 via the AMF 606 for configuring the UE 602 to make measurements and report data. The RDCRP 603 allows communication between the RAN node 607 and RDCCF 604 via the AMF 606 for configuring the RAN node 607 to make measurements and report data. The RDCCF 604 sends and receives messages to and from the AMF 606 in the CN via Ndccf 608 (or a new interface that can be denoted Nrdccf). The AMF 606 sends and receives messages to and from the RAN node 610 via the N2 interface 612, and the RAN node 608 sends and receives messages (e.g. NAS messages) to and from the UE over the Uu interface 614.

[0096] Figure 7 illustrates a signaling flowchart of a process for collecting data in accordance with aspects of the present disclosure. The process is for configuring a UE and RAN node for data collection. [0097] At step 701, a consumer requires data from UE and/or RAN in order, for example, to train an AI/ML model used by the UE or RAN for NR radio related procedures (e.g. beam management). The consumer may be an AF, a third party AI/ML training server for example.

[0098] At step 702, the consumer sends a data collection request via an SBI interface to the RDCCF. The data collection request can include one or more of an Event ID, Data ID, Data Type of the data needed to be collected, an area of interest (where data are to be collected), and target UEs (if data is to be collected by specific UEs).

[0099] At step 703, the RDCCF determines what data are needed to be collected from UE and or RAN based on the request in step 702. For example, the RDCCF can determine the data to be collected based on one or more of the parameters comprised by the data collection request.

[0100] At step 704, the RDCCF prepares configuration information for configuring one or more UEs and/or one or more RAN nodes to collect the required data. For example, the RDCCF can provide configuration information for within a UDCRP protocol for a UE and within a RDCRP protocol for a RAN node. The configuration information to the RAN node may include additional information to the RAN node to perform a specific task to assist one or more UEs in performing measurements to collect data. In one embodiment, the configuration information may indicate to the RAN node to send more pilot signals to the UE.

[0101] At step 705, the RDCCF determines the (appropriate) AMF serving a target area and UEs according to the data collection request in steps 701 and 702.

[0102] At step 706, the RDCCF sends a data collection configuration message (also referred to as “configuration message” herein) to the determined AMF. The data collection configuration message comprises the configuration information. The data collection configuration message may comprise the UDCRP and/or RDCRP in respective data containers. The data collection configuration message may further comprise one or more UE identifiers for identifying the UEs to which the configuration information should be sent. The data collection configuration message is typically a Namf message sent to the AMF.

[0103] At step 707 the AMF can extract the configuration information from the data collection configuration message. For example, AMF extracts respective data containers comprising the UE configuration information and the RAN configuration information. For example, the AMF can extract the data container comprising the UDCPR and/or the data container comprising RDCRP from the data collection configuration message. The AMF can insert the data container comprising the RAN configuration information in an N2 message towards the RAN. When the data collection configuration message comprises a UDCRP container, the AMF can page the UE(s) when the UE(s) are in IDLE mode before sending the N2 message to the RAN node.

[0104] At step 708, the AMF sends the data container(s) to the RAN node. For example, the AMF can include the RDCRP protocol within the N2 message, and the UDCRP protocol within the NAS message within N2.

[0105] At step 709, the data reporting client in the RAN can check the configuration information in the RAN data container and determine the data to collect and report. For example, the RAN node can check the configuration information within the RDCRP protocol. In some embodiments, the RAN node may perform one or more specific tasks that are indicated by the RDCCF to assist measurements to collect the data.

[0106] AT step 710, the RAN node sends data container with the UE configuration information to the UE. For example, the RAN node sends the NAS message via RRC signalling to the UE. In another implementation, depending on the pay load size of the radio measurements to be collected, user plane signalling may be used to request radio measurement data from the UE.

[0107] At step 711, the data reporting client in the UE checks the configuration information and determines the data to collect and report. For example, the UE extracts the UDRCP from the data container in the received NAS message and extracts the configuration information from the UDCRP. [0108] In an alternative embodiment, a request for data from a consumer may be sent directly to the AMF serving the target area and/or UEs. The AMF then initiates a communication session with an RDCCF serving the target area. The AMF then sends a data collection request to the RDCCF. The data collection request comprises information on the data that needs to be reported. The RDCCF then constructs configuration information for the UE and RAN as described in step 703. The RDCCF provides in the active communication session the UDCRP and RDCRP protocols as required. The AMF then sends the UDCRP and RDCRP in active N2 sessions between the AMF and RAN (i.e. when the UE enters connected state and establishes a NAS session with the AMF). The AMF may also page UEs if UEs are in IDLE mode, in order to receive the configuration information.

[0109] Figure 8 illustrates a signaling flowchart of a process for reporting collected data in accordance with aspects of the present disclosure. The process is for reporting collection data from a UE and from a Ran node.

[0110] At step 801, the data reporting clients in the UE and RAN node respectively have received configuration information as described in relation to Figure 7.

[0111] At step 802, once enough data are collected, the UE reports data e.g. within the UDCRP protocol. The UE and RAN node may start data collection after a certain help task is executed by the UE or RAN (e.g. RAN sends additional pilot signals) based on configuration information from the RDDCF.

[0112] At step 803, the UE includes the UDCRP protocol in a NAS message within RRC signalling towards the RAN. In another implementation, depending on the payload size of the radio measurements to be collected, user plane signalling may be used to report radio measurement data from the UE. The configuration information provided by the RDCCF may indicate the reporting path and may indicate one of user plane and control plane. The UE can then determine the reporting path based on the configuration information.

[0113] At step 804, when enough data are collected, the RAN node reports the data within the RDCRP protocol. The “enough data” collection may be based on information contained in the data collection request, e.g., number of measurement samples to be reported, and/or whether LI or L3 filtering is applied.

[0114] At step 805, the RAN includes in the N2 message the NAS message received from the UE and also includes the RAN related data within the RDCRP protocol within the N2 message to the AMF.

[0115] At step 806, the AMF extracts the UDCRP and RDCRP protocols.

[0116] At step 807, the AMF sends the collected data to the RDCCF. For example, the AMF includes the UDCRP and RDCRP protocols within a container in an Nrddcf message towards the RDCCF.

[0117] At step 808, the RDCCF receives the collection data. For example, the RDCCF extracts the data from UDCRP and RDCRP protocol. The RDCCF may store the collected data in a database, for example in the ADRF (using an Nadrf message).

[0118] At step 809, the RDCCF reports the data to the consumer that requested the data according to step 701 in Figure 7.

[0119] In an additional embodiment the RDCCF may use the existing LPP/SLPP/NRPP protocols (LTE Positioning Protocol, Sidelink positioning protocol, NR Positioning Protocol) defined for positioning (and supported by the LMF) to request UE and RAN to report positioning related data. In such a case in step 704 in Figure 7, the RDCCF prepares configuration data by re-using the LPP/SLPP/NRPP protocols and in the following steps of Figure 6 the RDCCF sends to the AMF the LPP/SLPP/NRPP protocols instead of the UDCRP and RDCRP protocols. In an alternative embodiment the RAN data reporting client in the RAN node may report data via a new SBI interface directly to the RDCCF. In such a case instead of steps 805-807 in Figure 8, the RAN client sends data directly to the RDCCF via the SBI interface.

[0120] Described below is an embodiment comprising data collection via the user plane.

[0121] The UE and RAN node may receive configuration information from RDDCF using the UDCRP and RDCRP protocols indicating what data are need to be reported, and nay receive further information such as how often the data should be transmitted and with what granularity. The information may also include configuration information for the RAN node with further information, e.g. sending additional pilot signals to the UE to collect data. The UE may be triggered internally to collect data to train an ML model. In one embodiment the trigger may be received by the ML model training client in the UE. The UE may then send the request to the DCAF/RDCCF via the R2 interface as described in Figure 3. The DCAF/RDCCCF may then map the request into a configuration for the UE and the RAN to collect data.

[0122] The UE instead of sending the data via the control plane may send the data via the user plane as follows:

[0123] The UE may report data via user plane by establishing a secure connection with the RDCCF. The UE may be configured with a DNN/S-NSSAI of the PDU session that needs to be established to report data. The UE may also be provisioned with a URSP rule where the URSP rule includes the S-NSSAI/DNN to provide the data within the UDCRP protocol.

[0124] Alternatively, the user plane function (UPF) may be configured to route data sent via a specific DNN and/or S-NSSAI combination to the RDCCF. The configuration may be part of N4 rules provided by the SMF and corresponding policies provided by the PCF.

[0125] Figure 9 illustrates an example of a UE 900 in accordance with aspects of the present disclosure. The UE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0126] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0127] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the UE 900 to perform various functions of the present disclosure.

[0128] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the UE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0129] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the UE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the UE 900 in accordance with examples as disclosed herein. The UE 900 may be configured to support a means for receiving a data collection message comprising a UE data container comprising data collection configuration information within a UE data collection and reporting protocol, wherein the data collection configuration information comprises a first indication of one or more data types and a first indication of a reporting frequency; collect data of the one or more data types; and report the data at the reporting frequency using the UE data collection and reporting protocol.

[0130] The controller 906 may manage input and output signals for the UE 900. The controller 906 may also manage peripherals not integrated into the UE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0131] In some implementations, the UE 900 may include at least one transceiver 908. In some other implementations, the UE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0132] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0133] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0134] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0135] The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0136] The controller 1002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0137] The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruct! on(s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory address of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1000.

[0138] The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000). In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000).

[0139] The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1002 and/or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions. For example, the processor 1000 and/or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0140] The one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000). In some other implementations, the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000). One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.

[0141] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1000 may be configured to or operable to support a means for obtaining a data collection message comprising a UE data container comprising data collection configuration information within a UE data collection and reporting protocol, wherein the data collection configuration information comprises a first indication of one or more data types and a first indication of a reporting frequency; obtain data of the one or more data types; and provide the data at the reporting frequency using the UE data collection and reporting protocol. [0142] Figure 11 illustrates an example of a NE 1100 in accordance with aspects of the present disclosure. The NE 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0143] The processor 1102, the memory 1104, the controller 1106, or the transceiver

1108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0144] The processor 1102 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1102 may be configured to operate the memory 1104. In some other implementations, the memory 1104 may be integrated into the processor 1102. The processor 1102 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the NE 1100 to perform various functions of the present disclosure.

[0145] The memory 1104 may include volatile or non-volatile memory. The memory 1104 may store computer-readable, computer-executable code including instructions when executed by the processor 1102 cause the NE 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1104 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0146] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the NE 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the NE 1100 in accordance with examples as disclosed herein. The NE 1100 may be configured to support a means for receiving a request for collecting data from at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes; and sending a configuration message to a network function serving the set of UEs or the set of RAN nodes, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency.

[0147] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the NE 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the NE 1100 in accordance with examples as disclosed herein. The NE 1100 may be configured to support a means for receive a configuration message for at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes to collect data, wherein the configuration message comprises: a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency; for the or each UE, send the UE data container to the UE; and for the or each RAN node, send the RAN data container to the RAN node. [0148] The controller 1106 may manage input and output signals for the NE 1100. The controller 1106 may also manage peripherals not integrated into the NE 1100. In some implementations, the controller 1106 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1106 may be implemented as part of the processor 1102.

[0149] In some implementations, the NE 1100 may include at least one transceiver 1108. In some other implementations, the NE 1100 may have more than one transceiver 1108. The transceiver 1108 may represent a wireless transceiver. The transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or a combination thereof.

[0150] A receiver chain 1110 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1110 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1110 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1110 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1110 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0151] A transmitter chain 1112 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1112 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1112 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1112 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0152] Figure 12 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0153] At 1202, the method may include a data collection message comprising a UE data container comprising data collection configuration information within a UDCRP, wherein the data collection configuration information comprises a first indication of one or more data types and a first indication of a reporting frequency. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a UE as described with reference to Figure 9.

[0154] At 1204, the method may include collecting data of the one or more data types. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a UE as described with reference to Figure 9.

[0155] At 1206, the method may include reporting the data at the reporting frequency using the UE data collection and reporting protocol. The operations of 1206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed by a UE as described with reference to Figure 9.

[0156] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. [0157] Figure 13 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0158] At 1302, the method may include receiving a request for collecting data from at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a NE as described with reference to Figure 11.

[0159] At 1304, the method may include sending a configuration message to a network function serving the set of UEs or the set of RAN nodes, wherein the configuration message. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a NE as described with reference to Figure 11.

[0160] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0161] Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0162] At 1402, the method may include receiving a configuration message for at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes to collect data. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a NE as described with reference to Figure 11. [0163] At 1404, the method may include sending a UE data container to the UE. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a NE as described with reference to Figure 11.

[0164] At 1406, the method may include sending a RAN data container to the RAN node. The operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by a NE as described with reference to Figure 11.

[0165] Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a CN as described herein. In some implementations, the CN may comprise one or more NEs to implement network functions of the CN.

[0166] At 1502, the method may include receiving a request for collecting data from a least one of a set of user equipments (UEs) and a set of Radio Access Network (RAN) nodes. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a NE as described with reference to Figure 11.

[0167] At 1504, the method may include sending a configuration message to an AMF. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 11.

[0168] At 1506, the method may include receiving the configuration message at the AMF. The operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed by a NE as described with reference to Figure 11. [0169] At 1508, the method may include sending a UE data container to the UE. The operations of 1508 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1508 may be performed by a NE as described with reference to Figure 11.

[0170] At 1510, the method may include sending a RAN data container to the RAN node. The operations of 1510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1510 may be performed by a NE as described with reference to Figure 11.

[0171] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0172] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a request for collecting data from at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes; and transmit a configuration message to a network function serving the set of UEs or the set of RAN nodes, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency.

2. The network entity of claim 1, wherein the at least one processor is further configured to cause the network entity to implement a radio data collection and coordination function of a core network.

3. The network entity of claim 1 or 2, wherein the at least one processor is further configured to cause the network entity to identify the network function based on at least one of an area served by the network function; one or more UEs served by the network function; and one or more RAN nodes served by the network function.

4. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to determine the first or the second indication of one or more data types from a data identifier comprised by the request.

5. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to determine the set of UEs or the set of RAN nodes from a target area indicator comprised by the request.

6. The network entity of any one of the preceding claims, wherein the UE configuration information further comprises one or more of: a location indication for configuring the UE to report a location at which the data was generated; a quality indication for configuring the UE to report an indication of a quality of the data that is reported; and a timestamp indication for configuring the UE to report a timestamp associated with each data point or set of the collected data.

7. The network entity of any one of the preceding claims, wherein, when the request is for collecting data for a UE, the RAN configuration information comprises assistance information for configuring the RAN node to provide additional pilot signals to one or more UEs for collecting and reporting data.

8. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to include the UE configuration information in a UE data collection and reporting protocol.

9. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to include the RAN configuration information in a RAN data collection and reporting protocol.

10. The network entity of any one of the preceding claims, wherein the request comprises location information relating to a target area for data collection, and the at least one processor is configured to cause the network entity to determine the network function based on the location information and to send to the network function a request for UE information to identify the set of UEs served by the network function.

11. A network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a configuration message for at least one of a set of user equipments (UEs) and a set of radio access network (RAN) nodes to collect data, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency; for the or each UE, send the UE data container to the UE; and for the or each RAN node, send the RAN data container to the RAN node.

12. The network entity of claim 11, wherein the network entity is configured to implement an access and mobility function (AMF) of a core network.

13. The network entity of claim 11 or 12, wherein the at least one processor is configured to send the UE data container to the UE within a non-access stratum (NAS) message and to send the RAN data container to the RAN node within an N2 message.

14. The network entity of any one of claims 11 to 13, wherein the at least one processor is configured to cause the network entity to: receive a request for collecting data from the set of UEs or from the set of RAN nodes; and determine a network function for determining a data collection configuration send the request to the network function; and receive from the network function the configuration message.

15. A core network (CN) in a wireless communication network, comprising: a radio data collection and coordination function (RDCCF) configured to receive a request for collecting data from at least one of a set of user equipments (UEs) and a set of Radio Access Network (RAN) nodes; an access and mobility management function (AMF) serving the set of UEs or the set of RAN nodes; wherein the RDCCF is configured to send a configuration message to the AMF, wherein the configuration message comprises a UE identifier and a UE data container comprising UE configuration information comprising a first indication of one or more data types and a first indication of a reporting frequency, or a RAN data container comprising RAN configuration information comprising a second indication of one or more data types and a second indication of a reporting frequency; wherein the AMF is configured to receive the configuration message and to, for the or each UE, send the UE data container to the UE, and, for the or each RAN node, send the RAN data container to the RAN node.

16. The CN of claim 15, wherein the AMF is configured to send the UE data container in a non-access stratum (NAS) message and the RAN data container in a N2 message.

17. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a data collection message comprising a UE data container comprising data collection configuration information within a UE data collection and reporting protocol, wherein the data collection configuration information comprises a first indication of one or more data types and a first indication of a reporting frequency; collect data of the one or more data types; and report the data at the reporting frequency using the UE data collection and reporting protocol.

18. The UE of claim 17, wherein the at least one processor is configured to cause the UE to extract the UE data collection and reporting protocol from the data container; and extract the UE data collection configuration information from the UE data collection and reporting protocol.

19. The UE of claim 17 or 18, wherein the data collection message is a non-access stratum (NAS) message.

20. The UE of any one of claims 17 to 19, wherein the at least one processor is further configured to cause the UE to collect and report physical layer and link layer related data.