Wireless communication method and base station

Abstract

A wireless communication method is provided. A base station, such as a gNB, receives a set of protocol data units (PDU) of a first frame type for a service from a user equipment (UE) over a first dynamic radio bearer (DRB), and receives a set of PDUs of a second frame type for the service over a second DRB. The base station transmits the PDU set of the first frame type of the service in a first quality of service (QoS) bearer to the user plane function (UPF), and transmits the PDU set of the second frame type of the service in a second QoS bearer.

Description

Technical Field

[0001] The present disclosure relates to the telecommunication field, and in particular to a wireless communication method and a base station. Background Art

[0002] Wireless communication systems, such as the third generation (3G) mobile phone standards and technologies, are well known. Such 3G standards and technologies are developed by the Third Generation Partnership Project (3GPP). The third generation of wireless communications is generally developed to support macrocellular mobile phone communications. Communication systems and networks have evolved into broadband and mobile systems. In a cellular wireless communication system, a user equipment (UE) is connected to a radio access network (RAN) via a radio link. The RAN includes a set of base stations (BS) that provide radio links for the UEs located in the cells covered by the base stations and interface with a core network (CN) that provides overall network control. It is understood that the RAN and CN each perform corresponding functions related to the overall network. The Third Generation Partnership Project developed the so-called Long Term Evolution (LTE) system, i.e., the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN), for mobile access networks, in which one or more macro cells are supported by base stations called eNodeBs or eNBs (evolved NodeBs). Recently, LTE has evolved further towards the so-called 5G or New Radio (NR) systems, in which one or more cells are supported by base stations called gNBs. Technical issues

[0003] The 5G wireless communication system is designed to provide enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine type communication (MTC) services. In 5G or NR, the functions supporting eMBB, URLLC, and mMTC were introduced in Release 15 and enhanced in Releases 16 and 17.

[0004] Extended reality (XR) is an umbrella term covering augmented reality (AR), mixed reality (MR), and virtual reality (VR). XR applications typically require high throughput and low latency, and cloud gaming is another application with the same requirements. XR and cloud gaming are important applications that 5G will enable.

[0005] XR services are characterized by their special traffic flows in real time, high data rate and low latency. XR video streams contain different frames / video slices. For example, a group of pictures (GOP) includes I / P / B frames. Some special characteristics of such XR service flows should be considered and supported in 5G.

[0006] On the one hand, the data size of different frames is different, and a frame can be divided into a group of data packets. However, the application can only decode these frames / video slices when all data packets of the frame / video slice are successfully received. A group of data packets belonging to a frame / video slice (hereinafter referred to as a data packet group) should be processed as a unit.

[0007] On the other hand, some types of data packet groups may depend on other data packet groups. For example, the data packets of P frames and B frames depend on the data packets of the I frames, and the data packets of B frames depend on the data packets of the P frames. In other words, there is a dependency relationship between different data packet groups. ●From a Quality of Service (QoS) perspective, the characteristics of XR services mean that different groups of data packets in a video stream have different QoS requirements.

[0008] The current QoS framework should be enhanced for XR services, especially for:

[0009] Potential dependencies between packets within a PDU set and / or dependencies between dependent PDU sets; ●Map PDU sets to dynamic radio bearers (DRBs) Summary of the invention

[0010] An object of the present disclosure is to provide a base station and a wireless communication method.

[0011] In a first aspect, an embodiment of the invention provides a wireless communication method, which may be performed in a base station, comprising: receiving a set of protocol data units (PDUs) of a first frame type served in a first quality of service (QoS) bearer, and receiving a set of PDUs of a second frame type for the service in a second QoS bearer; transmitting the PDU set of the first frame type of the service via a first dynamic radio bearer (DRB), and transmitting the PDU set of the second frame type of the service via a second DRB; At least one dependency between the PDU set of the first frame type and the PDU set of the second frame type is reflected in the QoS configuration of the first QoS bearer and the second QoS bearer and the DRB configuration of the first DRB and the second DRB.

[0012] In a second aspect, an embodiment of the invention provides a base station, comprising a processor configured to call and run a computer program stored in a memory, so that a device equipped with the processor performs the disclosed method.

[0013] In a third aspect, an embodiment of the invention provides a wireless communication method, which may be performed in a user equipment (UE), comprising:

[0014] The disclosed method may be implemented in a chip. The chip may include a processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes the disclosed method.

[0015] The disclosed method can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. When the non-transitory computer-readable medium is loaded into a computer, it instructs the processor of the computer to execute the disclosed method.

[0016] The non-temporary computer-readable medium may include at least one of the following groups: a hard disk, a read-only compact disk (CD-ROM), an optical storage device, a magnetic storage device, a read-only memory (Read-Only Memory), a programmable read-only memory (Programmable Read-Only Memory), an erasable programmable read-only memory (ErasableProgrammable Read-Only Memory, EPROM), an electrically erasable programmable read-only memory (ElectricallyErasableProgrammableRead-OnlyMemory) and a flash memory.

[0017] The disclosed method can be programmed into a computer program product to enable a computer to execute the disclosed method.

[0018] The disclosed method can be programmed into a computer program to enable a computer to execute the disclosed method. Beneficial Effects

[0019] At least one embodiment of the present disclosure provides a method to support considering dependencies between PDU sets between DRBs and within DRBs when processing data packets between multiple DRBs. Through the present invention, gNB can improve radio resource efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments or related technologies of the present disclosure, the drawings described in the embodiments are briefly introduced. Obviously, the drawings are only some embodiments of the present disclosure, and ordinary technicians in this field can obtain other drawings based on these drawings without paying the above premise.

[0021] Figure 1 A schematic diagram of a telecommunication system is shown.

[0022] Figure 2 A schematic diagram of a network embodiment showing the disclosed wireless communication method is shown.

[0023] Figure 3 A schematic diagram showing the protocol layers of a sending device and a receiving device.

[0024] Figure 4 A schematic diagram of a wireless communication method according to an embodiment of the present disclosure is shown.

[0025] Figure 5 A schematic diagram of a wireless communication method according to another embodiment of the present disclosure is shown.

[0026] Figure 6 A schematic diagram showing an example of a mapping configuration.

[0027] Figure 7 A schematic diagram showing another mapping configuration example.

[0028] Figure 8 A schematic diagram showing yet another mapping configuration example.

[0029] Fig. 9 is a block diagram of a wireless communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings in combination with technical matters, structural features, implementation objectives and effects. Specifically, the terms in the embodiments of the present disclosure are only used for the purpose of describing the specific embodiments, and are not intended to limit the present disclosure. The abbreviations used in this description are listed below: Table 1

[0031] The present invention discloses a wireless communication method for processing extended reality (XR) traffic in an extended reality (XR) service. The XR service may include augmented reality (AR), virtual reality (VR) or mixed reality (MR).

[0032] In the description herein, a data packet may be a PDU or SDU of a protocol layer. For the sake of simplicity, the term "data packet" may refer to a PDU or an SDU, and the term "PDU" may refer to a PDU or an SDU.

[0033] In the description of this document, a dependent data unit is called a dependent data unit, and a data unit that depends on the dependent data unit is called a dependent data unit. For example, a dependent DRB is called a dependent DRB, and a DRB that depends on the dependent DRB is called a dependent DRB. Similarly, a dependent PDU set is called a dependent PDU set, and a PDU set that depends on the dependent PDU set is called a dependent PDU set. A dependent data packet is called a dependent data packet, and a data packet that depends on the dependent data packet is called a dependent data packet. A dependent QoS flow is called a dependent QoS flow, and a QoS flow that depends on the dependent QoS flow is called a dependent QoS flow. A dependent QoS sub-flow is called a dependent QoS sub-flow, and a QoS sub-flow that depends on the dependent QoS sub-flow is called a dependent QoS sub-flow.

[0034] From a Quality of Service (QoS) perspective, the characteristics of XR services mean that different groups of packets in a video stream have different QoS requirements. QoS flow is the smallest granularity in the current QoS framework described in 5GS. When different groups of packets are carried by different QoS flows, dependencies are introduced between QoS flows. As an enhancement to the current QoS framework to support XR services, 3GPP SA2 introduced a concept called "PDU Set" in the Technical Report (TR) 23.700-60.

[0035] A PDU set consists of one or more PDUs that carry the payload of an information unit generated at the application layer (e.g., a frame or video slice of an XR service, as used in TR 26.926). In some implementations, the application layer requires all PDUs in a PDU set to use the information unit. In other implementations, the application layer can recover part or all of the information unit when some PDUs are missing.

[0036] For XR traffic, such as one or more service traffic flows, a PDU set may be a group of packets or PDUs that are decoded or processed as a whole unit at the application layer. XR traffic has some potential dependencies between packets within a PDU set and / or between PDU sets. A service traffic flow for an XR service may include PDU sets of different types, importance levels, and QoS requirements. Therefore, a potential QoS framework enhancement is to extend the QoS framework based on QoS flows. In one embodiment, a QoS flow includes multiple QoS sub-flows. The different types of PDU sets of the QoS flow are mapped to different QoS sub-flows of the QoS flow.

[0037] Reference Figure 1 A telecommunication system including a user equipment (UE) 10a, a user equipment 10b, a base station (BS) 20a and a network entity device 30 performs the disclosed method according to an embodiment of the present disclosure. Figure 1 For illustration only and not limitation, the system may include more UE, BS and CN entities. The connections between devices and device components are represented by lines and arrows in the figure. The user equipment 10a may include a processor 11a, a memory 12a and a transceiver 13a. The user equipment 10b may include a processor 11b, a memory 12b and a transceiver 13b. The base station 20a may include a processor 21a, a memory 22a and a transceiver 23a. The network entity device 30 may include a processor 31, a memory 32 and a transceiver 33. Each of the processors 11a, 11b, 21a and 31 may be configured to implement the functions, processes and / or methods proposed in the description herein. The layers of the wireless interface protocol may be implemented in the processors 11a, 11b, 21a and 31. Each of the memories 12a, 12b, 22a and 32 may be operable to store various programs and information to operate the connected processors. Each of the transceivers 13a, 13b, 23a and 33 is operably coupled to the connected processor to send and / or receive wireless signals or wired signals. The user equipment 10a can communicate with the user equipment 10b via a side link. The base station 20a can be one of an eNB, a gNB or other types of wireless nodes, and can configure wireless resources for the user equipment 10a and the user equipment 10b.

