Methods, devices, and systems for delivering QoS flow information

Abstract

This disclosure describes a method, system, and device for delivering Quality of Service (QoS) flow information. The method includes a first network node sending a first message to a second network node via a communication interface, the first message including a list of parameters corresponding to a data burst including at least one set of protocol data units (PDUs), and the first network node receiving a second message from the second network node via a communication interface, the second message responding to the first message.

Description

Technical Field

[0001] Technical Field The present disclosure generally relates to wireless communication. In particular, the present disclosure relates to methods, devices, and systems for delivering Quality of Service (QoS) flow information.

Background Art

[0002] Background Wireless communication technologies are leading the world towards a more connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). New generation networks are expected to provide high-speed, low-latency, and ultra-high reliability communication capabilities to meet the requirements from various industries and users.

[0003] Some devices and applications, including augmented reality (XR), virtual reality (VR), mixed reality (MR), and video streaming, require high data rates and low latency. Efficient and robust congestion control and mitigation mechanisms are crucial to supporting these applications. Identification and recognition of dropped data packets can be utilized by the receiving entity so that it can recognize as soon as possible that these data packets have been dropped. In some applications, distributing Quality of Service (QoS) flow information is used to support XR services. Because these types of services require high data rates and low latency, QoS flow information is used to optimize gNB radio resource scheduling, for example, by improving scheduling efficiency. Improved scheduling can guarantee data rates and latency. There are many challenges / problems associated with notifying QoS flow information between wireless communication nodes and / or between wireless communication nodes and wireless communication devices. These challenges / problems may include, and can result from, high latency, increased signaling overhead, and / or long downtime.

[0004] This disclosure describes various embodiments for delivering Quality of Service (QoS) flow information in order to address at least one of the challenges / problems described above. The various embodiments in this disclosure can achieve low latency, low overhead, and short interruption times, and thus improve the efficiency and / or performance of wireless communications. [Overview of the project] [Means for solving the problem]

[0005] overview This specification relates to methods, systems, and devices for wireless communications, more specifically, for delivering quality of service (QoS) flow information. Various embodiments of this disclosure can improve the resource utilization efficiency of wireless communications, boost latency performance, and / or save energy consumption of user equipment.

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: a first network node transmitting a first message to a second network node via a communication interface, the first message including a list of parameters corresponding to a data burst including at least one set of protocol data units (PDUs); and the first network node receiving a second message from the second network node via a communication interface, the second message responding to the first message.

[0007] In another embodiment, the Disclosure describes a method for wireless communication. The method includes: a second network node receiving a first message from a first network node via a communication interface, the first message including a list of parameters corresponding to a data burst including at least one set of PDUs; and the second network node sending a second message to the first network node via a communication interface, the second message responding to the first message.

[0008] In some other embodiments, the device for wireless communication may include a memory for storing instructions and a processing circuit communicating with the memory. When the processing circuit executes an instruction, the processing circuit is configured to perform the method described above.

[0009] In some other embodiments, the device for wireless communication may include a memory for storing instructions and a processing circuit communicating with the memory. When the processing circuit executes an instruction, the processing circuit is configured to perform the method described above.

[0010] In some other embodiments, the computer-readable medium includes instructions that cause the computer to perform the above method when executed by the computer. The computer-readable medium may include non-temporary computer-readable medium.

[0011] The above and other aspects and embodiments thereof are described in more detail in the drawings, the text of the specification and the claims. [Brief explanation of the drawing]

[0012] [Figure 1A] Figure 1A shows a schematic diagram of wireless communication.

[0013] [Figure 1B] Figure 1B shows a schematic diagram of a base station.

[0014] [Figure 1C] Figure 1C shows another schematic diagram of the base station.

[0015] [Figure 1D] Figure 1D shows a schematic diagram of the application data unit structure.

[0016] [Figure 2] Figure 2 shows an example of a network node.

[0017] [Figure 3] Figure 3 shows an example of user equipment.

[0018] [Figure 4A] Figure 4A shows a flowchart of the method for wireless communication.

[0019] [Figure 4B] Figure 4B shows a flowchart of another method for wireless communication.

[0020] [Figure 5] Figure 5 shows a flowchart of an exemplary embodiment for wireless communication.

[0021] [Figure 6] Figure 6 shows a flowchart of another exemplary embodiment for wireless communication.

[0022] [Figure 7] Figure 7 shows a flowchart of another exemplary embodiment for wireless communication.

[0023] [Figure 8] Figure 8 shows a flowchart of another exemplary embodiment for wireless communication.

