QoS flow framework

Abstract

An apparatus, a method, and a computer program product for processing a QoS flow are provided. An example method may include establishing a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows associated with a set of DRBs. The example method may also include communicating with the second device based on the set of QoS flows.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 664,639, entitled “QOS FLOW FRAMEWORK” and filed on May 23, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems with Quality of Service (QoS) flows. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example of a telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first device are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a protocol data unit (PDU) session with a second device, the PDU session including a quality of service (QoS) flow set, the QoS flow set being associated with a data radio bearer (DRB) set, each QoS flow in the QoS flow set being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. The memory and the at least one processor coupled to the memory may be further configured to communicate with the second device based on the QoS flow set.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first device are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a PDU session with a second device, the PDU session including a QoS flow set, the QoS flow set being associated with a DRB set, wherein one DRB in the DRB set is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. The memory and the at least one processor coupled to the memory may be further configured to communicate with the second device based on the QoS flow set.

[0009] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first device are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a PDU session with a second device, the PDU session including a QoS flow set, the QoS flow set being associated with a DRB set, each QoS flow in the QoS flow set being associated with at least one QoS identifier parameter, and one QoS identifier parameter in the at least one QoS identifier parameter being associated with one or more DRBs in the DRB set based on an inter-packet association and a QoS flow in the QoS flow set. The memory and the at least one processor coupled to the memory may be further configured to communicate with the second device based on the QoS flow set.

[0010] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0012] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0013] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0015] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0016] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0017] Figure 4 is a diagram illustrating an example mapping of service flows onto data radio bearers (DRBs).

[0018] Figure 5 is a diagram illustrating an example mapping of DL traffic to DRBs.

[0019] Figure 6 is a diagram illustrating example quality of service (QoS) flow differentiation within a protocol data unit (PDU) session.

[0020] Figure 7 is a diagram illustrating an example communication between a first device and a second device.

[0021] Figure 8 is a flow chart of a method of wireless communication.

[0022] Fig. 9 is a flow chart of a method of wireless communication.

[0023] Fig.10 is a flow chart of a method of wireless communication.

[0024] Fig.11 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0025] Fig.12 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0026] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0027] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] For example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described in this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0029] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have wide applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0031] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0032] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0035] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) 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 signals or send signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or send signals to one or more of the other units, or both, via a wireless transmission medium.

[0036] In some aspects, CU 110 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 through an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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 110 may be implemented to communicate with DU 130 for network control and signaling.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 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.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented by an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DUs 130 may correspond to logical nodes that host 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 this architecture, the RUs 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 140 may be controlled by the corresponding DUs 130. In some scenarios, this configuration may enable the implementation of the DUs 130 and CUs 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0039] The SMO framework 105 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 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0040] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 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 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125.

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

[0042] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. 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 to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0043] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. 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), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0045] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0048] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0049] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0050] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0051] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0052] Reference again Figure 1 , in some aspects, the UE 104 may include a QoS component 198. In some aspects, the QoS component 198 may be configured to establish a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the QoS component 198 may be configured to establish a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein one of the DRBs in the set of DRBs is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the QoS component 198 may be configured to establish a PDU session with the second device, the PDU session comprising a QoS flow set, the QoS flow set being associated with a DRB set, each QoS flow in the QoS flow set being associated with at least one QoS identifier parameter, a QoS identifier parameter of the at least one QoS identifier parameter being associated with one or more DRBs in the DRB set based on an inter-packet association and a QoS flow in the QoS flow set. In some aspects, the QoS component 198 may be configured to communicate with the second device based on the QoS flow set.

[0053] In some aspects, the base station 102 may include a QoS component 199. In some aspects, the QoS component 199 may be configured to establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the QoS component 199 may be configured to establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein a DRB in the set of DRBs is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the QoS component 199 may be configured to establish a PDU session with a second device, the PDU session comprising a QoS flow set, the QoS flow set being associated with a DRB set, each QoS flow in the QoS flow set being associated with at least one QoS identifier parameter, a QoS identifier parameter of the at least one QoS identifier parameter being associated with one or more DRBs in the DRB set based on an inter-packet association and a QoS flow in the QoS flow set. In some aspects, the QoS component 199 may be configured to communicate with the second device based on the QoS flow set.

[0054] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0055] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0056] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0057] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling).

[0058] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0059]

[0060] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing may be equal to 2μ*15kHz, where μ is parameter set 0 to 4. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0061] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and 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 a phase tracking RS (PT-RS).

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. 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 (also called SS block (SSB)). 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 not sent via the PBCH (such as the system information block (SIB)), and paging messages.

[0064] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent 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 base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0065] Figure 2D 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 hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0066] Figure 3375. The Controller / Processor 375 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes 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. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0067] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0068] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The reference signal and the symbol on each subcarrier are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0070] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0072] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0073] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The QoS component 198 is used to perform various aspects.

[0075] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The QoS component 199 is used to perform various aspects.

