In-band mapping to multiple radio bearers

Abstract

A method, apparatus, and computer program product are provided. The method includes receiving, from a network node, downlink (DL) traffic of a quality-of-service (QoS) flow on a first data radio bearer (DRB) of at least two DRBs, wherein: the QoS flow is mapped to at least a first DRB and a second DRB of the at least two DRBs; and the DL traffic of the QoS flow includes a data protocol header that includes an indication of a 1-to-N mapping between the QoS flow and the at least two DRBs; determining that the QoS flow is mapped to at least the first DRB and the second DRB based at least in part on the indication of the 1-to-N mapping; and in response to the determination, initiating to the network node, uplink (UL) traffic of the QoS flow on at least the first DRB and the second DRB.

Description

IN-BAND MAPPING TO MULTIPLE RADIO BEARERSCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application is related to U.S. Application No. 63 / 713,838, filed October 30, 2024, entitled “REMAPPING ONE OR MORE QUALITY OF SERVICE FLOWS,” the disclosure of which is incorporated by reference in its entirety.TECHNOLOGICAL FIELD

[0002] An example embodiment relates generally relates to wireless communication.BACKGROUND

[0003] Applications such as extended reality or traffic related to artificial intelligence or machine learning may require a very high data rate, for example from (100) Mbps to (10) Gbps or even higher. There is a challenge in how to support such high data rates in wireless communication systems.SUMMARY

[0004] The scope of protection sought for various example embodiments is set out by the claims. The example embodiments and features, if any, described in this specification that do not fall under the scope of the claims are to be interpreted as examples useful for understanding various embodiments.

[0005] In one example embodiment, provided is a user device (100, 10) for wireless communication, which may include: at least one processor (12); and at least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the user device (100, 10) to at least: receive (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); determine (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and inresponse to the determination, initiate (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0006] In another example embodiment, provided is a method (700), which may include: receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and in response to the determination, initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0007] In another example embodiment, provided is a user device (100, 10), which may include: means for receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); means for determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and in response to the determination, means for initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0008] In another example embodiment, a network node (104, 10) for wireless communication, which may include: at least one processor (12); and at least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the network node (104, 10) to at least: initiate (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and in accordance with the 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), receive (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

[0009] In another example embodiment, provided is a method (800), which may include: initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and in accordance with the 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

[0010] In another example, provided is a network node (104, 10), which may include: means for initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and in accordance with the 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), means for receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and where:

[0012] FIG. 1 illustrates an example of a wireless communication network and an example apparatus;

[0013] FIG. 2 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure;

[0014] FIG. 3 illustrates a signal flow diagram;

[0015] FIG. 4A illustrates a signal flow diagram showing configuration of I -to- A mapping for parallelization at the DRB level;

[0016] FIG. 4B illustrates a signal flow diagram showing forwarding of UL traffic on multiple DRBs in parallel;

[0017] FIG. 5 shows a signal diagram;

[0018] FIG. 6 shows a signal diagram;

[0019] FIG. 7 illustrates a flowchart of a method for DRB level parallelization that may be performed by a UE in accordance with example embodiments of the present disclosure;

[0020] FIG. 8 illustrates a flowchart of a method for DRB level parallelization that may be performed by a network device in accordance with example embodiments of the present disclosure;

[0021] FIG. 9 illustrates a flowchart of a method for DRB level parallelization that may be performed by a UE in accordance with example embodiments of the present disclosure; and

[0022] FIG. (10) illustrates a flowchart of a method for DRB level parallelization that may be performed by a network device in accordance with example embodiments of the present disclosure.DETAILED DESCRIPTION

[0023] FIG. 1 depicts an example of a simplified wireless communication network showing some physical and logical entities. The connections shown in FIG. 1 may be physicalconnections or logical connections. It is apparent to a person skilled in the art that the wireless communication network may also comprise other physical and logical entities than those shown in FIG. 1.

[0024] The example wireless communication network shown in FIG. 1 includes a radio access network (RAN) and a core network 110.

[0025] FIG. 1 shows user devices (100), 102 configured to be in a wireless connection on one or more communication channels in a radio cell with a network node (104) of a radio access network. As used herein, the terms user equipment (UE) and user device may be referred to interchangeably.

[0026] The network node (104) may comprise a computing device configured to control the radio resources of the network node (104) and to be in a wireless connection with one or more user devices (100), (102). The network node (104) may also be referred to as a network node, base station, a base transceiver station (BTS), an access point, a cell site, an access node, a radio access network node, a RAN node, or a network device.

[0027] The network node (104) may be, for example, an evolved NodeB (abbreviated as eNB or eNodeB), or a next generation evolved NodeB (abbreviated as ng-eNB), or a next generation NodeB (abbreviated as gNB or gNodeB), providing the radio cell. The network node (104) may include or be coupled to transceivers. From the transceivers of the network node (104), a connection may be provided to an antenna unit that establishes a bi-directional radio link to one or more user devices (100), (102). The antenna unit may comprise an antenna or antenna element, or a plurality of antennas or antenna elements.

[0028] In one embodiment, an network node (104) may comprise: a radio unit (RU) 103 may include a radio transceiver (TRX), i.e., a transmitter (Tx) and a receiver (Rx); one or more distributed units (DUs) 105 that may be used for the so-called Layer 1 (LI) processing and realtime Layer 2 (L2) processing; and a central unit (CU) 108 (also known as a centralized unit) that may be used for non-real-time L2 and Layer 3 (L3) processing. The CU 108 may be connected to the one or more DUs 105 for example via an El interface. Such an embodiment of the network node (104) may enable the centralization of CUs relative to the cell sites and DUs, whereas DUs may be more distributed and may even remain at cell sites. The CU and DU together may also be referred to as baseband or a baseband unit (BBU). The CU and DU may also be comprised in a radio access point (RAP).

[0029] The CU 108 may be a logical node hosting radio resource control (RRC), service data adaptation protocol (SDAP) and / or packet data convergence protocol (PDCP), of the NR protocol stack for a network node (104). The CU 108 may comprise a control plane (CU-CP), which may be a logical node hosting the RRC and the control plane part of the PDCP protocol of the NR protocol stack for the network node (104). The CU 108 may further comprise a user plane (CU-UP), which may be a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol of the CU for the network node (104).

[0030] The DU 105 may be a logical node hosting radio link control (RLC), medium access control (MAC) and / or physical (PHY) layers of the NR protocol stack for the network node (104). The operations of the DU 105 may be at least partly controlled by the CU 108. It should also be understood that the distribution of functions between the DU 105 and the CU 108 may vary depending on the implementation.

[0031] 6G wireless communication networks are expected to adopt flexible decentralized and / or distributed computing systems and architecture and ubiquitous computing, with local spectrum licensing, spectrum sharing, infrastructure sharing, and intelligent automated management underpinned by mobile edge computing, artificial intelligence, short-packet communication and blockchain technologies. Key features of 6G may include intelligent connected management and control functions, programmability, integrated sensing and communication, reduction of energy footprint, trustworthy infrastructure, scalability and affordability. In addition to these, 6G is also targeting new use cases covering the integration of localization and sensing capabilities into system definition to unifying user experience across physical and digital worlds.

