JP2021521689A - Easy service quality flow remapping using service data adaptation protocol layer - Google Patents

Abstract

Aspects for quality of service (QoS) flow remapping are disclosed. In one example, detecting a mapping reconstruction of a first QoS flow from a first data radio bearer (DRB) to another DRB detects the final service data adaptation protocol (SDAP) data protocol associated with the first quality of service flow. A SDAP control PDU is generated indicating that the data unit (PDU) has been transmitted over the first DRB. The SDAP control PDU is then transmitted via the first DRB. In another example, detecting a mapping reconstruction of the first QoS flow from the first DRB to another DRB causes the first SDAP data PDU to be sent to the first QoS flow on the first DRB. Endmarker parameters are set in the SDAP header of the first SDAP data PDU received from the higher layer after the mapping reconstruction indicating that it is the relevant final SDAP data PDU. [Selection diagram] Fig. 5

Description

Cross-reference of related applications

[0001] This application is a non-provisional patent application filed with the United States Patent and Trademark Office on April 10, 2019, Nos. 16 / 380, 924, and a provisional patent application filed with the United States Patent and Trademark Office on April 13, 2018. It claims the priority and interests of Patent Application No. 62 / 657,664, the entire contents of which are as if they were fully described below and for all applicable purposes. Incorporated herein by reference.

[0002] The techniques described below generally relate to wireless communication systems and, more specifically, to the use of service data adaptation protocol (SDAP) layers to facilitate quality of service (QoS) flow remapping.

[0003] Within a wireless communication network, quality of service (QoS) refers to a set of technologies that allow a network to meet certain performance parameters (eg, reliability and / or target delay). Such QoS technologies achieve these performance parameters by applying different treatments to different traffic flows in the network. For example, each flow may be assigned a particular QoS, which helps the network determine, among other things, the order in which packets from each of the flows are processed and the amount of bandwidth allocated to each flow. .. Each QoS flow may be further mapped to a data radio bearer (DRB) established between the user equipment (UE) and the base station.

[0004] However, mapping and remapping a particular QoS flow to the corresponding data radio bearer has become more difficult with the introduction of 5th generation (5G), such as new radio (NR), networks. There is. As the demand for mobile broadband access continues to grow, research and development will specifically improve QoS flow mapping, not only to meet the growing demand for mobile broadband access, but also to enhance and improve the user experience of mobile communications. Continue to evolve communication technology, including technology for.

[0005] To provide a basic understanding of one or more aspects of the present disclosure, a simplified overview of such aspects is presented below. This overview is not an broad overview of all intended features of the present disclosure, but may also identify key or important elements of all aspects of the present disclosure, of any or all aspects of the present disclosure. Nor is it intended to delineate the range. Its sole purpose is to present in a simplified form some concepts of one or more aspects of the present disclosure as a prelude to a more detailed description presented later.

[0006] Various aspects of the disclosure relate to mechanisms for utilizing the Service Data Adaptation Protocol (SDAP) layer to facilitate quality of service (QoS) flow remapping. In one example, detecting a mapping reconstruction of a first QoS flow from a first data radio bearer (DRB) to another DRB detects the final service data adaptation protocol (SDAP) data protocol associated with the first quality of service flow. A SDAP control PDU is generated indicating that the data unit (PDU) has been transmitted over the first DRB. The SDAP control PDU is then transmitted to the receiver via the first DRB. In another example, detecting a mapping reconstruction of the first QoS flow from the first DRB to another DRB causes the first SDAP data PDU to be sent to the first QoS flow on the first DRB. Endmarker parameters are set in the SDAP header of the first SDAP data PDU received from the higher layer after the mapping reconstruction indicating that it is the relevant final SDAP data PDU. The first SDAP data PDU and at least one subsequent SDAP data PDU associated with the first QoS flow are then such that the first SDAP data PDU is transmitted via the first DRB and at least one subsequent SDAP data PDU. The SDAP data PDU can be transmitted to the receiver such that it is transmitted via the second DRB.

[0007] In one example, a method of wireless communication is disclosed. The method is 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 a service data adaptation protocol in response to the mapping reconfiguration ( SDAP) Including generating a control protocol data unit (PDU), where the SDAP control PDU is an indication that the final SDAP data PDU associated with the first QoS flow was transmitted on the first DRB. I will provide a. The method further comprises transmitting a SDAP controlled PDU to the receiver via the first DRB.

[0008] 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 memory communicably coupled to the processor. The processor detects a mapping reconfiguration of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB and responds to the mapping reconfiguration with the Service Data Adaptation Protocol (SDAP). It is configured to generate a control protocol data unit (PDU), where the SDAP control PDU provides an indication that the final SDAP data PDU associated with the first QoS flow was transmitted over the first DRB. do. The processor is further configured to transmit the SDAP control PDU via the transceiver and through the first DRB to the scheduling entity.

[0009] Another example provides a method of wireless communication. The method receives multiple Service Data Adaptive Protocol (SDAP) Data Protocol Data Units (PDUs) associated with the first QoS flow via both the first data radio bearer (DRB) and the second DRB. That is, the SDAP control PDU applicable to the first QoS flow is received via the first DRB, and the SDAP control PDU applicable to the first QoS flow is received via the first DRB. In response, the SDAP control PDU includes transferring a plurality of SDAP data PDUs received via the second DRB to a higher layer, where the SDAP control PDU is the final SDAP associated with the first QoS flow. Provides an indication that the data PDU was transmitted over the first DRB.

[0010] Another example provides a scheduling entity within a wireless communication network. Scheduling entities include a processor, a transceiver communicatively coupled to the processor, and memory communicatively coupled to the processor. The processor is a plurality of quality of service data adaptation protocol (SDAP) data protocols associated with a first quality of service flow from a scheduled entity via both a first data radio bearer (DRB) and a second DRB via a transceiver. It receives a data unit (PDU), receives an SDAP controlled PDU applicable to a first QoS flow from a scheduled entity via a first DRB via a transceiver, and a first via a first DRB. In response to receiving an SDAP control PDU applicable to QoS flow of, a plurality of SDAP data PDUs received via a second DRB are configured to be transferred to a higher layer, where the SDAP control The PDU provides an indication that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB.

[0011] Another example provides a method of wireless communication. The method is to detect a mapping reconstruction of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB, and a first received from a higher layer after the mapping reconstruction. 1. The end marker parameter includes setting an end marker parameter in the service data adaptation protocol (SDAP) header of the SDAP data protocol data unit (PDU), wherein the end marker parameter is such that the first SDAP data PDU is the first DRB. It provides an indication that it is the final SDAP data PDU associated with the first QoS flow above. The method further comprises transmitting a first SDAP data PDU and at least one subsequent SDAP data PDU associated with the first QoS flow to the receiver, wherein the first SDAP data PDU is the first. It is transmitted via one DRB and at least one subsequent SDAP data PDU is transmitted via a second DRB.

[0012] 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 memory communicably coupled to the processor. The processor detects a mapping reconfiguration of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB, and the first received from the higher layer after the mapping reconfiguration. The SDAP Data Protocol Data Unit (PDU) is configured to set endmarker parameters in the Quality of Service Adaptive Protocol (SDAP) header, where the endmarker parameters are such that the first SDAP data PDU is on the first DRB. It provides an indication that it is the final SDAP data PDU associated with the first QoS flow. The processor is further configured to transmit a 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, where the first. The SDAP data PDU is transmitted via the first DRB and at least one subsequent SDAP data PDU is transmitted via the second DRB.

[0013] These and other aspects of the invention will be better understood by reviewing the detailed description that follows. Other aspects, features, and embodiments of the invention will be apparent to those skilled in the art by examining the following description of certain exemplary embodiments of the invention in conjunction with the accompanying figures. Features of the invention may be described with respect to the following specific embodiments and figures, but all embodiments of the invention may include one or more of the advantageous features described herein. can. In other words, one or more embodiments may be described as having certain advantageous features, but one or more of such features are also a variety of inventions described herein. Can be used according to various embodiments. Similarly, exemplary embodiments may be described below as embodiments of devices, systems, or methods, but such exemplary embodiments may be implemented in various devices, systems, and methods. Should be understood.

[0014] FIG. 1 is a schematic diagram of a wireless communication system. [0015] FIG. 2 is a conceptual diagram of an example of a radio access network. [0016] FIG. 5 illustrates an example of a radio protocol architecture for a user plane and a control plane. [0017] FIG. 4 is a diagram illustrating an exemplary quality of service (QoS) architecture that facilitates aspects disclosed herein. [0018] FIG. 5 is a diagram illustrating an exemplary remapping of a QoS flow from a first data radio bearer (DRB) to a second DRB. [0019] FIG. 6 is a diagram illustrating exemplary service data adaptation protocol (SDAP) control protocol data units (PDUs) and SDAP data PDUs. [0020] FIG. 7 is a diagram illustrating another exemplary SDAP data PDU. [0021] FIG. 8 is a block diagram illustrating an example of hardware implementation for a scheduled entity using a processing system. [0022] FIG. 9 is a block diagram illustrating an example of hardware implementation for a scheduling entity with a processing system. [0023] FIG. 10 is a flow chart illustrating an exemplary process for facilitating QoS flow remapping. [0024] FIG. 11 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping. [0025] FIG. 12 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping. [0026] FIG. 13 is a flow chart illustrating another exemplary process for facilitating QoS flow remapping.

Detailed explanation

