Quality of service (QoS) differentiation in user plane procedures

Abstract

Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The UE receives a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity. The at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB). Each QoS flow of the plurality of QoS flows is associated with at least one protocol data unit (PDU). The UE performs one or more Layer 2 (L2) procedures based on the received configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to PCT patent application No. PCT / CN2022 / 094875 filed on May 25, 2022, which is hereby incorporated by reference in its entirety. Background Art Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for quality of service (QoS) differentiation in user plane procedures for packet processing.

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0006] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuous desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0007] One aspect provides a method for wireless communication by a user equipment (UE), comprising: receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB), and wherein each of the plurality of QoS flows is associated with at least one protocol data unit (PDU); and performing one or more layer 2 (L2) procedures based on the received configuration.

[0008] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform the aforementioned method and those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the aforementioned method and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising code for performing the aforementioned method and those described elsewhere herein; and an apparatus comprising components for performing the aforementioned method and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0009] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings depict certain features of the aspects described herein and should not be considered to limit the scope of the disclosure.

[0011] Figure 1 An example wireless communication network is depicted.

[0012] Figure 2 An example decomposed base station (BS) architecture is depicted.

[0013] Figure 3 Aspects of an example BS and example user equipment (UE) are depicted.

[0014] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0015] Figure 5 Depicted are example quality of service (QoS) flows for extended reality (XR) applications with different QoS requirements.

[0016] Figure 6 An example layer 2 (L2) architecture is depicted.

[0017] Figure 7 Depicted is a call flow diagram illustrating example communications between a UE and a network entity.

[0018] Figure 8 Depicted is an example QoS differentiation for different QoS flows within a data radio bearer (DRB) using a new QoS profile identifier (QPI) associated with the different QoS flows.

[0019] Fig. 9Depicted is an example differentiated L2 procedure within a DRB.

[0020] Fig.10 Depicted is an example inter-QPI out-of-order delivery to upper layers.

[0021] Fig.11 Methods for wireless communications by a UE are described.

[0022] Fig.12 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0023] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for quality of service (QoS) differentiation in user plane layer 2 (L2) procedures for packet processing. The L2 procedures may include packet data convergence protocol (PDCP) layer procedures, radio link control (RLC) layer procedures, and / or medium access control (MAC) layer procedures.

[0024] Current L2 procedures are configured and executed on a per-data radio bearer (DRB) basis under the assumption that all packets in the same DRB have compatible and similar QoS requirements. This makes it difficult for L2 procedures (e.g., PDCP layer procedures) to meet different QoS requirements of various QoS flows multiplexed in the same DRB. For example, when QoS flows associated with control packets and text message packets are multiplexed in the same DRB during L2 procedures, the PDCP layer discard timer configured based on the packet delay budget (PDB) of the control packets may result in high loss of text message packets. Therefore, there is a need to distinguish the QoS requirements associated with different QoS flows within the same DRB so that the L2 procedures can meet the different QoS requirements of various QoS flows multiplexed in the same DRB.

[0025] The technology presented herein supports differentiated user plane L2 procedures for packet processing within a DRB based on a configured QoS profile identifier (QPI) associated with a QoS flow within a DRB associated with multiple QoS flows with different QoS requirements. The QPI may be associated with one or more QoS flows (e.g., with similar QoS requirements) within the DRB. In one example, the QPI may be associated with two QoS flows. In another example, the QPI may be associated with one QoS flow. Applying differentiated (e.g., based on configured QPIs) user plane L2 procedures within a DRB may satisfy QoS requirements of various QoS flows in the same DRB.

[0026] For example, when a first set of QoS flows (e.g., one or more QoS flows associated with control packets with short deadlines) configured with a first QPI are multiplexed with a second set of QoS flows (e.g., one or more QoS flows associated with user message packets such as audio / voice / text data) configured with a second QPI in the same DRB, applying differentiated user plane L2 procedures within the DRB corresponds to selecting a first value (e.g., based on the configured first QPI) of a discard timer for the first set of QoS flows and selecting a second value (e.g., based on the configured second QPI) of a discard timer for the second set of QoS flows. The first value and the second value are selected to satisfy QoS requirements of the first set of QoS flows and the second set of QoS flows within the same DRB.

[0027] The technology proposed in this paper can provide high speed / throughput, high reliability and low latency by meeting the different QoS requirements of various QoS flows multiplexed in the same DRB.

[0028] Introduction to wireless communication networks

[0029] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0030] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0031] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) that can communicate with other network elements (e.g., ground BSs) and UEs.

[0032] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190), which interoperate to provide communication services over various communication links (including wired and wireless links).

[0033] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0034] BS 102 wirelessly communicates with (e.g., transmits signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0035] BS 102 may generally include: NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, transceiver base station, radio BS, radio transceiver, transceiver function, transmission and reception point, and / or other. Each of BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (relatively small geographic area (e.g., a home)), and / or other types of cells.