[0032] In 5G, the core network 110 may classify downlink application flows (or data streams) and the non-access stratum (NAS) layer of the UE uplink application flows into quality of service (QoS) flows. The network node (104) (e.g., gNB) may define a radio bearer configuration for the user device (100), 102 and map QoS flows (e.g., QoS 305, see FIG. 2) to DRBs (e.g., DRBs 202a...202n, see FIG. 2) based on the QoS profiles received from the core network 110. In other words, the core network 110 may classify application flows (e.g., QoS flows 305) based on their QoS requirements, and the network node (104) may set up the necessary channels to ensure that the data is transmitted efficiently and with the required quality. Separate DRBs (202a...202n) may be established for QoS flows (305) requiring different packet forwarding treatment, or several QoS flows (305) belonging to the same protocol data unit(PDU) session can be multiplexed in the same DRB (202). As further described herein and shown in FIGS. 2-10, the present apparatuses, methods, and computer program products enable mapping of a QoS flow to multiple DRBs such that parallelization of QoS traffic in UL among two or more DRBs may be implemented.

[0033] As used herein, a DRB is a radio channel used in mobile networks to carry user data between the user device (100), 102 and the network node (104) (e.g., gNB). For example, the DRB 202a, DRB 202b, and DRB 202n shown in FIG. 2 may be radio channels used in mobile networks to carry user data (e.g., QoS flows, and / or the like) between the user device (100) and the network node (104).

[0034] An application flow (or data stream) refers to the stream of data packets generated by a specific application or service as it communicates over the network. For example, when streaming a video or making a video call, the data being sent and received forms an application flow. Each application flow may have different requirements for example for speed, latency, and reliability, which are managed by the network to ensure a satisfactory user experience. As used herein, the terms application flow, data stream, and QoS flow are referred to interchangeably.

[0035] A downlink (DL) application flow refers to data transmitted from the network (e.g., from the gNB (104)) to the user device (100), (102). An uplink (UL) application flow refers to data transmitted from the user device (100), 102 to the network (e.g., to the gNB (104)).

[0036] QoS requirements are specific criteria that define the performance level needed for an application flow (e.g., QoS flow (305)), such as minimum bandwidth, minimum throughput, maximum latency, availability, and reliability. QoS requirements ensure that different types of data traffic, such as video streaming or online gaming, receive the appropriate network resources to function smoothly. A QoS profile is a set of parameters that define the specific QoS requirements for an application flow (e.g., QoS flow (305)).

[0037] A QoS flow (305) may comprise or correspond to a data stream (201a...201n) that is managed according to these QoS requirements. In other words, the QoS flow (305) defines how the network manages the application flow, ensuring that it meets the specific QoS requirements. In essence, the application flow refers to the data being transmitted, and the QoS flow is the network’s way of ensuring that the data is delivered with the necessary performance and reliability.

[0038] FIG. 1 further illustrates, by way of example, a block diagram of an apparatus (10). The apparatus (10) comprises, for example, at least one processor (12) and at least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the apparatus (10) at least to perform the method or methods as disclosed herein, and any of the embodiments thereof. In an example, the at least one memory and the instructions (e.g. a computer program code, software), are configured, with the at least one processor, to cause the apparatus (10) to perform the method or methods as disclosed herein, and any of the embodiments thereof.

[0039] A processor (12) may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0040] The memory (14) may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory (14) may be at least in part external to apparatus (10) but accessible to apparatus (10).

[0041] The instructions (15) may be comprised in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random-access memory, RAM, vs. read only memory, ROM).

[0042] For example, the apparatus (10) is a terminal device, such as the user device of FIG. 1. As another example, the apparatus (10) is comprised in such a terminal device, e.g. as a chipset configured to control the terminal device. The apparatus (10) may be caused or configured to perform at least the method of FIGS. 7-10 and / or any one or more of the embodiments described.

[0043] As another example, the apparatus (10) is a network node, e.g. the network device (104) of FIG. 1. In another embodiment, the apparatus is comprised in such a network node, e.g. as a chipset configured to control the network node. The apparatus (10) may be caused or configured to perform at least the method of FIGS. 7-10 and / or any one or more of the embodiments described.

[0044] As used herein, QoS flow sent in DL may be referred to as “DL traffic,” and QoS flow (see, e.g., QoS flow 305a...305n shown in FIGS. 2-6) sent in UL may be referred to as “UL traffic.”

[0045] In 5G the core network (CN) may classify down service data flows (SDFs) and NAS layer of the UE uplink service data flows into the QoS flow (305). The NG-RAN node (e.g., network node (104), such as a gNodeB) may define radio bearer configuration for the UE and map QoS flows to DRBs based on the received QoS profiles of QoS flows from the CN. In some embodiments, separate DRBs are established for QoS flows requiring different packet forwarding treatment or several QoS flows belonging to the same PDU session may be multiplexed in the same DRB. As used herein, the 1-to-l QoS flow to DRB mapping refers to scenarios where a QoS flow (305) is mapped to a single DRB (e.g., anyone of 202a to 202n). As used herein, a 1-to-N QoS flow to DRB mapping refers to scenarios where any portions within the QoS flow (one of (305a) to (305n)) is / are mapped to two or more DRBs (202a, 202b, ...202n). In various embodiments, the mapping refers to a NG-RAN node (104) configuring a UL QoS flow (305) to DRB association (UL mapping Rule) to a user device (100).

[0046] As used herein, the mapping rules or the “mapping” refers to an association of QoS flow (305) (or any portions (305a...305n) of the QoS flow (two or more of 305a...305n)) to two or more DRB (202a, 202b,...202n), according to which the user device (100) or gNB (104) forwards SDAP PDUs to the DRBs (202a to 202n). The additional mapping refers to a case when one QoS flow (305b) is associated with additional DRB (202b, ... 202n), without removing the existing associations (mappings). For example, the current reflective mapping supports only replacement of the UL mapping, i.e. if a UE detects changes in the QoS flow (e.g., from (305a) to 305b) to the DRB mapping in the DL traffic, the current reflective mapping may derive a new UL rule for the new QoS flow (305b) and replaces the existing mapping rule, such as the new QoS flow 305b) is mapped to the existing DRB (202a).

[0047] The gNodeB may set a reflective QoS flow to DRB mapping indicator (RDI) bit (see, e.g., RDI bit (309) shown in FIG. 3) of the data protocol header (see, e.g., header 205 embodied as a PDCP in FIG. 2) to “1” to indicate to a user device (100) that the downlink (DL) traffic packet (e.g., SDAP packet) shall be used for reflective mapping. For example, when the user device (104) receives a DL SDAP packet (200) with the RDI bit (309) being set, the user device (100) may determine the QFI (see, e.g., QFI (307) shown in FIG. 3) and apply same mapping for the uplink (UL) traffic.

[0048] To provide satisfied quality of experience (QoE) for dependable communications (e.g., including extended reality and full versions of metaverse), 6G should be able to support very high data rates, ranging from (100) megabits per second (Mbps) to (10) gigabytes per second (Gbps) or even higher. Another additional requirement is short end-to-end (E2E) latency on the order of approximately (10) milliseconds (ms). To fulfill the stringent requirements, 6G UP protocol should be capable of enabling parallel processing and / or hardware -based processing of user plane, and further taking full advantage of the fast developed system-on-chip (SoC) design.

