Facilitating Quality of Service Flow Remapping Using Service Data Adaptation Protocol Layer

Abstract

Aspects for quality of service (QoS) flow remapping are disclosed. In an example, upon detecting a mapping reconfiguration of a first QoS flow from a first data radio bearer (DRB) to another DRB, a service data adaptation protocol (SDAP) control protocol data unit (PDU) is generated, indicating that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. The SDAP control PDU is then transmitted via the first DRB. In another example, upon detecting a mapping reconfiguration of a first QoS flow from a first DRB to another DRB, an end marker parameter is set in an SDAP header of a first SDAP data PDU received from an upper layer after the mapping reconfiguration, indicating that the first SDAP data PDU is the final SDAP data PDU associated with the first QoS flow transmitted on the first DRB.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Non-Provisional Patent Application No. 16 / 380,924 filed on April 10, 2019, and Provisional Patent Application No. 62 / 657,664 filed in the U.S. Patent and Trademark Office on April 13, 2018, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to utilizing a Service Data Adaptation Protocol (SDAP) layer to facilitate Quality of Service (QoS) flow remapping. Background Art

[0004] In wireless communication networks, Quality of Service (QoS) refers to a collection of techniques that enable the network to meet specific performance parameters (e.g., reliability and / or target latency). Such QoS techniques achieve these performance parameters by applying different treatments to different traffic flows in the network. For example, a specific QoS can be assigned to each flow, which can help the network determine, among other things, the order in which packets from each flow are treated and the amount of bandwidth allocated to each flow. Each QoS flow can be further mapped to a data radio bearer (DRB) established between a user equipment (UE) and a base station.

[0005] However, with the introduction of fifth generation (5G) (e.g., New Radio (NR)) networks, mapping and remapping specific QoS flows to corresponding data radio bearers has become increasingly challenging. As the demand for mobile broadband access continues to increase, research and development continues to advance communication technologies, including in particular technologies for enhancing QoS flow mapping, to not only meet the growing demand for mobile broadband access, but also to advance and enhance the user experience of mobile communications. Summary of the invention

[0006] A simplified overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a preface to a more detailed description presented later.

[0007] Various aspects of the present disclosure relate to mechanisms for facilitating quality of service (QoS) flow remapping using a service data adaptation protocol (SDAP) layer. In an example, upon detecting a mapping reconfiguration of a first QoS flow from a first data radio bearer (DRB) to another DRB, a service data adaptation protocol (SDAP) control protocol data unit (PDU) is generated, indicating that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. The SDAP control PDU is then transmitted to a receiver via the first DRB. In another example, upon detecting a mapping reconfiguration of a first QoS flow from a first DRB to another DRB, an end marker parameter is set in an SDAP header of a first SDAP data PDU received from an upper layer after the mapping reconfiguration, indicating that the first SDAP data PDU is the final SDAP data PDU associated with the first QoS flow transmitted on the first DRB. The first SDAP Data PDU and at least one subsequent SDAP Data PDU associated with the first QoS flow may then be transmitted to the receiver such that the first SDAP Data PDU is transmitted via the first DRB and the at least one subsequent SDAP Data PDU is transmitted via the second DRB.

[0008] In one example, a method of wireless communication is disclosed. The method includes: detecting a mapping reconfiguration of a first quality of service (QoS) flow from a first data radio bearer (DRB) to a second DRB, and in response to the mapping reconfiguration, generating a service data adaptation protocol (SDAP) control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. The method also includes transmitting the SDAP control PDU to a receiver via the first DRB.

[0009] Another example provides a scheduled entity within a wireless communication network. The scheduled entity includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor is configured to detect a mapping reconfiguration of a first quality of service (QoS) flow from a first data radio bearer (DRB) to a second DRB, and in response to the mapping reconfiguration, generate a service data adaptation protocol (SDAP) control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. The processor is further configured to transmit the SDAP control PDU to the scheduling entity via the first DRB via the transceiver.

[0010] Another example provides a method of wireless communication. The method includes: receiving multiple service data adaptation protocol (SDAP) data protocol data units (PDUs) associated with a first QoS flow via both a first data radio bearer (DRB) and a second DRB, receiving an SDAP control PDU applicable to the first QoS flow via the first DRB, and in response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB, forwarding the multiple SDAP data PDUs received via the second DRB to an upper layer, wherein the SDAP control PDU provides an indication that the final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB.

[0011] Another example provides a scheduling entity within a wireless communication network. The scheduling entity includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor is configured to: receive multiple service data adaptation protocol (SDAP) data protocol data units (PDUs) associated with a first QoS flow from a scheduled entity via the transceiver via both a first data radio bearer (DRB) and a second DRB, receive an SDAP control PDU applicable to the first QoS flow from the scheduled entity via the transceiver via the first DRB, and in response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB, forward the multiple SDAP data PDUs received via the second DRB to an upper layer, wherein the SDAP control PDU provides an indication that the final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB.

[0012] Another example provides a method for wireless communication. The method includes: detecting a mapping reconfiguration of a first quality of service (QoS) flow from a first data radio bearer (DRB) to a second DRB, and setting an end marker parameter in a service data adaptation protocol (SDAP) header of a first SDAP data protocol data unit (PDU) received from an upper layer after the mapping reconfiguration, wherein the end marker parameter provides an indication that the first SDAP data PDU is the last SDAP data PDU associated with the first QoS flow on the first DRB. The method further includes: transmitting the first SDAP data PDU and at least one subsequent SDAP data PDU associated with the first QoS flow to a receiver, the first SDAP data PDU being transmitted via the first DRB, and the at least one subsequent SDAP data PDU being transmitted via the second DRB.

[0013] Another example provides a scheduled entity in a wireless communication network. The scheduled entity includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor is configured to detect a mapping reconfiguration of a first quality of service (QoS) flow from a first data radio bearer (DRB) to a second DRB, and after the mapping reconfiguration, set an end marker parameter in a service data adaptation protocol (SDAP) header of a first SDAP data protocol data unit (PDU) received from an upper layer, wherein the end marker parameter provides an indication that the first SDAP data PDU is the last SDAP data PDU associated with the first QoS flow on the first DRB. The processor is further configured to transmit the first SDAP data PDU and at least one subsequent SDAP data PDU associated with the first QoS flow to the scheduling entity via the transceiver, wherein the first SDAP data PDU is transmitted via the first DRB, and the at least one subsequent SDAP data PDU is transmitted via the second DRB.

[0014] By reading the following detailed description, these and other aspects of the present invention will be more fully understood. When reading the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will become apparent to those skilled in the art. Although features of the present invention can be discussed relative to certain embodiments and accompanying drawings below, all embodiments of the present invention may include one or more advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, according to various embodiments of the present invention discussed herein, one or more such features may also be used. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a schematic illustration of a wireless communication system.

[0016] Figure 2 is a conceptual illustration of an example of a radio access network.

[0017] Figure 3 is a diagram illustrating an example of a radio protocol architecture for user and control planes.

[0018] Figure 4 is a diagram illustrating an exemplary quality of service (QoS) architecture that facilitates aspects disclosed herein.

[0019] Figure 5is a diagram illustrating an exemplary remapping of a QoS flow from a first data radio bearer (DRB) to a second DRB.

[0020] Figure 6 is a diagram illustrating an exemplary Service Data Adaptation Protocol (SDAP) control protocol data unit (PDU) and SDAP data PDUs.

[0021] Figure 7 is a diagram illustrating another exemplary SDAP data PDU.

[0022] Figure 8 is a block diagram illustrating an example of a hardware implementation for a scheduled entity employing a processing system.

[0023] Fig. 9 is a block diagram illustrating an example of a hardware implementation for a scheduling entity employing a processing system.

[0024] Fig.10 is a flow chart illustrating an exemplary process for facilitating QoS flow remapping.

[0025] Fig.11 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping.

[0026] Fig.12 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping.

[0027] Fig.13 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, known structures and components are shown in block diagram form in order to avoid obscuring these concepts.

[0029] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses may occur via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, devices enabling AI, etc.). Although some examples may or may not be specifically for use cases or applications, various applicability of the innovation may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and may further merge one or more aspects of the described innovations, fusion, distributed, or OEM devices or systems. In some practical settings, the device incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, (multiple) processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be practiced in various devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of various sizes, shapes, and configurations.

[0030] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are described with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 can be enabled to communicate data with an external data network 110 such as (but not limited to) the Internet.

[0031] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as LTE. 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0032] As shown, the RAN 104 includes a plurality of base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology.

