Method and apparatus for managing data communications in a wireless communication network

Abstract

Embodiments herein disclose a method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, first information about a mapping between at least one quality of service identifier, QoS ID, and at least one data radio bearer, DRB; identifying a QoS ID associated with a first uplink packet; based on the first information, identifying whether there is a DRB mapped to the QoS ID associated with the first uplink packet; and based on no DRB being identified, transmitting the first uplink packet to the base station on a default DRB, wherein the first uplink packet is marked by the QoS ID.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a wireless communication system. More specifically, to a method and apparatus for managing data communication in a next-generation communication system such as a 5G wireless communication system. BACKGROUND

[0002] To meet increasing demand with respect to wireless data traffic after deployment of 4th generation (4G) communication systems, efforts have been made to develop 5th generation (5G) or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "beyond 4G networks" or "post long term evolution (LTE) systems." 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates beyond those of 4G communication systems. To decrease propagation loss of the radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, and analog beamforming are discussed for use in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a device-to-device (D2D) communication, wireless backhaul, a moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), which are advanced coding modulation (ACM) methods, and filter bank multi-carrier (FBMC), orthogonal frequency division multiplexing (OFDM) and the like, which are advanced access techniques, are developed.

[0003] The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of Things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of the IoT technology and the Big Data processing technology through connection with a cloud server, has emerged as a new paradigm for the IoT. As technology elements for the IoT, such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" have been developed for use in connection with a sensor network, Machine-to-Machine (M2M) communication, Machine Type Communication (MTC), and so forth. The IoT has been applied to a variety of fields such as smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, M2M communications, and D2D communications can be implemented using beamforming, MIMO, and array antennas. The application of cloud RAN, a big data processing technology mentioned above, can also be seen as an example of the convergence of 5G and IoT technologies.

[0005] Several broadband wireless technologies have been developed to cater to the growing number of broadband subscribers and provide more and better applications and services. Second-generation wireless communication networks were developed to provide voice services while ensuring user mobility. Third-generation wireless communication systems support not only voice services but also data services. In recent years, fourth-generation wireless communication systems have been developed to provide high-speed data services. However, fourth-generation wireless communication systems currently lack the resources to meet the growing demand for high-speed data services. Therefore, fifth-generation wireless communication networks are being developed to meet the growing demand for high-speed data services, support ultra-reliable, low-latency applications, and support massive machine-type communications.

[0006] In the existing system, Figure 1 A bearer service architecture for supporting QoS is shown in FIG. An evolved packet service (EPS) bearer is established between a user equipment (UE) 110 and a public data network (PDN) gateway for the transport of application packets (or Internet Protocol (IP) packets). An EPS bearer is a bearer corresponding to an IP packet flow (or service data flow) with defined QoS between the UE 110 and the PDN gateway. An EPS bearer can be bidirectional or unidirectional. Multiple EPS bearers can be established for the UE 110 in order to provide different QoS flows or connections to different PDNs. In an example, a user can be busy on a voice call (i.e., a VoIP call) while performing web browsing or file transfer protocol (FTP) downloads. The VoIP EPS bearer will provide the necessary QoS for the voice call, while the best effort EPS bearer will be suitable for a web browsing or FTP session.

[0007] One EPS bearer and EUTRA Radio Access Bearer (E-RAB) is established when UE 110 connects to a PDN and remains established throughout the lifetime of the PDN connection, providing UE 110 with always-on IP connectivity to that PDN. This bearer is referred to as the default EPS bearer. Any additional EPS bearers / E-RABs established to the same PDN are referred to as dedicated bearers. Initial bearer-level QoS parameter values ​​for the default bearer are assigned by the network based on subscription data. The decision to establish or modify a dedicated bearer can only be made by the EPC, and bearer-level QoS parameter values ​​are always assigned by the EPC.

[0008] EPS bearers / E-RABs are the granularity level for bearer-level QoS control in the network. That is, service data flows (SDFs) mapped to the same EPS bearer receive the same bearer-level packet forwarding treatment (e.g., scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.).

[0009] If dedicated network resources for the GBR value associated with an EPS bearer / E-RAB are permanently allocated at bearer establishment / modification time (e.g., by the admission control function in the eNodeB), then the EPS bearer / E-RAB is called a guaranteed bit rate (GBR) bearer. Otherwise, the EPS bearer / E-RAB is called a non-GBR bearer. Dedicated bearers can be either GBR or non-GBR, while the default bearer shall be a non-GBR bearer.

[0010] Applications / IP flows or SDFs are mapped to EPS bearers based on packet classification rules or traffic flow templates (TFTs), namely, the source IP address, destination IP address, and port number of the IP flow or SDF. The UL TFT in UE 110 binds SDFs to EPS bearers in the uplink (UL) direction. Multiple SDFs can be multiplexed onto the same EPS bearer by including multiple uplink packet filters in the UL TFT. The DL TFT in PDN GW 140 binds SDFs to EPS bearers in the downlink (DL) direction. Multiple SDFs can be multiplexed onto the same EPS bearer by including multiple downlink packet filters in the DL TFT. The E-RAB transports EPS bearer packets between UE 110 and the EPC. When an E-RAB exists, there is a one-to-one mapping between the E-RAB and the EPS bearer. The data radio bearer transports EPS bearer packets between UE 110 and one or more eNBs 120. When a data radio bearer exists, there is a one-to-one mapping between the data radio bearer and the EPS bearer / E-RAB.

[0011] Furthermore, the S1 bearer transports E-RAB packets between the eNodeB 120 and the Serving GW 130. The S5 / S8 bearer transports EPS bearer packets between the Serving GW 130 and the PDN GW 140. The UE 110 stores mappings between uplink packet filters and data radio bearers to create bindings between the SDF and the data radio bearers in the uplink. The PDN GW 140 stores mappings between downlink packet filters and S5 / S8a bearers to create bindings between the SDF and the S5 / S8a bearers in the downlink. Furthermore, the eNB 120 stores a one-to-one mapping between the data radio bearer and the S1 bearer to create bindings between the data radio bearer and the S1 bearer in both the uplink and downlink. Furthermore, the Serving GW 130 stores a one-to-one mapping between the S1 bearer and the S5 / S8a bearer to create bindings between the S1 bearer and the S5 / S8a bearer in both the uplink and downlink.

[0012] The data radio bearer and S5 / S8 bearer corresponding to each EPS bearer are established when UE 110 enters the RRC Connected state from the Idle state. If a new EPS bearer is established, a new data radio bearer can be set up during the Connected state. If the corresponding EPS bearer is released, the existing data radio bearer is released during the Connected state. When the RRC connection is released, all data radio bearers are released. When establishing the DRB, the EPS bearer ID, PDCP configuration, RLC configuration, and logical channel configuration are provided by eNB 120 in the RRC Connection Reconfiguration message. The EPS bearer configuration provided by NAS signaling includes the EPS bearer ID, QoS information, and TFT. Summary of the Invention

[0013] Technical issues

[0014] In existing bearer concepts, SDFs with the same characteristics are mapped to the same bearer. Over-the-air (OTA) services are mapped to the same best effort EPS bearer. If SDFs of different services are mixed together in the same bearer, service "starvation or congestion" (i.e., large data blocks in the buffer) delays packets belonging to different services or delays TCP connection establishment process when TCP connection / request / response packets are queued at the end of the queue. In next generation communication design, it is proposed to remove EPS bearer to reduce signaling overhead and provide greater QoS granularity. If desired by the operator, OTA services can be handled differently. A flow-based QoS framework is being developed. In the flow-based QoS framework, a PDU session is established between the UE 110 and a data network. The PDU session can carry multiple flows, requiring QoS differentiation. QoS differentiation between several flows multiplexed on the same PDU session is provided by means of QoS marking applied to each packet. In the flow-based QoS framework, the existing method of establishing a data radio bearer and mapping packets to the data radio bearer cannot be used because an EPS bearer is not established between the UE 110 and the PDN. In the flow-based QoS framework, a robust method and apparatus for establishing a data radio bearer and mapping packets of a PDU session to the data radio bearer in the DL and UL is needed.

[0015] It is therefore desirable to address the above disadvantages or other deficiencies, or at least to provide a useful alternative.

[0016] Solution to the problem

[0017] Embodiments herein disclose a method for managing data communication in a wireless communication network. The method comprises receiving, by a gNodeB, a plurality of packets of at least one QoS flow from a network entity. A QoS flow identifier (QFI) associated with the at least one QoS flow is received in a header of each packet. Further, the method comprises mapping, by the gNodeB, each received packet of the at least one QoS flow to a DRB. The at least one QoS flow is mapped to the DRB based on the QFI associated with the at least one QoS flow.

[0018] In an embodiment, the plurality of packets of the at least one QoS flow is received by the gNodeB from the network entity by receiving the packets over at least one PDU tunnel between the gNodeB and the network entity. The PDU tunnels are each for receiving the plurality of packets of at least one QoS flow for each PDU session.

[0019] In an embodiment, if the list of at least one QoS flow identifier associated with an established DRB includes the QoS flow identifier of the received packet and the established DRB is associated with the PDU session of the received packet, then each received packet of at least one QoS flow from the network entity is mapped to the DRB by the gNodeB by mapping the received packet to the established DRB.

[0020] In an embodiment, each received packet of a QoS flow from a network entity is mapped to a DRB by a gNodeB in the following manner: if none of the established DRBs is associated with the PDU session and QoS flow of the received packet, then a new DRB is established; a signaling message including a DRB configuration of the new DRB is transmitted to a user equipment (UE), wherein the DRB configuration includes a PDU session identifier associated with the DRB and one or more of a list of QoS flow identifiers of one or more QoS flows; and the received packet is mapped to the newly established DRB.

[0021] In an embodiment, each received packet of a QoS flow from a network entity is mapped to a DRB in the following manner: if none of the established DRBs for the PDU session of the received packet is associated with the QoS flow of the received packet, then updating the configuration of the established DRB associated with the PDU session of the received packet, wherein the QoS flow identifier of the received packet is added to the QoS flow identifier list of the updated DRB; transmitting a signaling message including the DRB configuration of the updated DRB to the UE, wherein the DRB configuration includes the PDU session identifier associated with the DRB and at least one of the list of QoS flow identifiers of at least one QoS flow; and mapping the received packet to the updated DRB.

[0022] In an embodiment, a QoS flow is mapped to only one DRB.

[0023] In an embodiment, a DRB is mapped to at least one QoS flow of the same PDU session.

[0024] In an embodiment, each of the DRBs defines a packet forwarding process on a radio interface for data exchange between a UE and a gNodeB in a wireless communication network.