[0036] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of BS102 may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of BS102 may be virtualized. More generally, a BS (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which BS102 includes components located at various physical locations, each component may perform each function so that each component together achieves functionality similar to that of a BS 102 located at a single physical location. In some aspects, a BS102 including components located at various physical locations may be referred to as a decomposed radio access network (RAN) architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. Figure 2 An example decomposed BS architecture is depicted and described.

[0037] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0038] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 600 MHz-6 GHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 26 GHz–41 GHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A BS (e.g., a mmWave BS such as BS 180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and distance.

[0039] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0040] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Therefore, some BSs (e.g. Figure 1 180) may utilize beamforming 182 with UE 104 to improve path loss and distance. For example, BS 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels and / or antenna arrays) to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. It is noteworthy that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.

[0041] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0042] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0043] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0044] Typically, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0045] The BM-SC 170 may provide functionality for MBMS user service configuration and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0046] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMF 193, session management function (SMF) 194 and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0047] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0048] Internet Protocol (IP) packets are delivered through UPF 195, which connects to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0049] The wireless communication network 100 also includes a quality of service (QoS) profile identifier (QPI) component 198, which can be configured to perform Fig.11 The wireless communication network 100 also includes a QPI component 199 .

[0050] In various aspects, a network entity or network node may be implemented as a converged BS, a decomposed BS, a component of a BS, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0051] Figure 2 An example decomposed BS 200 architecture is depicted. The decomposed BS 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed BS units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0052] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0053] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 210. CU210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0054] DU 230 may correspond to a logical unit that includes one or more BS functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on functional splits such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0055] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting such as lower layer functional splitting. In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0056] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 211 via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0057] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0058] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0059] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0060] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0061] BS 102 includes a controller / processor 340 that can be configured to implement various functions related to wireless communication. In the depicted example, controller / processor 340 includes a QPI component 341, which can represent Figure 1 The SCI component 199 of BS 102. It is worth noting that, although depicted as an aspect of the controller / processor 340, in other specific implementations, the QPI component 341 may additionally or alternatively be implemented in various other aspects of the BS 102.

[0062] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0063] UE 104 includes a controller / processor 380 that can be configured to implement various functions related to wireless communication. In the depicted example, the controller / processor 380 includes a QPI component 381, which can represent Figure 1 The SCI component 198 of the UE 104. It is worth noting that, although depicted as an aspect of the controller / processor 380, in other specific implementations, the QPI component 381 may additionally or alternatively be implemented in various other aspects of the UE 104.

[0064] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0065] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0066] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 332a to 332t. Each modulator in transceivers 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0067] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0068] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0069] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0070] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0071] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0072] The scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0073] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0074] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0075] In some aspects, the processor may be configured to perform operations such as those associated with the methods described herein and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0076] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0077] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0078] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0079] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0080] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X can be used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include a micro-time slot, which typically has fewer symbols than a whole time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0081] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and parameter set μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0082] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted in , a resource grid can be used to represent a frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0083] like Figure 4A As illustrated, some of the REs carry data for UEs (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0084] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0085] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0086] The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0087] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0088] like Figure 4CAs illustrated, some of the REs carry DMRS for channel estimation at the BS (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may send a DMRS for PUCCH and a DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. The UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the BS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0089] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0090] Example Quality of Service (QoS)

[0091] Quality of Service (QoS) refers to the measurement of the overall performance of a service as experienced by users of a network. In order to quantitatively measure QoS packet loss, relevant aspects of the service such as bit rate, throughput, transmission delay, availability, etc. are considered. QoS includes requirements for all aspects of the connection, such as service response time, loss, signal-to-noise ratio, crosstalk, echo, interruption, frequency response and / or loudness level.

[0092] In 5G New Radio (NR), QoS is implemented at the QoS flow level. Each QoS flow packet (e.g., data packet) is classified and marked using a QoS flow identifier (QFI). For example, a first QoS flow is associated with video packets (e.g., video packets of a first video conferencing company and video packets of a second video conferencing company), and a second QoS flow is associated with video stream packets (e.g., video packets of the first video stream company). One or more QoS flows are mapped to one or more data radio bearers (DRBs) in an access network. For example, a DRB transports packets carried by an Evolved Packet System (EPS) between a User Equipment (UE) and a network entity.

[0093] Within a 5G network, a 5G QoS Identifier (5QI) mechanism may be used, where packets are classified into different QoS classes. In this way, QoS can be customized for specific requirements. Each QoS class has its own assigned QoS characteristics (e.g., such as packet delay and packet loss). Therefore, some packets may receive better QoS than other packets.

[0094] The network entity maps each QoS flow to one or more DRBs. A protocol data unit (PDU) session may contain multiple QoS flows and several DRBs. For example, a PDU session provides end-to-end user plane connectivity between a UE and a specific data network through a user plane function (UPF). A PDU session supports one or more QoS flows, and a DRB transports one or more QoS flows.

