Apparatus and method for routing data for a radio bearer

Abstract

Various aspects of the present disclosure relate to routing data for a radio bearer. New data for a radio bearer can be received at a packet data convergence protocol (PDCP) layer, the new data corresponding to a data type of a plurality of data types. A priority level for the data type can be identified, the identified priority level being one of a plurality of priority levels. The new data can be routed to a radio link control (RLC) entity that corresponds to the identified priority level. The RLC entity can be of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

Description

APPARATUS AND METHOD FOR ROUTING DATA FOR A RADIO BEARERRELATED APPLICATION

[0001] This application claims priority to U.S. Patent Application Serial No. 63 / 573,715 filed April 3, 2024 entitled “APPARATUS AND METHOD FOR ROUTING DATA FOR A RADIO BEARER,” the disclosure of which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to an apparatus and method for routing data for a radio bearer.BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting 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, such as time resources (e.g., symbols, slots, subframes, frames, or the like) and / or frequency resources (e.g., subcarriers, carriers, or the like), of the wireless communication system. Additionally, the wireless communications system may support wireless communications across various radio access technologies including third-generation (3G) radio access technology, fourthgeneration (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0004] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may be configured to, capable of, or operable to receive, at a packet data convergence protocol (PDCP) layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and route the new data to a radio link control (RLC) entity thatcorresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0005] A processor (e.g., a standalone processor chipset, or a component of a UE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and route the new data to a RLC entity that corresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0006] A method performed or performable by a UE for wireless communication is described. The method may include receiving, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identifying a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and routing the new data to a RLC entity that corresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0007] In some implementations of the UE, the processor, and the method described herein, the new data comprises a PDCP service data unit (SDU), and where to identify the respective priority level for the data type, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to parse a data information parameter attached to the PDCP SDU. In some implementations of the UE, the processor, and the method described herein, the UE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity, and where to route the new data to the respective RLC entity, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to select the respective RLC entity based on the mapping configuration.

[0008] In some implementations of the UE, the processor, and the method described herein, the plurality of priority levels comprises different quality of service (QoS) requirements for different stages of an artificial intelligence (Al) life cycle management (LCM) procedure. In someimplementations of the UE, the processor, and the method described herein, the PDCP entity is configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels.

[0009] In some implementations of the UE, the processor, and the method described herein, the data type comprises an Al model-related long-term evolution positioning protocol (LPP) data type. In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to use a dedicated radio bearer for Al-related LPP data for transmission of the new data. In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to route PDCP control protocol data units (PDUs) from the PDCP layer to an RLC entity having a highest priority level of the plurality of RLC entities.

[0010] In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to determine an air interface is congested; and discard data units associated with a lower priority level of the plurality of priority levels based on determining the air interface is congested, where the data units comprise at least one selected from service data units (SDUs) and PDUs. In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to determine a priority of the new data for a purpose of buffer status reporting based on a priority of the RLC entity the new data is routed to; ascertain the priority of the new data is higher than a priority of other data available for transmission; and trigger a buffer status report in response to ascertaining the priority of the new data is higher than the priority of the other data available for transmission.

[0011] In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configured to, capable of, performed, performable, or operable to compare the label to a list of labels identifying data types corresponding to at least one configured grant resource allocation; and transmit the new data on a corresponding configured grant allocation based on comparing the label to the list of labels. In some implementations of the UE, processor, and method described herein, the UE, processor, and method may further be configuredto, capable of, performed, performable, or operable to determine the identified priority level is higher than a priority threshold; and transmit the new data on SRB 1 or SRB2 based on the identified priority level being higher than the priority threshold.

[0012] An NE (e.g., a base station) for wireless communication is described. The NE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the NE may be configured to, capable of, or operable to receive, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and route the new data to a RLC entity that corresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0013] A processor (e.g., a standalone processor chipset, or a component of a NE (e.g., a base station)) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and route the new data to a RLC entity that corresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0014] A method performed or performable by an NE (e.g., a base station) for wireless communication is described. The method may include receiving, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types; identifying a priority level for the data type, where the identified priority level is one of a plurality of priority levels; and routing the new data to a RLC entity that corresponds to the identified priority level, where the RLC entity is one of a plurality of RLC entities, and where a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

[0015] In some implementations of the NE, the processor, and the method described herein, the new data comprises a PDCP SDU, and where to identify the respective priority level for the datatype, the NE, processor, and method may further be configured to, capable of, performed, performable, or operable to parse a data information parameter attached to the PDCP SDU.

[0016] In some implementations of the NE, the processor, and the method described herein, the NE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity, and where to route the new data to the respective RLC entity, the NE, processor, and method may further be configured to, capable of, performed, performable, or operable to select the respective RLC entity based on the mapping configuration.

[0017] In some implementations of the NE, the processor, and the method described herein, the plurality of priority levels comprises different QoS requirements for different stages of an Al LCM procedure.

[0018] In some implementations of the NE, the processor, and the method described herein, the PDCP entity is configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels.

[0019] In some implementations of the NE, the processor, and the method described herein, the data type comprises an Al model-related LPP data type.

[0020] In some implementations of the NE, processor, and method described herein, the NE, processor, and method may further be configured to, capable of, performed, performable, or operable to establish a dedicated radio bearer for Al-related LPP data for transmission of the new data.BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. These drawings depict only example embodimentsof the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

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

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

[0024] FIG. 2 is an example illustration of the transfer of a long-term evolution (LTE) positioning protocol (LPP) protocol data unit (PDU) in accordance with aspects of the present disclosure.

[0025] FIG. 3 is an example illustration of the transfer of an LPP PDU in accordance with aspects of the present disclosure.

[0026] FIG. 4 is an example illustration of a new radio (NR) Positioning Protocol A (NRPPa) PDU transfer case in accordance with aspects of the present disclosure.

[0027] FIG. 5 is an example illustration of a user plane protocol stack in accordance with aspects of the present disclosure.

[0028] FIG. 6 is an example illustration of a control plane protocol stack in accordance with aspects of the present disclosure.

[0029] FIG. 7 is an example illustration of a section of a protocol stack in accordance with aspects of the present disclosure.

[0030] FIG. 8 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0031] FIG. 9 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0032] FIG. 10 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0033] FIG. 11 illustrates a flowchart of method performed by a UE in accordance with aspects of the present disclosure.

[0034] FIG. 12 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0035] In a 3GPP Release 19 (Rell9) artificial intelligence (Al) for air interface work item (WI), a location management function (LMF), such as an LMF entity, may determine a UE location using an Al model operated at the LMF side with inputs (e.g., measurement or assisting information) collected from a UE or a gNB.

[0036] Document 3GPP RP-234039 describes a work item description (WID) on AI / Machine Learning (ML) for New Radio NR air interface, including the following work items:

[0037] Document 3GPP TR 38.843, Technical Specification Group Radio Access Network; Study on Artificial Intelligence (AI) / Machine Learning (ML) for NR air interface, describes: For positioning use cases, when considering LMF-side inference, it is assumed that the long-term evolution (LTE) positioning protocol (LPP) protocol should be applied to the data collected by UE and terminated at LMF, while the NRPPa protocol should be applied to the data collected by gNB and terminated at LMF. While for LMF-side performance monitoring, it is assumed that the LPP protocol should be applied to the data collected by UE and terminated at LMF, while the NRPPa protocol should be applied to the data collected by gNB and terminated at LMF.

[0038] In order to train an LMF-side model, the LMF may initiate an LPP session towards the UE / positioning reference unit (PRU). A UE can be fixed or mobile, where a PRU can have a known position that can be used as a reference, such as to check the position of the UE, can be used to verify an Al model, and can be used for other purposes that employ a known position. The LMF can configure the UE to measure and transmit the required training data, e.g., including positioning measurements and associated label information set via LPP message. In legacy, both uplink (UL) and downlink (DL) LPP messages are transmitted as non-access stratum (NAS) messages piggybacked in UL / DL radio resource control (RRC) messages (UL / DL information transfer messages) transmitted by signalling radio bearer (SRB)2 / SRB1. Compared to conventional LPP message transmission, the training data collection and report usually has very relaxed latency requirements, since the model offline training is not time-critical and can wait until all data is collected. The following table from document 3GPP Rl-2310638 lists the latency requirements for the other AI / ML-related data used at different stages of the LCM procedure.

[0039] As can be seen from the table, the transmission of the data collection for model training is not time-critical as already mentioned. However, the transmission of the data collection for performance monitoring has a strict latency requirement similar to real-time communication. For the latency requirement of data used for inference, no conclusive agreements have been reached so far. As can be seen, the latency requirement of the AI / ML-related data collection reporting varies depending on the LCM purpose.

[0040] Therefore, using SRB 1 / 2 for the transmission of LPP messages carrying AI / ML-related data is not very efficient from a radio resource efficiency perspective, e.g., using a high-priority SRB for the transmission of low-priority / delay-tolerant data like data collection for model training is not efficient.