[0025] In an embodiment, a plurality of packets for at least one QoS flow are received by a gNodeB (i.e., a target gNodeB) from another gNodeB (i.e., a source gNodeB). A QoS flow identifier associated with each packet is also received by the gNodeB from the other gNB.

[0026] In an embodiment, a plurality of packets of at least one QoS flow are received by a gNodeB (i.e., a target gNodeB) from another gNodeB (i.e., a source gNodeB). A QoS flow identifier associated with each packet and a PDU session identifier of a PDU session are also received by the gNodeB from the other gNodeB.

[0027] Embodiments herein disclose a method for managing data communications in a wireless communication network. The method includes determining, by a UE, a DRB for transmitting a packet based on a QoS flow identifier and a PDU session associated with the packet, and mapping the QoS flow identifier to a DRB for each established PDU session. In addition, the method includes performing, by the UE, one of: mapping the packet to an established non-default DRB if the list of at least one of the QoS flow identifiers associated with the DRB includes the QoS flow identifier of the packet and the DRB is associated with the PDU session of the packet; and mapping the packet to a default DRB associated with the PDU session of the packet if none of the established non-default DRBs are associated with the PDU session of the packet and the QoS flow identifier. In addition, the method includes transmitting the packet on the mapped DRB.

[0028] In an embodiment, the UE receives a mapping of QoS flow identifiers to DRBs for each established PDU Session from the gNodeB in a signaling message.

[0029] In an embodiment, the UE receives a list of at least one of a PDU session identifier and a QoS flow identifier associated with each DRB from the gNodeB in a signaling message.

[0030] In an embodiment, the UE receives a list of at least one of the QoS flow identifiers associated with each DRB from the gNodeB in a signaling message.

[0031] In an embodiment, the UE receives a default DRB configuration associated with the PDU session from the gNodeB in a signaling message.

[0032] In an embodiment, after RRC connection establishment, the UE receives the configuration of the default DRB associated with the PDU session from the gNodeB in a signaling message.

[0033] In an embodiment, the UE includes at least one of a QoS flow identifier and a PDU session identifier in a packet header of packets transmitted on a default DRB.

[0034] In an embodiment, upon receiving a packet on the default DRB, the gNodeB establishes a new DRB for the QoS flow identifier and the PDU session identifier received in a packet header of the packet received on the default DRB. In addition, the gNodeB transmits a signaling message including a DRB configuration for the new DRB, wherein the DRB configuration includes one or more of a list of QoS flow identifiers of the one or more QoS flows and the PDU session identifier associated with the DRB.

[0035] In an embodiment, upon receiving a packet on the default DRB, the gNodeB establishes a new DRB for the QoS flow identifier received in the packet header of the packet received on the default DRB. In addition, the gNodeB transmits a signaling message including a DRB configuration for the new DRB, wherein the DRB configuration includes a list of QoS flow identifiers for one or more QoS flows associated with the DRB.

[0036] In an embodiment, upon receiving a packet on a default DRB, the gNodeB updates an established DRB corresponding to a PDU session identifier received in a packet header of the packet received on the default DRB. The gNodeB adds a QoS flow identifier of the packet received on the default DRB to a list of QoS flow identifiers of the updated DRB. In addition, the gNodeB transmits a signaling message including a DRB configuration for the updated DRB, wherein the DRB configuration includes one or more of a PDU session identifier associated with the DRB and a list of QoS flow identifiers of one or more QoS flows.

[0037] In an embodiment, upon receiving a packet on a default DRB, the gNodeB updates the established DRB. The QoS flow identifier of the packet received on the default DRB is added to the list of QoS flow identifiers of the updated DRB. In addition, the gNodeB transmits a signaling message including a DRB configuration for the updated DRB, wherein the DRB configuration includes a list of QoS flow identifiers for one or more QoS flows associated with the DRB.

[0038] Embodiments herein disclose an apparatus for managing data communication in a wireless communication network. The apparatus comprises a processor and a memory for storing a DRB configuration. A DRB management unit is coupled to the memory and the processor. The DRB management unit is configured to receive a plurality of packets of at least one QoS flow from a network entity. A QoS flow identifier associated with the at least one QoS flow is received in a header of each packet. The DRB management unit is configured to receive a plurality of packets of the at least one QoS flow from another gNodeB (i.e., a source gNodeB). At least one of a QoS flow identifier associated with each packet and a PDU session identifier of a PDU session is also received. Further, the DRB management unit is configured to map each received packet of the at least one QoS flow to a DRB. The at least one QoS flow is mapped to the DRB based on an ID and a QoS parameter associated with the at least one QoS flow.

[0039] Embodiments herein disclose a UE for managing data communication in a wireless communication network. The UE comprises a processor and a memory for storing a DRB configuration received from a gNodeB in the wireless communication network. A DRB management unit is coupled to the memory and the processor. The DRB management unit is configured to determine a DRB for transmitting a packet based on a QoS flow identifier associated with the packet and a PDU session, and map the QoS flow identifier to a DRB for each established PDU session. Further, the UE is configured to perform one of: map the packet to an established non-default DRB if a list of at least one of QoS flow identifiers associated with the DRB includes the QoS flow identifier of the packet and the DRB is associated with a PDU session of the packet; and map the packet to a default DRB associated with a PDU session of the packet if none of the established non-default DRBs are associated with the PDU session and the QoS flow identifier of the packet. Further, the UE is configured to transmit the packet on the mapped DRB.

[0040] These and other aspects of embodiments herein will be better appreciated and understood when considered in connection with the following description and accompanying drawings. It should be understood, however, that the following description, while indicating preferred embodiments and numerous specific details thereof, is given by way of illustration and not of limitation. Many changes and modifications can be made within the scope of embodiments herein without departing from the spirit thereof, and embodiments herein include all such changes and modifications.

[0041] Advantages of the invention

[0042] A primary object of embodiments herein is to provide a method and an apparatus for managing data communication in a next generation wireless communication system.

[0043] Another object of embodiments herein is to receive, by a gNodeB from a network entity, a plurality of packets of one or more QoS flows.

[0044] Another object of embodiments herein is to map, by a gNodeB, each received packet of one or more QoS flows to a DRB.

[0045] Another object of embodiments herein is to determine, by a UE, a DRB for transmitting a packet based on a QoS flow identifier and a PDU session associated with the packet, and to map the QoS flow identifier to a DRB for each established PDU session.

[0046] Another object of embodiments herein is to receive a mapping of QoS flow identifiers to DRBs for each established PDU Session from the gNodeB in a signaling message.

[0047] It is another object of embodiments herein to map a packet to an established non-default DRB by the UE if the list of one or more QoS flow identifiers associated with the DRB includes the QoS flow identifier of the packet and the DRB is associated with a PDU session of the packet.

[0048] Another object of embodiments herein is to map a packet by the UE to a default DRB associated with a packetized PDU session if none of the established non-default DRBs are associated with the packetized PDU session and QoS flow identifier.

[0049] Another object of embodiments herein is to transmit packets on the mapped DRBs by the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] This method is illustrated in the accompanying drawings, where like reference numerals indicate corresponding parts throughout the drawings. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0051] Figure 1 The EPS bearer service architecture according to the prior art is shown;

[0052] Figure 2 is a diagram of a system for managing data communications in a wireless communication system according to an embodiment as disclosed herein;

[0053] Figure 3 shows various components of a gNodeB according to embodiments as disclosed herein;

[0054] Figure 4 shows various components of a UE according to embodiments as disclosed herein;

[0055] Figure 5is a flow diagram illustrating a method for managing data communication in a wireless communication network by a gNodeB, according to embodiments as disclosed herein;

[0056] Figure 6 is a flow diagram illustrating a method for managing data communication in a wireless communication network by a UE, according to embodiments as disclosed herein;

[0057] Figure 7 is a sequence diagram illustrating performing various operations for establishing data radio bearers in uplink (UL) and mapping packets of a QoS flow to a DRB, according to embodiments as disclosed herein;

[0058] Figure 8 is a sequence diagram illustrating performing various operations for establishing data radio bearers and mapping packets of a QoS flow to a DRB, according to embodiments as disclosed herein;

[0059] Figure 9 is a sequence diagram illustrating performing various operations for establishing data radio bearers in UL, according to embodiments as disclosed herein, wherein PM / QFI and PDU session identifier are included in a BSR;

[0060] Figure 10 is a sequence diagram illustrating performing various operations for establishing one or more DRBs, according to embodiments as disclosed herein;

[0061] Figure 11 is a sequence diagram illustrating performing various operations for establishing one or more DRBs in DL, according to embodiments as disclosed herein;

[0062] Figure 12 is a sequence diagram illustrating performing various operations for establishing one or more DRBs in UL, according to embodiments as disclosed herein;

[0063] Figure 13 is a sequence diagram illustrating performing various operations for DRB setup in DL, according to embodiments as disclosed herein; and

[0064] Figure 14 is a sequence diagram illustrating performing various operations for establishing data radio bearers in DL, according to embodiments as disclosed herein. DETAILED DESCRIPTION

[0065] The embodiments herein and their various features and advantageous details are more fully described with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments herein. In addition, the various embodiments described herein do not need to be mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise indicated, the term "or" as used herein refers to a non-exclusive or. The examples used herein are merely intended to help understand the manner in which the embodiments herein can be practiced, and further enable those skilled in the art to practice the embodiments herein. Therefore, the examples should not be interpreted as limiting the scope of the embodiments herein.

[0066] According to the tradition of this art, the embodiment can be described and illustrated according to the block that implements one or more desired functions.These blocks that can be referred to as managers, units or modules etc. in this article are physically implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits etc., and can be optionally driven by firmware and software.The circuit can be, for example, embedded in one or more semiconductor chips, or embedded on substrate support structures such as printed circuit boards.The circuits that make up the blocks can be implemented by dedicated hardware, or implemented by a processor (for example, one or more programmed microprocessors and associated circuits), or implemented by a combination of dedicated hardware for executing some functions of the block and a processor for executing other functions of the block. Without departing from the scope of this disclosure, each block of the embodiment can be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of this disclosure, the blocks of the embodiment can be physically combined into more complex blocks.

[0067] The terms "first" and "second" herein are used for labeling purposes only and may be used interchangeably without departing from the scope of the embodiments. It should be noted that the terms QoS packet marking or QoS marking or QoS ID or packet marking or QoS descriptor are used interchangeably throughout the specification. It should be noted that a QoS packet marking or QoS marking or QoS ID or packet marking or flow descriptor or QoS descriptor identifies a set of QoS parameters. The proposed method describes the present invention using packet marking (PM), however, the same applies to QoS packet marking or QoS marking or QoS ID or packet marking or flow descriptor.