[0033] Also illustrated is a radio access network 104 that supports wireless communications for multiple mobile devices. In the 3GPP standard, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device that provides a user with access to network services.

[0034] In this document, a "mobile" device does not necessarily have mobile capabilities and can be fixed. The term mobile device or mobile apparatus broadly refers to various arrangements of devices and technologies. A UE may include a number of hardware structural components that are sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular (cellular) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and various arrangements of embedded systems, for example, corresponding to the "Internet of Things" (IoT). In addition, the mobile device can be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device can also be a digital home or smart home device, such as a home audio, video and / or multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. The mobile device can also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electricity (e.g., a smart grid), lighting, water, etc.; industrial automation and enterprise devices; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weapons, etc. In addition, the mobile device can provide connected medicine or telemedicine support, that is, health care at a distance. Remote health devices may include remote health monitoring devices and remote health management devices, whose communications may be given preferential treatment or priority access over other types of information, for example, in terms of priority access for transmission of critical service data and / or associated QoS for transmission of critical service data.

[0035] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0036] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106, which may be a scheduled entity, may utilize resources allocated by the scheduling entity 108.

[0037] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0038] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. In a broad sense, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, which includes but is not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (e.g., the scheduling entity 108).

[0039] In addition, uplink and / or downlink control information and / or traffic information can be divided into frames, subframes, time slots and / or symbols according to time. As used herein, a symbol can refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme for organizing waveforms can be utilized, and the various time divisions of waveforms can have any suitable duration.

[0040] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the various base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or using any suitable transport network.

[0041] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0042] Reference now Figure 2 , by way of example and not limitation, a schematic illustration of a RAN 200 is provided. In some examples, the RAN 200 may be similar to that described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206, and small cells 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within the sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within the cell may be formed by multiple groups of antennas, each of which is responsible for communicating with UEs in a portion of the cell.

[0043] exist Figure 2In the example shown, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 that controls a remote radio head (RRH) 216 in cell 206 is shown in cell 206. That is, the base station can have an integrated antenna, or can be connected to the antenna or RRH by a feeder cable. In the example shown, cells 202, 204, and 126 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, a base station 218 is shown in a small cell 208 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home eNode B, etc.), which can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports a cell with a relatively small size. The cell size arrangement can be performed according to the system design and component constraints.

[0044] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base station / scheduling entity 108 is the same as that shown in FIG. 1.

[0045] In the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 222 and 224 may communicate with base station 210. UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 The UE / scheduled entity 106 shown in FIG.

[0046] In some examples, an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter, may be a mobile network node and may be configured to function as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0047] In a further aspect of RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) may communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a base station (e.g., base station 212). In a further example, UE 238 is illustrated communicating with UEs 240 and 242. Here, UE 238 may be used as a scheduling entity or a primary sidelink device, and UEs 240 and 242 may be used as scheduled entities or non-primary (e.g., auxiliary) sidelink devices. In yet another example, a UE may be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity 238, UEs 240 and 242 may optionally communicate directly with each other. Thus, in a wireless communication system having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration entity, or a mesh configuration, a scheduling entity and one or more scheduled entities can communicate using the scheduled resources. In some examples, the sidelink signal 227 includes sidelink traffic and sidelink control.

[0048] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of the spectrum with the help of mobile network operators that purchase licenses from government regulators. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although certain technical rules generally still need to be followed to access the unlicensed spectrum, generally any operator or device can obtain access rights. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, the holder of a license for a portion of the licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, for example, using conditions determined by the appropriate license holder to obtain access rights.

[0049] In order to achieve a low block error rate (BLER) for transmissions over the radio access network 200 while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is separated into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message may improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0050] In early 5G NR specifications, user data traffic is encoded using quasi-cyclic low-density parity check (LDPC) with two different base maps: one base map is used for large code blocks and / or high code rates, and the other base map is used otherwise. Control information and the physical broadcast channel (PBCH) are encoded using polar coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0051] However, it will be appreciated by those skilled in the art that various aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the scheduling entity 108 and the scheduled entity 106 may include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communication.

[0052] The air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP), the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexed DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0053] The air interface in the radio access network 200 can further utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link, in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full-duplex channel usually relies on the physical isolation of the transmitter and the receiver, and suitable interference elimination techniques. Full-duplex simulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate with different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, sometimes a channel is dedicated to transmission in one direction, and other times a channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot.

[0054] Used for example Figure 2 The radio protocol architecture of a RAN, such as the RAN 200 shown in FIG. 2 , may take various forms depending on the particular application. Figure 3 An example of a radio protocol architecture for the user and control planes is illustrated.

[0055] like Figure 3 As shown, the radio protocol architecture for UE and base station includes three layers: Layer 1 (L1), Layer 2 (L2) and Layer 3 (L3). L1 is the lowest layer and implements various physical layer signal processing functions. L1 will be referred to as physical layer 306 in this article. L2 308 is above physical layer 306 and is responsible for the link between UE and base station on physical layer 306.

[0056] In the user plane, the L2 layer 308 includes a medium access control (MAC) layer 310, a radio link control (RLC) layer 312, a packet data convergence protocol (PDCP) 314 layer, and a service data adaptation protocol (SDAP) layer 316, which are terminated at a base station on the network side. Although not shown, the UE may have several upper layers above the L2 layer 308, including at least one network layer (e.g., an IP layer and a user data protocol (UDP) layer), which is terminated at a user plane function (UPF) on the network side and one or more application layers.

[0057] The SDAP layer 316 provides mapping between 5G core (5GC) quality of service (QoS) flows and data radio bearers, and performs QoS flow ID marking in both downlink and uplink packets. The PDCP layer 314 provides packet sequence numbering, ordered delivery of packets, retransmission of PDCP protocol data units (PDUs), and delivery of upper layer data packets to the lower layer. PDUs may include, for example, Internet Protocol (IP) packets, Ethernet frames, and other unstructured data (i.e., machine type communications (MTC), hereinafter collectively referred to as "packets"). The PDCP layer 314 also provides header compression for upper layer data packets to reduce radio transmission overhead, provides security by encrypting data packets, and provides integrity protection for data packets. The RLC layer 312 provides segmentation and reassembly of upper layer data packets, error correction by automatic repeat request (ARQ), and sequence numbering independent of PDCP sequence numbering. The MAC layer 310 provides multiplexing between logical and transport channels. The MAC layer 310 is also responsible for allocating various radio resources (eg, resource blocks) in one cell between UEs and for HARQ operations. The physical layer 306 is responsible for transmitting and receiving data on a physical channel (eg, within a time slot).

[0058] In the control plane, the radio protocol architecture for UE and base station is basically the same for L1 306 and L2 308, except that there is no SDAP layer in the control plane and there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) layer 318 in L3 and a higher non-access stratum (NAS) layer 320. The RRC layer 318 is responsible for establishing and configuring signaling radio bearers (SRBs) and data radio bearers (DRBs) between the base station and the UE, paging initiated by 5GC or NG-RAN, and broadcasting of system information related to the access stratum (AS) and non-access stratum (NAS). The RRC layer 318 is further responsible for QoS management, mobility management (e.g., handover, cell selection, inter-RAT mobility), UE measurement and reporting, and security functions. The NAS layer 320 terminates at the AMF in the core network and performs various functions such as authentication, registration management, and connection management.

[0059] Various aspects of the present disclosure are generally directed to utilizing the SDAP layer to facilitate QoS flow remapping from one data radio bearer (DRB) to another DRB. Figure 4, a diagram illustrating an exemplary QoS structure 400 is provided that facilitates aspects disclosed herein. In some examples, the QoS architecture 400 is implemented within a next generation RAN (e.g., NG-RAN) 402 for both new radio (NR) connected to a 5G core network (5GC) 404 and E-UTRA connected to the 5GC. The NG-RAN 402 includes a user equipment (UE) 406 and a Node B (e.g., a next generation (ng)-eNB or gNB) 408, and the 5GC includes a user plane function (UPF) 410. The 5GC 404 may further include other core network nodes (not shown), such as a core access and mobility management function (AMF), a session management function (SMF), and a policy control function (PCF).