[0076] As used herein, the term "application data unit (ADU)", the term "PDU set", and the term "block" or other similar terms may be used interchangeably and may be used to refer to the smallest data unit that can be exchanged between a network and a user equipment for an application, e.g., application-level granularity. To illustrate the concepts, in a non-limiting example, an application may be used in a user head mounted device (HMD), such as an extended reality (XR) application (e.g., an augmented reality (AR) application, a virtual reality (VR) application, or a mixed reality (MR) application. In such an example, an ADU may be the smallest unit transmitted between a network and an HMD for an XR application. The ADU may be associated with a presentation of one or more frames, which may have different decoding mechanisms (e.g., based on an underlying protocol and a frame refresh rate). In some aspects, XR traffic may be time-sensitive and packet loss-sensitive because the XR traffic may be associated with visual or audio information that may be subject to a timeline (e.g., based on one or more frames) and integrity (e.g., integrity of one or more frames). Various aspects provided herein may enable accurate and timely delivery of ADUs. Various aspects presented herein are not limited to XR applications, and other example applications may include differential QOS specifications across streams, packets, applications, and radio configurations.

[0077] As used herein, the term "data radio bearer (DRB)" may refer to any radio bearer, including a data radio bearer or a multicast / broadcast radio bearer or a signaling radio bearer. A radio bearer may define packet processing on a radio interface. As used herein, the term "quality of service (QoS)" may refer to a measurement of the overall performance of a service experienced by a user of a network. QoS may be implemented at a QoS flow level. In some aspects, each QoS flow packet is classified and marked (e.g., using a QoS flow identifier (QFI) that may be carried in an encapsulation header on N3). In some aspects, a QoS flow classification (which may also be referred to as a type) may be associated with a guaranteed flow bit rate, an unspecified guaranteed flow bit rate, a mission-critical guaranteed flow bit rate, and the like. In some aspects, a DL or UL PDU session information frame may include a QFI field for each packet. A QoS flow may be the finest granularity of QoS differentiation in a PDU session. QFI may be used to identify a QoS flow. User plane services with the same QFI within a PDU session may be associated with the same service forwarding processing (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, and the like). For example, the QFI may be carried in the encapsulation header on N3 (and N9) without any changes to the e2e packet header. The QFI may be used for all PDU session types. The QFI may be unique within a PDU session. The QFI may be dynamically assigned or may be equal to the 5QI. In some aspects, the QoS identifier may be the same as or correspond to the 5QI.

[0078] The ADU may be associated with forward error correction (FEC) information. Such FEC information may be used to correct one or more lost bits in the ADU. For example, when the ADU is sent over a radio network, the ADU may be successfully delivered through various radio protocols. Various radio protocols may include PHY layer transmission based on PDCP, RLC, and HARQ. For example, packetization of the ADU may be performed based on PDCP, segmentation and retransmission of the ADU may be performed based on RLC, and redundancy of the ADU may be performed based on HARQ. The ADU may be sent in a PDU session that may include one or more QoS flows.

[0079] In some aspects, a QoS identifier (which may also be referred to as a "5QI") parameter may be configurable by the network to provide a mapping of QoS flows to data radio bearers (DRBs). In some aspects, a 5QI parameter set may be associated with a 5QI, which may be a pointer to a set of QoS characteristics, such as resource type (e.g., indicating whether dedicated network resources associated with a QoS flow level guaranteed flow bit rate (GFBR) value are permanently allocated (e.g., by an admission control function in a radio base station)), priority level, packet delay or packet error rate, average window, maximum data burst size, etc. The 5QI parameter set may include access node-specific parameters that control QoS transmission (e.g., forwarding) processing for QoS flows (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, drop timers, reordering timers, reassembly timers, retransmission timers, etc.). In some aspects, an ADU may belong to a flow, and each flow may have at least one QoS rule match to map packets from a given flow to a DRB. The matching filter rule can be specific to the flow or a full match filter (the filter is not specific to the flow, but applies to a set of flows, such as all flows) so that the packet can be routed to the corresponding DRB. Each DRB can be mapped to a logical channel with an associated priority so that it can be sent based on each logical channel prioritization (LCP) rule in the MAC TB UL.

[0080] Figure 4 FIG. 4 is a diagram illustrating an example mapping of service flows to DRBs. Figure 4 , the application / service layer 408 may provide data packets 410 to a user plane function (UPF) 406 or a UE 402. To exchange the data packets 410 (e.g., DL packets in the data packets 410), the UPF 406 may perform packet detection based on a packet detection rule (PDR) 462, and may classify the data packets 410 accordingly for QoS flow marking. The PDR 462 may also include a pointer to a forwarding action rule (FAR), a QoS enforcement rule (QER), a usage report rule (URR), or a buffer action rule (BAR). In some aspects, QoS flow marking may create different service classifications for different types of network services. In some aspects, QoS flow marking may include changing a field within a packet at layer 2 or layer 3. In some aspects, the UPF 406 may mark packets in the data packets 410 onto one or more different QoS flows 414. In some aspects, the SMF may provide the QFI and QoS profiles to the RAN, and may provide the UPF 406 with information to enable classification, bandwidth implementation, and marking of user plane services, such as the DL PDR of the DL portion containing the SDF template and the UL PDR of the UL portion containing the SDF template, PDR priority values, QoS-related information, corresponding packet marking information, or reflected QoS indications.

[0081] In some aspects, the UPF 406 may establish a PDU session 416 with an access network (AN) 404 to exchange data packets with the UE 402. In some aspects, to exchange data packets 410, the UE 402 may map one or more UL packets in the data packets 410 to one or more QoS flows 414 and apply a QoS flow marking based on a QoS rule set 412. In some aspects, the UE may also map the one or more QoS flows 414 to AN resources of the AN 404. In some aspects, the AN 404 may map the one or more QoS flows 414 to AN resources of the AN 404. The SMF may generate a QoS rule set 412 and provide to the UE 402 (e.g., by generating a QoS rule for each service data flow (SDF) that may be mapped to one or more QoS flows 414): a QoS rule identifier, a QFI in the QoS rule set to the QFI of the QoS flow to which the Policy and Charging Control (PCC) rule is bound, a packet filter set for the QoS rule generated from the UL SDF filter or DL ​​SDF filter of the PCC rule, a QoS rule priority value set to the priority value of the PCC rule for which the QoS rule is generated, QoS flow level QoS parameters, and the like.

[0082] In some wireless communication systems, one QoS flow may be mapped to one DRB, and several QoS flows may be mapped to the same DRB. Figure 5 FIG. 5 is a diagram illustrating an example mapping of DL traffic to DRBs. Figure 5 , an edge server 506 associated with an application 562 may provide data in a service flow set 512 to a radio access network (RAN) 504. The service flow set 512 may be mapped to a QoS flow set 510 (e.g., by the RAN 504). The QoS flow set 510 may also be mapped to a DRB set 514. In some aspects, one QoS flow may be mapped to one DRB, and several QoS flows may be mapped to the same DRB. The UE 502 may receive the data in the QoS flow set 510 based on the DRB set 514, and may use the data in an application 522. For example, the application 522 may include video or audio playback, and the data may be video or audio data.

[0083] Figure 6 FIG. 6 is a diagram illustrating example QoS flow differentiation within a PDU session. Figure 6, an application server 610 associated with a data network (DN) 608 may send data to a UPF 606 via one or more IP flows 614. The one or more IP flows 614 may be associated with one or more applications 612. The UPF 606 may perform packet inspection and classify the data in the one or more IP flows 614 into a QoS flow set 630 based on a QFI insertion 620 (which may correspond to a marking).

[0084] The SDF policy sets 622 may be associated with different QoS flows 630. The UPF 606 may send the data in the QoS flow set 630 to the gNB 604 based on the PDU session 640. At 650, the gNB 604 may map the QoS flow set 630 to the DRB set 652. Based on the DRB set 652, the data in the QoS flow set 630 may be sent from the gNB 604 to the UE 602. The data in the QoS flow set 630 may be available to an application on the UE 602 (which may correspond to an application associated with the application 612).

[0085] In some wireless communication systems, 5QI parameters may be configured per flow, either explicitly or by default rules, for a given flow. Since the rule is fixed for a given flow, all services on the flow may be processed with the same QOS or provided with the same QOS. For example, in the UL, for a PDU session of type IP or Ethernet, the UE may evaluate the UL packets for the UL packet filters in the packet filter set in the QoS rule in ascending order based on the priority value of the QoS rule until a matching QoS rule is found (i.e., its packet filter matches the UL packet), or discard the UL data packet if no matching QoS rule is found. For unstructured type PDU sessions, the default QoS rule does not contain a packet filter set, and all UL packets may be allowed. More than one QoS flow may be mapped to one DRB. The mapping between QoS flows and RB characteristics may be fixed at the RB level, and all flows may receive the same forwarding treatment.

[0086] In some wireless communication systems, 5QI parameters may be matched to incoming packets based on protocol content (e.g., which may be referred to as a 5-tuple). In some aspects, a 5-tuple may refer to a set of values ​​used to send a control protocol / Internet protocol (TCP / IP) connection. For example, a 5-tuple may include a source IP address / port number, a destination IP address / port number, and the protocol used. When there are different types of packets with varying importance (e.g., and associated specifications regarding latency, reliability, etc.) and varying decoding specifications (e.g., different FECs) flowing through the same QoS flow (e.g., XR applications for different frames), the various aspects provided herein may enable different QoS to be provided to different packets within a single QoS flow. The flexibility of QoS for different packets of a single QoS flow can improve the user experience of the application.

[0087] Figure 7 700 is a diagram illustrating an example communication between a first device and a second device. In some aspects, the first device may be a UE 702. In some aspects, the second device may be a network entity 704. The network entity may be a network node. In some aspects, the network entity 704 may be a base station that may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the network entity may be part of a terrestrial or non-terrestrial network or a combination thereof.

[0088] like Figure 7 As illustrated in FIG. 7 , UE 702 may establish a PDU session 708 with network entity 704 and may exchange communications 706 accordingly. In some aspects, such as in conjunction with Figures 4 to 6 As described, the PDU session 708 may include one or more QoS flows such as QoS flow 720A and QoS flow 720B. In some aspects, each QoS flow may be associated with (e.g., have) multiple 5QI parameter sets based on what traffic patterns are expected on the QoS flow. Each 5QI parameter set may include access node specific parameters that control QoS transmission (e.g., forwarding) processing (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, discard timers, reordering timers, reassembly timers, retransmission timers, etc.) for the QoS flow.

[0089] As an example, QoS flow 720A may be associated with 5QI parameter set A 730A and 5QI parameter set B 730B. QoS flow 720B may be associated with 5QI parameter set D 730D and 5QI parameter set E 730E. In some aspects, multiple packets on the same QoS flow may or may not have interdependencies and may belong to various sub-flows at the application level.

[0090] In some aspects, each QoS flow in one or more QoS flows (such as QoS flow 720A or QoS flow 720B) may be mapped to a DRB (such as DRB 710A or DRB 710B). In some aspects, each 5QI associated with a 5QI parameter belonging to a QoS flow (such as 5QI parameter set A 730A, 5QI parameter set B 730B, and 5QI parameter set C 730C) may be mapped to the same DRB or a different DRB (e.g., based on inter-packet dependencies for the QoS flow). The terms "inter-packet dependency" and "inter-packet association" may be used interchangeably and may refer to an association based on the association of data in a packet. For example, packets carrying related and defined associated video data or audio data (e.g., as part of a video / audio playback) may have inter-packet associations or inter-packet dependencies. For example, 5QI parameter set A 730A and 5QI parameter set B 730B belonging to QoS flow 720A may be mapped to DRB 710A. 5QI parameter set C 730C, which also belongs to QoS flow 720A, may be mapped to DRB 710B.

[0091] In some aspects, based on the type of 5QI, the PDCP or RLC radio bearer associated with each of the DRB 710A or DRB 710B may have a different set of configuration parameters. For example, for 5QI parameter set A 730A, the DRB 710A may have a UL PDCP discard timer of 100 ms, a DL PDCP reordering timer of 180 ms, a DL RLC reassembly timer of 40 ms, and a UL RLC polling retransmission timer of 40 ms. For 5QI parameter set B 730B, the DRB 710A may have a UL PDCP discard timer of 50 ms, a DL PDCP reordering timer of 80 ms, a DL RLC reassembly timer of 20 ms, and a UL RLC polling retransmission timer of 20 ms.

[0092] In some aspects, each packet in the communication 706 may be mapped to a bearer to identify a matching 5QI (and associated 5QI parameters and associated bearers (e.g., DRBs)) based on protocol content (e.g., 5-tuple) or traffic characteristics. For example, packet 740A may be mapped to DRB 710A, and packet 740B may be mapped to DRB 710B. In some aspects, traffic characteristics may be derived by application indication or in a modem (e.g., transceiver) at the UE 702 or network entity 704. For example, an application may explicitly indicate a 5QI associated with a packet (e.g., 5QI information provided to application-level logic), or a modem at a UE may select a 5QI based on application service characteristics, such as data transmission periodicity (e.g., cyclic / periodic transmission or non-cyclic / sporadic transmission) and associated statistics, periodicity (data transmission interval at the application layer) and associated statistics, whether the application is synchronized with network time and associated statistics, application data size (e.g., number of ADUs) and associated statistics, data delivery guarantees (e.g., deadlines, latency, bandwidth, etc.) and associated statistics, tolerance to interference, tolerance to loss, criticality, or other information about the service that the modem is able to obtain or determine.

[0093] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a first device (e.g., UE 104, base station 102, UE 702, network entity 704, apparatus 1104, network entity 1102, network entity 1102). The first device may be a UE or a base station. The second device may be a base station or a UE.

[0094] At 802, a first device may establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. For example, a UE 702 or a network entity 704 may establish a PDU session 708 with the network entity 704 or the UE 702. In some aspects, 802 may be performed by a QoS component 198 or a QoS component 199. In some aspects, each DRB in the set of DRBs is associated with a PDCP or an RLC, and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a state timer, a control information update timer, or a polling retransmission timer that is different from the second set of one or more configuration parameters. In some aspects, one of the plurality of QoS identifier parameters for a single QoS flow is associated with a plurality of DRBs in the set of DRBs. In some aspects, one of a plurality of QoS identifier parameters for a single QoS flow is associated with a single DRB in a set of DRBs based on an inter-packet association. In some aspects, each packet associated with each QoS flow in the set of QoS flows is associated with one of a plurality of QoS identifier parameters based on at least one of a set of protocol content or a set of service characteristics. In some aspects, a first device may include at least one of a transceiver or an antenna coupled to at least one processor configured to communicate with a second device, wherein at least one of the set of service characteristics or the QoS identifier parameter is provided by an application or derived at the transceiver.

[0095] At 804, the first device may communicate with the second device based on the QoS flow set. For example, UE 702 or network entity 704 may communicate with the second device (e.g., network entity 704 or UE 702) based on the QoS flow set. In some aspects, 804 may be performed by QoS component 198 or QoS component 199.

[0096] Fig. 9Flowchart 900 of a method of wireless communication. The method may be performed by a first device (e.g., UE 104, base station 102, UE 702, network entity 704, apparatus 1104, network entity 1102, network entity 1102). The first device may be a UE or a base station. The second device may be a base station or a UE. In some aspects, each QoS flow in a QoS flow set is associated with a plurality of QoS identifier parameters. In some aspects, a first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a state timer, a control information update timer, or a polling retransmission timer that is different from a second set of one or more configuration parameters. In some aspects, each QoS flow in a QoS flow set is associated with at least one QoS identifier parameter, and one QoS identifier parameter in at least one QoS identifier parameter for a single QoS flow is associated with a plurality of DRBs in a DRB set. In some aspects, each QoS flow in a QoS flow set is associated with at least one QoS identifier parameter, and one QoS identifier parameter in at least one QoS identifier parameter for a single QoS flow is associated with a single DRB in a DRB set based on an inter-packet association. In some aspects, each packet associated with each QoS flow in the set of QoS flows is associated with a QoS identifier parameter of the plurality of QoS identifier parameters based on at least one of a set of protocol content or a set of traffic characteristics. In some aspects, the first device may include at least one of a transceiver or an antenna coupled to at least one processor configured to communicate with the second device, wherein at least one of the set of traffic characteristics or the QoS identifier parameter is provided by an application or derived at the transceiver.

[0097] At 902, a first device may establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein a DRB in the set of DRBs is associated with a PDCP or an RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. For example, a UE 702 or a network entity 704 may establish a PDU session 708 with a network entity 704 or a UE 702. In some aspects, 902 may be performed by a QoS component 198 or a QoS component 199.

[0098] At 904, the first device may communicate with the second device based on the QoS flow set. For example, the UE 702 or the network entity 704 may communicate with the second device (e.g., the network entity 704 or the UE 702) based on the QoS flow set. In some aspects, 904 may be performed by the QoS component 198 or the QoS component 199.

[0099] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a first device (e.g., UE 104, base station 102, UE 702, network entity 704, apparatus 1104, network entity 1102, network entity 1102). The first device may be a UE or a base station. The second device may be a base station or a UE.

[0100] At 1002, a first device may establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with at least one QoS identifier parameter, one of the at least one QoS identifier parameter being associated with one or more DRBs in the set of DRBs based on an inter-packet association and one of the QoS flows in the set of QoS flows. For example, a UE 702 or a network entity 704 may establish a PDU session 708 with the network entity 704 or the UE 702. In some aspects, 1002 may be performed by a QoS component 198 or a QoS component 199. In some aspects, each DRB in the set of DRBs is associated with a PDCP or an RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a state timer, a control information update timer, or a polling retransmission timer that is different from the second set of one or more configuration parameters. In some aspects, each QoS flow in the set of QoS flows is associated with a plurality of QoS identifier parameters. In some aspects, each packet associated with each QoS flow in the set of QoS flows is associated with a QoS identifier parameter in the plurality of QoS identifier parameters based on at least one of a set of protocol content or a set of traffic characteristics. In some aspects, the first device may further include at least one of a transceiver or an antenna coupled to at least one processor configured to communicate with the second device, wherein at least one of the set of traffic characteristics or the QoS identifier parameter is provided by an application or derived at the transceiver.

[0101] At 1004, the first device may communicate with the second device based on the QoS flow set. For example, the UE 702 or the network entity 704 may communicate with the second device (e.g., the network entity 704 or the UE 702) based on the QoS flow set. In some aspects, 1004 may be performed by the QoS component 198 or the QoS component 199.

[0102] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, a satellite system module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the satellite system module 1116 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1124 communicates with the UE 104 and / or with a RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1124 / application processor 1106 to perform various functions described herein when executed by the cellular baseband processor 1124 / application processor 1106. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software. The cellular baseband processor 1124 / application processor 1106 may be a component of the UE 350 and may include at least one of a memory 360 and / or a TX processor 368, an RX processor 356, and a controller / processor 359.In one configuration, the device 1104 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1124 and / or the application processor 1106, while in another configuration, the device 1104 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1104.

[0103] As discussed herein, the QoS component 198 may be configured to establish a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the QoS component 198 may be configured to establish a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein a DRB in the set of DRBs is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the QoS component 198 may be configured to establish a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with at least one QoS identifier parameter, one of the at least one QoS identifier parameter being associated with one or more DRBs in the set of DRBs based on an inter-packet association and a QoS flow in the set of QoS flows. In some aspects, the QoS component 198 may be configured to communicate with the second device based on the set of QoS flows. The QoS component 198 may be in the cellular baseband processor 1124, the application processor 1106, or in both the cellular baseband processor 1124 and the application processor 1106. The QoS component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1104 may include a variety of components configured for various functions. In one configuration, the apparatus 1104 (and specifically, the cellular baseband processor 1124 and / or the application processor 1106) may include means for establishing a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the apparatus 1104 may include means for establishing a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein one of the DRBs in the set of DRBs is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.In some aspects, the apparatus 1104 may include a component for establishing a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with at least one QoS identifier parameter, one of the at least one QoS identifier parameter being associated with one or more DRBs in the set of DRBs based on an inter-packet association and a QoS flow in the set of QoS flows. In some aspects, the apparatus 1104 may include a component for communicating with the second device based on the set of QoS flows. The component may be a QoS component 198 of the apparatus 1104 configured to perform the functions recited by the component. As described herein, the apparatus 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the component.

[0104] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the component 199, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both a DU 1230 and a RU 1240; or a RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link, such as an F1 interface. DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0105] As discussed herein, the QoS component 199 is configured to establish a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the QoS component 199 may be configured to establish a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein one of the DRBs in the set of DRBs is associated with a PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter. In some aspects, the QoS component 199 may be configured to establish a PDU session with a second device, the PDU session comprising a set of QoS flows, the set of QoS flows being associated with a set of DRBs, each QoS flow in the set of QoS flows being associated with at least one QoS identifier parameter, one of the at least one QoS identifier parameters being associated with one or more DRBs in the set of DRBs based on an inter-packet association and one of the QoS flows in the set of QoS flows. In some aspects, the QoS component 199 may be configured to communicate with the second device based on the QoS flow set. The QoS component 199 may be within one or more processors of one or more of the CU 1210, the DU 1230, and the RU 1240. The QoS component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for establishing a PDU session with a second device, the PDU session including a QoS flow set, the QoS flow set being associated with a DRB set, each QoS flow in the QoS flow set being associated with multiple QoS identifier parameters to provide different QoS to different packets within a single QoS flow. In some aspects, the network entity 1202 may include components for establishing a PDU session with a second device, the PDU session including a set of QoS flows, the set of QoS flows being associated with a set of DRBs, wherein a DRB in the set of DRBs is associated with the PDCP or RLC and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.In some aspects, the network entity 1202 may include a component for establishing a PDU session with a second device, the PDU session including a QoS flow set, the QoS flow set being associated with a DRB set, each QoS flow in the QoS flow set being associated with at least one QoS identifier parameter, one QoS identifier parameter in the at least one QoS identifier parameter being associated with one or more DRBs in the DRB set based on an inter-packet association and a QoS flow in the QoS flow set. In some aspects, the network entity 1202 may include a component for communicating with the second device based on the QoS flow set. The component may be a QoS component 199 of the network entity 1202 configured to perform the functions recorded by the component. As described herein, the network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recorded by the component.