[0095] The network entity provides one or more QoS flow descriptions associated with a PDU session to the UE at PDU session establishment time or at PDU session modification time. Each QoS flow description may include a) a QFI; b) if the QoS flow is a guaranteed bit rate (GBR) QoS flow: 1) a guaranteed flow bit rate (GFBR) for uplink, 2) a GFBR for downlink, 3) a maximum flow bit rate (MFBR) for uplink, 4) a MFBR for downlink and / or 5) an averaging window applicable to both uplink and downlink, or if the QoS flow is a non-GBR QoS flow: 1) a reflective QoS attribute (RQA) in downlink and / or 2) additional QoS flow information; c) a 5G QoS identifier (5QI) if the QFI is different from the 5QI of the QoS flow identified by the QFI; d) an allocation and retention priority (ARP), and / or e) an EPS bearer identifier (EBI) if the QoS flow can be mapped to an EPS bearer. All packets belonging to a specific QoS flow have the same 5QI.

[0096] The network entity provides the UE with QoS rules associated with the PDU session. The QoS rules may be provided when the PDU session is established or when the PDU session is modified. Each QoS rule includes an indication of whether the QoS rule is a default QoS rule, a QoS rule identifier (QRI), a QFI, a set of packet filters, and / or a priority value.

[0097] Example Quality of Service (QoS) Flow in Extended Reality (XR) Applications

[0098] Extended reality (XR) applications may include virtual reality (VR) applications, augmented reality (AR) applications, and / or mixed reality (MR) applications. XR applications generate multiple quality of service (QoS) flows for different packets. Figure 5As illustrated, multiple QoS flows are associated with video frame packets, audio / voice packets, control packets (e.g., a user equipment (UE) may transmit multiple control messages during a car video game), gesture update packets (e.g., user head movements in a VR game), and text message packets. Figure 5 As further illustrated, multiple QoS flows may have different QoS requirements (eg, latency requirements, loss rate requirements, bit rate requirements, etc.).

[0099] Ideally, each QoS flow should be mapped to a single data radio bearer (DRB). However, in most cases, multiple QoS flows are mapped to a single DRB. The mapping of multiple QoS flows to a single DRB may occur for several reasons. In one example (i.e., on the network entity side), the operator is charged based on the number of DRBs (e.g., operating costs). Therefore, in order to prevent high costs, the operator may multiplex multiple QoS flows into a single DRB (e.g., as long as the QoS requirements of all QoS flows being multiplexed into a single DRB can be met). In another example (e.g., on the UE side), each DRB requires a separate layer 2 (L2) entity and a dedicated memory block. Therefore, multiple DRBs will require a large memory in the UE. The use of large memory results in higher production costs for the UE and more power consumption of the UE during operation.

[0100] In some cases (e.g., XR applications), when multiple QoS flows are mapped to a single DRB, the multiple QoS flows may have similar but slightly different QoS requirements. For example, when multiple QoS flows associated with audio / voice packets and posture update packets are mapped to a single DRB due to their similar QoS requirements (e.g., lower bit rate requirements), the posture update packets will still require better QoS treatment than the audio / voice packets (e.g., due to the very low latency QoS requirements associated with the posture update packets).

[0101] Currently, it is not possible to provide gesture update packets with better QoS treatment than audio / voice packets during processing because there is no technology to differentiate the QoS requirements associated with multiple QoS flows within a single DRB. Therefore, there is a need to differentiate the QoS requirements associated with multiple QoS flows within a single DRB to provide one QoS flow (e.g., associated with gesture update packets) with better QoS treatment than other QoS flows based on the different QoS requirements of the other QoS flows (e.g., associated with audio / voice packets).

[0102] In some cases, the UEs used for XR applications may be reduced-capability (RedCap) UEs, which have smaller memories and are more power-sensitive. RedCap UEs may exhibit relaxations in peak throughput (e.g., 20MHz), as well as lower latency and / or reliability requirements. Moreover, RedCap UEs may involve lower device cost (and complexity) and improved efficiency (e.g., power consumption, system overhead, and cost improvements) as compared to high-end devices such as high-end enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) devices (e.g., high-end smartphones) of 5G NR Release 15 / 16. Some design goals of NR RedCap UEs may include scalable resource allocation, coverage enhancement for downlink and / or uplink, power savings in all radio resource control (RRC) states, and / or coexistence with NR high-end UEs. NR RedCap UEs may be smart wearable devices, sensors (e.g., industrial wireless sensor networks), cameras (e.g., surveillance cameras), low-end smartphones, or any other device configured for easy Internet of Things (IoT) communications.

[0103] Example Layer 2 (L2) of the New Radio (NR) protocol stack

[0104] The New Radio (NR) radio protocol stack has two categories: 1) control plane stack, and 2) user plane stack. If the data corresponds to signaling or control messages, the data is transmitted through the control plane. User data is transmitted through the user plane.

[0105] like Figure 6 As illustrated, the user plane protocol stack (e.g., Layer 2 (L2)) of NR is split into sublayers such as a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. In NR, carrier aggregation is supported, and data for each carrier may be processed independently in the SDAP layer, the PDCP layer, the RLC layer, and multiplexed in the MAC layer.