[0068] Therefore, embodiments herein disclose a UE for managing data communications in a wireless communication network. The UE includes a processor and a memory, the memory being used to store a DRB configuration received from a gNodeB in the wireless communication network. A DRB management unit is connected to the memory and the processor. Furthermore, the DRB management unit is configured to determine a DRB for transmitting packets based on a QoS flow identifier and a PDU session associated with the packet, and to map the QoS flow identifier to a DRB for each established PDU session. The DRB management unit is configured to perform one of the following: if a list of one or more QoS flow identifiers associated with the DRB includes the QoS flow identifier of the packet and the DRB is associated with the PDU session of the packet, then mapping the packet to an established non-default DRB; and if none of the established non-default DRBs are associated with the PDU session and QoS flow identifier of the packet, then mapping the packet to a default DRB associated with the PDU session of the packet. Furthermore, the DRB management unit is configured to transmit the packet on the mapped DRB.

[0069] The proposed method can be used to reduce signaling overhead and provide greater QoS granularity by eliminating the EPS bearer concept in next-generation wireless communication systems (e.g., 5G wireless communication systems, etc.).

[0070] Unlike conventional methods and systems, the RAN provides mapping between DRBs and QoS flows. Multiple QoS flows can be mapped to the same DRB. In the UL, the UE maps QoS flows to DRBs based on the mapping received from the RAN. Furthermore, the UE receives packets from higher layers in the UL. The UE receives the PM associated with the packet along with the packet. Furthermore, if a DRB does not exist for the PM associated with the DRB, the UE maps the packet to a default DRB. Furthermore, the UE adds a packet marker to the header of the packet sent on the default DRB. Furthermore, the UE adds the packet marker to the packet header of the packet and transmits it to the gNB. The gNB adds the packet marker to the packet header of the packet and transmits it to the CN.

[0071] In the uplink, the UE marks uplink packets on the Uu interface with a QoS flow identifier for the purpose of marking forwarded packets to the CN, as described in 3GPP standard TR 38.804 and 3GPP standard TS 38.300.

[0072] Referring now to the drawings, and more particularly to Figures 2 to 14 , showing a preferred embodiment.

[0073] Figure 21 is a diagram of a system for managing data communications in a wireless communication system according to an embodiment as disclosed herein. In an embodiment, the system includes a UE 110, a gNodeB 120, and a network entity 160. The UE 110 may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0074] UE 110 may be, for example but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a wireless local loop (WLL) station, a universal serial bus (USB) dongle, a wireless router, etc.

[0075] gNodeB (GNB) 120 may also include or be referred to by those skilled in the art as 5GeNB, base station, base transceiver station, radio base station, access point, radio transceiver, eNB, or some other suitable terminology.

[0076] The next generation communication system supports a PDU connection service, i.e., a service that provides for the exchange of PDUs between the UE 110 and a data network (DN) (not shown). The PDU connection service is supported by PDU sessions established at a request from the UE 110. A PDU session is a connection between the UE 110 and the DN that provides the PDU connection service. Each PDU session supports a single PDU session type, i.e., supports the exchange of PDUs of a single type (e.g., IPv4, IPv6, Ethernet, etc.) requested by the UE 110 when establishing the PDU session. Non-access stratum (NAS) session management signaling exchanged between the UE 110 and a session management function (SMF) in the core network (CN) (not shown) is used to establish (at the request of the UE 110), modify (at the request of the UE 110 and the network), and release (at the request of the UE 110 and the network). In the next generation communication system, for data communication, the UE 110 can establish one or more PDU sessions with the same DN or different DNs. Each PDU session is identified by a PDU session identifier.

[0077] In the non-roaming case, packets of a PDU session in the uplink (UL) direction traverse from the UE 110 to the RAN (or gNodeB) 120 via the radio interface, traverse from the RAN (or gNodeB) 120 to the user plane function (UPF) via the N3 interface, and traverse from the UPF to the DN via the N6 interface. In the roaming case, packets of a PDU session in the UL traverse from the UE 110 to the RAN (or gNodeB) 120 via the radio interface, traverse from the RAN (or gNodeB) 120 to the UPF in the visited PLMN via the N3 interface, traverse from the UPF in the visited PLMN to the UPF in the home PLMN via the N9 interface, and traverse from the UPF in the home PLMN to the DN via the N6 interface. In a non-roaming situation, packets of a PDU session in the downlink (DL) traverse from the DN to the UPF via the N6 interface, traverse from the UPF to the RAN (or gNodeB) 120 via the N3 interface, and traverse from the RAN (or gNodeB) 120 to the UE 110. In a roaming situation, packets of a PDU session in the DL traverse from the DN to the UPF in the home PLMN via the N6 interface, traverse from the UPF in the home PLMN to the visited PLMN via the N9 interface, traverse from the UPF in the visited PLMN to the RAN (or gNodeB) 120 via the N3 interface, and traverse from the RAN (or gNodeB) 120 to the UE 110.

[0078] Furthermore, packets within a PDU session can require different QoS treatments. A QoS flow is the finest granularity for differentiating QoS for a PDU session. Packets within a PDU session that require the same QoS treatment constitute a QoS flow. Several QoS flows can exist per PDU session. A QoS flow identifier (ID) (or QoS marking, QoS ID, QoS descriptor, or packet marking) is used to identify a QoS flow. A QoS flow ID is unique within a PDU session. User plane services within a PDU session with the same QoS flow ID receive the same service forwarding treatment (e.g., scheduling, admission control, etc.). Each QoS flow is mapped to a set of QoS parameters (e.g., allocation and retention priority, guaranteed bit rate, maximum bit rate, etc.). The QoS flow identifier is included in each packet of a PDU session exchanged between the RAN (or gNodeB) 120 and the UPF. Packet marking (i.e., associating packets transmitted over the N3 interface with a QoS flow identifier) ​​is performed by the UPF in the DL. Packet marking (i.e., associating packets transmitted over the N3 interface with a QoS flow identifier) ​​is performed by the RAN (or gNodeB) 120 in the UL. For each PDU session, a single tunnel is established between the UPF and the RAN (or gNodeB) 120 for exchanging packets associated with different QoS flows of the PDU session.

[0079] In order to exchange packets of a PDU session, a data radio bearer (DRB) needs to be established between UE 110 and RAN (or gNodeB) 120. Various methods for establishing a DRB and mapping packets of a QoS flow to the DRB are further discussed.

[0080] In an embodiment, the RAN (or gNodeB) 120 is configured to receive a plurality of packets for at least one QoS flow from a network entity 160 (i.e., a UPF in the core network or a UP entity in the core network). A QoS flow ID (QFI) associated with the at least one QoS flow is received in a header of each packet. Furthermore, the RAN (or gNodeB) 120 is configured to map each received packet for the at least one QoS flow to a DRB. The at least one QoS flow is mapped to the DRB based on the QFI associated with the at least one QoS flow.

[0081] In an embodiment, the plurality of packets for the at least one QoS flow are received by gNodeB 120 from network entity 160 by receiving packets over at least one PDU tunnel between gNodeB 120 and network entity 160. The PDU tunnel is used separately to receive the plurality of packets for the at least one QoS flow for each PDU session.

[0082] In an embodiment, if the list of at least one QoS flow identifier associated with an established DRB includes the QoS flow identifier of the received packet and the established DRB is associated with the PDU session of the received packet, then each received packet of at least one QoS flow from the network entity 160 is mapped to the DRB by the gNodeB 120 by mapping the received packet to the established DRB.

[0083] In an embodiment, each received packet of a QoS flow from the network entity 160 is mapped by the gNodeB 120 to a DRB in the following manner: if no established DRB is associated with the PDU session and QoS flow of the received packet, then a new DRB is established; a signaling message including a DRB configuration for the new DRB is transmitted to the UE 110, wherein the DRB configuration includes a PDU session identifier associated with the DRB and one or more of a list of QoS flow identifiers of one or more QoS flows; and the received packet is mapped to the newly established DRB.

[0084] In an embodiment, each received packet of a QoS flow from the network entity 160 is mapped to a DRB in the following manner: if none of the established DRBs for the PDU session of the received packet is associated with the QoS flow of the received packet, then updating the configuration of the established DRB associated with the PDU session of the received packet, wherein the QoS flow identifier of the received packet is added to the QoS flow identifier list of the updated DRB; transmitting a signaling message including the DRB configuration of the updated DRB to the UE 110, wherein the DRB configuration includes at least one of a list of at least one of the PDU session identifier associated with the DRB and the QoS flow identifier of the QoS flow; and mapping the received packet to the updated DRB.

[0085] In an embodiment, a QoS flow is mapped to only one DRB.

[0086] In an embodiment, a DRB is mapped to at least one QoS flow of the same PDU session.

[0087] In an embodiment, each of the DRBs defines a packet forwarding process on a radio interface for data exchange between a UE 110 and a gNodeB 120 in a wireless communication network.

[0088] In an embodiment, the RAN (or gNodeB) 120 is configured to receive a plurality of packets for at least one QoS flow from another gNodeB. At least one of a QFI associated with each packet and a PDU session identifier of a PDU session is also received by the RAN (or gNodeB) 120 from the other gNodeB. Furthermore, the RAN (or gNodeB) 120 is configured to map each received packet for the at least one QoS flow to a DRB. The at least one QoS flow is mapped to the DRB based on the QFI associated with the at least one QoS flow. Furthermore, the UE 110 is configured to determine a DRB for transmitting the packet based on the QoS flow identifier and the PDU session associated with the packet, and to map the QoS flow identifier to a DRB for each established PDU session. Furthermore, the UE is configured to perform one of the following: if the list of at least one QoS flow identifier among the QoS flow identifiers associated with the DRB includes the QoS flow identifier of the packet and the DRB is associated with the PDU session of the packet, then mapping the packet to an established non-default DRB; and if no established non-default DRB is associated with the PDU session of the packet and the QoS flow identifier, then mapping the packet to a default DRB associated with the PDU session of the packet. Furthermore, the UE 110 is configured to transmit the packet on the mapped DRB.

[0089] In an embodiment, UE 110 receives a mapping of QoS flow identifiers to DRBs for each established PDU session from gNodeB 120 in a signaling message.

[0090] In an embodiment, UE 110 receives a list of at least one of a PDU session identifier and a QoS flow identifier associated with each DRB from gNodeB 120 in a signaling message.

[0091] In an embodiment, UE 110 receives a list of at least one of the QoS flow identifiers associated with each DRB from gNodeB 120 in a signaling message.

[0092] In an embodiment, UE 110 receives a default DRB configuration associated with the PDU session from gNodeB 120 in a signaling message.

[0093] In an embodiment, after RRC connection establishment, UE 110 receives the configuration of a default DRB associated with the PDU session from gNodeB 120 in a signaling message.

