WO2024207851A1

WO2024207851A1 - Techniques for supporting native artificial intelligence in wireless communications systems

Info

Publication number: WO2024207851A1
Application number: PCT/CN2023/143542
Authority: WO
Inventors: Shuigen Yang; Mingzeng Dai; Congchi ZHANG
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2023-12-29
Filing date: 2023-12-29
Publication date: 2024-10-10
Anticipated expiration: 2026-06-29

Abstract

Various aspects of the present disclosure relate to support of native AI in wireless communication systems. In one aspect, a first network entity determines a configuration of a radio bearer associated with data traffic for at least one AI service. The radio bearer is different than an SRB supporting exchange of control information or a DRB supporting exchange of data. In turn, the first network entity transmits the configuration of the radio bearer to a UE.

Description

TECHNIQUES FOR SUPPORTING NATIVE ARTIFICIAL INTELLIGENCE IN WIRELESS COMMUNICATIONS SYSTEMS

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to techniques for supporting native artificial intelligence (AI) in wireless communications systems (e.g., radio access networks (RANs) ) .

BACKGROUND

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) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

It may be desirable that the wireless communications system support native AI to achieve inclusive intelligence and intelligent connections. Native AI means the AI is a natural part of the functionality, in terms of design, deployment, operation, and maintenance. A native AI implementation leverages a data-driven ecosystem, where data may be consumed and produced to realize new AI-based functionality or augment and replace static, rule-based mechanisms with learning and adaptive AI. For example, the wireless communications system should be deeply fused with AI applications to meet connection, computing, data, and algorithm requirements. In this way, the deep integration of communication connection and computing is realized at the network architecture level where the computing power and data in the wireless communications system are fully utilized.

SUMMARY

The present disclosure relates to network entities, UE and methods that support native AI in wireless communications systems (e.g., RAN) . With the network entities, the UE and the methods, a radio bearer associated with data traffic for at least one AI service may be established.

Some implementations of a first network entity described herein may comprise at least one memory and at least one processor coupled with the at least one memory and configured to cause the first network entity to: determine a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than a signaling radio bearer (SRB) or a data radio bearer (DRB) ; and transmit the configuration of the radio bearer to a UE.

In some implementations, the configuration of the radio bearer comprises: an identifier of the radio bearer; or a quality of service (QoS) configuration of the radio bearer.

In some implementations, the QoS configuration of the radio bearer comprises at least one rule for associating the data traffic with the radio bearer.

In some implementations, the at least one rule is associated with a priority, and the priority indicates an order in which the at least one rule is applied.

In some implementations, the QoS configuration of the radio bearer comprises at least one of the following: at least one computing requirement of the at least one AI service; at least one AI algorithm requirement of the AI service; or at least one data requirement of the at least one AI service.

In some implementations, the configuration of the radio bearer comprises destination information of a second network entity associated with AI service management functionality.

In some implementations, the configuration of the radio bearer comprises an indication of whether the radio bearer is a default radio bearer.

In some implementations, to determine the configuration, the at least one processor is configured to cause the first network entity to: determine a QoS configuration of the radio bearer based at least in part on one or more requirements of the at least one AI service.

In some implementations, the at least one processor is further configured to cause the first network entity to: receive an indication of the one or more requirements of the at least one AI service from the second network entity.

In some implementations, the at least one processor is further configured to cause the first network entity to: transmit, to the second network entity, a request for the one or more requirements of the at least one AI service.

In some implementations, the one or more requirements of the at least one AI service comprise at least one of the following: at least one computing requirement of the at least one AI service, at least one AI algorithm requirement of the at least one AI service, at least one data requirement of the at least one AI service, or at least one connection requirement of the at least one AI service.

In some implementations, the at least one computing requirement comprises at least one of the following: a computation duration of a computing task, or a computation accuracy of the computing task.

In some implementations, the at least one AI algorithm requirement comprises at least one of the following: at least one function of the at least one AI algorithm; at least one performance metric of the at least one AI algorithm; or at least one execution time of the at least one AI algorithm.

In some implementations, the at least one data requirement comprises at least one of the following: at least one ratio of first data in a data report to second data logged by the UE; at least one duration for a transmission of the data report; or at least one method for packaging the first data in the data report.

In some implementations, the at least one connection requirement comprises at least one of the following: a priority level indicating a priority in scheduling resources associated with the data traffic; a packet delay budget indicating a first upper bound for a time that a packet is delayed between the UE and a second network entity; or a packet error rate indicating a second upper bound for a rate of non-congestion related packet losses.

In some implementations, the at least one processor is further configured to cause the first network entity to: receive, from the UE, a request for establishing a connection with the first network entity. The request comprises an indication that indicates that the connection is for establishing the radio bearer.

In some implementations, the request further comprises destination information of a second network entityassociated with AI service management functionality.

In some implementations, the at least one processor is further configured to cause the first network entity to: transmit a first paging message to the UE. The first paging message comprises a first paging cause indicating that the first paging message is originated due to the at least one AI service.

In some implementations, the at least one processor is further configured to cause the first network entity to: receive a second paging message from a second network entity associated with AI service management functionality. The second paging message comprises a second paging cause indicating that the second paging message is originated due to the at least one AI service.

In some implementations, the at least one processor is further configured to cause the first network entity to: receive, from the UE over the radio bearer, data according to a data format.

In some implementations, the data format comprises a header and at least one payload. The header indicates one or more types of the data carried in the at least one payload.

In some implementations, the header further indicates a destination for the data.

Some implementations of a UE described herein may comprise at least one memory and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and configure the radio bearer based on the configuration of the radio bearer.

In some implementations, the QoS configuration of the radio bearer comprises at least one of the following: at least one computing requirement of the at least one AI service; at least one AI algorithm requirement of the at least one AI service; or at least one data requirement of the at least one AI service.

