[go: up one dir, main page]

WO2024222021A1 - Collecte de données radio d'ue - Google Patents

Collecte de données radio d'ue Download PDF

Info

Publication number
WO2024222021A1
WO2024222021A1 PCT/CN2023/142860 CN2023142860W WO2024222021A1 WO 2024222021 A1 WO2024222021 A1 WO 2024222021A1 CN 2023142860 W CN2023142860 W CN 2023142860W WO 2024222021 A1 WO2024222021 A1 WO 2024222021A1
Authority
WO
WIPO (PCT)
Prior art keywords
radio data
network device
processor
app
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/142860
Other languages
English (en)
Inventor
Lizhuo ZHENG
Haiyan Luo
Congchi ZHANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2023/142860 priority Critical patent/WO2024222021A1/fr
Publication of WO2024222021A1 publication Critical patent/WO2024222021A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present disclosure relates to wireless communications, and more specifically to user equipments (UEs) , base stations, processors, and methods for collecting user equipment (UE) radio data.
  • UEs user equipments
  • base stations base stations
  • processors processors
  • UE radio data user equipment
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station 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) .
  • 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)) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • the 3 rd Generation Partnership Project (3GPP) has proposed to use artificial intelligence or machine learning (AI/ML) technology to optimize physical layer operation.
  • AI/ML artificial intelligence or machine learning
  • an AI/ML training entity needs to collect data for the AI/ML training.
  • the present disclosure relates to methods, apparatuses, and systems that support collection of UE radio data.
  • a first network device may comprise: a processor; and a transceiver coupled to the processor, wherein the processor is configured to:in response to a request for collecting user equipment (UE) radio data, transmit, via the transceiver and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) ; and transmit, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • the request for collecting UE radio data may be received from the UE AS layer of the UE.
  • the request for collecting UE radio data and the APP report indication may include an identification information associated with the UE APP.
  • the request for collecting UE radio data may be received from access and mobility management function (AMF) , and the processor may be further configured to: receive, via the transceiver and from the AMF, information for determining the UE; and determine the UE at least based on the information for determining the UE.
  • AMF access and mobility management function
  • the information for determining the UE may include at least one of: at least one UE selectin criteria; a UE identifier (ID) of the UE; and a UE list including the UE.
  • the processor may be further configured to: receive, via the transceiver and from the AMF, an information on a second network device, an information on a third network device, an APP identifier (ID) indicating the UE APP, and a task indication information related to an AI/ML model to which the collected UE radio data is to be applied; and transmit, via the transceiver and to the UE, the information on the second network device, the information on the third network device, the APP ID, and the task indication information, wherein the collected UE radio data is obtained by the third network device from the UE APP and transmitted by the third network device to the second network device based on the information on the second network device and the information on the third network device, and is used by the second network device to perform AI/ML model training.
  • ID APP identifier
  • the request for collecting UE radio data may include a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the data report and collection configuration may include at least one of: UE radio data parameters that need to be measured and collected; a format of the UE radio data and grouping standard when reporting the UE radio data; reporting rules of the UE radio data; collecting duration and sampling rules of the UE radio data; information associated with a timestamp, a scenario, a corresponding configuration when collecting the UE radio data; and criteria that need to be satisfied when collecting the UE radio data.
  • the request for collecting UE radio data includes a task indication information related to an AI/ML model to which the UE radio data is to be applied, and the processor may be further configured to: determine, based on the task indication information, a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the task indication information may include a task type, and the task type includes at least one of: UE side CSI prediction; UE side CSI compression; UE side beam prediction; and UE side positioning.
  • the processor may be further configured to: determine, based on the APP report indication, a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • a second network device may comprise: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit, via the transceiver and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request; and receive, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • AMF access and mobility management function
  • the request for collecting UE radio data may include a task indication information related to an AI/ML model to which the UE radio data is to be applied, and wherein receiving the UE radio data comprises: receive, via the transceiver and from the third network device, the UE radio data together with the task indication information.
  • the model training request may be received from at least one consumer for AI/ML model training.
  • the at least one consumer may include at least one of operations administration and maintenance (OAM) , UE side over the top (OTT) server, and radio access network (RAN) node.
  • OAM operations administration and maintenance
  • OTT UE side over the top
  • RAN radio access network
  • the model training request may include at least one of: at least one UE identifier (ID) and/or UE IP address; area of interest (AOI) information; task indication information related to an AI/ML model; requested model related information; UE related information; and a target address of a trained AI/ML model.
  • ID UE identifier
  • AOI area of interest
  • the processor may be further configured to: perform model training on the AI/ML model by using the collected UE radio data; and transmit, via the transceiver and to the at least one consumer, the trained AI/ML model.
  • the request for collecting UE radio data may include a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the data report and collection configuration may include at least one of: UE radio data parameters that need to be measured and collected; a format of the UE radio data and grouping standard when reporting UE radio data; reporting rules of the UE radio data; collecting duration and the sampling rules of the UE radio data; information associated with a timestamp, a scenario, a corresponding configuration when collecting the UE radio data; and criteria that need to be satisfied when collecting the UE radio data.
  • the third network device may be determined by the second network device from a set of predetermined third network devices based on capabilities of the predetermined third network devices for UE radio data collection.
  • the AMF may be determined by the second network device from a set of predetermined AMFs at least based on the UE related information or the AOI information.
  • the request for collecting UE radio data in the case that the request for collecting UE radio data is transmitted to the third network device, the request for collecting UE radio data may include at least one of the at least one UE ID and the task indication information.
  • the processor may be further configured to: determine, based on the at least one UE ID, at least one UE IP address, at least one APP ID, and at least one protocol data unit (PDU) session ID between at least one UE APP indicated by the at least one APP ID and the third network device, wherein the request for collecting UE radio data further includes the at least one APP ID, the at least one UE IP address, and the at least one PDU session ID, wherein the at least one APP ID includes an APP ID of the UE APP deployed on the UE.
  • PDU protocol data unit
  • the request for collecting UE radio data may further include the at least one UE IP address.
  • the request for collecting UE radio data may include at least one of: an information for determining the UE; an information on the second network device; an information on the third network device, at least one APP identifier (ID) indicating the at least one UE APP, and a task indication information related to an AI/ML model to which the UE radio data is to be applied.
  • ID APP identifier
  • a third network device may comprise: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver and from a second network device, a first request for collecting user equipment (UE) radio data; transmit, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request ; and receive, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • UE user equipment
  • the second request may include a data report and collection configuration, generated by the third network device or received via the first request from the second network device, for configuring collection and reporting of the UE radio data.
  • the data report and collection configuration may include at least one of: UE radio data parameters that need to be measured and collected; a format of the UE radio data and grouping standard when reporting UE radio data; reporting rules of the UE radio data; collecting duration and the sampling rules of the UE radio data; information associated with a timestamp, a scenario, a corresponding configuration when collecting the UE radio data; and criteria that need to be satisfied when collecting the UE radio data.
  • the first request may include at least one of the at least one UE ID and the task indication information.
  • the first request may further include at least one APP ID, at least one UE IP address, and at least one PDU session ID between at least one UE APP indicated by the at least one APP ID and the third network device, wherein the at least one APP ID includes an APP ID of the UE APP deployed on the UE.
  • the processor may be further configured to: determine at least one UE IP address, at least one APP ID, and at least one protocol data unit (PDU) session ID between at least one UE APP indicated by the at least one APP ID and the third network device based on the at least one UE ID, wherein the at least one APP ID includes an APP ID of the UE APP deployed on the UE.
  • PDU protocol data unit
  • a user equipment may comprise: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE; perform UE radio data collection based on the configuration at the UE AS layer; and transmit the collected UE radio data to the UE APP from the UE AS layer.
  • AS UE access stratum
  • the processor may be further configured to: receive, via the transceiver and from a third network device, a request for collecting UE radio data; and transmit, via the transceiver and to the first network device, the request from the UE AS layer of the UE, wherein the configuration is transmitted by the first network device in response to the request.
  • the request for collecting UE radio data and the APP report indication may include an identification information associated with the UE APP.
  • the processor may be further configured to: transmit, via the transceiver and to a third network device, the collected UE radio data from the UE APP.
  • the processor may be further configured to: determine whether there is available UE radio data for the request for collecting UE radio data; and transmit, via the transceiver and to the third network device, the available radio data from the UE APP.
  • the request for collecting UE radio data may include a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the data report and collection configuration may include at least one of: UE radio data parameters that need to be measured and collected; a format of the UE radio data and grouping standard when reporting UE radio data; reporting rules of the UE radio data; collecting duration and the sampling rules of the UE radio data; information associated with a timestamp, a scenario, a corresponding configuration when collecting the UE radio data; and criteria that need to be satisfied when collecting the UE radio data.
  • the request for collecting UE radio data may include a task indication information related to an AI/ML model to which the UE radio data is to be applied, wherein a data report and collection configuration for configuring collection and reporting of the UE radio data is determined by the first network device based on the task indication information.
  • the task indication information may include a task type, and the task type includes at least one of: UE side CSI prediction; UE side CSI compression; UE side beam prediction; and UE side positioning.
  • a processor for wireless communication may comprise: at least one memory; and a controller coupled with the at least one memory and configured to cause the processor to: in response to a request for collecting user equipment (UE) radio data, transmit, via a transceiver of a first network device and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) ; and transmit, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • a method performed by a first device may comprise: in response to a request for collecting user equipment (UE) radio data, transmitting, via the transceiver and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) ; and transmitting, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • a processor for wireless communication may comprise: at least one memory; and a controller coupled with the at least one memory and configured to cause the processor to: transmit, via a transceiver of a second network device and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request; and receive, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • AMF access and mobility management function
  • a method performed by a second device may comprise: transmitting, via a transceiver and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request; and receiving, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • AMF access and mobility management function
  • a processor for wireless communication may comprise: at least one memory; and a controller coupled with the at least one memory and configured to cause the processor to: receive, via a transceiver of a third network device and from a second network device, a first request for collecting user equipment (UE) radio data; transmit, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request ; and receive, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • UE user equipment
  • a method performed by a third device may comprise: receiving, via the transceiver and from a second network device, a first request for collecting user equipment (UE) radio data; transmitting, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request ; and receiving, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • UE user equipment
  • a processor for wireless communication may comprise: at least one memory; and a controller coupled with the at least one memory and configured to cause the processor to: receive, via a transceiver of a user equipment (UE) and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE; perform UE radio data collection based on the configuration at the UE AS layer; and transmit the collected UE radio data to the UE APP from the UE AS layer.
  • UE user equipment
  • AS UE access stratum
  • a method performed by a user equipment may comprise: receiving, via a transceiver and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE; performing UE radio data collection based on the configuration at the UE AS layer; and transmitting the collected UE radio data to the UE APP from the UE AS layer.
  • AS UE access stratum
  • FIG. 1 illustrates an example of a wireless communications system that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of data collection procedure from UE application associated with aspects of the present disclosure.
  • FIG. 3 illustrates a signalling procedure for collecting UE radio data in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example signalling procedure for collecting UE radio data in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates an example procedure for sending UE radio data collection request from DCAF to UE AS Layer in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates another example signalling procedure for collecting UE radio data in accordance with aspects of the present disclosure.
  • FIGS. 7 to 10 illustrate examples of devices that support collection of UE radio data in accordance with aspects of the present disclosure.
  • FIGS. 11 to 14 illustrate examples of processors that support collection of UE radio data in accordance with aspects of the present disclosure.
  • FIGS. 15 and 18 illustrate flowcharts of methods that support collection of UE radio data in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band internet of things (NB-IoT) , and so on.
  • NR 5G new radio
  • LTE long term evolution
  • LTE-A LTE-advanced
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • NB-IoT narrow band internet of things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • any suitable generation communication protocols including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.
  • the term “network device” generally refers to a node in a communication network via which a terminal device can access the communication network and receive services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on
  • terminal device generally refers to any end device that may be capable of wireless communications.
  • a terminal device may also be referred to as a communication device, a user equipment (UE) , an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) .
  • UE user equipment
  • SS subscriber station
  • UAV unmanned aerial vehicle
  • MS mobile station
  • AT access terminal
  • the terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain
  • 3GPP has proposed to use AI/ML technology to optimize physical layer operation, a.k.a. AI for air interface, for some use cases such as channel state information (CSI) feedback compression, CSI time domain prediction, beam spatial domain prediction, beam time domain prediction, AI/ML assisted positioning estimation, direction positioning, and the like.
  • an AI/ML model may be deployed at UE/gNB/location management function (LMF) , while it could be upon gNB, operations administration and maintenance (OAM) , UE-side over the top (OTT) server, UE, LMF, core network (CN) (besides LMF, e.g., network data analytics function (NWDAF) ) to train the AI/ML model as listed in Table 1 below.
  • LMF location management function
  • OAM operations administration and maintenance
  • OTT UE-side over the top
  • UE UE
  • LMF operations administration and maintenance
  • CN core network
  • NWDAF network data analytics function
  • Table 1 Possible Combination of AI/ML training entity and inference entity
  • the AI/ML training entity In order to train an AI/ML model, the AI/ML training entity needs to collect data for the AI/ML training.
  • Some examples of the training data for each use case may include data for CSI compression, CSI prediction, beam prediction, positioning, and the like.
  • UE radio data to be collected may include ground-truth CSI from network (NW) in scaler quantization and/or codebook-based quantization (e.g., e-type II like) , and assisted information for categorizing the data for the purpose of differentiating characteristics of data due to specific configuration, scenarios, site etc.
  • NW network
  • codebook-based quantization e.g., e-type II like
  • UE radio data to be collected may include CSI generation model training dataset (e.g., raw channel or the eigenvector as model input and latent space vector before or after quantization as model output) , and assisted information for categorizing the data for the purpose of differentiating characteristics of data due to specific configuration, scenarios, site etc.
  • CSI generation model training dataset e.g., raw channel or the eigenvector as model input and latent space vector before or after quantization as model output
  • UE radio data to be collected may include consecutive CSIs (historical CSIs and future CSIs) and assistance information for model management e.g., site/scenario/dataset related information.
  • types of CSIs may include raw channel matrices, precoding matrix indicators (PMIs) , eigen vectors, or the like.
  • UE radio data to be collected may be associated with Set B (for example, L1-RSRP measurement based on Set B or a subset of Set B) , label data (e.g., L1-RSRP measurement based on Set A or a subset of Set A, Partial L1-RSRP measurement based on Set A or a subset of Set A and beam indicator, and Top-k beam indicator) , time related information (e.g. timestamps) , and assistance information (e.g., site/scenarios/dataset related information such as dataset ID, gNB-side related assistance information, and UE-side related assistance information) .
  • Set B for example, L1-RSRP measurement based on Set B or a subset of Set B
  • label data e.g., L1-RSRP measurement based on Set A or a subset of Set A
  • Partial L1-RSRP measurement based on Set A or a subset of Set A and beam indicator e.g. timestamps
  • UE radio data with the measurement type may include channel impulse response (CIR) /power delay profile (PDP) /delay profile (DP) , and reference signal receiving power (RSRP) /reference signal time difference (RSTD) .
  • CIR channel impulse response
  • PDP power delay profile
  • DP delay profile
  • RSRP reference signal receiving power
  • RSTD reference signal time difference
  • the UE radio data with the label type may include location coordinate, timing estimation and line of sight (LOS) /non line of sight (NLOS) .
  • LOS line of sight
  • NLOS non line of sight
  • the AI/ML training node which could be gNB, OAM, UE-side OTT server, UE, LMF, CN (besides LMF)
  • the AI/ML training node which could be gNB, OAM, UE-side OTT server, UE, LMF, CN (besides LMF)
  • NWDAF Network Data Analytics Function
  • the possible use cases could be, for example, the UE side CSI compression, CSI prediction and beam prediction, UE side positioning, as listed in the Table 1 above.
  • L1 Layer 1
  • UE radio data is used to represent the UE data types mentioned above.
  • NWDAF NWDAF collect necessary radio data from UE, through which path to transmit, and how to configure the UE to do certain radio data collection.
  • Trace/minimization of drive test MDT
  • TCE OAM/trace collection entity
  • the NWDAF may directly fetch the UE radio data from OAM.
  • RRM radio resource management
  • the gNB may anyway configure the UE to report its L1/L3 measurements, the required training data is available at gNB already and it will be much more efficient that the AI/ML training entity may retrieve the training data from gNB directly, rather than requests the UE to send logged measurements again over air interface which consumes additional radio resources.
  • RRM radio resource management
  • the NWDAF may interact with DCAF to collect data from UE Application as an input for analytics generation and AI/ML model training.
  • the data collection request from NWDAF may trigger the DCAF to collect data from the UE Application.
  • the data that the DCAF can collect is the UE Application layer data and this is based on a prerequisite that the vendor (operator) has deployed the Application at UE side.
  • the NWDAF may interact with an application function (AF) to collect data from UE application (s) as an input for analytics generation and AI/ML model training.
  • the AF may be in the mobile network operator (MNO) domain or an AF external to MNO domain.
  • the data collection request from NWDAF may trigger the AF to collect data from the UE application (APP) .
  • the AF may be referred as data collection AF (DCAF) .
  • the UE APP may establish a connection to the DCAF in the MNO domain or external to MNO domain over user plane via a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the AF communicates with the UE Application and collects data from UE Application. Both direct data collection procedure (from the UE Application to the AF, either in trusted domain or untrusted domain) and indirect data collection procedure (from the UE Application to the Application server and from the Application server to the AF) shall be supported.
  • FIG. 2 illustrates an example of data collection procedure from UE application associated with aspects of the present disclosure.
  • the example data collection procedure illustrated in FIG. 2 will be explained with reference to 3GPP TS 23.288 V18.3.0.
  • the network function (NF) entity e.g., NWDAF service consumer, may subscribe to analytics information such as UE radio data by sending Nnwdaf_AnalyticsSubscription_Subscribe to the NWDAF.
  • the NWDAF may perform application function (AF) discovery at step 202 to discover an appropriate AF (e.g., DCAF) from network repository function (NRF) .
  • AF application function
  • the NWDAF may send a data collection request that contains UE identifier (ID) (generic public subscription identifier (GPSI) or subscription permanent identifier (SUPI) ) and UE APP ID to the DCAF.
  • ID UE identifier
  • GPSI public subscription identifier
  • SUPI subscription permanent identifier
  • the NWDAF may send the request to the DCAF via Naf_Event_Exposure_Subscribe at step 203a.
  • step 203b may be performed, at which the NWDAF may send the request to the Network Exposure Function (NEF) via Nnef_Event_Exposure_Subscribe, and then the NEF may forward the request to the AF via Naf_Event_Exposure_Subscribe.
  • NEF Network Exposure Function
  • data collection may be performed between the AF and the UE, the AF may find the corresponding UE IP address and send the request to the UE APP and later collect the data from UE APP using the user plane PDU session connection.
  • the AF may notify the NWDAF about the collected UE APP data.
  • the AF may notify the NWDAF about the collected UE APP data via Naf_Event_Exposure_Notify at step 205a.
  • step 205b may be performed, at which the AF may send the collected UE APP data to the NEF via Naf_Event_Exposure_Notify, and then the NEF may forward the collected UE APP data to the NWDAF via Nnef_Event_Exposure_Notify.
  • EVEX event exposure
  • the NWDAF may report the collected UE radio data to DCAF via the user plane connection upon certain configuration and the DCAF will continue to report it to the consumer (NWDAF) for the upcoming AI/ML model training.
  • the UE is normally configured by the RAN node to conduct the radio data collection and in turn report the collection result to the RAN node. No collected UE radio data will be sent to the UE APP.
  • the first issue is, how does the AI/ML model training entity configure the UE for radio data collection.
  • the second issue is how does UE know to report the collected radio data to the UE APP, instead of RAN node.
  • the present disclosure proposes a solution for collecting UE radio data.
  • the UE in the case that a UE is deployed with at least one UE application (APP) , the UE may be configured by a RAN node to collect UE radio data via its UE access stratum (AS) layer and report the collected UE radio data to its UE APP layer. Then the UE may transmit the collected UE radio data to DCAF from the UE APP layer, thereby the collected UE radio data may be forwarded by the DCAF to NWDAF for AI/ML model training.
  • the collected Layer 1 (L1) UE radio data may further improve the performance of the AI/ML model.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports collection of UE radio data, e.g. UE Layer 1 (L1) radio data, in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network.
  • LTE-A LTE-advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • 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 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. 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.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 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.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 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 mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an internet-of- things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT internet-of- things
  • IoE internet-of-everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 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) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open radio access network
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a CU, a DU, a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.
  • RIC RAN intelligent controller
  • SMO service management and orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU)) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) .
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 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) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway packet data network gateway
  • UPF user plane function
  • 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 network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 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 core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 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) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • 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 subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a 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.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • 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.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • 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) .
  • 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
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • FIG. 3 illustrates a signalling procedure 300 for collecting UE radio data in accordance with aspects of the present disclosure.
  • the signalling procedure 300 involves a first network device 102-1, a second network device 102-2, a third network device 102-3, and a UE 104. Additionally, the signalling procedure 300 may further involve AMF 102-4.
  • the first network device 102-1 may be a RAN node
  • the second network device may be the NWDAF
  • the third network device 102-3 may be the DCAF.
  • the UE 104 may be determined by at least one of the first network device 102-1, a second network device 102-2, a third network device 102-3, and AMF 102-4 for example, based on a request for collecting UE radio data, which may include UE ID or other information for determining or selecting the UE 104 for collecting radio data.
  • the UE 104 may be deployed with at least one UE APP on APP layer.
  • a first network device 102-1, a third network device 102-3, and a UE 104 are illustrated in FIG. 3, the same or similar procedure may occurs between the second network device 102-2 and more first network devices, more network devices, and more UEs.
  • the second network 102 may initial a UE radio data collection procedure so as to obtain UE radio data for model training.
  • the model training request may be received from at least one consumer for AI/ML model training, for example, from at least one of OAM, RAN node, UE OTT server, and the like.
  • the model training request may include at least one of: at least one UE ID and/or UE IP address, area of interest (AOI) information, task indication information related to an AI/ML model, requested model related information, UE related information, a target address of a trained AI/ML model, and the like.
  • the task indication information may be used to indicate or distinguish different AI/ML models or different tasks.
  • the UE radio data may be collected by the UE 104 via measurement, e.g., L1-RSRP measurement, and sent to the second network device 102-2.
  • the UE radio data collection may be configured by the first network device 102-1 to the UE 104, for example, based on an indication from UE 104 or an indication from other network device such as AMF 102-4.
  • the signalling procedure 300 may involve steps 301a, 303a, and 305 to 311.
  • the signalling procedure 300 may involve steps 301b, 302b, 303b, and 305 to 311. Detailed operations of these steps will be explained in detail below.
  • the second network device 102-2 may, at steps 301a, transmit a request for collecting UE radio data to the AMF102-4.
  • the AMF 102-4 may be determined by the second network device 102-2 from a set of predetermined AMFs at least based on, for example, the UE related information or the AOI information included in the model training request, or other information.
  • the request for collecting UE radio data transmitted to the AMF 102-4 may include at least one of: an information for determining the UE, an information on the second network device, an information on the third network device, at least one APP identifier (ID) indicating at least one UE APP, a task indication information related to an AI/ML model to which the UE radio data is to be applied, and the like.
  • the AMF 102-4 may find at least one corresponding first network device 102-1, and may transmit, at step 303a, the request for collecting UE radio data to each corresponding first network device 102-1.
  • first network device 102-1 After received the request for collecting UE radio data from the AMF 102-4, the first network device 102-1 may configure the UE 104 to perform radio data collection, which will be described in detail later.
  • the first network device 102-1 may be indicated to configure the UE 104 via steps 301b to 303b, i.e., the UE radio data collection is configured by the first network device 102-1 based on an indication from UE 104,
  • the second network device 102-2 may, at steps 301b, transmit a request for collecting UE radio data to the third network device 102-3.
  • the third network device 102-3 may be determined by the second network device 102-2 from a set of predetermined third network devices based on capabilities of the predetermined third network devices for UE radio data collection.
  • only one third network device 102-3 is shown in FIG. 3, but similar procedure may be applicable to more third network devices which are not shown.
  • the request for collecting UE radio data transmitted to the third network device 102-3 may include at least one of the at least one UE ID and the task indication information in the model training request.
  • the second network device 102-2 may determine, based on the at least one UE ID included in the model training request, at least one UE IP address, at least one APP ID, and at least one protocol data unit (PDU) session ID between at least one UE APP indicated by the at least one APP ID and the third network device 102-3.
  • the at least one APP ID may include APP ID (s) of UE APP (s) deployed on the UE 104.
  • the determined at least one APP ID, the at least one UE IP address, and the at least one PDU session ID may be further included in the request for collecting UE radio data transmitted to the third network device 102-3, such that the third network device 102-3 may establish a user plane connection between an UE APP deployed on the UE 104 and the third network device 102-3 to transmit UE radio data.
  • the at least one UE IP address may be forwarded to the third network device 102-3 by being included in the request for collecting UE radio data transmitted to the third network device 102-3, without needing to be determined based on the UE ID as above.
  • the third network device 102-3 may determine at least one UE IP address, at least one APP ID, and at least one PDU session ID between at least one UE APP indicated by the at least one APP ID and the third network device based on the received at least one UE ID.
  • the third network device 102-3 may also transmit the request for collecting UE radio data to the UE 104.
  • the UE 104 may transmit the request for collecting UE radio data received from the third network device 102-3 to the first network device 102-1, to ask the first network device 102-1 to configure the UE 104 for radio data collection.
  • the request for collecting UE radio data may be transmitted from the UE AS layer of the UE 104.
  • the first network device 102-1 may configure the UE 104 to perform radio data collection.
  • the first network device 102-1 may transmit, to the UE 104, a configuration for configuring UE AS layer of the UE to perform radio data collection. Furthermore, the first network device 102-1 may also transmit, to the UE 104, an APP report indication indicating the UE 104 to report UE radio data collected by the UE AS layer of the UE 104 to a UE APP among at least one UE APP deployed on the UE 104.
  • the configuration and the APP report indication may transmitted together, e.g., the APP report indication may be included in the configuration, or they could be transmitted separately.
  • the request received by the first network device 102-1 may include a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the data report and collection configuration may be generated by the third network device 102-3, or it may be generated by the second network device 102-2 and transmitted to the third network device 102-3 via the request transmitted from the second network device 102-2, and finally obtained by the first network device 102-1 .
  • the data report and collection configuration includes at least one of: UE radio data parameters that need to be measured and collected; a format of the UE radio data and grouping standard when reporting UE radio data; reporting rules of the UE radio data; collecting duration and sampling rules of the UE radio data; information associated with a timestamp, a scenario, a corresponding configuration when collecting the UE radio data; and criteria that need to be satisfied when collecting the UE radio data.
  • the request received by the first network device 102-1 may not include the data report and collection configuration, instead, it may include a task indication information related to an AI/ML model to which the UE radio data is to be applied.
  • the first network device 102-1 may determine, based on the task indication information, a data report and collection configuration for configuring collection and reporting of the UE radio data.
  • the task indication information may include a task ID or a task type, and the task type may include at least one of UE side CSI prediction, UE side CSI compression, UE side beam prediction, and UE side positioning.
  • an APP report indication may be also received from the UE 104, to let the first network device 102-1 know that UE radio data collection to be configured is for a UE APP.
  • the APP report indication may be transmitted to the UE 104 together with the configuration for configuring UE AS layer subsequently, to let the UE know that the UE radio data should be reported to the UE APP.
  • the first network device 102-1 may determine, directly based on the received APP report indication, a data report and collection configuration for configuring collection and reporting of the UE radio data by itself.
  • the first network device 102-1 may further receive the information for determining the UE from the AMF 102-4, and determine at least one UE including the UE 104 at least based on the information for determining the UE.
  • the information for determining the UE may include at least one of: at least one UE selectin criteria; a UE identifier (ID) of the UE; and a UE list including the UE 104.
  • the first network device 102-1 may further receive, from the AMF 102-4, information on the second network device (e.g., FQDN or IP address of the second network device) , information on the third network device (e.g., FQDN or IP address of the third network device) , an APP ID indicating the UE APP, and the task indication information related to an AI/ML model to which the collected UE radio data is to be applied, and transmit the information on the second network device, the information on the third network device, the APP ID, and the task indication information to the UE 104.
  • information on the second network device e.g., FQDN or IP address of the second network device
  • information on the third network device e.g., FQDN or IP address of the third network device
  • an APP ID indicating the UE APP e.g., an APP ID indicating the UE APP
  • the task indication information related to an AI/ML model to which the collected UE radio data is to be applied
  • a path for delivering the UE radio data may be determined, for example, the collected UE radio data may be obtained by the third network device 102-3 from the UE APP and transmitted by the third network device102-3 to the second network device 102-2 based on the information on the second network device and the information on the third network device, and is used by the second network device102-2 to perform AI/ML model training.
  • the request for collecting UE radio data and the APP report indication received by the UE 104 may include an identification information associated with the UE APP, such as APP ID, PDU session ID, and/or other information that may be used to identify a UE APP.
  • the UE 104 may associate the collected UE radio data with respective UE APPs and thereby the second network device 102-2 may identify UE radio data corresponding to different UE APP based on the identification information for subsequent usage.
  • the UE 104 may perform UE radio data collection based on the configuration at the UE AS layer, and at step 309, the UE 104 may transmit the collected UE radio data to the third network device 102-3. In some example embodiments, the UE 104 may transmit the collected UE radio data to the UE APP from the UE AS layer, and then transmit the collected UE radio data from the UE APP to the third network device 102-3.
  • the UE 104 may further determine whether there is available UE radio data (previously stored) for the request for collecting UE radio data, and transmit, to the third network device 102-3, the available radio data from the UE APP
  • the third network device 102-3 may transmit the UE radio data to the second network device 102-2.
  • the collected UE radio data may be transmitted to the second network device 102-2 together with the task indication information, such that the second network device 102-2 know which AI/ML model or which data collection task it relates to.
  • the second network device 102-2 may perform model training on the AI/ML model by using the collected UE radio data, and transmit, to the at least one consumer, the trained AI/ML model based on the target address in the model training request.
  • FIG. 4 illustrates an example signalling procedure for collecting UE radio data in accordance with aspects of the present disclosure.
  • the NWDAF as the AI/ML model training entity in the core network (CN) , may receive a model training request from consumers for UE side AI/ML model training.
  • the consumers may be OAM, UE side OTT server and/or RAN node.
  • the model training request may include following elements: 1) UE ID or UE IP address; 2) AOI information; 3) a task ID; 4) requested model related information, such as a use case the AI/ML model will relate to, for example, the UE CSI prediction, the target problem the model is trying to solve; 5) UE related information, such as UE vendor info, UE chipset info, UE type information; and 6) the target address (IP address/fully qualified domain name (FQDN) to send the trained model to.
  • the target address IP address/fully qualified domain name (FQDN) to send the trained model to.
  • the well-trained AI/ML model will be delivered from NWDAF to the consumers via certain ways.
  • NWDAF may translate the model training request to find out what kind of UE radio data is needed for model training given the use case, e.g., UE side CSI prediction, UE side spatial or time domain beam prediction, etc.
  • the UE radio data that needs to be collected may mainly have: 1) consecutive CSIs (historical CSIs+future CSIs) where the type of CSIs includes raw channel matrices, or precoding marix indicators (PMIs) , or eigen vectors, etc, and 2) assistance information for model management e.g., site/scenario/dataset related information.
  • the AIML model training entity may generate and provide its own Data Collection Configuration (e.g., the data report and collection configuration) for the sake of its own purpose, or directly sends a UE radio data collection request to DCAF and let DCAF generate the data report and collection configuration. Then, the NWDAF may check the analytics data repository function (ADRF) and OAM to see whether the requested data is available or already stored. If yes, NWDAF will retrieve the data from these entities directly. If not, the NWDAF may interact with DCAF to initiate the data collection procedure.
  • NWDAF Data Collection Configuration
  • OAM analytics data repository function
  • the NWDAF may discover at least one appropriate DCAF that supports UE radio data collection from NRF.
  • the DCAF may have already registered itself with the UE radio data collection as one of the supported capabilities at the NRF.
  • the NWDAF may obtain the DCAF instance information from the NRF, i.e., FQDN or IP address.
  • the NWDAF may send the UE radio data (AS Layer) collection request (i.e., the request for collecting UE radio data as mentioned above) to the selected DCAF via Naf_Event_Exposure_Subscribe, together with (e.g., including) UE ID (SUPI or GPSI) it received when receiving the model training request from the consumers, Event ID, UE APP ID and task ID.
  • the NWDAF may find the UE IP address by interacting with session management function (SMF) and unified data management (UDM) based on the received UE ID. Then the UE IP address and PDU session ID may be sent from the NWDAF to the DCAF.
  • SMF session management function
  • UDM unified data management
  • step 403 for the DCAF to correlate the UE radio data collection request and UE IP address and PDU session is not needed.
  • the NWDAF may receive the UE IP address from the consumer and may forward it to the DCAF when sending the UE radio data collection request.
  • step 403 for DCAF to correlate the UE radio data collection request and UE IP address and PDU session is not needed and NWDAF doesn’ t need to find the corresponding UE IP address using UE ID as well.
  • the NWDAF may need to collect radio data from multiple UEs for the AI/ML model training and therefore the multiple UE IDs may be provided to the DCAF.
  • the DCAF may interact with UDM and SMF to determine the corresponding UE IP address, the UE APP ID and the UP PDU session ID between the DCAF and the UE APP.
  • a user plane connection between the DCAF and a UE APP for data collection may be identified.
  • the detailed procedure to identify the user plane connection is to relate the UE IP address, UE APP ID and DCAF IP address together with the user plane connection. There might be 2 possible ways to do so.
  • the first way is that, since the UE APP is deployed by an application service provider (ASP) about the DCAF for the UE Application to connect to (e.g.
  • ASP application service provider
  • UE may establish a user plane connection with DCAF.
  • the UE Application provides the Application ID configured in the UE Application to the AF via the user plane connection.
  • DCAF may bind the APP ID, UE IP address and user plane connection together.
  • the DCAF may obtain the UE IP address either by itself or received from the NWDAF, and combines with the UE ID and UE APP ID received from the NWDAF, to bind the APP ID, UE IP address and user plane connection together.
  • the DCAF may send the UE radio data collection request that includes the data report and collection configuration set (either received from NWDAF or derived by itself) to the target UE APP using the user plane connection, together with (e.g. including) the task ID and DCAF info (e.g., IP address or FQDN) .
  • the UE APP may forward the UE radio data collection request to the UE AS layer, together with the APP ID (e.g. included in the UE radio data collection request) .
  • the data report and collection configuration may be generated by NWDAF, or by DCAF, and may include the following elements: (1) the UE radio data (parameters) that needs to be measured and collected, for example, L1-RSRP measurement, Top-k beam indicator, Ground truth location coordination, CSIs include raw channel matrices, or PMIs, or eigen vectors, etc; (2) the format of the data, the grouping standard when reporting the data (based on feature or based on UE ID) ; (3) the reporting rules of the data, i.e., event report, periodic report; (4) the collecting duration and the sampling rules of the data; (5) some other associated information, for example, the timestamp, scenario, the corresponding configuration when collecting the data, etc; and (6) the certain criteria that need to be satisfied when collecting the data, for example, the frequency, the area information (tracking area identity (TAI) , Cell ID) , the synchronization signal block (SSB) information, the state of the UE, etc.
  • the UE radio data parameters
  • the data report and collection configuration could also be in the form of task type.
  • the RAN node receives the task type, e.g., UE side CSI prediction, the RAN node will know what the corresponding data report and collection configuration is. A detailed description of how the UE radio data collection request is sent is depicted in FIG. 5.
  • FIG. 5 illustrates an example procedure for sending UE radio data collection request from DCAF to UE AS Layer in accordance with aspects of the present disclosure.
  • RX1, RX2, and R1 to R8 represent connection between respective entities in FIG. 5, and connections R1 to R8 have been explained in 3GPP in TS 23.288 and TS 26.531.
  • the data collection from the UE APP to the DCAF in some example embodiments of present disclosure may be either direct (R2) or indirect (R8+R3) . Therefore, when DCAF sends the UE radio data collection request to the UE AS Layer, there can be two possible ways. One is through the Direct Data Collection Client, namely via the connection RX1. The other way is through the Indirect Data Collection Client, which is R3+R8 and then the connection RX2 from UE Application to UE AS Layer.
  • UE may determine whether the data that needs to be collected is already stored. If not, goes to step 406. Otherwise, the stored data may be transmitted to the DCAF, step 406 may be performed if necessary.
  • UE reversely asks the RAN node to configure the UE 104 for radio data collection.
  • the UE may notify the RAN node that the collected data will be reported to the UE APP based on the original UE radio data collection request received from the UE APP (i.e., UE AS layer originally receives the UE radio data collection request from its APP) .
  • RAN node will know what kind of data configuration the UE needs. Therefore, UE may provide the APP report indicator and/or some ID to the RAN node to let RAN node know that this data needs to be sent back to which APP.
  • the some ID may be APP ID, PDU session ID, PDU session ID+QFI as long as it can assist to find the corresponding APP to report the collected UE radio data, and it may be optional, for example, in the case that there is only one UE APP deployed on the UE, the some ID may be not needed.
  • the UE may directly provide the data report and collection configuration to the RAN node, either in the form of detailed information depicted above, or a task ID, or the task type.
  • the relationship between different data report and collections configuration and different task IDs/task types may be predetermined or preconfigured in the RAN node or transmitted to the RAN node in advance.
  • the RAN node may accordingly know the data configuration that needs and may configure the UE based on that.
  • the UE combines above two ways to provide both information to the RAN node for further configuration.
  • the RAN node may configure the UE AS Layer via RRC signalling to perform the radio data collection. Furthermore, for example, the RAN node may configure the UE with a dedicated radio bearer that has a low priority for its data report. When the DCAF or NWDAF indicates that the collected UE radio data is enough, the RAN node may accordingly release the radio bearer and terminate the configuration for UE radio data collection.
  • an indication e.g., the APP report indication
  • the indication may either be an indication, or a task type that distinguish that this data needs to be transmitted to the UE APP.
  • the UE AS layer conducts the radio data measurement, collection, and reports the UE radio data to the UE APP either based on the request from the UE APP or based on the indication from RAN node.
  • the UE APP may transmit the UE radio data to the DCAF via user plane connection, together with UE APP ID (optional, in the case that some other UE APP may use the same user plane connection) .
  • the user plane connection may be the existing one found based on the DCAF Info, or established upon a data transmission request.
  • the DCAF may notify the NWDAF about the UE radio data, together with UE APP ID, UE IP address, Task ID, Event ID and UE ID via Naf_Event_Exposure_Notify.
  • the NWDAF may deliver the trained AI/ML model using the collected UE radio data to corresponding consumers via certain ways.
  • the DCAF may determine whether the requested UE radio parameters are allowed to be collected or not. Also, when the model training request updates, it may lead to the update of the UE radio data collection configuration.
  • FIG. 6 illustrates another example signalling procedure for collecting UE radio data in accordance with aspects of the present disclosure.
  • the UE radio data collection request may be sent from the NWDAF to the RAN node (finally to UE) via control plane in 5GC.
  • the RAN node may receive the UE radio data collection request from AMF and configure the UE AS Layer to do the radio data measurement and collection.
  • the NWDAF as the AI/ML model training entity in the core network (CN) , may receive the model training request from consumers for UE side AI/ML model training.
  • the consumers may be OAM, UE side OTT server and/or RAN node.
  • the well-trained AI/ML model will be delivered from NWDAF to the consumers via certain ways.
  • the model training request may include the following elements: 1) UE ID or UE IP address; 2) AOI information; 3) task ID;4) requested model related information, such as the use case the model will relate to, for example, the UE CSI prediction, the target problem the model is trying to solve; 5) UE related information, such as UE vendor info, UE chipset info, UE type info; and 6) The target address (IP address/FQDN) to send the trained model to.
  • the target address IP address/FQDN
  • NWDAF may translate the model training request to determine what kind of UE radio data is needed given the use case, e.g., UE side CSI prediction, UE side spatial or time domain beam prediction, etc. Then, the NWDAF may check the ADRF and OAM to see whether the requested data is available or already stored. If yes, the NWDAF will retrieve the data from these entities directly. If not, the NWDAF will initiate the data collection procedure. Then, NWDAF may discover an appropriate DCAF for UE radio data collection from NRF. The DCAF may already registered itself with the UE radio data collection as one of the supported capabilities at the NRF. The NWDAF may get the DCAF instance from the NRF, i.e., FQDN or IP address. Moreover, the NWDAF may find the AMF from the NRF using the AOI information included in the request.
  • the DCAF may already registered itself with the UE radio data collection as one of the supported capabilities at the NRF.
  • the NWDAF may get the DCAF instance from the NRF,
  • the NWDAF may send the UE radio data collection request that includes the data report and collection configuration to the serving AMF that is discovered from the NRF using AOI information and other UE related information, together with the NWDAF Info (e.g., FQDN or IP address) , DCAF Info (e.g., FQDN or IP Address) , task ID, APP ID and other UE selection criteria received from the UE radio data collection request (e.g., they may be included in the UE radio data collection request) .
  • NWDAF Info e.g., FQDN or IP address
  • DCAF Info e.g., FQDN or IP Address
  • task ID e.g., APP ID
  • UE selection criteria e.g., they may be included in the UE radio data collection request
  • steps 603 to 605 may be optional.
  • the other UE selection criteria may be area of interest (target area, tracking area, location of UE) , cell, frequency, UE type (e.g., internet of things (IoT) device) , UE capability (e.g., multi-input multi-output (MIMO) capable) , UE vender info, UE chipset info, etc.
  • the NWDAF Info may be used by the DCAF to report the collected UE radio data.
  • the DCAF Info may be used by the UE APP as server IP address to establish the PDU session (user plane connection) to transmit the collected data if needed.
  • the AMF After receiving the UE radio data collection request from the NWDAF, the AMF will proceed using the following optional steps:
  • the AMF may determine appropriate UE (s) for radio data collection, based on the UE radio data collection request, other criteria provided by the NWDAF, and the UE capability stored at AMF. Based on the selected UE (s) , the AMF may find at least one corresponding serving RAN node. Then at step 604a, the AMF may forward the UE radio data collection request to the RAN node, together with (e.g., including) the selected UE ID.
  • steps 603a and 604a steps 603b and 604b may be performed.
  • the AMF may firstly determine an initial UE lists based on the received information from NWDAF, find at least one corresponding RAN node. Then at step 604b, the AMF may send the UE radio data collection request, other UE selection criteria and the initial UE list to the RAN node and let the RAN node decide final UE (s) for radio data collection.
  • steps 603a and 604a may be performed instead of steps 603a and 604a, and steps 603b and 604.
  • steps 603c may be performed.
  • the AMF may directly forward the UE radio data collection request, UE selection criteria to the RAN node based on the AOI information and ask the RAN node to select the UE (s) .
  • the NWDAF Info, DCAF Info, APP ID and task ID may also be sent to the RAN node from AMF (e.g., they may be included in the UE radio data collection request) .
  • the AMF may translate the UE ID received from NWDAF (GPSI/SUPI) into AMF UE NGAP ID and RAN UE NGAP ID so that the RAN node can understand when it receives the selected UE or the initial UE list. Moreover, if the signalling connection between the AMF and RAN is per UE signalling, UE list or ID doesn’ t need to be included since the UE ID is already mandatory included. If it is a common signalling, the UE ID or list is needed and included.
  • NWDAF GPSI/SUPI
  • the RAN node may determine the appropriate UE(s) .
  • the RAN node may receive the initial UE list, the UE radio data collection request and other criteria information from the AMF. Then, the RAN node will narrow down to find the final UE (s) for data collection.
  • the RAN node may refer to the detailed physical layer related information in the UE selection criteria, e.g., measurement on the specific frequency and find the appropriate UE (s) by comparing with the stored UE capability at the RAN node.
  • the RAN node may receive the UE radio data collection request, other UE selection criteria information from AMF and find the appropriate UE (s) by itself.
  • the RAN node may send the UE radio data (L1) collection request to the UE via RRC signalling to configure the radio data collection.
  • an explicit indication e.g., the APP report indication as above
  • NWDAF Info, DCAF Info and task ID may be sent from the RAN node to the UE together (e.g., included in the UE radio data collection request) .
  • the UE AS layer may perform radio data measurements and collection according to the configuration received from the RAN node and transmits the UE radio data, the NWDAF Info, DCAF Info and the task ID to its UE APP based on the APP ID received from the RAN node.
  • the UE APP may transmit the collected UE radio data, together with the NWDAF Info and task ID to the DCAF based on the DCAF Info, either uses the existing user plane connection (identified by using the DCAF Info to see whether there is an existing connection between its APP and the DCAF) or establishes a new user plane session.
  • the DCAF may forward the UE radio data to the NWDAF either based on the subscription from NWDAF, or based on the NWDAF Info and the task ID to inform the NWDAF about what the UE radio data is associated with.
  • the NWDAF may deliver the trained AI/ML model using the collected UE data to corresponding consumers via certain ways.
  • the UE may inform the RAN node about the data collection result, e.g., whether the data collection can be conducted or not, whether the data collection is finished or not, together with the task ID and UE ID, via uplink (UL) radio resource control (RRC) message or UL media access control (MAC) Control Element (CE) .
  • RRC radio resource control
  • MAC media access control
  • NWDAF is illustrated as a data collection entity
  • the data collection entity may be OTT server (NW side) .
  • OTT server initiates the UE radio data collection procedure (by itself or upon request) , it will either go through the same way via DCAF to configure and collect the data, or through AF, NEF (optional) and then via AMF and RAN node to configure the UE radio data collection.
  • FIG. 7 illustrates an example of a device 700 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the device 700 may be an example of the first network device 102-1 (e.g., RAN node) as described herein.
  • the device 700 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I/O controller 708. 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) .
  • the processor 702, the memory 704, the transceiver 706, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field- programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
  • the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein.
  • the processor 702 may be configured to operable to support a means for, in response to a request for collecting user equipment (UE) radio data, transmitting, via the transceiver and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) ; and means for transmitting, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • the processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 702 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 702.
  • the processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
  • the memory 704 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 700 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 code may not be directly executable by the processor 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 704 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 708 may manage input and output signals for the device 700.
  • the I/O controller 708 may also manage peripherals not integrated into the device M02.
  • the I/O controller 708 may represent a physical connection or port to an external peripheral.
  • the I/O controller 708 may utilize an operating system such as or another known operating system.
  • the I/O controller 708 may be implemented as part of a processor, such as the processor 706.
  • a user may interact with the device 700 via the I/O controller 708 or via hardware components controlled by the I/O controller 708.
  • the device 700 may include a single antenna 410. However, in some other implementations, the device 700 may have more than one antenna 410 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 706 may communicate bi-directionally, via the one or more antennas 410, wired, or wireless links as described herein.
  • the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 410 for transmission, and to demodulate packets received from the one or more antennas 410.
  • the transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain 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 transmit chain 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 transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain 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 receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 8 illustrates an example of a device 800 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the device 800 may be an example of a second network device 102-2 (e.g., NWDAF) as described herein.
  • NWDAF wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 800 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 802, a memory 804, a transceiver 806, and, optionally, an I/O controller 808. 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) .
  • interfaces e.g., buses
  • the processor 802, the memory 804, the transceiver 806, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 802 and the memory 804 coupled with the processor 802 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804) .
  • the processor 802 may support wireless communication at the device 800 in accordance with examples as disclosed herein.
  • the processor 802 may be configured to operable to support a means for transmitting, via a transceiver and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request; and means for receiving, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • AMF access and mobility management function
  • the processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 802 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 802.
  • the processor 802 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 804) to cause the device 800 to perform various functions of the present disclosure.
  • the memory 804 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 802 cause the device 800 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 code may not be directly executable by the processor 802 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 804 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 808 may manage input and output signals for the device 800.
  • the I/O controller 808 may also manage peripherals not integrated into the device M02.
  • the I/O controller 808 may represent a physical connection or port to an external peripheral.
  • the I/O controller 808 may utilize an operating system such as or another known operating system.
  • the I/O controller 808 may be implemented as part of a processor, such as the processor 806.
  • a user may interact with the device 800 via the I/O controller 808 or via hardware components controlled by the I/O controller 808.
  • the device 800 may include a single antenna 510. However, in some other implementations, the device 800 may have more than one antenna 510 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 806 may communicate bi-directionally, via the one or more antennas 510, wired, or wireless links as described herein.
  • the transceiver 806 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 806 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 510 for transmission, and to demodulate packets received from the one or more antennas 510.
  • the transceiver 806 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain 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 transmit chain 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 transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 510 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain 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 receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 9 illustrates an example of a device 900 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the device 900 may be an example of a third network device 102-3 (e.g., DCAF) as described herein.
  • the device 900 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 900 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 902, a memory 904, a transceiver 906, and, optionally, an I/O controller 908. 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) .
  • the processor 902, the memory 904, the transceiver 906, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904) .
  • the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein.
  • the processor 902 may be configured to be operable to support a means for receiving, via the transceiver and from a second network device, a first request for collecting user equipment (UE) radio data; means for transmitting, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request; and means for receiving, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • AS UE access stratum
  • the processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 902 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 902.
  • the processor 902 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 904) to cause the device 900 to perform various functions of the present disclosure.
  • the memory 904 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 902 cause the device 900 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 code may not be directly executable by the processor 902 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 904 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 908 may manage input and output signals for the device 900.
  • the I/O controller 908 may also manage peripherals not integrated into the device M02.
  • the I/O controller 908 may represent a physical connection or port to an external peripheral.
  • the I/O controller 908 may utilize an operating system such as or another known operating system.
  • the I/O controller 908 may be implemented as part of a processor, such as the processor 906.
  • a user may interact with the device 900 via the I/O controller 908 or via hardware components controlled by the I/O controller 908.
  • the device 900 may include a single antenna 510. However, in some other implementations, the device 900 may have more than one antenna 510 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 906 may communicate bi-directionally, via the one or more antennas 510, wired, or wireless links as described herein.
  • the transceiver 906 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 906 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 510 for transmission, and to demodulate packets received from the one or more antennas 510.
  • the transceiver 906 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain 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 transmit chain 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 transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 510 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain 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 receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 10 illustrates an example of a device 1000 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the device 1000 may be an example of a UE 104 as described herein.
  • the device 1000 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 1000 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1002, a memory 1004, a transceiver 1006, and, optionally, an I/O controller 1008. 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) .
  • interfaces e.g., buses
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004) .
  • the processor 1002 may support wireless communication at the device 1000 in accordance with examples as disclosed herein.
  • the processor 1002 may be configured to operable to support a means for receiving, via a transceiver and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE; means for performing UE radio data collection based on the configuration at the UE AS layer; and means for transmitting the collected UE radio data to the UE APP from the UE AS layer.
  • AS UE access stratum
  • the processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1002 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1002.
  • the processor 1002 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1004) to cause the device 1000 to perform various functions of the present disclosure.
  • the memory 1004 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1002 cause the device 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 code may not be directly executable by the processor 1002 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1004 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 1008 may manage input and output signals for the device 1000.
  • the I/O controller 1008 may also manage peripherals not integrated into the device M02.
  • the I/O controller 1008 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1008 may utilize an operating system such as or another known operating system.
  • the I/O controller 1008 may be implemented as part of a processor, such as the processor 1006.
  • a user may interact with the device 1000 via the I/O controller 1008 or via hardware components controlled by the I/O controller 1008.
  • the device 1000 may include a single antenna 510. However, in some other implementations, the device 1000 may have more than one antenna 510 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1006 may communicate bi-directionally, via the one or more antennas 510, wired, or wireless links as described herein.
  • the transceiver 1006 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1006 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 510 for transmission, and to demodulate packets received from the one or more antennas 510.
  • the transceiver 1006 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain 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 transmit chain 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 transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 510 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain 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 receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 11 illustrates an example of a processor 1100 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein.
  • the processor 1100 may optionally include at least one memory 1104, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1100.
  • ALUs arithmetic-logic units
  • 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) .
  • the processor 1100 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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 1100) 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1102 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 1100 to cause the processor 1100 to support various operations of a base station in accordance with examples as described herein.
  • the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction (s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein.
  • the controller 1102 may be configured to track memory address of instructions associated with the memory 1104.
  • the controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein.
  • the controller 1102 may be configured to manage flow of data within the processor 1100.
  • the controller 1102 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1100.
  • ALUs arithmetic logic units
  • the memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100) . In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100) .
  • caches e.g., memory local to or included in the processor 1100 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100) . In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100) .
  • the memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 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 1102 and/or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions.
  • the processor 1100 and/or the controller 1102 may be coupled with or to the memory 1104, and the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein.
  • the processor 1100 may include multiple processors and the memory 1104 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.
  • the one or more ALUs 1100 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1100 may reside within or on a processor chipset (e.g., the processor 1100) .
  • the one or more ALUs 1100 may reside external to the processor chipset (e.g., the processor 1100) .
  • One or more ALUs 1100 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1100 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1100 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 1100 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1100 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1100 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1100 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1100 may be configured to or operable to support a means for, in response to a request for collecting user equipment (UE) radio data, transmitting, via the transceiver and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) ; and means for transmitting, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • FIG. 12 illustrates an example of a processor 1200 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the processor 1200 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1200 may include a controller 1202 configured to perform various operations in accordance with examples as described herein.
  • the processor 1200 may optionally include at least one memory 1204, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1200 may optionally include one or more arithmetic-logic units (ALUs) 1200.
  • ALUs arithmetic-logic units
  • 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) .
  • the processor 1200 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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 1200) 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1202 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 1200 to cause the processor 1200 to support various operations of a UE in accordance with examples as described herein.
  • the controller 1202 may operate as a control unit of the processor 1200, generating control signals that manage the operation of various components of the processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1204 and determine subsequent instruction (s) to be executed to cause the processor 1200 to support various operations in accordance with examples as described herein.
  • the controller 1202 may be configured to track memory address of instructions associated with the memory 1204.
  • the controller 1202 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1202 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein.
  • the controller 1202 may be configured to manage flow of data within the processor 1200.
  • the controller 1202 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1200.
  • ALUs arithmetic logic units
  • the memory 1204 may include one or more caches (e.g., memory local to or included in the processor 1200 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1204 may reside within or on a processor chipset (e.g., local to the processor 1200) . In some other implementations, the memory 1204 may reside external to the processor chipset (e.g., remote to the processor 1200) .
  • caches e.g., memory local to or included in the processor 1200 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1204 may reside within or on a processor chipset (e.g., local to the processor 1200) . In some other implementations, the memory 1204 may reside external to the processor chipset (e.g., remote to the processor 1200) .
  • the memory 1204 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1200, cause the processor 1200 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 1202 and/or the processor 1200 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the processor 1200 to perform various functions.
  • the processor 1200 and/or the controller 1202 may be coupled with or to the memory 1204, and the processor 1200, the controller 1202, and the memory 1204 may be configured to perform various functions described herein.
  • the processor 1200 may include multiple processors and the memory 1204 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.
  • the one or more ALUs 1200 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1200 may reside within or on a processor chipset (e.g., the processor 1200) .
  • the one or more ALUs 1200 may reside external to the processor chipset (e.g., the processor 1200) .
  • One or more ALUs 1200 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1200 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1200 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 1200 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1200 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1200 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1200 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1200 may be configured to or operable to support means for transmitting, via a transceiver and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request; and means for receiving, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • AMF access and mobility management function
  • FIG. 13 illustrates an example of a processor 1300 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the processor 1300 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1300 may include a controller 1302 configured to perform various operations in accordance with examples as described herein.
  • the processor 1300 may optionally include at least one memory 1304, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1300 may optionally include one or more arithmetic-logic units (ALUs) 1300.
  • ALUs arithmetic-logic units
  • 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) .
  • the processor 1300 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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 1300) 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1302 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 1300 to cause the processor 1300 to support various operations of a UE in accordance with examples as described herein.
  • the controller 1302 may operate as a control unit of the processor 1300, generating control signals that manage the operation of various components of the processor 1300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1304 and determine subsequent instruction (s) to be executed to cause the processor 1300 to support various operations in accordance with examples as described herein.
  • the controller 1302 may be configured to track memory address of instructions associated with the memory 1304.
  • the controller 1302 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1300 to cause the processor 1300 to support various operations in accordance with examples as described herein.
  • the controller 1302 may be configured to manage flow of data within the processor 1300.
  • the controller 1302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1300.
  • ALUs arithmetic logic units
  • the memory 1304 may include one or more caches (e.g., memory local to or included in the processor 1300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1304 may reside within or on a processor chipset (e.g., local to the processor 1300) .
  • the memory 1304 may reside external to the processor chipset (e.g., remote to the processor 1300) .
  • the memory 1304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1300, cause the processor 1300 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 1302 and/or the processor 1300 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the processor 1300 to perform various functions.
  • the processor 1300 and/or the controller 1302 may be coupled with or to the memory 1304, and the processor 1300, the controller 1302, and the memory 1304 may be configured to perform various functions described herein.
  • the processor 1300 may include multiple processors and the memory 1304 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.
  • the one or more ALUs 1300 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1300 may reside within or on a processor chipset (e.g., the processor 1300) .
  • the one or more ALUs 1300 may reside external to the processor chipset (e.g., the processor 1300) .
  • One or more ALUs 1300 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1300 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1300 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 1300 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1300 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1300 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1300 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1300 may be configured to or operable to support means for receiving, via the transceiver and from a second network device, a first request for collecting user equipment (UE) radio data; means for transmitting, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request; and means for receiving, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • UE user equipment
  • FIG. 14 illustrates an example of a processor 1400 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the processor 1400 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1400 may include a controller 1402 configured to perform various operations in accordance with examples as described herein.
  • the processor 1400 may optionally include at least one memory 1404, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1400 may optionally include one or more arithmetic-logic units (ALUs) 1400.
  • ALUs arithmetic-logic units
  • the processor 1400 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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 1400) 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1402 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 1400 to cause the processor 1400 to support various operations of a UE in accordance with examples as described herein.
  • the controller 1402 may operate as a control unit of the processor 1400, generating control signals that manage the operation of various components of the processor 1400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1404 and determine subsequent instruction (s) to be executed to cause the processor 1400 to support various operations in accordance with examples as described herein.
  • the controller 1402 may be configured to track memory address of instructions associated with the memory 1404.
  • the controller 1402 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1400 to cause the processor 1400 to support various operations in accordance with examples as described herein.
  • the controller 1402 may be configured to manage flow of data within the processor 1400.
  • the controller 1402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1400.
  • ALUs arithmetic logic units
  • the memory 1404 may include one or more caches (e.g., memory local to or included in the processor 1400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1404 may reside within or on a processor chipset (e.g., local to the processor 1400) . In some other implementations, the memory 1404 may reside external to the processor chipset (e.g., remote to the processor 1400) .
  • caches e.g., memory local to or included in the processor 1400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1404 may reside within or on a processor chipset (e.g., local to the processor 1400) . In some other implementations, the memory 1404 may reside external to the processor chipset (e.g., remote to the processor 1400) .
  • the memory 1404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1400, cause the processor 1400 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 1402 and/or the processor 1400 may be configured to execute computer-readable instructions stored in the memory 1404 to cause the processor 1400 to perform various functions.
  • the processor 1400 and/or the controller 1402 may be coupled with or to the memory 1404, and the processor 1400, the controller 1402, and the memory 1404 may be configured to perform various functions described herein.
  • the processor 1400 may include multiple processors and the memory 1404 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.
  • the one or more ALUs 1400 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1400 may reside within or on a processor chipset (e.g., the processor 1400) .
  • the one or more ALUs 1400 may reside external to the processor chipset (e.g., the processor 1400) .
  • One or more ALUs 1400 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1400 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1400 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 1400 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1400 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1400 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1400 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1400 may be configured to or operable to support means for receiving, via a transceiver and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE; means for performing UE radio data collection based on the configuration at the UE AS layer; and means for transmitting the collected UE radio data to the UE APP from the UE AS layer.
  • AS UE access stratum
  • FIG. 15 illustrates a flowchart of a method 1500 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a device or its components as described herein.
  • the operations of the method 1500 may be performed by the first network device (e.g., RAN node) as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include, in response to a request for collecting user equipment (UE) radio data, transmitting, via the transceiver and to a UE, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection, wherein the UE is deployed with at least one UE application (APP) .
  • UE user equipment
  • AS UE access stratum
  • APP UE application
  • the method may include transmitting, via the transceiver and to the UE, an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among the at least one UE APP.
  • 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 device as described with reference to FIG. 1.
  • FIG. 16 illustrates a flowchart of a method 1600 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a device or its components as described herein.
  • the operations of the method 1600 may be performed by the second network device (e.g., NWDAF) as described herein.
  • NWDAF the second network device
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, via a transceiver and to a third network device or access and mobility management function (AMF) , a request for collecting user equipment (UE) radio data in response to reception of a model training request.
  • AMF access and mobility management function
  • the operations of 1605 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1605 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving, via the transceiver and from the third network device, UE radio data collected by a UE, wherein the UE is determined at least based on the request for collecting UE radio data, wherein the collected UE radio data is obtained by the third network device from a UE application (APP) deployed on the UE.
  • APP UE application
  • the operations of 1610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1610 may be performed by a device as described with reference to FIG. 1.
  • FIG. 17 illustrates a flowchart of a method 1700 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a device or its components as described herein.
  • the operations of the method 1700 may be performed by the third network device (e.g., DCAF) as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, via the transceiver and from a second network device, a first request for collecting user equipment (UE) radio data.
  • UE user equipment
  • the operations of 1705 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1705 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting, via the transceiver and to a UE, a second request for collecting UE radio data determined based on the first request.
  • the operations of 1710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1710 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving, via the transceiver and from the UE, radio data collected by the UE APP from UE access stratum (AS) layer of the UE.
  • the operations of 1715 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1715 may be performed by a device as described with reference to FIG. 1.
  • FIG. 18 illustrates a flowchart of a method 1800 that supports collection of UE radio data in accordance with aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a device or its components as described herein.
  • the operations of the method 1800 may be performed by the UE 104 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, via a transceiver and from a first network device, a configuration for configuring UE access stratum (AS) layer of the UE to perform radio data collection and an APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE.
  • AS UE access stratum
  • APP report indication indicating the UE to report UE radio data collected by the UE AS layer of the UE to a UE APP among at least one UE application deployed on the UE.
  • the method may include performing UE radio data collection based on the configuration at the UE AS layer.
  • the operations of 1810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1810 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting the collected UE radio data to the UE APP from the UE AS layer.
  • the operations of 1815 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1815 may be performed by a device as described with reference to FIG. 1.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • 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.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • 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.
  • a list of items 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) .
  • the phrase “based on” shall not be construed 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.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente invention concernent des équipements utilisateurs, des stations de base, des processeurs et des procédés de collecte de données radio d'UE. Selon un aspect, en réponse à une demande de collecte de données radio d'équipement utilisateur (UE), un premier dispositif de réseau transmet une configuration pour configurer une couche de strate d'accès (AS) d'UE d'un UE pour effectuer une collecte de données radio à l'UE, et transmet, à l'UE, une indication de rapport d'APP indiquant l'UE pour rapporter des données radio d'UE collectées par la couche AS d'UE à une APP UE parmi au moins une APP UE déployée sur l'UE.