[0094] In an embodiment, upon receiving a packet on the default DRB, gNodeB 120 is further configured to establish a new DRB for the QoS flow identifier and the PDU session identifier received in the packet header of the packet received on the default DRB. In addition, UE 110 is configured to transmit a signaling message including a DRB configuration for the new DRB, wherein the DRB configuration includes one or more of a list of QoS flow identifiers of the one or more QoS flows and a PDU session identifier associated with the DRB.

[0095] In an embodiment, upon receiving a packet on the default DRB, gNodeB 120 is configured to establish a new DRB for the QoS flow identifier received in the packet header of the packet received on the default DRB. In addition, gNodeB 120 is configured to transmit a signaling message including a DRB configuration for the new DRB. The DRB configuration includes a list of one or more QoS flow identifiers for the QoS flows associated with the DRB.

[0096] In an embodiment, upon receiving a packet on the default DRB, gNodeB 120 is further configured to update an established DRB corresponding to the PDU session identifier received in a packet header of the packet received on the default DRB. The QoS flow identifier of the packet received on the default DRB is added to the list of QoS flow identifiers of the updated DRB. Furthermore, gNodeB 120 is configured to transmit a signaling message including a DRB configuration for the updated DRB, wherein the DRB configuration includes one or more of the PDU session identifier associated with the DRB and the list of QoS flow identifiers of the one or more QoS flows.

[0097] In an embodiment, upon receiving a packet on a default DRB, gNodeB 120 is configured to update the already established DRB. The QoS flow identifier of the packet received on the default DRB is added to the list of QoS flow identifiers of the updated DRB. Furthermore, gNodeB 120 is configured to transmit a signaling message including a DRB configuration for the updated DRB. The DRB configuration includes a list of one or more QoS flow identifiers for QoS flows associated with the DRB.

[0098] Figure 2 This is a limited diagram of a system, but it should be understood that other embodiments are not limited thereto. Furthermore, the system may include any number of hardware or software components that communicate with each other. Furthermore, labels are used for illustrative purposes only and do not limit the scope of the present invention. For example, a component may be, but is not limited to, an object, an executable process, an execution thread, a program, a computer, or a process running on a controller or processor.

