WO2025156340A1

WO2025156340A1 - Systems and methods for user equipment performance feedback

Info

Publication number: WO2025156340A1
Application number: PCT/CN2024/077963
Authority: WO
Inventors: Man ZHANG; Jiajun Chen; Yin Gao; Dapeng Li; Zhuang Liu
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-02-21
Filing date: 2024-02-21
Publication date: 2025-07-31
Anticipated expiration: 2026-08-21

Abstract

Presented are systems and methods for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture. A first network node of a split architecture may send a request for performance data of one or more wireless communication devices to a second network node of the split architecture. The first network node may receive a response to the request from the second network node. The performance data can be for processing by an artificial intelligence (AI) function.

Description

SYSTEMS AND METHODS FOR USER EQUIPMENT PERFORMANCE FEEDBACK

TECHNICAL FIELD

The disclosure relates generally to wireless communications, including but not limited to systems and methods for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture.

BACKGROUND

The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) . The 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) . In order to facilitate the enablement of different data services and requirements, the elements of the 5GC, also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need. Communication via satellite is one of the typical scenarios of the non-terrestrial networks in 3GPP standardization.

SUMMARY

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

At least one aspect is directed to a system, method, apparatus, or a computer-readable medium of the following. A first network node (e.g., a gNB-centralized unit (CU) , or a gNB-CU-control plane (CP) ) of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node (e.g., a gNB-distributed unit (DU) , or a gNB-CU-user plane (UP) ) of the (e.g., CU-DU) split architecture. The first network node may receive a response to the request from the second network node. The performance data can be for processing by an artificial intelligence (AI) function, e.g., to determine/calculate velocity and/or location information. The present disclosure describes the procedures for performance feedback in a split architecture. The performance data may comprise at least one of: resource status information; performance feedback of the one or more wireless communication devices; trajectory information of the one or more wireless communication devices; or energy cost of the one or more wireless communication devices. The present disclosure provides information that may be included as the performance feedback. Currently, there is no definition for performance feedback in a F1 application protocol (F1AP) or a E1 application protocol (E1AP) message. In some embodiments, the first network node may deploy the AI function. The first network node may process the performance data using the AI function.

In some embodiments, the request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. The present disclosure introduces information that may be included in the request message for UE performance feedback, so that a receiving node (e.g., that is receiving and/or measuring a reference signal that has traversed a target) can be able to understand the intention of collecting the UE performance, and to identify the different tasks of data collection. The configuration for collection of the UE performance may comprise at least one of: a collection time duration; a collection time window; or a collection interval. For example, the time duration may indicate a period of time, e.g., 5 seconds. The collection time window may include a start time and a stop time. The present disclosure provides information that may be included in the configuration for collection for UE performance, which may regulate the specific task of data collection.

In some embodiments, the response comprises at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a node measurement initiation result list; or a cell measurement initiation result list. The present disclosure introduces information included in the response message of the request for the performance feedback. With the information included in the response message, the first network node can be aware of how the performance feedback is triggered in the second network node. The node measurement initiation result list may comprise an indication of at least one of: a measurement characteristic or object associated with a measurement or initialization failure; a cause of the measurement or initialization failure; or a list of user equipment (UE) IDs associated with the measurement or initialization failure. The present disclosure provides a list for node level measurement initiation result, which can include the result information collected within a node, e.g., a gNB-DU, or a gNB-CU-UP.

In some embodiments, the cell measurement initiation result list may comprise an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. The present disclosure provides a list for cell level measurement initiation result, which can include the result information collected within multiple cells. In some embodiments, the first network node may receive an update message (e.g., a data collection update message, a resource status update message, or a resource update message) to the request from the second network. The update message may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The present disclosure describes the message that is used to update the data collected in the UE for the purpose of AI/ML processing.

In some embodiments, the UE associated information may comprise at least one of: a UE ID; a data radio bearer (DRB) ID; an average UE throughput; a maximum UE throughput; a minimum UE throughput; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss; a maximum packet loss; or a minimum packet loss. In some embodiments, the above measurements can be calculated per UE. If the DRB ID is present, the result can be calculated per DRB per UE. The present disclosure describes/provides information that may be collected as UE performance. Currently, there is no definition for the UE performance feedback in a split architecture. In some embodiments, the request for performance data can be sent via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message. The present disclosure points out the interface (s) that is involved/utilized, e.g., a F1AP in a CU-DU split architecture, or a E1AP in a gNB-CU-CP/UP split architecture. In some embodiments, the response can be received via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message. The present disclosure points out the interface (s) that is involved/utilized, e.g., a F1AP in a CU-DU split architecture, a E1AP in a gNB-CU-CP/UP split architecture.

In some embodiments, the first network node can be a gNB centralized unit (gNB-CU) or a gNB-CU-control plane (gNB-CU-CP) . The second network node can be a gNB distributed unit (gNB-DU) or a gNB-CU-user plane (gNB-CU-UP) . In some embodiments, the request may comprise a data collection request or a resource status request. The response may comprise a data collection response or a resource status response.