[0049] In various embodiments, the present apparatuses, methods, and computer program products address these challenges, and others, to enable parallel processing of QoS flow (305) on multiple data radio bearers (e.g., DRB level parallelization on two or more DRBs 202a...202n). For example, instead of a complex schema mixing all mechanisms and optimizations as in 5G NR, for 6G UP design, a multi-stack approach may be implemented. An anchor protocol stack (APS) may be implemented for low bit rate services, with optimizations to optimize coverage (e.g. bit-level optimizations) and reliability (e.g., RLC automatic repeat request (ARQ). A fast protocol stack (FPS) may be implemented for high bit rate services, where the focus is laid on a processing-friendly and implementation-friendly design allowing the concept of radio processing unit (RPU), enabling parallel processing of the radio functions.

[0050] In various embodiments, parallel processing may be provided on different protocol layers. For example, to enable parallel processing, a DRB (202) may be split on a PDCP layer into two or more branches. The PDCP layer may be split into PDCP-Hi and PDCP-Low sub layer, with PDCP-Hi being a common layer for all “branches” of a DRB and PDCP-low managing branch-specific tasks.

[0051] FIG. 2 illustrates an example approach to parallel processing in accordance with some embodiments of the present disclosure. As shown, parallelization may be performed at the DRBlevel by mapping high data rate QoS flow (305) (or any number of portions 305a...305n) to multiple parallel DRBs (e.g., 1 -to- / mapping), instead of mapping a single DRB to multiple parallel L2 branches. For example, multiple instances of a data stream 201a, 201b, 201n (e.g., corresponding to a QoS flow 305 with instances 305a, 305b...305n) may be mapped from the SDAP layer 200 to a plurality of parallel DRBs 202a, 202b, 202 / r, which may include, respectively, radio processing units (RPUs) 203a, 203b, 203m Although singular RPUs are shown for each DRB 202a...202n, it should be noted that greater numbers of RPUs are contemplated. In some embodiments, DRB-level parallelization enables PDU set-based mapping to DRBs 202a...202n at the RAN node, which may allow easier and more flexible PDU set differentiation on radio interface. In various embodiments, the instances 305a, 305b, ...305n may be duplicative of the QoS flow 305 or may correspond to or comprise the same or different portions of the QoS flow 305.

[0052] In various embodiments shown in FIGS. 3 to 10, the apparatuses, methods, and computer program products overcome challenges associated with configuring the UL QoS flow to DRB mapping over a user plane (UP) via reflective mapping. For example, if a gNodeB (network node 104) has mapped a first QoS (305) flow initially to a first DRB (202a) but determines that the data rate of the first QoS flow (305) is so high that it requires parallel processing. In response, the gNodeB (104) may determine to additionally map the first QoS flow (which may be referred to as QoS flow 305a) to one or more additional DRB (202b...202n) with reflective mapping of QoS flows (305b...305n). The gNodeB (104) may start sending, to the user device (100), DL SDAP PDUs containing the QFI (307), the RDI (309) set to 1 and a 1-to-N mapping indicator (311a) set through the additional DRB (202b...202n) to indicate that the QoS flow (305 a) should be reflectively (per the RDI (309)) and additionally (per the indicator (31 la)) mapped to the DRB (202b...202n). The disclosed embodiments provide means for the user device (100) to determine that the intention of the gNodeB (104) is to map the QoS flow (305) to both the first DRB (202a) and the additional DRBs (202b...202n). The disclosed embodiments solve the problems of existing approaches, that is, the user device (100) may incorrectly interpret the reception of the SDAP PDU of the QoS flow (e.g., any of 305b...305n) from the additional DRB (e.g., any of 202b...202n) as an intention for QoS flow relocation from the first DRB (202a) to additional DRBs (202b...202n). As a result, the UE in the existing approach may incorrectly perform an unintended operation of removing the initial mapping of the QoS flow (305) to thefirst DRB (202a). Such instances of QoS flow relocation may be referred to as “replacement” due to the additional DRB (any one of 202b...202n) replacing the first DRB (202a). For example, in a scenario of replacement, the mapping of QoS UL traffic is switched between a first DRB (202a) and a second DRB (202b) such that the QoS flow UL traffic is sent on the second DRB (202b) instead of the first DRB (202b) (e.g., the second DRB (202b) is added to the mapping, resulting in a removal of the first DRB 202a from the mapping).

[0053] In various embodiments, the apparatuses, methods, and computer program products introduce techniques for mapping the QoS flow to multiple DRBs simultaneously. As used herein, instances of “additional” or “simultaneous” mapping mean that the QoS UL traffic is mapped to multiple DRBs (e.g., any of two of 202a...202n) concurrently. For example, additional mapping or simultaneous mapping may refer to an instance in which a second DRB (202b) is added to a mapping of the QoS flow (305) without removing a first DRB (202a) from the mapping, resulting in all or portions of the QoS flow UL traffic being sent on the first DRB (202a) and the second DRB (202b) concurrently.

[0054] In a first example embodiment, further depicted in FIGS. 3, 4, and 7, a RAN node (e.g., radio access point, such as a gNodeB) sends a I -to- A mapping indication (311) in a radio protocol header (205) of data PDU indicating that the UL QoS flow (305) to DRB mapping rule derived from the data PDU header (205) is an additional rule to the existing mapping rules (e.g., instead of an overriding rule). In a second example embodiment, further depicted in FIGS. 5, 6, and 8, a RAN node (104) provides UL QoS flow-to-DRB mapping rules to the UE (100) with in-band signaling, such as in a radio protocol control PDU or control element (e.g., MAC CE, and / or the like).

[0055] Existing approaches for configuring mapping rules to QoS flow to DRB mapping fail to support parallelization at the DRB level. For example, a single QoS flow (or portions thereof) cannot be mapped to multiple DRBs. A first existing approach for 1-to-l QoS flow to DRB mapping includes reflective mapping in which, for each DRB (202a...202n), the user device (100) monitors the QoS flow identifiers (QFIs) (307) of the downlink packets and applies the same mapping in the uplink. That is, for a DRB (202), the user device (104) maps the uplink packets belonging to the QoS flows(s) (305) corresponding to the QFI(s) (307) and PDU session (303) observed in the downlink packets for that DRB (202a...202n). To enable this reflective mapping, the NG-RAN marks downlink packets over Uu with QFI (307). A second existingapproach for 1 -to- 1 QoS flow to DRB mapping includes explicit configuration in which QoS flow to DRB mapping rules can be explicitly signaled by RRC. However, because such approaches only supporting mapping of a QoS flow (305) to a singular DRB (e.g., exclusively one of DRBs 202a...202n), these techniques are insufficient for configuring parallelization of a QoS flow (305) at the DRB level. Incorporated U.S. Application No. 63 / 713,838 introduces a method for a user device (100) to request a parallel processing from the NG-RAN node.However, such techniques do not consider how the DRB level parallelization (e.g., 1 to A mapping) may be configured to the user device (100).

[0056] Some example embodiments for enabling DRB level parallelization are described below using principles and terminology of 5G radio access technology without limiting the example embodiments to 5G radio access technology, however. For example, some example embodiments may also be applied to 6G and beyond.

[0057] Turning now to FIG. 3, it is shown a signal flow diagram in accordance with some embodiments of the present disclosure. In the signal flow shown, the network node (104) may configure DRB level parallelization at the user device (100) by sending a I -to- A mapping indication 31 la, b in the header (205) of a radio protocol (e.g., PDU, and / or the like). In some embodiments, the network node (104) may configure a bit of an RDI (309) to a predetermined value 1 to indicate that the packet shall be used for UL mapping derivation and the 1 to N mapping indication to a predetermined value to indicate to the user device (100) that the 1-to-A mapping indication (311a, b) is associated with applying an additional DRB (202) to the mapping of the QoS flow (305a, 305b...305n) (e.g., instead of replacing an existing DRB (202) mapped to the QoS flow 305a).

[0058] In some embodiments, a network node (104) (e.g., a gNodeB, and / or the like) may configure two or more DRBs (202) for a PDU session (303) and initially maps a QoS flow (305a) to a first DRB (202) (see indicium 300). In some embodiments, the network device determines to map the QoS flow (305b...305 / 7) to additional DRBs (202), such as two or more DRBs (202b...202n) (see indicium 302). For example, the network node (104) may determine that the data rate of the QoS flow (305a, 305b...305n) is so high that it may require parallel processing. Additionally, or alternatively, the network node (104) may determine that satisfaction of latency requirements may be achieved through parallel processing at the DRB level. In response to the one or more determinations, the network node (104) may determine toadditionally map the QoS flow (305b...3Q5n) to one or more additional DRB (202) with reflective QoS. In various embodiments, the network node (104) determines to enable parallel processing and use an in-band mechanism to update the UL mapping to the user device (100). In various embodiments, the network node (104) determines one or more distribution weights (“weight values” 317) for respective DRBs 202a, (202b...202n). Additionally, or alternatively, in some embodiments, the network node (104) determines one or more distribution thresholds for mapping one or more QoS flow traffic (305a to 305n) to one or more DRBs (202a, 202b...202n). In some embodiments, a weight value (317) may define a percentage of the UL traffic to be mapped to a DRB (202a to 202n). In some embodiments, a distribution threshold may define a data rate threshold after which the QoS flow (305a to 305n) may be forwarded to multiple DRBs (202a to 202n). For example, the distribution threshold may define a data rate at which the network node (104) initiates parallelization at the DRB level. The network node (104) may determine respective percentages of the QoS flow to forward to two or more DRBs 202a, (202b...202n) based at least in part on their associated weight values (315).

[0059] In some embodiments, the network node (104) determines one or more DRBs (202) to which the QoS flow (305a, 305b...305n) may be mapped based at least in part on a type of data stream (315) associated with the QoS flow (305). For example, the types of data streams (315) may include audio, image, video, XR traffic with specified PDU sets, user input, machine input, and / or the like. In various embodiments, different DRBs (202) are associated with sending traffic (e.g., QoS flows 305) of different data types. The network node (104) may determine to prioritize mapping the QoS flow (305a, 305b...305n) to one or DRBs (202) sharing an association to the same type of data stream as the traffic of the QoS flow (305a, 305b...305n). For example, the QoS flow (305a, 305b...305n) may be associated with a data stream type (315) of audio. Based at least in part on the QoS flow (305) being associated with audio, the network node (104) may determine to prioritize mapping the QoS flow (305a, 305b...305n) to one or more DRBs (202) that are associated with the audio data stream type.

[0060] Additionally, or alternatively, in some embodiments, the network node (104) determines one or more DRBs (202) to which the QoS flow 305b...305n may be mapped based at least in part on the type of data stream (315) of the QoS flow (305a, 305b...305n) and respective weight values (317) of the candidate DRBs (202). For example, different DRBs (202) may be associated with different weight values (317) pursuant to sending traffic of various types of datastreams 315. A DRB (202b) may be associated with a higher weight value (317) for audio and a lower weight value (317) for video. Another DRB (DRB 202n) may be associated with a lower weight value (317) for audio and a higher weight value (317) for video. The network node (104) may determine that the traffic of the QoS flow (305a, 305b...305n) is associated with a data stream type (315) of a video data stream. In response to the determination, the network node (104) may determine to prioritize mapping the QoS flow 305n to the DRB 202n based at least in part on the DRB 202n having a higher weight value (317) for the video data stream type (315) as compared to the weight value (317) of the DRB 202b. In this manner, the network node (104) may prioritize parallelization of QoS traffic to DRBs that may be best suited to servicing the associated type of data stream.

[0061] As another example, different DRBs (202) may be associated with different priorities assigned according to one or more of: the different data stream types (315) associated with the QoS flow (305a, 305b...305n), a sequence number of data packets being transmitted in the UL traffic, or a network node identity, and / or the like. The network node (104) may determine that the traffic of the QoS flow (305a) may be associated with a predetermined sequence number of data packets and that a DRB (202b) is assigned priority for supporting the predetermined sequence number. In response, the network node (104) may determine to additionally map the QoS flow (305b) to the DRB (202b) while maintaining a mapping between the QoS flow (305a) and an initial DRB (202a). In doing so, the network node (104) may prioritize particular DRBs in accordance with one or more properties or associations of the QoS flow (305a, 305b...305n).

[0062] In some embodiments, the network node (104) begins to forward the QoS flow (305b...305n) (e.g., QoS DL PDUs) to the two or more DRBs (202b to 202n) in parallel (see signals 304, 306). For example, as further depicted in the signal flow diagram of FIG. 4A, the network node (104) forwards the DL traffic (e.g., QoS flow 305a, 305b...305n) to a first DRB (202a) and one or more additional DRBS (202b,...202n). The forwarded QoS flows (305a, 305b...305n) may be duplicative, having the same QFI (307) and / or may comprise or correspond to portions of a QoS traffic. Additionally, in various embodiments, the network node (104) sets the RDI bit (309) of the header (205) of radio protocol to a particular value to provide an indication that reflective mapping applies and an indication that a 1 -to-A mapping indication (311a) is associated with a mapping of the QoS flow (305b to 305n) to one or more additional DRBs (202b to 202n) (e.g., instead of replacing an existing 1-to-l mapping of the first QoS flow(305a) to the first DRB (202a), which may be indicated if the 1 -to-N mapping indication is not set). For example, the network node (104) may set the RDI bit (309) to a value of “1” to indicate i) reflective mapping applies to the QoS flow (305), and a 1 -to- / V mapping indication is for mapping of the QoS flow (305b) to an additional DRB (202b) while maintaining a mapping of the QoS flow (305a) to another DRB (202a). In some embodiments, the header (205) includes one or more weight values (315), distribution thresholds, assigned priorities, and / or the like. In this manner, the user device (100) may configure QoS flow mapping, QoS flow forwarding, and / or the like based at least in part on the one or more weight values (315), distribution thresholds, assigned priorities, and / or the like.