[0024] [Figure 9] Figure 9 shows a flowchart of another exemplary embodiment for wireless communication.

[0025] [Figure 10] Figure 10 shows a flowchart of another exemplary embodiment for wireless communication.

Embodiments of the Invention

[0026] Detailed Description The present disclosure will be described in detail below with reference to the accompanying drawings which form a part of the present disclosure and illustrate specific examples of embodiments. However, it should be noted that the present disclosure may be embodied in various different forms, and thus the subject matter included or claimed is not intended to be limited to any of the embodiments described below.

[0027] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in several embodiments” used herein do not necessarily refer to the same embodiment, and the expressions “in another embodiment” or “in other embodiments” used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include typical embodiments or combinations of embodiments, in whole or in part.

[0028] In general, terms can be understood at least partially from their use in context. For example, terms such as “and,” “or,” and “and / or,” when used herein, may have a variety of meanings that may at least partially depend on the context in which such terms are used. Typically, when “or” is used to relate a list such as A, B, or C, it is intended to mean A, B, and C, used here in an inclusive sense, as well as A, B, or C, used here in an exclusive sense. Furthermore, the terms “one or more” or “at least one” as used herein may be used at least partially, depending on the context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” and “the” can also be understood, at least partially, depending on the context, to convey either a singular or plural usage. Furthermore, the terms “based on” or “determined by” may be understood not necessarily to convey an exclusive set of factors, but rather, depending at least partially on the context, may allow for the presence of additional factors that are not necessarily explicitly stated.

[0029] This disclosure describes various embodiments for delivering Quality of Service (QoS) flow information.

[0030] Wireless communication technology is driving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including, but not limited to, base stations). Next-generation networks are expected to provide high-speed, low-latency, and ultra-high-reliability communication capabilities, meeting the requirements of various industries and users.

[0031] Some devices and applications, including augmented reality (XR), virtual reality (VR), mixed reality (MR), and video streaming, require high data rates and low latency. Efficient and robust congestion control and mitigation mechanisms are crucial to supporting these applications. Identification and recognition of dropped data packets can be utilized by the receiving entity so that it can recognize as soon as possible that these data packets have been dropped. In some applications, distributing Quality of Service (QoS) flow information is used to support XR services. Because these types of services require high data rates and low latency, QoS flow information is used to optimize gNB radio resource scheduling, for example, by improving scheduling efficiency. Improved scheduling can guarantee data rates and latency. There are many challenges / problems associated with notifying flow information between wireless communication nodes and / or between wireless communication nodes and wireless communication devices. These challenges / problems may include, and can result from, high latency, increased signaling overhead, and / or long downtime.

[0032] In various embodiments, the method may include distributing QoS flow information via various interfaces, such as the NG interface, F1 interface, E1 interface, and / or Xn interface. The QoS flow information may include uplink (UL) and downlink (DL) traffic periodicity, UL and DL traffic jitter information (e.g., jitter range), burst arrival time, and protocol data unit (PDU) set QoS parameters. In some embodiments, the PDU set QoS parameters may include the PDU set error rate, PDU set delay budget, and PDU set integrated processing indication. The QoS flow information is used to optimize gNB radio resource scheduling and achieve high efficiency in wireless communication. It can also be used for mapping QoS flow to DRB.

[0033] Figure 1A shows an exemplary cellular wireless communication network 100 (also called a wireless communication system) including a core network 110, a radio access network (RAN) 120, and one or more user equipment (UEs) 130.

[0034] RAN120 further includes a plurality of base stations 122 and 124. The base stations 122 and one or more user equipment (UEs) 130 communicate with each other via an over-the-air (OTA) radio communication resource 140. The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, 5G, or 6G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as a 2G base station, a 3G node B, an LTE eNB, or a 5G new radio (NR) gNB. The UEs 130 may be implemented as mobile communication devices or fixed communication devices for accessing the wireless communication network 100. One or more UEs 130 may include, but are not limited to, mobile phones, Internet of Things (IoT) devices, machine-type communication (MTC) devices, laptop computers, tablets, personal digital assistants, wearable devices, distributed remote sensor devices, roadside assistance equipment, and desktop computers. Instead of the context of a cellular wireless network, RAN 120 and the principles described below may be implemented as other types of wireless access networks, such as Wi-Fi, Bluetooth®, ZigBee®, and WiMAX networks.