In some embodiments, a second network node of a split architecture (e.g., a gNB-distributed unit (DU) , or a gNB-CU-user plane (UP) ) may receive a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) from a first network node of the split architecture (e.g., a gNB-centralized unit (CU) , or a gNB-CU-control plane (CP) ) . The second network node may send a response to the request to the first network node. The performance data can be for processing by an artificial intelligence (AI) function.

BRIEF DESCRIPTION OF THE DRAWINGS

Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure;

FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure;

FIG. 3 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure;

FIG. 5 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure; and

FIG. 7 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

1. Mobile Communication Technology and Environment

FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100. ” Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In FIG. 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.

For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.

FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.

System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) . The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.

As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.

The UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various embodiments, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some embodiments, the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.

The network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.

The Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols. The OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.

Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

2. Systems and Methods for User Equipment (UE) Performance Feedback for an Artificial Intelligence (AI) /Machine Learning (ML) Function in a Split Architecture

A next generation radio access network (NG-RAN) node, featuring (CU-DU) split architecture, can support an artificial intelligence (AI) /machine learning (ML) function. However, within the split architecture, there is a lack of support for UE performance feedback. The present disclosure provides a method for enabling a gNB distributed unit (gNB-DU) /gNB-CU-user plane (gNB-CU-UP) to deliver user equipment (UE) performance feedback to a gNB centralized unit (gNB-CU) /gNB-CU-control plane (gNB-CU-CP) .

A NG-RAN node can support/host/execute/include an AI function. The following approaches can be incorporated in whole or in part, in accordance with the solutions disclosed herein. Considering locations of AI/ML model training and AI/ML model inference for mobility solution, the following two options can be considered. In some embodiments, the AI/ML model training function can be deployed in an operations, administration and maintenance (OAM) , while the model inference function may reside within the RAN node. In some embodiments, both the AI/ML model training function and the AI/ML model inference function can reside within the RAN node.

In some embodiments, for a CU-DU split architecture scenario, the following options can be possible. For example, AI/ML model training can be located/performed in a CU or an OAM, and an AI/ML model inference function can be located in a CU. For example, AI/ML model training can be located/performed in a CU or an OAM, and an AI/ML model inference function can be located in a DU. In some embodiments, the gNB can be allowed to continue model training based on the AI/ML model (that is already/partially) trained in the OAM.

In some embodiments, the following information can be configured to be reported by an NG-RAN node. The information may include at least one of: predicted resource status information; UE performance feedback information; a measured UE trajectory; or an energy cost (EC) . The collection and reporting can be configured through a data collection reporting Initiation procedure, while the actual reporting can be performed through a data collection reporting procedure. In some embodiments, the collection of measured UE trajectory and UE performance feedback can be triggered by successful execution of a handover.

Implementation Example 1: Messages for F1AP UE performance feedback

FIG. 3 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure.

Step 1: A first network node of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node of the split architecture. The first network node can be a gNB-centralized unit (CU) . The second network node can be a gNB-distributed unit (DU) . The UE performance data can be measurement results collected/gathered/received/reported from at least one UE, e.g., some L2 measurements such as throughput, for the network to evaluate the performance of UE after the AI/ML function is deployed. The performance data may comprise at least one of: resource status information; performance feedback of the one or more UEs; trajectory information of the one or more UEs; or energy cost of the UEs. For example, the gNB-CU may send a new F1AP message to a gNB-DU, e.g., DATA COLLECTION REQUEST message. The request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. In some embodiments, the measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement identifier (ID) allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. This information element (IE) may not be mandatory. For example, during initiation of the UE performance data, the gNB-DU measurement ID may not be present. In some embodiments, the list of user equipment (UE) IDs may indicate UEs of which the performance feedback can be collected by the gNB-DU. The registration request can be a type of request for which the information is requested, which can be encoded as, e.g., an ENUMERATED Type which includes codes such as start, stop, modify, add, delete, etc. In the initial request for the UE performance feedback, the Registration Request can be set to “start. ” The characteristic or object for reporting can be a report characteristic that indicates the object that the gNB-DU is requested to report, e.g., the specific UE performance feedback, or the energy cost at gNB-DU. The report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-DU can report. The list of cell IDs can be to identify cell (s) for data collection, or cell IDs to which the request applies. The periodicity for reporting can be a reporting periodicity, which may indicate the periodicity that can be used for reporting of requested objects. This periodicity can also be used as the averaging window length for all objects if supported. The configuration for collection of UE performance (or UE performance data) can include at least one of following information: a collection time duration; a collection time window; or a collection interval. For example, the collection time duration may indicate a period of time, e.g., 5 seconds. The collection time duration may start at the execution of the UE performance measurement. The collection time window may include a start time and a stop time. The collection time window may indicate the duration of time for the UE performance to be measured. The collection interval may indicate the time between two continuous performance collection durations. The present disclosure provides information that may be included in the configuration for collection of UE performance data, which may regulate the specific task of data collection.