[0099] Figure 3 1 shows various components of a gNodeB 120 according to an embodiment as disclosed herein. In an embodiment, the gNodeB 120 includes a DRB management unit 121, a communication unit 122, a memory 123, and a processor 124. The processor 124 is in communication with the DRB management unit 121, the communication unit 122, and the memory 123. The DRB management unit 121 is coupled to the memory 123 and the processor 124. In an embodiment, the DRB management unit 121 is configured to receive a plurality of packets of at least one QoS flow from the network entity 160. (Various processes for receiving a plurality of packets of at least one QoS flow from the network entity 160 are described in Figures 7 to 14 After receiving a plurality of packets of at least one QoS flow from the network entity 160, the DRB management unit 121 is configured to map each received packet of the at least one QoS flow to a DRB. (The various processes for mapping each received packet of the at least one QoS flow to a DRB are described in Figures 7 to 14In an embodiment, the DRB management unit 121 is configured to establish a DRB based on information received from the network entity 160 and / or the UE 110 and provide DRB-to-QoS flow mapping information to the UE 110. (The various processes for establishing a DRB and providing DRB-to-QoS flow mapping information to the UE 110 are described in Figures 7 to 14 (see instructions in the text).

[0100] The communication unit 122 is configured to communicate with internal units of the gNodeB 120. In addition, the communication unit 122 is configured to communicate with external units of the system.

[0101] In an embodiment, memory 123 is configured to store DRB configurations. Memory 123 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or in the form of an electrically programmable memory (EPROM) or an electrically erasable and programmable (EEPROM) memory. Additionally, in some examples, memory 123 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as meaning that memory 123 is non-removable. In some examples, memory 123 may be configured to store a larger amount of information than memory. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or cache memory).

[0102] although Figure 3 The hardware components of gNodeB 120 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, gNodeB 120 may include fewer or more components. Furthermore, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present invention. One or more components may be combined to perform the same or substantially similar functions to manage data communications in a wireless communication network.

[0103] Figure 4 Various components of a UE 110 are shown according to an embodiment as disclosed herein. In an embodiment, the UE 110 includes a DRB management unit 111, a communication unit 112, a memory 113, and a processor 114. The processor 114 is in communication with the DRB management unit 111, the communication unit 112, and the memory 113.

[0104] In an embodiment, the DRB management unit 111 is coupled to the memory 113 and the processor 114. Furthermore, the DRB management unit 111 is configured to determine a DRB for transmitting the packet based on the QoS flow identifier and the PDU session associated with the packet, and to map the QoS flow identifier to a DRB for each established PDU session. Furthermore, the DRB management unit 111 is configured to perform one of: mapping the packet to an established non-default DRB if the list of at least one of the QoS flow identifiers associated with the DRBs includes the QoS flow identifier of the packet and the DRB is associated with the PDU session of the packet; and mapping the packet to a default DRB associated with the PDU session of the packet if none of the established non-default DRBs are associated with the PDU session of the packet and the QoS flow identifier. Furthermore, the DRB management unit 111 is configured to transmit the packet on the mapped DRB.

[0105] Furthermore, the communication unit 112 is configured to communicate with internal units of the UE 110. Furthermore, the communication unit 112 is configured to communicate with external units of the system.

[0106] In an embodiment, memory 113 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of electrically programmable memory (EPROM) or electrically erasable and programmable (EEPROM) memory. In addition, in some examples, memory 113 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as meaning that memory 113 is non-removable. In some examples, memory 113 may be configured to store a larger amount of information than memory. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or cache memory).

[0107] although Figure 4 The hardware components of UE 110 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, UE 110 may include fewer or more components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present invention. One or more components may be combined to perform the same or substantially similar functions to manage data communications in a wireless communication network.

[0108] Figure 5 is a flow chart 500 illustrating a method for managing data communications in a wireless communication network by a gNodeB 120 according to embodiments as disclosed herein. The operations of 502 and 504 are performed by the DRB management unit 121 .

[0109] At 502, the method includes receiving a plurality of packets for at least one QoS flow from a network entity 160. An identifier associated with the at least one QoS flow is included in a header of each packet by the network entity 160. A plurality of packets for at least one QoS flow for at least one PDU session are received from the network entity 160 via at least one tunnel established between the gNodeB 120 and the network entity 160. The tunnel established between the gNodeB 120 and the network entity 160 is for the PDU session. In one embodiment, the plurality of packets for the at least one QoS flow are received from another gNodeB. At least one of a QFI associated with each packet and a PDU session identifier for the PDU session is also received from the other gNodeB. At 504, the method includes mapping each received packet for the at least one QoS flow for the PDU session to a DRB. The at least one QoS flow for the PDU session is mapped to the DRB based on the ID associated with the at least one QoS flow.

[0110] If the list of at least one QoS flow identifier associated with an established DRB includes the QoS flow identifier of the received packet and the established DRB is associated with the PDU session of the received packet, then the received packet of at least one QoS flow is mapped to the established DRB.

[0111] Received packets of at least one QoS flow are mapped to a DRB in the following manner: if no established DRB is associated with the PDU session and QoS flow of the received packets, then a new DRB is established; a signaling message including a DRB configuration of the new DRB is transmitted to UE 110, wherein the DRB configuration includes a PDU session identifier associated with the DRB and one or more of a list of QoS flow identifiers of one or more QoS flows; and the received packets are mapped to the newly established DRB.

[0112] Received packets of at least one QoS flow are mapped to a DRB in the following manner: if none of the established DRBs for the PDU session of the received packets is associated with the QoS flow of the received packets, then updating the configuration of the established DRB associated with the PDU session of the received packets, wherein the QoS flow identifier of the received packets is added to the QoS flow identifier list of the updated DRB; transmitting a signaling message including the DRB configuration of the updated DRB to UE110, wherein the DRB configuration includes at least one of the lists of at least one of the PDU session identifier associated with the DRB and the QoS flow identifier of the QoS flow; and mapping the received packets to the updated DRB.

[0113] Each QoS flow is mapped to only one DRB. Each DRB is mapped to at least one QoS flow of the same PDU session.

[0114] In an embodiment, mapping each received packet of at least one QoS flow of a PDU session to a DRB includes: establishing a new DRB if no established DRB is associated with the PDU session and QoS flow of the received packet; transmitting a signaling message including a DRB configuration for the new DRB to UE 110, wherein the DRB configuration includes a PDU session identifier associated with the DRB and one or more of a list of QoS flow identifiers of one or more QoS flows; and mapping the received packet to the newly established DRB.

[0115] In an embodiment, mapping each received packet of at least one QoS flow of a PDU session to a DRB includes: if none of the established DRBs for the PDU session of the received packet is associated with the QoS flow of the received packet, then updating the configuration of the established DRB associated with the PDU session of the received packet, wherein the QoS flow identifier of the received packet is added to the QoS flow identifier list of the updated DRB; transmitting a signaling message including the DRB configuration of the updated DRB to UE 110, wherein the DRB configuration includes at least one of a list of at least one of the PDU session identifier associated with the DRB and the QoS flow identifier of the QoS flow; and mapping the received packet to the updated DRB.

[0116] Figure 6 6 is a flow chart 600 illustrating a method for managing data communications in a wireless communication network by a UE 110 according to embodiments as disclosed herein. The operations of 602 , 604 a , 604 b , and 606 are performed by the DRB management unit 111 .

[0117] At 602, the method includes determining a DRB for transmitting the packet based on a QoS flow identifier and a PDU session associated with the packet, and mapping the QoS flow identifier to a DRB for each established PDU session. At 604a, the method includes mapping the packet to an established non-default DRB if the list of at least one of the QoS flow identifiers associated with the DRBs includes the QoS flow identifier of the packet and the DRB is associated with the PDU session of the packet. At 604b, the method includes mapping the packet to a default DRB associated with the PDU session of the packet if none of the established non-default DRBs are associated with the PDU session of the packet and the QoS flow identifier. At 606, the method includes transmitting the packet on the mapped DRB.

[0118] In an embodiment, UE 110 receives a mapping of QoS flow identifiers to DRBs for each established PDU session from gNodeB 120 in a signaling message (eg, an RRC signaling message).

[0119] In an embodiment, the UE 110 receives, from the gNodeB 120 in a signaling message, a list of at least one of a PDU session identifier and a QoS flow identifier associated with each DRB.

[0120] In an embodiment, the UE 110 receives, from the gNodeB 120 in a signaling message, a list of at least one of a QoS flow identifier associated with each DRB.

[0121] In an embodiment, the UE 110 receives, in a RRC signaling message, a default DRB configuration associated with a PDU session.

[0122] In an embodiment, the UE 110 includes at least one of a QoS flow identifier and a PDU session identifier in a packet header of a packet transmitted on the default DRB.

[0123] The various actions, acts, blocks, steps, etc. in flowcharts 500 and 600 can be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions, acts, blocks, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the application.

[0124] Figure 7 is a sequence diagram illustrating performance of various operations for establishing DRBs and mapping UL packets to DRBs, in accordance with embodiments as disclosed herein.

[0125] In an embodiment, when a PDU session is established, a new QoS flow is established, or a radio connection is established, the QoS parameters associated with the QoS flow are provided to the RAN (or gNodeB) 120 as a QoS profile. The QoS parameters may also be pre-configured in the RAN 120. In the RAN 120, a DRB defines packet processing on the radio interface (i.e., the Uu interface). DRBs utilize the same packet forwarding processing to serve packets. Separate DRBs may be established for QoS flows requiring different packet forwarding processing. The RAN (or gNodeB) 120 is aware of the mapping between each QoS flow and the associated QoS parameters (or QoS profile) and determines the radio configuration for the corresponding DRB accordingly. In the DL, the RAN (or gNodeB) 120 maps the QoS flow to the DRB based on the packet tag (i.e., QoS flow ID) and the associated QoS profile. For the UL, the RAN (or gNodeB) 120 provides the QoS flow to DRB mapping in an RRC signaling message. This mapping information is used by the UE 110 to map the packets to be transmitted to one of the established DRBs. One DRB can be mapped to multiple QoS flows. For each DRB configured, the RAN (or gNodeB) 120 provides a list of one or more QoS flow identifiers (QFIs) and a PDU session identifier. In a system where only one PDU session can be established for each UE 110, the RAN (or gNodeB) 120 may not provide a PDU session identifier for each configured DRB. The QoS parameters related to radio-level QoS (e.g., packet error rate, latency, data rate, etc.) can be the same for multiple QoS flows, and therefore multiple QoS flows of the same PDU session can be mapped to the same DRB. The QoS flows of a PDU session are not mapped to more than one DRB. A QoS flow of one PDU session and another QoS flow of another PDU session can have the same QoS flow ID, but these are mapped to different DRBs. In other words, QoS flows of different PDU sessions are not mapped to the same DRB. If QoS flows for different PDU sessions are mapped to the same DRB, then upon receiving a packet from UE 110 on this DRB, gNodeB 120 will not be able to identify the PDU session associated with this packet and will therefore not be able to identify the tunnel through which this packet is sent to UPF 170. It should be noted that the tunnel between gNodeB 120 and UPF 170 is different for each PDU session.

[0126] In the proposed method, the RAN (or gNodeB) 120 first establishes one or more DRBs and provides the configuration of each established DRB to the UE 110 in an RRC signaling message after the RRC connection is established between the UE 110 and the RAN (or gNodeB) 120. Each established DRB is a default DRB associated with a PDU session or a non-default DRB associated with a PDU session. One default DRB is established for each PDU session. Multiple non-default DRBs can be associated with a PDU session. For each non-default DRB, a list of one or more QoS flow identifiers is provided by the gNodeB 120. In the DRB configuration included in the RRC signaling, the RAN (or gNodeB) 120 can indicate whether it is a default DRB or not.

[0127] In the UL, the access stratum (i.e., AS) in the UE 110 receives (702) the packet to be transmitted and the associated PM / QFI and the PDU session identifier from a higher layer (e.g., the NAS layer or the application layer in the UE 110). In a system in which only one PDU session can be established for each UE 110, the access stratum (i.e., AS) in the UE 110 receives the packet to be transmitted and the associated PM / QFI from a higher layer (e.g., the NAS layer or the application layer in the UE 110).

[0128] In the proposed method, the UE 110 checks (704) whether a DRB has been established at least for the QoS flow (identified by the PM / QFI) and the PDU session associated with the received packet. If yes, then the UE 110 maps the packet to the DRB and transmits the packet on the mapped DRB. If no, then the UE 110 maps the packet to the default DRB of the PDU session associated with the packet and transmits (706) the packet using the default DRB of the PDU session associated with the packet.

[0129] In addition, the UE 110 sends (708) the packet and the associated PM / QFI (i.e., PM_1 / QFI_1) to the RAN (or gNodeB) 120 over the air.

[0130] The PM / QFI is included in the packet sent on the default DRB. The PM / QFI can be included in the packet header (e.g., it can be included in the header of the service data adaptation protocol (SDAP)).

[0131] RAN (or gNodeB) 120 sends (710) the UL packet with packet tag PM_1 / QFI_1 to UPF 170. UPF 170 sends (712) the UL IP packet to DN 180. In addition, if there is no DRB for processing the packet with packet tag PM_1 / QFI_1, 110 RAN (or gNodeB) 120 determines (714) to establish a DRB setup.

[0132] Upon receiving a packet with a PM / QFI on the default DRB, the RAN (or gNodeB) 120 may add the QoS flow identified by the PM / QFI to an existing (i.e., already established) DRB or add a new DRB for the QoS flow identified by the PM / QFI. The RAN (or gNodeB) 120 sends (716) the updated DRB configuration to the UE 110. If adding a new DRB, the UE 110 creates (718) a new DRB corresponding to the new configuration and PM / QFI included in the DRB configuration message. In response, the UE 110 may send a DRB configuration complete message. If adding a new DRB configuration for the PM / QFI, then after receiving the DRB configuration complete message, the RAN (or gNodeB) 120 creates (720) the DRB using the DRB configuration.

[0133] After receiving a packet from UE 110 via the DRB, RAN (or gNodeB) 120 identifies the PM / QFI and PDU session identifier of the received packet based on the mapping between the DRB, the PM / QFI, and the PDU session identifier. RAN (or gNodeB) 120 indicates the PM / QFI of the packet to UPF 170 (710 or 724) by adding the PM / QFI to the header and simultaneously transmits the packet to UPF 170. The packet is transmitted to UPF 170 over the tunnel associated with the packet's PDU session. UPF 170 transmits the UL IP packet (726) to DN 180.

[0134] In an embodiment, packets on the default DRB may be transmitted on a first-come, first-served basis or may be prioritized based on QoS marking.

[0135] In an embodiment, the PM / QFI and PDU session identifier may be included in the BSR. Figure 9. When the PM / QFI and PDU session identifier are received in the BSR, if there is no DRB for this PM / QFI and PDU session identifier, the RAN (or gNodeB) 120 starts DRB setup. The RAN (or gNodeB) 120 may map the PM / QFI to an existing DRB or add a new DRB for this PM / QFI and PDU session identifier. The RAN (or gNodeB) 120 sends the updated DRB configuration to the UE 110. If a new DRB is added, the UE 110 creates a new DRB corresponding to the new configuration and PM / QFI included in the DRB configuration message. In response, the UE 110 may send a DRB configuration complete message. If a new DRB configuration is added for the PM / QFI, after receiving the DRB configuration complete message, the RAN (or gNodeB) 120 creates the DRB using the DRB configuration.

[0136] In one embodiment of the proposed method, instead of sending packets on a default DRB, UE 110 may create a new DRB and configure the new DRB using a default configuration. The default configuration may be predefined or provided by RAN (or gNodeB) 120 in an RRC message. In addition, UE 110 may use an unused LCID for this new DRB. The PM / QFI and, optionally, the PDU session identifier may be included in packets transmitted over this new DRB. Upon receiving a packet for an LCID and / or PM / QFI and / or PDU session identifier (which has no associated DRB), RAN (or gNodeB) 120 may map the PM / QFI to an existing DRB or add a new DRB for this PM / QFI. In addition, RAN (or gNodeB) 120 sends the updated DRB configuration to UE 110. If a new DRB is added, UE 110 updates / creates a new DRB corresponding to the new configuration and PM / QFI included in the DRB configuration message. In response, UE 110 may send a DRB configuration complete message. If a new DRB configuration is added for PM / QFI, after receiving the DRB configuration complete message, the RAN (or gNodeB) 120 creates a DRB using the DRB configuration.

[0137] like Figure 8As shown, a PDU session and DRBs (including a default DRB) are established (802) between UE 110, gNodeB 120, UP entity 190, and CP entity 200. The UE AS receives (804) a packet with a new QFI from the UE NAS. Furthermore, UE 110 uses (806) the packet's QFI to map it to a DRB. If no QFI-to-DRB mapping exists in the AS mapping table for this PDU session, the packet is assigned to the default DRB for this PDU session.

[0138] Furthermore, UE 110 sends (808) the packet on the default DRB. If SDAP has been configured for this DRB, UE 110 includes the QFI in the SDAP header. An SDAP entity is created for each PDU session.

[0139] Furthermore, the gNodeB 120 transmits (810) an UL packet over NG-U and includes a corresponding QFI.

[0140] In addition, gNodeB 120 optionally sets (812) a DRB for the new QoS flow. User plane data is exchanged (814) between UE 110 and gNodeB 120 over the radio interface, and the QFI may be included in the packet header. User plane data is exchanged (814) between gNodeB 120 and UP entity 190 over the PDU tunnel, and the QFI is included in the packet header.

[0141] like Figure 9 As shown, UE 110 receives an UL packet with packet tag PM_1 / QFI_1 for a PDU session. Furthermore, UE 110 determines (904) that there is no DRB for processing the packet with packet tag PM_1 / QFI_1. Furthermore, UE 110 sends (906) the packet on a default DRB.

[0142] In addition, UE 110 sends (908) BSR: PM_1 / QFI_1 to RAN (or gNodeB) 120. In addition, RAN (or gNodeB) 120 determines that there is no DRB for processing the packet with packet tag PM_1 / QFI_1, and then RAN (or gNodeB) 120 sets (910) the DRB. The DRB setting includes (912) DRB configuration->PM_1 / QFI_1. In addition, UE 110 creates (914) a DRB using the DRB configuration corresponding to PM_1 / QFI_1, and RAN (or gNodeB) 120 creates (916) a DRB using the DRB configuration corresponding to PM_1 / QFI_1. UE 110 sends (918) a wireless packet to RAN (or gNodeB) 120. RAN (or gNodeB) 120 sends (920) the UL packet with packet tag PM_1 / QFI_1 to UPF 170. Furthermore, UPF 170 sends (922) the ULIP packet to DN 180.

[0143] Figure 10 is a sequence diagram illustrating various operations performed for establishing one or more DRBs and mapping packets of a QoS flow to the DRBs according to an embodiment as disclosed herein.

[0144] In an embodiment, RAN (or gNodeB) 120 obtains a list of authorized QoS flows (identified by packet marking, i.e., PM or QoS marking or QoS ID or QoS rule or flow descriptor or QoS descriptor or QoS flow ID (QFI)) for UE 110. After RAN 120 receives an RRC connection request from UE 110, RAN (or gNodeB) 120 may obtain the authorized PM / QFI list for UE 110 based on the CP function in the CN. Alternatively, UE 110 may send the authorized PM / QFI list to RAN (or gNodeB) 120. In addition, UE 110 may be pre-configured with the authorized PM / QFI list, or UE 110 may obtain the authorized PM / QFI list based on the CP function in the CN.

[0145] When a PDU session is established or a new QoS flow is established or when a radio connection is established, the QoS parameters of the QoS flow are also provided to the RAN (or gNodeB) 120 as a QoS profile. The QoS parameters can also be pre-configured in the RAN. In the RAN 120, a DRB defines packet handling over the radio interface (i.e., Uu). DRBs are served with the same packet forwarding treatment. Separate DRBs can be established for QoS flows that require different packet forwarding treatment. The RAN (or gNodeB) 120 is aware of the mapping between each QoS flow and the associated QoS parameters (or QoS profile) and decides accordingly the radio configuration for the corresponding data radio bearer. In the downlink, the RAN (or gNodeB) 120 maps QoS flows to DRBs based on packet marking (i.e., QoS flow ID) and associated QoS profile. For the uplink, the RAN (or gNodeB) provides the mapping of QoS flows to DRBs in RRC signaling messages. One DRB can be mapped to multiple QoS flows. For each DRB configured, the RAN (or gNodeB) 120 provides a list of one or more QFIs and a PDU session identifier. In systems where only one PDU session can be established per UE 110, the RAN (or gNodeB) 120 can not provide a PDU session identifier for each configured DRB. QoS parameters related to radio level QoS (e.g., packet error rate, latency, data rate, etc.) can be the same for multiple QoS flows and thus multiple QoS flows of the same PDU session can be mapped to the same DRB. QoS flows of a PDU session are not mapped to more than one DRB. A QoS flow of one PDU session and another QoS flow of another PDU session can have the same QoS flow identifier, but these are mapped to different DRBs.

[0146] In other words, QoS flows of different PDU sessions are not mapped to the same DRB. If QoS flows of different PDU sessions are mapped to the same DRB, then upon receiving a packet from the UE 110 on that DRB, the gNB 120 will not be able to identify the PDU session associated with this packet and thus will not be able to identify the tunnel via which this packet should be sent to the UPF. It should be noted that for each PDU session, the tunnel is different.

[0147] In an embodiment, the RAN (or gNodeB) 120 provides one or more DRB configurations to the UE 110 in an RRC signaling message (e.g., an RRC connection reconfiguration message). The DRB configuration includes an L2 configuration similar to the DRB configuration in the existing system. For example, it may include a Service Data Adaptation Protocol (SDAP) configuration, a Packet Data Convergence Protocol (PDCP) configuration, a Radio Link Control (RLC) configuration, a MAC configuration, etc. Each DRB configuration is mapped to one or more PM / QFIs. For each configured DRB, the RAN (or gNodeB) 120 provides a list of one or more QFIs and a PDU session identifier. The RAN (or gNodeB) 120 also indicates whether the DRB corresponding to each DRB configuration is a UL DRB, a DL DRB, or a bidirectional DRB. Regardless of whether one or more QoS flows are mapped to the same DRB configuration, the UE 110 and the RAN (or gNodeB) 120 create a DRB for each DRB configuration. The created DRB is associated with one or more QoS flows listed in the DRB configuration. The DRB processes the grouping of one or more PM / QFIs associated with the DRB.

[0148] In an embodiment, the RAN (or gNodeB) 120 provides one or more DRB configurations to the UE 110 in an RRC signaling message (e.g., an RRC Connection Reconfiguration message). Each DRB configuration maps to one or more PM / QFIs. The RAN (or gNodeB) 120 also indicates whether the DRB corresponding to each data DRB configuration is a UL DRB, a DL DRB, or a bidirectional DRB. The UE 110 and the RAN (or gNodeB) 120 create one DRB for each DRB configuration. However, if the DRB configuration maps to multiple PM / QFIs, then the UE 110 creates a separate data DRB for each PM / QFI using the same DRB configuration. So basically in this embodiment, the mapping of one DRB configuration to multiple PM / QFIs means that the DRBs for these PM / QFIs have the same configuration, but the packets for these PM / QFIs are mapped to different DRBs and therefore to different queues. The created DRB is associated with one PM / QFI. The DRB processes packets of the QoS flow (identified by the PM / QFI) associated with the DRB.

[0149] In the UL, the access stratum (i.e., AS) in UE 110 receives a packet to be transmitted from a higher layer (i.e., the NAS layer or the application layer), along with the associated PM / QFI and PDU session identifier (required only when multiple PDU sessions are established for UE 110). UE 110 maps the packet to the appropriate DRB based on a) the packet's PM / QFI and, optionally, the PDU session identifier, and b) the mapping between the DRB and the PM / QFI and, optionally, the PDU session identifier. After receiving the packet from UE 110 via the DRB, RAN (or gNodeB) 120 identifies the PM / QFI and, optionally, the PDU session identifier of the received packet based on the mapping between the DRB and the PM / QFI and, optionally, the PDU session identifier. RAN (or gNodeB) 120 indicates the PM / QFI of the packet to UPF 170 by adding the PM / QFI to the header and transmitting the packet to UPF 170. The packet is transmitted to UPF 170 over the tunnel associated with the packet's PDU session.