[0063] In various embodiments, the user device (100) receives packets of the QoS flow 305b...305n from the one or more additional DRBs (202b...202n) (see indicium 308) while also receiving packets of the QoS flow (305) on the first DRB (202). In some embodiments, based at least in part on the RDI bit (309) being set to the particular value (e.g., 1) and the QFI (307) of the packets received via the additional DRB (202) matching the QFI of the packets received via the first DRB (202), the user device (100) determines that the PDU is subject to reflective QoS flow to DRB mapping (indicium 308). Based at least in part on the 1 -to- / V mapping indication 311a and the set RDI bit (309), the user device (100) derives a new QoS rule for UL traffic, which maps the QoS flow 305b to the DRB (202b) (indicium 308). Further, the user device (100) determines that the mapping to the additional DRB (202b) is an additional mapping rule that does not override the initial mapping of the QoS flow (305 a) to the first DRB 202a. In response to the determination, the user device (100) does not remove the initial mapping rule that associates the UL traffic (e.g., QoS flow 305a) to the first DRB 202a.

[0064] In various embodiments, in accordance with the mappings, the user device (100) forwards UL packets of the QoS flow (305a, 305b) to both the first and the additional DRB (202a, 202b) (see signal 310). For example, as depicted in the signal diagram of FIG. 4, the user device (100) forwards the QoS flow 305a, 305b on the first DRB 202a and one or more additional DRBs (202b) (see signals 310a, 310b). In various embodiments, the user device (100) configures the distribution of UL packets of the QoS flow (305) between the additional DRBs based at least in part on weight values 315, assigned priorities, distribution thresholds, and / or the like, which may be obtained from the header 205 received from the network node (104).