[0041] For example, for an AI / ML positioning use case (LMF-side model), the LMF may initiate a LPP session towards the UE / PRU and can configure the UE to measure and transmit the required data, e.g., for model training, inference, performance monitoring via LPP message. In legacy, both UL and DL LPP messages are transmitted as a NAS message piggybacked in UL / DL RRC messages (UL / DL information transfer messages) transmitted by SRB2 / SRB1. Compared to conventional LPP message transmission, AI / ML-related data collection reports have different QoSrequirements / latency requirements, e.g., the transmission of the data collection for model training is not time-critical, whereas transmission of the data collection for performance monitoring has strict latency requirements similar to real-time communication. Essentially the latency requirement of the AI / ML related data collection reporting varies depending on the LCM purpose. Therefore, using SRB 1 / 2 for the transmission of LPP messages carrying AI / ML-related data is not very efficient from a radio resource efficiency perspective, e.g., using a high-priority SRB for the transmission of low-priority / delay-tolerant data like data collection for model training is not efficient. This may lead to a situation where it may delay the transmission of more important RRC messages e.g., for RRC reconfiguration or RRC reestablishment, e.g., if we allow transmitting of data collection messages which are del y-tol erant (e.g., data collection for offline model training which is considered as best effort) in the same SRB 1 / 2.

[0042] At least some embodiments provide several solutions for an efficient protocol operation using multiple radio bearer configurations or a radio bearer associated with multiple logical channels (LCHs) for the transmission of different types of Al / ML data, e.g., data for a different AI / ML LCM purpose. The different types of AI / ML Life cycle management procedures considered throughout this disclosure include training data collection, inference, performance monitoring, model transfer / delivery, and other AI / ML Life cycle management procedures. As will be described later below, these solutions for an efficient protocol operation using multiple radio bearer configurations or a radio bearer associated with multiple LCHs can be applied for other transmissions and purposes.

[0043] At least one embodiment provides for transmission of the AI / ML-related data on a new (dedicated) radio bearer which is associated with multiple RLC entities / LCHs, each of the LCHs accommodating the different QoS requirements of the different types of data for the purposes of AI / ML operations, e.g., data for different LCM purposes like model training, inference, performance monitoring. Using different LCHs for the transmission of different types of AI / ML- related data ensures that the data is treated with a different QoS on the air interface tailored to the QoS requirements. Several implementations can allow for distinguishing the different types of data with different QoS requirements in Layer 2 procedures like buffer status reporting and PDCP discarding.

[0044] For example, a dedicated radio bearer used for AI / ML data reporting associated with a plurality of LCHs can accommodate the different QoS / latency requirements of the type of A I / ML data for different LCM purposes, such as data collection for model training, inference, performance monitoring, model transfer. The PDCP can perform the packet routing to RLC entities based on information associated with a PDCP SDU. The information can be or can be included in a tag, label, priority field, and / or other types of information that can identify the priority / type of data.

[0045] Embodiments can also provide for an LMF to configure gNB to establish a radio bearer for Al / ML-related LPP reports from the UE. QoS information for the different types of data / LCM purposes can be signalled to the gNB as part of assistance information. Based on the received assistance / QoS information the gNB can establish a radio bearer associated with multiple RLC entities.

[0046] Embodiments can further provide for a PDCP entity of the dedicated radio bearer configured with multiple PDCP discard timers to accommodate the different latency requirements of the data transmitted over the dedicated radio bearer. For example, data for performance monitoring can have a shorter PDCP discard timer value compared to data for model training.

[0047] Embodiments can provide for prioritization of high priority / delay-critical data over lower priority / delay-tolerant data of the dedicated radio bearer in a case of congestion. The UE / PDCP can discard lower-priority data in case of congestion to free up resources for the high- priority / delay-critical data. The priority can be determined based on the info / priority / tag associated with a PDCP SDU.

[0048] Embodiments can provide for buffer status reporting for a dedicated radio bearer associated with multiple RLC entities / LCHs. The priority of the PDCP data can be determined based on the priority of the LCHs the PDCP SDU is mapped / routed to.

[0049] Currently, a UE can map the AI / ML-related LPP data to the SRB 1 / 2. This may lead to a situation where it may delay the transmission of more important RRC messages e.g., for RRC reconfiguration or RRC reestablishment, e.g., if we allow transmitting of data collection messages which are delay-tolerant (e.g., data collection for offline model training which is considered as best effort) in the same SRB 1 / 2. By using a dedicated radio bearer that is associated with different LCHs / RLC entities, it can be ensured that the AI / ML-related data is transmitted in accordance with their respective QoS requirements.

[0050] Reference is made herein to receiving, transmitting, or communicating data or information, such as signaling communication resources and / or communications that are transmitted or received between devices. It is to be appreciated that other terms may be used interchangeably with communicating, such as signaling, transmitting, receiving, outputting, forwarding, retrieving, obtaining, and so forth. Similarly, other terms may be used interchangeably with transmitting (e.g., communicating, signaling, outputting, forwarding, and so forth), and other terms may be used interchangeably with receiving (e.g., communicating, retrieving, obtaining, and so forth).

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

[0052] FIG. 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a network 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a fourth-generation (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 NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be one of, or a combination of, a 4G network, a 5G network, a Third Generation Partnership Project (3GPP)-based network, one or more of a future generation network (6G, etc.), and / or one or more of any other suitable radio access technology, wireless access technology, and / or wired access technology, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, a Wireless Local Area Networks (WLAN), a satellite communications network, high-altitude platform network, the Internet, and / or other communications networks. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support various multiple access technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), etc.

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

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

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

[0056] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 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.

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

[0058] The network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The 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 NE 102 associated with the network 106.

[0059] The network 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a PDU session, or the like) with the network 106 via an NE 102. The network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the network 106 (e.g., one or more network functions of the network 106).

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

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

[0062] 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.

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

[0064] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data, etc.). For example, communications traffic can include user data, control information, and other communications traffic. The control information can be used for establishing and controlling communications that transmit and receive the user data, such as in packets, in physical shared channels, in data regions of subframes, and in other communications.

[0065] In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

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

[0067] A list of at least some abbreviations above and at least some other abbreviations relevant to at least some embodiments of the present disclosure is provided at the end of this detailed description for ease of reference.

[0068] FIG. 2 is an example illustration of the transfer of an LPP PDU between an LMF 208 and a UE 202 via an NG RAN Node 204 and an access and mobility management function (AMF) 206 in a network-triggered case 200 in accordance with aspects of the present disclosure. FIG. 3 is an example illustration of the transfer of an LPP PDU between the LMF 208 and the UE 202 via the NG RAN Node 204 and the AML 206 in a UE-triggered case 300 in accordance with aspects of the present disclosure. These two cases 200 and 300 may occur separately or as parts of a single more complex operation. Steps 210 to 216 may occur before, after, or at the same time as steps 302 to 308. Steps 210 to 216 and 302 to 308 may also be repeated.

[0069] Steps 210 to 216 of the network-triggered case 200 are triggered when the LMF 208 needs to send an LPP message to the UE 202 as part of some LPP positioning activity. The LMF 208 then invokes the Namf_Communication_NlN2MessageTransfer service operation at 210 towards the AMF 206 to request the transfer of an LPP PDU to the UE 202. The service operation includes the LPP PDU together with the location services (LCS) correlation identifier (ID) in the N1 Message Container as defined in TS 29.518

[0028] , where

[0028] identifies the version number.

[0070] At 212, if the UE 202 is in connection management (CM)-IDLE state (e.g., if the NG connection was previously released due to data and signalling inactivity), the AMF 206 initiates a network-triggered service request as defined in TS 23.502

[0026] in order to establish a signalling connection with the UE 202 and assign a serving NG-RAN Node 204.

[0071] At 214, the AMF 206 includes the LPP PDU in the payload container of a DL NAS Transport message, and a Routing Identifier identifying the LMF 208 in the Additional Information of the DL NAS Transport message defined in TS 24.501

[0029] . The AMF 206 then sends the DL NAS Transport message to the serving NG-RAN Node 204 in a next-generation application protocol (NGAP) DL NAS Transport message defined in TS 38.413

[0030] . The NGAP can be employed for both the N 1 interface between the UE 202 and the access network (AN) and the N2 interface between different AN nodes. The AMF 206 need not retain state information for this transfer; it can treat any response in step 306 below as a separate non-associated transfer. At 216,the NG-RAN Node 204 forwards the DL NAS Transport message to the UE 202 in an RRC DL Information Transfer message.

[0072] Steps 302 to 308 of the UE-triggered case 300 are triggered when the UE 202 needs to send an LPP PDU to the LMF 208 as part of some LPP positioning activity. At 302, if the UE 202 is in CM-IDLE state, the UE 202 instigates a UE-triggered service request as defined in TS 23.502

[0026] in order to establish a signalling connection with the AMF 206 and assign a serving NG-RAN Node 204.

[0073] At 304, the UE 202 includes the LPP PDU in the payload container of a UL NAS Transport message, and the Routing Identifier, which it can receive in step 216, in the Additional Information of the UL NAS Transport message defined in TS 24.501

[0029] . The UE 202 then sends the UL NAS Transport message to the serving NG-RAN Node 204 in an RRC UL Information Transfer message.

[0074] At 306, the NG-RAN Node 204 forwards the UL NAS Transport Message to the AMF 206 in an NGAP Uplink NAS Transport message. At 308, the AMF 206 invokes the Namf_Communication_NlMessageNotify service operation towards the LMF 208 indicated by the Routing Identifier received in step 306. The service operation includes the LPP PDU received in step 306 together with the LCS Correlation ID in the N 1 Message Container as defined in TS 29.518