[0038] The network entity device 30 may be a node in a core network. The core network may include a Long Term Evolution (LTE) core network or a 5G Core (5G Core, 5GC), including a User Plane Function (UPF), a Session Management Function (SMF), a 5G Core Access and Mobility Management Function (AMF), a Unified Data Management (UDM), a Policy Control Function (PCF), a Control Plane (CP) / User Plane (UP) Separation (CUPS), an Authentication Server (AUSF), a Network Slice Selection Function (NSSF) and the Network Exposure Function (NEF).

[0039] The example of the user equipment described in this article may include one of the user equipment 10a or the user equipment 10b. The example of the base station described in this article may include the base station 20a. The transmission of an uplink (UL) control signal or data may be a transmission operation from the user equipment to the base station. The transmission of a downlink (DL) control signal or data may be a transmission operation from the base station to the user equipment. The downlink control signal may include a downlink control information (DCI) or a radio resource control (RRC) signal from the base station to the user equipment.

[0040] Figure 2It is a transmission network model of XR services supported by the 5G system. The user equipment (UE) 10 is a 5G terminal that supports XR services and XR applications, and can be called a client, a client terminal, or an XR client. The gNB 20 is a 5G wireless node. The gNB 20 communicates with the UE 10 and provides the UE with NR user plane and control plane protocol termination via the NR Uu interface. The gNB 20 is connected to the 5G core network (5GC) 300 via the NG interface. The user plane function (UPF) 30b is a UPF in the 5GC 300, that is, the 5G core network. The data network (DN) 40 is a data network in which an XR server 41 providing XR services is located. The DN 40 can provide network operator services, Internet access, or third-party services. The XR server 41 may include a processor 411, a memory 412, and a transceiver 413. The processor 411 may be configured to implement the XR service-related functions, processes, and / or methods described in the description of this article. The layers of the wireless interface protocol may be implemented in the processor 411. The memory 412 may be operable to store various programs and information to operate the connected processor. The transceiver 413 may be operably coupled to the connected processor to send and / or receive wireless signals or wired signals.

[0041] Each of the processors 411, 11a, 11b, 21a and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. Each of the memories 412, 12a, 12b, 22a and 32 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other storage devices. Each of the transceivers 413, 13a, 13b, 23a and 33 may include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, processes, functions, entities, etc. that perform the functions described herein. The modules may be stored in a memory and executed by the processor. The memory may be implemented inside the processor or outside the processor, in which case they may be communicatively coupled to the processor in various ways known in the art. The device that performs the wireless communication method may be a sending device that transmits an XR traffic stream of an XR service to a receiving device, or a receiving device that receives the XR traffic stream. The XR traffic stream may include one or more service traffic streams of the XR service. For example, the device that performs the wireless communication method may include the gNB 20, an XR server 41 in the data network 40, or a UE. That is, the XR server 41 in the data network 40 may operate as a sending device that performs the wireless communication method in certain XR traffic transmission occasions, and one or more XR clients (for example, one or more of the UE 10, UE 10a, and UE 10b) receive the XR traffic stream sent from the sending device as the receiving device. Similarly, an XR client (for example, one or more of the UE 10, UE 10a, and UE 10b) may operate as a sending device that performs the wireless communication method in certain XR traffic transmission occasions, and another XR client or the XR server 41 receives the XR traffic stream sent from the sending device as the receiving device. Alternatively, the sending device may include an intermediate device between the UE 10 and the XR server 41. The UE 10 may include an embodiment of the UE 10a or UE 10b. The gNB 20 may include an embodiment of the base station 20a. It should be noted that although the gNB 20 and UPF / 5GC 30b are described as an example in the description of this document, the wireless communication method may be performed by a base station, such as another gNB, an eNB, a base station integrating an eNB and a gNB, or a base station for technologies above 5G.The UPF / 5GC 30b may include another network entity of the 5GC.

[0042] A service traffic flow 5, such as an XR flow of an XR service, is established between the UE 10 and the XR server 41. The flow 5 includes a traffic flow 51 from the XR server 41 to the UE 10 and a traffic flow 52 from the UE 10 to the XR server 41.

[0043] In the description herein, a layer, such as an application layer, a PDCP layer, an RLC layer, a MAC layer, or a physical layer (PHY layer or L1 layer), may be a protocol layer entity in a transmitting device or a receiving device. The protocol layer entity may be implemented by a program or software module executed by a processor, or by a hardware module in an integrated circuit (IC).

[0044] Reference Figure 3 , an example of the sending device is shown as a sending device 10c, and an example of the receiving device is shown as a receiving device 10d. The sending device 10c includes a physical layer (PHY layer or L1 layer) 14c, a MAC layer 15c, an RLC layer 16c, a PDCP layer 17c, an RRC layer 18c, and an application layer 19c. The receiving device 10d includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, an RRC layer 18d, and an application layer 19d. For example, when the application layer 19c of the sending device 10c sends a PDU to the application layer 19d of the receiving device 10d through a lower layer (i.e., the PDCP layer 17c, the RLC layer 16c, the MAC layer 15c, and the physical layer 14c), the layer in the sending device 10c acts as a sending protocol layer entity on the sending side, and the layer in the receiving device 10d acts as a receiving protocol layer entity on the receiving side. The embodiments of the present disclosure may be implemented in the PDCP layer or the RLC layer. One or more steps (or blocks) in the embodiments of the present disclosure may be implemented as a computer program, instruction, software module stored in the memory of the transmitting device, or a circuit or hardware module in the processor of the transmitting device, or an IC chip, circuit or plug-in of the transmitting device.

[0045] The video stream of the XR service will be quasi-periodically encoded and compressed in the form of frames, each of which has a frame period of 1 / 60, 1 / 90 or 1 / 120 seconds. Since the sending device can divide the video stream of the XR service into multiple transmission units, encapsulate and transmit each of the transmission units into a transmission data packet across the network, the transmission mechanism of the XR service is actually based on data packets rather than frames. The size of each data packet can be variable, the number of data packets can be variable, and can be configured according to the QoS requirements and one or more parameters of the XR service characteristics, such as packet delay budget (PDB), packet error rate (PER), packet loss rate (PLR), frame error rate, frame delay budget, resolution, frame rate and / or data rate.

[0046] Reference Figure 4 , the gNB 20 executes an embodiment of the disclosed method and initiates the XR service.

[0047] The gNB 20 receives a protocol data unit (PDU) set of a first frame type served in a first quality of service (QoS) bearer from the UPF 30b, and receives a PDU set of a second frame type served in a second QoS bearer (201). For example, the first frame type is one of an I frame, a P frame, and a B frame, and the second frame type is another one of the I frame, the P frame, and the B frame. The gNB 20 transmits the PDU set of the first frame type of the service to the UE 10 via a first dynamic radio bearer (DRB), and transmits the PDU set of the second frame type of the service via a second DRB (203).

[0048] At least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type is reflected in the QoS configurations of the first QoS bearer and the second QoS bearer and the DRB configurations of the first DRB and the second DRB.

[0049] Reference Figure 5 , the gNB 20 executes an embodiment of the disclosed method and initiates the XR service.

[0050] The gNB 20 receives a protocol data unit (PDU) set of a first frame type of service from the UE 10 through a first dynamic radio bearer (DRB), and receives a PDU set of a second frame type of the service through a second DRB (301). For example, the first frame type is one of an I frame, a P frame, and a B frame, and the second frame type is another one of the I frame, the P frame, and the B frame.

[0051] The gNB 20 transmits the PDU set of the first frame type of the service to the UPF 30b in a first Quality of Service (QoS) bearer, and transmits the PDU set of the second frame type of the service in a second QoS bearer (303).

[0052] At least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type is reflected in the QoS configurations of the first QoS bearer and the second QoS bearer and the DRB configurations of the first DRB and the second DRB.

[0053] In the Figure 4 and Figure 5 In the embodiment of the present invention, the first QoS bearer may include a first QoS flow with a first QoS flow identifier (ID), and the second QoS bearer may include a second QoS flow with a second QoS flow ID. The first QoS flow and the second QoS flow constitute a first QoS flow group with a first QoS flow group ID. The first QoS flow and the second QoS flow may be mapped to one or more DRBs constituting a DRB group according to the DRB configuration.

[0054] In the QoS configuration, the at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type may include one or more of the following: ● QoS inter-flow dependencies between different QoS flows in the QoS flow group; ● QoS intra-flow dependencies for each QoS flow; ●Intra-PDU set dependencies for each QoS flow; The QoS inter-flow dependency indicates that the PDU set of the dependent QoS flow depends on the PDU set of the dependent QoS flow between QoS flows; The intra-QoS flow dependency indicates that a dependent PDU set of a QoS flow depends on a dependent PDU set of the same QoS flow within the QoS flow; The intra-PDU set dependency indicates that a dependent PDU in a PDU set of a QoS flow depends within the PDU set on a dependent PDU in the same PDU set of the same QoS flow.

[0055] In the DRB configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type includes one or more of the following: ●Inter-DRB dependencies between different DRBs; ●Intra-DRB dependencies for each DRB; ●Intra-PDU set dependencies for each DRB; wherein the inter-DRB dependency is aligned with the inter-QoS flow dependency and indicates that the PDU set of the dependent DRB depends on the PDU set of the dependent DRB between the DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS flow, and indicates that a dependent PDU in the PDU set of a DRB depends within the PDU set on the dependent PDU in the same PDU set of the same DRB.

[0056] In the Figure 4 and Figure 5 In the embodiment, the first QoS bearer may include a first QoS subflow with a first QoS subflow identifier (ID), the second QoS bearer includes a second QoS subflow with a second QoS subflow ID, and the first QoS subflow and the second QoS subflow constitute a third QoS flow with a third QoS flow ID. The first QoS subflow and the second QoS subflow may be mapped to one or more DRBs constituting a DRB group according to the DRB configuration.

[0057] In the QoS configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type includes one or more of the following: ● QoS sub-flow inter-dependencies between different QoS sub-flows in the third QoS flow; ●Intra-QoS sub-flow dependencies for each QoS sub-flow; ●Intra-PDU set dependencies for each QoS subflow; The dependency between QoS sub-flows indicates that the PDU set of the dependent QoS sub-flow depends on the PDU set of the dependent QoS sub-flow between QoS sub-flows; The intra-QoS sub-flow dependency indicates that a dependent PDU set of a QoS sub-flow depends on a dependent PDU set of the same QoS sub-flow within the QoS sub-flow; The intra-PDU set dependency indicates that a dependent PDU in a PDU set of a QoS sub-flow depends within the PDU set on a dependent PDU in the same PDU set of the same QoS sub-flow.