[0106] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0107] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. 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. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while" do not mean an instantaneous time relationship or reaction. That is, these phrases, such as "when ...", do not mean an instantaneous action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a condition is met, but no specific or instantaneous time limit is required for the occurrence of an action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device by the set of devices. All structural and functional equivalents that are known to those of ordinary skill in the art or will be known later throughout the elements of the various aspects described in this disclosure are explicitly incorporated herein by reference, and are covered by the claims. In addition, anything disclosed herein is not intended to be dedicated to the public, regardless of whether such disclosures are explicitly recorded in the claims. "Module", "mechanism", "element", "equipment" and other words cannot replace the word "component". Therefore, no claim element will be understood as a functional component unless the element is explicitly recorded using the phrase "component for...".

[0108] As used in this disclosure outside of the claims, the phrase "based on" includes all interpretations and should not be limited to any single interpretation unless specifically recorded or indicated as such. For example, the phrase "based on A" (where "A" may be information, a condition, a factor, etc.) may be interpreted as: "at least based on A", "partially based on A", "at least partially based on A", "only based on A" or "based on A alone". Therefore, as disclosed herein, in one aspect, "based on A" may refer to "at least based on A". In another aspect, "based on A" may refer to "partially based on A". In another aspect, "based on A" may refer to "at least partially based on A". In another aspect, "based on A" may refer to "only based on A". In another aspect, "based on A" may refer to "based on A alone". In another aspect, "based on A" may refer to any combination of alternative interpretations. As used in the claims, the phrase "based on A" should be interpreted as "at least based on A", unless otherwise specifically stated.