[0060] For each UE (e.g., UE 406), 5GC 404 establishes one or more PDU sessions 412. Each PDU session 412 may include one or more data streams 418a-418c (e.g., IP, Ethernet, and / or unstructured data streams), each of which is associated with a set of one or more applications. 5GC 404 may further select a QoS to be associated with each data stream 418a-418c in the PDU session 412. At the NAS level, a QoS flow is the finest granularity of QoS differentiation in a PDU session and is characterized by both a QoS profile provided by 5GC 404 to NB 408 and (multiple) QoS rules provided by 5GC 404 to UE 406. NB 408 uses the QoS profile to determine the treatment on the radio interface, while the QoS rules specify the mapping between uplink user plane services and QoS flows 418a-418c to UE 406.

[0061] The QoS profile may include one or more QoS parameters. For example, the QoS profile may include an Allocation and Retention Priority (ARP), which may indicate a priority level for allocation and reservation of data radio bearers; and a 5G QoS Identifier (5QI), which is associated with a specific 5G QoS feature. Examples of 5G QoS features may include resource type (e.g., guaranteed bit rate (GBR), delay critical GBR, or non-GBR), priority level, packet delay budget, packet error rate, averaging window, and minimum data burst. For GBR QoS flows, the QoS profile may further specify a guaranteed flow bit rate (GFBR) for both uplink and downlink, a maximum flow bit rate (MFBR) for uplink and downlink, and a maximum packet loss rate for uplink and downlink. For non-GBR QoS flows, the QoS profile may include a reflective QoS attribute (RQA). When RQA is included, it indicates that some (not necessarily all) services carried on this QoS flow are subject to reflective QoS (RQoS) at the NAS layer. Standardized or preconfigured 5G QoS features are derived from 5QI values ​​and are not explicitly signaled. Include signaled QoS characteristics as part of the QoS profile.

[0062] Additionally, an aggregate maximum bit rate is associated with each PDU session 412 (session-AMBR) and each UE 406 (UE-AMBR). The session-AMBR limits the aggregate bit rate that can be expected to be provided across all non-GBR QoS flows for a particular PDU session 412. The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all non-GBR QoS flows of a UE.

[0063] NB 408 establishes one or more data radio bearers (DRBs) 414a and 414b for each PDU session 412. NB 408 also maps packets belonging to different PDU sessions 412 to different DRBs. Here, NB 408 establishes at least one default DRB (e.g., DRB 414a) for each PDU session 412. At the access layer (AS) level, DRBs define packet handling on the radio interface (Uu). DRBs serve packets using the same packet forwarding handling. Separate DRBs can be established for QoS flows that require different packet forwarding handling, or several QoS flows belonging to the same PDU session can be multiplexed into the same DRB. Within each PDU session 412, NB 408 determines how to map multiple QoS flows to DRBs. For example, NB 408 can map GBR flows and non-GBR flows, or more than one GBR flow to the same DRB. For QoS flow(s) configured during establishment of a PDU session, the timing of establishing non-default DRB(s) (eg, DRB 414b) between NB 408 and UE 406 may be different from the time the PDU session is established.

[0064] The NG-RAN 402 and 5GC 404 ensure quality of service (e.g., reliability and target latency) by mapping packets to appropriate QoS flows 418a-418c and DRBs 414a and 414b. The NAS layer performs packet filtering in both the UE 406 and the 5GC 404 to associate uplink (UL) and downlink (DL) packets with QoS flows 418a-419c. The AS layer, which is a functional layer between the UE 406 and the NB 408, implements mapping rules in the UE 406 and the NB 408 to associate UL and DL QoS flows 418a-418c with the DRBs 414a and 414b. Therefore, there is a two-step mapping of IP flows to QoS flows (in NAS) and from QoS flows to DRBs (in AS). In Figure 4 In the example shown, QoS flows 418a and 418b are mapped to DRB 414a, while QoS flow 418c is mapped to DRB 414b.

[0065] Each QoS flow 418a-418c is identified in the PDU session 412 by a QoS flow ID (QFI) carried in the encapsulation header by a next generation tunnel (NG-U tunnel) 416 provided on the interface between the NB 408 and the UPF 410 (NG-U). The QoS flow to DRB mapping performed by the NB 408 is based on the QFI and the associated QoS profile (i.e., QoS parameters and QoS characteristics). For example, in the uplink, the NB 408 can use reflective mapping or explicit configuration to control the mapping of QoS flows 418a-418c to DRBs 414a and 414b. In reflective mapping, for each DRB 414a and 414b, the UE 406 monitors the QFI(s) of the downlink packets and applies the same mapping in the uplink. That is, for a DRB (e.g., DRB 414a), UE 406 maps uplink packets belonging to QoS flows 418a and 418b corresponding to QFI(s) and PDU sessions 412 observed in downlink packets for the DRB 414a. To enable this reflective mapping, NB 408 marks downlink packets on the radio interface (Uu) with the QFI. In an explicit configuration, NB 408 can configure the uplink "QoS flow to DRB mapping" through RRC. UE 406 can apply the latest update of the mapping rules, regardless of whether the update is performed via reflective mapping or explicit configuration.

[0066] In the downlink, for RQoS purposes, the NB 408 signals the QFI over the wireless interface (Uu), and if neither the NB 408 nor the NAS (as indicated by RQA) intends to use reflective mapping for the (multiple) QoS flows carried in the DRB, then the QFI is not signaled over Uu for that DRB. However, the NB 408 can configure the UE 406 to still signal the QFI over Uu. As described above, for each PDU session 412, a default DRB (e.g., DRB 414a) is configured. If an incoming UL packet does not match either the RRC-configured or reflectively-configured "QoS Flow ID to DRB mapping", the UE 406 can map the UL packet to the default DRB 414a for the PDU session 412.

[0067] Figure 5 is a diagram illustrating an exemplary remapping of a QoS flow from a first data radio bearer (DRB) to a second DRB. Figure 5 An example is provided from the perspective of a UE, which shows a 5G uplink mapping relationship 500 for a single PDU session as part of a QoS implementation. Figure 5A single PDU session is illustrated in FIG, but it should be understood that a UE may have multiple PDU sessions. Each PDU session of the UE may have multiple DRBs, each DRB may have multiple QoS flows (e.g., where each QoS flow is identified by a QFI), and each QFI may contain multiple SDFs.

[0068] Figure 5 The UE protocol stack and the processing of uplink packets from service data flows (SDFs) 514a-514e associated with the PDU session are further illustrated. For ease of understanding, a service data flow (SDF) can be conceptually viewed as data / packets / frames from a set of applications on a wireless communication device (e.g., UE).

[0069] exist Figure 5 In the example shown, an application layer 502, a NAS layer 504, a SDAP layer 506, PDCP layers 508a and 508b, RLC layers 510a and 510b, and MAC and PHY layers 512 are illustrated in the protocol stack. The NAS layer 504 and the SDAP layer 506 may correspond to, for example, Figure 3 NAS layer 320 and SDAP layer 316 are shown. In addition, PDCP layers 508a and 508b may correspond to PDCP layer 314, and RLC layers 510a and 510b may correspond to Figure 3 The RLC layer 312 is shown. In addition, the MAC and PHY layers 508 may correspond to, for example, Figure 3 The MAC layer 310 and the physical layer 306 are shown. Each of the PDCP layers 508a and 508b corresponds to a corresponding PDCP entity implemented within a corresponding DRB 520a and 520b, and each of the RLC layers 510a and 510b corresponds to a corresponding RLC entity implemented within a corresponding DRB 520a and 520b.

[0070] Once the PDU session is established, the UE may be configured (e.g., using a control message from the NB) to map the first QoS flow (QFI=1) 516a to DRB1 520a. The UE may be further configured to map the second QoS flow (QFI=2) 516b to DRB2 520b, and the third QoS flow (QFI=3) to DRB2 520b. The NAS layer 504 may then perform packet filtering to associate UL packets with QoS flows. For example, the NAS layer 504 may associate packets from SDF#1 514a with the first QoS flow 516a, packets from SDF#2 514b and SDF#3 514c with the second QoS flow 516b, and packets from SDF#4 514d and SDF#5 514e with the third QoS flow 516c.

[0071] exist Figure 5 In the example shown, SDF#1 514a generates four UL packets (Pkt1 518a, Pkt2 518b, Pkt3 518c, and Pkt4 518d). When UL packets 1 and 2 (Pkt1 518a and Pkt2 518b) associated with the first QoS flow 516a arrive at the SDAP layer 506, the SDAP layer 506 maps Pkt1 518a and Pkt2 518b to DRB1 520a according to the network configuration of the UE described above. Before the SDAP receives UL packets 3 and 4 (Pkt3 518c and Pkt4 518d), the network (e.g., NB via explicit or reflective mapping) reconfigures the UE to map the first QoS flow 516a to DRB2 520a. Then, when UL packets 3 and 4 (Pkt 3 518c and Pkt 4 518d) of the first QoS flow 516a arrive at the SDAP layer 506, the SDAP layer 506 maps Pkt3 518c and Pkt4 518d to DRB2 520b according to the new network configuration of the UE.