[0058] The dependency between the QoS sub-flows may include a processing mode indicating whether to discard the dependent PDU set of the dependent QoS sub-flow when the dependent PDU set of the dependent QoS sub-flow is discarded; The intra-QoS sub-flow dependency includes a processing mode indicating whether to discard the dependent PDU set of the QoS sub-flow that depends on the dependent PDU set of the same QoS sub-flow within the QoS sub-flow when the dependent PDU set of the same QoS sub-flow is discarded; The intra-PDU set dependency includes a processing method indicating whether to discard the dependent PDU in the PDU set of the QoS substream that depends on the dependent PDU in the same PDU set of the same QoS substream within the PDU set when the dependent PDU in the same PDU set of the same QoS substream is discarded.

[0059] In the DRB configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type includes one or more of the following: ●Inter-DRB dependencies between different DRBs; ●Intra-DRB dependencies for each DRB; ● Dependencies within the PDU set of each DRB; wherein the inter-DRB dependency is aligned with the inter-QoS sub-flow dependency, and indicates that the PDU set that depends on the DRB depends on the PDU set of the dependent DRB between the DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS sub-flow, and indicates that a dependent PDU in the PDU set of a DRB depends within the PDU set on the dependent PDU in the same PDU set of the same DRB.

[0060] Reference Figure 4 and Figure 5 In one embodiment, the first QoS bearer may include a first PDU set type with a first PDU set type identifier (ID), the second QoS bearer may include a second PDU set type with a second PDU set type ID, and the first PDU set type and the second PDU set type constitute a third QoS flow with a third QoS flow ID. The first PDU set type and the second PDU set type may be mapped to one or more DRBs constituting a DRB group according to the DRB configuration.

[0061] In the QoS configuration, the at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type may include one or more of the following: ● inter-PDU set type dependencies between different PDU set types in the third QoS flow; ●Intra-PDU set type dependencies for each PDU set type; ●Intra-PDU set dependencies for each PDU set type; The inter-PDU set type dependency indicates that a PDU set of a dependent PDU set type depends on a PDU set of a dependent PDU set type among PDU set types; The intra-PDU set type dependency indicates that a dependent PDU set of a PDU set type depends on a dependent PDU set of the same PDU set type within the PDU set type; The intra-PDU set dependency indicates that a dependent PDU in a PDU set of a PDU set type depends within the PDU set on a dependent PDU in the same PDU set of the same PDU set type.

[0062] The inter-PDU set type dependency includes a processing mode indicating whether to discard the dependent PDU set of the dependent PDU set type when the dependent PDU set of the dependent PDU set type is discarded; The intra-PDU set type dependency includes a processing mode indicating whether to discard the dependent PDU set of the PDU set type that depends on the dependent PDU set of the same PDU set type within the PDU set type when the dependent PDU set of the same PDU set type is discarded; The intra-PDU set dependency includes a processing method indicating whether to discard the dependent PDU in the PDU set type of the PDU set that depends on the dependent PDU in the same PDU set of the same PDU set type within the PDU set when the dependent PDU in the same PDU set of the same PDU set type is discarded.

[0063] The at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type includes one or more of the following: ●Inter-DRB dependencies between different DRBs; ●Intra-DRB dependencies for each DRB; ●Intra-PDU set dependencies for each DRB; wherein the inter-DRB dependency is aligned with the inter-PDU set type dependency, and indicates that the PDU set of the dependent DRB depends on the PDU set of the dependent DRB between DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each PDU set type, and indicates that a dependent PDU in a PDU set of a DRB depends within the PDU set on a dependent PDU in the same PDU set of the same DRB. Example 1: Mapping QoS flow groups to DRB groups

[0064] In this embodiment, the service traffic flow of a service (e.g., an XR service) is identified in the 5GC (e.g., the 5GC 300) as one or more different types of PDU sets, hereinafter referred to as PDU set types. Different types of PDU sets correspond to different QoS requirements, and each PDU set type corresponds to one of the QoS requirements. Each PDU set type is mapped to a QoS flow in the 5GC, and all QoS flows belonging to the same service traffic flow constitute a QoS flow group. In the QoS flow group, at least one QoS flow is independent, and each of the other QoS flows depends on at least one or more QoS flows.

[0065] In order to enable the gNB and / or UE to map the QoS flow to the DRB and support the QoS requirements of the service traffic flow, an embodiment of the disclosed method includes the following process and the corresponding configuration information. 1.QoS flow mapping and dependency configuration:

[0066] Based on the QoS flow group of the service traffic flow, the 5GC configures the QoS flows of the QoS flow group and the dependencies between the QoS flows, and provides the configuration to the gNB (e.g., gNB 20), as described below.

[0067] The 5GC configures multiple QoS flows to form a QoS flow group and provides the configuration to the gNB.

[0068] As an embodiment, each QoS flow is uniquely identified by the QoS flow group identifier (ID) of the QoS flow group and the QoS flow ID of the QoS flow. The QoS flows with the same QoS flow group ID should be regarded as a whole. For example, the application layer, packet data convergence protocol (PDCP) layer and / or radio link control (RLC) layer of the sending device and the receiving device process the QoS flows with the same QoS flow group ID as a unit. Based on the current NG application protocol (NGAP), a new information element (IE) "QoS flow group identifier" can be introduced for each QoS flow. The hierarchical structure and characteristics of the IE "QoS flow group identifier" are shown in the table below. Table 2

[0069] In the tables presented in the description herein, "M" in the "Present" column indicates mandatory and "O" indicates optional.

[0070] As an embodiment, a QoS flow is configured as a main QoS flow, having only its own QoS flow ID, and other QoS flows configured with their own QoS flow ID and the main QoS flow should be regarded as a QoS flow group together with the main QoS flow. Based on the current NGAP protocol, the new information element (IE) "main QoS flow identifier" can be introduced for each QoS flow. The hierarchical structure and characteristics of the IE "main QoS flow identifier" are shown in the table below. Table 3

[0071] The 5GC configures the dependency information of each QoS flow in the QoS flow group to the gNB. The dependency information may include one or more of the following: ● QoS inter-flow dependencies between different QoS flows in the QoS flow group; ● QoS intra-flow dependencies for each QoS flow; ●Intra-PDU set dependencies for each QoS flow.

[0072] The dependency information is described in detail below. ● QoS inter-flow dependencies between different QoS flows in the QoS flow group: ■For each dependent QoS flow, the information (or configuration) of the inter-QoS flow dependency indicates which QoS flow the dependent QoS flow depends on. Specifically, the information (or configuration) of the inter-QoS flow dependency indicates that the PDU set of the dependent QoS flow depends on the PDU set of the dependent QoS flow between QoS flows. ■The information (or configuration) of the dependency between the QoS flows may further provide a processing method for the dependency. The dependency between the QoS flows includes a processing method indicating whether to discard the dependent PDU set of the dependent QoS flow when the dependent PDU set of the dependent QoS flow is discarded. For example, if a PDU set is lost or discarded, the processing method indicates whether to discard unsent data packets of a PDU set between QoS flows that depends on the lost or discarded PDU set. A QoS flow may depend on multiple other QoS flows. ●QoS intra-flow dependencies for each QoS flow: ■QoS intra-flow dependency means that a PDU set in a QoS flow can depend on another PDU set in the same QoS flow. The information (or configuration) of the intra-flow dependency indicates whether there is an intra-flow dependency in a QoS flow in the QoS flow group and the processing method of the dependency. Specifically, the information (or configuration) of the intra-flow dependency indicates that a dependent PDU set of a QoS flow depends on a dependent PDU set of the same QoS flow within the QoS flow. The intra-flow dependency includes a processing method indicating whether to discard the dependent PDU set of the QoS flow that depends on the dependent PDU set of the same QoS flow within the QoS flow when the dependent PDU set of the same QoS flow is discarded. For example, the processing method indicates whether to discard a data packet of a PDU set that depends on the discarded PDU set within the QoS flow if a PDU set is lost or discarded. ● Dependency within the PDU set for each QoS flow: ■The information (or configuration) of the intra-PDU set dependency indicates whether there is an intra-PDU set dependency in the PDU set of a QoS flow of the QoS flow group and how the dependency is handled. Specifically, the information (or configuration) of the intra-PDU set dependency indicates that a dependent PDU in the PDU set of a QoS flow depends on a dependent PDU in the same PDU set of the same QoS flow within the PDU set. The intra-PDU set dependency includes a handling method, indicating whether to discard the dependent PDU in the PDU set of the QoS flow that depends on the dependent PDU in the same PDU set of the same QoS flow when the dependent PDU in the same PDU set of the same QoS flow is discarded. For example, if a data packet in the PDU set is lost and other unsent data packets in the same PDU set depend on the data packet, the handling method indicates whether to discard the other unsent data packets in the same PDU set.

[0073] As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the following table may be introduced for each QoS flow. The hierarchy and characteristics of the IEs are shown in the following table. Table 4

[0074] In another embodiment, the dependencies between the QoS flows can be configured with different priorities, for example, an independent QoS flow is configured as the highest priority, and a dependent QoS flow is configured as a higher priority than the dependent QoS flow that depends on the dependent QoS flow. Specifically, the PDU set of the dependent QoS flow is configured as a higher priority than the PDU set of the dependent QoS flow that depends on the dependent QoS flow. As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the table below can be introduced for each QoS flow. The hierarchy and characteristics of the IE are shown in the table below. Table 5