[0109] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0110] Aspect 1 is a method for communicating at a first device, the method comprising: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a quality of service (QoS) flow set, the QoS flow set being associated with a data radio bearer (DRB) set, each QoS flow in the QoS flow set being associated with multiple QoS identifier parameters to provide different QoS to different packets within a single QoS flow; and communicating with the second device based on the QoS flow set.

[0111] Aspect 2 is a method according to Aspect 1, wherein each DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.

[0112] Aspect 3 is a method according to any one of Aspects 1 to 2, wherein the first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer or a polling retransmission timer that is different from the second set of one or more configuration parameters.

[0113] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the single QoS flow having the multiple QoS identifier parameters is associated with multiple DRBs in the DRB set, wherein each QoS identifier parameter in the multiple QoS identifier parameters is supported by a corresponding DRB in the DRB set.

[0114] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the single QoS flow having the multiple QoS identifier parameters is associated with a single DRB in the DRB set, and the single DRB is associated with support for multiple configuration parameter sets corresponding to each QoS identifier parameter in the multiple QoS identifier parameters.

[0115] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein each packet associated with each QoS flow in the QoS flow set is associated with one QoS identifier parameter among the multiple QoS identifier parameters based on at least one of a protocol content set or a service characteristic set.

[0116] Aspect 7 is a method according to any one of aspects 1 to 6, wherein at least one of the service characteristic set or QoS identifier parameter is provided by an application or derived at the transceiver.