[0027] The detailed description presented below in connection with the accompanying drawings is intended as a description of the various configurations and represents the only configuration in which the concepts described herein can be implemented. Is not intended. The detailed description includes specific details to give a complete understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some cases, well-known structures and components are presented in the form of block diagrams to avoid obscuring such concepts.

[0028] Aspects and embodiments will be illustrated in this application by way of illustration to some examples, but those skilled in the art will appreciate that additional implementations and use cases can occur in many different arrangements and scenarios. Will understand. The invention described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses include integrated chip embodiments and other non-modular component-based devices such as end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / purchasing devices, medical devices. , AI-enabled device, etc.). Some examples may or may not explicitly target use cases or applications, but a wide range of applicability categories of the inventions described can occur. Implementations range from chip-level or modular components to non-modular, non-chip-level implementations, as well as aggregates, dispersions, or OEMs that incorporate one or more aspects of the invention described. It can extend to the spectrum to the device or system. In some practical settings, the device incorporating the aspects and features described will also necessarily include additional components and features for the implementation and implementation of the claimed and described embodiments. obtain. For example, the transmission and reception of wireless signals necessarily involves several components (eg, antennas, RF chains, power amplifiers, modulators, buffers, processors (s), inters) for analog and digital purposes. Includes hardware components including rivers, adders / summers, etc.). It is intended that the inventions described herein can be implemented in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, end-user devices, and the like.

[0029] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Here, with reference to FIG. 1, various aspects of the present disclosure are illustrated with reference to the wireless communication system 100 as an example, but not a limitation, of the present disclosure. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. The wireless communication system 100 may allow the UE 106 to perform data communication with an external data network 110 such as (but not limited to) the Internet.

[0030] The RAN 104 may implement one or more suitable wireless communication techniques to provide wireless access to the UE 106. As an example, RAN104 may operate according to 3G Partnership Project (3GPP®) New Radio (NR) specifications, often referred to as 5G. As another example, RAN104 may operate under a hybrid of 5G NR and the Advanced Universal Terrestrial Radio Access Network (eUTRAN) standard, often 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 this disclosure.

[0031] As illustrated, the RAN 104 includes a plurality of base stations 108. In general, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE. In different technologies, standards, or contexts, base stations, depending on the person skilled in the art, are transceiver base stations (BTS), radio base stations, radio transceivers, transceiver functions, basic service sets (BSS), extended service sets (ESS), access points. It may be variously referred to as (AP), node B (NB), enode B (eNB), gnode B (gNB), or some other suitable term.

[0032] A radio access network 104 that supports wireless communication for multiple mobile devices is further illustrated. Mobile devices, which may be referred to as user devices (UEs) in the 3GPP standard, can be referred to by those skilled in the art as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices. , Wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or any other suitable term. obtain. The UE can be a device that provides users with access to network services.

[0033] As used herein, a "mobile" device does not necessarily have the ability to move and may be stationary. The term mobile device or mobile device broadly refers to a diverse array of devices and technologies. The UE may include several hardware structural components that are sized, shaped, and arranged to aid in communication, such components as antennas, antenna arrays, RF chains that are electrically coupled to each other. , Amplifiers, one or more processors, etc. For example, some non-limiting examples of mobile devices include mobile, cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smarts. Includes books, tablets, personal computers (PDAs), and a wide range of embedded systems for, for example, the "Internet of Things" (IoT). Mobile devices additionally include automobiles or other transport vehicles, remote sensors or actuators, robots or robotics devices, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multicopters, quadcopters, remote control devices. Can be consumer and / or wearable devices such as eyewear, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (eg MP3 players), cameras, game consoles, etc. Mobile devices can additionally be digital home or smart home devices such as home audio, video and / or multimedia devices, appliances, vending machines, intelligent lighting, home security systems, smart meters, etc. .. Mobile devices additionally include municipal infrastructure devices (eg, smart grids) that control smart energy devices, security devices, solar panels or solar arrays, power, lighting, water, etc., industrial automation and enterprise devices, logistics controllers. , Agricultural equipment, military defense equipment, vehicles, aircraft, ships, and weapons, etc. In addition, mobile devices may provide connected medicine or telemedicine support, ie, remote health care. A telemedicine device may include a telemedicine surveillance device and a telemedicine management device, the communication of which may include, for example, preferred access for transporting critical service data and / or critical services. In terms of the relevant QoS for transporting data, preferential treatment or preferred access may be given over other types of information.

Wireless communication between the RAN 104 and the UE 106 can be described using an air interface. Transmission from a base station (eg, base station 108) to one or more UEs (eg, UE 106) via an air interface may be referred to as downlink (DL) transmission. According to a particular aspect of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating from a scheduling entity (discussed further below, eg, base station 108). Another way to describe this scheme could be to use the term broadcast channel multiplexing. Transmission from a UE (eg, UE 106) to a base station (eg, base station 108) can be referred to as uplink (UL) transmission. According to a further aspect of the present disclosure, the term uplink can refer to point-to-point transmission originating from a scheduled entity (described further, eg, UE 106).

[0035] In some examples, access to an air interface may be scheduled, and a scheduling entity (eg, base station 108) communicates between some or all devices and devices within its service area or cell. Allocate resources for. Within this disclosure, scheduling entities may be responsible for scheduling, allocating, reconfiguring, and freeing resources for one or more scheduled entities, as described further below. That is, in the case of scheduled communication, the UE 106, which can be the scheduled entity, can utilize the resources allocated by the scheduling entity 108.

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

As illustrated in FIG. 1, scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. In general, scheduling entity 108 schedules traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to scheduling entity 108. A node or device responsible for that. On the other hand, the scheduled entity 106 includes, but is not limited to, scheduling information (eg, authorization), synchronization or timing information, or other control information from another entity in the wireless communication network, such as scheduling entity 108. A node or device that receives downlink control information 114.

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

[0039] In general, base station 108 may include a backhaul interface for communication with the backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base station 108 and the core network 102. Moreover, in some examples, the backhaul network may provide interconnection between the respective base stations 108. Various types of backhaul interfaces can be used, such as direct physical connections, virtual networks, or similar using any suitable forwarding network.

[0040] The core network 102 may be part of the wireless communication system 100 and will be independent of the wireless access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (eg, 5GC). In another example, the core network 102 may be configured according to a 4G evolutionary packet core (EPC), or any other suitable standard or configuration.

[0041] With reference to FIG. 2, a schematic diagram of the RAN 200 is provided as an example, not a limitation. In some examples, the RAN 200 can be the same as the RAN 104 described above and illustrated in FIG. The geographic area covered by the RAN 200 can be divided into cellular areas (cells) that can be uniquely identified by the user equipment (UE) based on the identification information broadcast from one access point or base station. FIG. 2 illustrates macrocells 202, 204, and 206 and small cells 208, each of which may include one or more sectors (not shown). A sector is a subarea of a cell. All sectors in a cell are serviced by the same base station. Radio links within a sector can be identified by a single logical identity belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by a group of antennas in which each antenna is responsible for communicating with the UE in a portion of the cell.

[0042] In FIG. 2, two base stations 210 and 212 are shown in cells 202 and 204, and a third base station 214 is shown to control the remote radio head (RRH) 216 in cell 206. There is. 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 illustrated example, cells 202, 204, and 126 may be referred to as macrocells because base stations 210, 212, and 214 support cells of large size. Further, base station 218 is shown in small cells 208 (eg, microcells, picocells, femtocells, home base stations, homenodes B, home enodes B, etc.) that can overlap with one or more macrocells. ing. In this example, cell 208 may be referred to as a small cell because base station 218 supports cells with a relatively small size. Cell sizing can be done according to system design and component constraints.

It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes can 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 to any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be the same as the base station / scheduling entity 108 described above and illustrated in FIG.

[0044] Within the RAN 200, a cell may include a UE that may be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide access points to the core network 102 (see FIG. 1) to all UEs in their respective cells. For example, UEs 222 and 224 may be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, and UEs 230 and 232 may be in communication with base station 214 via RRH216. The UE 234 may be in communication with the base station 218. In some examples, UE 222, 224, 226, 228, 230, 232, 234, 238, 240, and / or 242 are the same as the UE / scheduled entity 106 described above and illustrated in FIG. could be.

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

[0046] In a further aspect of the RAN 200, the sidelink signal can be used between UEs without necessarily relying on scheduling or control information from the base station. For example, two or more UEs (eg, UEs 226 and 228) use peer-to-peer (P2P) or sidelink signals 227 without relaying communication through a base station (eg, base station 212). Can communicate with each other. In a further example, the UE 238 is exemplified in communication with the UEs 240 and 242. Here, the UE 238 can function as a scheduling entity or a primary sidelink device, and the UEs 240 and 242 can act as a scheduled entity or a non-primary (eg, secondary) sidelink device. In yet another example, the UE is a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or in a mesh network. Can work. In the mesh network example, UEs 240 and 242 can optionally communicate directly with each other in addition to communicating with the scheduling entity 238. Therefore, in a wireless communication system that has scheduled access to time-frequency resources and has a cellular, P2P, or mesh configuration, the scheduling entity and one or more scheduled entities utilize the scheduled resource. Can communicate with. In some examples, the sidelink signal 227 includes sidelink traffic and sidelink control.