[0035] In the exemplary wireless communication system 100 shown in Figure 1A, one or more UEs 130 can connect to a base station 122 via an OTA interface 140 and establish a communication session with the base station 122. The communication session between the UEs 130 and the base station 122 can utilize downlink (DL) and / or uplink (UL) transmission resources. DL transmission resources carry data from the base station 122 to the UEs 130, and UL transmission resources carry data from the UEs 130 to the base station 122. Under certain circumstances, for example, when base station 122 is unavailable or when the UEs 130 move into the coverage of base station 124, one or more UEs 130 can connect to base station 122 and establish a communication session with the base station 122.

[0036] Referring to Figure 1B, the base station (e.g., gNB) 122 may have a control distribution isolation structure which may include a control unit (CU) 160 and one or more distributed units (DU) 171 and / or 172. The 5GC can communicate with the gNB via the NG interface between them. The gNB and another gNB can communicate via the Xn-C interface. The gNB-CU can communicate with one or more gNB-DU via the F1 interface.

[0037] In some embodiments, in a CU / DU partitioned architecture, the gNB may consist of a gNB central unit (gNB-CU) and one or more gNB distributed units (gNB-DU). The gNB-CU and gNB-DU are connected via an F1 interface. The gNB-CU is defined as a logical node that hosts the gNB's RRC, SDAP, and PDCP protocols, or the en-gNB's RRC and PDCP protocols that control the operation of one or more gNB-DUs. The gNB-DU is defined as a logical node that hosts the gNB or en-gNB's RLC, MAC, and PHY layers, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. One cell is supported by only one gNB-DU.

[0038] In some embodiments, the gNB-CU is defined as a logical node that hosts the RRC, SDAP, and PDCP protocols of the gNB, or the RRC and PDCP protocols of the en-gNB that control the operation of one or more gNB-DUs. The gNB-DU is defined as a logical node that hosts the RLC, MAC, and PHY layers of the gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. A single cell may be supported by only one gNB-DU.

[0039] Figure 1C shows another schematic diagram of a base station (e.g., gNB) 150. The gNB may have a control distribution isolation structure which may include a control unit (CU) 160 and one or more distributed units (DUs) (e.g., 171 and / or 172). The CU may include a control plan (gNB-CU-CP) 161 and one or more user plans (gNB-CU-UP) 162. The gNB-CU-CP 161 may also be called a CU-CP or CP, and the gNB-CU-UP 162 may also be called a CU-UP or UP. The CU-CP 161 can communicate with one or more CU-UPs 162 via an E1 interface between them. The CU-CP 161 can communicate with one or more DUs via an F1-C interface, and each of the one or more CU-UPs 162 can communicate with one or more DUs via an F1-U interface.

[0040] In some embodiments, the gNB can be composed of a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU through an F1-C interface. The gNB-CU-UP is connected to the gNB-DU through an F1-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through an E1 interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP.

[0041] In some embodiments, for resilience, a gNB-DU and / or gNB-CU-UP may be connected to multiple gNB-CU-CPs by the appropriate embodiment. In some embodiments, one gNB-DU may be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. In some embodiments, one gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP.

[0042] In some embodiments, connectivity between gNB-CU-UP and gNB-DU is established by gNB-CU-CP using bearer context management functionality.

[0043] In some embodiments, the gNB-CU-CP selects the appropriate (one or more) gNB-CU-UP for the service requested by the UE. In some embodiments, multiple CU-UPs may belong to the same security domain.

[0044] In some embodiments, data transfer between gNB-CU-UP during a handover within gNB-CU-CP can be supported by Xn-U.

[0045] In various embodiments of this disclosure, a set of protocol data units (PDUs) may be a set comprising one or more PDUs that carry a payload of a single unit of information generated at the application level (e.g., a frame or a video slice). A data burst may comprise one or more sets of PDUs generated and transmitted by an application over a short period of time. The period may be the duration between the start of two data bursts. The burst arrival time may be the most recent possible time for the first packet of the data burst to arrive at either the entry interface of the RAN (downlink flow direction) or the exit interface of the UE (uplink flow direction).