Step 2: The first network node may receive a response to the request from the second network node. For example, the gNB-DU may send a new F1AP message to the gNB-CU, e.g., DATA COLLECTION RESPONSE message. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a node measurement initiation result list; or a cell measurement initiation result list. The measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement ID allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. In some embodiments, the node measurement initiation result list can be a list of measurement objects that failed to be initiated, e.g., the performance metrics that have failed to be measured as UE performance data/feedback. Each item in the measurement initiation result list may include an indication of at least one of: a measurement characteristic or object associated with a measurement or initialization failure; a cause of the measurement or initialization failure; or a list of user equipment (UE) IDs associated with the measurement or initialization failure. The measurement characteristic or object can be node measurement failed report characteristics, which indicates the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. The measurement failed report characteristics can be indicated by/using a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-DU failed to initiate/obtain as the UE performance feedback. The cause may indicate the failure cause/reason for measurement objects for which measurement cannot be initiated. The list of UE IDs associated with the measurement or initialization failure may indicate/identify the UEs for which the performance feedback has failed to be initiated by the gNB-DU. In some embodiments, the cell measurement initiation result list can be a list of measurement objects that have failed to be initiated per cell. Each item of the cell measurement initiation result list may include an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. In certain embodiments, all the UEs in the cell may have failed to collect/provide corresponding/any UE performance data. The measurement characteristic or object may indicate that the gNB-DU cannot initiate the measurement for at least one of the requested measurement objects in the cell. Cell measurement failed report characteristics may indicate the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. Measurement failed report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object failed to initiate/provide as UE performance in the cell. The failure cause/reason may indicate the cause and/or reason that the measurement objects cannot be initiated in the cell.

Step 2a: If none of the requested data collection objects in step 1 can be initiated, the gNB-DU may send a DATA COLLECTION FAILURE message to the gNB-CU. This message may include at least one of the following: a gNB-CU measurement ID allocated by the gNB-CU; a gNB-DU measurement ID allocated by the gNB-DU; or a cause which indicates cause of the failure of the request.

In some embodiments, after the data collection request is successfully initiated, the gNB-DU may collect the UE performance data as requested by the gNB-CU. The UE performance data can be the measurement results collected from at least one UE, e.g., some L2 measurements such as throughput, for the network to evaluate the performance of the at least one UE after the AI/ML function is deployed.

Step 3: The first network node may receive an update message (e.g., a data collection update message) to the request from the second network. For example, the gNB-DU may send a new F1AP message, e.g., DATA COLLECTION UPDATE message, to the gNB-CU. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement ID allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. The UE associated information can be a UE associated information result list. Each item in the list may include at least one of the following information: a UE ID; a data radio bearer (DRB) ID; an average UE throughput (downlink or uplink) ; a maximum UE throughput (downlink or uplink) ; a minimum UE throughput (downlink or uplink) ; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss (downlink or uplink) ; a maximum packet loss (downlink or uplink) ; or a minimum packet loss (downlink or uplink) . In some embodiments, the above measurements can be calculated per UE. If the DRB ID is present, the performance feedback information list can be taken as a DRB level performance feedback, and the result can be calculated per DRB per UE. The energy cost can be the measurement energy consumption at the gNB-DU.

In some embodiments, the gNB-CU may collect the UE performance feedback for use by an AI/ML function, e.g., to evaluate the performance of UE that experiences mobility. After some duration of collection of UE performance feedback, the gNB-CU may send another DATA COLLECTION REQUEST message to the gNB-DU to stop collecting the UE performance feedback, with the Registration Request type set to “stop. ” In this case, the gNB-DU measurement ID allocated by the gNB-DU can be present in the DATA COLLECTION REQUEST message. In certain embodiments, the gNB-CU may also send the DATA COLLECTION REQUEST message to the gNB-DU, to modify, add, or delete some measurement objects, with the Registration Request type set as modify, add, or delete.

Implementation Example 2: Messages for F1AP UE performance feedback

FIG. 4 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure.

Step 1: A first network node of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node of the split architecture. The first network node can be a gNB-centralized unit (CU) . The second network node can be a gNB-distributed unit (DU) . The UE performance can be measurement results collected/gathered/received/reported from at least one UE, e.g., some L2 measurements such as throughput, for the network to evaluate the performance of UE after the AI/ML function is deployed. The performance data may comprise at least one of: resource status information; performance feedback of the one or more UEs; trajectory information of the one or more UEs; or energy cost of the UEs. For example, the gNB-CU may send a F1AP message to a gNB-DU, e.g., RESOURCE STATUS REQUEST message. The request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. In some embodiments, the measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement identifier (ID) allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. This information element (IE) may not be mandatory. For example, during initiation of the UE performance, the gNB-DU measurement ID may not be present. In some embodiments, the list of user equipment (UE) IDs may indicate UEs of which the performance feedback can be collected by the gNB-DU. The registration request can be a type of request for which the information is requested, which can be encoded as, e.g., an ENUMERATED Type which includes codes such as start, stop, modify, add, delete, etc. In the initial request for the UE performance feedback, the Registration Request can be set to “start. ” The characteristic or object for reporting can be a report characteristic that indicates the object that the gNB-DU is requested to report, e.g., the specific UE performance feedback, or the energy cost at gNB-DU. The report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object the gNB-DU can report. The list of cell IDs can be to identify cell (s) for data collection, a cell IDs to which the request applies. The periodicity for reporting can be a reporting periodicity, which may indicate the periodicity that can be used for reporting of requested objects. This periodicity can also be used as the averaging window length for all objects if supported. The configuration for collection of UE performance (or UE performance data) can include at least one of following information: a collection time duration; a collection time window; or a collection interval. For example, the collection time duration may indicate a period of time, e.g., 5 seconds. The collection time duration may start at the execution of the UE performance measurement. The collection time window may include a start time and a stop time. The collection time window may indicate the duration of time for the UE performance to be measured. The collection interval may indicate the time between two continuous performance collection durations. The present disclosure provides information that may be included in the configuration for collection of UE performance data, which may regulate the specific task of data collection.