[0106] The SDAP layer may perform mapping between quality of service (QoS) flows (e.g., associated with one or more packets (e.g., protocol data units (PDUs)) and data radio bearers (DRBs) (e.g., due to a QoS framework). The SDAP layer may also perform marking QoS flow IDs (QFIs) in both downlink and uplink packets (e.g., downlink due to reflective QoS and uplink due to a QoS framework). A single protocol entity of SDAP is configured for each respective protocol data unit (PDU) session.

[0107] The PDCP layer can perform header compression and decompression of Internet Protocol (IP) data (e.g., Robust Header Compression (ROHC)), maintain the PDCP sequence number (SN), perform in-order delivery of upper layer PDUs upon re-establishment of lower layers, perform reordering and eliminate copies of lower layer service data units (SDUs), perform PDCP PDU routing for split bearer scenarios, perform retransmission of lower layer SDUs, encrypt and decrypt control plane and user plane data, perform integrity protection and integrity verification of control plane and user plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0108] The RLC layer may operate in a variety of operation modes including a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). The RLC layer may perform delivery of upper layer PDU error correction for AM data delivery through automatic repeat request (ARQ) and perform segmentation and reassembly of RLC SDUs for UM and AM data delivery. The RLC layer may maintain SNs for UM and AM data delivery independently of SNs in PDCP. The RLC layer may perform re-segmentation of RLC data PDUs for AM data delivery, detect duplicate data for AM data delivery, discard RLC SDUs for UM and AM data delivery, detect protocol errors for AM data delivery, and / or perform RLC reconstruction.

[0109] The MAC layer can perform mapping between logical channels and transport channels, multiplexing MAC SDU from one or more logical channels to transport blocks (TBs) to be delivered to the physical layer (PHY) via the transport channel, demultiplexing MAC SDU from TBs delivered from the PHY via the transport channel to one or more logical channels, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority processing between UEs with the help of dynamic scheduling, priority processing between logical channels of a UE with the help of logical channel prioritization, and / or padding.

[0110] Current L2 procedures (e.g., PDCP layer procedures, MAC layer procedures, etc.) are configured and executed on a per-DRB basis (e.g., under the assumption that all packets in the same DRB have compatible and similar QoS requirements). This makes it difficult for the L2 procedures to meet the different QoS requirements of various QoS flows multiplexed in the same DRB. In one example, when QoS flows associated with control packets and text message packets are multiplexed in the same DRB, a PDCP discard timer (e.g., a short discard timer) configured based on a packet delay budget (PDB) for control packets may result in high loss of text message packets during the L2 procedures. In another example (e.g., out-of-order delivery in PDCP), when QoS flows associated with control packets and text message packets are multiplexed in the same DRB, then in some cases, text message packets may block the delivery of control packets (e.g., which may be more delay-sensitive than text message packets) during the L2 procedures. In another example (eg, Logical Channel Prioritization (LCP) in MAC during L2 procedures), implementing the LCP traffic shaper per QoS flow is more resource efficient than implementing the LCP traffic shaper per DRB.

[0111] Therefore, there is a need to differentiate the QoS requirements associated with different QoS flows within the same DRB so that the L2 procedure can meet the different QoS requirements of the various QoS flows multiplexed in the same DRB.

[0112] Aspects related to Quality of Service (QoS) differentiation in user plane procedures

[0113] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for Quality of Service (QoS) differentiation in user plane layer 2 (L2) procedures for packet processing.

[0114] The technology presented herein supports differentiated user plane L2 procedures for packet processing within a data radio bearer (DRB) that is associated with multiple QoS flows with different QoS requirements based on a configured QoS profile identifier (QPI) associated with a QoS flow within the DRB (e.g., rather than a QoS flow identifier (QFI) associated with a single QoS flow). The QPI may be associated with one or more QoS flows within the DRB. In one example, the QPI may be associated with two QoS flows (e.g., with similar QoS requirements). In another example, the QPI may be associated with one QoS flow. Applying differentiated user plane L2 procedures within a DRB may satisfy the QoS requirements of individual QoS flows in the same DRB.

[0115] For example, when a first set of QoS flows (e.g., one or more QoS flows associated with control packets with short deadlines) configured with a first QPI are multiplexed with a second set of QoS flows (e.g., one or more QoS flows associated with user message packets such as audio / voice / text data) configured with a second QPI in the same DRB, applying differentiated user plane L2 procedures within the DRB corresponds to selecting a first value (e.g., based on the configured first QPI) of a discard timer for the first set of QoS flows and selecting a second value (e.g., based on the configured second QPI) of a discard timer for the second set of QoS flows. The first value and the second value are selected to satisfy QoS requirements of the first set of QoS flows and the second set of QoS flows within the same DRB.

[0116] For reference Figures 7 to 11 To understand the technology proposed in this article for QoS differentiation in user plane procedures.