[0047] In various implementations, the air interface in the radio access network 200 may utilize a licensed spectrum, an unlicensed spectrum, or a shared spectrum. The license spectrum generally provides exclusive use of a portion of the spectrum by mobile network operators by purchasing licenses from government regulators. Unlicensed spectra provide shared use of parts of the spectrum without the need for government-licensed licenses. In general, access to the unlicensed spectrum requires compliance with some technical rules, but in most cases any operator or device can gain access. The shared spectrum can be located between the licensed spectrum and the unlicensed spectrum, where technical rules or restrictions may be required to access this spectrum, but this spectrum is still multiple. It can be shared by the operator and / or multiple RATs. For example, a license holder for a portion of a license spectrum may provide License Sharing Access (LSA) and, for example, share the spectrum with other parties with appropriate conditions set by the licensee to gain access. obtain.

[0048] Channel coding can be used to transmit over the radio access network 200 to obtain a low block error rate (BLER) while still achieving very high data rates. That is, wireless communication can generally utilize appropriate error correction block chords. In a typical block code, an informational message or sequence is divided into code blocks (CBs), and the encoder of the transmitting device (eg, a codec) then mathematically adds redundancy to this informational message. Exploitation of this redundancy in a coded informational message can increase the reliability of the message, which allows correction of any bit error that may occur due to noise.

[0049] In the early 5G NR specification, user data traffic is used for two different bases, one base graph is used for large code blocks and / or high code rates, and the other base graph is used otherwise. It is coded using a quasi-circular low density parity check (LDPC) with a graph. Control information and physical broadcast channels (PBCH) are coded using Polar coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0050] However, one of ordinary skill in the art will appreciate that aspects of the present disclosure can be implemented utilizing any suitable channel code. Various implementations of the scheduling entity 108 and the scheduled entity entity 106 have the appropriate hardware and capabilities (eg, encoder, decoder) to utilize one or more of these channel codecs for wireless communication. , And / or CODEC).

The air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to allow simultaneous communication of various devices. For example, the 5G NR specification utilizes multiple access for UL transmission from UE 222 and 224 to base station 210 and orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) from base station 210 to 1. Provides multiplexing for DL transmission to one or more UEs 222 and 224. In addition, for UL transmission, the 5G NR specification provides support for Discrete Fourier Transform Spread OFDM (DFT-s-OFDMA) (also referred to as Single Carrier FDMA (SC-FDMA)) with CP. However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above methods: time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code. It may be provided using multiple access (SCMA), resource diffusion multiple access (RSMA), or other suitable multiple access method. Further, multiplexing DL transmission from base station 210 to UE 222 and 224 includes time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), and orthogonal frequency division multiplexing ( It may be provided using OFDM), sparse code multiplexing (SCM), or other suitable multiplexing scheme.

[0052] The air interface in the radio access network 200 may further utilize one or more duplication algorithms. Duplex refers to a point-to-point communication link that allows both endpoints to communicate with each other in both directions. Full duplex means that both endpoints can communicate with each other at the same time. Half duplex means that only one endpoint can send information to the other at a time. In wireless links, full-duplex channels generally rely on physical separation of transmitters and receivers and appropriate deinterference techniques. Full duplex emulation is often implemented for wireless links by utilizing Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some point, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction is very rapidly, eg, for example. It can change several times per slot.

Radio protocol architectures for RANs, such as the RAN 200 shown in FIG. 2, may take various forms depending on the particular application. An example of a radio protocol architecture for the user plane and control plane is illustrated in FIG.

As illustrated in FIG. 3, the radio protocol architecture for UEs and base stations 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 herein as physical layer 306. L2 308 is above the physical layer 306 and is responsible for the link between the UE and the base station via the physical layer 306.

In the user plane, the L2 layer 308 terminates at the base station on the network side, with medium access control (MAC) layer 310, radio link control (RLC) layer 312, and packet data convergence protocol (PDCP) layer 314. And the Service Data Adaptation Protocol (SDAP) Layer 316. Although not shown, the UE has at least one network layer (eg, IP layer and User Data Protocol (UDP) layer) that terminates in the user plane function (UPF) on the network side and one or more application layers. May have several higher layers above L2 layer 308, including.

[0056] SDAP layer 316 provides a mapping between 5G core (5GC) quality of service (QoS) flows and data radio bearers to perform QoS flow ID marking on both downlink and uplink packets. PDCP layer 314 provides packet sequence numbering, delivery of packets in the correct order, retransmission of the Protocol Protocol Data Unit (PDU), and transfer of higher layer data packets to lower layers. A PDU can include, for example, Internet Protocol (IP) packets, Ethernet® frames, and other unstructured data (ie, Machine Type Communication (MTC), hereinafter collectively referred to as "packets"). .. PDCP layer 314 also provides header compression of higher layer data packets to reduce radio transmission overhead, security by encrypting the data packets, and protection of data packet integrity. The RLC layer 312 provides segmentation and reassembly of higher layer data packets, error correction by automatic repeat request (ARQ), and sequence numbering that is independent of PDCP sequence numbering. 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 HARQ operation. The physical layer 306 is responsible for transmitting and receiving data on the physical channel (eg, within a slot).

[0057] In the control plane, the radio protocol architecture for UEs and base stations is substantially the same for L1 306 and L2 308, except that the control plane does not have a SDAP layer and no control plane header compression capabilities. Is. The control plane also includes a radio resource control (RRC) layer 318 at L3 and a higher non-access layer (NAS) layer 320. RRC layer 318 establishes and configures signaling radio bearers (SRBs) and data radio bearers (DRBs) between base stations and UEs, paging initiated by 5GC or NG-RAN, and access layers (AS) and non-accessories. Responsible for broadcasting system information related to the access layer (NAS). The RRC layer 318 is further responsible for QoS management, mobility management (eg handover, cell selection, inter-RAT mobility), UE measurement and reporting, and security functions. The NAS layer 320 terminates at AMF in the core network and performs various functions such as authentication, registration management, and connection management.

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

[0059] For each UE (eg, UE406), the 5GC404 establishes one or more PDU sessions 412. Each PDU session 412 may include one or more data flows 418a-418c (eg, IP, Ethernet, and / or unstructured data flows), each associated with a set of one or more applications. The 5GC404 may further select the QoS that will be associated with each of the data flows 418a-418c within the PDU session 412. At the NAS level, QoS flow is the finest grained QoS differentiation in a PDU session, both the QoS profile provided to NB408 by 5GC404 and the (s) QoS rules provided to UE406 by 5GC404. Characterized by. The QoS profile is used by the NB 408 to determine the treatment on the wireless interface, and the QoS rules dictate the mapping between the QoS flows 418a-418c to the UE 406 and the uplink user plane traffic. ..

[0060] A QoS profile may include one or more QoS parameters. For example, a QoS profile may include an allocation and retention priority (ARP) that may indicate the priority level of allocation and retention of the data radio bearer, and a 5G QoS identifier (5QI) that is associated with a particular 5G QoS characteristic. Examples of 5G QoS characteristics include resource type (eg, guaranteed bit rate (GBR), delayed critical GBR, or non-GBR), priority level, packet delay budget, packet error rate, averaging window, and minimum data burst volume. Can be included. For GBR QoS flows, the QoS profile is a guaranteed flow bit rate (GFBR) for both uplink and downlink, a maximum flow bit rate (MFBR) for both uplink and downlink, and both uplink and downlink. You can further specify the maximum packet loss rate for. For non-GBR quality of service flows, the quality of service profile may include an RQA (reflective QoS attribute). RQA, when included, indicates that some (but not all) traffic carried on this quality of service is under the influence of QoS (reflective QoS) at the NAS layer. Standardized or preconfigured 5G QoS characteristics are derived from 5QI values and are not explicitly signaled. The signaled QoS characteristics are included as part of the QoS profile.

[0061] In addition, the aggregate maximum bit rate is associated with each PDU session 412 (Session-AMBR) and with each UE 406 (UE-AMBR). Session-AMBR limits the total 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 total bit rate that can be expected to be provided across all non-GBR QoS flows in the UE.

[0062] NB408 establishes one or more data radio bearers (DRBs) 414a and 414b per PDU session 412. The NB408 also maps packets belonging to different PDU sessions 412 to different DRBs. Here, the NB 408 establishes at least one default DRB (eg, DRB414a) for each PDU session 412. At the access layer (AS) level, the DRB defines packet processing on the wireless interface (Uu). The DRB supplies packets in the same packet transfer process. Separate DRBs can be established for QoS flows that require different packet forwarding processing, or several QoS flows that belong to the same PDU session can be multiplexed in the same DRB. Within each PDU session 412, the NB 408 determines how to map multiple QoS flows to the DRB. For example, the NB408 may map GBR and non-GBR flows, or more than one GBR flow, to the same DRB. The timing of the establishment of the non-default DRB (eg, DRB414b) between the NB408 and the UE 406 for the (one or more) QoS flows configured during the establishment of the PDU session is It can be different from the time when the PDU session is established.

[0063] NG-RAN402 and 5GC404 ensure quality of service (eg reliability and target delay) by mapping packets to appropriate QoS flows 418a-418c and DRB414a and 414b. The NAS layer performs packet filtering on both UE406 and 5GC404 to associate uplink (UL) and downlink (DL) packets with QoS flows 418a-418c. The AS layer, which is the functional layer between UE 406 and NB 408, implements mapping rules in UE 406 and NB 408 to associate UL and DL QoS flows 418a-418c with DRB 414a and 414b. Therefore, there is a two-step mapping from IP flow to QoS flow (in NAS) and from QoS flow to DRB (in AS). In the example shown in FIG. 4, QoS flows 418a and 418b are mapped to DRB414a and QoS flows 418c are mapped to DRB414b.