Step 2: The first network node may receive a response to the request from the second network node. For example, the gNB-DU may send a F1AP message to the gNB-CU, e.g., RESOURCE STATUS RESPONSE message. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a node measurement initiation result list; or a cell measurement initiation result list. The measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement ID allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. In some embodiments, the node measurement initiation result list can be a list of measurement objects that are failed to be initiated, e.g., the performance metrics that have failed to be measured as UE performance feedback/data. Each item in the measurement initiation result list may include an indication of at least one of: a measurement characteristic or object associated with a measurement or initialization failure; a cause of the measurement or initialization failure; or a list of user equipment (UE) IDs associated with the measurement or initialization failure. The measurement characteristic or object can be node measurement failed report characteristics, which indicates the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. The measurement failed report characteristics can be indicated by/using a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-DU failed to initiate/obtain as the UE performance feedback. The cause may indicate the failure cause/reason for measurement objects for which measurement cannot be initiated. The list of UE IDs associated with the measurement or initialization failure may indicate/identify the UEs for which the performance feedback has failed to be initiated by the gNB-DU. In some embodiments, the cell measurement initiation result list can be a list of measurement objects that have failed to be initiated per cell. Each item of the cell measurement initiation result list may include an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. In certain embodiments, all the UEs in the cell may have failed to collect/provide corresponding/any UE performance data. The measurement characteristic or object may indicate that the gNB-DU cannot initiate the measurement for at least one of the requested measurement objects in the cell. Cell measurement failed report characteristics may indicate the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. Measurement failed report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object failed to initiate/provide as UE performance in the cell. The failure cause/reason may indicate the cause and/or reason that the measurement objects cannot be initiated in the cell.

Step 2a: If none of the requested data collection objects in step 1 can be initiated, the gNB-DU may send a RESOURCE STATUS FAILURE message to the gNB-CU. This message may include at least one of the following: a gNB-CU measurement ID allocated by the gNB-CU; a gNB-DU measurement ID allocated by the gNB-DU; or a cause which indicates cause of the failure of the request.

In some embodiments, after the data collection request is successfully initiated, the gNB-DU may collect the UE performance data as requested by the gNB-CU. The UE performance data can be the measurement results collected from at least one UE, e.g, , some L2 measurements such as throughput, for the network to evaluate the performance of the at least one UE after the AI/ML function is deployed.

Step 3: The first network node may receive an update message (e.g., a data collection update message) to the request from the second network. For example, the gNB-DU may send a F1AP message, e.g., RESOURCE STATUS UPDATE message, to the gNB-CU. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The measurement identifier (ID) allocated by the first network node can be a gNB-CU measurement ID allocated by the gNB-CU. The measurement ID allocated by the second network node can be a gNB-DU measurement ID allocated by the gNB-DU. The UE associated information can be a UE associated information result list. Each item in the list may include at least one of the following information: a UE ID; a data radio bearer (DRB) ID; an average UE throughput (downlink or uplink) ; a maximum UE throughput (downlink or uplink) ; a minimum UE throughput (downlink or uplink) ; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss (downlink or uplink) ; a maximum packet loss (downlink or uplink) ; or a minimum packet loss (downlink or uplink) . In some embodiments, the above measurements can be calculated per UE. If the DRB ID is present, the performance feedback information list can be taken as a DRB level performance feedback, and the result can be calculated per DRB per UE. The energy cost can be the measurement energy consumption at the gNB-DU.

In some embodiments, the gNB-CU may collect the UE performance feedback for the use by an AI/ML function, e.g., to evaluate the performance of UE that experiences mobility. After some duration of collection of UE performance feedback, the gNB-CU may send another RESOURCE STATUS REQUEST message to the gNB-DU to stop collecting the UE performance feedback, with the Registration Request type set to “stop. ” In this case, the gNB-DU measurement ID allocated by the gNB-DU can be present in the RESOURCE STATUS REQUEST message. In certain embodiments, the gNB-CU may also send the RESOURCE STATUS REQUEST message to the gNB-DU, to modify, add, or delete some measurement objects, with the Registration Request type set as modify, add, or delete.

Implementation Example 3: Messages for E1AP UE performance feedback

FIG. 5 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure.