[0065] In some embodiments, to configure a return to 1-to-l mapping (e.g., forwarding of UL traffic on a single DRB (202), either the initial DRB or one or more of the additionally mapped DRBs), the network node (104) stops forwarding packets of the QoS flow (305a, 305b...305n) to a subset of the QoS-mapped DRBs and continues forwarding packets of the QoS flow (305) to an intendent DRB (202). In various embodiments, the network node (104) forwards packets of the QoS flow (305) to the intendent DRB (202) with the 1-to-A mapping indication 31 la, b not set, which may cause the user device (104) to determine that 1-to-l mapping is indicated instead of 1-to-A mapping (signal 312). In some instances, the RDI bit (309) may remain set to indicate that reflective QoS mapping is to be used (e.g., QoS requirements in DL are reflectively mapped to QoS traffic in UL).

[0066] Alternately, the RDI bit (309) may be un-set or altogether missing a 1-to-N indication, such that the user device (100) (or UE) may default back to a 1-to-l mapping of a DRB (202) to the flow stream (305). In response to the I -to- A mapping indication not being set, the user device (100) may determine that there shall be no mappings to other DRBs (202) (indicium 314). In response to the determination, the UE may remove mapping rules pointing to other DRBs (202b...202n) (indicium 314), suspending sending of UL traffic on the removed DRBs (202b...202n) while maintaining the UL traffic on the intendent DRB (202).

[0067] Turning now to FIG. 5, shown is a signal flow diagram in accordance with some embodiments of the present disclosure. In the signal flow shown, the network node (104) may configure DRB level parallelization at the user device (100) by providing UL QoS flow-to-DRB mapping rules to the user device (100) with in-band signaling, such as in a control PDU (503).

[0068] In various embodiments, the signal flow depicted in FIG. 5 includes the network node (104) and the user device (100) carrying out functionality similar to behaviors shown in the signal flow diagram of FIG. 3, in particular those behaviors associated with indicia 300 and 302.

[0069] In various embodiments, in response to determining to enable parallel processing and use an in-band mechanism to update the UL mapping to the user device (100), the network node (104) sends a radio protocol, e.g. SDAP, control PDU (503) to the user device (100), containing a QFI (307) of QoS flow and identifiers (IDs) 501 of DRBs (202) where the QoS flow (305a, 305b...305n) shall be mapped in the UL direction (see signal 502a). In various embodiments, the network node (104) sends the control PDU (503) any DRB (202) configured for the PDU session (303).

[0070] Alternatively, in some embodiments, the network node (104) sends a radio protocol control PDU (503) to the user device (100) through a DRB (202) that is to be added to the mapping of the QoS flow (305a, 305b...305n) (e.g., in UL) (see signal 502b). In some embodiments, the control PDU (503) contains the QoS flow ID (307) of the QoS flow. In some embodiments, the control PDU (503) includes an indicator (e.g., a set bit value, flag, and / or the like) indicating that the new QoS flow to DRB mapping rule shall be derived to the DRB through which the control PDU (503) was received. For example, as depicted in the signal flow diagram of FIG. 5, the user device (100) may be initially configured to forward QoS flow (305a) in UL through a first DRB (202a) (see signal 602). To cause the user device (100) to initiate parallelization of the QoS flow (305b...305n) on one or more additional DRBs (202b...202n), the network node (104) may provision a control PDU (503) on the one or more DRBs (202b...202n) that are to be added to the mapping of QRS flow in UL (see signal 604). In some embodiments, the control PDU (503) includes one or more weight values (315), assigned priorities, distribution thresholds, and / or the like.

[0071] In various embodiments, the user device (100) determines the mapping of the QoS flow (305a, 305b...305n) in UL based at least in part on the control PDU (503) (see indicium 504). For example, in instances in which the network node (104) provisions the signal (502a), the user device (100) determines the mapping based on the content of the control PDU (503) (e.g., included the QFI and DRB ID associations). In some embodiments, the user device (100) determines respective portions of the QoS flow (305a, 305b...305n) that may be forwarded to different DRBs (202a, 202b...202n) based at least in part on weight values (315) assigned to the DRBs 202a, (202b...202n). Alternatively, in instances in which the network node (104) provisions the signal 502b, the user device (100) determines the mapping based on the identification of the DRB (202b...202n) through which the control PDU (503) was received and the QFI (307) in the control PDU (503). In various embodiments, the user device (100) applies the determined UL mapping for the UL traffic (e.g., QoS flow in UL) and forwards, in parallel, the packets of the QoS flow (305a, 305b...305n) on the two or more mapped DRBs (202a, 202b...202n) (see signal 506).

[0072] In some embodiments, to remove one or more DRBs (202) from the QoS flow mapping, the network node (104) sends a control PDU (503) to any DRB (202) of the PDU session (303), where the control PDU (503) indicates the new UL mapping of the QoS flow (305a...305n) bycontaining the QoS flow ID (307) and the respective IDs 501 of the DRB (202) where QoS flow (305a...305n) is meant to be mapped (e.g., previously mapped DRBs that are not identified in the control PDU are removed by the user device (100), such as via removal of the associated mapping rule) (see signal 508a). Alternatively, in some embodiments, the network node (104) sends a control PDU (503) to the one or more DRB (202a...202n) to be removed from the QoS flow mapping (see signal 508b). The control PDU (503) may include the QoS flow ID (307) and an indication (e.g., set bit value, flag, and / or the like) indicating that the mapping rule for the QoS flow (305a...305n) to the DRB shall be removed. In various embodiments, the user device (100) determines to remove one or more DRBs (202a....202n) from the UL mapping of the QRS flow (305a...305n) and, based on the updated mapping, suspends provision of the UL traffic of the QRS flow (e.g., any of 305a...305n) on the one or more determine DRBs (e.g., any of 202a...202n).

[0073] Turning now to FIG. 7, shown is a flowchart of a method 700 for DRB level parallelization in accordance with example embodiments of the present disclosure. The method of FIG. 7 may be performed by an apparatus (10) depicted in FIG. 1. For example, the apparatus (10) may be, a user device (100), (102).

[0074] As shown in block 703 of FIG. 7, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (304), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n). In various embodiments, the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n). In some embodiments, a data protocol of the downlink traffic comprises a header (205) may include an indication (311a) of a 1-to-A mapping between the QoS flow (305) and the at least two DRBs (202a, 202b...202n). In some embodiments, includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (306) the DL traffic of the QoS flow (305) on one or more additional DRBs (202b...202n). In some embodiments, the data protocol associated with the data protocol header (205) comprises an upper or a lower layer data protocol, which comprises at least one of: service data adaptation protocol (SDAP), packet data convergence protocol (PDCP) and medium access control element (MAC-CE).

[0075] As shown in block 706 of FIG. 7, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for determining (308) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the I -to- A mapping (311b). In some embodiments, at block 706, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for generating (308) a second mapping between the QoS flow (305) and at least the second DRB (202b) of the at least two DRBs (202a, 202b...202n) while maintaining the first mapping between the QoS flow (305) and the first DRB (202a) of the at least two DRBs (202a, 202b). In some embodiments, the header (205) of the data protocol comprises a QoS flow ID (QFI) (307) associated with the QoS flow (305). In some embodiments, the indication (311a, 311b) within the header (205) of the data protocol is configured to indicate the addition of one or more DRBs (202b....202n) to the mapping of QoS traffic in UL (e.g., the second mapping is to be applied in addition rather than as an alternative replacement). For example, the RDI bit (309), when set, may indicate that reflective QoS flow mapping applies. Further, a 1-to-N mapping indication, when set, (311b) may indicate that one or more indicated DRBs (202b...202n) may be additionally mapped to the QoS flow (305a, 305b...305n), while a mapping of the QoS flow (305 a) on the first DRB (202a) is maintained.

[0076] As shown in block 709 of FIG. 7, the apparatus embodied by the user device (100) optionally includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for, in response to the determination, initiating (310) to the network node, (104) uplink (UL) traffic of the QoS flow (305) on at least the first DRB (202a) and the second DRB (202b).