In some implementations, the processor is further configured to: transmit, to the first network entity, a request for establishing a connection with the first network entity. The request comprises an indication that indicates that the connection is for establishing the radio bearer.

In some implementations, the request further comprises destination information of a second network entity associated with AI service management functionality.

In some implementations, the at least one processor is further configured to: receive a first paging message from the first network entity. The first paging message comprises a first paging cause indicating that the first paging message is originated due to the at least one AI service.

In some implementations, the at least one processor is further configured to: transmit, to the first network entity over the radio bearer, data according to a data format.

Some implementations of a second network entity described herein may comprise at least one memory and at least one processor coupled with the at least one memory and configured to cause the second network entity to: determine one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality; and transmit an indication of the one or more requirements of the at least one AI service to a first network entity.

In some implementations, the at least one processor is further configured to cause the second network entity to: receive, from the first network entity, a request for the one or more requirements of the at least one AI service.

In some implementations, the at least one processor is further configured to cause the second network entity to: transmit a second paging message to the first network entity. The second paging message comprises a second paging cause indicating that the second paging message is originated due to the at least one AI service.

Some implementations of a method described herein may comprise: determining a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and transmitting the configuration of the radio bearer to a UE.

Some implementations of a method described herein may comprise: receiving, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and configuring the radio bearer based on the configuration of the radio bearer.

Some implementations of a method described herein may comprise: determining one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality; and transmitting an indication of the one or more requirements of the at least one AI service to a first network entity.

Some implementations of a processor described herein may comprise at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: determine one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality; and transmit an indication of the one or more requirements of the at least one AI service to a first network entity.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system that supports native AI in wireless communication systems in accordance with aspects of the present disclosure;

FIG. 2A illustrates another example of a wireless communications system that supports native AI in wireless communication systems in accordance with aspects of the present disclosure;

FIG. 2B illustrates a further example of a wireless communications system that supports native AI in wireless communication systems in accordance with aspects of the present disclosure;

FIG. 2C illustrates a still further example of a wireless communications system that supports native AI in wireless communication systems in accordance with aspects of the present disclosure;

FIGs. 3 and 4 illustrate a signaling diagram illustrating an example process that supports native AI in wireless communication systems in accordance with aspects of the present disclosure, respectively;

FIG. 5 illustrates an example of a data format in accordance with aspects of the present disclosure;

FIG. 6 illustrates a signaling diagram illustrating an example process that supports native AI in wireless communication systems in accordance with aspects of the present disclosure;

FIG. 7 illustrates an example of a device that supports native AI in wireless communication systems in accordance with some aspects of the present disclosure;

FIG. 8 illustrates an example of a processor that supports native AI in wireless communication systems in accordance with aspects of the present disclosure; and

FIGs. 9, 10 and 11 illustrate a flowchart of a method that supports native AI in wireless communication systems in accordance with aspects of the present disclosure, respectively.

DETAILED DESCRIPTION

Various aspects of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

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.

It shall be understood that although the terms “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 terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

A wireless communications system may support native AI to obtain inclusive intelligence and intelligent connections. The wireless communications system, including network entities and UEs may support various types of radio bears for exchange of control information and data, and the like. In some cases, the wireless communications system may supportan SRB or a DRB, or a combination thereof. The SRB and the DRB may be configured to support exchange of control information and data, support mobility for UEs, and ensure service experience for the UEs. Although use of the SRB and the DRB may be effective for legacy operation, for native AI related operations, the SRB and DRB may be limited (e.g., deficient) .

As an example, the SRB does not support an AI model transfer where an AI model size satisfies a threshold value (e.g., greater than 45KB) . An AI model is a program that has been trained on a set of data to recognize certain patterns or make certain decisions without further human intervention. Additionally, because the SRB requires the highest priority processing, it may be unsuitable for tasks with different quality of service (QoS) requirements. As another example, QoS provision for the DRB may be initiated by a core network (CN) of the wireless communications system. However, in the case of AI in the RAN, data transfer via the CN (e.g., exposure to the CN) may be unnecessary, eliminating any charging requirement. As an example, for hybrid beamforming, the data (or model) may have to be transferred between a UE and a network entity (e.g., a base station) within the RAN.

Various aspects of the present disclosure relate to supporting a native AI in the wireless communications system. A first network entity may determine a configuration of a radio bearer (also referred to as a computing bearer) associated with data traffic for at least one AI service. The radio bearer may be different than an SRB or a DRB. Put another way, the radio bearer may be specific for supporting control information and data traffic for at least one AI service and addressing the shortcomings of the SRB and the DRB as described herein. The first network entity may transmit the configuration of the radio bearer to a UE. The radio bearer associated with data traffic for at least one AI service may be established in response to the transmitted configuration. For example, the UE may establish a packet data convergence protocol (PDCP) entity and configure the PDCP entity in accordance with the received configuration of the radio bearer.

By enabling the wireless communications system, including network entities and UEs to support a radio bearer associated with data traffic for at least one AI service, may enable the wireless communications system to support AI-related operations compared to legacy communications systems. Additionally, by enabling the wireless communications system, including network entities and UEs to support a radio bearer associated with data traffic for at least one AI service may improve operational efficiency (e.g., utilization of resources) for the network entities and UEs when performing operations related to the at least one AI service.

Aspects of the present disclosure are described in the context of a wireless communications system.

FIG. 1 illustrates an example of a wireless communications system 100 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network (CN) 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as a long-term evolution (LTE) network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , 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.

The 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 (BS) , a network element, a radio access network (RAN) node, 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. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. For example, the network entities 102 may comprise a first network entity 102-1 and a second network entity 102-2, as shown in FIG. 1.

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. For example, 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. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 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. For example, 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. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, 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. Additionally, or alternatively, 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. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, 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) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, 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) .