[0150] Furthermore, whenever the PM / QFI granted to the UE changes (either adding a new QoS flow or releasing an existing QoS flow), the RAN (or gNodeB) 120 may provide the updated DRB configuration to the UE 110 in an RRC signaling message.

[0151] In one embodiment, the DRB configuration may be provided by the RAN (or gNodeB) 120. The mapping between PM / QFI, PDU session identifier, and DRB configuration may be provided to the UE 110 by the CP function in the CN.

[0152] In one embodiment, in addition to PM / QFI, a priority level can also be associated with a packet. Within the same DRB, packets of different priorities can be processed differently. Packets can be transmitted in order of priority. The packet queues within a DRB can be managed as priority queues. Alternatively, multiple queues can be maintained for packets of different priorities.

[0153] like Figure 10As shown, a list of authorized QoS flows and associated QoS parameters is provided (1002) between the gNodeB 120 and the CN-CP entity. In addition, a DRB configuration setup is provided (1004) between the UE 110 and the gNodeB 120, the DRB configuration setup including a list of one or more DRBs; for each DRB, a list of one or more QoS flows (QFIs) and a PDU session ID. In addition, the UE 110 creates (1006) a DRB based on the received DRB configuration. The gNodeB 120 creates (1008) a DRB based on the sent DRB configuration. For each DRB, the UE 110 stores (1010) a list of associated QoS flows and, optionally, a PDU session ID. In addition, the gNB 120 maps (1012) the received DL packet to the DRB based on the QFI of the received packet. Furthermore, UE 110 maps (1014) the UL packet to the DRB using a) the QFI of the UL packet and optionally the PDU session id and b) the mapping of DRB to QoS flow and optionally PDU session identifier.

[0154] Figure 11 is a sequence diagram for performing various operations for establishing one or more DRBs in the DL according to an embodiment as disclosed herein, and Figure 12 is a sequence diagram illustrating various operations performed for establishing one or more DRBs in the UL according to embodiments as disclosed herein.

[0155] In an embodiment, the RAN (or gNodeB) 120 provides a mapping between one or more DRB configurations and QoS flows (identified by QoS flow identifiers / PMs) to the UE 110 in an RRC signaling message (e.g., an RRC connection reconfiguration message). The DRB configuration includes an L2 configuration similar to the DRB configuration provided for each DRB in existing systems. For example, it may include an SDAP configuration, a PDCP configuration, an RLC configuration, a MAC configuration, etc. Each DRB is mapped to one or more PMs / QFIs. For each configured DRB, the RAN (or gNB) 120 provides a list of one or more QFIs and optionally a PDU session identifier. QoS flows of the same PDU session may be mapped to the same DRB. QoS flows of a PDU session are not mapped to more than one DRB. A QoS flow of one PDU session and another QoS flow of another PDU session may have the same QoS flow ID, but these are mapped to different DRBs. In other words, QoS flows of different PDU sessions are not mapped to the same DRB.

[0156] Furthermore, if QoS flows for different PDU sessions are mapped to the same DRB, then upon receiving a packet from UE 110 on that DRB, gNB 120 will not be able to identify the PDU session associated with that packet and will therefore not be able to identify the tunnel via which the packet should be sent to UPF 170. Note that the tunnel is different for each PDU session. RAN 120 also indicates whether each DRB is a UL DRB, a DL DRB, or a bidirectional DRB. The Logical Channel ID may or may not be present in the DRB configuration. However, the LCG ID may be included. In one embodiment, if the LCID is included, the PM / QFI and PDU Session ID may not be included for DL-only DRBs.

[0157] The PM / QFI for which DRB configuration is not provided may be the QFI / PM authorized to UE 110. When RAN 120 receives an RRC Connection Request from UE 110, RAN (or gNodeB) 120 may obtain the PM / QFI. RAN (or gNodeB) 120 may obtain the PM / QFI based on the CP function in the CN. Alternatively, UE 110 may send the PM / QFI to RAN (or gNodeB) 120. Furthermore, UE 110 may be pre-configured with the authorized QFI / PM, or UE 110 may obtain the PM / QFI based on the CP function in the CN.

[0158] When establishing a PDU session or a new QoS flow, or when establishing a radio connection, the QoS parameters for the QoS flow are also provided to the RAN (or gNodeB) 120 as a QoS profile. The QoS parameters can also be pre-configured in the RAN 120. The RAN (or gNodeB) 120 knows the mapping between each QFI / PM and the associated QoS parameters and decides the radio configuration for the corresponding DRB accordingly. The QoS parameters related to radio-level QoS (e.g., packet error rate, latency, data rate, etc.) can be the same for two QFIs / PMs, and therefore multiple QFIs / PMs can be mapped to the same DRB.

[0159] In the proposed method, as Figure 11 DRB is established for DL ​​as shown and Figure 12 As shown, a DRB is established for UL.

[0160] DL DRB creation: In the proposed method, the RAN (or gNodeB) 120 receives a packet in the DL according to the UP function in the CN. The RAN (or gNodeB) 120 receives the PM / QFI associated with the packet and the packet tag. The RAN (or gNodeB) 120 checks whether a DRB has been established for the PM / QFI associated with the received packet.

[0161] If not, then in an embodiment, the RAN (or gNodeB) 120 may create a DRB using a DRB configuration corresponding to the PM / QFI and PDU session and add the packet to the DRB queue. Furthermore, the RAN (or gNodeB) 120 sends the packet to the UE 110 and may include the PM / QFI and, optionally, the PDU session ID in the packet header.