PCT/CN2023/142860 2023-12-28 2023-12-28 Collecte de données radio d'ue Pending WO2024222021A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/142860 WO2024222021A1 (fr) 2023-12-28 2023-12-28 Collecte de données radio d'ue

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/142860 WO2024222021A1 (fr) 2023-12-28 2023-12-28 Collecte de données radio d'ue

Publications (1)

Publication Number Publication Date
WO2024222021A1 true WO2024222021A1 (fr) 2024-10-31

Family

ID=93255489

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/142860 Pending WO2024222021A1 (fr) 2023-12-28 2023-12-28 Collecte de données radio d'ue

Country Status (1)

Country Link
WO (1) WO2024222021A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141834A1 (fr) * 2022-01-26 2023-08-03 Oppo广东移动通信有限公司 Procédé et appareil de surveillance de performance de modèle, dispositif et support
WO2023150996A1 (fr) * 2022-02-11 2023-08-17 Qualcomm Incorporated Informations assistées par réseau
WO2023192299A1 (fr) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Procédés, appareil et systèmes pour fournir des informations à une wtru par l'intermédiaire d'un plan de commande ou d'un plan d'utilisateur
WO2023201733A1 (fr) * 2022-04-22 2023-10-26 Oppo广东移动通信有限公司 Procédé et dispositif de communication sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141834A1 (fr) * 2022-01-26 2023-08-03 Oppo广东移动通信有限公司 Procédé et appareil de surveillance de performance de modèle, dispositif et support
WO2023150996A1 (fr) * 2022-02-11 2023-08-17 Qualcomm Incorporated Informations assistées par réseau
WO2023192299A1 (fr) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Procédés, appareil et systèmes pour fournir des informations à une wtru par l'intermédiaire d'un plan de commande ou d'un plan d'utilisateur
WO2023201733A1 (fr) * 2022-04-22 2023-10-26 Oppo广东移动通信有限公司 Procédé et dispositif de communication sans fil