[0028] ,

[0075] FIG. 4 is an example illustration of a NRPPa PDU transfer case 400 between the LMF 208 and the NG-RAN Node 204 to support the positioning of a particular UE 202 in accordance with aspects of the present disclosure. Steps 402 to 406 are triggered when the LMF 208 needs to send an NRPPa message to the serving NG-RAN Node 204 for a target UE 202 as part of an NRPPa positioning activity. The LMF 208 then invokes the Namf_Communication_NlN2MessageTransfer service operation towards the AMF 206 at 402 to request the transfer of an NRPPa PDU to the serving NG-RAN Node 204 for the UE 202. The service operation includes the NRPPa PDU together with the LCS Correlation ID in the N2 Message Container as defined in TS 29.518

[0028] .

[0076] At 404, if the UE 202 is in CM-IDLE state (e.g., if the NG connection was previously released due to data and signalling inactivity), the AMF 206 performs a network-triggered service request as defined in TS 23.502

[0026] in order to establish a signalling connection with the UE 202 and assign a serving NG-RAN Node 204.

[0077] At 406, the AMF 206 forwards the NRPPa PDU to the serving NG-RAN Node 204 in an NGAP DL UE Associated NRPPa Transport message over the NG signalling connection corresponding to the UE 202 and includes the Routing ID related to the LMF 208. The AMF 206 need not retain state information for this transfer, e.g., it can treat any response in step 408 as a separate non-associated transfer.

[0078] Steps 408 and 410 are triggered when a serving NG-RAN Node 204 needs to send an NRPPa message to the LMF 208 for a target UE 202 as part of an NRPPa positioning activity. At 408 the NG-RAN Node 204 sends an NRPPa PDU to the AMF 206 in an NGAP Uplink UE Associated NRPPa Transport message and includes the Routing ID received in step 406.

[0079] At 410, the AMF invokes the Namf_Communication_N2InfoNotify service operation towards the LMF 208 indicated by the Routing ID received in step 408. The service operation includes the NRPPa PDU received in step 408 together with the LCS Correlation ID in the N2 Info Container as defined in TS 29.518

[0028] . Steps 402 to 410 may be repeated.

[0080] According to possible embodiments, an LMF can configure a UE / PRU to report any of (but not limited to) the following data periodically, one-time (also referred to as on-demand), and / or event-triggered manner: measurement types, label types, and assistance information data. The data can be used by LMF for the different AI / ML operations of the LCM.

[0081] Measurement types of data can include UL-based channel impulse response (CIR) / power delay profile (PDP) / delay profile (DP) and / or DL-based CIR / PDP / DP. Measurement types of data can also include DL- positioning reference signal (PRS) reference signal received power (RSRP) / DL-PRS RSRP / UL sounding reference signal (SRS) RSRP / UL SRS RSRP / DL- reference signal time difference (RSTD) / UE Rx-Tx time difference / gNB Rx-Tx time difference / UL-relative time of arrival (RTOA) / UL-angle of arrival (AoA) / DL-angle of departure (AoD) / synchronization signal block (SSB) RSRP / channel state information (CSI)-reference signal (RS) RSRP, DL received signal code power (RSCP), DL reference signal carrier phase difference (RSCPD), and / or UL RSCP. Measurement types of data can also include other measurement information.

[0082] Label types of data can include location coordinates and / or timing estimation. Label types of data can also include at least one line-of-sight (LOS) / non-line-of-sight (NLOS) indicator including soft indicator in terms of probability of LOS / NLOS, e.g., [0, 0.1 , 0.2, ...1 ] and / or hardindicator in terms of a binary Boolean indicator LOS or NLOS, e.g., [True(LOS), False (NLOS)]. Label types of data can include other label information. Assistance information types of data can include time stamp information, measurement / label quality indicator information, RS configuration information, and / or other assistance information.

[0083] In disclosed embodiments, the (dedicated radio) bearer can be a radio bearer different from SRB1 / SRB2 / SRB3. It can be a new SRB configured by a gNB and / or a dedicated data radio bearer (DRB) configured by a gNB. Embodiments can provide for establishing multiple dedicated bearers to accommodate the different quality of service (QoS) requirements. Embodiments can also provide for mapping to different radio bearers based on the type of message / priority of the message. Embodiments can further provide for establishing one dedicated radio bearer with multiple LCHs, where packet routing in the PDCP layer to the different associated LCHs / RLC channels can be done based on a type of message / priority of the message.

[0084] According to a possible embodiment, a UE can be configured with a radio bearer that is associated with a plurality of LCHs, e.g., PDCP entity of the radio bearer is associated with multiple LCHs. The different LCHs are configured to accommodate the different / multiple QoS requirements of the data that is expected to be transmitted on the radio bearer. In one example, a QoS requirement may be characterized by one or more of the following types of information including resource type (e.g., Guaranteed Bit rate (GBR), delay critical GBR, non-GBR), priority level, packet delay budget, packet error rate, averaging window, and / or maximum data burst volume (MDBV). In another example, separate such QoS requirements may be defined depending on the LCM process / stage, e.g., model training, inference, performance monitoring, and / or model transfer. In one implementation of the embodiment, the configured radio bearer carries LPP messages. In one example, the LPP messages are comprised of AI / ML-related data (for instance for positioning), e.g., data collection reports for different LCM purposes, e.g., model training, inference, performance monitoring, and / or model transfer. According to one implementation of the embodiment, the PDCP layer of the radio bearer performs the routing of PDCP PDUs to the associated RLC entities based on some information associated with a PDCP SDU. In one example the radio bearer is a data radio bearer or a signalling radio bearer. According to one exemplary implementation, the information used for routing is a tag / label, e.g., this tag / label is used to identify the type of data or LCM purpose that is carried within the SDU, e.g., data collection report for training, inference, performance monitoring, and / or model transfer. In one example, the information that is used for the routing in thePDCP layer is a priority information associated with PDCP SDUs. In one example, the information based on which the routing of PDCP PDUs is done, i.e., tag / label identifying the LCM purpose or a priority value, is carried in some higher layer header, e.g., LPP PDU carries some header identifying the LCM purpose. In an extended implementation, a priority value may further be associated with an LCM purpose, e.g., for a decreasing order of priority, where data for performance monitoring is associated with a highest priority value of 1 , training / inference data has a priority value of 2, AI / ML model data transfer has the lowest priority value of 3. Such a mapping of the priority value and LCM purpose may also be specified. The assumption for this embodiment is that the PDCP layer is aware of such information associated with a PDCP SDU, e.g., type of data / LCM purpose. In one example the information is provided to the UE access stratum (AS) by inter-layer communication. It is basically up to the UE implementation how the information, e.g., tag / label / priority identifying the LCM purpose, is provided to the UE PDCP layer.

[0085] In one example the PDCP layer is provided with a mapping configuration, specifying the mapping between a tag / label / data type or priority and a RLC entity / RLC bearer. In one example the PDCP layer of the UE uses the mapping information for the routing of PDCP PDUs to the associated RLC entities.

[0086] According to one implementation of the embodiment, the priority information or the tag / label associated with a message / SDU is explicitly configured by LMF. For example, in the LPP message from LMF configuring the data collection report (e.g., LPP RequestLocationlnformation or LPP ProvideAssistanceData message), an information element (IE) is used to indicate the priority level or tag / label of the corresponding report message transmission. Such information is used for the data routing at the PDCP layer and other Layer 2-related functionalities, such as outlined in the following embodiments.

[0087] According to another implementation of the embodiment, the priority level / label of an LPP message that is e.g., used for data routing at the PDCP layer is specified in the standard. For example, the LPP message from UE to LMF containing data (e.g., measurement result) for offline AI / ML training is considered to be lower priority than other LPP messages, e.g., data for performance monitoring, capability exchange, assistance data exchange, and / or location information exchange.

[0088] In another example, an LPP layer, such as an LPP entity, in the UE determines the priority / label / tag of a UL LPP message. In one example, the UE LPP layer will deliver the UL LPP message with the corresponding associated priority information / label / tag to the PDCP entity / radio bearer. In another example, the UE LPP layer will deliver the UL LPP message together with the associated priority information which is used for packet routing as a NAS PDU to the RRC layer.

[0089] According to one example, UE is configured with a radio bearer, such as a dedicated radio bearer, for UL LPP message transmission that is associated with two LCHs / RLC entities. One LCH is configured with a high LCH priority, whereas the other LCH is configured with a lower LCH priority. Other RLC / LCH parameters may be also differently configured for the two RLC entities / LCHs, e.g., RLC mode, timer settings, etc. In one example a UE PDCP entity routes the high-priority LPP messages, e.g., data for performance monitoring, to the high-priority RLC entity / LCH since the data is delay-critical and should be treated hence with a high priority within the logical prioritization procedure (LCP). Low-priority data with more relaxed QoS requirements are mapped to the low(er) priority RLC entity / LCH, e.g., data collection for offline training.