[0117] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein each packet associated with a QoS identifier parameter in the multiple QoS identifier parameters is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

[0118] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein each packet associated with a QoS identifier parameter in the multiple QoS identifier parameters is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, wherein the second device is a user equipment (UE) and the first device is a base station.

[0119] Aspect 10 is a method for communicating at a first device, the method comprising: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a quality of service (QoS) flow set, the QoS flow set being associated with a data radio bearer (DRB) set, wherein one DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter; and communicating with the second device based on the QoS flow set.

[0120] Aspect 11 is a method according to aspect 10, wherein each QoS flow in the set of QoS flows is associated with a plurality of QoS identifier parameters.

[0121] Aspect 12 is a method according to any one of Aspects 10 to 11, wherein the first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer, or a polling retransmission timer that is different from the second set of one or more configuration parameters.

[0122] Aspect 13 is a method according to any one of Aspects 10 to 12, wherein each QoS flow in the QoS flow set is associated with at least one QoS identifier parameter, and wherein at least one QoS flow in the QoS flow set is associated with multiple DRBs in the DRB set, wherein each QoS identifier parameter in the at least one QoS identifier parameter is supported by a corresponding DRB in the DRB set.

[0123] Aspect 14 is a method according to any one of Aspects 10 to 13, wherein each QoS flow in the QoS flow set is associated with at least one QoS identifier parameter, and wherein at least one QoS flow in the QoS flow set is associated with a single DRB in the DRB set, and the single DRB is associated with support for multiple configuration parameter sets corresponding to each QoS identifier parameter in the at least one QoS identifier parameter.