[0072] In some examples, each DRB 520a and 520b may be able to guarantee that packets within the DRB are received by a receiver (e.g., NB) in their original order because the PDCP entity (here, an entity is an instance of a "protocol layer") of each DRB will tag each packet with a sequence number. The PDCP entity of each DRB maintains its own PDCP sequence number (SN), independent of the PDCP entities of other DRBs. For example, the PDCP entity 508a of DRB1 520a may tag Pkt1 518a with PDCP sequence number SN=901 and Pkt2 518b with PDCP sequence number SN=902. In addition, the PDCP entity 508b of DRB2 520b may tag Pkt3 518c with PDCP sequence number SN=1 and Pkt4 518d with PDCP sequence number SN=2. However, the MAC and PHY layers 512 may not be able to guarantee in-order delivery on the receiver side. For example, the receiver may receive Pkt3 518c and Pkt4 before Pkt1 518a and Pkt2 518b.

[0073] Therefore, when the receiver receives the four packets 518a-518b, the receiver knows that packets 518a-518d belong to the same QoS flow (e.g., due to the QFI). However, due to the different PDCP sequence numbers caused by the remapping from DRB1 520a to DRB2 520b between the second packet (Pkt2 518b) and the third packet (Pkt3 518c), the receiver may not be able to restore the original order of packets 518a-518d at the application layer 502 of the UE. In particular, the receiver may not be able to distinguish when the packet from DRB1 520a ends and when the packet from DRB2 520b begins. For example, due to retransmissions by lower layers (e.g., RLC layer, MAC layer), there may be an intermediate time period during which the receiver may receive packets from both DRB1 520a and DRB2 520b.

[0074] In addition, the SDAP layer 506 does not include a sequence number in the SDAP PDU provided to the PDCP entities 508a and 508b, and therefore, the receiver is unable to perform reordering of the SDAP PDU in a scenario in which the receiver is unable to perform reordering of the PDCP PDU due to remapping of the QoS flow from one DRB to another DRB.

[0075] Thus, various aspects of the present invention provide mechanisms to ensure that a receiver is able to record the original order of packets generated at a transmitter. In some examples, the SDAP layer 506 may generate an independent SDAP PDU 522 including control information that includes an indication that the final SDAP data PDU associated with a QoS flow (e.g., QoS flow 516a) has been transmitted on the old DRB (DRB1 520a) upon detecting a remapping configuration change (e.g., remapping QoS flow 516a from DRB1 520a to DRB2 520b). Such detection may be based, for example, on a radio resource control (RRC) message or a reflection mapping.

[0076] Thus, the SDAP PDU 522 may be considered as an SDAP control PDU that acts as an “end marker” SDAP PDU in the SDAP layer 506. The SDAP layer 506 may generate the SDAP control PDU 522 after transmitting the last / final SDAP data PDU (e.g., Pkt2 518b) for the QoS flow 516a to DRB1 520a. The SDAP control PDU 522 may also be provided to an old DRB (e.g., DRB1 520a) and processed by the PDCP entity 508a to preserve the order of the end marker SDAP control PDU 522. Using the above example, the PDCP entity 508a may assign the next PDCP sequence number (e.g., SN=903) to the SDAP control PDU 522. Thus, the order of packets may be preserved by the PDCP entity 508a, so that when the receiver receives the SDAP control PDU 522, the receiver knows that all packets for the first QoS flow 516a on DRB1 520a have been received and processed. In this way, the SDAP entity can utilize the end-marked SDAP PDU 522 at a receiver (e.g., a UE) to indicate that the SDAP entity should stop mapping the SDAP session data units (SDUs) of the QoS flow 516a indicated by the QFI to the DRB (e.g., DRB1 520a) on which the end-marked SDAP PDU 522 is transmitted.

[0077] It should be noted that the PDCP entity 508a cannot distinguish SDAP control PDUs from SDAP data PDUs, and therefore, both types of SDAP PDUs can be processed by the PDCP entity 508a in the same manner, thereby allowing the PDCP entity 508a to process the SDAP control PDUs as described above and preserve the order of all SDAP PDUs. Since all packets within a DRB can be received in sequence at the PDCP layer on the receiver side, when the receiver receives the SDAP control PDU, the receiver can determine that all packets on the old DRB (DRB1 520a) have been received. Therefore, upon receiving the SDAP control PDU, the receiver can forward the remapped packets (e.g., Pkt3 518c and Pkt4 518d) received on the new DRB (e.g., DRB2 520b) to the upper layer.

[0078] In some examples, the SDAP control PDU may include the QFI of the remapped QoS flow. For example, the SDAP layer 506 may set the "QFI" of the SDAP control PDU to the QFI of the remapped QoS flow (e.g., QFI=1). In addition, the SDAP control PDU may include a control identifier to distinguish the SDAP control PDU (which includes a control message generated by the SDAP layer) from the SDAP data PDU (e.g., including application data). In one example, the value of the control identifier may be set differently for the SDAP control PDU and the SDAP data PDU (i.e., where the SDAP layer sets the identifier of the SDP control PDU to indicate that the PDU is an "SDAP control PDU"). For example, the control identifier may include a one-bit "data / control (D / C)" identifier (e.g., D / C parameter=0 indicates an SDAP control PDU, and D / C parameter=1 indicates an SDAP data PDU).

[0079] In other examples, when Figure 5 When performing remapping configuration by a transmitter (e.g., UE), the transmitter may first determine, for example, whether there are any untransmitted packets (e.g., packets that have not yet been processed by the SDAP layer 506) belonging to the old DRB (e.g., DRB1 520a) waiting in a transmit buffer associated with the SDAP layer 506. If there is at least one untransmitted packet belonging to the old DRB (e.g., DRB1 520a), the SDAP layer 506 may set an end marker parameter in the last untransmitted packet belonging to DRB1 520a. Otherwise, if there are no remaining untransmitted packets, the SDAP layer 506 may generate an end marker SDAP control PDU 522.

[0080] In this example, the SDAP layer 506 may set an end marker parameter in the SDAP header of the last data packet of the QFI (e.g., the first QoS flow 516a) mapped to the old DRB1 520a. For example, assuming that when a remapping configuration change is detected (e.g., remapping the QoS flow 516a from DRB1 520 to DRB2 520b), SDF#2 has generated Pkt1 518a and Pkt2 518b, but has not yet generated Pkt3 518c or Pkt4 518d, the SDAP layer 506 may set an end marker parameter in the SDAP header of the SDAP data PDU containing Pkt2 518b. In some examples, the end marker parameter may include a one-bit end marker parameter (e.g., an end marker parameter = 0 indicates that the SDAP PDU is not the last / final SDAP data PDU of the DRB, while an end marker parameter = 1 indicates that the SDAP PDU is the last / final SDAP data PDU of the DRB).