[0075] According to the received QoS flow group configuration, the gNB (e.g., the gNB 20) configures the same number of DRBs as the number of QoS flows in the QoS flow group, and configures mapping of the QoS flows to the DRBs one by one, and these DRBs can be regarded as a DRB group. The gNB (e.g., the gNB 20) may perform the following operations: The inter-DRB dependency between different DRBs in the DRB group should be configured to align with the inter-QoS flow dependency between different QoS flows in the QoS flow group. The inter-DRB dependency is aligned with the inter-QoS flow dependency and indicates that the PDU set of a dependent DRB is dependent on the PDU set of the dependent DRB in the inter-DRB. ●The intra-DRB dependency of each DRB should be configured to be aligned with the intra-QoS flow dependency of the mapped QoS flow. As another embodiment, the inter-DRB dependency can be expressed as an inter-SDAP SDU or PDU group dependency, an inter-PDCP SDU or PDU group dependency, or an inter-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which can be regarded as SDUs or PDU groups of a protocol layer entity. The protocol layer entity may include one or more of the SDAP, PDCP and RLC protocol entities. The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that the dependent PDU set of a DRB depends on the dependent PDU set of the same DRB within the DRB. ●The intra-PDU set dependency of each DRB should be configured to be aligned with the intra-PDU set dependency of the mapped QoS flow. As another embodiment, the intra-PDU set dependency can be expressed as an intra-SDAP SDU or PDU group, an intra-PDCP SDU or PDU group, or an intra-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which can be regarded as SDUs or PDU groups of a protocol layer entity. The protocol layer entity may include one or more of the SDAP, PDCP and RLC protocol entities. The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS flow, and indicates that a dependent PDU in the PDU set of a DRB depends on a dependent PDU in the same PDU set of the same DRB within the PDU set.

[0076] Each of the DRBs should be configured according to the QoS requirements of the mapped QoS flow.

[0077] At the same time, the gNB (e.g., the gNB 20) configures these DRBs and the related configurations to the UE.

[0078] The configuration includes one or more of the following information: mapping of QoS flows to the DRBs, mapping of QoS flow groups to DRB groups, inter-DRB dependencies, intra-DRB dependencies, and intra-PDU set dependencies.

[0079] As an embodiment, based on the current RRC protocol, some new IEs highlighted below may be introduced for each DRB. The hierarchy and characteristics of the IEs are shown in the table below. Table 6 Table 7

[0080] like Figure 6 As shown, for QoS flow and QoS flow group configuration: ●For the service traffic flow 1, the QoS flows of the I / P / B frames in the GOP constitute the QoS flow group 1; the QoS flow 1 for the I frame is independent; the QoS flow 2 for the P frame depends on the QoS flow 1 among the QoS flows; the QoS flow 3 for the B frame depends on the QoS flow 1 and QoS flow 2 among the QoS flows; the QoS flow 2 is configured with intra-QoS flow dependency; the QoS flows 1 / 2 / 3 are all configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". ●For the service traffic flow 2, the QoS flows for PDU set types 1 / 2 / 3 constitute QoS flow group 2. The QoS flow 4 for PDU set type 1 is independent; the QoS flow 5 for PDU set type 2 and the QoS flow 6 for PDU set type 3 are both dependent on the QoS flow 4 between QoS flows. The QoS flow 5 and the QoS flow 6 are both configured with intra-QoS flow dependencies; all QoS flows are configured with intra-PDU set dependencies. The dependency handling mode can be configured as the value of "discard" or "no operation". ●In another embodiment, the QoS flow IDs of different QoS flow groups may be the same.

[0081] Mapping of the DRB groups to and from the QoS flow groups:

[0082] The sending device configures the mapping of QoS flow to DRB one by one as follows: ●QoS flow group 1 is mapped to DRB group 1 as follows: ■QoS flow ID=1 is mapped to DRB 3. ■QoS flow ID=2 is mapped to DRB 4. ■QoS flow ID=3 is mapped to DRB 5. ■DRB 3 is independent, DRB 4 depends on DRB 3 between DRBs, and DRB 5 depends on DRB 3 and DRB 4 between DRBs. DRB 4 is configured with intra-DRB dependency. The DRBs 3 / 4 / 5 are all configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". ●QoS flow group 2 is mapped to DRB group 2 as follows: ■QoS flow ID=4 is mapped to DRB 1. ■QoS flow ID=5 is mapped to DRB 2. ■QoS flow ID=6 is mapped to DRB 6. ■DRB 1 is independent. DRB 2 and DRB 6 are both dependent on DRB 1 in inter-DRB. DRB 2 and DRB 6 are both configured with intra-DRB dependency. All DRBs are configured with intra-PDU set dependency. The dependency handling mode can be configured with the value of "discard" or "no operation". ●In another embodiment, the DRB IDs of different DRB groups can be the same. 1.PDU set mapping and dependency application:

[0083] For transmission of the service traffic flow, the transmitting device (e.g., the gNB and / or the UE) receives data packets of a PDU set from a QoS flow and transmits the data packets to the corresponding DRB according to the mapping configuration. At the same time, for each data packet of the PDU set received in each DRB, the identifier of the PDU set and the related dependency information are also received in the transmitting device (e.g., the gNB and / or the UE) and associated with the data packet. As an embodiment, the identifier of the PDU set may be the sequence number (SN).

[0084] As shown in the table below, Figure 6 , Figure 7 and Figure 8 In the example, blocks with f=B represent PDUs in a PDU set associated with a B frame, blocks with f=P represent PDUs in a PDU set associated with a P frame, blocks with f=I represent PDUs in a PDU set associated with an I frame, blocks with t=1 represent PDUs in a PDU set associated with a PDU set type 1, blocks with t=2 represent PDUs in a PDU set associated with a PDU set type 2, and blocks with t=3 represent PDUs in a PDU set associated with a PDU set type 3. The variable i represents the PDU set ID of the PDU set. Table 8 variable definition f Frame Type t PDU Set Type <![CDATA[t d ]]> Dependent PDU set type ID i PDU Set ID <![CDATA[i d ]]> Dependent PDU set ID D DRB ID <![CDATA[D d ]]> Dependent DRB ID Q QoS Flow ID <![CDATA[Q d ]]> Dependent QoS flow ID q QoS sub-flow ID <![CDATA[q d ]]> Dependent QoS sub-flow ID

[0085] like Figure 6 As shown:

[0086] For the downlink, when a data packet in the form of a GTP-U PDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the gNB (e.g., the gNB 20) acts as the sending device, and the following contents apply.

[0087] For the uplink, when a data packet in the form of a high-layer SDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the UE (eg, the UE 10) acts as the sending device, and the following applies.

[0088] The identification of the PDU set and the related dependency information include one or more of the following information: the PDU set ID or the PDU set sequence number (SN), the dependent QoS flow ID and / or the related dependent PDU set ID or PDU set IDSN.

[0089] The sending device transmits the data packet as an SDU and / or a PDU to the mapped DRB according to the mapping configuration.

[0090] The sending device associates the identifier of the PDU set of the data packet and the related dependency with the SDU and / or PDU of the DRB. In the description herein, for simplicity, a data packet may be an SDU or a PDU. ●For DRB Group 1:

[0091] The PDU sets of the same QoS flow group are numbered uniformly, for example, based on the arrival time of the first data packet of the PDU set and the dependencies between the QoS flows.

[0092] The data packets of PDU set 1 of DRB 3 are independent; the data packets of PDU set 3 of DRB 4 depend on PDU set 1 of DRB 3 between DRBs; the data packets of PDU set 2 of DRB 5 depend on PDU set 1 of DRB 3 and PDU set 3 of DRB 4 between DRBs; the data packets of PDU set 5 of DRB 4 also depend on PDU set 4 of DRB 4 within the DRB; the data packets of each PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set. For DRB Group 2:

[0093] The PDU sets of each QoS flow are numbered separately, for example based on the arrival time of the first packet of the PDU set and the intra-QoS flow dependencies.

[0094] The data packets of PDU set 1 of DRB 1 are independent; the data packets of PDU set 2 of DRB 2 and the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 1 between DRBs; the data packets of PDU set 2 of DRB 2 depend on PDU set 1 of DRB 2 within the DRB; the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 6 within the DRB; the data packets of a PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set.

[0095] Based on the DRB group, the transmitting device (e.g., the gNB 20 and / or the UE) processes each PDU set or each data packet of the PDU set according to the dependency information configured for each DRB. The transmitting device may perform the following operations.

[0096] As an embodiment, for the dependency within a PDU set, if the processing mode value of the dependency configuration is "discard", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be discarded; if the processing mode value of the dependency configuration is "no operation", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be transmitted normally.

[0097] As an embodiment, for intra-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be transmitted normally. A DRB may include multiple PDU sets that depend on a PDU set within the DRB. As an embodiment, a configured or predefined number of consecutive PDU sets depend on this PDU set after following a PDU set. As Figure 6 As shown, for the DRB 4 of service traffic flow 1, the PDU set 5 depends on the PDU set 3 in the DRB. If the PDU set 3 is lost or discarded, and the dependency handling mode is configured as the value of "discard", the PDU set 5 should be discarded.

[0098] As an embodiment, for inter-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of a DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be transmitted normally. Figure 6As shown, the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 are both dependent on the PDU set 1 of DRB 1 between DRBs. If the PDU set 1 of DRB 1 is lost or discarded, and the dependency processing method is configured as the "discard" value, then the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 should both be discarded.

[0099] The above-mentioned discarding of the dependent data packet may occur in the PDCP or RLC entity of the DRB of the transmitting device (e.g., the gNB or the UE). If the discarding is determined in the PDCP entity, for the data packet transmitted to the RLC entity, the PDCP entity shall notify the relevant RLC entity to discard the relevant data packet.

[0100] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may consider that the priority of the data packet of the dependent PDU set is higher than the priority of the dependent PDU set that depends on the dependent PDU set, so as to schedule the data packets of the dependent PDU set and the dependent PDU set.

[0101] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the PDU set of all DRBs of a DRB group as a whole.

[0102] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the dependent PDU set and the data packets of the inter-DRB dependent PDU set that depends on the dependent PDU set as a whole with the same priority. Embodiment 2: Mapping QoS sub-flows in a QoS flow to a DRB group

[0103] In this embodiment, the service traffic flow of a service (e.g., an XR service) is identified in the 5GC (e.g., the 5GC300) as one or more different types of PDU sets, hereinafter referred to as PDU set types. Different types of PDU sets correspond to different QoS requirements, and each PDU set type corresponds to one of the QoS requirements. Each PDU set type is mapped to a QoS sub-flow in the 5GC, and all QoS sub-flows belonging to the same service traffic flow constitute a QoS flow. In the QoS flow, at least one QoS sub-flow is independent, and each other QoS sub-flow depends on at least one or more other QoS sub-flows.

[0104] In order to enable the gNB and / or the UE to map the QoS sub-flow to the DRB and support the service QoS requirement of the service traffic flow, an embodiment of the disclosed method includes the following process and the corresponding configuration information: 1.QoS sub-flow mapping and dependency configuration:

[0105] Based on the QoS flow of the service traffic flow, the 5GC configures the QoS sub-flows of the QoS flow and the dependencies between the QoS sub-flows, and provides the configuration to a gNB (e.g., gNB 20), as described below.

[0106] The 5GC configures multiple QoS sub-flows to the gNB within the QoS flow.

[0107] As an embodiment, each QoS sub-flow is uniquely identified by a QoS flow ID and a QoS sub-flow ID. The QoS sub-flows with the same QoS flow ID should be treated as a whole. For example, the application layer, packet data convergence protocol (PDCP) layer and / or radio link control (RLC) layer of the sending device and the receiving device treat the QoS sub-flows with the same QoS flow ID as a unit. Based on the current NGAP protocol, the new information element (IE) "QoS sub-flow identifier" can be introduced for each QoS sub-flow. The hierarchical structure and characteristics of the IE "QoS sub-flow identifier" are shown in the table below. Form 9

[0108] As an embodiment, the QoS flow further includes a plurality of QoS sub-flows, which have unique QoS sub-flow identifiers in the QoS flow. Based on the current NGAP protocol, some new IEs highlighted in the following table may be introduced for each QoS flow. The hierarchy and characteristics of the new IEs are shown in the following table. Table 10

[0109] The 5GC configures the dependency information of each QoS sub-flow in the QoS flow to the gNB. The dependency information may include one or more of the following: ● QoS inter-sub-flow dependencies between different QoS sub-flows in the QoS flow; ●Intra-QoS sub-flow dependencies for each QoS sub-flow; ● Intra-PDU set dependency for each QoS sub-flow.

[0110] The dependency information is described in detail below. ● QoS inter-sub-flow dependencies between different QoS sub-flows in the QoS flow: ■For each dependent QoS sub-flow, the information (or configuration) of the dependency between QoS sub-flows indicates which QoS sub-flow the dependent QoS sub-flow depends on. Specifically, the information (or configuration) of the dependency between QoS sub-flows indicates that the PDU set of the dependent QoS sub-flow depends on the PDU set of the dependent QoS sub-flow between QoS sub-flows. ■The information (or configuration) of the dependency between the QoS sub-streams may further include a processing method for the dependency. The dependency between the QoS sub-streams includes a processing method indicating whether to discard the dependent PDU set of the dependent QoS sub-stream when the dependent PDU set of the dependent QoS sub-stream is discarded. For example, if a PDU set is lost or discarded, the processing method indicates whether to discard the unsent data packets of the PDU set that depends on the lost or discarded PDU set between QoS sub-streams. A QoS sub-stream may depend on multiple other QoS sub-streams between QoS sub-streams. ●Intra-QoS sub-flow dependency for each QoS sub-flow: ■QoS intra-substream dependency means that a PDU set can depend on another PDU set in the same QoS substream. Specifically, the information (or configuration) of the intra-QoS substream dependency indicates that a dependent PDU set of a QoS substream depends on a dependent PDU set of the same QoS substream within the QoS substream. The information (or configuration) of the intra-QoS substream dependency indicates whether there is an intra-QoS substream dependency in a QoS substream and how the dependency is handled. The intra-QoS substream dependency includes a handling method indicating whether to discard the dependent PDU set of the QoS substream that depends on the dependent PDU set of the same QoS substream within the QoS substream when the dependent PDU set of the same QoS substream is discarded. For example, the handling method indicates whether to discard the data packets of the PDU set that depends on the discarded PDU set within the QoS substream if a PDU set is lost or discarded. ●Intra-PDU set dependency for each QoS subflow: ■The information (or configuration) of the intra-PDU set dependency indicates whether there is an intra-PDU set dependency in the PDU set of a QoS substream and how the dependency is handled. Specifically, the information (or configuration) of the intra-PDU set dependency indicates that a dependent PDU in the PDU set of a QoS substream depends on a dependent PDU in the same PDU set of the same QoS substream within the PDU set. The intra-PDU set dependency includes a handling method that indicates whether to discard the dependent PDU in the PDU set of the QoS substream that depends on the dependent PDU in the same PDU set of the same QoS substream within the PDU set when the dependent PDU in the same PDU set of the same QoS substream is discarded. For example, if a data packet in the PDU set is lost, and other unsent data packets in the same PDU set depend on the data packet, The processing mode indicates whether to discard the other unsent data packets in the same PDU set.

[0111] As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the following table may be introduced for each QoS flow. The hierarchy and characteristics of the IEs are shown in the following table. Table 11

[0112] Another embodiment is as follows: Table 12

[0113] In another embodiment, the dependencies between the QoS sub-streams can be configured with different priorities, for example, an independent QoS sub-stream is configured as the highest priority, and a dependent QoS sub-stream is configured as a higher priority than the dependent QoS sub-stream that depends on the dependent QoS sub-stream. Specifically, the PDU set of the dependent QoS sub-stream is configured as a higher priority than the PDU set of the dependent QoS sub-stream that depends on the dependent QoS sub-stream. As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the table below can be introduced for each QoS flow. The hierarchy and characteristics of the IE are shown in the table below. Form 13

[0114] According to the received QoS flow configuration, the gNB (e.g., the gNB 20) configures the same number of DRBs as the number of QoS sub-flows in the QoS flow, and configures mapping of the QoS sub-flows to the DRBs one by one, and these DRBs can be regarded as a DRB group. The gNB (e.g., the gNB 20) may perform the following operations: The inter-DRB dependency between different DRBs in the DRB group should be configured to align with the inter-QoS sub-flow dependency between different QoS sub-flows in the QoS flow. The inter-DRB dependency is aligned with the inter-QoS sub-flow dependency and indicates that the PDU set of a dependent DRB depends on the PDU set of the dependent DRB between DRBs. ●The intra-DRB dependency of each DRB should be configured to be aligned with the intra-QoS sub-flow dependency of the mapped QoS sub-flow. As another embodiment, the inter-DRB dependency can be expressed as an inter-SDAP SDU or PDU group dependency, an inter-PDCP SDU or PDU group dependency, or an inter-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which can be regarded as SDUs or PDU groups of a protocol layer entity. The protocol layer entity may include one or more of the SDAP, PDCP and RLC protocol entities. The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that the dependent PDU set of a DRB depends on the dependent PDU set of the same DRB within the DRB. ●The intra-PDU set dependency of each DRB should be configured to be aligned with the intra-PDU set dependency of the mapped QoS subflow. As another embodiment, the intra-PDU set dependency can be expressed as an intra-SDAP SDU or PDU group, an intra-PDCP SDU or PDU group, or an intra-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which can be regarded as SDUs or PDU groups of a protocol layer entity. The protocol layer entity may include one or more of the SDAP, PDCP and RLC protocol entities. The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS subflow, and indicates that the dependent PDU in the PDU set of one DRB depends on the dependent PDU in the same PDU set of the same DRB within the PDU set.

[0115] Each of the DRBs shall be configured according to the QoS requirements of the mapped QoS sub-flow.

[0116] At the same time, the gNB (e.g., the gNB 20) configures these DRBs and the related configurations to the UE.

[0117] The configuration includes one or more of the following information: mapping of QoS sub-flows to the DRBs, mapping of QoS flows to DRB groups, inter-DRB dependencies, intra-DRB dependencies, and intra-PDU set dependencies.

[0118] As an embodiment, based on the current RRC protocol, some new IEs highlighted below may be introduced for each DRB. The hierarchy and characteristics of the IEs are shown in the table below. Table 14 Form 15

[0119] like Figure 7 As shown, for QoS sub-flow and QoS flow configuration: ●For the service traffic flow 1, the QoS substreams of the I / P / B frames in the GOP constitute QoS flow 1, the QoS substream 1 for the I frame is independent, the QoS substream 2 for the P frame depends on the QoS substream 1 among QoS substreams, and the QoS substream 3 for the B frame depends on the QoS substream 1 and QoS substream 2 among QoS substreams; the QoS substream 2 is configured with intra-QoS substream dependency; the QoS substreams 1 / 2 / 3 are all configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". ●For the service traffic flow 2, the QoS subflows for PDU set types 1 / 2 / 3 constitute QoS flow 2, the QoS subflow 4 for PDU set type 1 is independent, the QoS subflow 5 for PDU set type 2 and the QoS subflow 6 for PDU set type 3 are both dependent on the QoS subflow 4 between QoS subflows; the QoS subflow 5 and the QoS subflow 6 are both configured with intra-QoS subflow dependencies; all QoS flows are configured with intra-PDU set dependencies. The dependency handling mode can be configured as the value of "discard" or "no operation". In another embodiment, the QoS sub-flow IDs of different QoS flows may be the same.

[0120] The mapping of the DRB groups and the QoS flows from:

[0121] The sending device configures the mapping of QoS sub-flows to DRBs one-to-one as follows: QoS flow 1 is mapped to DRB group 1 as follows: ■QoS sub-flow ID=1 is mapped to DRB 3. ■QoS sub-flow ID=2 is mapped to DRB 4. ■QoS sub-flow ID=3 is mapped to DRB 5. ■DRB 3 is independent, DRB 4 depends on DRB 3 between DRBs, and DRB 5 depends on DRB 3 and DRB 4 between DRBs; DRB 4 is configured with intra-DRB dependency; and DRB 3 / 4 / 5 are all configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". QoS flow 2 is mapped to DRB group 2 as follows: ■QoS sub-flow ID=4 is mapped to DRB 1. ■QoS sub-flow ID=5 is mapped to DRB 2. ■QoS sub-flow ID=6 is mapped to DRB 6. ■DRB 1 is independent, DRB 2 and DRB 6 are dependent on DRB 1 in inter-DRB mode; DRB 2 and DRB 6 are configured with intra-DRB dependency; all DRBs are configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". ●In another embodiment, the DRB IDs of different DRB groups can be the same. 1.PDU set mapping and dependency application:

[0122] For transmission of the service traffic flow, the transmitting device (e.g., the gNB and / or the UE) receives data packets of the PDU set from the QoS subflow and transmits the data packets to the corresponding DRB according to the mapping configuration. At the same time, for each data packet of the PDU set received in each DRB, the identifier of the PDU set and the related dependency information are also received in the transmitting device (e.g., the gNB and / or the UE) and associated with the data packet. As an embodiment, the identifier of the PDU set can be the sequence number (SN).