In some implementations, 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) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (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.

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) . In some implementations, 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) ) .

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. For example, 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. In some implementations, the CU may host upper protocol layer (e.g., an L3, an 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 an 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.

Additionally, or alternatively, 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) . In some implementations, 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) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, 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) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

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. In some implementations, 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) .

In the wireless communications system 100, 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) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, 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 numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

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

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

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the 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) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

FIG. 2A illustrates another example of a wireless communications system 200A that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The wireless communications system 200A may implement or be implemented by aspects of the wireless communications system 100 as described herein with reference to FIG. 1. For example, the wireless communications system 200A may include a UE 104 and a CN 106, which may be examples of a UE 104 and a CN 106 as described herein with reference to FIG. 1. The wireless communications system 200A may also include a RAN 120, which may comprise a first network entity 102-1 (e.g., a base station (BS) ) and a second network entity 102-2 (e.g., an AI service management functionality (ASMF) ) , which may be examples of network entities 102 as described herein with reference to FIG. 1. The second network entity 102-2 may be separate from the first network entity 102-1 (e.g., the functionalities in the second network entity 102-2 are different than the functionalities in the first network entity 102-1) .

In some implementations, the second network entity 102-2 may be associated with (e.g., support, perform, process) ASMF. For example, the second network entity 102-2 may include, provide, or host the ASMF. In such implementations, the ASMF may be external to the first network entity 102-1.

In some implementations, the ASMF may be a RAN function.

In some implementations, the ASMF may comprise a computing power management functionality. For example, the computing power management functionality may comprise at least one of the following functionalities: computing power sensing functionality, for the sensing of computing power capability, resource status and service; computing power orchestration functionality, for the lifecycle management of the computing power; computing power scheduling functionality, for the scheduling of computing power based on the service requirements; or computing power allocation functionality.

Alternatively or additionally, in some implementations, the ASMF may comprise a data management functionality. For example, the data management may comprise at least one of the following functionalities: data collection functionality, for collecting RAN data; data storage functionality, for storing RAN data; data analytics functionality, for training AI models based on the collected RAN data and using AI models to obtain analysis result information; or data exposure functionality, for exposing RAN data as a service to application functions.

Alternatively or additionally, in some implementations, the ASMF may comprise an AI algorithm management functionality. For example, the AI algorithm management functionality may comprise at least one of the following functionalities: model training functionality, model inference operation functionality, model monitoring functionality, or model update functionality.

There may be multiple ASMF instance, wherein an ASMF instance is an identifiable instance of the ASMF. Some or all of the above ASMF functionalities may be supported in a single instance of the ASMF. For example, an ASMF instance includes the computing power sensing functionality, computing power orchestration functionality and computing power allocation functionality.

FIG. 2B illustrates an example of a wireless communications system 200B that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The wireless communications system 200B may implement or be implemented by aspects of the wireless communications system 100 as described herein with reference to FIG. 1. For example, the wireless communications system 200B may include a UE 104 and a CN 106, which may be examples of a UE 104 and a CN 106 as described herein with reference to FIG. 1. The wireless communications system 200B may also include a RAN 120, which may comprise a first network entity 102-1 (e.g., a BS) and a RAN controller 102-2, which may be examples of network entities 102 as described herein with reference to FIG. 1. The RAN controller 102-2 may be associated with (e.g., support, perform, process) ASMF. For example, the RAN controller 102-2 may include, provide, or host the ASMF. In such implementations, the ASMF may be external to the first network entity 102-1.

FIG. 2C illustrates an example of a wireless communications system 200C that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The wireless communications system 200C may implement or be implemented by aspects of the wireless communications system 100 as described herein with reference to FIG. 1. For example, the wireless communications system 200C may include a UE 104 and a CN 106, which may be examples of a UE 104 and a CN 106 as described herein with reference to FIG. 1. The wireless communications system 200C may also include a RAN 120, which may comprise a first network entity 102-1 (e.g., a BS) , which may be examples of network entities 102 as described herein with reference to FIG. 1. The first network entity 102-1 may be associated with (e.g., support, perform, process) ASMF. For example, the first network entity 102-1 may include, provide, or host the ASMF. In such implementations, the ASMF is within the first network entity 102-1, and the wireless communication system 200C does not comprise the second network entity 102-2.

FIG. 3 illustrates a signaling diagram of an example process flow 300 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The process flow 300 may implement aspects of the wireless communications systems as described herein with reference to FIGs. 1 through 2C, respectively. The process flow 300 may involve a first network entity 102-1 and a UE 104, which may be examples of a network entity and a UE as described herein with reference to FIGs. 1 through 2C.

At 310, the first network entity 102-1 may determine a configuration of a radio bearer. The radio bearer may be associated with data traffic for at least one AI service, and the radio bearer may be different than an SRB and a DRB. The radio bearer associated with the data traffic for the at least one AI service may be different than an SRB or a DRB, and may also be referred to as a computing radio bearer (CRB) . At 320, the first network entity 102-1 may transmit, and the UE 104 may receive, the configuration of the radio bearer (i.e., CRB) to the UE 104. For example, the first network entity 102-1 may transmit, and the UE 104 may receive, a radio resource control (RRC) message carrying the configuration of the radio bearer. In some other examples, the first network entity 102-1 may transmit a medium access control-control element (MAC-CE) or a downlink control information (DCI) , which may indicate (e.g., activate, enable) the configuration of the radio bearer for the data traffic associated with the at least one AI service. At 330, the UE 104 may configure (e.g., establish) the radio bearer based on the received configuration.