[0162] If not, then in an embodiment, RAN (or gNodeB) 120 may add the QoS flow corresponding to the PM / QFI of the received packet to one of the existing DRBs. Furthermore, RAN (or gNodeB) 120 updates the mapping of DRB configurations to QoS flows. Furthermore, RAN (or gNodeB) 120 sends an RRC signaling message with the updated mapping of DRB configurations to QoS flows to UE 110. Furthermore, RAN (or gNodeB) 120 adds the packet to the DRB queue to which the QoS flow of the received packet is mapped.

[0163] If so, the RAN (or gNodeB) 120 adds the packet in the DRB queue.

[0164] After receiving a packet in the DL, the UE 110 obtains the LCID and determines whether there is a DRB corresponding to the LCID. If so, the UE 110 maps the packet to the DRB. If not, there are two methods.

[0165] Method 1 (such as Figure 11 shown): UE 110 obtains the PM / QFI and, optionally, the PDU session identifier for the received packet. Furthermore, UE 110 creates a DRB using the DRB configuration corresponding to the PM / QFI and, optionally, the PDU session identifier, and adds the packet to the DRB queue. The LCID of the logical channel associated with this new DRB is the LCID of the received packet.

[0166] Method 2: Alternatively, UE 110 creates a DRB using the DRB configuration corresponding to the LCID and adds the packet to the DRB queue. It should be noted that the DRB configuration configured for each PM / QFI can have an LCID. Therefore, based on the LCID, UE 110 can identify the DRB configuration to be used to create the DRB. The LCID of the logical channel associated with this new DRB is the LCID of the received packet.

[0167] In an embodiment, depending on whether the LCID is included in the DRB configuration, the UE 110 may decide to follow Method 1 or Method 2. Depending on whether the LCID is included in the DRB configuration, the RAN (or gNodeB) 120 may include the PM / QFI and optionally the PDU session id in the packet header.

[0168] UL DRB creation: In the UL, the access layer in the UE receives a packet to be transmitted and the associated PM / QFI and optionally a PDU session identifier from a higher layer (e.g., the NAS layer or the application layer). In addition, the UE 110 checks whether a DRB has been established for the PM / QFI and optionally the PDU session identifier associated with the received packet.

[0169] If not, UE 110 creates a DRB using the DRB configuration corresponding to the PM / QFI and, optionally, the PDU session identifier, and adds the packet to the DRB queue. If the LCID is not included in the DRB configuration, UE 110 itself allocates an unused LCID to the DRB. Furthermore, UE 110 sends the packet to RAN (or gNodeB) 120 and may include the PM / QFI and PDU session ID in the packet header. If the LCID is included in the DRB configuration, UE 110 may not include the PM / QFI and PDU session identifier in the packet header.

[0170] If so, UE 110 adds the packet in the DRB queue.

[0171] In an embodiment, upon receiving a packet from UE 110, RAN (or gNodeB) 120 checks whether a DRB has been established for the PM / QFI and PDU session ID associated with the received packet. If not, RAN (or gNodeB) 120 creates a DRB using the DRB configuration corresponding to the PM / QFI and PDU session identifier and adds the packet to the DRB queue. If yes, RAN (or gNodeB) 120 adds the packet to the DRB queue.

[0172] In an embodiment, upon receiving a packet in the UL, the RAN (or gNodeB) 120 obtains the LCID and determines whether a DRB corresponding to this LCID exists. If so, the RAN (or gNodeB) 120 maps the packet to the DRB. If not, there are two methods.

[0173] Method 1:The RAN (or gNodeB) 120 obtains the PM / QFI and PDU session identifier for the received packet. Furthermore, the RAN (or gNodeB) 120 creates a DRB using the DRB configuration corresponding to the PM / QFI and, optionally, the PDU session identifier, and adds the packet to the DRB queue. The LCID of the logical channel associated with the new DRB is the LCID of the received packet.

[0174] Method 2: Alternatively, the RAN (or gNodeB) 120 creates a DRB using the DRB configuration corresponding to the LCID and adds the packet to the DRB queue. It should be noted that the DRB configuration configured for each PM / QFI and, optionally, the PDU session identifier, can have an LCID. Thus, based on the LCID, the RAN (or gNodeB) 120 can identify the DRB configuration to be used for creating the DRB. The LCID of the logical channel associated with the new DRB is the LCID of the received packet.

[0175] In an embodiment, depending on whether the LCID is included in the DRB configuration, the RAN (or gNodeB) 120 decides to follow Method 1 or Method 2. Depending on whether the LCID is included in the DRB configuration, the UE 110 may include a PM / QFI and optionally a PDU session identifier in the packet header.

[0176] In addition, the RAN (or gNodeB) sends the packet to the UPF 170 and may include PM / QFI in the packet header. The packet is transmitted to the UPF 170 on a tunnel associated with the packet's PDU session.

[0177] In an embodiment, the PM / QFI and, optionally, the PDU session identifier may be included in the BSR. Upon receiving the PM / QFI and, optionally, the PDU session identifier in the BSR, if a DRB for the PM / QFI and, optionally, the PDU session identifier does not exist, the RAN (or gNodeB) 120 creates a DRB. In this case, the UE 110 does not include the PM / QFI in the UL packet. Alternatively, the LCID may be included in the BSR. Upon receiving the LCID in the BSR, if a DRB for this LCID does not exist, the RAN (or gNodeB) 120 creates a DRB. In this case, the UE 110 does not need to include the PM / QFI and, optionally, the PDU session identifier in the UL packet. It should be noted that the DRB configuration configured for each PM / QFI and PDU session identifier may have an LCID. Therefore, based on the LCID, the RAN (or gNodeB) 120 can identify the DRB configuration to be used to create the DRB. The LCID of the logical channel associated with this new DRB is the LCID of the received packet.

[0178] like Figure 11 As shown, DN 180 sends (1102) a DL IP packet to UPF 170. DRB Configuration Setup: A mapping list between PM / QFI and DRB configuration is established (1104) between UE 110 and RAN 120. The UPF sends (1106) a DL packet and a packet tag PM_1 or QFI_1 to RAN 120. In addition, the RAN determines (1108) that there is no DRB for processing the packet with the packet tag PM_1 / QFI_1. The RAN creates (1110) a DRB using the DRB configuration corresponding to PM_1 / QFI_1. RAN 120 sends (1112) a radio packet and the packet tag PM_1 / QFI_1. UE 110 determines (1114) that there is no DRB for processing the received radio packet. UE 110 creates (1116) a DRB using the DRB configuration corresponding to PM_1 / QFI_1.

[0179] like Figure 12As shown, the DRB configuration is set up: a mapping list between PM / QFI and DRB configuration is established (1202) between UE 110 and RAN 120. In addition, UE 110 receives (1204) an UL packet with packet tag PM_1 / QFI_1. In addition, UE 110 determines (1206) that there is no DRB for processing the packet with packet tag PM_1 / QFI_1. In addition, UE 110 creates (1208) a DRB using the DRB configuration corresponding to PM_1 / QFI_1. In addition, UE 110 sends (1210) a wireless packet with packet tag PM_1 / QFI_1 to RAN 120. In addition, RAN 120 determines (1212) that there is no DRB for processing the received wireless packet. In addition, RAN 120 creates (1214) a DRB using the DRB configuration corresponding to PM_1 / QFI_1. In addition, RAN 120 sends (1216) the UL packet and the packet tag PM_1 / QFI_1 to UPF 170. UPF 170 sends (1218) the UL IP packet to DN 140.

[0180] Figure 13 is a sequence diagram illustrating various operations performed for DRB establishment in DL according to embodiments as disclosed herein.

[0181] When a PDU session is established or a new QoS flow is established or when a radio connection is established, the QoS parameters of the QoS flow are also provided to the RAN (or gNodeB) 120 as a QoS profile. In addition, the QoS parameters can also be pre-configured in the RAN 120. In the RAN 120, a DRB defines packet handling over the radio interface (Uu). A DRB is served with the same packet forwarding treatment. Separate DRBs can be established for QoS flows that require different packet forwarding treatment. The RAN (or gNodeB) 120 is aware of the mapping between each QoS flow and the associated QoS parameters (or QoS profile) and decides accordingly the radio configuration for the corresponding data radio bearer. In the downlink, the RAN (or gNodeB) 120 maps QoS flows to DRBs based on packet marking (i.e., QoS flow ID) and associated QoS profile. For the uplink, the RAN (or gNodeB) 120 provides the QoS flow to DRB mapping in RRC signaling messages. One DRB can be mapped to multiple QoS flows. For each DRB configured, the RAN (or gNodeB) 120 provides a list of one or more QFIs and a PDU session identifier. QoS parameters related to radio level QoS (e.g., packet error rate, latency, data rate, etc.) can be the same for multiple QoS flows and thus multiple QoS flows of the same PDU session can be mapped to the same DRB. QoS flows of a PDU session are not mapped to more than one DRB. A QoS flow of one PDU session and another QoS flow of another PDU session can have the same QoS flow ID, but these are mapped to different DRBs. In other words, QoS flows of different PDU sessions are not mapped to the same DRB.

[0182] If QoS flows of different PDU sessions are mapped to the same DRB, upon receiving a packet from the UE 110 on this DRB, the gNodeB 120 cannot identify the PDU session associated with this packet and thus will not be able to identify the tunnel via which this packet should be sent to the UPF. It should be noted that for each PDU session, the tunnel is different.

[0183] In the proposed method, the DN 180 sends (1302) a DL IP packet to the UPF 170. The RAN (or gNodeB) 120 receives (1304) the packet in the DL according to the UP function in the CN. In addition, the RAN (or gNodeB) 120 receives the PM / QFI associated with the packet and the packet tag. The RAN (or gNodeB) 120 checks (1306) whether a DRB has been established for the PM / QFI and optionally the PDU session associated with the received packet. If not, the RAN (or gNodeB) 120 starts (1308) the DRB setup. It sends a DRB configuration message that includes the DRB configuration and its mapping to one or more PM / QFIs and optionally the PDU session identifier. The RAN (or gNodeB) 120 knows the mapping between each PM / QFI and the associated QoS parameters and decides the radio configuration for the corresponding DRB accordingly. The QoS parameters related to radio-level QoS may be the same for both PM / QFIs, and thus multiple PM / QFIs may be mapped to the same DRB, so that the RAN (or gNodeB) 120 may add the PM / QFI of the received packet to the PM / QFI list of the existing DRB, or add a new DRB and provide a new DRB configuration for the PM / QFI of the received packet. If a new DRB is added, the UE 110 creates (1310) a new DRB corresponding to the new configuration and PM / QFI included in the DRB configuration message.