[0046] In various embodiments / models of this disclosure, an XR service may include a video stream represented by a plurality of application data units, each application data unit consisting of a plurality of application frames (e.g., I-frames, P-frames, B-frames). Referring to Figure 1D, one application frame may include at least one IP packet, which may be represented in a set of PDUs in a QoS flow (e.g., a “media unit” or “slice”, a sequence of packets containing all the information necessary to reconstruct a video frame, corresponding to video / audio frames / tiles, haptic application information, e.g., a GTP-U, NG user plane interface (NG-U), Xn user plane (Xn-U) interface, or user data from the Non-Access Layer (NAS). For example, one of the application frames (I1) may contain n PDUs (i.e., I 11 , I 12 , I 13 ,...I 1n It may also include a first set of PDUs (PDU set 1) containing ), where n is a positive integer. For another example, another application frame (B2) may contain m PDUs (i.e., B 11 B 12 B 13 ,...B 1m It may also include a second PDU set (PDU set 2) containing ), where m is a positive integer.

[0047] In some embodiments, an I-frame is a keyframe that stores / transmits all the data necessary to display that frame. Typically, I-frames are inserted in compressed video mixed with P-frames and B-frames. The more I-frames included, the better the video quality. However, I-frames contain most of the bits and therefore occupy more space on the storage medium and consume more wireless resources to deliver them over the Uu interface. A P-frame is a delta frame, which contains only data that has changed from the preceding I-frame (such as changes in color or content). For this reason, a P-frame relies on the preceding I-frame to fill most of its data. A B-frame is also a delta frame, which contains only data that has changed from the previous frame and is different from the data in the very next frame. For this reason, a B-frame relies on the preceding and following frames to fill most of its data.

[0048] Figure 2 shows an example of an electronic device 200 implementing a network base station. The exemplary electronic device 200 may include a radio transmission / reception (Tx / Rx) circuit 208 for transmitting / receiving communications with UEs and / or other base stations. The electronic device 200 may also include a network interface circuit 209 for the base station to communicate with other base stations and / or core networks, such as optical or wired interconnects, Ethernet®, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with operators, etc.

[0049] The electronic device 200 may also include a system circuit 204. The system circuit 204 may include (one or more) processors 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured so that one or more of the processors 124 perform the functions of a network node. Parameters 228 may include parameters to support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0050] Figure 3 shows an example of an electronic device for implementing a terminal device 300 (e.g., a user device (UE)). The UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. The UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and storage 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuits. The system circuit 304 may be implemented using, for example, one or more system-on-a-chip (SoCs), application-specific integrated circuits (ASICs), separate analog and digital circuits, and other circuits. The system circuit 304 may be part of the implementation of any desired function in the UE 300. In this regard, the system circuit 304 may include logic to facilitate, for example, decoding and playback of music and video, e.g., decoding and playback of MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; execution of applications; acceptance of user input; storage and retrieval of application data; establishment, maintenance, and termination of data connections for cellular phone calls or, for example, internet connections; establishment, maintenance, and termination of wireless network connections, Bluetooth® connections, or other connections; and display of relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch sensor display, haptic feedback or other haptic output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Further examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0051] Referring to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) circuit 316 that handles the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include a modulation / demodulation circuit, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The signals transmitted and received may conform to one of a variety of arrays of format, protocol, modulation (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channel, bit rate, and encoding. As a specific example, the communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / Long-Term Evolution (LTE), 5G standards, and / or 6G standards. However, the technologies described below are applicable to other wireless communication technologies, whether or not they originate from the Third Generation Partnership Project (3GPP®), the GSM® Association, 3GPP2, IEEE, or other partnerships or standardization bodies.

[0052] Referring to Figure 3, the system circuit 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute instructions 326 to perform desired functions for the UE300. The parameters 328 may provide and specify setting and operation options for instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data transmitted or received by the UE300 via the communication interface 302. In various embodiments, the system power of the UE300 may be supplied by an energy storage device such as a battery or transformer.

[0053] This disclosure describes various embodiments for distributing Quality of Service (QoS) flow information that can be partially or fully implemented on the network base stations and / or user equipment described above, as shown in Figures 2 and 3.

[0054] Referring to Figure 4A, the present disclosure describes various embodiments of Method 400 for wireless communication. Method 400 may include, in whole or in part, the following steps: Step 410, by a first network node, sending a first message to a second network node via a communication interface, wherein the first message includes a list of parameters corresponding to a data burst including at least one set of protocol data units (PDUs); and / or Step 420, by the first network node, receiving a second message from the second network node via a communication interface, wherein the second message is a response to the first message.

[0055] Referring to Figure 4B, the present disclosure describes various embodiments of Method 450 for wireless communication. Method 450 may include, in whole or in part, the following steps: Step 460, by a second network node, receiving a first message from a first network node via a communication interface, wherein the first message includes a list of parameters corresponding to a data burst including at least one set of PDUs; and / or Step 470, by the second network node, sending a second message to the first network node via a communication interface, wherein the second message is a response to the first message.

[0056] In some embodiments, the list of parameters includes at least one of the following: uplink (UL) traffic periodicity, downlink (DL) traffic periodicity, UL traffic jitter information, DL traffic jitter information (e.g., jitter range), burst arrival time, or a list of PDU set quality of service (QoS) parameters, and / or the list of PDU set QoS parameters includes at least one of the following: PDU set error rate, PDU set delay budget, or PDU set integrated processing indication.

[0057] In some embodiments, the first network node includes an Access and Mobility Management Function (AMF) node, the second network node includes a Radio Access Network (RAN) node, and / or the communication interface includes an NG interface.

[0058] In some embodiments, the first message and the second message belong to the NG interface messages.

[0059] In some embodiments, the first and second messages include one of the following: a PDU session resource setup request message and a PDU session resource setup response message, a PDU session resource modification request message and a PDU session resource modification response message, or a handover request message and a handover request acknowledgment response message, and / or, the first message includes at least one of the following information elements (IEs) including a list of parameters: a time-sensitive communication (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a QoS flow setup request list IE, or a QoS flow addition or modification request list IE.

[0060] In some embodiments, the first network node includes a central unit (CU) of the RAN node, the second network node includes a distributed unit (DU) of the RAN node, and / or the communication interface includes an F1 interface.

[0061] In some embodiments, the first message and the second message belong to the F1 interface messages.

[0062] In some embodiments, the first message and the second message each include one of the following: a user equipment (UE) context setup request message and a UE context setup request response message, or a UE context modification request message and a UE context modification request response message, and / or the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameters IE, a list of data radio bearers (DRBs) to be set up IE, or a list of DRBs to be modified IE.

[0063] In some embodiments, the first network node includes the control plane (CP) of the central unit (CU) of the RAN node, the second network node includes the user plane (UP) of the CU of the RAN node, and / or the communication interface includes the E1 interface.

[0064] In some embodiments, the first message and the second message belong to the E1 interface message.

[0065] In some embodiments, the first message and the second message each include one of the following: a bearer context setup request message and a bearer context setup request response message, or a bearer context modification request message and a bearer context modification request response message, and / or the first message includes at least one of the following IEs including a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameters IE, setup scheduled DRB list IE, or modification scheduled DRB list IE.

[0066] In some embodiments, the first network node includes a source RAN node, the second network node includes a target RAN node, and / or the communication interface includes an Xn interface.

[0067] In some embodiments, the first message and the second message each include a handover request message and a handover request acknowledgment message, and / or the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to a DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

[0068] In some embodiments, the first network node includes a new RAN node, the second network node includes an old RAN node, and / or the communication interface includes an Xn interface.

[0069] In some embodiments, the first message and the second message each include a UE context retrieval request message and a UE context retrieval response message, and / or the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to a DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

[0070] In some embodiments, the first network node includes a master node (MN), the second network node includes a secondary node (SN), and / or the communication interface includes an Xn interface.

[0071] In some embodiments, the first message and the second message each include one of the following: an S-node addition request message and an S-node addition request acknowledgment message, or an S-node modification request message and an S-node modification request acknowledgment message, and / or the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to a DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

[0072] This disclosure describes various embodiments having exemplary examples for delivering Quality of Service (QoS) flow information. The exemplary embodiments provide examples for this disclosure and do not impose any limitations on this disclosure. In the embodiments and representations of this disclosure, any step and / or operation may be combined or arranged in any quantity or order as desired. Two or more steps and / or operations may be performed in parallel. The embodiments and representations of this disclosure may be used separately or combined in any order. Furthermore, any one of the method (or embodiment), wireless communication node, and wireless communication device may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits).

[0073] Embodiment Set I: QoS flow information delivered via NG interface Various embodiments of this disclosure describe the distribution of QoS flow information via an NG interface. Figure 5 shows a non-limiting example between an NG-RAN node 591 and an AMF 592.

[0074] In step 501, the AMF sends QoS flow information to the NG-RAN node via NG interface messages (for example, PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE MODIFY REQUEST, or HANDOVER REQUEST messages).

[0075] QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. In some embodiments, the PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0076] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0077] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0078] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0079] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0080] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0081] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by the transmission device (e.g., the RAN) but have not been delivered by the receiving device (e.g., the UE).