Step 1: A first network node of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node of the split architecture. The first network node can be a gNB-CU-control plane (gNB-CU-CP) . The second network node can be a gNB-CU-user plane (gNB-CU-UP) . The UE performance data can be measurement results collected/gathered/received/reported from at least one UE, e.g., some L2 measurements such as throughput, for the network to evaluate the performance of UE after the AI/ML function is deployed. The performance data may comprise at least one of: resource status information; performance feedback of the one or more UEs; trajectory information of the one or more UEs; or energy cost of the UEs. For example, the gNB-CU-CP may send a new F1AP message to a gNB-CU-UP, e.g., DATA COLLECTION REQUEST message. The request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. In some embodiments, the measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement identifier (ID) allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. This information element (IE) may not be mandatory. For example, during an initiation of the UE performance data, the gNB-CU-UP measurement ID may not be present. In some embodiments, the list of user equipment (UE) IDs may indicate UEs of which the performance feedback can be collected by the gNB-CU-UP. The registration request can be a type of request for which the information is requested, which can be encoded as, e.g., an ENUMERATED Type which includes codes such as start, stop, modify, add, delete, etc. In the initial request for the UE performance feedback, the Registration Request can be set to “start. ” The characteristic or object for reporting can be a report characteristic that indicates the object that the gNB-CU-UP is requested to report, e.g., the specific UE performance feedback, or the energy cost at gNB-CU-UP. The report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-CU-UP can report. The list of cell IDs can be to identify a cell for data collection, or cell IDs to which the request applies. The periodicity for reporting can be a reporting periodicity, which may indicate the periodicity that can be used for reporting of requested objects. This periodicity can also be used as the averaging window length for all objects if supported. The configuration for collection of UE performance (or UE performance data) can include at least one of following information: a collection time duration; a collection time window; or a collection interval. For example, the collection time duration may indicate a period of time, e.g., 5 seconds. The collection time duration may start at the execution of the UE performance measurement. The collection time window may include a start time and a stop time. The collection time window may indicate the duration of time for the UE performance to be measured. The collection interval may indicate the time between two continuous performance collection durations. The present disclosure provides information that may be included in the configuration for collection of UE performance data, which may regulate the specific task of data collection.

Step 2: The first network node may receive a response to the request from the second network node. For example, the gNB-CU-UP may send a new F1AP message to the gNB-CU-CP, e.g., DATA COLLECTION RESPONSE message. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a node measurement initiation result list; or a cell measurement initiation result list. The measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement ID allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. In some embodiments, the node measurement initiation result list can be a list of measurement objects that failed to be initiated, e.g., the performance metrics that have failed to be measured as UE performance data/feedback. Each item in the measurement initiation result list may include an indication of at least one of: a measurement characteristic or object associated with a measurement or initialization failure; a cause of the measurement or initialization failure; or a list of user equipment (UE) IDs associated with the measurement or initialization failure. The measurement characteristic or object can be node measurement failed report characteristics, which indicates the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. The measurement failed report characteristics can be indicated by/using a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-CU-UP failed to initiate/obtain as the UE performance feedback. The cause may indicate the failure cause/reason for measurement objects for which measurement cannot be initiated. The list of UE IDs associated with the measurement or initialization failure may indicate/identify the UEs for which the performance feedback has failed to be initiated by the gNB-CU-UP. In some embodiments, the cell measurement initiation result list can be a list of measurement objects that have failed to be initiated per cell. Each item of the cell measurement initiation result list may include an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. In certain embodiments, all the UEs in the cell may have failed to collect/provide corresponding/any UE performance data. The measurement characteristic or object may indicate that the gNB-CU-UP can not initiate the measurement for at least one of the requested measurement objects in the cell. Cell measurement failed report characteristics may indicate the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. Measurement failed report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate/provide each specific object failed to initiate as UE performance in the cell. The failure cause/reason may indicate the cause and/or reason that the measurement objects that cannot be initiated in the cell.

Step 2a: If none of the requested data collection objects in step 1 can be initiated, the gNB-CU-UP may send a DATA COLLECTION FAILURE message to the gNB-CU-CP. This message may include at least one of the following: a gNB-CU-CP measurement ID allocated by the gNB-CU-CP; a gNB-CU-UP measurement ID allocated by the gNB-CU-UP; or a cause which indicates cause of the failure of the request.

In some embodiments, after the data collection request is successfully initiated, the gNB-CU-UP may collect the UE performance data as requested by the gNB-CU-CP. The UE performance data can be the measurement results collected from at least one UE, e.g, some L2 measurements such as throughput, for the network to evaluate the performance of the at least one UE after the AI/ML function is deployed.

Step 3: The first network node may receive an update message (e.g., a data collection update message) to the request from the second network. For example, the gNB-CU-UP may send a new F1AP message, e.g., DATA COLLECTION UPDATE message, to the gNB-CU-CP. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement ID allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. The UE associated information can be a UE associated information result list. Each item in the list may include at least one of the following information: a UE ID; a data radio bearer (DRB) ID; an average UE throughput (downlink or uplink) ; a maximum UE throughput (downlink or uplink) ; a minimum UE throughput (downlink or uplink) ; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss (downlink or uplink) ; a maximum packet loss (downlink or uplink) ; or a minimum packet loss (downlink or uplink) . In some embodiments, the above measurements can be calculated per UE. If the DRB ID is present, the performance feedback information list can be taken as a DRB level performance feedback, and the result can be calculated per DRB per UE. The energy cost can be the measurement energy consumption at the gNB-CU-UP.