[0117] like Figure 7 As illustrated, at 702, a network entity (e.g., such as Figure 1 102 in the wireless communication network 100) to a UE (e.g., such as Figure 1 A UE 104 in a wireless communication network 100 of the present invention may send a configuration of at least one QPI associated with multiple QoS flows within a DRB (e.g., associated with multiple packets (e.g., protocol data units (PDUs)) to a UE 104 in a wireless communication network 100 of the present invention. For example, the network entity may configure the UE via a radio resource control (RRC) to specify how to map the multiple QoS flows to the at least one QPI.

[0118] In some cases, each QoS flow in the plurality of QoS flows may have a unique identifier (e.g., a QoS flow identifier (QFI)). The mapping may be a one-to-one mapping between the QFI and at least one QPI (e.g., one QFI is mapped to one QPI). The mapping may be a many-to-one mapping between the QFI and at least one QPI (e.g., two QFIs are mapped to one QPI). In one example, the mapping may be performed at a service data adaptation protocol (SDAP) layer. In another example, the mapping may be performed at some other layer.

[0119] At 704, the UE performs one or more L2 procedures based on the received configuration.For example, the UE may support and perform differentiated L2 procedures or configurations within a DRB based on the configured at least one QPI associated with the PDUs within the DRB.

[0120] In certain aspects, one or more differentiated L2 procedures may include packet data convergence protocol (PDCP) layer procedures, radio link control (RLC) layer procedures, and / or medium access control (MAC) layer procedures that can be differentiated within a DRB (e.g., to meet different QoS requirements for different QoS flows).

[0121] In certain aspects, conventional L2 configuration and procedures may be applied by default to all PDUs within a DRB. However, PDUs within a DRB whose QPI matches at least one QPI configured by RRC may be subject to differentiated L2 procedures.

[0122] like Figure 8 As illustrated, at the sender node (e.g., UE, network entity, etc.), the mapping between different QoS flows and QPIs is performed at the SDAP layer. The QPI of the MAC service data unit (SDU) is then added to the MAC subheader, which is then delivered to the physical (PHY) layer. The packet received by the layer is called an SDU. At the receiver node (e.g., network entity, UE, etc.), the QPI is extracted at the MAC layer and then passed up to the L2 protocol stack (e.g., to the PDCP layer) through a cross-layer indication.

[0123] like Fig. 9 As illustrated, the UE applies different PDCP procedures, RLC procedures, and MAC procedures to different QoS flows or PDUs associated with different QPIs (e.g., indicating different QoS requirements) within a DRB to meet different QoS requirements. The differentiated PDCP procedures, RLC procedures, and MAC procedures are based on different QPIs.

[0124] In one example, the UE applies differentiated PDCP procedures to use separate values ​​for discard timers for different PDUs associated with different QPIs. For example, when a first PDU associated with a first QPI (e.g., a control packet with a short deadline) and a second PDU associated with a second QPI (e.g., a user message packet such as audio / voice / text data) are multiplexed, the discard timers for the first PDU and the second PDU may have different values. Different values ​​are selected to meet different QoS requirements of the first PDU and the second PDU.

[0125] In another example, the UE applies differentiated PDCP procedures to allow out-of-order delivery for different PDUs associated with different QPIs while applying in-order delivery for other PDUs associated with the same QPI. For example, out-of-order delivery of a first PDU may be allowed when the first PDU is blocked by a second PDU within a DRB (e.g., due to a shorter deadline of the first PDU).

[0126] In another example, the UE applies differentiated PDCP procedures to use separate values ​​for reordering timers (e.g., t-Reordering timers) for different PDUs associated with different QPIs. For example, the reordering timers for the first PDU and the second PDU may have different values, such that the value of the reordering timer for the first PDU may have a smaller value than the value of the reordering timer for the second PDU. The different values ​​are selected to meet different QoS requirements for the first PDU and the second PDU.

[0127] In another example, the UE applies differentiated PDCP procedures to use different primary paths (e.g., split bearer routing) for different PDUs associated with different QPIs. For example, a first PDU is transmitted on New Radio (NR) and a second PDU is transmitted on Long Term Evolution (LTE). Different paths are selected to meet different QoS requirements of the first PDU and the second PDU.

[0128] In another example, the UE applies a differentiated PDCP procedure to duplicate one or more PDUs associated with at least one QPI (eg, which may be a specific QPI). For example, the UE may only duplicate the first PDU but not the second PDU.

[0129] In another example, the UE applies differentiated RLC procedures to use separate values ​​for reassembly timers (e.g., t-Reassembly timers) for different PDUs associated with different QPIs. For example, the reassembly timers for the first PDU and the second PDU may have different values, such that the value of the reassembly timer for the first PDU may have a smaller value than the value of the reassembly timer for the second PDU. The different values ​​are selected to meet different QoS requirements for the first PDU and the second PDU.

[0130] In another example, the UE applies differentiated RLC procedures to use separate values ​​for the state prohibit timer (e.g., t-StatusProhibit timer) for different PDUs associated with different QPIs. For example, the state prohibit timer for a first PDU and a second PDU may have different values, such that the value of the state prohibit timer for the first PDU may have a smaller value than the value of the state prohibit timer for the second PDU (e.g., to allow faster feedback for time-sensitive PDUs).

[0131] In another example, the UE applies differentiated MAC procedures to enforce separate sets of prioritized bit rate (PBR), bucket size duration (BSD), and / or logical channel prioritization (LCP) limits for different PDUs associated with different QPIs. For example, the PBR / BSD / LCR limits for a first PDU associated with a first QPI and a third PDU (e.g., a posture update packet) associated with a third QPI may be different. Different PBR / BSD / LCR limits are selected to meet different QoS requirements for the first PDU and the second PDU.

[0132] In certain aspects, the configuration corresponds to a first configuration that enables various differentiated L2 procedures over at least one of a default PDCP configuration, a default RLC configuration, or a default logical channel configuration. For example, the network entity may enable differentiation of various features (e.g., a discard timer or a t-statusProhibitTimer) over a default PDCP configuration (e.g., PDCP-Config), a default RLC configuration (e.g., RLC-Config), or a default logical channel configuration (e.g., LogicalChannelConfig).

[0133] In certain aspects, the configuration corresponds to a second configuration that indicates a separate default PDCP configuration, RLC configuration, or logical channel configuration for at least one QPI. For example, the network entity may configure a PDCP configuration, RLC configuration, or logical channel configuration for a specific QPI for a UE.

[0134] In certain aspects, the configuration indicates that the first configuration and the second configuration are applied to different protocol stack layers.

[0135] like Fig.10 As illustrated, the first PDU, the third PDU, the fourth PDU, and the eighth PDU are associated with the first QPI. The second PDU, the fifth PDU, the sixth PDU, and the seventh PDU are associated with the second QPI. During the L2 protocol inter-QPI out-of-order delivery operation, the first PDU, the second PDU, the fifth PDU, the sixth PDU, and the eighth PDU are received in the receiver buffer. At this time, the third PDU, the fourth PDU, and the seventh PDU have not yet been received. Since the second PDU, the fifth PDU, and the sixth PDU are in sequence (and associated with the same QPI), the second PDU, the fifth PDU, and the sixth PDU can be delivered (i.e., inter-QPI out-of-order delivery) to the upper layer even when the third PDU and the fourth PDU are not received in the buffer. This allows PDUs in more delay-sensitive QoS flows to not be blocked by other PDUs ahead of them. In some aspects, when inter-QPI out-of-order delivery is configured, each QPI has its own associated sequence number in addition to the legacy PDCP sequence number.

[0136] Example Operation of UE

[0137] Fig.11 Example operations 1100 for wireless communication are illustrated. Operations 1100 may be performed, for example, by a user equipment (UE) (e.g., such as Figure 1 Operation 1100 may be implemented as a processor (e.g., Figure 3 In addition, the UE may transmit and receive signals in operation 1100 by, for example, one or more antennas (e.g., Figure 3 In some aspects, the signal transmission and / or reception by the UE may be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 380).

[0138] Operations 1100 begin at 1110 by receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity. The at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB). Each QoS flow in the plurality of QoS flows is associated with at least one protocol data unit (PDU). For example, the UE may use Figure 1 or Figure 3 The UE 104 and / or Fig.12 The antenna and / or receiver / transceiver components of the illustrated apparatus receive the configuration from a network entity.

[0139] At 1120, the UE performs one or more layer 2 (L2) procedures based on the received configuration. For example, the UE may use Figure 1 or Figure 3 The UE 104 and / or Fig.12 The processor of the device shown is used to execute one or more L2 procedures.

[0140] It should be noted that Fig.11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0141] Example Communication Device

[0142] Fig.12 Various aspects of an example communications device 1200 are depicted. In some aspects, the communications device 1200 is a user equipment (UE), such as described above with respect to Figure 1 and Figure 3 UE 104 is described.

[0143] The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or a receiver). The transceiver 1208 is configured to transmit and receive signals for the communication device 1200, such as the various signals described herein, via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.

[0144] The processing system 1202 includes one or more processors 1220. In various aspects, the one or more processors 1220 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as shown in FIG. Figure 3 The one or more processors 1220 are coupled to the computer readable medium / memory 1230 via the bus 1206. In some aspects, the computer readable medium / memory 1230 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1220, cause the one or more processors 1220 to perform operations related to Fig.11 The described operations 1100 or any aspects related thereto. Note that reference to a processor performing a function of the communication device 1200 may include one or more processors performing that function of the communication device 1200.

[0145] In the depicted example, computer readable medium / memory 1230 stores: code (e.g., executable instructions) for receiving 1231, the code including code for receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB) and wherein each of the plurality of QoS flows is associated with at least one protocol data unit (PDU); and code for executing 1233, the code including code for executing one or more layer 2 (L2) procedures based on the received configuration. Processing of code 1231-code 1233 may cause the communication device 1200 to perform operations relative to Fig.11 The described operations 1100 or any aspect related thereto.