[0090] Transmitting the different types of (LPP) messages via different LCHs allows a different QoS treatment over the air interface. Lor example, only for a specific type of high-priority, delay- critical messages, e.g., performance monitoring, a dedicated scheduling request (D-SR) on PUCCH may be configured. According to one implementation of the embodiment, an SR configuration is only mapped to high-priority LCH out of the plurality of LCHs associated with the PDCP entity of the radio bearer.

[0091] It should be noted that even though the embodiments are mainly described for the UL direction, the procedures / techniques described in the various embodiments can be equally applicable to the DL direction.

[0092] According to a possible embodiment, the LME informs a gNB about the need to establish a radio bearer, such as a dedicated radio bearer, for the transmission of AI / ML-related LPP data collection and reports, e.g., data collection for training, inference, performance monitoring, and / or model transfer. The gNB, upon reception of such message / information, configures a corresponding radio bearer for UE to transmit the AI / ML-related LPP data collection report(s) taking into account the corresponding QoS requirements. In one implementation of theembodiment, the LMF configures the UE to start data collection and reporting over LPP, which is expected to be transmitted via the established dedicated radio bearer.

[0093] According to one implementation of the embodiment, the LMF requests a gNB to configure / establish a new (dedicated) radio bearer or multiple dedicated radio bearers for LPP data collection and reporting for a particular UE / PRU via an NRPPa message. In one example the bearer setup request includes some QoS-related information which enables gNB to configure the bearer(s) accordingly. Such QoS-related information may be comprised of latency and / or reliability requirements of the data to be transmitted via the radio bearer. In one example a plurality of QoS requirements may be provided to the gNB, denoting the QoS requirements of the different types of LCM data, e.g., data collection for training, inference, performance monitoring, and / or model transfer. In one example the QoS information is comprised of multiple QoS flow identifiers (QFI).

[0094] According to one implementation of the embodiment, a gNB is provided with a number of different tags / labels / data types supported by the radio bearer. In one example, information on the number of different tags / labels used for a QoS flow / radio bearer is signalled within Al assistance information provided to the RAN by the core network. In one specific implementation, LMF requests gNB to set up a plurality of dedicated radio bearer(s) or one dedicated radio bearer associated with multiple LCHs in order to accommodate the different QoS requirements of the AI / ML-related data, e.g., data collection for training, inference, model performance monitoring, and / or model transfer (e.g., different LCM purpose / type of AI / ML data). Based on the provided information, the gNB can determine the required number of LCHs for the case that one radio bearer is associated with multiple RLC channels / LCHs and e.g., the corresponding LCH parameters e.g., RLC mode, timers, etc.

[0095] According to one implementation of the embodiment, the LMF generates a (UE- associated or non-UE-associated) NRPPa message that includes a request to establish dedicated radio bearer(s) for the transmission of AI / ML-related LPP data. This can be included in a new NRPPa message or by re-using the legacy NRPPa messages, e.g., an NRPPa Positioning Information Request message that is sent to the AMF. As mentioned above, the NRPPa message may further contain information related to QoS requirements of the LPP data that is to be transmitted on the radio bearer(s). In one example, the request for setting up a dedicated bearer includes some QoS-related information that enables the gNB to configure the bearer(s) accordingly.In one example such QoS-related information may be comprised of a plurality of latency and / reliability requirements for the different types of LPP data, enabling gNB to e.g., configure multiple RLC entities / LCH associated with the PDCP entity of the radio bearer or to configure the RLC mode or certain timers (PDCP / RLC timer). The AMF forwards the received NRPPa PDU to the serving gNB of that UE in an NGAP message.

[0096] After the gNB receives the NRPPa message indicating the request to establish dedicated radio bearer(s) for a particular UE, the gNB is expected to configure the UE with a single radio bearer associated with multiple LCHs or multiple dedicated radio bearers which can be used for LPP data collection report. The dedicated radio bearer(s) can be configured via an RRC reconfiguration procedure.

[0097] According to another implementation of the embodiment, LMF initiates an LPP procedure and sends an LPP message (e.g., LPP RequestLocationlnformation or LPP ProvideAssistanceData) to configure the UE to start AI / ML-related data collection and reporting over LPP and includes in the same message from LMF to AMF that conveys the LPP message as LPP PDU the request to the gNB to establish dedicated radio bearer(s). In one example, LMF includes in the message (e.g., Namf_Communication_NlN2MessageTransfer) from LMF to AMF that conveys the LPP message as an LPP PDU a request to establish dedicated radio bearer(s) for the transmission of the LPP messages / PDUs from the UE.