FIG. 4 illustrates a signaling diagram of an example process flow 400 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The process flow 400 may implement aspects of the wireless communications systems as described herein with reference to FIGs. 1 through 2C, respectively. The process flow 400 may be considered as an example implementation of the process flow 300. The process flow 400 may involve the UE 104, the first network entity 102-1 and the second network entity 102-2 in FIG. 2A or 2B. For the purpose of discussion, the process flow 400 will be described with reference to FIG. 2A or 2B.

Generally, in the process flow 400, the UE 104 may trigger establishment of a CRB for at least one AI service. For example, when the UE 104 wants to transmit the updated AI model to the first network entity 102-1 for the federated learning, the UE 104 may want to establish the CRB for the at least one AI service.

At 410, in order to trigger establishment of a CRB for at least one AI service, the UE 104 may transmit, and the first network entity 102-1 may receive, a request for establishing a connection with the first network entity 102-1.

For example, the UE 104 may, and the first network entity 102-1 may receive, an RRCSetupRequest message carrying the request for establishing the connection with the first network entity 102-1.

For another example, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCReestablishmentRequest message carrying the request for establishing the connection with the first network entity 102-1.

For a further example, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCResumeRequest message carrying the request for establishing the connection with the first network entity 102-1.

In some implementations, the request for establishing the connection with the first network entity 102-1 may comprise an indication that indicates that the connection is for establishing the radio bearer. For example, the RRCSetupRequest message may comprise a dedicated field. The dedicated field may comprise an indicator that indicates that the connection is for establishing the CRB. Alternatively, the indicator may indicate that the connection is for AI service or computing service.

Alternatively, in some implementations, the request for establishing the connection with the first network entity 102-1 may comprise a cause for establishment of the connection indicating the connection is for establishing the CRB. For example, the RRCSetupRequest message may comprise an establishmentCause information element (IE) . A value of the establishmentCause IE provides the establishment cause for the RRCSetupRequest in accordance with the at least one AI service. For example, the value of the IE may be AI service, CRB, or computing service.

In some implementations, the UE 104 may set the indicator or the establishmentCause IE in accordance with the information received from upper layers.

In some implementations, the request for establishing the connection with the first network entity 102-1 may further comprise a first destination which provides destination information of the second network entity 102-2 associated with AI service management functionality. For example, the destination information of the second network entity 102-2 may be the internet protocol version 4 (IPv4) /internet protocol version 4 (IPv6) address of the second network entity 102-2, MAC address of the second network entity 102-2, or the tunnel identity (e.g., virtual local area network identity) of the second network entity 102-2. The destination information of the second network entity 102-2 may be the destination of the RAN controller if the RAN controller includes the ASMF, as shown in FIG. 2B. For simplicity, the destination information of the second network entity 102-2 is the same as the destination of the RAN controller.

The request for establishing the connection with the first network entity 102-1 may further comprise the UE identity which is a UE identification used for the at least one AI service. The UE identity may be a unique identification, or a temporarily identification.

In some implementations, the first network entity 102-1 may not include the ASMF as shown in FIG. 2A and 2B. In such implementations, at 430, the second network entity 102-2 may transmit, and the first network entity 102-1 may receive, one or more requirements of the at least one AI service. For example, at 430, the second network entity 102-2 may transmit, and the first network entity 102-1 may receive, an indication of the one or more requirements of the at least one AI service. Hereinafter, the one or more requirements of the at least one AI service are also referred to as “AI service requirement” for brevity.

In some implementations, in order to obtain the AI service requirement, the first network entity 102-1 may transmit, and the second network entity 102-2 may receive, a request for the AI service requirement. For example, at 420, the first network entity 102-1 may transmit, and the second network entity 102-2 may receive, the request for the AI service requirement by transmitting an AI service request.

In some implementations, if the request for establishing the connection with the first network entity 102-1 comprises the first destination, the first network entity 102-1 may transmit the request for the AI service requirement based on the first destination.

In some implementations, the request for the AI service requirement may comprise the UE identity which is received from the UE in the RRCSetupRequest message.

Alternatively, in some implementations, the first network entity 102-1 may obtain the AI service requirement without transmitting the request for the AI service requirement. In such implementations, the second network entity 102-2 may transmit the AI service requirement to the first network entity 102-1. For example, the second network entity 102-2 may transmit the AI service requirement to the first network entity 102-1 before the UE 104 transmits the request for establishing a connection with the first network entity 102-1.

In some implementations, the first network entity 102-1 may include the ASMF as shown in FIG. 2C. In such implementations, the first network entity 102-1 may obtain the AI service requirement locally. Thus, the actions 420 and 430 may be omitted.

In some implementations, the AI service requirement may comprise at least one of the following: at least one computing requirement of the at least one AI service, at least one AI algorithm requirement of the at least one AI service, at least one data requirement of the at least one AI service, or at least one connection requirement of the at least one AI service.

In some implementations, the at least one computing requirement may comprise at least one of the following: a computation duration of a computing task, or a computation accuracy of the computing task.

In some implementations, the at least one AI algorithm requirement may comprise at least one of the following: at least one function of the at least one AI algorithm; at least one performance metric of the at least one AI algorithm; or at least one execution time of the at least one AI algorithm. For example, the at least one function may be channel quality estimation, hybrid beamforming, or spectrum sensing. The at least one performance metric may be mean absolute error indicating mean absolute difference between the predicted values and the actual values in a dataset, or root mean square error indicating square root of average squared difference between the predicted values and the actual values in a dataset. The at least one execution time may be the number of operations, e.g., the number of iterations.

In some implementations, the at least one data requirement may comprise at least one ratio of first data in a data report to second data logged by the UE 104.