[0081] Based on the end marker parameter, the receiver SDAP entity may consider all packets for the remapped QFI from the old DRB1 520a (e.g., Pkt1 518a and Pkt2 518b) to be received before any packets for the remapped QFI from the new DRB2 520b (e.g., Pkt3 518c and Pkt4 518d), regardless of whether the old DRB1 packets are actually received before or after the new DRB1 packets. However, if the receiver PDCP entity does not receive and deliver to the receiver SDAP layer a packet with an end marker parameter in the SDAP header for the remapped QFI from the old DRB 1 (i.e., Pkt2 518b), the receiver SDAP layer may not be able to deliver to upper layers any received packets for the remapped QFI from the new DRB2 520b (in Example 1, these packets are packets #3 and #4).

[0082] In this example, the complexity of the implementation is higher than the example in which the SDAP control PDU is generated when the remapping is detected. However, by allowing the SDAP layer to generate the SDAP control PDU when there are no untransmitted packets waiting in the buffer, the transmitter is able to perform the remapping immediately without having to wait for the next SDAP data PDU to include the end marker parameter. In addition, if the old DRB is not required for other flows (e.g., DRB1 520a), by generating the SDAP control PDU when there are no untransmitted packets, the old DRB can be released faster than if the SDAP layer needs to wait for the next SDAP data PDU to include the end marker parameter.

[0083] In other examples, when the network configures a remapping of a QoS flow (e.g., QFI=1 514a) from DRB1 520a to DRB2 520b, if there are no more unprocessed packets available on the old DRB1 520a (e.g., all existing packets have been processed by the SDAP layer 506, even though they may not have been sent over the air yet and may still be buffered by lower layers (e.g., PDCP layer 508a)), then when new incoming packets of the remapped QFI (e.g., QFI=1 516a) arrive at the SDAP layer 506, the SDAP layer 506 may set an end marker parameter in the first new incoming packet from the remapped QFI 516a. The SDAP layer 506 may then transmit the packet containing the end marker parameter on the old DRB (e.g., DRB1 520a). The SDAP layer 506 may then send subsequent incoming packets of the remapped QFI on the new DRB (e.g., DRB2 520b) without setting the end marker.

[0084] exist Figure 6600 and SDAP data PDU 610. As shown, the SDAP control PDU 600 is configured to have a total length of 8 bits at the SDAP layer. The SDAP control PDU 600 includes a data / control (D / C) bit 602 indicating whether the SDAP control PDU 600 is an SDAP data PDU or an SDAP control PDU. For example, the D / C bit 602 may be set to zero to indicate that the SDAP control PDU 600 is an SDAP control PDU. The SDAP control PDU 600 may further include a reserved field 604, and may further include a QFI parameter 606, which identifies a specific QoS flow that can be applied to the control information (e.g., D / C bit 602) in the SDAP control PDU 600. For example, the QFI parameter may be set to a value corresponding to a QoS flow that has been remapped from one DRB to another DRB.

[0085] The SDAP data PDU 610 includes an SDAP header 612 within the first octet (octet 1) having a total length of 8 bits. The SDAP header 612 may include, for example, a D / C bit 616, a reserved field 618, and a QFI parameter 620. The D / C bit 616 indicates whether the SDAP control PDU 600 is an SDAP data PDU or an SDAP control PDU. For example, the D / C bit may be set to one to indicate that the SDAP data PDU 610 is an SDAP data PDU. The QFI parameter 620 identifies a specific QoS flow associated with the SDAP data PDU 610. The SDAP data PDU 610 may further include a body 614, which may include data 622 (e.g., application data) starting from octet 2, as shown, and may have a variable length.

[0086] Figure 7Another example of an SDAP data PDU 700 is illustrated. As shown, the SDAP data PDU 700 includes an SDAP header 702 within the first octet (octet 1), which has a total length of 8 bits. The SDAP header 702 may include, for example, an end marker parameter 706, a reserved field 708, and a QFI parameter 710. The end marker parameter 706 indicates whether the SDAP data PDU is the last / final SDAP data PDU for the DRB. For example, the end marker parameter 706 may include a single end marker bit, wherein the end marker parameter = 0 indicates that the SDAP data PDU is not the last / final SDAP data PDU for the DRB, and the end marker parameter = 1 indicates that the SDAP data PDU is the last / final SDAP data PDU for the DRB. The QFI parameter 710 identifies a specific QoS flow associated with the SDAP data PDU 700. The SDAP data PDU 700 may further include a body 704 that contains data 712 (eg, application data) that may begin at octet 2, as shown, and may have a variable length.

[0087] Figure 8 is a block diagram illustrating an example of a hardware implementation for a scheduled entity 800 employing a processing system 814. For example, the scheduled entity 800 may be a processor disclosed herein. Figure 1 , 2 and / or any one or more of the user equipment (UE) shown in 4.

[0088] The scheduled entity 800 may be implemented with a processing system 814 including one or more processors 804. Examples of processors 804 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. In various examples, the scheduled entity 800 may be configured to perform any one or more of the functions described herein. That is, as utilized in the scheduled entity 800, the processor 804 may be used to implement any one or more of the processes and procedures described below. In some instances, the processor 804 may be implemented via a baseband or modem chip, and in other implementations, the processor 804 itself may include multiple devices that are distinct and different from the baseband or modem chip (e.g., in such a scenario, may work together to implement the embodiments discussed herein). And as described above, various hardware arrangements and components other than the baseband modem processor may be used in the implementation, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0089] In this example, the processing system 814 can be implemented with a bus architecture, which is generally represented by bus 802. Depending on the specific application and overall design constraints of the processing system 814, the bus 802 may include any number of interconnecting buses and bridges. The bus 802 communicatively couples various circuits including one or more processors (generally represented by processor 804), memory 805, and computer-readable media (generally represented by computer-readable media 806). The bus 802 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described in detail. The bus interface 808 provides an interface between the bus 802 and the transceiver 810. The transceiver 810 provides a communication interface or component for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 812 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be optionally provided.

[0090] The processor 804 is responsible for managing the bus 802 and general processing, including executing software stored on the computer-readable medium 806. The software, when executed by the processor 804, causes the processing system 814 to perform the various functions described below for any particular device. The computer-readable medium 806 and memory 805 can also be used to store data that is manipulated by the processor 804 when executing the software.

[0091] One or more processors 804 in the processing system can execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or other forms. The software can reside on a computer-readable medium 806.

[0092] The computer-readable medium 806 may be a non-transitory computer-readable medium. Non-transitory computer-readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. For example, the computer-readable medium may also include carrier waves, transmission lines, and any other suitable medium for transmitting software and / or instructions that can be accessed and read by a computer. The computer-readable medium 806 may reside in the processing system 814, outside the processing system 814, or distributed between multiple entities including the processing system 814. The computer-readable medium 806 may be embodied in a computer program product. In some examples, the computer-readable medium 806 may be part of the memory 805. As an example, a computer program product may include a computer-readable medium in packaging materials.Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0093] In some aspects of the present disclosure, the processor 804 may include circuits configured for various functions. For example, as described herein, the processor 804 may include a QoS mapping circuit 841 configured for various functions, including, for example, facilitating quality of service (QoS) flow remapping using a service data adaptation protocol (SDAP) layer. The QoS mapping circuit 841 may be configured to detect a mapping reconfiguration of a first QoS flow from a first data radio bearer (DRB) to a second DRB. For example, the QoS mapping circuit 841 may be configured to detect a mapping reconfiguration via a radio resource control (RRC) message transmitted from a base station or via a reflection mapping, wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received from the base station via a second DRB after being initially received via the first DRB.

[0094] The QoS mapping circuit 841 may be further configured to generate an SDAP control protocol data unit (PDU) in response to the mapping reconfiguration, wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. In some examples, the SDAP control PDU may be configured to be easily distinguished from the SDAP data PDU. For example, the QoS mapping circuit 841 may be configured to include a control identifier within the SDAP control PDU to facilitate the distinction between the SDAP control PDU and the SDAP data PDU. In a specific implementation, the QoS mapping circuit 841 may be configured to include a data / control (D / C) bit in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates the distinction between the SDAP control PDU and the SDAP data PDU.

[0095] The QoS mapping circuit 841 may be further configured to include a QoS flow identifier (QFI) parameter within the SDAP control PDU. The QFI parameter identifies a specific QoS flow that can be applied to the control information included in the SDAP control PDU. For example, the QoS mapping circuit 841 may be configured to set the QFI parameter within the SDAP control PDU to a value corresponding to the first QoS flow. The QoS mapping circuit 841 may be further configured to maintain the order in which the transmitter-side SDAP layer transmits the SDAP control PDU after transmitting the final SDAP data PDU associated with the first QoS flow via the first DRB. In some examples, maintaining the order helps the receiver-side SDAP layer receive the SDAP control PDU after receiving the final SDAP data PDU associated with the first QoS flow via the first DRB. For example, the QoS mapping circuit 841 may be configured to maintain this order by utilizing a packet data convergence protocol (PDCP) entity associated with the first DRB.

[0096] The QoS mapping circuit 841 may be further configured to generate an SDAP control PDU based on whether the untransmitted SDAP data PDU is associated with the first QoS flow. In some examples, the untransmitted SDAP data PDU may be in a transmission buffer 815 associated with the SDAP layer, which may be included in, for example, the memory 805. For example, the QoS mapping circuit 841 may be configured to include an end marker parameter in the SDAP header of the untransmitted SDAP data PDU instead of generating an SDAP control PDU. The end marker parameter may indicate that the untransmitted SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB.

[0097] In other examples, the QoS mapping circuit 841 may be further configured to detect a mapping reconfiguration of a first quality of service (QoS) flow from a first data radio bearer (DRB) to a second DRB, and set an end marker parameter in a header of a first SDAP data protocol data unit (PDU) received from an upper layer after the mapping reconfiguration. The end marker parameter provides an indication that the first SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB.