[0098] The Namf -Communication J\[lN2MessageTransfer message may further contain information related to the QoS requirements of the LPP data (data collection for training, inference, performance monitoring, etc.). In one example the request for establishing dedicated bearer(s) includes some QoS-related information that enables the gNB to configure the bearer(s) accordingly. In one example such QoS-related info may be comprised of a plurality of latency and / reliability requirements for the different types of LPP data, enabling the gNB to e.g., configure multiple RLC entities / LCHs associated with the PDCP entity of the radio bearer or to configure the RLC mode or certain timers (PDCP / RLC timer).

[0099] The AMF will then forward the LPP message / PDU as well as the request and related QoS information (if provided) to gNB via NGAP procedure (e.g., NGAP DL NAS Transport). In response to the reception of the NGAP message containing LPP PDU and the request, the gNB will deliver the LPP message to UE / PRU conveyed in an RRC message (i.e., RRCDLInformationTransfer message). The gNB is also expected to configure UE with dedicated radio bearer(s) which are used for LPP data collection reporting in accordance with the signaled QoS requirements.

[0100] According to a possible embodiment, PDCP control PDUs of a PDCP entity associated with multiple RLC entities are delivered from the PDCP layer to the RLC entity having the highest priority LCH. In another implementation of the embodiment, PDCP control PDUs can be carried via any of the LCHs / RLC entities associated with the common PDCP entity.

[0101] According to a possible embodiment, a PDCP entity is configured with multiple PDCP discard timer / PDCP discard timer configurations. According to one implementation of the embodiment, each of the PDCP discard timers is associated with a specific LCM purpose, e.g., data collection for training, inference, performance monitoring, and / or model transfer. Since there may be different latency requirements for data of different LCM purposes and respectively different types of LPP message transmitted via the radio bearer / PDCP entity, different PDCP discard timers / values are applied for different types of messages. In one example the PDCP entity determines the type of data (LCM purpose) that is carried in a PDCP SDU when arriving from a higher layer at the PDCP entity and applies the corresponding PDCP discard timer, e.g., the PDCP entity starts the corresponding PDCP discard timer. In one exemplary implementation, the PDCP entity determines the corresponding PDCP discard timer that is to be used for the PDCP SDU based on the flag / label / priority associated with a PDCP SDU identifying the type of data / LCM purpose. According to one implementation of the embodiment, a mapping between the message type / flag / label / priority identifying the type of data carried in a PDCP SDU and the corresponding PDCP discard timer configuration is configured for the PDCP entity.

[0102] The following table shows an exemplary implementation of the above embodiment in TS38.331, e.g., PDCP-Config IE has a new field configuring multiple PDCP discard timers (one for each LCM purpose / message type):

[0103] For example, the following information can be added:

[0104] According to a possible embodiment, the UE discards PDCP SDUs / PDUs associated with a specific predefined label / message type / tag / priority in case of congestion in order to free up radio resources with the aim of reducing / eliminating the congestion. According to one implementation of the embodiment, the PDCP layer (transmitting entity) discards PDCP SDUs / PDUs that carry a specific type of message - data for a specific LCM purpose as identifiedby the associated label / tag - being of lower priority / importance in order to free up radio resources for the transmission of data of higher importance / priority when the air interface is congested. In order to avoid a situation where data of lower importance / priority pending in UE’s buffer is hindering the transmission of higher priority / importance data, UE should according to this embodiment discard the low priority data, e.g., delay non-critical data, and use the radio resources for the transmission of the high priority - e.g., delay-critical - PDUs / SDUs in order to reduce the congestion level on the air interface. In one example, the NW configures the UE / PDCP entity with the type of data that should be discarded in the case of congestion. In one specific exemplary implementation, the NW configures / signals the UE / PDCP entity the list of tag(s) / label(s) / priorities that should be treated as low priority during congestion and corresponding PDCP PDUs / SDUs associated with such label / tag should be discarded.

[0105] According to a possible embodiment, a buffer status report (BSR) is triggered based on new data becoming available for transmission and this data has a higher priority than the priority of any other data that is available for transmission. According to one implementation of the embodiment, the priority of the data becoming available for transmission, e.g., arriving in the PDCP, is determined based on the type of message / label / tag associated with the data. In one example the UE determines the priority of the data (e.g., PDCP SDU) based on the mapping between the label / tag associated with the data, e.g., PDCP SDU, and the associated LCH priority. In one example the priority of the data for the purpose of BSR triggering / reporting is the priority of the LCH to which a PDCP SDU is / will be routed based on the message type / label / tag associated with the data.

[0106] According to a possible embodiment, a new mapping / association between a tag / label associated with a PDCP SDU and a configured grant (CG) configuration is configured. For cases when PDCP SDUs / PDUs associated with different labels / tags identifying the type of message carried in the PDCP SDU / PDU are carried over a single radio bearer, a new mapping configuration can be provided that allows a finer granularity than the current LCH to CG mapping. According to one implementation of the embodiment, the type of message identified by the label / tag associated with an SDU / PDU is an LCM purpose, e.g., data collection for training, inference, performance monitoring, and / or model transfer. The data for the different LCM purposes may be of different sizes (transport block sizes) and may also have different periodicities (if the traffic is periodic). This new mapping configuration is in one example considered during the LCP procedure, e.g., new sub-LCH restriction is applied during LCH selection, e.g., LCH is only considered during LCP for a configured grant allocation when data of this LCH has an associated message type / label that is in the list of allowed message types / labels configured for the corresponding CG configuration. In one example, a new configuration is introduced, e.g., RRC configuration, that configures for a CG configuration the list of supported / allowed message types / labels. In another example, a new configuration is introduced, e.g., RRC configuration, that controls per message type / label the list of allowed CG configurations. In yet another example, a new configuration, e.g., RRC configuration, configures for an LCH, the mapping between a message type / label supported by the LCH and the list of allowed CG configurations, e.g., here the mapping between message type / label and CG configuration(s) is LCH-specific.

[0107] According to a possible embodiment, LPP messages carrying delay critical ALML related data, e.g., data for performance monitoring, are transmitted on SRB1 / SRB2, whereas other AI / ML related LPP data that is not time critical is transmitted via another radio bearer, e.g., data radio bearer or another SRB, configured according to the more relaxed QoS requirements. The other radio bearer may be configured with multiple RLC entities / LCHs as outlined in the above embodiments.

[0108] FIG. 5 is an example illustration of a user plane protocol stack 500 in accordance with aspects of the present disclosure. The protocol stack 500 can include a service data adaptation protocol (SDAP) layer, a PDCP layer, a RLC layer, a medium access control (MAC) layer, and a physical (PHY) layer. The layers can be implemented in a UE 502 and in a gNB 504. Certain layers can also be considered sublayers. For example, Layer 2 of NR protocol stack can be split into the following sublayers: MAC, RLC, PDCP, and SDAP. In the present disclosure, some sublayers may be referred to as layers. The PHY layer can offer to the MAC sublayer transport channels. The MAC sublayer offers to the RLC sublayer LCHs. The RLC sublayer offers to the PDCP sublayer RLC channels. The PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to the 5GC QoS flows. The PDCP sublayer operates between the RLC sublayer and the SDAP sublayer for the user plane protocol stack 500.

[0109] FIG. 6 is an example illustration of a control plane protocol stack 600 in accordance with aspects of the present disclosure. The protocol stack 600 can include a NAS layer, a RRC layer, a PDCP layer, an REC layer, a MAC layer, and a PHY layer. The RRC, PDCP, REC, MAC, andPHY layers can be implemented in the UE 602 and in the gNB 604. The NAS layer can be implemented in the UE 602 and in an AMF 606 of a network. The PDCP layer operates between the RLC layer and the RRC layer for the control plane protocol stack 600.

[0110] FIG. 7 is an example illustration of a section of a protocol stack 700 in accordance with aspects of the present disclosure. The section of the protocol stack 700 only includes selected elements of a protocol stack and other elements are omitted for ease of illustration. The described layers of the protocol stack 700 can be considered sublayers of Layer 2. The protocol stack 700 can include a PDCP layer 702. The PDCP layer 702 can be a functional layer within the protocol stack 700, responsible for providing various data transmission-related functionalities. The PDCP layer 702 can operate between the RLC layer 706 and the SDAP or RRC layer 720 depending on the protocol stack, such as the user plane protocol stack with a SDAP layer or the control plane protocol stack with the RRC layer. The PDCP layer 702 can perform tasks such as header compression and ciphering.

[0111] The PDCP layer 702 can include at least one PDCP entity 704. The PDCP entity 704 can represent an instance of the PDCP layer 702 running on a specific communication link within the network, handling PDCP-related functions for that link. There can be one radio bearer 710 per PDCP entity 704. The radio bearer 710 can be an SRB or a data radio bearer DRB. The PDCP layer 702, such as the PDCP entity 704, can perform routing of data based on the data type, priority of the data type, label of the data type, and / or other information about data received for the radio bearer 710.

[0112] The stack 700 can include a RLC layer 706 including a plurality of RLC entities 708, such as RLC entities 708-1 and 708-2. The PDCP entity 704 of the PDCP layer 702 can be associated with the plurality of RLC entities 708. Each RLC entity 708 can have a priority level. For example, the RLC entity 708-1 can have a high priority level and the RLC entity 708-2 can have a low priority level. There can be one LCH, such as one of LCHs 714-1 and 714-2, per RLC entity 708. Each LCH of the plurality of LCHs 714 can be configured with a different LCH priority and other LCH parameters which are configured in the IE LogicalChannelConfig. For example, LCH 714-1 can have a high priority and LCH 714-2 can have a low priority.

[0113] An RLC entity 708 can represent an instance of the RLC layer 706 running on specific communication links handling RLC-related functions. An RLC bearer can encompass a RLC entity708 and a corresponding LCH 714 which is the interface / channel between a RLC entity 708 and a corresponding MAC entity 716 of MAC layer 718. The RLC bearer configuration is comprised of the respective RLC entity 708 configuration and the LCH 714 configuration. A radio bearer 710 can provide the physical link for data transmission, while LCHs 714 can provide a way of organizing and multiplexing different types of data and control information within that physical link.

[0114] In operation according to a possible embodiment, the PDCP layer 702 can receive new data for a radio bearer 710. For example, the PDCP entity 704 can receive the new data from the SDAP / RRC layer 720, which had received the new data from higher layers, such as an internet protocol (IP) layer. The new data can correspond to a data type of a plurality of data types. The PDCP layer 702, such as the PDCP entity 704, can identify a priority level for the data type, where the identified priority level can be one of a plurality of priority levels, such as a high priority level, a low priority level, and / or other priority levels in between. The PDCP layer 702 can route the new data to an RLC entity 708 that corresponds to the identified priority level. For example, the PDCP layer 702 can route the new data on a respective RLC channel 712 of a plurality of RLC channels, such as RLC channels 712-1 and 712-2 to a corresponding RLC entity 708.

[0115] Embodiments can provide for different RLC bearers, such as different RLC entities and LCHs, with different priorities. Embodiments can also treat data in the same radio bearer with different priorities, such as QoS requirements, differently and can route the data based on its priority level.

[0116] While some embodiments are described in the context of LMF, embodiments can also be applied to other data types with different priority levels. For example, embodiments can relate to LMF data types (that can include LMF assistance data), beam prediction data types, CSI compression data types, CSI prediction data types, and other purposes relating to data with different priority levels. In an LMF embodiment, a radio bearer can carry LPP messages including Al-related new data.

[0117] FIG. 8 illustrates an example of a UE 800 in accordance with aspects of the present disclosure. The UE 800 may include at least one processor 802, at least one memory 804, at least one controller 806, and at least one transceiver 808. The processor 802, the memory 804, the controller 806, the transceiver 808, various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as describedherein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

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

[0119] The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, a field programmable gate array (FPGA), or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer- readable instructions stored in the memory 804 to cause the UE 800 to perform various functions of the present disclosure.

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

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

[0122] In some implementations, the UE 800 may include at least one transceiver 808. In some other implementations, the UE 800 may have more than one transceiver 808. The transceiver 808may represent a wireless transceiver. The transceiver 808 may also represent and / or include one or more other wireless and or wired communication interfaces, such as a network interface, a universal serial bus (USB) port, an optical transceiver, and / or any other transceiver, interface, port, communication interface, etc. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

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

[0124] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 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 modulation techniques such as amplitude modulation (AM), frequency modulation (FM), digital modulation schemes like phaseshift keying (PSK) or quadrature amplitude modulation (QAM), and / or any other modulation techniques. The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0125] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to or operable to cause the UE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the UE 800 in accordance with the examples as disclosed herein.

[0126] The UE 800 may be configured to or operable to support a means for routing data for a radio bearer. In operation according to a possible embodiment, the at least one processor 802 can beconfigured to or operable to cause the UE 800 to receive, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types. The at least one processor 802 can be configured to or operable to cause the UE 800 to identify a priority level for the data type, where the identified priority level can be one of a plurality of priority levels. The at least one processor 802 can be configured to or operable to cause the UE 800 to route the new data to a RLC entity that corresponds to the identified priority level. The RLC entity can be a RLC entity of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

[0127] In a possible embodiment, the new data can be a PDCP SDU. The at least one processor 802 can be configured to or operable to cause the UE 800 to parse a data information parameter attached to the PDCP SDU to identify the respective priority level for the data type. For example, the data information parameter can identify the data type. An SDU can include the data that is exchanged between different layers of a protocol stack, such as the payload or user data that is transmitted from one layer to another. The SDU can be included in a PDU.

[0128] In a possible embodiment, the UE 800 can be configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity. The at least one processor 802 can be configured to or operable to cause the UE 800 to select the respective RLC entity based on the mapping configuration to route the new data to the respective RLC entity.