[0123] like Figure 7 As shown:

[0124] For the downlink, when a GTP-U PDU is received as a data packet, the gNB (e.g., the gNB 20) acts as the sending device based on the information in the GTP-U PDU, and the following contents apply.

[0125] For the uplink, when a data packet is received from a higher layer, the UE (eg, the UE 10) acts as the sending device, and the following applies.

[0126] For the downlink, when a data packet in the form of a GTP-U PDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the gNB (e.g., the gNB 20) acts as the sending device, and the following contents apply.

[0127] For the uplink, when a data packet in the form of a high-layer SDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the UE (eg, the UE 10) acts as the sending device, and the following applies.

[0128] The identification of the PDU set and the related dependency information include one or more of the following information: the PDU set ID or the PDU set sequence number (SN), the dependent QoS sub-flow ID and / or the related dependent PDU set ID or PDU set ID SN.

[0129] The sending device transmits the data packet as an SDU and / or a PDU to the mapped DRB according to the mapping configuration.

[0130] The sending device associates the identifier of the PDU set of the data packet and the related dependency with the SDU and / or PDU of the DRB. In the description herein, for simplicity, a data packet may be an SDU or a PDU. ●For DRB Group 1:

[0131] The PDU sets of the same QoS flow are numbered uniformly, for example, based on the arrival time of the first data packet of the PDU set and the dependencies between the QoS flows.

[0132] The data packets of PDU set 1 of DRB 3 are independent; the data packets of PDU set 3 of DRB 4 depend on PDU set 1 of DRB 3 between DRBs; the data packets of PDU set 2 of DRB 5 depend on PDU set 1 of DRB 3 and PDU set 3 of DRB 4 between DRBs; the data packets of PDU set 5 of DRB 4 also depend on PDU set 4 of DRB 4 within the DRB; the data packets of each PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set. For DRB Group 2:

[0133] The PDU sets of each QoS sub-flow of a QoS flow are numbered separately, for example based on the arrival time of the first data packet of the PDU set and the intra-QoS flow dependency.

[0134] The data packets of PDU set 1 of DRB 1 are independent; the data packets of PDU set 2 of DRB 2 and the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 1 between DRBs; the data packets of PDU set 2 of DRB 2 depend on PDU set 1 of DRB 2 within the DRB; the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 6 within the DRB; the data packets of a PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set.

[0135] Based on the DRB group, the transmitting device (e.g., the gNB 20 and / or the UE) processes each PDU set or each data packet of the PDU set according to the dependency information configured for each DRB. The transmitting device may perform the following operations.

[0136] As an embodiment, for the dependency within a PDU set, if the processing mode value of the dependency configuration is "discard", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be discarded in the PDCP entity of the DRB; if the processing mode value of the dependency configuration is "no operation", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be transmitted normally.

[0137] As an embodiment, for intra-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be transmitted normally. A DRB may include multiple PDU sets that depend on a PDU set within the DRB. As an embodiment, a configured or predefined number of consecutive PDU sets depend on this PDU set after following a PDU set. As Figure 7 As shown, for the DRB 4 of service traffic flow 1, the PDU set 5 depends on the PDU set 3 in the DRB. If the PDU set 3 is lost or discarded, and the dependency handling mode is configured as the value of "discard", the PDU set 5 should be discarded.

[0138] As an embodiment, for inter-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of a DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be transmitted normally. Figure 7 As shown, the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 are both dependent on the PDU set 1 of DRB 1 between DRBs. If the PDU set 1 of DRB 1 is lost or discarded, and the dependency processing method is configured as the "discard" value, then the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 should both be discarded.

[0139] The above-mentioned discarding of the dependent data packet may occur in the PDCP or RLC entity of the DRB of the transmitting device (e.g., the gNB or the UE). If the discarding is determined in the PDCP entity, for the data packet transmitted to the RLC entity, the PDCP entity shall notify the relevant RLC entity to discard the relevant data packet.

[0140] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may consider that the priority of the data packet of the dependent PDU set is higher than the priority of the dependent PDU set that depends on the dependent PDU set, so as to schedule the data packets of the dependent PDU set and the dependent PDU set.

[0141] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the PDU set of all DRBs of a DRB group as a whole.

[0142] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the dependent PDU set and the data packets of the inter-DRB dependent PDU set that depends on the dependent PDU set as a whole with the same priority. Embodiment 3: Mapping of PDU set types in QoS flows to DRB groups

[0143] In this embodiment, the service traffic flow of a service (e.g., an XR service) is identified in the 5GC (e.g., the 5GC300) as one or more different types of PDU sets, hereinafter referred to as PDU set types. Different types of PDU sets correspond to different QoS requirements, and each PDU set type corresponds to one of the QoS requirements. All these PDU set types are mapped to one QoS flow in the 5GC. However, each data packet of different PDU set types in the QoS flow is associated with unique identification information (or configuration) of the PDU set type.

[0144] In order to enable the gNB and / or the UE to map the different PDU set types to DRBs and support the XR service QoS requirements of the service traffic flow, an embodiment of the disclosed method includes the following process and the corresponding configuration information: 2.PDU set type mapping and dependency configuration:

[0145] Based on the QoS flow of the service traffic flow, the 5GC configures the PDU set type of the QoS flow and the dependency between the PDU set types, and provides the configuration to a gNB (e.g., gNB 20), as described below.

[0146] The 5GC configures multiple PDU set types to the gNB within the QoS flow.

[0147] As an embodiment, each PDU set type is uniquely identified by a QoS flow ID and a PDU set type ID. The PDU set type with the same QoS flow ID should be treated as a whole. For example, the application layer, packet data convergence protocol (PDCP) layer and / or radio link control (RLC) layer of the sending device and the receiving device treat the PDU set type with the same QoS flow ID as a unit. Based on the current NGAP protocol, the new information element (IE) "PDU set type identifier" can be introduced for each PDU set type. The hierarchy and characteristics of the IE "PDU set type identifier" are shown in the table below. Table 16

[0148] As an embodiment, the QoS flow further includes a plurality of PDU set types, which have unique PDU set type identifiers in the QoS flow. Based on the current NGAP protocol, some new IEs highlighted in the table below can be introduced for each QoS flow. The hierarchy and characteristics of the new IEs are shown in the table below. Table 17

[0149] The 5GC configures the dependency information of each PDU set type in the QoS flow to the gNB. The dependency information may include one or more of the following: ● Inter-PDU Set Type dependencies between different PDU Set Types in the QoS flow; ●Intra-PDU set type dependencies for each PDU set type; ● Intra-PDU set dependencies for each PDU set type.

[0150] The dependency information is described in detail below. ● Inter-PDU Set Type dependencies between different PDU Set Types in the QoS flow: ■For each dependent PDU set type, the information (or configuration) of the inter-PDU set type dependency indicates which PDU set type the dependent PDU set type depends on. Specifically, the information (or configuration) of the inter-PDU set type dependency indicates that the PDU set of the dependent PDU set type depends on the PDU set of the dependent PDU set type between PDU set types. ■The information (or configuration) of the dependency between the PDU set types may further include a processing method of the dependency. The dependency between the PDU set types includes a processing method indicating whether to discard the dependent PDU set of the dependent PDU set type when the dependent PDU set of the dependent PDU set type is discarded. For example, if a PDU set is lost or discarded, the processing method indicates whether to discard the unsent data packets of the PDU set that depends on the lost or discarded PDU set between PDU set types. A PDU set type may depend on multiple other PDU set types between PDU set types. ●Intra-PDU set type dependencies for each PDU set type: ■Intra-PDU set type dependency means that a PDU set can depend on another PDU set in the same PDU set type. The information (or configuration) of the intra-PDU set type dependency indicates whether there is an intra-PDU set type dependency in a PDU set type and how the dependency is handled. Specifically, the information (or configuration) of the intra-PDU set type dependency indicates that a dependent PDU set of a PDU set type depends on a dependent PDU set of the same PDU set type within the PDU set type. The intra-PDU set type dependency includes a handling method, indicating whether to discard the dependent PDU set of the PDU set type that depends on the dependent PDU set of the same PDU set type within the PDU set type when the dependent PDU set of the same PDU set type is discarded. For example, the handling method indicates whether to discard the data packet of the PDU set that depends on the discarded PDU set within the PDU set type if a PDU set is lost or discarded. ●Intra-PDU set dependencies for each PDU set type: ■The information (or configuration) of the intra-PDU set dependency indicates whether there is an intra-PDU set dependency in a PDU set of a PDU set type and how the dependency is handled. Specifically, the information (or configuration) of the intra-PDU set dependency indicates that a dependent PDU in a PDU set of a PDU set type depends on a dependent PDU in the same PDU set of the same PDU set type within the PDU set. The intra-PDU set dependency includes a handling method, indicating whether to discard the dependent PDU in the PDU set of the PDU set type that depends on the dependent PDU in the same PDU set of the same PDU set type within the PDU set when the dependent PDU in the same PDU set of the same PDU set type is discarded. For example, if a data packet in the PDU set is lost, and other unsent data packets in the same PDU set depend on the data packet, the handling method indicates whether to discard the other unsent data packets in the same PDU set.

[0151] As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the following table may be introduced for each QoS flow. The hierarchy and characteristics of the IEs are shown in the following table. Form 18

[0152] Another embodiment is as follows: Table 19

[0153] In another embodiment, the dependencies between the PDU set types can be configured with different priorities, for example, an independent PDU set type is configured as the highest priority, and a dependent PDU set type is configured as a higher priority than the dependent PDU set type that depends on the dependent PDU set type. As an embodiment, based on the current NGAP protocol, some new IEs highlighted in the following table can be introduced for each QoS flow. The hierarchy and characteristics of the IE are shown in the following table. Form 20