[0184] In response, UE 110 may send a DRB Configuration Complete message. After receiving the DRB Configuration Complete message, if a new DRB configuration is added for this PM / QFI, RAN (or gNodeB) 120 creates (1312) a DRB using the DRB configuration corresponding to the PM / QFI of the received packet and adds the packet to the DRB queue. If the PM / QFI of the received packet is added to an existing DRB, the packet is mapped (1312) to the DRB queue.

[0185] Figure 141408 is a sequence diagram illustrating various operations for performing DRB establishment in the DL according to an embodiment as disclosed herein. In an embodiment, in the UL, the access layer receives (1402) a packet to be transmitted and the associated PM / QFI and optionally a PDU session identifier from a higher layer (e.g., the NAS layer or the application layer). In addition, the UE 110 checks (1404) whether a DRB has already been established for the PM / QFI and optionally the PDU session identifier associated with the received packet. If not, the UE starts (1406) DRB setup. It sends a DRB configuration request message, which includes the PM / QFI and optionally the PDU session identifier of the received packet. After receiving the DRB configuration request message with the PM / QFI and the PDU session identifier, the RAN (or gNodeB) 120 decides (1408) the radio configuration for the corresponding DRB. The RAN (or gNodeB) 120 knows the mapping between each PM / QFI and the associated QoS parameters and decides the radio configuration accordingly. QoS parameters related to radio-level QoS can be the same for two PMs / QFIs, and therefore for multiple PMs. Furthermore, the QFIs can be mapped to the same DRB, so that the RAN (or gNodeB) 120 can add the PM / QFI received in the DRB Configuration Request message to the list of PM / QFIs for an existing DRB, or add a new DRB and provide a new DRB configuration for the PM / QFI and PDU Session ID of the received packet. Furthermore, the RAN (or gNodeB) 120 sends the DRB Configuration message to the UE 110.

[0186] If a new DRB is added, UE 110 creates (1410) a new DRB corresponding to the new configuration and PM / QFI included in the DRB Configuration message. In response, UE 110 may send a DRB Configuration Complete message. If a new DRB configuration is added for a PM / QFI, after receiving the DRB Configuration Complete message, RAN (or gNodeB) 120 creates (1412) a DRB using the DRB configuration.

[0187] Furthermore, UE 110 transmits the wireless packet to RAN (or gNodeB) 120. Furthermore, RAN 120 transmits (1416) the UL packet and the packet tag PM_1 / QFI_1 to UPF 170. UPF 170 transmits (1418) the UL IP packet to DN 140.

[0188] In an embodiment, each DRB is associated with a PDCP entity, multiple RLC entities and logical channels. In the proposed scheme, packets with different PM / QFI or packets of different flows are handled by the same PDCP entity. PDCP PDUs associated with different PM / QFI or different flows are handled by different RLC entities. RLC PDUs of each RLC entity are processed or mapped to different logical channels.

[0189] Further, the RAN (or gNodeB) 120 can provide one or more DRB configurations. Each DRB configuration is associated with one or more PM / QFI or flows. There is one PDCP configuration per DRB. There can be multiple RLC configurations per DRB. Each RLC configuration is mapped to one or more PM / QFI or flows. Further, the UE 110 creates RLC entities and logical channels for each RLC configuration. There can be multiple logical channel configurations per DRB. The number of logical channel configurations is equal to the number of RLC configurations. That is, there is one-to-one mapping between logical channels and RLC entities.

[0190] The advantage of this approach is that one PDCP entity can be used to apply the same functionality, such as ROHC, security, etc., for each flow. The RLC / logical channel functionality is flow specific and thus applied independently.

[0191] In an embodiment, the RAN (or gNodeB) 120 can provide one or more DRB configurations. Each DRB configuration is associated with one or more PM / QFI or flows. There is one PDCP configuration per DRB. There is one RLC configuration per DRB. The logical channel configuration can be different for different PM / QFI or flows. This means that each DRB is mapped to multiple logical channels. RLC PDUs of different flows / PM / QFI are mapped to different logical channels. The advantage of this approach is that one PDCP / RLC entity can be used to apply the same functionality, such as ROHC, security, ARQ, etc., for each flow. The logical channel functionality is flow specific and thus applied independently.

[0192] In an embodiment, due to mobility, the UE 110 can be handed over from one RAN (or gNodeB), also referred to as source gNodeB, to another RAN (or gNodeB), also referred to as target gNodeB. In this case, to avoid any packet loss, the source gNodeB can transfer one or more packets received by it from the network entity 160 to the target gNodeB. Packets that have not been transferred by the source gNodeB to the UE 110 or packets that have been transferred but not acknowledged by the UE 110 are transferred by the source gNodeB to the target gNodeB. To enable the target gNodeB to map these packets to the appropriate DRB, the source gNodeB provides the QFI associated with each packet and optionally the PDU session identifier of the PDU session to the target gNodeB. The target gNodeB can then map these packets of each PDU session to the DRB using the methods explained earlier based on the QFI, wherein the gNodeB 120 maps the packets received from the network entity 160 to the DRB based on the QFI.

[0193] The embodiments disclosed herein can be implemented using at least one software program running on at least one hardware apparatus and performing network management functions to control the elements.

[0194] The foregoing description of specific embodiments has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the embodiments disclosed herein to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the disclosure be ac- knowledged in all its novel aspects and equivalents of the embodiments described. While embodiments have been described above, it is intended that numerous other changes, adaptations and modifications will be apparent to one skilled in the art. Therefore, it is intended that the claims be interpreted to embrace all such changes, adaptations and modifications.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, first information related to a mapping between at least one quality of service identifier (QoS ID) and at least one data radio bearer (DRB); identifying a QoS ID associated with the first uplink packet; identifying, based on the first information, whether there is a DRB mapped to the QoS ID associated with the first uplink packet; as well as In case the DRB is not identified, the first uplink packet marked with the QoS ID is sent to the base station on a default DRB.

2. The method according to claim 1, wherein Identifying whether there is a DRB mapped to the QoS ID associated with the first uplink packet includes: It is identified whether a DRB is established for the QoS ID associated with the first uplink packet.

3. The method according to claim 1, further comprising: Second information is received from the base station on the default DRB.

4. The method according to claim 1, further comprising: receiving third information related to a mapping between the QoS ID and a new DRB from the base station, The first information and the third information are received via a radio resource control RRC message.

5. The method according to claim 4, further comprising: identifying, based on the third information, whether there is a new DRB mapped to the QoS ID associated with the second uplink packet; as well as Upon identifying the new DRB mapped to the QoS ID associated with the second uplink packet, the second uplink packet tagged with the QoS ID is sent to the base station on the new DRB.

6. The method according to claim 1, further comprising: receiving, from the base station, fourth information related to a mapping between a new QoS ID and an existing DRB; as well as Based on the fourth information, a downlink packet marked with the new QoS ID is received from the base station on the existing DRB.

7. A method performed by a base station in a wireless communication system, the method comprising: Sending first information related to a mapping between at least one quality of service identifier (QoS ID) and at least one data radio bearer (DRB) to a terminal; as well as receiving a first uplink packet marked with a QoS ID from the terminal on a default DRB, There is no DRB mapped to the QoS ID associated with the first uplink packet in the first information.

8. The method according to claim 7, wherein: The absence of a DRB mapped to the QoS ID associated with the first uplink packet in the first information corresponds to no DRB being established for the QoS ID associated with the first uplink packet.

9. The method according to claim 7, further comprising: Send second information to the terminal on the default DRB.

10. The method according to claim 7, further comprising: sending third information related to the mapping between the QoS ID and the new DRB to the terminal, The first information and the third information are sent via a radio resource control RRC message.

11. The method according to claim 10, further comprising: Based on the third information, a second uplink packet marked with the QoS ID is received from the terminal on the new DRB.

12. The method according to claim 7, further comprising: sending fourth information related to a mapping between a new QoS ID and an existing DRB to the terminal; as well as Based on the fourth information, a downlink packet marked with the new QoS ID is sent to the terminal on the existing DRB.

13. A terminal in a wireless communication system, the terminal comprising: transceiver; and Controller, configured as: controlling the transceiver to receive first information related to mapping between at least one quality of service identifier (QoS ID) and at least one data radio bearer (DRB) from a base station; identifying a QoS ID associated with the first uplink packet; identifying, based on the first information, whether there is a DRB mapped to the QoS ID associated with the first uplink packet; as well as In case the DRB is not identified, the first uplink packet marked with the QoS ID is sent to the base station on a default DRB. The terminal according to claim 13 , wherein: The controller is further configured to: It is identified whether a DRB is established for the QoS ID associated with the first uplink packet. The terminal according to claim 13 , wherein: The controller is further configured to control the transceiver to receive second information from the base station on the default DRB. The terminal according to claim 13 , wherein: The controller is further configured to: control the transceiver to receive third information related to the mapping between the QoS ID and the new DRB from the base station, The first information and the third information are received via a radio resource control RRC message. The terminal according to claim 16 , wherein: The controller is further configured to: identify, based on the third information, whether there is a new DRB mapped to the QoS ID associated with the second uplink packet; and upon identifying the new DRB mapped to the QoS ID associated with the second uplink packet, controlling the transceiver to transmit the second uplink packet marked with the QoS ID to the base station on the new DRB. The terminal according to claim 13 , wherein: The controller is further configured to: control the transceiver to receive fourth information related to mapping between a new QoS ID and an existing DRB from the base station; as well as Based on the fourth information, the transceiver is controlled to receive a downlink packet marked with the new QoS ID from the base station on the existing DRB.

19. A base station in a wireless communication system, the base station comprising: transceiver; and Controller, configured as: controlling the transceiver to send first information related to a mapping between at least one quality of service identifier (QoS ID) and at least one data radio bearer (DRB) to the terminal; as well as controlling the transceiver to receive a first uplink packet marked with a QoS ID from the terminal on a default DRB, There is no DRB mapped to the QoS ID associated with the first uplink packet in the first information.

20. The base station according to claim 19, wherein The absence of a DRB mapped to the QoS ID associated with the first uplink packet in the first information corresponds to no DRB being established for the QoS ID associated with the first uplink packet.

21. The base station according to claim 19, wherein The controller is further configured to control the transceiver to send second information to the terminal on the default DRB.

22. The base station according to claim 19, wherein The controller is further configured to: control the transceiver to send third information related to the mapping between the QoS ID and the new DRB to the terminal, The first information and the third information are sent via a radio resource control RRC message.

23. The base station according to claim 22, wherein: The controller is further configured to control the transceiver to receive a second uplink packet with the QoS ID from the terminal on the new DRB based on the third information.

24. The base station according to claim 19, wherein The controller is also configured to: control the transceiver to send fourth information related to the mapping between the new QoS ID and the existing DRB to the terminal; and based on the fourth information, control the transceiver to receive downlink packets marked with the new QoS ID from the terminal on the existing DRB.

Images