[0082] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0083] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communication (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a QoS flow setup request list IE, or a QoS flow add or modify request list IE.

[0084] In step 502, the NG-RAN node responds with an NG interface message (for example, a PDU SESSION RESOURCE SETUP RESPONSE message, a PDU SESSION RESOURCE MODIFY RESPONSE message, or a HANDOVER REQUEST ACKNOWLEDGE message).

[0085] Embodiment Set II: QoS flow information delivered via the F1 interface Various embodiments of this disclosure illustrate the distribution of QoS flow information via the F1 interface. Figure 6 shows a non-limiting example between gNB-CU 691 and gNB-DU 692.

[0086] In step 601, the gNB-CU sends QoS flow information to the gNB-DU via an F1 interface message (for example, a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message).

[0087] In some embodiments, the QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. The PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. In some embodiments, the QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0088] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0089] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0090] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0091] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0092] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0093] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by a transmission device (e.g., RAN) but have not been delivered to its upper layer by a receiving device (e.g., UE).

[0094] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0095] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communications (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a DRB list to be set up IE, or a DRB list to be modified IE.

[0096] In step 602, the gNB-DU responds using an F1 interface message (for example, a UE CONTEXT MODIFICATION REQUEST RESPONSE message).

[0097] Embodiment Set III: QoS flow information delivered via the E1 interface Various embodiments of this disclosure describe the distribution of QoS flow information via the E1 interface. Figure 7 shows a non-limiting example between gNB-CU-CP 791 and gNB-DU-UP 792.

[0098] In step 701, the gNB-CU-CP sends QoS flow information to the gNB-CU-UP via an E1 interface message (for example, a BEARER CONTEXT SETUP REQUEST message or a BEARER CONTEXT MODIFICATION REQUEST message).

[0099] In some embodiments, the QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. The PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. In some embodiments, the QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0100] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0101] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0102] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0103] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0104] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0105] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by a transmission device (e.g., RAN) but have not been delivered to its upper layer by a receiving device (e.g., UE).