Similar Documents

Publication Publication Date Title
JP2022122939A (ja) Ｎｅｗ ｒａｄｉｏのためのｃｓｉフィードバック設計
WO2024187797A1 (fr) Dispositifs et procédés de collecte de données
WO2024207850A1 (fr) Collecte de données pour apprentissage ou surveillance de modèle
WO2024156270A1 (fr) Synchronisation pour un dispositif iot ambiant
WO2024093447A1 (fr) Procédure de préparation pour ltm
WO2024222021A1 (fr) Collecte de données radio d'ue
WO2024213187A1 (fr) Indication de condition supplémentaire côté réseau
WO2025097820A1 (fr) Compte-rendu de mesures dans un message de couche 3
WO2024119964A1 (fr) Collecte de mesures pour apprentissage de modèle
WO2024198452A1 (fr) Établissement de rapport de csi
WO2024183322A1 (fr) Compression de csi
WO2024093275A1 (fr) Groupe d'états indicateurs de configuration de transmission
WO2024183344A1 (fr) Configuration pour signal de référence d'informations d'état de canal
WO2024169259A1 (fr) Prédiction d'informations d'état de canal
WO2024109163A1 (fr) Surveillance de performance basée sur une rsrp différentielle pour un modèle ou une fonctionnalité d'ia/am
WO2025194829A1 (fr) Prédiction de faisceau
WO2024156202A1 (fr) Transmission de liaison descendante basée sur de multiples trp
WO2025107605A1 (fr) Rapport de faisceaux
WO2025175837A1 (fr) Indication de relation qcl dynamique pour ensemble de ressources rs
WO2025175815A1 (fr) Collecte de données pour fonctionnalités prises en charge
WO2025055364A1 (fr) Compression de csi basée sur l'ia/ml
WO2025145707A1 (fr) Acquisition précoce de csi pour mobilité déclenchée de couche l1/l2
WO2024179075A1 (fr) Appariement de modèles pour compression de csi basée sur ia/ml
WO2024159790A1 (fr) Agrégation de bande passante pour positionnement
WO2025213873A1 (fr) Collecte de données de mesure basée sur une couche supérieure

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23935187

Country of ref document: EP

Kind code of ref document: A1