[0077] As shown in block 712 of FIG. 7, the apparatus embodied by the user device (100) optionally includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (312), from the network node (104), additional DL traffic of the QoS flow (305) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n). In some embodiments, a data protocol header (205) of the additional DL traffic of the QoS flow (305) comprises a header (205) may include a second indication (313) value to indicate a 1-to-l mapping between the QoS flow (305) and the first DRB (202a) (also referred to herein as a 1-to-1 mapping indication). In some example instances, the RDI bit (309) in the header (205) may notbe set or the RDI bit (309) may be configured to a value zero. In some embodiments, the data protocol header (205) of the additional DL traffic of the QoS flow (305) comprises: a 1-to-l mapping indication (313), which may be configured to indicate that there are no mappings between a subset of the at least two DRBs (202a, 202b) excluding the first DRB (202a).In some embodiments, the 1-to-l mapping indication (313) may comprise or correspond to a scenario where the 1-to-N indication (311a, 311b) is not set (e.g., configured to a value of “0”).

[0078] As shown in block 715 of FIG. 7, the apparatus embodied by the user device (100) optionally includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for suspending (314) the provision of the UL traffic of the QoS flow (305) on the second DRB (202b) while maintaining the UL traffic of the QoS flow (305) on the first DRB (202a) in accordance with the 1-to-l mapping. In some embodiments, at block 715, the apparatus (10) embodied by the user device (100) optionally includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for removing (314) a mapping rule associated with the second DRB (202) in accordance with the 1-to-l mapping indication (313).

[0079] Turning now to FIG. 8, shown is a flowchart of a method 800 for DRB level parallelization in accordance with example embodiments of the present disclosure. The method of FIG. 8 may be performed by an apparatus (10) depicted in FIG. 1. For example, the apparatus (10) may be, or comprise, or be comprised in, a network node (104).

[0080] As shown in block 803 of FIG. 8, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for initiating (304), to a user device (100), downlink (DL) traffic of a QoS flow (305) on a first DRB (202a) of at least two DRBs (202a, 202b...202n). In some embodiments, the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n). In some embodiments, a data protocol of the DL traffic of the QoS flow (305) comprises a header (205) may include an indication (311a) of a 1-to-A mapping between the QoS flow (305) and the at least two DRBs (202a, 202b...202n).

[0081] As shown in block 806 of FIG. 8, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for, in accordance with the 1-to-N mapping between the QoS flow (305),receiving (310), from the user device (100), UL traffic of the QoS flow (305) on the first DRB (202a) and the second DRB (202b).

[0082] As shown in block 809 of FIG. 8, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for initiating (312), to the user device (100), additional DL traffic of the QoS flow (305) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n) to cause the user device (100) to suspend the provision of the UL traffic of the QoS flow (305) on the second DRB (202b). In some embodiments, a data protocol of the additional DL traffic of the QoS flow (305) comprises a (205) may include a second indication (313) of a 1-to-l mapping between the QoS flow (305) and the first DRB (202a).

[0083] As shown in block 812 of FIG. 8, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for, in accordance with the 1-to-l mapping, receiving additional UL traffic of the QoS flow (305) on the first DRB (202a).

[0084] Turning now to FIG. 9, shown is a flowchart of a method 900 for DRB level parallelization in accordance with example embodiments of the present disclosure. The method of FIG. 9 may be performed by an apparatus (10) depicted in FIG. 1. For example, the apparatus (10) may be, or comprise, or be comprised in, a user device (100), (102).

[0085] As shown in block 903 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for initiating (300), on a first data radio bearer (DRB) (202a) uplink (UL) traffic of a quality-of-service (QoS) flow (305) to a network node (104).

[0086] As shown in block 906 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (404a, 404b) from the network node (104) a control packet data unit (PDU) (503) on at least one of the first DRB (202a) or at least one additional DRB (202b). In some embodiments, the control PDU (503) comprises: a QoS identifier (307); a first identifier (501) associated with the first DRB (202a) and at least one additional identifier (501) associated with the at least one additional DRB (202b).

[0087] As shown in block 909 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18),and / or the like, for updating (505) a mapping (505) of the QoS flow (305) based at least in part on the control PDU (503) or an identification of the at least one additional DRB (202b) on which the control PDU (503) was received. In some embodiments, the control PDU (503) comprises: a QoS identifier (307); a first identifier (501) associated with the first DRB (202a) and at least one additional identifier (501) associated with the at least one additional DRB (202b). In various embodiments, at block 909, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for updating (504) the mapping (505) based at least in part on the at least one additional identifier (501) to indicate an association of the QoS flow (305) to the at least one additional DRB (202b).

[0088] As shown in block 912 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for initiating (505), based at least in part on the mapping (505), the UL traffic of the QoS flow (305) on the at least one additional DRB (202b) while maintaining the provision of the UL traffic of the QoS flow (305) on the first DRB (202a).

[0089] As shown in block 915 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (508a, 508b) from the network node (104) a second control PDU (503) on the first DRB (202a) or the at least one additional DRB (202b). In some embodiments, at block 915, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (508a) from the network node (104) a second control PDU (503) on the first DRB (202a) or the at least one additional DRB (202b). In some embodiments, the second control PDU (503) comprises the QoS flow identifier (409) and a plurality of identifiers excluding the first identifier (501) or the at least one additional identifier (501). In some embodiments, at block 915, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for updating (504) the mapping (505) based on the plurality of identifiers. At block 918, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for, based on the mapping (505), suspending (510) the provision of the UL traffic of the QoS flow (305) on at least one of the first DRB (202a) or the at least one additional DRB (202b).

[0090] In some embodiments, at block 915, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (508b) from the network node a second control PDU (503) on the first DRB (202a) or the at least one additional DRB (202b), wherein the second control PDU (503) comprises an indication (313) to remove from the mapping the DRB (202a, 202b) on which the second control PDU (503) was received. In some embodiments, at block 915, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for updating (504) the mapping (505) based at least in part on an identification of the DRB on which the second control PDU was received (510). At block 918, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for, based at least in part on the mapping (505), suspending (510) the provision of the UL traffic of the QoS flow (305) on the first DRB (202a) or the at least one additional DRB (202b).

[0091] As shown in block 918 of FIG. 9, the apparatus embodied by the user device (100) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for suspending (510) the provision of the UL traffic of the QoS flow (305) on the first DRB (202a) or the at least one additional DRB (202b) based on the second control PDU (503) or an identification of the DRB (202a, 202b) that received the second control PDU (503) (508a, 508a).

[0092] Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

[0093] Turning now to FIG. 10, shown is a flowchart of a method 1000 for DRB level parallelization in accordance with example embodiments of the present disclosure. The method of FIG. (10) may be performed by an apparatus (10) depicted in FIG. 1. For example, the apparatus (10) may be, or comprise, or be comprised in, a network node (104).

[0094] As shown in block 1003 of FIG. 10, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18),and / or the like, for initiating (300), on a first data radio bearer (DRB) (202a), to a user device (100), uplink (UL) traffic of a quality-of-service (QoS) flow (305).

[0095] As shown in block 1006 of FIG. 10, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for determining (302) to map the QoS flow (305) to at least one additional DRB (202b). For example, the apparatus may determine that a data rate, latency, and / or the like associated with the QoS flow (305) meets one or more predetermined thresholds associated with initiating parallelization at the DRB level.

[0096] As shown in block 1009 of FIG. 10, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for provisioning (502a, 502b), to the user device (100), a control packet data unit (PDU) (503) on at least one of the first DRB (202a) or the at least one additional DRB (202b) to cause the user device (100) to update (5054) a mapping (505) of the QoS flow (305) based at least in part on the control PDU (503), an identification of the at least one additional DRB (202b) on which the control PDU (503) was received, and / or the like.