[0106] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0107] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communications (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a setup-planned DRB list IE, or a modification-planned DRB list IE.

[0108] In step 702, the gNB-CU-UP responds with an E1 interface message (for example, a BEARER CONTEXT SETUP RESPONSE message or a BEARER CONTEXT MODIFICATION RESPONSE message).

[0109] Embodiment Set IV: QoS flow information delivered via the Xn interface for handover Various embodiments of this disclosure describe situations in which QoS flow information is delivered via an Xn interface for handover. Figure 8 shows a non-limiting example between a gNB-CU-CP 891 and a gNB-DU-UP 892.

[0110] In step 801, the source NG-RAN node sends QoS flow information to the target NG-RAN node via an Xn interface message (e.g., a HANDOVER REQUEST message).

[0111] In some embodiments, the QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. The PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. In some embodiments, the QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0112] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0113] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0114] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0115] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0116] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0117] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by a transmission device (e.g., RAN) but have not been delivered to its upper layer by a receiving device (e.g., UE).

[0118] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0119] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communications (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a PDU session resource list to be set up IE, a QoS flow list to be set up IE, a DRB list to be set up IE, a QoS flow list mapped to a DRB IE, a QoS flow list to be modified IE, or a DRB list to be modified IE.

[0120] In step 802, the target NG-RAN node responds with an Xn interface message (for example, a HANDOVER REQUEST ACKNOWLEDGE message).

[0121] Embodiment Set V: QoS flow information delivered via the Xn interface to retrieve the UE context Various embodiments of this disclosure describe how QoS flow information is delivered via the Xn interface to retrieve the UE context. Figure 9 shows a non-limiting example between an old NG-RAN node 991 and a new NG-RAN node 992.

[0122] In step 901, the new NG-RAN node sends an Xn interface message (for example, RETRIEVE UE CONTEXT REQUEST) to retrieve the UE context.

[0123] In step 902, the old NG-RAN node responds to the new NG-RAN node via an Xn interface message (for example, a RETRIEVE UE CONTEXT RESPONSE message) using QoS flow information.

[0124] In some embodiments, the QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. The PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. In some embodiments, the QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0125] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0126] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0127] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0128] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0129] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0130] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by a transmission device (e.g., RAN) but have not been delivered to its upper layer by a receiving device (e.g., UE).