In some implementations, the at least one ratio may comprise a first ratio. The first ratio may be equal to a ratio threshold of a first amount of data which has been logged by the UE 104 to a second amount of data that the UE 104 is indicated to log. If a ratio of the first amount to the second amount is equal to or above the first ratio, the UE 104 may trigger reporting or transmission of the logged data.

In some implementations, the at least one ratio may comprise a second ratio. The second ratio may be equal to a ratio threshold of a first amount of data which has been logged by the UE 104 to a maximum amount of data that the UE 104 can log. If a ratio of the first amount to the maximum amount is equal to or above the first ratio, the UE 104 may trigger reporting or transmission of the logged data.

Alternatively or additionally, in some implementations, the at least one data requirement may comprise at least one of the following: at least one duration for a transmission of the data report; or at least one method for packaging the first data in the data report. For example, the at least one method for packaging the first data in the data report may indicate a maximum number of records per data report.

In some implementations, the at least one connection requirement comprise at least one of the following: a priority level indicating a priority in scheduling resources associated with the data traffic; a packet delay budget indicating a first upper bound for a time that a packet is delayed between the UE 104 and the second network entity 102-2; or a packet error rate indicating a second upper bound for a rate of non-congestion related packet losses.

At 440, the first network entity 102-1 may determine the configuration of the CRB.

In some implementations, the configuration of the CRB may comprise a quality of service (QoS) configuration of the CRB.

In some implementations, the QoS configuration of the CRB may comprise at least one rule for associating the data traffic with the CRB. Based on at least one rule for associating the data traffic with the CRB, the UE 104 may determine the association of uplink (UL) and/or downlink (DL) data traffic with the CRB. Hereinafter, the at least one rule for associating the data traffic with the CRB is also referred to as at least one traffic classification rule.

For example, the UL data traffic is an IP packet, and a traffic classification rule should support at least any combination of the following: source/destination IP address or IPv6 prefix, source/destination port number, type of service/traffic class and mask. For another example, the UL data traffic is an ethernet packet, and a traffic classification rule should support at least any combination of the following: source/destination MAC address, virtual local area network tag.

In some implementations, there may be multiple traffic classification rules associated with the same CRB. In such implementations, each of the multiple traffic classification rules may be associated with a priority. The priority indicates an order in which a respective one of the multiple traffic classification rules is applied by the UE 104.

In some implementations, the QoS configuration of the CRB may comprise at least one of the following: the at least one computing requirement of the at least one AI service; the at least one AI algorithm requirement of the AI service; or the at least one data requirement of the at least one AI service.

Some implementations of the at least one computing requirement, the at least one AI algorithm requirement and the at least one data requirement have been described with reference to the action 430. Details of these implementations are omitted for brevity.

In some implementations, the first network entity 102-1 may determine the QoS configuration of the CRB based at least in part on the AI service requirement.

For example, the first network entity 102-1 may determine the QoS forwarding treatment for the CRB (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration) based on the at least one connection requirement in the AI service requirement received from the second network entity 102-2, and then determine that the at least one computing requirement, the at least one AL algorithm requirement, and/or the at least one data requirement in the QoS configuration of the CRB are the same as those in the AI service requirement.

For another example, the first network entity 102-1 may determine the QoS configuration of the CRB by itself. For example, the first network entity 102-1 may include the ASMF locally, and the ASMF may determine the at least one computing requirement, the at least one AL algorithm requirement, and/or the at least one data requirements.

In turn, the first network entity 102-1 may transmit, and the UE 104 may receive, the configuration of the CRB.

For example, if the UE 104 transmits the RRCSetupRequest message to the first network entity 102-1 at 410, at 450, the first network entity 102-1 may transmit, and the UE 104 may receive, an RRCSetup message comprising the configuration of the CRB.

For another example, if the UE 104 transmits the RRCReestablishmentRequest message to the first network entity 102-1 at 410, the first network entity 102-1 may transmit, and the UE 104 may receive, an RRCReestablishment message comprising the configuration of the CRB.

For a further example, if the UE 104 transmits the RRCResumeRequest message to the first network entity 102-1 at 410, the first network entity 102-1 may transmit, and the UE 104 may receive, an RRCResume message comprising the configuration of the CRB.

In some implementations, the configuration of the CRB may comprise an identifier of the CRB. The identifier of the CRB is unique within the scope of the UE 104. That is, two CRBs cannot use the same identifier for the UE 104. In the present disclosure, the term “identifier” may be used interchangeably with the term “identity” .

In some implementations, the configuration of the CRB may also comprise a second destination which provides the destination information of the second network entity 102-2. The second network entity 102-2 is associated with the ASMF.

In one example, if the RRCSetupRequest message received from the UE 104 comprises the first destination, the configuration of the CRB does not need to comprise the second destination.

In another example, if the RRCSetupRequest message received from the UE 104 does not comprise the first destination, the configuration of the CRB comprises the second destination.

In some implementations, the configuration of the CRB may comprise an IE which provides the second destination.

In some implementations, the configuration of the CRB may comprise an indicator which indicates whether the ASMF is included in the first network entity 102-1.For example, if the value of the indicator is set to 1, TRUE or YES, the UE 104 may determine the ASMF is included in the first network entity 102-1. If the value of the indicator is set to 0, FALSE or NO, the UE 104 may determine the ASMF is not included in the first network entity 102-1.

In some implementations, the configuration of the CRB may also comprise an indication which indicates whether the CRB is a default CRB. If the UE 104 cannot find any traffic classification rule mapping to the data traffic to be transferred in other CRBs, the UE 104 determines to use the default CRB for transmission of data traffic. For the default CRB, the QoS configuration does not comprise any traffic classification rule.

At 460, the UE 104 may configure the CRB based on the configuration of the CRB.

In some implementations, optionally, the UE 104 may transmit, and the first network entity 102-1 may receive, an indication indicating that the CRB is configured.