In some embodiments, the gNB-CU-CP may collect the UE performance feedback for use by an AI/ML function, e.g., to evaluate the performance of UE that experiences mobility. After some duration of collection of UE performance feedback, the gNB-CU-CP may send another DATA COLLECTION REQUEST message to the gNB-CU-UP to stop collecting the UE performance feedback, with the Registration Request type set to “stop. ” In this case, the gNB-CU-UP measurement ID allocated by the gNB-CU-UP can be present in the DATA COLLECTION REQUEST message. In certain embodiments, the gNB-CU-CP may also send the DATA COLLECTION REQUEST message to the gNB-CU-UP, to modify, add, or delete some measurement objects, with the Registration Request type set as modify, add, or delete.

Implementation Example 4: Messages for E1AP UE performance feedback

FIG. 6 illustrates a flow diagram of an example method for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture, in accordance with some embodiments of the present disclosure.

Step 1: A first network node of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node of the split architecture. The first network node can be a gNB-CU-control plane (gNB-CU-CP) . The second network node can be a gNB-CU-user plane (gNB-CU-UP) . The UE performance can be measurement results collected/gathered/received/reported from at least one UE, e.g., some L2 measurements such as throughput, for the network to evaluate the performance of UE after the AI/ML function is deployed. The performance data may comprise at least one of: resource status information; performance feedback of the one or more UEs; trajectory information of the one or more UEs; or energy cost of the UEs. For example, the gNB-CU-CP may send a F1AP message to a gNB-CU-UP, e.g., RESOURCE STATUS REQUEST message. The request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. In some embodiments, the measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement identifier (ID) allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. This information element (IE) may not be mandatory. For example, during an initiation of the UE performance, the gNB-CU-UP measurement ID may not be present. In some embodiments, the list of user equipment (UE) IDs may indicate UEs of which the performance feedback can be collected by the gNB-CU-UP. The registration request can be a type of request for which the information is requested, which can be encoded as, e.g., an ENUMERATED Type which includes codes such as start, stop, modify, add, delete, etc. In the initial request for the UE performance feedback, the Registration Request can be set to “start. ” The characteristic or object for reporting can be a report characteristic that indicates the object that the gNB-CU-UP is requested to report, e.g., the specific UE performance feedback, or the energy cost at gNB-CU-UP. The report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate each specific object the gNB-CU-UP can report. The list of cell IDs can be to identify cell (s) for data collection, a cell IDs to which the request applies. The periodicity for reporting can be a reporting periodicity, which may indicate the periodicity that can be used for reporting of requested objects. This periodicity can also be used as the averaging window length for all objects if supported. The configuration for collection of UE performance (or UE performance data) can include at least one of following information: a collection time duration; a collection time window; or a collection interval. For example, the collection time duration may indicate a period of time, e.g., 5 seconds. The collection time duration may start at the execution of the UE performance measurement. The collection time window may include a start time and a stop time. The collection time window may indicate the duration of time for the UE performance to be measured. The collection interval may indicate the time between two continuous performance collection durations. The present disclosure provides information that may be included in the configuration for collection of UE performance data, which may regulate the specific task of data collection.

Step 2: The first network node may receive a response to the request from the second network node. For example, the gNB-CU-UP may send a F1AP message to the gNB-CU-CP, e.g., RESOURCE STATUS RESPONSE message. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a node measurement initiation result list; or a cell measurement initiation result list. The measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement ID allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. In some embodiments, the node measurement initiation result list can be a list of measurement objects that have failed to be initiated, e.g., the performance metrics that have failed to be measured as UE performance feedback/data. Each item in the measurement initiation result list may include an indication of at least one of: a measurement characteristic or object associated with a measurement or initialization failure; a cause of the measurement or initialization failure; or a list of user equipment (UE) IDs associated with the measurement or initialization failure. The measurement characteristic or object can be node measurement failed report characteristics, which indicates the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. The measurement failed report characteristics can be indicated by/using a bit string or a bitmap. Each position in the bitmap may indicate each specific object that the gNB-CU-UP failed to initiate/obtain as the UE performance feedback. The cause may indicate the failure cause/reason for measurement objects for which measurement cannot be initiated. The list of UE IDs associated with the measurement or initialization failure may indicate/identify the UEs for which the performance feedback has failed to be initiated by the gNB-CU-UP. In some embodiments, the cell measurement initiation result list can be a list of measurement objects that have failed to be initiated per cell. Each item of the cell measurement initiation result list may include an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. In certain embodiments, all the UEs in the cell may have failed to collect/provide corresponding/any UE performance data. The measurement characteristic or object may indicate that the gNB-CU-UP can not initiate the measurement for at least one of the requested measurement objects in the cell. Cell measurement failed report characteristics may indicate the object that failed to be initiated in the cell, e.g., the specific UE performance feedback. Measurement failed report characteristics can be indicated in a bit string or a bitmap. Each position in the bitmap may indicate/provide each specific object failed to initiate as UE performance in the cell. The failure cause/reason may indicate the cause and/or reason that the measurement objects that cannot be initiated in the cell.