[0064] Each QoS flow 418a-418c is carried in the encapsulation header through the next generation tunnel (NG-U tunnel) 416 provided on the interface (NG-U) between NB408 and UPF410. It is identified within the PDU session 412 by ID (QFI). The mapping of QoS flows to DRBs by NB408 is based on QFI and associated QoS profiles (ie, QoS parameters and QoS characteristics). For example, on the uplink, the NB408 may use reflective mapping or explicit configuration to control the mapping of QoS flows 418a-418c to DRB414a and 414b. In reflective mapping, for each DRB 414a and 414b, UE 406 monitors the QFI (s) of the downlink packet and applies the same mapping on the uplink. That is, for a DRB (eg, DRB414a), the UE 406 corresponds to the PDU session 412 and (s) QFIs (s) observed in the downlink packet for that DRB414a (s) QoS flow 418a. And the uplink packets belonging to 418b are mapped. To enable this reflective mapping, the NB408 marks downlink packets on the radio interface (Uu) with QFI. In an explicit configuration, the NB408 may construct an uplink "QuoS flow vs. DRB mapping" by RRC. The UE 406 may apply the latest update of the mapping rule, whether the update is performed via reflection mapping or through explicit configuration.

[0065] On the downlink, QFI is signaled by NB408 on the radio interface (Uu) for QoS, and both NB408 and NAS (as indicated by RQA) are carried in the DRB (one). Or if you do not intend to use reflective mapping for (or more) QoS flows, the QFI for that DRB will not be signaled on the Uu. However, the NB 408 can still configure the UE 406 to signal QFI on the Uu. As shown above, a default DRB (eg, DRB414a) is configured for each PDU session 412. If the incoming UL packet does not match either the RRC-configured "QoS Flow ID vs. DRB Mapping" or the reflection-configured "QoS Flow ID vs. DRB Mapping", the UE 406 sends the UL packet to the default DRB414a for PDU session 412. Can be mapped to.

[0066] FIG. 5 is a diagram illustrating an exemplary remapping of the QoS flow from the first data radio bearer (DRB) to the second DRB. FIG. 5 provides an example from a UE perspective showing a 5G uplink mapping relationship 500 for a single PDU session as part of QoS enforcement. Although FIG. 5 illustrates a single PDU session, it should be recognized that a UE can have multiple PDU sessions. Each PDU session in the UE can have multiple DRBs, each DRB can have multiple QoS flows (eg, where each QoS flow is identified by a QFI), and each QFI can have multiple. SDF can be included.

FIG. 5 further illustrates the processing of uplink packets from the UE protocol stack and service data flows (SDFs) 514a-514e associated with the PDU session. For ease of understanding, a service data flow (SDF) can be conceptually considered as data / packets / frames from one set of applications on a wireless communication device (eg, UE).

In the example shown in FIG. 5, application layers 502, NAS layer 504, SDAP layers 506, PDCP layers 508a and 508b, RLC layers 510a and 510b, and MAC and PHY layers 512 are exemplified in the protocol stack. The NAS layer 504 and SDAP layer 506 may correspond to, for example, the NAS layer 320 and the SDAP layer 316 shown in FIG. In addition, PDCP layers 508a and 508b may correspond to PDCP layer 314 and RLC layers 510a and 510b may correspond to RLC layer 312 shown in FIG. Further, the MAC and PHY layers 508 may correspond to, for example, the MAC layer 310 and the physical layer 306 shown in FIG. PDCP layers 508a and 508b correspond to their respective PDCP entities implemented within their respective DRB520a and 520b, and RLC layers 510a and 510b correspond to their respective RLC entities implemented within their respective DRB520a and 520b, respectively. do.

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

[0070] In the example shown in FIG. 5, SDF # 1 514a produces 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 SDAP layer 506, SDAP layer 506 will perform Pkt1 518a and Pkt2 according to the UE network configuration described above. Map 518b to DRB1 520a. Before the SDAP receives UL packets 3 and 4 (Pkt3 518c and Pkt4 518d), the network (eg, NB via explicit or reflective mapping) will map the first QoS flow 516a to the DRB1 520a. Reconfigure the UE. Then, when UL packets 3 and 4 (Pkt3 518c and Pkt4 518d) of the first QoS flow 516a arrive at SDAP layer 506, SDAP layer 506 performs Pkt3 518c and Pkt4 518d DRB2 520b according to the new network configuration of the UE. Map to.

[0071] In some examples, each DRB520a and 520b is a DRB because each DRB's PDCP entity (where the entity is an instance of the "protocol layer") tags each packet with a sequence number. It may be possible to ensure that the packets within are received by the receiver (eg, NB) in their original order. Each DRB's PDCP entity maintains its own PDCP sequence number (SN), independent of the other DRB's PDCP entities. 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 delivery in the correct order on the receiver side. For example, Pkt3 518c and Pkt4 518d may be received by the receiver prior to Pkt1 518a and Pkt2 518b.

[0072] Thus, when the receiver receives the four packets 518a-518d, the receiver notices (eg, by QFI) that the packets 518a-518d belong to the same QoS flow. However, the receiver is a UE application as a result of different PDCP sequence numbers resulting from the remapping of the DRB1 520a to the DRB2 520b between the second packet (Pkt2 518b) and the third packet (Pkt3 518c). It may not be possible to restore the original order of packets 518a-518d at layer 502. In particular, the receiver may not be able to determine when the packet from the DRB1 520a ends and when the packet from the DRB2 520b starts. For example, there may be an intermediate time period during which the receiver may receive packets from both DRB1 520a and DRB2 520b due to lower layer (eg, RLC layer, MAC layer) retransmissions.

[0073] In addition, SDAP layer 506 does not include the sequence number in the SDAP PDU provided to PDCP entities 508a and 508b, resulting in the receiver remapping the QoS flow from one DRB to another. Therefore, in a situation where the receiver is unable to perform PDCP PDU sorting, it is not possible to perform SDAP PDU sorting.

[0074] Thus, various aspects of the disclosure provide a mechanism for ensuring that the receiver can restore the original order of packets generated at the transmitter. In some examples, the SDAP layer 506 is associated with the final related QoS flow (eg, QoS flow 516a) with the detection of a remapping configuration change (eg, remapping of the QoS flow 516a from DRB2 520a to DRB1 520b). A stand-alone SDAP PDU 522 may be generated that includes control information including indication that the SDAP data PDU was transmitted over an old DRB (eg, DRB1 520a). Such detection may be based on, for example, radio resource control (RRC) messages or reflective mapping.

[0075] Thus, the SDAP PDU 522 can be considered as an SDAP controlled PDU that functions as an "end marker" SDAP PDU at SDAP layer 506. The SDAP layer 506 may generate the SDAP control PDU 522 after transmitting the final / final SDAP data PDU (eg, Pkt2 518b) for the QoS flow 516a to the DRB1 520a. The SDAP control PDU522 may also be provided to an older DRB (eg, DRB1 520a) and processed by the PDCP entity 508a to adhere to the order of the endmarker SDAP control PDU522. Using the above example, the SDAP control PDU522 may be assigned the next PDCP sequence number (eg, SN = 903) by the PDCP entity 508a. Therefore, the order of the packets can be adhered to by the PDCP entity 508a, so that when the receiver receives the SDAP control PDU522, the receiver will receive all of the packets for the first QoS flow 516a on the DRB1 520a. It can recognize that it has been received and processed. Thus, the endmarker SDAP PDU522 causes the SDAP entity to stop mapping the SDAP session data unit (SDU) of the QoS flow 516a indicated by the QFI to the DRB (eg, DRB1 520a) to which the endmarker SDAP PDU522 is transmitted. It can be utilized by the SDAP entity in the receiver (eg UE) to indicate that it should be.

[0076] As described above, PDCP entity 508a cannot distinguish SDAP control PDUs from SDAP data PDUs, so both types of SDAP PDUs can be treated in the same way by PDCP entity 508a, which It should be noted that the PDCP entity 508a can process the SDAP control PDU and adhere to the order of all SDAP PDUs. Since all packets in one DRB can be received in order at the PDCP layer on the receiver side, when the receiver receives the SDAP controlled PDU, the receiver will see everything on the old DRB (DRB1 520a). Can be determined to have been received. Therefore, upon receiving the SDAP control PDU, the receiver may forward the remapped packets received on the new DRB (eg DRB2 520b) (eg Pkt3 518c and Pkt4 518d) to the higher layers.

[0077] In some examples, the SDAP control PDU may include a QFI of remapped QoS flows. For example, the SDAP layer 506 may set the "QFI" of the SDAP control PDU to the QFI of the remapped QoS flow (eg, QFI = 1). In addition, the SDAP control PDU may include a control identifier to distinguish the SDAP control PDU (including the control message generated by the SDAP layer) from the SDAP data PDU (including, for example, application data). In one example, the value of the control identifier can be set separately for the SDAP control PDU and the SDAP data PDU (ie, the SDAP layer of the SDP control PDU to indicate that the PDU is a "SDAP control PDU". Set the identifier). For example, the control identifier may include a 1-bit "data / control (D / C)" identifier (eg, D / C parameter = 0 indicates SDAP control PDU, D / C parameter = 1 is SDAP data. Indicates PDU).

[0078] In another example, as shown in FIG. 5, when the remapping configuration is performed by the transmitter (eg, UE), the transmitter waits, for example, in the transmit buffer associated with SDAP layer 506. It may first determine if there are untransmitted packets (eg, packets that have not yet been processed by SDAP layer 506) that belong to the old DRB (eg, DRB1 520a). If there is at least one untransmitted packet belonging to the old DRB (eg, DRB1 520a), the SDAP layer 506 may set the end marker parameter on the last untransmitted packet belonging to the DRB1 520a. Otherwise, if no untransmitted packets remain, the SDAP layer 506 may generate an endmarker SDAP control PDU522.