[0146] The one or more processors 1220 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1230, including: circuits for receiving 1221, the circuits including circuits for receiving a configuration of at least one QPI from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a DRB and wherein each of the plurality of QoS flows is associated with at least one PDU; and circuits for executing 1223, the circuits including circuits for executing one or more L2 procedures based on the received configuration. Processing using circuits 1221-1223 may cause the communication device 1200 to perform operations with respect to Fig.11 The described operations 1100 or any aspect related thereto.

[0147] The various components of the communication device 1200 may be provided for performing Fig.11 The described means for operation 1100 or any aspect related thereto. For example, means for sending, transmitting, or outputting for sending may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.12 The transceiver 1208 and antenna 1210 of the communication device 1200 in FIG.

[0148] Sample Clauses

[0149] Specific implementation examples are described in the following numbered clauses:

[0150] Clause 1: A method for wireless communications by a user equipment (UE), comprising: receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB), and wherein each of the plurality of QoS flows is associated with at least one protocol data unit (PDU); and performing one or more layer 2 (L2) procedures based on the received configuration.

[0151] Clause 2: The method of clause 1, alone or in combination, wherein the configuration further indicates a mapping of one or more of the plurality of QoS flows within the DRB to the at least one QPI.

[0152] Clause 3: The method as recited in clause 2, alone or in combination, wherein the mapping is performed at a Service Data Adaptation Protocol (SDAP) layer.