For example, if the UE 104 transmits the RRCSetupRequest message to the first network entity 102-1 at 410, at 470, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCSetupComplete message comprising the indication.

For another example, if the UE 104 transmits the RRCReestablishmentRequest message to the first network entity 102-1 at 410, at 470, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCReestablishmentComplete message comprising the indication.

For a further example, if the UE 104 transmits the RRCResumeRequest message to the first network entity 102-1 at 410, at 470, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCResume message comprising the indication at 470.

Upon configuring the CRB, the CRB is established between the UE 104 and the first network entity 102-1.

After the establishment of the CRB, there may be three radio bearers in the UE 104/the first network entity 102-1: SRB, DRB, and CRB. The SRB is used for the transmission of RRC and NAS messages. The DRB is used for the transmission of data traffic between the UE 104 and the core network 106. The CRB is used for the transmission of data traffic for at least one AI service.

In some implementations, the first network entity 102-1 may further want to modify and/or release the CRB.

In one example, the first network entity 102-1 may transmit, and the UE 104 may receive, an RRCReconfiguration messagecarrying an identifier of the CRB to be released.

In another example, the first network entity 102-1 may transmit, and the UE 104 may receive, an RRCReconfiguration message carrying an identifier of the CRB and the updated configuration of the CRB, e.g., the updated QoS configuration of the CRB.

In some implementations, whenever there is a need to transfer the collected RAN data, at 480, the UE 104 may transmit, and the first network entity 102-1 may receive, the RAN data over the CRB.

In some implementations, at 480, the UE 104 may transmit, and the first network entity 102-1 may receive, the RAN data according to a data format over the CRB.

In some implementations, the data format may comprise a header and at least one payload. The header indicates one or more types of the data carried in the at least one payload. The at least one payload may follow the header.

FIG. 5 illustrates an example of a data format 500 in accordance with aspects of the present disclosure. As shown in FIG. 5, the data format 500 comprises a header 510 and payload 1, payload 2, payload 3, payload 4, payload 5, payload 6, payload 7, …, payload n.

The header 510 may comprise one or more fields. Each of the one or more fields may be associated with one type of the RAN data. For example, the header 510 may comprise at least one of the following field: a B/C field, an L field, an RT field, an HM field, an LM field, a CS field, a CP field, or an M field.

In some implementations, the B/C field may indicate the destination of the RAN data. For example, if the bit value is set to 0, the destination of the RAN data is the first network entity 102-1. If the bit value is set to 1, the destination of the RAN data is the ASMF out of the first network entity 102-1. In this case, the payload 1 should include the destination information of the ASMF.

In some implementations, the L field may indicate the location information of the UE 104. For example, if the bit value is set to 1, the payload 2 should include the detailed location information of the UE 104.

In some implementations, the RT field may indicate the radio access technology information. For example, if the bit value is set to 1, the payload 3 should include the detailed radio access technology information, e.g., new radio.

In some implementations, the HM field may indicate the layer 3 measurement result. For example, if the bit value is set to 1, the payload 4 should include the detailed layer 3 measurement result, e.g., cell level measurement result based on channel state information reference signal (CSI-RS) related measurement.

In some implementations, the LM field may indicate the layer 1 measurement result. For example, if the bit value is set to 1, the payload 5 should include the detailed layer 1 measurement result, e.g., beam level measurement result based on synchronization signal/physical broadcast channel block (SSB) related measurement.

In some implementations, the CS field may indicate connectivity state of the UE 104 when the UE 104 performs the task, e.g., training. For example, if the bit value is set to 1, the payload 6 should include the detailed connectivity state of the UE 104, e.g., RRC_IDLE, RRC_INACTIVE, RRC_CONNECTED.

In some implementations, the CP field may indicate computing power of the UE 104 when the UE 104 performs the task, e.g., training. For example, if the bit value is set to 1, the payload 7 should include the detailed computing power of the UE 104, e.g., 35 tera operations per second.

In some implementations, the M field is reserved for future use.

In some implementations, the header may further indicate a destination for the RAN data.

It shall be noted that the data format 500 is illustrated by way of example. Depending on the type of the RAN data, the header 510 may comprise more or less fields. The scope of the present disclosure is not limited in this regard.

Returning to FIG. 4, in some implementations, based on the received at least one data requirement at 450, the UE 104 may determine whether to transmit the RAN data to the first network entity 102-1.

As described above, in some implementations, the at least one data requirement may comprise the at least one ratio.

In some implementations, the at least one ratio may comprise a first ratio. The first ratio may be equal to a ratio threshold of a first amount of data which has been logged by the UE 104 to a second amount of data that the UE 104 is indicated to log. If a ratio of the first amount to the second amount is equal to or above the first ratio, the UE 104 may trigger reporting or transmission of the logged data. For example, the first ratio may be equal to 80%. If the UE 104 is indicated to log data of 100MB, the second amount is equal to 100MB. If the UE 104 has logged 80MB, the first amount is equal to 80MB. The ratio of the first amount to the second amount is equal to 80%, which is equal to the first ratio. Thus, the UE 104 may trigger reporting or transmission of the logged data.

In some implementations, the at least one ratio may comprise a second ratio. The second ratio may be equal to a ratio threshold of a first amount of data which has been logged by the UE 104 to a maximum amount of data that the UE 104 can log. If a ratio of the first amount to the maximum amount is equal to or above the first ratio, the UE 104 may trigger reporting or transmission of the logged data. For example, the second ratio may be equal to 70%. The maximum amount may be equal to 100MB. If the UE 104 has logged 70MB, the first amount is equal to 70MB. The ratio of the first amount to the maximum amount is equal to 70%, which is equal to the second ratio. Thus, the UE 104 may trigger reporting or transmission of the logged data.