[0079] In this example, SDAP layer 506 may set endmarker parameters in the SDAP header of the last data packet of the QFI (eg, first QoS flow 516a) mapped to the old DRB1 520a. For example, with the detection of a remapping configuration change (eg, remapping of QoS flow 516a from DRB1 520a to DRB2 520b), SDF # 2 generated Pkt1 518a and Pkt2 518b, but still Pkt3 518c or Pkt4 518d. Assuming that it has not been generated, the SDAP layer 506 may set an endmarker parameter in the SDAP header of the SDAP data PDU that contains Pkt2 518b. In some examples, the end-marker parameters may include 1-bit end-marker parameters (eg, end-marker parameter = 0 indicates that the SDAP PDU is not the last / last SDAP data PDU for the DRB, the end. Marker parameter = 1 indicates that the SDAP PDU is the last / final SDAP data PDU for the DRB).

[0080] Based on the end marker parameters, the receiver-side SDAP entity re-from the old DRB1 520a regardless of whether the old DRB1 packet is actually received before or after the new DRB packet. All mapped QFI packets (eg, Pkt1 518a and Pkt2 518b) were received prior to any remapped QFI packets (eg, Pkt3 518c and Pkt4 518d) from the new DRB2 520b. Can be considered. However, if the receiver-side PDCP entity does not receive a packet (ie, Pkt2 518b) with an end-marker parameter in the SDAP header for the remapped QFI from the old DRB1 and does not deliver it to the receiver-side SDAP layer. , The receiver-side SDAP layer cannot deliver the remapped QFI received packets from the new DRB2 520b to the higher layers (in Example 1, these packets are packets # 3 and # 4).

[0081] In this example, the complexity of the implementation is higher than in the example where the SDAP control PDU is generated with the detection of remapping. However, by allowing the SDAP layer to generate a SDAP control PDU when there are no untransmitted packets waiting in the buffer, the transmitter waits for the next SDAP data PDU that should include endmarker parameters. Instead, the remapping can be performed immediately. In addition, if the old DRB (eg DRB1 520a) is not needed for other flows, the old DRB should include the end marker parameters by generating the SDAP control PDU when there are no untransmitted packets. The PDU can be released sooner than if the SDAP layer had to wait.

[0082] In another example, when the network configures a remapping of the QoS flow from DRB1 520a to DRB1 520b (eg, QFI = 1 514a), the unprocessed packets available on the old DRB2 520a are this. If not (for example, all existing packets are not sent over the radio and may still be buffered by a lower layer such as PDCP layer 508a, but they may still be buffered by the SDAP layer 506. When a new incoming packet of remapped QFI (eg, QFI = 1 516a) arrives at SDAP layer 506 (if already processed), SDAP layer 506 receives the first new incoming from the remapped QFI 516a. Endmarker parameters can be set on the packet. The SDAP layer 506 can then transmit a packet containing the end marker parameters on the old DRB (eg, DRB1 520a). The SDAP layer 506 can then send subsequent incoming packets of the remapped QFI on the new DRB (eg DRB2 520b) without setting an end marker.

[0083] Examples of the SDAP control PDU 600 and the SDA P data PDU 610 are illustrated in FIG. As illustrated, the SDAP control PDU 600 is configured to have a total length of 8 bits in the SDAP layer. The SDAP control PDU 600 includes data / control (D / C) bits 602 indicating whether the SDAP control PDU 600 is a SDAP data PDU or a SDAP control PDU. For example, the D / C bit 602 can be set to 0 to indicate that the SDAP control PDU 600 is a SDAP control PDU. The SDAP control PDU 600 may further include a spare field 604 and may further include a QFI parameter 606 that identifies a particular QoS flow applicable to control information (eg, D / C bit 602) within the SDAP control PDU 600. For example, the QFI parameter can be set to a value corresponding to a QoS flow remapped from one DRB to another.

[0084] The SDAP data PDU610 includes the SDAP header 612 in a 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 spare field 618, and a QFI parameter 620. The D / C bit 616 indicates whether the SDAP control PDU 600 is a SDAP data PDU or a SDAP control PDU. For example, the D / C bit can be set to 1 to indicate that the SDAP data PDU 610 is an SDAP data PDU. The QFI parameter 620 identifies a particular QoS flow associated with the SDAP data PDU610. The SDAP data PDU610 may further include a body 614 containing data 622 (eg, application data) which can start from octet 2 and can have variable length, as illustrated.

[0085] FIG. 7 illustrates another example of the SDAP data PDU700. As illustrated, the SDAP data PDU 700 includes the SDAP header 702 in a first octet (octet 1) having a total length of 8 bits. The SDAP header 702 may include, for example, an end marker parameter 706, a spare 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, where end marker parameter = 0 indicates that the SDAP data PDU is not the last / last SDAP data PDU for the DRB and the end marker. Parameter = 1 indicates that the SDAP data PDU is the last / last SDAP data PDU for the DRB. The QFI parameter 710 identifies a particular QoS flow associated with the SDAP data PDU700. The SDAP data PDU 700 may further include a body 704 containing data 712 (eg, application data) which can start from octet 2 and can have variable length, as illustrated.

[0086] FIG. 8 is a block diagram illustrating an example of hardware implementation for the scheduled entity 800 using the processing system 814. For example, the scheduled entity 800 can be the user equipment (UE) exemplified in any one or more of FIGS. 1, 2, and / or 4 disclosed herein.

[0087] The scheduled entity 800 may be implemented in a processing system 814 that includes one or more processors 804. Examples of processor 804 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and the entire disclosure. Includes other suitable hardware configured to perform the various functionality described through. In various examples, the scheduled entity 800 may be configured to perform any one or more of the functions described herein. That is, processor 804 can be used to implement any one or more of these processes and the processes described below when utilized in the scheduled entity 800. The processor 804 may be implemented via a baseband or modem chip in some cases, in other implementations the processor 804 itself comprises several devices that are separate and different from the baseband or modem chip. (For example, in such a scenario, it may work together to achieve the embodiments described herein). Also, as mentioned above, various hardware arrays outside the baseband modem processor, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc. Components can be used in the implementation.

[0088] In this example, the processing system 814 can be implemented in a bus architecture commonly represented by bus 802. Bus 802 may include any number of interconnect buses and bridges, depending on the particular application of processing system 814 and the overall design constraints. Bus 802 communicates with each other various circuits including one or more processors (generally represented by processor 804), memory 805, and computer readable medium (generally represented by computer readable medium 806). Combine as possible. Bus 802 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, but these are well known in the art and are not described further. There will be. The bus interface 808 provides an interface between the bus 802 and the transceiver 810. Transceiver 810 provides a communication interface or means for communicating with various other devices on the transmission medium. Depending on the nature of the device, a user interface 812 (eg, keypad, display, speaker, microphone, joystick) may also be provided as an option.

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

[0090] One or more processors 804 in the processing system may execute software. Software, whether referred to by software, firmware, middleware, microcode, hardware description language, or by any other name, is an instruction, a set of instructions, a code, a code segment, a program code, a program, a subprogram. , Software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software may reside on a computer-readable medium 806.

[0091] The computer-readable medium 806 can be a non-temporary computer-readable medium. Non-temporary computer-readable media include, for example, magnetic storage devices (eg, hard disks, floppy® discs, magnetic strips), optical discs (eg, compact discs (CDs) or digital versatile discs (DVDs). )), Smart card, flash memory device (eg card, stick, or key drive), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical Includes erasable PROM (EEPROM®), registers, removable discs, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable media may also include, for example, carrier waves, transmission lines, and any other suitable medium for transmitting instructions and / or software that can be accessed and read by a computer. The computer-readable medium 806 may reside within the processing system 814, be outside the processing system 814, or be distributed across multiple entities including the processing system 814. The computer-readable medium 806 can be embodied in a computer program product. In some examples, the computer-readable medium 806 may be part of memory 805. As an example, a computer program product may include a computer-readable medium of packaging material. One of ordinary skill in the art will recognize the best way to implement the described functionality presented throughout this disclosure, depending on the particular application and the overall design constraints imposed on the entire system. Let's do it.

[0092] In some aspects of the present disclosure, the processor 804 may include circuits configured for various functions. For example, processor 804 has a variety of features, including utilizing the Service Data Adaptation Protocol (SDAP) layer to facilitate quality of service (QoS) flow remapping, for example, as described herein. It may include a QoS mapping circuit 841 configured for. The QoS mapping circuit 841 may be configured to detect the mapping reconfiguration of the first QoS flow from the first data radio bearer (DRB) to the second DRB. For example, a quality of service 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 reflective mapping, where the mapping reconfiguration is , The packet associated with the first QoS flow is detected based on whether it is first received via the first DRB and then from the base station via the second DRB.

[0093] The QoS mapping circuit 841 may be further configured to generate an SDAP control protocol data unit (PDU) in response to the mapping reconstruction, where the SDAP control PDU is associated with a first QoS flow. Provides an indication that the final SDAP data PDU was transmitted over the first DRB. In some examples, the SDAP control PDU can be configured to be easily distinguishable from the SDAP data PDU. For example, the QoS mapping circuit 841 may be configured to include a control identifier in the SDAP control PDU to facilitate the distinction between the SDAP control PDU and the SDAP data PDU. In certain implementations, the QoS mapping circuit 841 may be configured to include data / control (D / C) bits in each of the SDAP control PDU and SDAP data PDU, where the D / C bits are SDAP. Facilitates the distinction between control PDUs and SDAP data PDUs.

[0094] The QoS mapping circuit 841 may be further configured to include a QoS flow identifier (QFI) parameter within the SDAP control PDU. QFI parameters can identify specific QoS flows applicable to the control information contained in the SDAP control PDU. For example, the QoS mapping circuit 841 may be configured to set the QFI parameters in the SDAP control PDU to values corresponding to the first QoS flow. The QoS mapping circuit 841 is further configured to comply with the order in which the transmitter-side SDAP layer transmits the SDAP control PDU after transmitting the final SDAP data PDU related to the first QoS flow via the first DRB. Can be done. In some examples, observing the order means having 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. To facilitate. For example, a QoS mapping circuit 841 may be configured to adhere to such an order by utilizing the Packet Data Convergence Protocol (PDCP) entity associated with the first DRB.

[0095] The QoS mapping circuit 841 may be further configured to generate SDAP control PDUs based on whether untransmitted SDAP data PDUs are associated with a first QoS flow. In some examples, the untransmitted SDAP data PDU can be, for example, in the transmit buffer 815 associated with the SDAP layer, which may be contained in memory 805. For example, the QoS mapping circuit 841 may be configured to include endmarker parameters in the SDAP header of the untransmitted SDAP data PDU instead of generating the 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.

[0096] In another example, the QoS mapping circuit 841 detects and reconfigures the mapping of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB. It may be further configured to set endmarker parameters in the header of the first SDAP data protocol data unit (PDU) received from the higher layer after. The endmarker 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.

[0097] Processor 804 further provides a DL reception and processing circuit 842 configured to receive and process downlink data, control information, and other signals received within one or more subframes or slots. Can include. For example, the DL reception and processing circuit 842 may be configured to receive an RRC message indicating the mapping reconstruction of the first QoS flow from the first DRB to the second DRB via the transceiver 810. The DL reception and processing circuit 842 further receives the packet associated with the first QoS flow via the second DRB after being first received via the transceiver 810 via the first DRB. Can be configured. The DL reception and processing circuit 842 is intended to execute DL reception and processing software 852 stored on a computer-readable medium 806 to implement one or more of the functions described herein. It can be further configured.

[0098] Processor 804 may further include UL generation and transmission circuitry 843 configured to generate and transmit data and control information within one or more subframes or slots. For example, the UL generation and transmission circuit 843 receives the SDAP control PDU from the QoS mapping circuit 841 via the first DRB and transmits the SDAP control PDU to the scheduling entity (eg, base station) via the transceiver 810. Can be configured as The UL generation and transmission circuit 843 receives the SDAP data PDU from the QoS mapping circuit 841 and receives the SDAP data PDU containing an end marker parameter indicating that the SDAP data PDU is the final SDAP data PDU associated with the QoS flow on a particular DRB, and the transceiver 810. It may be further configured to send SDAP data PDUs to a scheduling entity (eg, a base station) via. The UL generation and transmission circuit 843 is to execute the UL generation and transmission software 853 stored on a computer-readable medium 806 to implement one or more of the functions described herein. It can be further configured.

[0099] FIG. 9 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary scheduling entity 900 using the processing system 914. According to various aspects of the present disclosure, an element, or any part of an element, or any combination of elements can be implemented in a processing system 914 that includes one or more processors 904. For example, the scheduling entity 900 can be the base station exemplified in any one or more of FIGS. 1, 2, and / or 4.

[0100] The processing system 914 is substantially the same as the processing system 914 exemplified in FIG. 9, and includes a bus interface 908, a bus 902, a memory 905, a processor 904, and a computer-readable medium 906. Can include. Further, the scheduling entity 900 may include an optional user interface 912 and transceiver 910 that are substantially similar to those described above in FIG. That is, processor 904 can be used to implement any one or more of the processes described below when utilized in the scheduling entity 900.

[0101] In some aspects of the disclosure, the processor 904 is a service data adaptation protocol (SDAP) layer to facilitate quality of service (QoS) flow remapping, eg, as described herein. Can include a QoS mapping circuit 941 configured for a variety of functions, including the use of. In some examples, the QoS mapping circuit 941 receives at least one SDAP data PDU associated with the first QoS flow from the scheduled entity via the first DRB and through the second DRB. It may be configured to receive at least one SDAP data PDU associated with one QoS flow. In some examples, the QoS mapping circuit 941 indicates that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB, the first QoS flow via the first DRB. It may be further configured to transfer at least one SDAP data PDU received via a second DRB to a higher layer in response to receiving a SDAP control PDU applicable to.

[0102] The QoS mapping circuit 941 identifies the SDAP control PDU based on the control identifier contained in the SDAP control PDU, and identifies the SDAP data PDU based on the control identifier contained in the SDAP header of the SDAP data PDU. Can be further configured. In some examples, the control identifier facilitates the distinction between SDAP control PDUs and SDAP data PDUs. For example, the QoS mapping circuit 941 may be configured to identify the SDAP control PDU by checking the values of the D / C bits in each of the SDAP control PDU and the SDAP data PDU, where the D / C bits are. , Makes it easy to distinguish between SDAP control PDUs and SDAP data PDUs.

[0103] The QoS mapping circuit 941 may be further configured to identify the QoS flow identifier (QFI) parameters 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 flows identified by the QFI parameters contained in the SDAP control PDU.

[0104] In another example, the QoS mapping circuit 941 is applicable to the first QoS flow and sets the end marker parameters in the SDAP header of at least one SDAP data PDU received via the first DRB. In response to the detection, at least one SDAP data PDU received via the second DRB may be configured to be transferred to a higher layer. The QoS mapping circuit 941 may be further configured to run QoS mapping software 941 stored on a computer-readable medium 906 to implement one or more of the features described herein. ..

[0105] Processor 904 may further include DL generation and transmission circuits 942 configured to generate and transmit downlink data, control information, and other signals within one or more subframes or slots. For example, the DL generation and transmission circuit 942 is configured to send an RRC message to the scheduled entity via the transceiver 910 indicating a reconfiguration of the mapping of the first QoS flow from the first DRB to the second DRB. Can be done. The DL generation and transmission circuit 942 further transmits packets related to the first QoS flow via the second DRB after being first transmitted via the transceiver 910. Can be configured. The DL generation and transmission circuit 942 is intended to execute DL generation and transmission software 952 stored on a computer-readable medium 906 to implement one or more of the functions described herein. It can be further configured.

[0106] Processor 904 may further include UL reception and processing circuitry 943 configured to receive and process data and control information received within one or more subframes or slots. For example, the UL reception and processing circuit 943 may be configured to provide the QoS mapping circuit 941 with an SDAP control PDU for the first QoS flow received from the scheduled entity via the first DRB. The UL reception and processing circuit 943 may be further configured to provide the QoS mapping circuit 941 with the SDAP data PDU for the first QoS flow received from the scheduled entity on the first DRB. In some examples, the SDAP data PDU may include endmarker parameters indicating that the SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB. The UL reception and processing circuit 943 may be further configured to provide the QoS mapping circuit 941 with the SDAP data PDU of the first QoS flow received from the scheduled entity on the second DRB. The UL reception and processing circuit 943 is to execute the UL reception and processing software 953 stored on a computer-readable medium 906 to implement one or more of the functions described herein. It can be further configured.

[0107] FIG. 10 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 a particular implementation within the scope of the present disclosure, and some illustrated features may be implemented in all embodiments. It may not be necessary for the installation. In some examples, process 1000 may be executed by the scheduled entity 800 illustrated in FIG. In some examples, process 1000 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0108] In block 1002, the scheduled entity may detect a mapping reconstruction of the first QoS flow from the first DRB to the second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from the scheduling entity that is wirelessly communicating with the scheduled entity. In another example, the scheduled entity may detect the mapping restructuring via reflective mapping, where the mapping restructuring is such that the packets associated with the first QoS flow first go through the first DRB. Is received and then detected based on whether it is received from the scheduling entity via the second DRB. For example, the QoS mapping circuit 841 may detect the mapping reconstruction, along with the DL reception and processing circuit 842 shown and described above with reference to FIG.