[0154] According to the received QoS flow configuration, the gNB (e.g., the gNB 20) configures the same number of DRBs as the number of PDU set types in the QoS flow, and configures mappings of the PDU set types to the DRBs one by one, and these DRBs can be regarded as a DRB group. The gNB (e.g., the gNB 20) may perform the following operations: The inter-DRB dependencies between different DRBs in the DRB group shall be configured to align with the inter-PDU set type dependencies between different PDU set types in the QoS flow. The inter-DRB dependencies are aligned with the inter-PDU set type dependencies and indicate that the PDU set of a dependent DRB is dependent on the PDU set of the dependent DRB in the inter-DRB. ●The intra-DRB dependency of each DRB should be configured to be aligned with the intra-PDU set type dependency of the mapped PDU set type. As another embodiment, the inter-DRB dependency can be expressed as an inter-SDAP SDU or PDU group dependency, an inter-PDCP SDU or PDU group dependency, or an inter-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which may be regarded as SDUs or PDU groups of a protocol layer entity. The protocol layer entity may include one or more of the SDAP, PDCP and RLC protocol entities. The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that the dependent PDU set of a DRB depends on the dependent PDU set of the same DRB within the DRB. The intra-PDU set dependency of each DRB should be configured to be aligned with the intra-PDU set dependency of the mapped PDU set type. As another embodiment, the intra-PDU set dependency can be expressed as an intra-SDAP SDU or PDU group, an intra-PDCP SDU or PDU group, or an intra-RLC SDU or PDU group dependency, because a PDU set may include multiple data packets, which can be regarded as SDUs or PDU groups of protocol layer entities. The protocol layer entity may include one or more of SDAP, PDCP and RLC protocol entities. The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each PDU set type, and indicates that a dependent PDU in the PDU set of a DRB depends on a dependent PDU in the same PDU set of the same DRB within the PDU set.

[0155] Each of the DRBs shall be configured according to the QoS requirements of the mapped PDU set type.

[0156] At the same time, the gNB (e.g., the gNB 20) configures these DRBs and the related configurations to the UE.

[0157] The configuration includes one or more of the following information: mapping of PDU set type to the DRB, mapping of QoS flow to DRB group, inter-DRB dependency, intra-DRB dependency, and intra-PDU set dependency.

[0158] As an embodiment, based on the current RRC protocol, some new IEs highlighted below may be introduced for each DRB. The hierarchy and characteristics of the IEs are shown in the table below. Form 21 Form 22

[0159] like Figure 8 As shown, for PDU set type and QoS flow configuration: ●For the service traffic flow 1, the PDU set types of I / P / B frames in the GOP constitute QoS flow 1, the PDU set type 1 for I frames is independent, the PDU set type 2 for P frames depends on the PDU set type 1 between PDU set types, and the PDU set type 3 for B frames depends on the PDU set type 1 and PDU set type 2 between PDU set types; the PDU set type 2 is configured with intra-PDU set type dependency; the PDU set types 1 / 2 / 3 are all configured with intra-PDU set dependencies. The dependency handling method can be configured as the value of "discard" or "no operation". ●For the service traffic flow 2, the PDU set types used for PDU set types 1 / 2 / 3 constitute QoS flow 2, the PDU set type 4 used for PDU set type 1 is independent, the PDU set type 5 used for PDU set type 2 and the PDU set type 6 used for PDU set type 3 are both dependent on the PDU set type 4 between PDU set types; the PDU set type 5 and the PDU set type 6 are both configured with intra-PDU set type dependencies; all QoS flows are configured with intra-PDU set dependencies. The dependency handling mode can be configured as the value of "discard" or "no operation". ●In another embodiment, the PDU set type IDs of different QoS flows may be the same.

[00160] The mapping of the DRB groups and the QoS flows: ●

[00161] The sending device configures the mapping of PDU set types to DRBs one by one as follows: QoS flow 1 is mapped to DRB group 1 as follows: ■PDU set type ID=1 is mapped to DRB 3. ■PDU set type ID=2 is mapped to DRB 4. ■PDU set type ID=3 is mapped to DRB 5. ■DRB 3 is independent, DRB 4 depends on DRB 3 between DRBs, and DRB 5 depends on DRB 3 and DRB 4 between DRBs; DRB 4 is configured with intra-DRB dependency; and DRB 3 / 4 / 5 are all configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". QoS flow 2 is mapped to DRB group 2 as follows: ■PDU set type ID=4 is mapped to DRB 1. ■PDU set type ID=5 is mapped to DRB 2. ■PDU set type ID=6 is mapped to DRB 6. ■DRB 1 is independent, DRB 2 and DRB 6 are dependent on DRB 1 in inter-DRB mode; DRB 2 and DRB 6 are configured with intra-DRB dependency; all DRBs are configured with intra-PDU set dependency. The dependency handling mode can be configured as the value of "discard" or "no operation". ●In another embodiment, the DRB IDs of different DRB groups can be the same. 3.PDU set mapping and dependency application:

[0162] For the transmission of the service traffic flow, the transmitting device (e.g., the gNB and / or the UE) receives a data packet of a PDU set from a PDU set type and transmits the data packet to the corresponding DRB according to the mapping configuration. At the same time, for each data packet of the PDU set received in each DRB, the identifier of the PDU set and the related dependency information are also received in the transmitting device (e.g., the gNB and / or the UE) and associated with the data packet. As an embodiment, the identifier of the PDU set can be the sequence number (SN).

[0163] like Figure 8 As shown:

[0164] For the downlink, when a GTP-U PDU is received as a data packet, the gNB (e.g., the gNB 20) acts as the sending device based on the information in the GTP-U PDU, and the following contents apply.

[0165] For the uplink, when a data packet is received from a higher layer, the UE (eg, the UE 10) acts as the sending device, and the following applies.

[0166] For the downlink, when a data packet in the form of a GTP-U PDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the gNB (e.g., the gNB 20) acts as the sending device, and the following contents apply.

[0167] For the uplink, when a data packet in the form of a high-layer SDU is received, the data packet is associated with the identifier of the PDU set and the related dependency information, and the UE (eg, the UE 10) acts as the sending device, and the following applies.

[0168] The identification of the PDU set and the related dependency information include one or more of the following information: the PDU set type ID, the PDU set ID or the PDU set sequence number (SN), the dependent PDU set type ID and / or the related dependent PDU set ID or PDU set ID SN.

[0169] The sending device transmits the data packet as an SDU and / or a PDU to the DRB according to the mapping configuration.

[0170] The sending device associates the identifier of the PDU set of the data packet and the related dependency with the SDU and / or PDU of the DRB. In the description herein, for simplicity, a data packet may be an SDU or a PDU. ●For DRB Group 1

[0171] The PDU sets of the same QoS flow are numbered uniformly, for example, based on the arrival time of the first data packet of the PDU set and the dependencies between the QoS flows.

[0172] The data packets of PDU set 1 of DRB 3 are independent; the data packets of PDU set 3 of DRB 4 depend on PDU set 1 of DRB 3 between DRBs; the data packets of PDU set 2 of DRB 5 depend on PDU set 1 of DRB 3 and PDU set 3 of DRB 4 between DRBs; the data packets of PDU set 5 of DRB 4 also depend on PDU set 4 of DRB 4 within the DRB; the data packets of each PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set. For DRB Group 2:

[0173] The PDU sets of each PDU set type of a QoS flow are numbered separately, for example based on the arrival time of the first packet of the PDU set and the intra-QoS flow dependencies.

[0174] The data packets of PDU set 1 of DRB 1 are independent; the data packets of PDU set 2 of DRB 2 and the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 1 between DRBs; the data packets of PDU set 2 of DRB 2 depend on PDU set 1 of DRB 2 within the DRB; the data packets of PDU set 2 of DRB 6 depend on PDU set 1 of DRB 6 within the DRB; the data packets of a PDU set of all DRBs depend on other data packets of the same PDU set within the PDU set.

[0175] Based on the DRB group, the transmitting device (e.g., the gNB 20 and / or the UE) processes each PDU set or each data packet of the PDU set according to the dependency information configured for each DRB. The transmitting device may perform the following operations.

[0176] As an embodiment, for the dependency within a PDU set, if the processing mode value of the dependency configuration is "discard", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be discarded in the PDCP entity of the DRB; if the processing mode value of the dependency configuration is "no operation", if a data packet of a PDU set of this DRB is lost, the unsent data packet of the same PDU set should be transmitted normally.

[0177] As an embodiment, for intra-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set within the DRB should be transmitted normally. A DRB may include multiple PDU sets that depend on a PDU set within the DRB. As an embodiment, a configured or predefined number of consecutive PDU sets depend on this PDU set after following a PDU set. As Figure 8 As shown, for the DRB 4 of service traffic flow 1, the PDU set 5 depends on the PDU set 3 in the DRB. If the PDU set 3 is lost or discarded, and the dependency handling mode is configured as the value of "discard", the PDU set 5 should be discarded.

[0178] As an embodiment, for inter-DRB dependency, if the processing mode value of the dependency configuration is "discard", if a PDU set of a DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be discarded. If the processing mode value of the dependency configuration is "no operation", if a PDU set of this DRB is lost or discarded, the unsent data packets of the PDU set that depends on the lost or discarded PDU set between DRBs should be transmitted normally. Figure 8 As shown, the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 are both dependent on the PDU set 1 of DRB 1 between DRBs. If the PDU set 1 of DRB 1 is lost or discarded, and the dependency processing method is configured as the "discard" value, then the PDU set 1 of DRB 2 and the PDU set 1 of DRB 6 should both be discarded.

[0179] The above-mentioned discarding of the dependent data packet may occur in the PDCP or RLC entity of the DRB of the transmitting device (e.g., the gNB or the UE). If the discarding is determined in the PDCP entity, for the data packet transmitted to the RLC entity, the PDCP entity shall notify the relevant RLC entity to discard the relevant data packet.

[0180] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may consider that the priority of the data packet of the dependent PDU set is higher than the priority of the dependent PDU set that depends on the dependent PDU set, so as to schedule the data packets of the dependent PDU set and the dependent PDU set.

[0181] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the PDU set of all DRBs of a DRB group as a whole.

[0182] As an embodiment, the MAC entity in the sending device (e.g., the gNB or the UE) may schedule the data packets of the dependent PDU set and the data packets of the inter-DRB dependent PDU set that depends on the dependent PDU set as a whole with the same priority.

[0183] Fig. 9 10 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. The embodiments described herein may be implemented into the system using any appropriately configured hardware and / or software. FIG. 10 shows the system 700, including a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage device 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, which are coupled to each other as shown.

[0184] The processing unit 730 may include circuits, such as but not limited to one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (such as graphics processors and application processors). The processor may be coupled to the memory / storage device and configured to execute instructions stored in the memory / storage device to support various applications and / or operating systems running on the system.