In some implementations, if a duration or period between the last data reporting and the current data reporting achieves a duration or period for a transmission of a data report, the UE 104 may trigger transmission of the RAN data.

In some implementations, records in the data report should not exceed the method for packaging the data in the data report in the received at least one data requirement.

In some implementations, based on the received destination information at 510, the UE 104 may determine the destination where the RAN data should be transmitted to.

For example, if the received destination information is destination information of the ASMF out of the first network entity 102-1, the bit value of the B/C field should be set to 1, and the destination information of the ASMF should be included. In this case, the destination information of the ASMF may be the same as destination information of the second network entity 102-2 or destination information of the RAN controller. If the received destination information is destination information of the first network entity 102-1, the bit value of the B/C field should be set to 0.

In some implementations, at 490, the first network entity 102-1 may forward, and the second network entity 102-2 may receive, the RAN data.

In one example, if the header of the received RAN data indicates the destination of the ASMF out of the first network entity 102-1, the first network entity 102-1 should not decode the RAN data but transparently forward the RAN data to the second network entity 102-2 including the ASMF.

In another example, if the header of the received RAN data indicates the destination of the first network entity 102-1, the first network entity 102-1 should not forward the RAN data to the second network entity 102-2.

FIG. 6 illustrates a signaling diagram of an example process flow 600 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The process flow 400 may implement aspects of the wireless communications systems as described herein with reference to FIGs. 1 through 2C, respectively. The process flow 600 may be considered as another example implementation of the process flow 300. The process flow 600 may involve the UE 104, the first network entity 102-1 and the second network entity 102-2 in FIG. 2A or 2B. For the purpose of discussion, the process flow 600 will be described with reference to FIG. 2A or 2B.

Generally, in the process flow 600, the second network entity 102-2 including the ASMF may trigger establishment of a CRB for at least one AI service.

At 610, in order to trigger establishment of a CRB for at least one AI service, the second network entity 102-2 may transmits, and the first network entity may receive, a second paging message. The second paging message may comprise a second paging cause indicating that the second paging message is originated due to the at least one AI service.

In turn, at 620, the first network entity 102-1 may transmit, and the UE 104 may receive, a first paging message.

In one example, the first paging message may comprise a first paging cause indicating that the first paging message is originated due to the at least one AI service. For example, a value of the first paging cause may be AI service, computing service, or CRB.

In another example, the first paging message may comprise an access type with a value indicating whether the first paging message is originated due to the request from the ASMF out of the first network entity 102-1. For example, the value may be ASMF.

In some implementations, the first network entity 102-1 may transmit the first paging message to the UE 104 without receiving the second paging message from the second network entity 102-2. For example, if the first network entity 102-1 wants to establish the CRB for the at least one AI service when the UE 104 is in an RRC_IDLE state or an RRC_INACTIVE state (e.g., the first network entity 102-1 transmits an AI training task to the UE 104) , the first network entity 102-1 may transmit the first paging message to the UE 104 to trigger the establishment of the CRB.

Upon receiving the first paging message, the UE 104 may forward the first paging cause or the access type received in the first paging message to the upper layers of the UE 104.

After that, the UE 104 may initiate an RRC connection establishment procedure, an RRC connection re-establishment procedure, or an RRC connection resume procedure. The detailed descriptions of the RRC connection establishment procedure, the RRC connection re-establishment procedure and the RRC connection resume procedure have been described with respect to the actions 410, 450 and 470 in FIG. 4.

For example, in order to initiate the RRC connection establishment procedure, at 630, the UE 104 may transmit, and the first network entity 102-1, an RRCSetupRequest message carrying the request for establishing the connection with the first network entity 102-1.

For another example, in order to initiate the RRC connection re-establishment procedure, at 630, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCReestablishmentRequest message carrying the request for establishing the connection with the first network entity 102-1.

For a further example, in order to initiate the RRC connection resume procedure, at 630, the UE 104 may transmit, and the first network entity 102-1 may receive, an RRCResumeRequest message carrying the request for establishing the connection with the first network entity 102-1.

The actions 640, 650, 660, 670, 680 and 690 are similar to the actions 420, 430, 440, 450, 460 and 470 in FIG. 4. Details of these actions are omitted for brevity.

FIG. 7 illustrates an example of a device 700 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The device 700 may be an example of a network entity 102 or a UE 104 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. For example, 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.

In some implementations, 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. In some implementations, 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) .

For example, 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 performing the following: determining a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and transmitting the configuration of the radio bearer to a UE.

Alternatively, in some implementations, the processor 702 may be configured to operable to support a means for performing the following: receiving, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and configuring the radio bearer based on the configuration of the radio bearer.

Alternatively, in some implementations, the processor 702 may be configured to operable to support a means for performing the following: determining one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality; and transmitting an indication of the one or more requirements of the at least one AI service to a first network entity.

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) . In some implementations, the processor 702 may be configured to operate a memory array using a memory controller. In some other implementations, 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. In some implementations, 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. In some implementations, 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.

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. In some implementations, the I/O controller 708 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 708 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 708 may be implemented as part of a processor, such as the processor 702. In some implementations, 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.

In some implementations, the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (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 710, wired, or wireless links as described herein. For example, 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 710 for transmission, and to demodulate packets received from the one or more antennas 710. 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 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. For example, the receive chain may include one or more antennas 710 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 processor 800 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. 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 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) 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) .

The controller 802 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 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

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

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

The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 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 controller 802 and/or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and/or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 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 806 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800) . In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800) . One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 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 806 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to operable to support a means for performing the following: determining a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and transmitting the configuration of the radio bearer to a UE.

Alternatively, in some implementations, the processor 800 may be configured to operable to support a means for performing the following: receiving, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one AI service, wherein the radio bearer is different than an SRB or a DRB; and configuring the radio bearer based on the configuration of the radio bearer.