[0131] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0132] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communications (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a PDU session resource list to be set up IE, a QoS flow list to be set up IE, a DRB list to be set up IE, a QoS flow list mapped to a DRB IE, a QoS flow list to be modified IE, or a DRB list to be modified IE.

[0133] Embodiment Set VI: QoS Flow Information Delivered via Xn Interface for MR-DC Various embodiments of this disclosure describe the distribution of QoS flow information via an Xn interface for multi-radio dual connectivity (MR-DC). Figure 10 shows a non-limiting example between a master node (MN) 1091 and a secondary node (SN) 1092.

[0134] In step 1001, the MN sends QoS flow information to the SN via Xn interface messages (e.g., S-NODE ADDITION REQUEST messages, S-NODE MODIFICATION REQUEST messages).

[0135] In some embodiments, the QoS flow information may include UL traffic periodicity, DL traffic periodicity, UL traffic jitter information (e.g., jitter range), DL traffic jitter information (e.g., jitter range), burst arrival time, and some or all of the PDU set QoS parameters of the QoS flow. The PDU set QoS parameters of the QoS flow may be applicable to all PDU sets in the QoS flow and may include some or all of the PDU set error rate, PDU set delay budget, and PDU set integrated processing indications. In some embodiments, the QoS flow information is used to optimize gNB radio resource scheduling, for example, to improve scheduling efficiency. It can also be used for mapping from QoS flows to DRBs.

[0136] In some embodiments, the PDU set integration processing indication is used, for example, to indicate whether all PDUs in a PDU set are required for use by the application layer under specific conditions where one or more PDUs have transmission errors.

[0137] In some embodiments, UL traffic periodicity indicates the periodicity of UL traffic in a QoS flow, indicating whether UL traffic is periodic and / or what the periodicity of UL traffic may be.

[0138] In some embodiments, DL traffic periodicity indicates the periodicity of DL traffic in a QoS flow, indicating whether DL traffic is periodic and / or what the periodicity of DL traffic may be.

[0139] In some embodiments, DL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0140] In some embodiments, UL traffic jitter information may indicate a jitter range that can be associated with each periodicity of the QoS flow, and may indicate the duration of the jitter range.

[0141] In some embodiments, the PDU set error rate (PSER) may define an upper limit on the non-congestion-related PDU set loss rate between the RAN and the UE. In some embodiments, the PSER may correspond to PDU sets that have been processed by a transmission device (e.g., RAN) but have not been delivered to its upper layer by a receiving device (e.g., UE).

[0142] In some embodiments, in DL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UPF and the successful delivery of the last PDU arriving in the PDU set in UE. In some embodiments, in UL, the PDU set delay budget may represent the time and / or duration between the reception of the first PDU in UE and the successful delivery of the last PDU arriving in the PDU set in UPF.

[0143] In some embodiments, QoS flow information may be defined as a new information element (IE), or it may be included in an existing IE such as a time-sensitive communications (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a PDU session resource list to be set up IE, a QoS flow list to be set up IE, a DRB list to be set up IE, a QoS flow list mapped to a DRB IE, a QoS flow list to be modified IE, or a DRB list to be modified IE.

[0144] In step 1002, SN responds using an Xn interface message (for example, an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message).

[0145] This disclosure describes methods, apparatus, and computer-readable media for wireless communications. This disclosure addresses the challenges related to delivering Quality of Service (QoS) flow information. The methods, devices, and computer-readable media described in this disclosure can facilitate the performance of wireless communications by delivering QoS flow information, and thus improve efficiency and overall performance. The methods, devices, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0146] In some other embodiments, the computer-readable medium includes instructions that cause the computer to perform the above-described method when executed by the computer. The computer-readable medium may be called non-temporary computer-readable medium (CRM) that stores data for a long period of time, such as a flash drive or compact disc (CD), or that stores data for a short period of time in the presence of power, such as a memory device or random access memory (RAM). In some embodiments, the computer-readable instructions may be contained in software embodied in one or more tangible non-temporary computer-readable mediums. Such non-temporary computer-readable mediums may be user-accessible mass storage, as well as mediums associated with certain short-term storage of a non-temporary nature, such as internal mass storage or ROM. Software implementing various embodiments of this disclosure may be stored in such devices and executed by a processor (or processing circuit). The computer-readable medium may include one or more memory devices or chips, depending on the specific needs. The software may cause a processor (including a CPU, GPU, FPGA, etc.) to perform certain processes or specific parts of certain processes described herein, including defining data structures stored in RAM and modifying such data structures according to processes defined by the software.

[0147] Throughout this specification, references to features, benefits, or similar terms do not imply that all features and benefits that may be realized by the Solution should or will be included in any single embodiment thereof. Rather, any terms referring to features and benefits should be understood to mean that certain features, benefits, or characteristics described in relation to an embodiment are included in at least one embodiment of the Solution. Accordingly, descriptions of features and benefits, as well as similar terms, throughout this specification may, but not necessarily, refer to the same embodiment.

[0148] Furthermore, the described features, advantages, and characteristics of this solution may be combined in any suitable manner in one or more embodiments. As those skilled in the art will see, in light of the description herein, this solution may be practiced without any particular features or advantages of a particular embodiment. In other examples, additional features and advantages may be recognized in certain embodiments where they may not be present in all embodiments of this solution.

Claims