Step 2a: If none of the requested data collection objects in step 1 can be initiated, the gNB-CU-UP may send a RESOURCE STATUS FAILURE message to the gNB-CU-CP. This message may include at least one of the following: a gNB-CU-CP measurement ID allocated by the gNB-CU-CP; a gNB-CU-UP measurement ID allocated by the gNB-CU-UP; or a cause which indicates cause of the failure of the request.

Step 3: The first network node may receive an update message (e.g., a data collection update message) to the request from the second network. For example, the gNB-CU-UP may send a F1AP message, e.g., RESOURCE STATUS UPDATE message, to the gNB-CU-CP. This message may include at least one of the following: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The measurement identifier (ID) allocated by the first network node can be a gNB-CU-CP measurement ID allocated by the gNB-CU-CP. The measurement ID allocated by the second network node can be a gNB-CU-UP measurement ID allocated by the gNB-CU-UP. The UE associated information can be a UE associated information result list. Each item in the list may include at least one of the following information: a UE ID; a data radio bearer (DRB) ID; an average UE throughput (downlink or uplink) ; a maximum UE throughput (downlink or uplink) ; a minimum UE throughput (downlink or uplink) ; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss (downlink or uplink) ; a maximum packet loss (downlink or uplink) ; or a minimum packet loss (downlink or uplink) . In some embodiments, the above measurements can be calculated per UE. If the DRB ID is present, the performance feedback information list can be taken as a DRB level performance feedback, and the result can be calculated per DRB per UE. The energy cost can be the measurement energy consumption at the gNB-CU-UP.

In some embodiments, the gNB-CU-CP may collect the UE performance feedback for the use by an AI/ML function, e.g., to evaluate the performance of UE that experiences mobility. After some duration of collection of UE performance feedback, the gNB-CU-CP may send another RESOURCE STATUS REQUEST message to the gNB-CU-UP to stop collecting the UE performance feedback, with the Registration Request type set to “stop. ” In this case, the gNB-CU-UP measurement ID allocated by the gNB-CU-UP can be present in the RESOURCE STATUS REQUEST message. In certain embodiments, the gNB-CU-CP may also send the RESOURCE STATUS REQUEST message to the gNB-CU-UP, to modify, add, or delete some measurement objects, with the Registration Request type set as modify, add, or delete.

It should be understood that one or more features from the above/following implementation examples are not exclusive to the specific implementation examples, but can be combined in any manner (e.g., in any priority and/or order, concurrently or otherwise) .

FIG. 7 illustrates a flow diagram of a method 700 for user equipment (UE) performance feedback for an artificial intelligence (AI) /machine learning (ML) function in a split architecture. The method 700 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGs. 1–6. In overview, the method 700 may be performed by a first network node (e.g., a gNB-centralized unit (CU) , or a gNB-CU-control plane (CP) ) , in some embodiments. Additional, fewer, or different operations may be performed in the method 700 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.

A first network node (e.g., a gNB-centralized unit (CU) , or a gNB-CU-control plane (CP) ) of a split architecture may send a request for performance data of one or more wireless communication devices (e.g., one or more user equipment (UEs) ) to a second network node (e.g., a gNB-distributed unit (DU) , or a gNB-CU-user plane (UP) ) of the split architecture. The first network node may receive a response to the request from the second network node. The performance data can be for processing/use by an artificial intelligence (AI) function. The present disclosure describes the procedures for performance feedback in a split architecture. The performance data may comprise at least one of: resource status information; performance feedback of the one or more wireless communication devices; trajectory information of the one or more wireless communication devices; or energy cost of the one or more wireless communication devices. The present disclosure describes/defines/provides information that may be included as the performance feedback. Currently, there is no definition of (UE) performance feedback in a F1 application protocol (F1AP) or a E1 application protocol (E1AP) message. In some embodiments, the first network node may deploy/host/execute the AI function. The first network node may process the performance data using the AI function.

In some embodiments, the request may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; a list of user equipment (UE) IDs; a registration request; a characteristic or object for reporting; a list of cell IDs; a periodicity for reporting; or a configuration for collection of user equipment (UE) performance. The present disclosure introduces information that may be included in the request message for UE performance feedback, so that a receiving node can be able to understand the intention of collecting the UE performance, and to identify the different tasks of data collection. The configuration for collection of the UE performance may comprise at least one of: a collection time duration; a collection time window; or a collection interval. For example, the time duration may indicate a period of time, e.g., 5 seconds. The collection time window may include a start time and/or a stop time. The present disclosure provides information that may be included in the configuration for collection for UE performance, which may regulate the specific task of data collection.