[0124] Aspect 15 is a method according to any one of Aspects 10 to 14, wherein each packet associated with each QoS flow in the QoS flow set is associated with one QoS identifier parameter of the at least one QoS identifier parameter based on at least one of a protocol content set or a service characteristic set.

[0125] Aspect 16 is a method according to any one of aspects 10 to 15, wherein at least one of the service characteristic set or QoS identifier parameter is provided by an application or derived at the transceiver.

[0126] Aspect 17 is a method according to any one of Aspects 10 to 16, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

[0127] Aspect 18 is a method according to any one of Aspects 10 to 17, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the second device is a user equipment (UE) and the first device is a base station.

[0128] Aspect 19 is a method for communicating at a first device, the method comprising: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a quality of service (QoS) flow set, the QoS flow set being associated with a data radio bearer (DRB) set, each QoS flow in the QoS flow set being associated with at least one QoS identifier parameter, one QoS identifier parameter of the at least one QoS identifier parameter being associated with one or more DRBs in the DRB set based on an inter-packet association and a QoS flow in the QoS flow set; and communicating with the second device based on the QoS flow set.

[0129] Aspect 20 is a method according to Aspect 19, wherein each DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.

[0130] Aspect 21 is a method according to any one of Aspects 19 to 20, wherein the first set of one or more configuration parameters includes at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer or a polling retransmission timer that is different from the second set of one or more configuration parameters.