1. A method for wireless communication, The first network node transmits a first message to a second network node via a communication interface, wherein the first message includes a list of parameters corresponding to a data burst comprising at least one set of protocol data units (PDUs). The first network node receives a second message from the second network node via the communication interface, and the second message is a response to the first message. Methods that include...

2. A method for wireless communication, The second network node receives a first message from the first network node via a communication interface, wherein the first message includes a list of parameters corresponding to a data burst containing at least one PDU set. The second network node transmits a second message to the first network node via the communication interface, the second message being a response to the first message. Methods that include...

3. The list of parameters includes at least one of the following: uplink (UL) traffic periodicity, downlink (DL) traffic periodicity, UL traffic jitter information, DL traffic jitter information, burst arrival time, or a list of PDU set quality of service (QoS) parameters. The method according to any one of claims 1 to 2, wherein the list of PDU set QoS parameters includes at least one of the following: PDU set error rate, PDU set delay budget, or PDU set integration processing indicator.

4. The first network node includes an Access and Mobility Management Function (AMF) node, The second network node includes a wireless access network (RAN) node, The method according to any one of claims 1 to 3, wherein the communication interface includes an NG interface.

5. The method according to claim 4, wherein the first message and the second message belong to the NG interface messages.

6. The first message and the second message include one of the following: a PDU session resource setup request message and a PDU session resource setup response message, a PDU session resource modification request message and a PDU session resource modification response message, or a handover request message and a handover request acknowledgment response message. The method according to claim 4, wherein the first message includes at least one of the following information elements (IEs) including a list of parameters: namely, a time-sensitive communication (TSC) traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a QoS flow setup request list IE, or a QoS flow addition or modification request list IE.

7. The first network node includes a central unit (CU) of the RAN node, The second network node includes a distributed unit (DU) of the RAN node, The method according to any one of claims 1 to 3, wherein the communication interface includes an F1 interface.

8. The method according to claim 7, wherein the first message and the second message belong to the F1 interface messages.

9. Each of the first message and the second message includes one of the following: a user equipment (UE) context setup request message and a UE context setup request response message, or a UE context modification request message and a UE context modification request response message. The method according to claim 7, wherein the first message includes at least one of the following IEs, which include a list of parameters: a TSC traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a list of data radio bearers (DRBs) to be set up IE, or a list of DRBs to be modified IE.

10. The first network node includes the control plane (CP) of the central unit (CU) of the RAN node, The second network node includes the user plane (UP) of the CU of the RAN node, The method according to any one of claims 1 to 3, wherein the communication interface includes an E1 interface.

11. The method according to claim 10, wherein the first message and the second message belong to the E1 interface message.

12. The first message and the second message each include one of the following: a bearer context setup request message and a bearer context setup request response message, or a bearer context modification request message and a bearer context modification request response message. The method according to claim 10, wherein the first message includes at least one of the following IEs, which include a list of parameters: a TSC traffic characteristics IE, a TSC support information IE, a QoS flow level QoS parameter IE, a setup schedule DRB list IE, or a modification schedule DRB list IE.

13. The first network node includes a source RAN node, The second network node includes a target RAN node, The method according to any one of claims 1 to 3, wherein the communication interface includes an Xn interface.

14. The first message and the second message each include a handover request message and a handover request acknowledgment message, The method according to claim 13, wherein the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

15. The first network node includes a new RAN node, The second network node includes the old RAN node, The method according to any one of claims 1 to 3, wherein the communication interface includes an Xn interface.

16. The first message and the second message each include a UE context retrieval request message and a UE context retrieval response message, The method according to claim 15, wherein the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

17. The first network node includes a master node (MN), The second network node includes a secondary node (SN), The method according to any one of claims 1 to 3, wherein the communication interface includes an Xn interface.

18. Each of the first message and the second message includes one of the following: an S-node addition request message and an S-node addition request acknowledgment message, or an S-node modification request message and an S-node modification request acknowledgment message. The method according to claim 17, wherein the first message includes at least one of the following IEs, which include a list of parameters: TSC traffic characteristics IE, TSC support information IE, QoS flow level QoS parameter IE, PDU session resource list to be set up IE, QoS flow list to be set up IE, DRB list to be set up IE, QoS flow list mapped to DRB IE, QoS flow list to be modified IE, or DRB list to be modified IE.

19. The method according to any one of claims 13 to 18, wherein the first message and the second message belong to the Xn interface messages.

20. A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory and implement the method according to any one of claims 1 to 19.

21. A computer program product having a computer-readable program medium code stored therein, wherein the computer-readable program medium code, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 19.

Images