[0097] As shown in block 1012 of FIG. 10, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for receiving (506), in accordance with the mapping (505), the UL traffic of the QoS flow (305) on the at least one additional DRB (202b) while receiving the UL traffic of the QoS flow (305) on the first DRB (202a).

[0098] As shown in block 1015 of FIG. 10, the apparatus embodied by the network node (104) includes means, such as the processor (12), the radio interface (16), the user interface (18), and / or the like, for provisioning (508a, 508b) to the user device (100) a second control PDU (503) on the first DRB (202a) or the at least one additional DRB (202b) to cause the user device (100) to suspend (510) the provision of the UL traffic of the QoS flow (305) on the first DRB (202a) or the at least one additional DRB (202b) based at least in part on: the second control PDU (503), an identification of the DRB (202a, 202b) that received the second control PDU (503) (508a, 508a), and / or the like.

[0099] The blocks, related functions, and information exchanges (messages) described above by means of FIGS. 3-10 are in no absolute chronological order, and some of them may be performed simultaneously or in an order differing from the described one. Other functions canalso be executed between them or within them, and other information may be sent, and / or other rules applied. Some of the blocks or part of the blocks or one or more pieces of information can also be left out or replaced by a corresponding block or part of the block or one or more pieces of information.

[0100] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0101] In an embodiment, at least some of the processes described herein may be carried out by an apparatus may include means for carrying out at least some of the described processes. Means for performing method steps as disclosed herein may include software and / or hardware components of the apparatus (10). For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the embodiments thereof. As used herein the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0102] As used in this application, the term “circuitry” may refer to one or more or all of the following: a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); and b) combinations of hardware circuits and software, such as (as applicable): i) a combination of analog and / or digital hardware circuit(s) with software / firmware and ii) any portions of hardware processor(s) with software (including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone, to perform various functions); and c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (for example firmware) for operation, but the software may not be present when it is not needed for operation.

[0103] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0104] The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For a hardware implementation, the apparatus(es) of example embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be carried out through modules of at least one chipset (for example procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the systems described herein may be rearranged and / or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.

[0105] It will be obvious to a person skilled in the art that, as technology advances, the inventive concept may be implemented in various ways within the scope of the claims. The embodiments are not limited to the example embodiments described above but may vary within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the embodiments.

[0106] In a first example, provided is a user device (100, 10) for wireless communication, which may include: at least one processor (12); and at least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the user device (100, 10) to at least: receive (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); determine (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and in response to the determination, initiate (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0107] In some aspects, the data protocol header (205) comprises an upper or a lower layer data protocol, which comprises at least one of: service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), or medium access control control element (MAC-CE).

[0108] In some aspects, the at least one memory (14) comprises a first mapping between the QoS flow (305, 305a, 305b...305n) and the first DRB (202a) of the at least two DRBSs (202a, 202b...202n); and the instructions (15), when executed by the at least one processor (12), cause the user device (100, 10) to: generate (308, 706) a second mapping between the QoS flow (305b) and at least the second DRB (202b) of the at least two DRBs (202a, 202b...202n) while maintaining the first mapping between the QoS flow (305 a) and the first DRB (202a) of the at least two DRBs (202a, 202b).

[0109] In some aspects, the protocol header (205) comprises a QoS flow ID (QFI) (307) associated with the QoS flow (305, 305a, 305b, ...305n); and the indication (311a, 311b) within the data protocol header (205) is associated with a reflective QoS flow to DRB mapping indicator (RDI) bit (309) and configured to indicate the second mapping.

[0110] In some aspects, the reflective mapping comprises for each DRB (202a,...202n), the apparatus (100) monitors the QoS flow identifiers (QFIs) (307) of downlink packets in thedownlink traffic, and applies the same 1-to-N mapping in the uplink traffic of the QoS flow (305a, 305b, ...305n).

[0111] In some aspects, the instructions (15), when executed by the at least one processor (12), cause the user device (100, 10) to perform at least one or both of: receive (312, 712), from the network node (104), additional DL traffic of the QoS flow (305a) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n), wherein: the additional DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include a second indication (313) with a value to indicate a 1-to-l mapping between the QoS flow (305a) and the first DRB (202a); or in response to the second indication: suspend (314, 715) the provision of the UL traffic of the QoS flow (305b) on the second DRB (202b) while maintaining the UL traffic of the QoS flow (305a) on the first DRB (202a) in accordance with the 1-to-l mapping.

[0112] In some aspects, the data protocol header (205) of the additional DL traffic of the QoS flow (305) comprises: the 1-to-N mapping indication (313) configured to a second value to indicate that there are no mappings between a subset of the at least two DRBs (202a, 202b) excluding the first DRB (202a).

[0113] In some aspects, respective DRBs (202) of the at least two DRBs (202a, 202b...202n) are associated with different types of data streams (315); and the indication (311a) of the 1-to-N mapping between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n) is based at least in part on a type of data stream (315) associated with the QoS flow (305, 305a, 305b, ...305n).

[0114] In some aspects, the different types of data streams (315) at least comprise audio, image, video, XR traffic, PDU sets, and one or both of user input or machine input.

[0115] In some aspects, the at least two DRBs (202a, 202b...202n) comprise or are associated with respective different weight values (317) or priorities assigned according to one or more of: the different types of data streams (315) associated with the QoS flow (305, 305a, 305b, ...305n), a sequence number of data packets being transmitted in the UL traffic, and a network node identity; respective weight values (317) are associated with sending different types of data streams (315) on respective DRBs (202) of the at least two DRBs (202a, 202b...202n); and the indication (311a) of the 1-to-N mapping between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n) is: configured to prioritize a subset of the at least two DRBs (202a, 202b...202n) having a respective weight value (317) in accordance with one ormore of the type of data stream (315) associated with the QoS flow (305, 305a, 305b, ...305n), the sequence number of data packets being transmitted in the UL traffic, and the network node identity.

[0116] In a second example, provided is a method (700), which may include: receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and in response to the determination, initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0117] In a third example, provided is a user device (100, 10), which may include: means for receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); means for determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1-to-N mapping (311b) in the data protocol header (205); and in response to the determination, means for initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

[0118] In a fourth example, provided is a network node (104, 10) for wireless communication, which may include: at least one processor (12); and at least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the network node (104, 10) to atleast: initiate (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and in accordance with the 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), receive (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

[0119] In some aspects, the instructions (15), when executed by the at least one processor (12), causes the network node (104, 10) to: initiate (312, 809), to the user device (100), additional DL traffic of the QoS flow (305) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n) to cause the user device (100) to suspend the provision of the UL traffic of the QoS flow (305b) on the second DRB (202b), wherein: the additional DL traffic of the QoS flow (305b) comprises a data protocol header (205), which may include a second indication (313) of a 1-to-l mapping between the QoS flow (305a) and the first DRB (202a); and in accordance with the 1-to-l mapping, receive (812) additional UL traffic of the QoS flow (305a) on the first DRB (202a).

[0120] In some aspects, the data protocol header (205) further comprises at least two weight values (315) associated with distribution of the QoS flow (305a, 305b...305n) between the at least two DRBs (202a, 202b...202n).

[0121] In a fifth example, provided is a method (800), which may include: initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and in accordance with the 1-to-N mapping (31 lb) between the QoSflow (305, 305a, 305b, ...305n), receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

[0122] In a sixth example, provided is a network node (104, 10), which may include: means for initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein: the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); and the DL traffic of the QoS flow (305) comprises a data protocol header (205), which may include an indication (311a) of a 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); and, in accordance with the 1-to-N mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), means for receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