[0131] Aspect 22 is a method according to any one of aspects 19 to 21, wherein each QoS flow in the set of QoS flows is associated with a plurality of QoS identifier parameters.

[0132] Aspect 23 is a method according to any one of Aspects 19 to 22, wherein each packet associated with each QoS flow in the QoS flow set is associated with a single QoS identifier parameter among the multiple QoS identifier parameters based on at least one of a protocol content set or a service characteristic set.

[0133] Aspect 24 is a method according to any one of aspects 19 to 23, wherein at least one of the service characteristic set or QoS identifier parameter is provided by an application or derived at the transceiver.

[0134] Aspect 25 is a method according to any one of Aspects 19 to 24, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

[0135] Aspect 26 is a method according to any one of Aspects 19 to 25, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the second device is a user equipment (UE) and the first device is a base station.

[0136] Aspect 27 is an apparatus for wireless communication at a network entity, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 9 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0137] Aspect 28 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 1 to 9.

[0138] In aspect 29, the apparatus according to aspect 27 or 28 further comprises at least one of a transceiver or an antenna.

[0139] Aspect 30 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 1 to 9.

[0140] Aspect 31 is an apparatus for wireless communication at a network entity, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 10 to 18 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0141] Aspect 32 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 10 to 18.

[0142] In aspect 33, the apparatus according to aspect 31 or 32 further comprises at least one of a transceiver or an antenna.

[0143] Aspect 34 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 10 to 18.

[0144] Aspect 35 is an apparatus for wireless communication at a network entity, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 19 to 26 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0145] Aspect 36 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 19 to 26.

[0146] In aspect 37, the apparatus according to aspect 35 or 36 further comprises at least one of a transceiver or an antenna.

[0147] Aspect 38 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 19 to 26.

Claims

1. An apparatus for communicating at a first device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow; as well as Communicate with the second device based on the QoS flow set.

2. The apparatus of claim 1, wherein each DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.

3. The apparatus of claim 2, wherein the first set of the one or more configuration parameters comprises at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer, or a polling retransmission timer that is different from the second set of the one or more configuration parameters.

4. The apparatus of claim 1 , wherein the single QoS flow having the plurality of QoS identifier parameters is associated with a plurality of DRBs in the DRB set, wherein each of the plurality of QoS identifier parameters is supported by a corresponding DRB in the DRB set.

5. An apparatus according to claim 1, wherein the single QoS flow having the multiple QoS identifier parameters is associated with a single DRB in the DRB set, and the single DRB is associated with support for multiple configuration parameter sets corresponding to each QoS identifier parameter in the multiple QoS identifier parameters.