[0109] In block 1004, the scheduled entity responds to the mapping reconfiguration to indicate that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB. Can be generated. In some examples, the SDAP control PDU may include a control identifier that facilitates the distinction 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, where the D / C bit facilitates the distinction between the SDAP control PDU and the SDAP data PDU. To. 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 QoS mapping circuit 841 shown and described above with reference to FIG. 8 may generate a SDAP controlled PDU.

[0110] In block 1006, the scheduled entity may transmit the SDAP control PDU to the receiver (eg, the scheduling entity) via the first DRB. For example, the UL generation and transmission circuit 843 may transmit the SDAP control PDU to the receiver, along with the transceiver 810 shown and described above with reference to FIG.

[0111] FIG. 11 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 a particular implementation within the scope of the present disclosure, and some illustrated features may be implemented in all embodiments. It may not be necessary for the installation. In some examples, process 1100 may be performed by the scheduled entity 800 illustrated in FIG. In some examples, process 1100 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0112] At block 1102, the scheduled entity may detect a mapping reconstruction of the first QoS flow from the first DRB to the second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from the scheduling entity that is wirelessly communicating with the scheduled entity. In another example, the scheduled entity may detect the mapping restructuring via reflective mapping, where the mapping restructuring is such that the packets associated with the first QoS flow first go through the first DRB. Is received and then detected based on whether it is received from the scheduling entity via the second DRB. For example, the QoS mapping circuit 841 may detect the mapping reconstruction, along with the DL reception and processing circuit 842 shown and described above with reference to FIG.