In some embodiments, the cell measurement initiation result list may comprise an indication of at least one of: a list of cell IDs associated with a measurement or initialization failure; a measurement characteristic or object associated with the measurement or initialization failure; or a cause of the measurement or initialization failure. The present disclosure provides a list for cell level measurement initiation result, which can include the result information collected within multiple cells. In some embodiments, the first network node may receive an update message (e.g., a data collection update message, a resource status update message, or a resource update message) to the request from the second network. The update message may comprise at least one of: a measurement identifier (ID) allocated by the first network node; a measurement ID allocated by the second network node; user equipment (UE) associated information; performance feedback information; or energy cost of the second network node. The present disclosure describes/defines/provides the message that can be used to update the data being collected in the UE for the purpose of AI/ML processing.

In some embodiments, the UE associated information may comprise at least one of: a UE ID; a data radio bearer (DRB) ID; an average UE throughput; a maximum UE throughput; a minimum UE throughput; an average packet delay; a maximum packet delay; a minimum packet delay; an average packet loss; a maximum packet loss; or a minimum packet loss. In some embodiments, the above measurements can be calculated per (e.g., for each) UE. If the DRB ID is present, the result can be calculated per DRB per UE. The present disclosure provides information that may be collected as UE performance (data/feedback) . Currently, there is no definition for the UE performance feedback in a split architecture. In some embodiments, the request for performance data can be sent via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message. The present disclosure points out the interface (s) that is utilized/involved, e.g., a F1AP in a CU-DU split architecture, or a E1AP in a gNB-CU-CP/UP split architecture. In some embodiments, the response can be received via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message. The present disclosure points out the interface (s) that is utilized/involved, e.g., a F1AP in a CU-DU split architecture, a E1AP in a gNB-CU-CP/UP split architecture.

While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

It is also understood that any reference to an element herein using a designation such as "first, " "second, " and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

A method, comprising:

sending, by a first network node of a split architecture, to a second network node of the split architecture, a request for performance data of one or more wireless communication devices; and

receiving, by the first network node from the second network, a response to the request, wherein the performance data is for processing by an artificial intelligence (AI) function.
The method of claim 1, where the performance data comprises at least one of:

resource status information;

performance feedback of the one or more wireless communication devices;

trajectory information of the one or more wireless communication devices; or

energy cost of the one or more wireless communication devices.
The method of claim 1, wherein the request comprises at least one of:

a measurement identifier (ID) allocated by the first network node;

a measurement ID allocated by the second network node;

a list of user equipment (UE) IDs;

a registration request;

a characteristic or object for reporting;

a list of cell IDs;

a periodicity for reporting; or

a configuration for collection of user equipment (UE) performance.
The method of claim 3, wherein the configuration for collection of the UE performance comprises at least one of:

a collection time duration;

a collection time window; or

a collection interval.
The method of claim 1, wherein the response comprises at least one of:

a measurement identifier (ID) allocated by the first network node;

a measurement ID allocated by the second network node;

a node measurement initiation result list; or

a cell measurement initiation result list.
The method of claim 5, wherein the node measurement initiation result list comprises an indication of at least one of:

a measurement characteristic or object associated with a measurement or initialization failure;

a cause of the measurement or initialization failure; or

a list of user equipment (UE) IDs associated with the measurement or initialization failure.
The method of claim 5, wherein the cell measurement initiation result list comprises an indication of at least one of:

a list of cell IDs associated with a measurement or initialization failure;

a measurement characteristic or object associated with the measurement or initialization failure; or

a cause of the measurement or initialization failure.
The method of claim 1, comprising:

receiving, by the first network node from the second network, an update message to the request, wherein the update message comprises at least one of:

a measurement identifier (ID) allocated by the first network node;

a measurement ID allocated by the second network node;

user equipment (UE) associated information;

performance feedback information; or

energy cost of the second network node.
The method of claim 8, wherein the UE associated information comprises at least one of:

a UE ID;

a data radio bearer (DRB) ID;

an average UE throughput;

a maximum UE throughput;

a minimum UE throughput;

an average packet delay;

a maximum packet delay;

a minimum packet delay;

an average packet loss;

a maximum packet loss; or

a minimum packet loss.
The method of claim 1, wherein the request for performance data is sent via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message.
The method of claim 1, wherein the response is received via a F1 application protocol (F1AP) message or a E1 application protocol (E1AP) message.
The method of claim 1, wherein the first network node is a gNB centralized unit (gNB-CU) or a gNB-CU-control plane (gNB-CU-CP) .
The method of claim 1, wherein the second network node is a gNB distributed unit (gNB-DU) or a gNB-CU-user plane (gNB-CU-UP) .
The method of claim 1, wherein the request comprises a data collection request or a resource status request.
The method of claim 1, wherein the response comprises a data collection response or a resource status response.
A method, comprising:

receiving, by a second network node of a split architecture, from a first network node of the split architecture, a request for performance data of one or more wireless communication devices;

sending, by the second network node to the first network node, a response to the request, wherein the performance data is for processing by an artificial intelligence (AI) function.
A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-16.
An apparatus comprising:

at least one processor configured to perform the method of any one of claims 1-16.