[0129] In a possible embodiment, the plurality of priority levels can include different QoS requirements for different stages of an Al LCM procedure. It is noted that Al can include ML. The PDCP entity can be configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels. For example, the discard timer configurations can be associated with respective different stages of the Al LCM procedure. As a further example, the PDCP entity can be configured with multiple PDCP discard timers / PDCP discard timer configurations. According to one implementation of the embodiment, each of the PDCP discard timers can be associated with a specific LCM purpose or with a subset of LCM purposes. When the discard timer expires for a PDCP SDU, the transmitting PDCP entity can discard the PDCP SDU along with the corresponding PDCP Data PDU.

[0130] In a possible embodiment, the data type can be an Al model-related LPP data type. The data type can correspond to an Al positioning model LCM purpose. For example, the data type can be Al positioning model training data type, Al positioning model inference data type, Al positioning model performance monitoring data type, and / or Al positioning model transfer data type. The data type can also correspond to other purposes. For example, the data type can correspond to location determination, beam prediction, CSI compression, CSI prediction, and other purposes relating to data with different priority levels. In a possible embodiment, the data type can relate to different stages of Al procedures.

[0131] In a possible embodiment, the at least one processor 802 can be configured to or operable to cause the UE 800 to use a dedicated radio bearer for Al-related LPP data for transmission of the new data. For example, an LMF informs a gNB about the need to establish a radio bearer, such as a dedicated radio bearer, for the transmission of AI / ML-related LPP data collection and reports, e.g., data collection for training, inference, performance monitoring, and model transfer. Upon reception of such message / information, the gNB configures a corresponding radio bearer for UE 800 to transmit the AI / ML-related LPP data collection report(s) taking into account the corresponding QoS requirements. In one implementation of this embodiment, the LML configures the UE 800 to start data collection and reporting over LPP, which is expected to be transmitted via the established dedicated radio bearer.

[0132] In a possible embodiment, the at least one processor 802 can be configured to or operable to cause the UE 800 to route PDCP control PDUs from the PDCP layer to an RLC entity having a highest priority level of the plurality of RLC entities. Lor example, PDCP control PDUs of a PDCP entity associated with multiple RLC entities are delivered from the PDCP layer to the RLC entity having the highest priority LCH. In another implementation of this embodiment, PDCP control PDUs can be carried via any of the LCHs / RLC entities associated with the common PDCP entity.

[0133] In a possible embodiment, the at least one processor 802 can be configured to or operable to cause the UE 800 to determine whether an air interface is congested. The at least one processor 802 can be configured to or operable to cause the UE 800 to discard data units associated with a lower priority level of the plurality of priority levels based on determining the air interface is congested.

[0134] The data units can be SDUs and / or PDUs. For example, a gNB may not be able to guarantee that a Layer 2 (L2) buffer overflow will never occur. If such overflow occurs, a UE 800 may discard packets in the L2 buffer. The UE 800 discards PDCP SDUs / PDUs associated with a specific predefined label / message type / tag / priority in case of congestion to free up radio resources to reduce / eliminate the congestion. According to one implementation of the embodiment, the PDCP layer (transmitting entity) discards PDCP SDUs / PDUs that carry a specific type of message, data for a specific LCM purpose as identified by the associated label / tag, being of lower priority / importance to free up radio resources for the transmission of data of higher importance / priority when the air interface is congested.

[0135] In a possible embodiment, the priority of the data can be determined for triggering a BSR. The at least one processor 802 can be configured to or operable to cause the UE 800 to determine a priority of the new data for the purpose of buffer status reporting based on a priority of the RLC entity the new data is routed to. The at least one processor 802 can be configured to or operable to cause the UE 800 to ascertain the priority of the new data is higher than a priority of other data available for transmission. The at least one processor 802 can be configured to or operable to cause the UE 800 to trigger a BSR in response to ascertaining the priority of the new data is higher than the priority of the other data available for transmission. The priority of other data available for transmission can be at least one priority of other data available for transmission. For example, the other data can have different priority levels and the new data can have a priority higher than all of the other priority levels. As a further example, a BSR is triggered based on new data becoming available for transmission and this data has a higher priority than the priority of any other data which is available for transmission. According to one implementation of the embodiment, the priority of the data becoming available for transmission, e.g., arriving in the PDCP, is determined based on the type of message / label / tag associated with the data. In one example the UE 800 determines the priority of the data (e.g., PDCP SDU) based on the mapping between the label / tag associated with the data, e.g., PDCP SDU, and the associated LCH priority. In one example the priority of the data for the purpose of BSR triggering / reporting is the priority of the LCH to which a PDCP SDU is / will be routed based on the message type / label / tag associated with the data.

[0136] In a possible embodiment, the new data includes a label identifying the data type. The at least one processor 802 can be configured to or operable to cause the UE 800 to compare the label to a list of labels identifying data types corresponding to at least one configured grant resourceallocation. The at least one processor 802 can be configured to or operable to cause the UE 800 to transmit the new data on a corresponding configured grant allocation based on comparing the label to the list of labels. For example, a new mapping / association between a tag / label associated with a PDCP SDU and a CG configuration is configured. For cases when PDCP SDUs / PDUs associated with different labels / tags identifying the type of message carried in the PDCP SDU / PDU are carried over a single radio bearer, a new mapping configuration can allow a finer granularity than the current ECH to CG mapping. According to one implementation of this embodiment, the type of message identified by the label / tag associated with an SDU / PDU is an ECM purpose, e.g., data collection for training, inference, performance monitoring, and / or model transfer.

[0137] In a possible embodiment, the radio bearer can be an SRB. The at least one processor 802 can be configured to or operable to cause the UE 800 to determine the identified priority level is higher than a priority threshold. The at least one processor 802 can be configured to or operable to cause the UE 800 to transmit the new data on SRB 1 or SRB2 based on the identified priority level being higher than the priority threshold. For example, LPP messages carrying delay critical AI-ML related data, e.g., data for performance monitoring, are transmitted on SRB1 / SRB2, whereas other AI / ML related LPP data that is not time critical is transmitted via another radio bearer, e.g., data radio bearer or another SRB, configured according to the more relaxed QoS requirements. The other radio bearer may be configured with multiple RLC entities / LCHs as outlined in embodiments above. In an implementation, SRB0 is used for transmitting RRC messages via the Common Control Channel (CCCH) LCH, SRB 1 handles both RRC messages and NAS messages before the establishment of SRB2, which operates over the Dedicated Control Channel (DCCH) LCH, SRB2 is used for NAS messages and also operates over the DCCH LCH and has a lower priority than SRB 1 , and SRB3 serves specific RRC messages when the UE 800 is in dual connectivity and operates over the DCCH LCH.

[0138] FIG. 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to perform various operations in accordance with the examples described herein. The processor 900 may include at least one controller 902 configured to perform various operations in accordance with the examples described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906. One or more of thesecomponents may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0139] The processor 900 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 900)) 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).

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

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

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

[0143] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions. For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 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.

[0144] The one or more ALUs 906 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 906 may reside within or on a processor chipset (e.g., the processor 900). In some other implementations, the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900). One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 906 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 906 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 906 to handle conditional operations, comparisons, and bitwise operations.

[0145] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to or operable to support a means for routing data for a radio bearer.

[0146] In operation according to a possible embodiment, the at least one controller 902 can be configured to or operable to cause the processor 900 to receive, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types. The at least one controller 902 can be configured to or operable to cause the processor 900 to identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels. The at least one controller 902 can be configured to or operable to cause the processor 900 to route the new data to a RLC entity that corresponds to the identified priority level. The RLC entity can be an RLC entity of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

[0147] In a possible embodiment, the new data can be a PDCP SDU. The at least one controller 902 can be configured to or operable to cause the processor 900 to parse a data information parameter attached to the PDCP SDU to identify the respective priority level for the data type.

[0148] In a possible embodiment, the processor 900 is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity. The at least one controller 902 can be configured to or operable to cause the processor 900 to select the respective RLC entity based on the mapping configuration to route the new data to the respective RLC entity.

[0149] In a possible embodiment, the plurality of priority levels can include different QoS requirements for different stages of an Al LCM procedure. In a possible embodiment, the PDCP entity is configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels. In other possible embodiments, the at least one controller 902 can be configured to or operable to cause the processor 900 to perform other operations corresponding to the operations performed by the UE 800.

[0150] EIG. 10 illustrates an example of an NE 1000 in accordance with aspects of the present disclosure. The NE 1000 may include at least one processor 1002, at least one memory 1004, at least one controller 1006, and at least one transceiver 1008. The processor 1002, the memory 1004,the controller 1006, the transceiver 1008, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

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

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

[0153] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the NE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1004 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates the 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.

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

[0155] In some implementations, the NE 1000 may include at least one transceiver 1008. In some other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent at least one wireless transceiver and may include other transceivers, such as a wired transceiver, like a network interface. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

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

[0157] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 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 modulation techniques such as AM, FM, or digital modulation schemes like PSK or QAM, and / or any other modulation techniques. The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0158] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the NE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the NE 1000 in accordance with examples as disclosed herein.