Claims

What is claimed is:

1. A user device (100, 10) for wireless communication, comprising:at least one processor (12); andat least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the user device (100, 10) to at least:receive (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a 1 -to-A mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n); determine (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1 -to-A mapping (311b) in the data protocol header (205); andin response to the determination, initiate (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

2. The user device (100, 10) of claim 1, wherein the data protocol header (205) comprises an upper or a lower layer data protocol, which comprises at least one of: service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), or medium access control control element (MAC-CE).

3. The user device (100, 10) of any one of claims 1 to 2, wherein:the at least one memory (14) comprises a first mapping between the QoS flow (305, 305a, 305b...305n) and the first DRB (202a) of the at least two DRBSs (202a, 202b...202n); and the instructions (15), when executed by the at least one processor (12), cause the user device (100, 10) to:generate (308, 706) a second mapping between the QoS flow (305b) and at least the second DRB (202b) of the at least two DRBs (202a, 202b...202n) while maintaining the first mapping between the QoS flow (305a) and the first DRB (202a) of the at least two DRBs (202a, 202b).

4. The user device (100, 10) of any one of claims 1 to 3, wherein:the protocol header (205) comprises a QoS flow ID (QFI) (307) associated with the QoS flow (305, 305a, 305b, ...305n); andthe indication (311a, 311b) within the data protocol header (205) comprises or is associated witha reflective QoS flow to DRB mapping indicator (RDI) bit (309) and configured to indicate the second mapping.

5. The user device apparatus (100) of claim 4, wherein the reflective mapping comprises for each DRB (202a,...202n), the apparatus (100) monitors the QoS flow identifiers (QFIs) (307) of downlink packets in the downlink traffic, and applies the same 1-to-N mapping in the uplink traffic of the QoS flow (305a, 305b, ...305n305a, 305n).

6. The user device (100, 10) of claim 4, wherein:the instructions (15), when executed by the at least one processor (12), cause the user device (100, 10) to perform at least one or both of:receive (312, 712), from the network node (104), additional DL traffic of the QoS flow (305a) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n), wherein:the additional DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising a second indication (313) with a value configured to indicate a 1-to-l mapping between the QoS flow (305a) and the first DRB (202a); orin response to the second indication:suspend (314, 715) the provision of the UL traffic of the QoS flow (305b) on the second DRB (202b) while maintaining the UL traffic of the QoS flow (305a) on the first DRB (202a) in accordance with the 1-to-l mapping.

7. The user device (100, 10) of any one of claims 1 to 6, wherein:the data protocol header (205) of the additional DL traffic of the QoS flow (305) comprises:the 1-to-N mapping indication (313) configured to a second value to indicate that there are no mappings between a subset of the at least two DRBs (202a, 202b) excluding the first DRB (202a).

8. The user device (100, 10) of any one of claims 1 to 7, wherein:respective DRBs (202) of the at least two DRBs (202a, 202b...202n) are associated with different types of data streams (315); andthe indication (311a) of the 1-to-N mapping between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n) is based at least in part on a type of data stream (315) associated with the QoS flow (305, 305a, 305b, ...305n).

9. The user device (100, 10) of claim 8, wherein:the different types of data streams (315) at least comprise audio, image, video, XR traffic, PDU sets, and one or both of user input or machine input.

10. The user device (100,10) of any one of claims 1 to 9, wherein:the at least two DRBs (202a, 202b...202n) comprise or are associated with respective different weight values (317) or priorities assigned according to one or more of: the different types of data streams (315) associated with the QoS flow (305, 305a, 305b, ...305 / 1), a sequence number of data packets being transmitted in the UL traffic, and a network node identity;respective weight values (317) are associated with sending different types of data streams (315) on respective DRBs (202) of the at least two DRBs (202a, 202b...202n); andthe indication (311a) of the 1-to-iV mapping between the QoS flow (305, 305a, 305b, ...305 / 1) and the at least two DRBs (202a, 202b...202n) is:configured to prioritize a subset of the at least two DRBs (202a, 202b...202n) having a respective weight value (317) in accordance with one or more of the type of data stream (315) associated with the QoS flow (305, 305a, 305b, ...305n), the sequence number of data packets being transmitted in the UL traffic, and the network node identity.

11. A method (700), comprising:receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a I -to- A mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n);determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1 -to-A mapping (311b) in the data protocol header (205); andin response to the determination, initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

12. A user device (100, 10), comprising:means for receiving (300, 304, 703), from a network node (104), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a 1-to-A mapping (311b) between the QoS flow (305a, 305b...305n) and the at least two DRBs (202a, 202b...202n);means for determining (308, 706) that the QoS flow (305b) is mapped to at least the first DRB (202a) and the second DRB (202b) based at least in part on the indication of the 1 -to- / V mapping (311b) in the data protocol header (205); andin response to the determination, means for initiating (310, 709) to the network node, (104) uplink (UL) traffic of the QoS flow (305a, 305b) on at least the first DRB (202a) and the second DRB (202b).

13. A network node (104, 10) for wireless communication, comprising:at least one processor (12); andat least one memory (14) storing instructions (15) that, when executed by the at least one processor, cause the network node (104, 10) to at least:initiate (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality- of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a 1 -to-A mapping (311b) between the QoS flow (305, 305a, 305b, ...3Q5n) and the at least two DRBs (202a, 202b...202n); andin accordance with the 1-to-A mapping (311b) between the QoS flow (305, 305a, 305b, ...305 / 1), receive (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

14. The network node (104, 10) of claim 13, wherein:the instructions (15), when executed by the at least one processor (12), causes the network node (104, 10) to:initiate (312, 809), to the user device (100), additional DL traffic of the QoS flow (305) on the first DRB (202a) of the at least two DRBs (202a, 202b...202n) to cause the user device (100) to suspend the provision of the UL traffic of the QoS flow (305b) on the second DRB (202b), wherein:the additional DL traffic of the QoS flow (305b) comprises a data protocol header (205) comprising a second indication (313) of a 1-to-l mapping between the QoS flow (305a) and the first DRB (202a); andin accordance with the 1-to-l mapping, receive (812) additional UL traffic of the QoS flow (305a) on the first DRB (202a).

15. The network node (104, 10) of any one of claims 13 or 14, wherein the data protocol header (205) further comprises at least two weight values (315) associated with distribution of the QoS flow (305a, 305b...3Q5n) between the at least two DRBs (202a, 202b...202n).

16. A method (800), comprising:initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305 / 1) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a I -to- A mapping (311b) between the QoS flow (305, 305a, 305b, ...305 / 1) and the at least two DRBs (202a, 202b...202n); andin accordance with the 1-to-A mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

17. A network node (104, 10), comprising:means for initiating (300, 304, 803), to a user device (100), downlink (DL) traffic of a quality-of-service (QoS) flow (305, 305a, 305b, ...305n) on a first data radio bearer (DRB) (202a) of at least two DRBs (202a, 202b...202n), wherein:the QoS flow (305a, 305b) is mapped to at least a first DRB (202a) and a second DRB (202b) of the at least two DRBs (202a, 202b...202n); andthe DL traffic of the QoS flow (305) comprises a data protocol header (205) comprising an indication (311a) of a 1-to-iV mapping (311b) between the QoS flow (305, 305a, 305b, ...305n) and the at least two DRBs (202a, 202b...202n); andin accordance with the 1-to-iV mapping (311b) between the QoS flow (305, 305a, 305b, ...305n), means for receiving (310, 806), from the user device (100), UL traffic of the QoS flow (305a, 305b) on the first DRB (202a) and the second DRB (202b).

Images