[0113] At block 1104, the scheduled entity may identify whether the buffer contains untransmitted SDAP data PDUs associated with the first QoS flow. In some examples, the buffer can be associated with the SDAP layer in the scheduled entity. For example, the QoS mapping circuit 841 shown and described above with reference to FIG. 8 can identify the presence or absence of untransmitted SDAP data PDUs.

[0114] If the buffer contains untransmitted SDAP data PDUs associated with the first QoS flow (Y-branch of block 1104), in block 1106, the scheduled entity is the SDAP of the untransmitted SDAP data PDUs. Endmarker parameters can be included in the header. The end marker parameter indicates that the untransmitted SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB. For example, the QoS mapping circuit 841 shown and described above with reference to FIG. 8 may include endmarker parameters in the untransmitted SDAP data PDU.

[0115] At block 1108, the scheduled entity may transmit an untransmitted SDAP data PDU containing endmarker parameters to a receiver (eg, a scheduling entity). For example, the UL generation and transmission circuit 843 may transmit untransmitted SDAP data PDUs to the receiver, along with the transceiver 810 shown and described above with reference to FIG.

[0116] In block 1110, the scheduled entity is associated with a first QoS flow if the buffer does not contain untransmitted SDAP data PDUs associated with the first QoS flow (N-branch of block 1104). An SDAP control PDU may be generated in response to the mapping reconstruction to indicate that the final SDAP data PDU has been transmitted over the first DRB. In some examples, the SDAP control PDU may include a control identifier that facilitates the distinction 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, where the D / C bit facilitates the distinction between the SDAP control PDU and the SDAP data PDU. To. 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 QoS mapping circuit 841 shown and described above with reference to FIG. 8 may generate a SDAP controlled PDU.

[0117] In block 1112, the scheduled entity may transmit the SDAP control PDU to the receiver (eg, the scheduling entity) via the first DRB. For example, the UL generation and transmission circuit 843 may transmit the SDAP control PDU to the receiver, along with the transceiver 810 shown and described above with reference to FIG.

[0118] FIG. 12 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 a particular implementation within the scope of the present disclosure, and some illustrated features may be implemented in all embodiments. It may not be necessary for the installation. In some examples, process 1200 may be performed by the scheduling entity 900 illustrated in FIG. In some examples, process 1200 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0119] In block 1202, the scheduling entity receives at least one SDAP data PDU associated with the first QoS flow via the first DRB and is associated with the first QoS flow via the second DRB. At least one SDAP data PDU may be received. For example, the QoS mapping circuit 941 is at least one associated with the first QoS flow via the first DRB, along with the UL reception and processing circuit 943 and transceiver 910 shown and described above with reference to FIG. The SDAP data PDU may be received and at least one SDAP data PDU associated with the first QoS flow may be received via the second DRB.

[0120] At block 1204, the scheduling entity may receive an SDAP control PDU applicable to the first QoS flow via the first DRB. The SDAP control PDU may indicate that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB. In some examples, the scheduling entity may identify the SDAP control PDU based on the control identifier in the SDAP control PDU that facilitates the distinction between the SDAP control PDU and the SDAP data PDU. For example, the scheduling entity may confirm the value of the data / control (D / C) bit in each of the SDAP control PDU and at least one SDAP data PDU, where the D / C bit is at least one with the SDAP control PDU. Facilitates the distinction between two SDAP data PDUs. 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 the QoS flow identified by the QFI parameter in the SDAP control PDU (eg,). , The control information of the SDAP control PDU can be further applied only to the first QoS flow). For example, the QoS mapping circuit 941 may receive the SDAP control PDU along with the UL reception and processing circuit 943 and transceiver 910 shown and described above with reference to FIG.

[0121] In block 1206, the scheduling entity at least received via the second DRB in response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB. One SDAP data PDU can be transferred to a higher layer. For example, the QoS mapping circuit 941 shown and described above with reference to FIG. 9 may transfer at least one SDAP data PDU received via the second DRB to a higher layer.

[0122] FIG. 13 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 a particular implementation within the scope of the present disclosure, and some illustrated features may be implemented in all embodiments. It may not be necessary for the installation. In some examples, process 1300 may be performed by the scheduled entity 800 illustrated in FIG. In some examples, process 1300 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0123] In block 1302, the scheduled entity may detect a mapping reconstruction of the first QoS flow from the first DRB to the second DRB. In some examples, the scheduled entity may detect the mapping reconfiguration via an RRC message from the scheduling entity that is wirelessly communicating with the scheduled entity. In another example, the scheduled entity may detect the mapping restructuring via reflective mapping, where the mapping restructuring is such that the packets associated with the first QoS flow first go through the first DRB. Is received and then detected based on whether it is received from the scheduling entity via the second DRB. For example, the QoS mapping circuit 841 may detect the mapping reconstruction, along with the DL reception and processing circuit 842 shown and described above with reference to FIG.

[0124] In block 1304, the scheduled entity may set endmarker parameters in the SDAP header of the first SDAP data PDU received from the higher 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 QoS mapping circuit 841 shown and described above with reference to FIG. 8 may include endmarker parameters in the first SDAP data PDU.

[0125] In block 1306, the scheduled entity receives a first SDAP data PDU containing endmarker parameters and at least one subsequent SDAP data PDU associated with the first QoS flow (eg, a scheduling entity). Can be sent to. The first SDAP data PDU is transmitted to the receiver via the first DRB and at least one subsequent SDAP data PDU is transmitted to the receiver via the second DRB. For example, the UL generation and transmission circuit 843 may transmit a first SDAP data PDU and at least one subsequent SDAP data PDU to the receiver, along with the transceiver 810 shown and described above with reference to FIG.

[0126] Several aspects of wireless communication networks are presented with reference to exemplary implementations. The various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards so that those skilled in the art will readily recognize them.

[0127] As an example, various aspects include Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications (UMTS), and / or Global Systems for Mobile (GSM®). ) Can be implemented within other systems defined by 3GPP. Various aspects can also be extended to systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples include IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth®, and / or in systems using other suitable systems. Can be implemented. The actual telecommunications standard, network architecture, and / or communication standard used will depend on the overall design constraints imposed on the particular application and system.

[0128] Within the present disclosure, the word "exemplary" is used to mean "act as an example, case, or example." Any implementation or aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over the other aspects of the present disclosure. Similarly, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages, or modes of operation described. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A is in physical contact with object B and object B is in contact with object C, objects A and C may be in direct physical contact with each other, even if they are not in direct physical contact with each other. It can still be considered to be connected to each other. For example, the first object will be bound to the 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 to enable the performance of the functions described in this disclosure, regardless of the type of electronic circuit, when connected and configured. Intended to include both hardware implementations of electrical devices and conductors and software implementations of information and instructions that enable the performance of the functions described in this disclosure when performed by a processor. Will be done.

[0129] One or more of the components, steps, features, and / or functions exemplified in FIGS. 1-13 are rearranged into a single component, step, feature, or function and / or. It can be combined or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the new features disclosed herein. The devices, devices, and / or components exemplified in FIGS. 1, 2, 4, 8, and / or 9 perform one or more of the methods, features, or steps described herein. Can be configured to. The novel algorithms described herein can also be implemented efficiently in software and / or integrated into hardware.

[0130] It should be understood that the particular order or hierarchy of steps in the disclosed method is an example of an exemplary process. It should be understood that the particular order or hierarchy of steps in these methods can be rearranged based on design preferences. The accompanying method claims present the elements of the various steps in an exemplary order and are not intended to be limited to the particular order or hierarchy presented unless specified herein.

[0131] The above description is provided to allow one of ordinary skill in the art to implement the various aspects described herein. Various modifications to these embodiments will be readily apparent to those of skill in the art, and the comprehensive principles defined herein may apply to other embodiments. Therefore, the scope of claims is not intended to be limited to the aspects set forth herein, but should be given the full scope consistent with the wording in the claims. In, reference to a singular element is not intended to mean "one and only one" unless otherwise stated, but rather "one or more". (One or more) ". Unless otherwise stated, the term "some / some" refers to one or more. An expression that refers to "at least one" of a list of items refers to any combination of those items, including a single member. As an 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 and b and c. NS. All structural and functional equivalents of the various aspects of the elements described throughout this disclosure, which will be known to those of skill in the art or will be known later, are expressly incorporated herein by reference. , It is intended to be included by the scope of claims. Moreover, none of the disclosures herein are intended to be dedicated to the public, whether or not such disclosures are explicitly stated in the claims.

Claims (35)