[0153] Clause 4: The method of clause 1, alone or in combination, wherein the performing further comprises using separate discard timers for different PDUs associated with different QPIs.

[0154] Clause 5: The method of claim 1, alone or in combination with clause 1, wherein the performing further comprises allowing out-of-order delivery for different PDUs associated with different QPIs while applying in-order delivery for other PDUs associated with the same QPI.

[0155] Clause 6: The method of clause 1, alone or in combination, wherein the performing further comprises using separate reordering timers for different PDUs associated with different QPIs.

[0156] Clause 7: The method as recited, alone or in combination with clause 1, wherein said performing further comprises allowing different primary paths for different PDUs associated with different QPIs.

[0157] Clause 8: The method as recited in clause 1, alone or in combination, wherein said performing further comprises applying replication only to one or more PDUs associated with said at least one QPI.

[0158] Clause 9: The method of clause 1, alone or in combination, wherein the performing further comprises using separate reassembly timers for different PDUs associated with different QPIs.

[0159] Clause 10: The method of clause 1, alone or in combination with clause 1, wherein the performing further comprises using separate state prohibit timers for different PDUs associated with different QPIs.

[0160] Clause 11: The method of clause 1, alone or in combination with clause 1, wherein the performing further comprises performing separate sets of prioritized bit rate (PBR), bucket size duration (BSD), and logical channel prioritization (LCP) constraints for different PDUs associated with different QPIs.

[0161] Clause 12: The method described in claim 1, either alone or in combination with the first clause, wherein the configuration corresponds to a first configuration that enables each differentiated L2 procedure to be based on at least one of a default packet data convergence protocol (PDCP) configuration, a default radio link control (RLC) configuration, or a default logical channel configuration.

[0162] Clause 13: The method of claim 1, alone or in combination with the first clause, wherein the configuration corresponds to a second configuration, the second configuration indicating a separate default Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) configuration, or logical channel configuration for the at least one QPI.

[0163] Clause 14: A method as described in claim 1, either alone or in combination with the method described in claim 1, wherein: the configuration indicates that a first configuration and a second configuration are applied to different protocol stack layers; the first configuration enables each differentiated L2 procedure to be on top of at least one of a default packet data convergence protocol (PDCP) configuration, a default radio link control (RLC) configuration, or a default logical channel configuration; and the second configuration indicates a separate PDCP configuration, the RLC configuration, or the logical channel configuration for the at least one QPI.

[0164] Clause 15: The method as recited, alone or in combination with clause 1, wherein when inter-QPI out-of-order delivery is configured based on the received configuration, the at least one QPI has an associated sequence number.

[0165] Clause 16: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 1 to 15.

[0166] Clause 17: An apparatus comprising means for performing the method according to any one of clauses 1 to 15.

[0167] Clause 18: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 15.

[0168] Clause 19: A computer program product embodied on a computer readable storage medium, the computer readable storage medium comprising code for performing the method according to any one of clauses 1 to 15.

[0169] Additional considerations

[0170] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may ignore, replace or add various procedures or components as appropriate. For example, the described method may be performed in a different order than the described order, and various actions may be added, omitted or combined. Moreover, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0171] The various illustrative logic blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0172] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0173] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0174] The method disclosed herein includes one or more actions for implementing the method. The method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, each operation of the method described above can be performed by any appropriate component that can perform the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0175] The following claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly stated in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB), and wherein each QoS flow in the plurality of QoS flows is associated with at least one protocol data unit (PDU); as well as One or more layer 2 (L2) procedures are performed based on the received configuration.

2. The method of claim 1, wherein the configuration further indicates a mapping of one or more of the plurality of QoS flows within the DRB to the at least one QPI. 3 . The method of claim 2 , wherein the mapping is performed at a Service Data Adaptation Protocol (SDAP) layer.