[0098] The processor 804 may also include a DL reception and processing circuit 842 configured to receive and process downlink data, control information, and other signals received in one or more subframes or time slots. For example, the DL reception and processing circuit 842 may be configured to receive an RRC message via the transceiver 810 indicating a mapping reconfiguration of the first QoS flow from the first DRB to the second DRB. The DL reception and processing circuit 842 may be further configured to receive, via the transceiver 810, a packet associated with the first QoS flow via the second DRB after being initially received via the first DRB. The DL reception and processing circuit 842 may be further configured to execute the DL reception and processing software 852 stored in the computer-readable medium 806 to implement one or more functions described herein.

[0099] The processor 804 may also include a UL generation and transmission circuit 843, which is configured to generate and transmit data and control information within one or more subframes or time slots. For example, the UL generation and transmission circuit 843 may be configured to receive an SDAP control PDU from the QoS mapping circuit 841 via a first DRB, and transmit the SDAP control PDU to a scheduling entity (e.g., a base station) via the transceiver 810. The UL generation and transmission circuit 843 may be further configured to receive an SDAP data PDU from the QoS mapping circuit 841, the SDAP data PDU including an end marker parameter indicating that the SDAP data PDU is the final SDAP data PDU associated with the QoS flow on a specific DRB, and transmit the SDAP data PDU to the scheduling entity (e.g., a base station) via the transceiver 810. The UL generation and transmission circuit 843 may be further configured to execute UL generation and transmission software 853 stored in the computer-readable medium 806 to implement one or more functions described herein.

[0100] Fig. 9 904. The scheduling entity 900 may be implemented as follows: Figure 1 , 2 and / or any one or more of the base stations shown in 4.

[0101] Processing system 914 can be used with Fig. 9 The processing system 914 shown is substantially the same, including a bus interface 908, a bus 902, a memory 905, a processor 904, and a computer readable medium 906. In addition, the scheduling entity 900 may include the same Fig. 9 An optional user interface 912 and transceiver 910 are substantially similar to those shown. That is, as utilized in scheduling entity 900, processor 904 may be used to implement any one or more of the processes described below.

[0102] In some aspects of the present disclosure, the processor 904 may include a QoS mapping circuit 941 configured for various functions, including, for example, facilitating quality of service (QoS) flow remapping using a service data adaptation protocol (SDAP) layer, as described herein. In some examples, the QoS mapping circuit 941 may be configured to receive at least one SDAP data PDU associated with a first QoS flow from a scheduled entity via a first DRB, and to receive at least one SDAP data PDU associated with the first QoS flow via a second DRB. In some examples, the QoS mapping circuit 941 may be further configured to forward at least one SDAP data PDU received via the second DRB to an upper layer in response to receiving via the first DRB an SDAP control PDU applicable to the first QoS flow indicating that the final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB.

[0103] The QoS mapping circuit 941 may be further configured to identify the SDAP control PDU based on a control identifier included in the SDAP control PDU, and to identify the SDAP data PDU based on a control identifier included in the SDAP header of the SDAP data PDU. In some examples, the control identifier facilitates the distinction between the SDAP control PDU and the SDAP data PDU. For example, the QoS mapping circuit 941 may be configured to identify the SDAP control PDU by ascertaining the value of a D / C bit in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates the distinction between the SDAP control PDU and the SDAP data PDU.

[0104] The QoS mapping circuit 941 may be further configured to identify a QoS flow identifier (QFI) parameter included in the SDAP control PDU. The QoS mapping circuit 941 may then be further configured to apply the control information of the SDAP control PDU only to the QoS flow identified by the QFI parameter included in the SDAP control PDU.

[0105] In other examples, the QoS mapping circuit 941 can be configured to forward at least one SDAP data PDU received via the second DRB to an upper layer in response to detecting an end marker parameter in the SDAP header of at least one SDAP data PDU applicable to the first QoS flow and received via the first DRB. The QoS mapping circuit 941 can be further configured to execute QoS mapping software 941 stored in the computer-readable medium 906 to implement one or more functions described herein.

[0106] The processor 904 may further include a DL generation and transmission circuit 942 configured to generate and transmit downlink data, control information, and other signals within one or more subframes or time slots. For example, the DL generation and transmission circuit 942 may be configured to transmit an RRC message to the scheduled entity via the transceiver 910, the RRC message indicating a mapping reconfiguration of the first QoS flow from the first DRB to the second DRB. The DL generation and transmission circuit 942 may also be configured to transmit a packet associated with the first QoS flow via the second DRB via the transceiver 910 after initially transmitting via the first DRB. The DL generation and transmission circuit 942 may be further configured to execute DL generation and transmission software 952 stored in the computer-readable medium 906 to implement one or more functions described herein.

[0107] The processor 904 may further include a UL receiving and processing circuit 943, which is configured to receive and process data and control information received in one or more subframes or time slots. For example, the UL receiving and processing circuit 943 may be configured to provide the QoS mapping circuit 941 with an SDAP control PDU of a first QoS flow received from a scheduled entity via a first DRB. The UL receiving and processing circuit 943 may be further configured to provide the QoS mapping circuit 941 with an SDAP data PDU of a first QoS flow received from a scheduled entity on a first DRB. In some examples, the SDAP data PDU may include an end marker parameter indicating that the SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB. The UL receiving and processing circuit 943 may be further configured to provide the QoS mapping circuit 941 with an SDAP data PDU of a first QoS flow received from a scheduled entity on a second DRB. The UL receiving and processing circuit 943 may be further configured to execute the UL receiving and processing software 953 stored in the computer-readable medium 906 to implement one or more functions described herein.

[0108] Fig.10 1 is a flow chart illustrating an exemplary process 1000 for facilitating QoS flow remapping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, process 1000 may consist of Figure 8 1000 is performed by the scheduled entity 800 shown in FIG. In some examples, the process 1000 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0109] At block 1002, a scheduled entity may detect a mapping reconfiguration of a first QoS flow from a first DRB to a second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from a scheduling entity in wireless communication with the scheduling entity. In other examples, the scheduled entity may detect the mapping reconfiguration via reflective mapping, wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received from the scheduling entity via the second DRB after being initially received via the first DRM. For example, the above reference Figure 8 The QoS mapping circuitry 841 shown and described, together with the DL reception and processing circuitry 842, can detect mapping reconfigurations.

[0110] At box 1004, the scheduled entity may generate an SDAP control PDU in response to the mapping reconfiguration to indicate that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. In some examples, the SDAP control PDU may include a control identifier that facilitates distinguishing between the SDAP control PDU and the SDAP data PDU. For example, the control identifier may include a data / control (D / C) bit in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates distinguishing between the SDAP control PDU and the SDAP data PDU. In some examples, the SDAP control PDU may further include a QoS flow identifier (QFI) parameter that identifies the first QoS flow. For example, the above reference Figure 8 The QoS mapping circuit 841 shown and described may generate the SDAP control PDU.

[0111] At block 1006, the scheduled entity may transmit the SDAP control PDU to the receiver (eg, the scheduling entity) via the first DRB. Figure 8 The UL generation and transmission circuit 843 is shown and described in conjunction with the transceiver 810 as being capable of transmitting the SDAP control PDU to the receiver.

[0112] Fig.11 1 is a flow chart illustrating another exemplary process 1100 for facilitating QoS flow remapping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and certain illustrated features may not be required for implementation of all embodiments. In some examples, the process 1100 may be composed of Figure 8 1100 is performed by the scheduled entity 800 shown in FIG. In some examples, the process 1100 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0113] At block 1102, a scheduled entity may detect a mapping reconfiguration of a first QoS flow from a first DRB to a second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from a scheduling entity in wireless communication with the scheduled entity. In other examples, the scheduled entity may detect the mapping reconfiguration via reflective mapping, wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received from the scheduling entity via the second DRB after being initially received via the first DRM. For example, the above reference Figure 8 The QoS mapping circuitry 841 shown and described, together with the DL reception and processing circuitry 842, can detect mapping reconfigurations.

[0114] At block 1104, the scheduled entity may identify whether the buffer includes untransmitted SDAP data PDUs associated with the first QoS flow. In some examples, the buffer may be associated with an SDAP layer in the scheduled entity. For example, the above reference Figure 8 The QoS mapping circuitry 841 shown and described may identify whether there are undelivered SDAP data PDUs.