It ’s a wireless communication method.
Detecting the mapping reconstruction of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB,
In response to the mapping reconstruction, a service data adaptation protocol (SDAP) control protocol data unit (PDU) is generated, wherein the SDAP control PDU is the final SDAP data PDU associated with the first quality of service flow. Provides an indication that was transmitted over the first DRB.
A method comprising transmitting the SDAP control PDU to a receiver via the first DRB. Detecting the mapping reconstruction
The method of claim 1, comprising detecting the mapping reconstruction via a radio resource control (RRC) message. Detecting the mapping reconstruction
It comprises detecting the mapping reconstruction via reflective mapping, where the mapping reconstruction is such that the packet associated with the first QoS flow was first received via the first DRB. It is later detected based on whether it is received via the second DRB.
The method according to claim 1. Generating the SDAP controlled PDU is
The SDAP control PDU includes a control identifier, wherein the control identifier facilitates the distinction between the SDAP control PDU and the SDAP data PDU.
The method according to claim 1. Including the control identifier
Each of the SDAP control PDU and the SDAP data PDU includes a data / control (D / C) bit, wherein the D / C bit is the distinction between the SDAP control PDU and the SDAP data PDU. To facilitate
The method according to claim 4. Generating the SDAP controlled PDU is
The SDAP control PDU includes a QoS flow identifier (QFI) parameter, wherein the QFI parameter identifies a particular QoS flow applicable to the control information contained in the SDAP control PDU.
The method according to claim 1. Generating the SDAP controlled PDU is
The method of claim 6, further comprising setting the QFI parameter in the SDAP control PDU to a value corresponding to the first QoS flow. Sending the SDAP control PDU is
To enable the receiver-side SDAP layer to receive the SDAP-controlled PDU after receiving the final SDAP data PDU associated with the first QoS flow via the first DRB, the transmitter-side. The first aspect of claim 1, wherein the SDAP layer adheres to the order of transmitting the SDAP control PDU after transmitting the final SDAP data PDU associated with the first QoS flow via the first DRB. the method of. The method of claim 8, wherein observing the order is performed by the Packet Data Convergence Protocol (PDCP) entity associated with the first DRB. Generating the SDAP controlled PDU is
Identifying whether the buffer comprises untransmitted SDAP data PDUs associated with the first QoS flow.
When the buffer comprises the untransmitted SDAP data PDU associated with the first QoS flow, the SDAP header of the untransmitted SDAP data PDU includes an endmarker parameter, wherein the endmarker. The parameter indicates that the untransmitted SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB.
The method of claim 1, further comprising transmitting the untransmitted SDAP data PDU to the receiver. Generating the SDAP controlled PDU is
10. The method of claim 10, further comprising generating the SDAP control PDU when the buffer does not include the untransmitted SDAP data PDU associated with the first QoS flow. A scheduled entity in a wireless communication network
With the processor
With a transceiver communicatively coupled to the processor
The processor comprises a memory that is communicatively coupled to the processor.
Detecting the mapping reconstruction of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB,
In response to the mapping reconstruction, a service data adaptation protocol (SDAP) control protocol data unit (PDU) is generated, wherein the SDAP control PDU is the final SDAP data PDU associated with the first quality of service flow. Provides an indication that was transmitted over the first DRB.
A scheduled entity configured to transmit the SDAP control PDU via the transceiver to the scheduling entity via the first DRB. The processor
Further configured to detect said mapping reconstruction via radio resource control (RRC) messages.
The scheduled entity according to claim 12. The processor
It is further configured to detect the mapping reconstruction via reflective mapping, where the mapping reconstruction is such that the packet associated with the first QoS flow is first received via the first DRB. Detected based on whether it is received via the second DRB after it has been
The scheduled entity according to claim 12. The processor
The SDAP control PDU is further configured to include a control identifier, wherein the control identifier facilitates the distinction between the SDAP control PDU and the SDAP data PDU.
The scheduled entity according to claim 12. The processor
Each of the SDAP control PDU and the SDAP data PDU is further configured to include a data / control (D / C) bit, wherein the D / C bit is a combination of the SDAP control PDU and the SDAP data PDU. To facilitate the distinction,
The scheduled entity according to claim 15. The processor
The SDAP control PDU is further configured to include a QoS flow identifier (QFI) parameter, wherein the QFI parameter identifies a particular QoS flow applicable to the control information contained in the SDAP control PDU.
The scheduled entity according to claim 12. The processor
Further configured to set the QFI parameters in the SDAP control PDU to values corresponding to the first QoS flow.
The scheduled entity according to claim 17. The processor
To allow a receiver-side SDAP layer within the scheduling entity to receive the SDAP control PDU after receiving the final SDAP data PDU associated with the first QoS flow via the first DRB. In addition, the transmitter-side SDAP layer in the scheduled entity transmits the SDAP control PDU after transmitting the final SDAP data PDU related to the first QoS flow via the first DRB. Further configured to comply,
The scheduled entity according to claim 12. The processor
Identifying whether the buffer in memory comprises an untransmitted SDAP data PDU associated with the first QoS flow.
When the buffer comprises the untransmitted SDAP data PDU associated with the first QoS flow, the SDAP header of the untransmitted SDAP data PDU includes an endmarker parameter, wherein the endmarker. The parameter indicates that the untransmitted SDAP data PDU is the final SDAP data PDU associated with the first QoS flow on the first DRB.
The scheduled entity according to claim 12, further configured to transmit the untransmitted SDAP data PDU to the scheduling entity. The processor
Further configured to generate the SDAP control PDU when the buffer does not include the untransmitted SDAP data PDU associated with the first QoS flow.
The scheduled entity according to claim 20. It ’s a wireless communication method.
Receives multiple service data adaptation protocol (SDAP) data protocol data units (PDUs) associated with a first quality of service flow from a transmitter via both a first data radio bearer (DRB) and a second DRB. To do and
Receiving the SDAP control PDU applicable to the first QoS flow from the transmitter via the first DRB, and
In response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB, the plurality of SDAP data PDUs received via the second DRB are ranked higher. With the transfer to the layer,
Here, the SDAP control PDU provides an indication that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB.
Method. It further comprises identifying the SDAP control PDU based on a control identifier in the SDAP control PDU, wherein the control identifier facilitates the distinction between the SDAP control PDU and the at least one SDAP data PDU. ,
22. The method of claim 22. Identifying the SDAP control PDU is
Further comprising confirming the value of a data / control (D / C) bit in each of the SDAP control PDU and the at least one SDAP data PDU, wherein the D / C bit is the SDAP control PDU and said. To facilitate the distinction from at least one SDAP data PDU,
23. The method of claim 23. Identifying the QoS flow identifier (QFI) parameters in the SDAP control PDU
22. The method of claim 22, further comprising applying the control information of the SDAP control PDU only to the first QoS flow identified by the QFI parameter in the SDAP control PDU. A scheduling entity within a wireless communication network
With the processor
With a transceiver communicatively coupled to the processor
The processor comprises a memory that is communicatively coupled to the processor.
A plurality of service data adaptive protocol (SDAP) data protocol data units associated with a first quality of service flow from a scheduled entity via both a first data radio bearer (DRB) and a second DRB via said transceiver. Receiving (PDU) and
Receiving an SDAP-controlled PDU applicable to the first QoS flow from the scheduled entity via the transceiver and via the first DRB.
In response to receiving the SDAP control PDU applicable to the first QoS flow via the first DRB, the plurality of SDAP data PDUs received via the second DRB are ranked higher. It is configured to do and to transfer to layers
Here, the SDAP control PDU provides an indication that the final SDAP data PDU associated with the first QoS flow has been transmitted over the first DRB.
Scheduling entity. The processor
It is further configured to identify the SDAP control PDU based on the control identifier in the SDAP control PDU, where the control identifier facilitates the distinction between the SDAP control PDU and the at least one SDAP data PDU. do,
The scheduling entity of claim 26. The processor
It is further configured to confirm the value of the data / control (D / C) bits in each of the SDAP control PDU and the at least one SDAP data PDU, wherein the D / C bits are the same as the SDAP control PDU. To facilitate the distinction from the at least one SDAP data PDU.
27. The scheduling entity of claim 27. The processor
Identifying the QoS flow identifier (QFI) parameters in the SDAP control PDU
26. The scheduling entity of claim 26, further configured to apply control information of the SDAP control PDU only to the first QoS flow identified by the QFI parameter in the SDAP control PDU. .. It ’s a wireless communication method.
Detecting the mapping reconstruction of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB,
Setting the end marker parameter in the service data adaptation protocol (SDAP) header of the first SDAP data protocol data unit (PDU) received from the upper layer after the mapping reconstruction, wherein the end marker parameter is 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.
The first SDAP data PDU and at least one subsequent SDAP data PDU related to the first QoS flow are transmitted to the receiver, wherein the first SDAP data PDU is the first. The at least one subsequent SDAP data PDU is transmitted via the second DRB.
How to prepare. Detecting the mapping reconstruction
30. The method of claim 30, comprising detecting the mapping reconstruction via a radio resource control (RRC) message. Detecting the mapping reconstruction
It comprises detecting the mapping reconstruction via reflective mapping, where the mapping reconstruction is such that the packet associated with the first QoS flow was first received via the first DRB. It is later detected based on whether it is received via the second DRB.
30. The method of claim 30. A scheduled entity in a wireless communication network
With the processor
With a transceiver communicatively coupled to the processor
The processor comprises a memory that is communicatively coupled to the processor.
Detecting the mapping reconstruction of the first quality of service (QoS) flow from the first data radio bearer (DRB) to the second DRB,
Setting the end marker parameter in the service data adaptation protocol (SDAP) header of the first SDAP data protocol data unit (PDU) received from the upper layer after the mapping reconstruction, wherein the end marker parameter is 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.
Sending 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, where the first SDAP data The PDU is transmitted via the first DRB, and the at least one subsequent SDAP data PDU is transmitted via the second DRB.
A scheduled entity that is configured to do. The processor
Further configured to detect said mapping reconstruction via radio resource control (RRC) messages.
The scheduled entity according to claim 33. The processor
It is further configured to detect the mapping reconstruction via reflective mapping, where the mapping reconstruction is such that the packet associated with the first QoS flow is first received via the first DRB. Detected based on whether it is received via the second DRB after it has been
The scheduled entity according to claim 33.

Images