[0159] The NE 1000 may be configured to or operable to support a means for routing data for a radio bearer. In operation according to a possible embodiment, the at least one processor 1002 can be configured to or operable to cause the NE 1000 to receive, at a PDCP layer, new data for a radiobearer, where the new data corresponds to a data type of a plurality of data types. The at least one processor 1002 can be configured to or operable to cause the NE 1000 to identify a priority level for the data type, where the identified priority level is one of a plurality of priority levels. The at least one processor 1002 can be configured to or operable to cause the NE 1000 to route the new data to a RLC entity that corresponds to the identified priority level. The RLC entity can be an RLC entity of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

[0160] In a possible embodiment, the new data can be a PDCP SDU. To identify the respective priority level for the data type, the at least one processor 1002 can be configured to or operable to cause the NE 1000 to parse a data information parameter attached to the PDCP SDU.

[0161] In a possible embodiment, the NE 1000 is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity. To route the new data to the respective RLC entity, the at least one processor 1002 can be configured to or operable to cause the NE 1000 to select the respective RLC entity based on the mapping configuration.

[0162] In a possible embodiment, the plurality of priority levels can include different QoS requirements for different stages of an Al LCM procedure. In a possible embodiment, the PDCP entity is configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels.

[0163] In a possible embodiment, the data type can be an Al model-related LPP data type. In a possible embodiment, the at least one processor 1002 is configured to or operable to cause the NE 1000 to establish a dedicated radio bearer for Al-related LPP data for transmission of the new data. In other embodiments, the at least one processor 1002 can be configured to or operable to cause the NE 1000 to perform other operations corresponding to the operations performed by the UE 800.

[0164] FIG. 11 illustrates a flowchart 1100 of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions. Each operation of the flowchart 1100 may beperformed in accordance with the examples described herein. In some implementations, aspects of particular operations may be performed by the UE 800 as described with reference to FIG. 8.

[0165] At 1102, the method can include receiving, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types. At 1104, the method can include identifying a priority level for the data type, where the identified priority level is one of a plurality of priority levels. In a possible embodiment, the plurality of priority levels can include different QoS requirements for different stages of an Al LCM procedure. In a possible embodiment, the new data can be in a PDCP SDU and identifying the respective priority level for the data type can include parsing a data information parameter attached to the PDCP SDU to identify the respective priority level.

[0166] At 1106, the method can include routing the new data to a radio link control (RLC) entity that corresponds to the identified priority level. In a possible embodiment, the UE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity. Routing the new data to the respective RLC entity can include selecting the respective RLC entity based on the mapping configuration. The RLC entity can be an RLC entity of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

[0167] In a possible embodiment, the PDCP entity is configured with multiple PDCP discard timer configurations. Different PDCP discard timer configurations of the multiple PDCP discard timer configurations can be associated with different priority levels of the plurality of priority levels.

[0168] In a possible embodiment, the data type can be an Al model-related LPP data type. In a possible embodiment, the method can include establishing a dedicated radio bearer for Al-related LPP data for transmission of the new data. In other possible embodiments, the method can include other operations corresponding to the operations performed by the UE 800.

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

[0170] FIG. 12 illustrates a flowchart 1200 of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. Each operation of the flowchart 1200 may be performed in accordance with the examples described herein. In some implementations, aspects of particular operations may be performed by the NE 1000 as described with reference to FIG. 10.

[0171] At 1202, the method can include receiving, at a PDCP layer, new data for a radio bearer, where the new data corresponds to a data type of a plurality of data types. At 1204, the method can include identifying a priority level for the data type, where the identified priority level is one of a plurality of priority levels. In a possible embodiment, the new data can be a PDCP SDU and identifying the respective priority level for the data type can include parsing a data information parameter attached to the PDCP SDU to identify the respective priority level.

[0172] At 1206, the method can include routing the new data to an RLC entity that corresponds to the identified priority level. The RLC entity can be an RLC entity of a plurality of RLC entities. A PDCP entity of the PDCP layer can be associated with the plurality of RLC entities.

[0173] In a possible embodiment, the NE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity. Routing the new data to the respective RLC entity can include selecting the respective RLC entity based on the mapping configuration.

[0174] In a possible embodiment, the plurality of priority levels includes different QoS requirements for different stages of an Al LCM procedure. In a possible embodiment, the PDCP entity is configured with multiple PDCP discard timer configurations. Different PDCP discard timer configurations of the multiple PDCP discard timer configurations can be associated with different priority levels of the plurality of priority levels.

[0175] In a possible embodiment, the data type can be an Al model-related LPP data type. In a possible embodiment, the method can include establishing a dedicated radio bearer for Al-related LPP data for transmission of the new data. In other possible embodiments, the method can include other operations corresponding to the operations performed by the UE 800.

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

[0177] According to at least some embodiments, a UE is configured with a radio bearer that is associated with a plurality of LCHs, e.g., PDCP entity of the radio bearer is associated with multiple LCHs. The different LCHs are configured in order to accommodate the different QoS requirements of the data which is expected to be transmitted on the radio bearer. The radio bearer carries LPP messages comprised of AI / ML-related data (for instance for positioning), e.g., data collection reports for different LCM purposes, e.g., model training, inference, performance monitoring, and / or model transfer. The PDCP layer of the radio bearer performs the routing of PDCP PDUs to the associated RLC entities based on some information associated with a PDCP SDU.

[0178] In a possible embodiment, a PDCP entity is configured with multiple PDCP discard timer / PDCP discard timer configurations. According to one implementation of the embodiment, each of the PDCP discard timers is associated with a specific LCM purpose, e.g., data collection for training, inference, performance monitoring, and / or model transfer. Since there may be different latency requirements for data of different LCM purposes respectively different types of LPP message transmitted via the radio bearer / PDCP entity, different PDCP discard timers / values are applied for different types of messages.

[0179] In a possible embodiment, an apparatus can include a memory and a processor coupled to the memory. The processor can be configured to or operable to cause the apparatus to receive, at a PDCP layer / entity, new data for a radio bearer, where the new data corresponds to a data type; identify a priority level for the data type, where the respective priority level is one of a plurality of priority levels; and route the new data to a respective RLC entity / bearer that corresponds to the priority information, where the PDCP layer / entity is associated with a plurality of RLC entities / bearers.

[0180] In a possible implementation, the new data can be a PDCP SDU, where to identify the respective priority level for the data type, the processor is configured to or operable to cause the apparatus to parse a data information parameter attached to the PDCP SDU.

[0181] In a possible implementation, the apparatus can be configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and thecorresponding RLC entity / bearer, where to route the new data to the respective RLC entity / bearer, the processor can be configured to or operable to cause the apparatus to select the respective RLC entity / bearer based on the mapping configuration.

[0182] 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.

[0183] At least some methods of this disclosure can be implemented on a programmed processor. However, the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like. In general, any device on which resides a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this disclosure.

[0184] At least some embodiments can improve operation of the disclosed devices. Various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.

[0185] 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. For example, an element proceeded by "a," "an," or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by aphrase 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). For example, the phrase "at least one of," "at least one selected from the group of," or "at least one selected from" followed by a list is defined to mean one, some, or all, but not necessarily all of, the elements in the list. 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.

[0186] The terms "comprises," "comprising," "including," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Also, the term "another" is defined as at least a second or more. The terms "including," "having," and the like, as used herein, are defined as "comprising." Terms of approximation, such as “approximately,” “near,” “substantially,” and / or other related terms, unless otherwise defined, are defined as a range within + / - 5% of the approximated element, a range within + / - 10% of the approximated element, and / or a range close enough to the approximated element to achieve an intended result. All elements of the disclosed embodiments can be modified with such terms. In this document, relational terms such as "first," "second," and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

[0187] The background section is not admitted as prior art, is written as the inventor's own understanding of the context of some embodiments at the time of filing, and includes the inventor's own recognition of any problems with existing technologies and / or problems experienced in the inventor's own work.