6. The apparatus of claim 1, wherein each packet associated with each QoS flow in the set of QoS flows is associated with one of the plurality of QoS identifier parameters based on at least one of a protocol content set or a traffic characteristic set.

7. The apparatus of claim 6, further comprising at least one of a transceiver or an antenna coupled to the at least one processor configured to communicate with the second device, wherein at least one of the service characteristic set or the QoS identifier parameter is provided by an application or derived at the transceiver.

8. The apparatus of claim 1 , wherein each packet associated with a QoS identifier parameter in the plurality of QoS identifier parameters is routed to an associated DRB in the set of DRBs that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

9. An apparatus according to claim 1, wherein each packet associated with a QoS identifier parameter in the multiple QoS identifier parameters is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, wherein the second device is a user equipment (UE) and the first device is a base station.

10. An apparatus for communicating at a first device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), wherein one of the set of DRBs is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC) and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter; as well as Communicate with the second device based on the QoS flow set.

11. The apparatus of claim 10, wherein each QoS flow in the set of QoS flows is associated with a plurality of QoS identifier parameters.

12. The apparatus of claim 10, wherein the first set of the one or more configuration parameters comprises at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer, or a polling retransmission timer that is different from the second set of the one or more configuration parameters.

13. The apparatus of claim 10, wherein each QoS flow in the QoS flow set is associated with at least one QoS identifier parameter, and wherein at least one QoS flow in the QoS flow set is associated with a plurality of DRBs in the DRB set, wherein each QoS identifier parameter in the at least one QoS identifier parameter is supported by a corresponding DRB in the DRB set.

14. An apparatus according to claim 10, wherein each QoS flow in the QoS flow set is associated with at least one QoS identifier parameter, and wherein at least one QoS flow in the QoS flow set is associated with a single DRB in the DRB set, and the single DRB is associated with support for multiple configuration parameter sets corresponding to each QoS identifier parameter in the at least one QoS identifier parameter.

15. The apparatus of claim 10, wherein each packet associated with each QoS flow in the set of QoS flows is associated with one of the at least one QoS identifier parameters based on at least one of a protocol content set or a traffic characteristic set.

16. The apparatus of claim 15, further comprising at least one of a transceiver or an antenna coupled to the at least one processor configured to communicate with the second device, wherein at least one of the service characteristic set or the QoS identifier parameter is provided by an application or derived at the transceiver.

17. An apparatus according to claim 10, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

18. The apparatus of claim 10, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the second device is a user equipment (UE) and the first device is a base station.

19. An apparatus for communicating at a first device, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), each QoS flow in the set of QoS flows being associated with at least one QoS identifier parameter, one QoS identifier parameter of the at least one QoS identifier parameter being associated with one or more DRBs in the set of DRBs based on an inter-packet association and a QoS flow in the set of QoS flows; as well as Communicate with the second device based on the QoS flow set.

20. An apparatus according to claim 19, wherein each DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.

21. The apparatus of claim 20, wherein the first set of the one or more configuration parameters comprises at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer, or a polling retransmission timer that is different from the second set of the one or more configuration parameters.

22. The apparatus of claim 19, wherein each QoS flow in the set of QoS flows is associated with a plurality of QoS identifier parameters.

23. The apparatus of claim 19, wherein each packet associated with each QoS flow in the set of QoS flows is associated with a single QoS identifier parameter of the at least one QoS identifier parameter based on at least one of a protocol content set or a traffic characteristic set.

24. The apparatus of claim 23, further comprising at least one of a transceiver or an antenna coupled to the at least one processor configured to communicate with the second device, wherein at least one of the service characteristic set or the QoS identifier parameter is provided by an application or derived at the transceiver.

25. The apparatus of claim 19, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the first device is a user equipment (UE) and the second device is a base station.

26. An apparatus according to claim 19, wherein each packet associated with a QoS identifier parameter in the at least one QoS identifier parameter is routed to an associated DRB in the DRB set that supports the QoS identifier parameter, and wherein the second device is a user equipment (UE) and the first device is a base station.

27. A method for communicating at a first device, the method comprising: establishing a protocol data unit (PDU) session with a second device, the PDU session comprising a set of quality of service (QoS) flows, the set of QoS flows being associated with a set of data radio bearers (DRBs), each QoS flow in the set of QoS flows being associated with a plurality of QoS identifier parameters to provide different QoS to different packets within a single QoS flow; as well as Communicate with the second device based on the QoS flow set.

28. A method according to claim 27, wherein each DRB in the DRB set is associated with a packet data convergence protocol (PDCP) or a radio link protocol (RLC), and is associated with a first set of one or more configuration parameters based on a first QoS identifier parameter and a second set of one or more configuration parameters based on a second QoS identifier parameter.

29. The method of claim 28, wherein the first set of one or more configuration parameters comprises at least one of a discard timer, a reordering timer, a reassembly timer, a status timer, a control information update timer, or a polling retransmission timer that is different from the second set of the one or more configuration parameters.

30. The method of claim 27, wherein the single QoS flow having the multiple QoS identifier parameters is associated with multiple DRBs in the DRB set, wherein each QoS identifier parameter in the multiple QoS identifier parameters is supported by a corresponding DRB in the DRB set.

Images