Alternatively, in some implementations, the processor 800 may be configured to operable to support a means for performing the following: determining one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality; and transmitting an indication of the one or more requirements of the at least one AI service to a first network entity.

FIG. 9 illustrates a flowchart of a method 900 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a device or its components as described herein. For example, the operations of the method 900 may be performed by the first network entity 102-1 as described herein. In some implementations, 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.

At 910, the method may include determining a configuration of a radio bearer associated with data traffic for at least one AI service. The radio bearer is different than an SRB or a DRB. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to FIG. 1, 2A, 2B or 2C.

At 920, the method may include transmitting the configuration of the radio bearer to a UE. The operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a device as described with reference to FIG. 1, 2A, 2B or 2C.

FIG. 10 illustrates a flowchart of a method 1000 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by the UE 104 as described herein. In some implementations, 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.

At 1010, the method may include receiving, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one AI service. The radio bearer is different than an SRB or a DRB. The operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to FIG. 1, 2A, 2B or 2C.

At 1020, the method may include configuring the radio bearer based on the configuration of the radio bearer. The radio bearer is different than an SRB or a DRB. The operations of 1020 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1020 may be performed by a device as described with reference to FIG. 1, 2A, 2B or 2C.

FIG. 11 illustrates a flowchart of a method 1100 that supports native AI in wireless communication systems in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by the second network entity 102-2 as described herein. In some implementations, 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.

At 1110, the method may include determining one or more requirements of at least one AI service, wherein the second network entity is associated with AI service management functionality. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1, 2A or 2B.

At 1120, the method may include transmitting an indication of the one or more requirements of the at least one AI service to a first network entity. The operations of 1120 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1120 may be performed by a device as described with reference to FIG. 1, 2A or 2B.

It shall be noted that implementations of the present disclosure which have been described with reference to Figs. 1 to 6 are also applicable to the device 700, the processor 800 as well as the methods 900, 1000 and 1100.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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. By way of example, 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.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be 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. In other words, as used herein, the phrase “based on”shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

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

Claims

A first network entity, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the first network entity to:

determine a configuration of a radio bearer associated with data traffic for at least one artificial intelligence (AI) service, wherein the radio bearer is different than a signaling radio bearer (SRB) or a data radio bearer (DRB) ; and

transmit the configuration of the radio bearer to a user equipment (UE) .
The first network entity of claim 1, wherein, to determine the configuration, the at least one processor is configured to cause the first network entity to:

determine a quality of service (QoS) configuration of the radio bearer based at least in part on one or more requirements of the at least one AI service.
A user equipment (UE) , comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the UE to:

receive, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one artificial intelligence (AI) service, wherein the radio bearer is different than a signaling radio bearer (SRB) or a data radio bearer (DRB) ; and

configure the radio bearer based on the configuration of the radio bearer.
The UE of claim 3, wherein the configuration of the radio bearer comprises:

an identifier of the radio bearer; or

a quality of service (QoS) configuration of the radio bearer.
The UE of claim 4, wherein the QoS configuration of the radio bearer comprises at least one rule for associating the data traffic with the radio bearer.
The UE of claim 5, wherein the at least one rule is associated with a priority, and wherein the priority indicates an order in which the at least one rule is applied.
The UE of claim 4, wherein the QoS configuration of the radio bearer comprises at least one of the following:

at least one computing requirement of the at least one AI service;

at least one AI algorithm requirement of the at least one AI service; or

at least one data requirement of the at least one AI service.
The UE of claim 4, wherein the configuration of the radio bearer comprises destination information of a second network entity associated with AI service management functionality.
The UE of claim 4, wherein the configuration of the radio bearer comprises an indication of whether the radio bearer is a default radio bearer.
The UE of claim 7, wherein the at least one computing requirement comprises at least one of the following:

a computation duration of a computing task, or

a computation accuracy of the computing task.
The UE of claim 7, wherein the at least one AI algorithm requirement comprises at least one of the following:

at least one function of the at least one AI algorithm;

at least one performance metric of the at least one AI algorithm; or

at least one execution time of the at least one AI algorithm.
The UE of claim 7, wherein the at least one data requirement comprises at least one of the following:

at least one ratio of first data in a data report to second data logged by the UE;

at least one duration for a transmission of the data report; or

at least one method for packaging the first data in the data report.
The UE of claim 3, wherein the processor is further configured to:

transmit, to the first network entity, a request for establishing a connection with the first network entity, wherein the request comprises an indication that indicates that the connection is for establishing the radio bearer.
The UE of claim 13, wherein the request further comprises destination information of a second network entity associated with AI service management functionality.
The UE of claim 3, wherein the at least one processor is further configured to:

receive a first paging message from the first network entity, wherein the first paging message comprises a first paging cause indicating that the first paging message is originated due to the at least one AI service.
The UE of claim 3, wherein the at least one processor is further configured to:

transmit, to the first network entity over the radio bearer, data according to a data format.
The UE of claim 16, wherein the data format comprises a header and at least one payload, wherein the header indicates one or more types of the data carried in the at least one payload.
The UE of claim 17, wherein the header further indicates a destination for the data.
A second network entity, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the second network entity to:

determine one or more requirements of at least one artificial intelligence (AI) service, wherein the second network entity is associated with AI service management functionality; and

transmit an indication of the one or more requirements of the at least one AI service to a first network entity.
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

receive, from a first network entity, a configuration of a radio bearer associated with data traffic for at least one artificial intelligence (AI) service, wherein the radio bearer is different than a signaling radio bearer (SRB) or a data radio bearer (DRB) ; and

configure the radio bearer based on the configuration of the radio bearer.