[0115] If the buffer includes an untransmitted SDAP data PDU associated with the first QoS flow (Y branch of block 1104), then at block 1106, the scheduled entity may include an end marker parameter in the SDAP header of the untransmitted SDAP data PDU. The end marker parameter indicates that the untransmitted SDAP data PDU is the last SDAP data PDU associated with the first QoS flow on the first DRB. For example, the above reference Figure 8 The QoS mapping circuit 841 is shown and described as being capable of including an end marker parameter in untransmitted SDAP data PDUs.

[0116] At block 1108, the scheduled entity may transmit the untransmitted SDAP data PDU including the end marker parameter to the receiver (eg, the scheduling entity). Figure 8 The UL generation and transmission circuit 843 is shown and described in conjunction with the transceiver 810 to transmit untransmitted SDAP data PDUs to the receiver.

[0117] If the buffer does not include an untransmitted SDAP data PDU associated with the first QoS flow (N branch of box 1104), then in box 1110, the scheduled entity may generate an SDAP data PDU in response to the mapping reconfiguration to indicate that the final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. In some examples, the SDAP control PDU may include a control identifier that facilitates distinguishing between the SDAP control PDU and the SDAP data PDU. For example, the control identifier may include a data / control (D / C) bit in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates distinguishing between the SDAP control PDU and the SDAP data PDU. In some examples, the SDAP control PDU may further include a QoS flow identifier (QFI) parameter that identifies the first QoS flow. For example, the above reference Figure 8 The QoS mapping circuit 841 shown and described may generate the SDAP control PDU.

[0118] At block 1112, the scheduled entity may transmit the SDAP control PDU to the receiver (eg, the scheduling entity) via the first DRB. Figure 8The UL generation and transmission circuit 843 is shown and described in conjunction with the transceiver 810 to transmit the SDAP control PDU to the receiver.

[0119] Fig.12 1 is a flow chart illustrating another exemplary process 1200 for facilitating QoS flow remapping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and certain illustrated features may not be required for implementation of all embodiments. In some examples, process 1200 may be performed by Fig. 9 1200 is performed by the scheduled entity 900 shown in FIG. In some examples, the process 1200 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0120] At block 1202, the scheduling entity may receive at least one SDAP data PDU associated with a first QoS flow via a first DRB and receive at least one SDAP data PDU associated with the first QoS flow via a second DRB. Fig. 9 The QoS mapping circuit 941 shown and described together with the UL reception and processing circuit 943 and the transceiver 910 can receive at least one SDAP data PDU associated with the first QoS flow via the first DRB, and receive at least one SDAP data PDU associated with the first QoS flow via the second DRB.

[0121] At box 1204, the scheduling entity may receive, via the first DRB, an SDAP control PDU applicable to the first QoS flow. The SDAP control PDU may indicate that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB. In some examples, the scheduling entity may identify the SDAP control PDU based on a control identifier within the SDAP control PDU, which facilitates the distinction between the SDAP control PDU and the SDAP data PDU. For example, the scheduling entity may ascertain the value of a data / control (D / C) bit of each of the SDAP control PDU and at least one SDAP data PDU, wherein the D / C bit facilitates the distinction between the SDAP control PDU and the at least one SDAP data PDU. In some examples, the scheduling entity may identify a QoS flow identifier (QFI) parameter in the SDAP control PDU that identifies the first QoS flow, and may further apply the control information of the SDAP control PDU only to the QoS flow (e.g., the first QoS flow) identified by the QFI parameter in the SDAP control PDU. For example, the above reference Fig. 9 The QoS mapping circuit 941 is shown and described along with the UL reception and processing circuit 943 and the transceiver 910 can receive the SDAP control PDU.

[0122] At block 1206, in response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB, the scheduling entity may forward at least one SDAP data PDU received via the second DRB to an upper layer. Fig. 9 The QoS mapping circuit 941 shown and described may forward at least one SDAP data PDU received via the second DRB to an upper layer.

[0123] Fig.13 1 is a flow chart illustrating another exemplary process 1300 for facilitating QoS flow remapping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and certain illustrated features may not be required for implementation of all embodiments. In some examples, process 1300 may be performed by Figure 8 13. In some examples, process 1300 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0124] At block 1302, a scheduled entity may detect a mapping reconfiguration of a first QoS flow from a first DRB to a second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from a scheduling entity in wireless communication with the scheduled entity. In other examples, the scheduled entity may detect the mapping reconfiguration via reflective mapping, wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received from the scheduling entity via the second DRB after being initially received via the first DRM. For example, the above reference Figure 8 The QoS mapping circuitry 841 shown and described, together with the DL reception and processing circuitry 842, can detect mapping reconfigurations.

[0125] At block 1304, the scheduled entity may set an end marker parameter in the SDAP header of the first SDAP data PDU received from the upper layer after the mapping configuration. The end marker parameter indicates that the first SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB. For example, the above reference Figure 8 The QoS mapping circuit 841 is shown and described as including an end marker parameter in the first SDAP data PDU.

[0126] At block 1306, the scheduled entity may send a first SDAP data PDU including an end marker parameter and at least one subsequent SDAP data PDU associated with the first QoS flow to a receiver (e.g., a scheduling entity). The first SDAP data PDU is transmitted to the receiver via a first DRB, and the at least one subsequent SDAP data PDU is transmitted to the receiver via a second DRB. For example, the above reference Figure 8 The UL generation and transmission circuit 843 shown and described in conjunction with the transceiver 810 may transmit a first SDAP Data PDU and at least one subsequent SDAP Data PDU to a receiver.

[0127] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0128] For example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0129] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as being preferred or advantageous over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered coupled to each other even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the functions described in the present disclosure to be performed without limitation to the type of electronic circuits, and are intended to include software implementations of information and instructions that, when executed by a processor, enable the functions described in the present disclosure to be performed.

[0130] Figure 1-13 One or more of the components, steps, features and / or functions shown in the drawings can be rearranged and / or combined into a single component, step, feature or function, or implemented in several components, steps or functions. Additional elements, components, steps and / or functions can also be added without departing from the novel features disclosed herein. Figure 1 , 2 , 4, 8 and / or 9 shown in the device, means, and / or components can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithm described herein can also be effectively implemented in software and / or embedded in hardware.

[0131] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented unless specifically set forth therein.

[0132] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given a full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one", unless specifically set forth, but means "one or more". Unless otherwise specifically set forth, the term "some" refers to one or more. A phrase referring to "at least one" in a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements throughout the various aspects described in the present disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, the content disclosed herein, whether or not it is explicitly set forth in the claims, is not intended to be dedicated to the public.

Claims

1. A method of wireless communication, comprising: detecting a mapping reconfiguration of a first quality of service QoS flow from a first data radio bearer DRB to a second DRB; generating, in response to the mapping reconfiguration, a Service Data Adaptation Protocol (SDAP) control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB; and transmitting the SDAP control PDU to a receiver via the first DRB, Generating SDAP control PDU includes: including a QoS flow identifier QFI parameter in the SDAP control PDU, wherein a value of the QFI parameter is set to a value corresponding to the first QoS flow to identify the first QoS flow applicable to control information included in the SDAP control PDU, Wherein detecting the mapping reconfiguration comprises: The mapping reconfiguration is detected via reflective mapping, wherein the mapping reconfiguration is detected based on whether packets associated with the first QoS flow are received via the second DRB after being initially received via the first DRB.

2. The method according to claim 1, wherein generating the SDAP control PDU further comprises: A control identifier is included within the SDAP control PDU, the control identifier facilitating differentiation between the SDAP control PDU and SDAP data PDUs.

3. The method according to claim 2, wherein the control identifier comprises: A data / control D / C bit is included in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates differentiation between the SDAP control PDU and the SDAP data PDU.

4. The method of claim 1, wherein transmitting the SDAP control PDU comprises: Maintaining the order in which the transmitter-side SDAP layer transmits the SDAP control PDU after transmitting the final SDAP data PDU associated with the first QoS flow via the first DRB, so that the receiver-side SDAP layer can receive the SDAP control PDU after receiving the final SDAP data PDU associated with the first QoS flow via the first DRB.

5. The method of claim 4, wherein maintaining the order is performed by a Packet Data Convergence Protocol (PDCP) entity associated with the first DRB.

6. The method according to claim 1, wherein generating the SDAP control PDU further comprises: identifying whether the buffer includes untransmitted SDAP data PDUs associated with the first QoS flow; When the buffer includes an undelivered SDAP data PDU associated with the first QoS flow, including an end marker parameter in an SDAP header of the undelivered SDAP data PDU, wherein the end marker parameter indicates that the undelivered SDAP data PDU is a final SDAP data PDU associated with the first QoS flow on the first DRB; and The untransmitted SDAP data PDU is transmitted to a receiver.