4. The method of claim 1, wherein the performing further comprises using separate discard timers for different PDUs associated with different QPIs.

5. The method of claim 1, wherein the performing further comprises allowing out-of-order delivery for different PDUs associated with different QPIs while applying in-order delivery for other PDUs associated with the same QPI.

6. The method of claim 1, wherein the performing further comprises using separate reordering timers for different PDUs associated with different QPIs.

7. The method of claim 1, wherein the performing further comprises allowing different primary paths for different PDUs associated with different QPIs.

8. The method of claim 1, wherein the performing further comprises applying replication only to one or more PDUs associated with the at least one QPI.

9. The method of claim 1, wherein the performing further comprises using separate reassembly timers for different PDUs associated with different QPIs.

10. The method of claim 1, wherein the performing further comprises using separate state prohibit timers for different PDUs associated with different QPIs.

11. The method of claim 1 , wherein the performing further comprises performing separate sets of prioritized bit rate (PBR), bucket size duration (BSD), and logical channel prioritization (LCP) restrictions for different PDUs associated with different QPIs.

12. The method of claim 1, wherein the configuration corresponds to a first configuration that enables respective differentiated L2 procedures to be over at least one of a default Packet Data Convergence Protocol (PDCP) configuration, a default Radio Link Control (RLC) configuration, or a default logical channel configuration.

13. The method of claim 1, wherein the configuration corresponds to a second configuration indicating a separate default Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) configuration, or logical channel configuration for the at least one QPI.

14. The method of claim 1, wherein: The configuration indicates that the first configuration and the second configuration are applied to different protocol stack layers; The first configuration enables respective differentiated L2 procedures to be over at least one of a default Packet Data Convergence Protocol (PDCP) configuration, a default Radio Link Control (RLC) configuration, or a default logical channel configuration; and The second configuration indicates a separate PDCP configuration, the RLC configuration, or the logical channel configuration for the at least one QPI.

15. The method of claim 1, wherein when inter-QPI out-of-order delivery is configured based on the received configuration, the at least one QPI has an associated sequence number.

16. A user equipment (UE) configured for wireless communication, comprising: a memory including computer executable instructions; and a processor configured to execute the computer executable instructions and cause the UE to: receiving a configuration of at least one quality of service (QoS) profile identifier (QPI) from a network entity, wherein the at least one QPI is associated with a plurality of QoS flows within a data radio bearer (DRB), and wherein each QoS flow in the plurality of QoS flows is associated with at least one protocol data unit (PDU); as well as One or more layer 2 (L2) procedures are performed based on the received configuration.

17. The UE of claim 16, wherein the configuration further indicates a mapping of one or more QoS flows among the plurality of QoS flows within the DRB to the at least one QPI.

18. The UE of claim 17, wherein the mapping is performed at a Service Data Adaptation Protocol (SDAP) layer.

19. The UE of claim 16, wherein the performing further comprises using separate discard timers for different PDUs associated with different QPIs.

20. The UE of claim 16, wherein the performing further comprises allowing out-of-order delivery for different PDUs associated with different QPIs while applying in-order delivery for other PDUs associated with the same QPI.

21. The UE of claim 16, wherein the performing further comprises using separate reordering timers for different PDUs associated with different QPIs.

22. The UE of claim 16, wherein the performing further comprises allowing different primary paths for different PDUs associated with different QPIs.

23. The UE of claim 16, wherein the performing further comprises applying replication only to one or more PDUs associated with the at least one QPI.

24. The UE of claim 16, wherein the performing further comprises using separate reassembly timers for different PDUs associated with different QPIs.

25. The UE of claim 16, wherein the performing further comprises using separate state prohibit timers for different PDUs associated with different QPIs.

26. The UE of claim 16, wherein the performing further comprises performing separate sets of prioritized bit rate (PBR), bucket size duration (BSD), and logical channel prioritization (LCP) restrictions for different PDUs associated with different QPIs.

27. The UE of claim 16, wherein the configuration corresponds to a first configuration that enables respective differentiated L2 procedures to be over at least one of a default Packet Data Convergence Protocol (PDCP) configuration, a default Radio Link Control (RLC) configuration, or a default logical channel configuration.

28. The UE of claim 16, wherein the configuration corresponds to a second configuration indicating a separate default Packet Data Convergence Protocol (PDCP) configuration, a Radio Link Control (RLC) configuration, or a logical channel configuration for the at least one QPI.

29. The UE of claim 16, wherein: The configuration indicates that the first configuration and the second configuration are applied to different protocol stack layers; The first configuration enables respective differentiated L2 procedures to be over at least one of a default Packet Data Convergence Protocol (PDCP) configuration, a default Radio Link Control (RLC) configuration, or a default logical channel configuration; and The second configuration indicates a separate PDCP configuration, the RLC configuration, or the logical channel configuration for the at least one QPI.

30. The UE of claim 16, wherein when inter-QPI out-of-order delivery is configured based on the received configuration, the at least one QPI has an associated sequence number.

Images