[0188] The following abbreviations are defined for this disclosure: 3GPP: 3rd Generation Partnership Project; 5G: Fifth Generation; 5G-CRG: 5G-Cable Residential Gateway; 5G-GUTI: 5G-Global Unique Temporary Identifier; 5G-S-TMSI: 5G Short-Temporary Mobile SubscriptionIdentifier; 5G-TMSI: 5G Temporary Mobile Subscription Identifier; ACK: Acknowledgement; A- CSI: Aperiodic CSI; AF: Application Function; Al: Artificial Intelligence ; AMF: Access and Mobility Management Function; BFD: Beam Failure Detection; BWP: Bandwidth Part; CA: Carrier Aggregation; CC: Component Carrier; CCCH SDU: Common Control Channel Service Data Unit; CCE: Control Channel Element; CDMA: Code Division Multiple Access; CM: Connection Management; CORESET: Control Resource Set; CRC: Cyclic Redundancy Check; CRI: CSI-RS Resource Index; C-RNTI: Cell RNTI; CSI-RS: Channel State Information Reference Signal; CSI: Channel State Information; CSS: Common Search Space; D2D: Device-to-Device; DCI: Downlink Control Information; DL: Downlink; DMRS: Demodulation Reference Signal; DRX: Discontinuous Reception; E-UTRAN: Evolved Universal Terrestrial Access Network; eNB: Enhanced NodeB; FDD: Frequency Division Duplex; FN-BRG: Fixed Network Broadband RG; FN-CRG: Fixed Network Cable RG; GCI: Global Cable identifier; GERAN: GSM EDGE Radio Access Network; GLI: Global Line Identifier; gNB: New Radio NodeB; GPSI: Generic Public Subscription Identifier; GUAMI: Global Unique AMF Identifier; GUE: Gateway UE; GUTI: Global Unique Temporary Identifier; HARQ-ACK: Hybrid Automatic Repeat Request- Acknowledgement; HST: High Speed Train; ID: Identifier; IE: Information Element; IIoT: Industrial Internet of Things; IMEI: International Mobile Equipment Identity; IMEISV: International Mobile Equipment Identity Software Version; IMSI: International Mobile Subscriber Identity; loT: Internet of Things; I-RNTI: Inactive Radio Network Temporary Identifier; LTE: Long Term Evolution; MAC: Medium Access Control; MAC CE: Medium Access Control Control Element; MCG: Master Cell Group; MCS: Modulation and Coding Scheme; ML: Machine Learning; MPE: Maximum Permissible Exposure; MPO: MsgA PUSCH Occasion; MsgA: Message A; MsgB: Message B; MTC: Machine Type Communication; NACK: Non-Acknowledgement; NE: Network Element; NEF: Network Exposure Function; NG-RAN: Next-Generation Radio Access Network; NR: New Radio; NUL: Non- supplementary Uplink; OAM: Operations, Administration and Maintenance; OFDMA: Orthogonal Frequency Division Multiple Access; PCell: Primary Cell ; PDCCH: Physical Downlink Control Channel; PDSCH: Physical Downlink Shared Channel; PDU: Protocol Data Unit; PEI: Permanent Equipment Identifier; PF: Paging Frame; PHR: Power Headroom Report; MPE-P-MPR: Maximum Permitted Exposure Power Management Maximum Power Reduction; P-MPR: Power Management Maximum Power Reduction; PO: Paging Occasion; PRACH: Physical Random Access Channel; PSCell: Primary Secondary Cell; PS-RNTI: Power Saving RNTI; PUCCH: Physical Uplink ControlChannel; PUSCH: Physical Uplink Shared Channel; QCL: Quasi-co-location; RACH: Random Access Channel (Procedure); RAN: Radio Access Network; RAR: Random Access Response; RG: Residential Gateway; RLF: Radio Link Failure; RLM: Radio Link Monitoring; RM: Registration Management; RNA: RAN-based Notification Area; RNTI: Radio Network Temporary Identifier; RRC: Radio Resource Control; RRM: Radio Resource Management; RS: Reference Signal; RSRP: Reference Signal Received Power; RUE: Real UE (non-virtual UE); SAR: Specific Absorption Rate; SCell: Secondary Cell; SCG: Secondary Cell Group; SCS: Subcarrier Spacing; SFI: Slot Format Indicator; SFN: Single Frequency Network; S-NSSAI: Single Network Slice Selection Assistance Information; SpCell: Special Cell (i.e., a PCell of a MCG or SCG) ; SP-CSI: Semi- persistent CSI; SR: Scheduling Request; SRI: SRS Resource Indicator; SRS: Sounding Reference Signal; SPS: Semi-persistent scheduling; SS: Search space; SS / PBCH: Synchronization Signal / Physical Broadcast Channel; SSBRI: SS / PBCH Block Resource Index; SUL: Supplementary Uplink; SUPI: Subscription Permanent Identifier; TB: Transport block ; TCI: Transmission Configuration Indicator; TC-RNTI: Temporary Cell RNTI; TDD: Time Division Duplex; TDMA: Time Division Multiple Access; TMSI: Temporary Mobile Subscriber Identity; TPC: Transmit Power Control; TRP: Transmission and Reception Point; UCI: Uplink Control Information; UDM: Unified Data Management; UDR: Unified Data Repository; UE: User Equipment; UL: Uplink; UPF: User Plane Function; URLLC: Ultra-Reliable Low-Latency Communication; USS: UE- specific Search Space; VUE: Virtual UE; W-5GAN: Wireline 5G Access Network; XR: extended Reality

Claims

CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the UE to: receive, at a packet data convergence protocol (PDCP) layer, new data for a radio bearer, wherein the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, wherein the identified priority level is one of a plurality of priority levels; and route the new data to a radio link control (RLC) entity that corresponds to the identified priority level, wherein the RLC entity is one of a plurality of RLC entities, and wherein a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

2. The UE of claim 1, wherein the new data comprises a PDCP service data unit (SDU), and wherein to identify the respective priority level for the data type, the at least one processor is further operable to cause the UE to parse a data information parameter attached to the PDCP SDU.

3. The UE of claim 1, wherein the UE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity, and wherein to route the new data to the respective RLC entity, the at least one processor is further operable to cause the UE to select the respective RLC entity based on the mapping configuration.

4. The UE of claim 1 , wherein the plurality of priority levels comprises different quality of service (QoS) requirements for different stages of an artificial intelligence (Al) life cycle management (LCM) procedure.

5. The UE of claim 4, wherein the PDCP entity is configured with multiple PDCP discard timer configurations, where different PDCP discard timer configurations of the multiple PDCP discard timer configurations are associated with different priority levels of the plurality of priority levels.

6. The UE of claim 1 , wherein the data type comprises an artificial intelligence (Al) model-related long-term evolution positioning protocol (LPP) data type.

7. The UE of claim 6, wherein the at least one processor is further operable to cause the UE to use a dedicated radio bearer for Al-related LPP data for transmission of the new data.

8. The UE of claim 1, wherein the at least one processor is further operable to cause the UE to route PDCP control protocol data units (PDUs) from the PDCP layer to an RLC entity having a highest priority level of the plurality of RLC entities.

9. The UE of claim 1, wherein the at least one processor is further operable to cause the UE to: determine an air interface is congested; and discard data units associated with a lower priority level of the plurality of priority levels based on determining the air interface is congested, wherein the data units comprise at least one selected from service data units (SDUs) and protocol data units (PDUs).

10. The UE of claim 1, wherein the at least one processor is further operable to cause theUE to: determine a priority of the new data for a purpose of buffer status reporting based on a priority of the RLC entity the new data is routed to; ascertain the priority of the new data is higher than a priority of other data available for transmission; and trigger a buffer status report in response to ascertaining the priority of the new data is higher than the priority of the other data available for transmission.

11. The UE of claim 1 , wherein the new data includes a label identifying the data type, and wherein the at least one processor is further operable to cause the UE to: compare the label to a list of labels identifying data types corresponding to at least one configured grant resource allocation; and transmit the new data on a corresponding configured grant allocation based on comparing the label to the list of labels.

12. The UE of claim 1, wherein the radio bearer comprises a signaling radio bearer (SRB), and wherein the at least one processor is further operable to cause the UE to: determine the identified priority level is higher than a priority threshold; and transmit the new data on SRB 1 or SRB2 based on the identified priority level being higher than the priority threshold.

13. A method performed by a user equipment (UE), the method comprising: receiving, at a packet data convergence protocol (PDCP) layer, new data for a radio bearer, wherein the new data corresponds to a data type of a plurality of data types; identifying a priority level for the data type, wherein the identified priority level is one of a plurality of priority levels; and routing the new data to a radio link control (RLC) entity that corresponds to the identified priority level, wherein the RLC entity is one of a plurality of RLC entities, and wherein a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

14. The method of claim 13, wherein the new data comprises a PDCP service data unit (SDU), and wherein identifying the respective priority level for the data type includes parsing a data information parameter attached to the PDCP SDU to identify the respective priority level.

15. The method of claim 13, wherein the UE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity, and wherein routing the new data to the respective RLC entity includes selecting the respective RLC entity based on the mapping configuration.

16. A network equipment (NE) comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the NE to: receive, at a Packet Data Convergence Protocol (PDCP) layer, new data for a radio bearer, wherein the new data corresponds to a data type of a plurality of data types; identify a priority level for the data type, wherein the identified priority level is one of a plurality of priority levels; and route the new data to a Radio Link Control (RLC) entity that corresponds to the identified priority level, wherein the RLC entity is one of a plurality of RLCentities, and wherein a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

17. The NE of claim 16, wherein the new data comprises a PDCP service data unit (SDU), and wherein to identify the respective priority level for the data type, the at least one processor is further operable to cause the NE to parse a data information parameter attached to the PDCP SDU.

18. The NE of claim 16, wherein the NE is configured with a mapping configuration that specifies a mapping between each of the plurality of priority levels and a respective RLC entity, and wherein to route the new data to the respective RLC entity, the at least one processor is further operable to cause the NE to select the respective RLC entity based on the mapping configuration.

19. The NE of claim 16, wherein the plurality of priority levels comprises different quality of service (QoS) requirements for different stages of an artificial intelligence (Al) life cycle management (LCM) procedure.

20. A method performed by a network equipment (NE), the method comprising: receiving, at a packet data convergence protocol (PDCP) layer, new data for a radio bearer, wherein the new data corresponds to a data type of a plurality of data types; identifying a priority level for the data type, wherein the identified priority level is one of a plurality of priority levels; and routing the new data to a radio link control (RLC) entity that corresponds to the identified priority level, wherein the RLC entity is one of a plurality of RLC entities, and wherein a PDCP entity of the PDCP layer is associated with the plurality of RLC entities.

Images