7. The method according to claim 6, wherein generating the SDAP control PDU further comprises: The SDAP control PDU is generated when the buffer does not include an untransmitted SDAP data PDU associated with the first QoS flow.

8. A scheduled entity in a wireless communication network, comprising: processor; a transceiver communicatively coupled to the processor; a memory communicatively coupled to the processor, wherein the processor is configured to: detecting a mapping reconfiguration of a first quality of service QoS flow from a first data radio bearer DRB to a second DRB; generating, in response to the mapping reconfiguration, a Service Data Adaptation Protocol (SDAP) control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB; and transmitting, via the transceiver, the SDAP control PDU to a scheduling entity via the first DRB, Wherein, in order to generate the SDAP control PDU, the processor is further configured to: including a QoS flow identifier QFI parameter in the SDAP control PDU, wherein a value of the QFI parameter is set to a value corresponding to the first QoS flow to identify the first QoS flow applicable to control information included in the SDAP control PDU, The processor is further configured to: The mapping reconfiguration is detected via reflective mapping, wherein the mapping reconfiguration is detected based on whether packets associated with the first QoS flow are received via the second DRB after being initially received via the first DRB.

9. The scheduled entity according to claim 8, wherein the processor is further configured to: A control identifier is included within the SDAP control PDU, the control identifier facilitating differentiation between the SDAP control PDU and SDAP data PDUs.

10. The scheduled entity according to claim 9, wherein the processor is further configured to: A data / control D / C bit is included in each of the SDAP control PDU and the SDAP data PDU, wherein the D / C bit facilitates differentiation between the SDAP control PDU and the SDAP data PDU.

11. The scheduled entity according to claim 8, wherein the processor is further configured to: Maintaining the order in which the transmitter-side SDAP layer within the scheduled entity transmits the SDAP control PDU after transmitting the final SDAP data PDU associated with the first QoS flow via the first DRB, so that the receiver-side SDAP layer within the scheduled entity can receive the SDAP control PDU after receiving the final SDAP data PDU associated with the first QoS flow via the first DRB.

12. The scheduled entity according to claim 8, wherein the processor is further configured to: identifying whether a buffer within the memory includes untransmitted SDAP data PDUs associated with the first QoS flow; When the buffer includes an undelivered SDAP data PDU associated with the first QoS flow, including an end marker parameter in an SDAP header of the undelivered SDAP data PDU, wherein the end marker parameter indicates that the undelivered SDAP data PDU is a final SDAP data PDU associated with the first QoS flow on the first DRB; and The untransmitted SDAP data PDU is transmitted to the scheduling entity.

13. The scheduled entity according to claim 12, wherein the processor is further configured to: The SDAP control PDU is generated when the buffer does not include an untransmitted SDAP data PDU associated with the first QoS flow.

14. A method of wireless communication, comprising: receiving a plurality of service data adaptation protocol (SDAP) data protocol data units (PDUs) associated with a first QoS flow from a transmitter via both a first data radio bearer (DRB) and a second DRB; receiving, from the transmitter via the first DRB, an SDAP control PDU applicable to the first QoS flow; and In response to receiving, via the first DRB, an SDAP control PDU applicable to the first QoS flow, forwarding to an upper layer the plurality of SDAP data PDUs received via the second DRB; wherein the SDAP control PDU is generated in response to a mapping reconfiguration and provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB, and wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received via the second DRB after being initially received via the first DRB, and Wherein, the method further comprises: identifying a QoS Flow Identifier (QFI) parameter in the SDAP Control PDU; and The control information of the SDAP control PDU is applied only to the first QoS flow identified by the QFI parameter in the SDAP control PDU.

15. The method according to claim 14, further comprising: The SDAP control PDU is identified based on a control identifier within the SDAP control PDU, the control identifier facilitating differentiation between the SDAP control PDU and at least one SDAP data PDU.

16. The method of claim 15, wherein identifying the SDAP control PDU further comprises: A value of a data / control D / C bit in each of the SDAP control PDU and the at least one SDAP data PDU is ascertained, and wherein the D / C bit facilitates differentiation between the SDAP control PDU and the at least one SDAP data PDU.

17. A scheduling entity in a wireless communication network, comprising: processor; a transceiver communicatively coupled to the processor; a memory communicatively coupled to the processor, wherein the processor is configured to: receiving, via the transceiver, a plurality of Service Data Adaptation Protocol (SDAP) data protocol data units (PDUs) associated with a first QoS flow from a scheduled entity via both a first data radio bearer (DRB) and a second DRB; receiving, via the transceiver, from a scheduled entity via the first DRB, an SDAP control PDU applicable to the first QoS flow; and In response to receiving, via the first DRB, an SDAP control PDU applicable to the first QoS flow, forwarding to an upper layer the plurality of SDAP data PDUs received via the second DRB; wherein the SDAP control PDU is generated in response to a mapping reconfiguration and provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB, and wherein the mapping reconfiguration is detected based on whether a packet associated with the first QoS flow is received via the second DRB after being initially received via the first DRB, and Wherein, the processor is further configured to: identifying a QoS Flow Identifier (QFI) parameter in the SDAP Control PDU; and The control information of the SDAP control PDU is applied only to the first QoS flow identified by the QFI parameter in the SDAP control PDU.

18. The scheduling entity according to claim 17, wherein the processor is further configured to: The SDAP control PDU is identified based on a control identifier within the SDAP control PDU, the control identifier facilitating differentiation between the SDAP control PDU and at least one SDAP data PDU.

19. The scheduling entity according to claim 18, wherein the processor is further configured to: A value of a data / control D / C bit in each of the SDAP control PDU and the at least one SDAP data PDU is determined, and wherein the D / C bit facilitates differentiation between the SDAP control PDU and the at least one SDAP data PDU.

20. A method of wireless communication, comprising: detecting a mapping reconfiguration of a first quality of service QoS flow from a first data radio bearer DRB to a second DRB; upon detecting the mapping reconfiguration and performing the mapping reconfiguration, determining whether there are any untransmitted packets belonging to the first DRB; In the absence of untransmitted packets belonging to the first DRB, generating an SDAP control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB; In the presence of at least one undelivered packet belonging to the first DRB, setting an end marker parameter in an SDAP header of a first SDAP data PDU containing an undelivered packet of the at least one undelivered packet, wherein the end marker parameter provides an indication that the first SDAP data PDU is a final SDAP data PDU associated with the first QoS flow on the first DRB; and transmitting to a receiver the first SDAP data PDU and at least one subsequent SDAP data PDU associated with a first QoS flow, the first SDAP data PDU being transmitted via the first DRB and the at least one subsequent SDAP data PDU being transmitted via the second DRB, Wherein detecting the mapping reconfiguration comprises: The mapping reconfiguration is detected via reflective mapping, wherein the mapping reconfiguration is detected based on whether packets associated with the first QoS flow are received via the second DRB after being initially received via the first DRB.

21. A scheduled entity in a wireless communication network, comprising: processor; a transceiver communicatively coupled to the processor; a memory communicatively coupled to the processor, wherein the processor is configured to: detecting a mapping reconfiguration of a first quality of service QoS flow from a first data radio bearer DRB to a second DRB; upon detecting the mapping reconfiguration and performing the mapping reconfiguration, determining whether there are any untransmitted packets belonging to the first DRB; In the absence of untransmitted packets belonging to the first DRB, generating an SDAP control protocol data unit (PDU), wherein the SDAP control PDU provides an indication that a final SDAP data PDU associated with the first QoS flow has been transmitted on the first DRB; In the presence of at least one undelivered packet belonging to the first DRB, setting an end marker parameter in an SDAP header of a first SDAP data protocol data unit (PDU) containing an undelivered packet of the at least one undelivered packet, wherein the end marker parameter provides an indication that the first SDAP data PDU is a final SDAP data PDU associated with the first QoS flow on the first DRB; and transmitting, via the transceiver, to a scheduling entity the first SDAP data PDU and at least one subsequent SDAP data PDU associated with the first QoS flow, the first SDAP data PDU being transmitted via the first DRB and the at least one subsequent SDAP data PDU being transmitted via the second DRB, The processor is further configured to: The mapping reconfiguration is detected via reflective mapping, wherein the mapping reconfiguration is detected based on whether packets associated with the first QoS flow are received via the second DRB after being initially received via the first DRB.

Images