[0185] The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuit may support communication with one or more wireless technologies. For example, in some embodiments, the baseband circuit may support communication with 5G New Air (NR), LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and other wireless metropolitan area networks (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). An embodiment in which the baseband circuit is configured to support wireless communications of multiple wireless protocols may be referred to as a multi-mode baseband circuit. In various embodiments, the baseband circuit 720 may include circuits for processing signals that are not strictly regarded as baseband frequencies. For example, in some embodiments, the baseband circuit may include circuits for processing intermediate frequency signals between the baseband frequency and the radio frequency.

[0186] In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a notebook computing device, a tablet computing device, a mini notebook, a netbook, a smart phone, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0187] The described embodiments of the present disclosure may employ a combination of techniques / processes in 3GPP specifications to create a final product.

[0188] If the software functional unit is implemented as a product and used and sold, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution proposed in the present disclosure can be essentially or partially implemented in the form of a software product. Alternatively, a part of the technical solution that is beneficial to the prior art can be implemented in the form of a software product. The computer software product is stored in a storage medium and includes multiple instructions for enabling a computing device (such as a personal computer, a server, or a network device) to run all or part of the steps disclosed in the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other medium capable of storing program code.

[0189] While the present disclosure has been described in connection with what are presently considered to be the most practical and preferred embodiments, it is to be understood that the disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements within the scope thereof without departing from the broadest interpretation of the appended claims.

Claims

1. A wireless communication method, which may be performed in a base station, comprising: Receive a protocol data unit (PDU) set of a first frame type served in a first quality of service (QoS) bearer, and receive a PDU set of a second frame type of the service in a second QoS bearer; transmit the PDU set of the first frame type of the service through a first dynamic radio bearer (DRB), and transmit the PDU set of the second frame type of the service through a second DRB; wherein at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type is reflected in the QoS configuration of the first QoS bearer and the second QoS bearer and the DRB configuration of the first DRB and the second DRB.

2. The method of claim 1, wherein the first frame type is one of an I frame, a P frame, and a B frame, and the second frame type is another one of an I frame, a P frame, and a B frame.

3. The method of claim 1, wherein the first QoS bearer comprises a first QoS The first QoS flow having a flow identifier (ID), the second QoS bearer including a first QoS flow having a second QoS A second QoS flow having a flow ID, wherein the first QoS flow and the second QoS flow constitute a first QoS flow group having a first QoS flow group ID.

4. The method of claim 3, wherein the first QoS flow and the second QoS flow are mapped to one or more DRBs according to the DRB configuration.

5. The method of claim 4, wherein the plurality of DRBs constitute a DRB group.

6. The method of claim 3, wherein in the QoS configuration, the at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type comprises one or more of the following: QoS inter-flow dependencies between different QoS flows in the QoS flow group; QoS intra-flow dependencies for each QoS flow; Intra-PDU set dependencies for each QoS flow; The QoS inter-flow dependency indicates that the PDU set of the dependent QoS flow depends on the PDU set of the dependent QoS flow between QoS flows; The intra-QoS flow dependency indicates that a dependent PDU set of a QoS flow depends on a dependent PDU set of the same QoS flow within the QoS flow; The intra-PDU set dependency indicates that a dependent PDU in a PDU set of a QoS flow depends within the PDU set on a dependent PDU in the same PDU set of the same QoS flow.

7. The method of claim 6, wherein the inter-QoS flow dependency includes a processing mode indicating whether to discard the dependent PDU set of the dependent QoS flow when the dependent PDU set of the dependent QoS flow is discarded; The intra-QoS flow dependency includes a processing mode indicating whether to discard the dependent PDU set of the QoS flow that depends on the dependent PDU set of the same QoS flow within the QoS flow when the dependent PDU set of the same QoS flow is discarded; The intra-PDU set dependency includes a processing method indicating whether to discard the dependent PDU in the PDU set of the QoS flow that depends on the dependent PDU in the same PDU set of the same QoS flow within the PDU set when the dependent PDU in the same PDU set of the same QoS flow is discarded.

8. The method of claims 4 and 6, wherein in the DRB configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type comprises one or more of the following: Inter-DRB dependencies between different DRBs; Intra-DRB dependencies for each DRB; Dependencies within the PDU set of each DRB; wherein the inter-DRB dependency is aligned with the inter-QoS flow dependency and indicates that the PDU set of the dependent DRB depends on the PDU set of the dependent DRB between the DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS flow, and indicates that a dependent PDU in the PDU set of a DRB depends within the PDU set on the dependent PDU in the same PDU set of the same DRB.

9. The method of claim 1, wherein the first QoS bearer comprises a first QoS The first QoS sub-flow and the second QoS sub-flow constitute a third QoS flow with a third QoS flow ID.

10. The method of claim 9, wherein the first QoS sub-flow and the second QoS sub-flow are mapped to one or more DRBs according to the DRB configuration. The method of claim 10 , wherein the plurality of DRBs constitute a DRB group.

12. The method of claim 9, wherein in the QoS configuration, the at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type comprises one or more of the following: QoS inter-sub-flow dependencies between different QoS sub-flows in the third QoS flow; QoS intra-subflow dependencies for each QoS subflow; Intra-PDU dependency for each QoS sub-flow; The dependency between QoS sub-flows indicates that the PDU set of the dependent QoS sub-flow depends on the PDU set of the dependent QoS sub-flow between sub-QoS flows; The intra-QoS sub-flow dependency indicates that a dependent PDU set of a QoS sub-flow depends on a dependent PDU set of the same QoS sub-flow within the QoS sub-flow; and The intra-PDU dependency indicates the dependent PDUs in the PDU set of a QoS sub-flow. The dependent PDU in the same PDU set that depends on the same QoS sub-flow.

13. The method of claim 12, wherein the inter-QoS sub-flow dependency includes a processing mode indicating whether to discard the dependent PDU set of the dependent QoS sub-flow when the dependent PDU set of the dependent QoS sub-flow is discarded; The intra-QoS sub-flow dependency includes a processing mode indicating whether to discard the dependent PDU set of the QoS sub-flow that depends on the dependent PDU set of the same QoS sub-flow within the QoS sub-flow when the dependent PDU set of the same QoS sub-flow is discarded; and The intra-PDU set dependency includes a processing method indicating whether to discard the dependent PDU in the PDU set of the QoS substream that depends on the dependent PDU in the same PDU set of the same QoS substream within the PDU set when the dependent PDU in the same PDU set of the same QoS substream is discarded.

14. The method of claims 10 and 12, wherein in the DRB configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type comprises one or more of the following: Inter-DRB dependencies between different DRBs; Intra-DRB dependencies for each DRB; Dependencies within the PDU set of each DRB; wherein the inter-DRB dependency is aligned with the inter-QoS sub-flow dependency, and indicates that the PDU set that depends on the DRB depends on the PDU set of the dependent DRB between the DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; and The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each QoS sub-flow, and indicates that a dependent PDU in the PDU set of a DRB depends within the PDU set on the dependent PDU in the same PDU set of the same DRB.

15. The method of claim 1, wherein the first QoS bearer comprises a first PDU set type having a first PDU set type identifier (ID), the second QoS bearer comprises a second PDU set type having a second PDU set type ID, and the first PDU set type and the second PDU set type constitute a third QoS flow having a third QoS flow ID.

16. The method of claim 15, wherein the first PDU set type and the second PDU set type are mapped to one or more DRBs according to the DRB configuration.

17. The method of claim 16, wherein the plurality of DRBs constitute a DRB group.

18. The method of claim 15, wherein in the QoS configuration, the at least one dependency between the set of PDUs of the first frame type and the set of PDUs of the second frame type comprises one or more of the following: inter-PDU set type dependencies between different PDU set types in the third QoS flow; Intra-PDU set type dependencies for each PDU set type; Intra-PDU set dependencies for each PDU set type; The inter-PDU set type dependency indicates that the PDU set that depends on the PDU set type is in the PDU PDU sets of set types that depend on the PDU set type that is dependent on; The intra-PDU set type dependency indicates that a dependent PDU set of a PDU set type is dependent on a dependent PDU set of the same PDU set type within the PDU set type; and The intra-PDU set dependency indicates that a dependent PDU in a PDU set of a PDU set type depends within the PDU set on a dependent PDU in the same PDU set of the same PDU set type.

19. The method of claim 18, wherein the inter-PDU set type dependency includes a processing mode indicating whether to discard the dependent PDU set of the dependent PDU set type when the dependent PDU set of the dependent PDU set type is discarded; The intra-PDU set type dependency includes a processing mode indicating whether to discard the dependent PDU set of the PDU set type that depends on the dependent PDU set of the same PDU set type within the PDU set type when the dependent PDU set of the same PDU set type is discarded; and The intra-PDU set dependency includes a processing method indicating whether to discard the dependent PDU in the PDU set type of the PDU set that depends on the dependent PDU in the same PDU set of the same PDU set type within the PDU set when the dependent PDU in the same PDU set of the same PDU set type is discarded.

20. The method of claims 16 and 18, wherein in the DRB configuration, the at least one dependency between the PDU set of the first frame type and the PDU set of the second frame type comprises one or more of the following: Inter-DRB dependencies between different DRBs; Intra-DRB dependencies for each DRB; Dependencies within the PDU set of each DRB; wherein the inter-DRB dependency is aligned with the inter-PDU set type dependency, and indicates that the PDU set of the dependent DRB depends on the PDU set of the dependent DRB between DRBs; The intra-DRB dependency is aligned with the intra-QoS flow dependency and indicates that a dependent PDU set of a DRB is dependent on a dependent PDU set of the same DRB within the DRB; and The intra-PDU set dependency of each DRB is aligned with the intra-PDU set dependency of each PDU set type, and indicates that a dependent PDU in a PDU set of a DRB depends within the PDU set on a dependent PDU in the same PDU set of the same DRB.

21. The method of claim 1, wherein the priority of a PDU in a dependent PDU set is higher than that of a dependent PDU set.

22. The method of claim 1, wherein the PDU set dependent on the QoS flow is configured to have a higher priority than the dependent QoS flow.

23. A wireless communication device, comprising: A processor configured to call and run a computer program stored in a memory so that a device equipped with the processor executes the method according to any one of claims 1 to 22.

24. A chip, comprising: A processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 22.

25. A computer-readable storage medium having a computer program stored therein, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 22.

26. A computer program product comprising a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 22.

27. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 22.

Images