Method, apparatus and computer program product for wireless communication

By identifying and managing PDU collections and their timing in 5G wireless communications, and updating QoS parameters based on network capabilities, the problem of low PDU transmission efficiency is solved, efficient video stream decoding and display is realized, and wireless communication performance is improved.

CN119054412APending Publication Date: 2024-11-29ZTE CORP
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202280093532.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-05-17
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In 5G wireless communication, the prior art is difficult to effectively identify and manage PDU sets and their timing, resulting in low quality of service (QoS) parameter update and data transmission efficiency, which cannot meet the needs of XR services for efficient video stream decoding and display.

Method used

By transmitting a protocol data unit (PDU) between a wireless communication node and a terminal, identifying the PDU set and PDU set timing, and sending reflective quality of service (QoS) indication or active QoS update request based on network capabilities and preferences, scheduling PDU transmission, realizing Effective management and transmission of PDU collections.

Benefits of technology

It improves the transmission efficiency and service quality of PDU collections, meets the demands of XR services for efficient video stream decoding and display, and improves the overall performance of wireless communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054412A_ABST
    Figure CN119054412A_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, an apparatus, and a computer program product for wireless communication. The method comprises: a wireless communication node receiving a protocol data unit (PDU) from a high layer, the PDU comprising identification information; and the wireless communication node identifying a PDU set of the PDUs and a PDU set timing of the PDU set; wherein the PDU is scheduled to be transmitted through a Uu interface according to at least one of the PDU set or the PDU set timing; wherein the upper layer comprises at least one of a generic packet radio traffic tunneling protocol user plane (GTP-U), a next generation user plane interface (NG-U), an Xn user plane, an Xn-U interface, user data from a non-access stratum (NAS), or user data of a QoS flow.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This document is generally directed to wireless communications, and in particular fifth generation (5G) wireless communications. Background Art

[0002] XR (Extended Reality) services are usually video streams represented by multiple application data units. Each application data unit consists of multiple application frames, such as I frames, P frames, and B frames. These application frames can be dependent on each other and have a certain transmission, decoding, or display order. Summary of the invention

[0003] The present disclosure relates to methods, apparatus, and computer program products for identifying PDU sets and PDU set timing in wireless communications.

[0004] One aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receives a protocol data unit (PDU) from a higher layer, the PDU includes identification information; and the wireless communication node identifies a PDU set of the PDU and / or a PDU set timing of the PDU set; wherein the PDU is scheduled to be transmitted through a Uu interface according to at least one of the PDU set or the PDU set timing; wherein the higher layer includes at least one of the following: a general packet radio service tunneling protocol user plane (GTP-U), a next generation user plane interface (NG-U), an Xn user plane, an Xn-U interface, user data from a non-access layer (NAS), or user data of a QoS flow.

[0005] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node sends a reflective quality of service (QoS) indication or an active QoS update request to a core network (CN) or a wireless communication terminal according to at least one of network capabilities or network preferences to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network or the wireless communication terminal to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0006] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receiving a buffer size indication from a wireless communication terminal.

[0007] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node sends a discontinuous reception (C-DRX) configuration in an RRC connected state to a wireless communication terminal; and according to the C-DRX configuration, the wireless communication node communicates with the wireless communication terminal in multiple C-DRX modes for each cell group, each data radio bearer (DRB) or each logical channel.

[0008] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receives a buffer status report (BSR) of an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU from a wireless communication terminal.

[0009] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication node receives a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal from a first wireless communication terminal.

[0010] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a node in a core network (CN) receives a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0011] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal receives a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0012] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal sending a buffer size indication to a wireless communication node.

[0013] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal receives a discontinuous reception (C-DRX) configuration in an RRC connected state from a wireless communication node; and according to the C-DRX configuration, the wireless communication node communicates with the wireless communication terminal in multiple C-DRX modes for each cell group, each data radio bearer (DRB) or each logical channel.

[0014] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal sends a buffer status report (BSP) of an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU to a wireless communication node.

[0015] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a first wireless communication terminal sends a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal to a wireless communication node.

[0016] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: receive a protocol data unit (PDU) from a high layer, the PDU including PDU set information; identify a PDU set of the PDU and / or a PDU set timing of the PDU set; wherein the PDU is scheduled for transmission over a Uu interface according to at least one of the PDU set or the PDU set timing; wherein the high layer includes at least one of the following: a general packet radio service tunneling protocol user plane (GTP-U), a next generation user plane interface (NG-U), an Xn user plane, an Xn-U interface, user data from a non-access layer (NAS), or user data of a QoS flow.

[0017] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: send a reflective quality of service (QoS) indication or an active QoS update request to a core network (CN) or a wireless communication terminal according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network or the wireless communication terminal to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0018] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: receive a buffer size indication from a wireless communication terminal.

[0019] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: send a discontinuous reception (C-DRX) configuration in an RRC connected state to a wireless communication terminal; and communicate with the wireless communication terminal according to the C-DRX configuration for multiple C-DRX modes for each cell group, each data radio bearer (DRB) or each logical channel.

[0020] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to receive a buffer status report (BSP) of an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU from a wireless communication terminal.

[0021] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: receive a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal from a first wireless communication terminal.

[0022] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to: receive a reflective quality of service (QoS) indication or an active QoS update request from the wireless communication node according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0023] Another aspect of the present disclosure relates to a communication node (e.g., a communication node in a core network). In one embodiment, the communication node includes a communication unit and a processor. The processor is configured to: receive a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0024] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to: receive a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node according to at least one of a network capability or a network preference to trigger a QoS parameter update; wherein the reflective QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information to allow the core network to determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS auxiliary information.

[0025] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to: send a buffer size indication to a wireless communication node.

[0026] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to: receive a discontinuous reception (C-DRX) configuration in an RRC connected state from a wireless communication node; and communicate with the wireless communication terminal according to the C-DRX configuration, with multiple C-DRX modes per cell group, per data radio bearer (DRB), or per logical channel.

[0027] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to send a buffer status report (BSP) of an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU to a wireless communication node.

[0028] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to: send a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal to a wireless communication node.

[0029] Various embodiments may preferably achieve the following features:

[0030] Preferably, the wireless communication node receives a PDU set sequence number of the PDU set, and the PDU set is determined by the PDU set sequence number.

[0031] Preferably, the PDU set timing is indicated by the PDU set sequence number.

[0032] Preferably, the PDU sets are mapped to different Quality of Service (QoS) flows, and the PDU set sequence numbers are encoded across multiple QoS flows based on decoding timing of the QoS flows.

[0033] Preferably, the wireless communication node receives at least one of a PDU set start indication or a PDU set end indication for each PDU set, and the PDU set is determined by at least one of the PDU set start indication or the PDU set end indication.

[0034] Preferably, the PDU set timing is determined by a QoS flow identifier (QFI) sequence number of the PDU in the PDU set.

[0035] Preferably, the PDU sets are mapped to different QoS flows, and the QFI sequence number is encoded across multiple QoS flows based on the PDU set timing.

[0036] Preferably, the wireless communication node includes a PDU corresponding to each PDU set in a Service Data Adaptation Protocol (SDAP) PDU.

[0037] Preferably, the PDUs corresponding to each PDU set are sequentially included in the SDAPPDU based on the PDU sequence numbers of the PDUs.

[0038] Preferably, the wireless communication node includes a PDU corresponding to each PDU set in one or more SDAP PDUs, and the one or more SDAP PDUs are included in a Packet Data Convergence Protocol (PDCP) PDU.

[0039] Preferably, the PDUs corresponding to each PDU set are sequentially included in the PDCP PDU.

[0040] Preferably, the PDCP PDU includes one or more Message Authentication Code-Integrity (MAC-I) for the one or more SDAP PDUs.

[0041] Preferably, the wireless communication node indicates information of a PDU set in at least one of an SDAP PDU, a PDCP PDU or a Radio Link Control (RLC) PDU, and the information of the PDU set is indicated by using at least one of a temporary header or a reserved bit.

[0042] Preferably, the information of the PDU set includes at least one of a PDU set sequence number or a PDU set indication.

[0043] Preferably, the information indicated by the PDU set includes at least one of the following: an indication that the corresponding PDU is in a PDU set having a single PDU, an indication that the corresponding PDU is at the starting position of the corresponding PDU set, an indication that the corresponding PDU is at the ending position of the corresponding PDU set, or an indication that the corresponding PDU is at the middle position of the corresponding PDU set.

[0044] Preferably, the wireless communication node transmits SDAP PDU, PDCP PDU or RLC PDU corresponding to the same PDU set in one transport block (TB), in one TB group or in the same time domain position.

[0045] Preferably, the wireless communication node includes a PDU set type indication or a PDU set dependency indication in at least one of an SDAP PDU, a PDCP PDU or an RLC PDU, and the information of the PDU set is indicated by using at least one of a temporary header or a reserved bit.

[0046] Preferably, the PDU set type indication indicates that the corresponding PDU set corresponds to the video compression type of the I frame, B frame or P frame, or indicates the corresponding PDU set decoding timing or PDU set decoding dependency, such as a main frame, a secondary frame, or the nth secondary frame, where n is an integer.

[0047] Preferably, the PDU set type indicates that the corresponding PDU set is independent, dependent on the immediately preceding PDU set, or dependent on the immediately preceding PDU set and the immediately following PDU set.

[0048] Preferably, the wireless communication node includes a sequence number (SN) in at least one of the PDCP PDU or the RLC PDU to indicate a PDU set dependency relationship between the PDUs.

[0049] Preferably, the SN in at least one of the PDCP PDU or the RLC PDU is encoded on a plurality of data radio bearers (DRBs).

[0050] Preferably, the wireless communication node indicates the PDU set dependency of the PDUs by including a SN of the associated PDU and an identifier (ID) of the associated DRB or the associated logical channel in at least one of the PDCP PDU or the RLC PDU.

[0051] Preferably, the wireless communication node indicates a PDU set sequence number in at least one of a PDCP PDU or an RLC PDU, and the PDU set sequence number is encoded on multiple DRBs or multiple logical channels based on the PDU set sequence number in a PDCP service data unit (SDU).

[0052] Preferably, the recommended QoS auxiliary information includes at least one of the following parameter types: recommended QoS parameter values, recommended QoS flow priorities, recommended mappings between application data and QoS flows, recommended paging strategies, user equipment (UE) mobility information, artificial intelligence-related information, machine learning-related information, network usage perception, network computing capabilities, or UE positioning-related information.

[0053] Preferably, the SN in at least one of the PDCP PDU or the RLC PDU is encoded on a plurality of data radio bearers (DRBs).

[0054] Preferably, the wireless communication node indicates the PDU set dependency of the PDUs by including a SN of the associated PDU and an identifier (ID) of the associated DRB or the associated logical channel in at least one of the PDCP PDU or the RLC PDU.

[0055] Preferably, the wireless communication node indicates a PDU set sequence number in at least one of a PDCP PDU or an RLC PDU, and the PDU set sequence number is encoded on multiple DRBs or multiple logical channels based on the PDU set sequence number in a PDCP service data unit (SDU).

[0056] Preferably, the suggested QoS assistance information sent to the CN includes at least one of the following parameters:

[0057] an aggregate maximum bit rate per cell preferred or allowed by the wireless communication node;

[0058] The maximum bit rate of each QoS flow carried by the wireless communication node is preferred or allowed;

[0059] an aggregate maximum bit rate per protocol data unit (PDU) session preferred or allowed by the wireless communication node;

[0060] a downlink (DL) PDU transmission time offset, for instructing the CN to transmit the PDU of the QoS flow or PDU session with a time delay offset or a time advance offset, wherein the DL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time or a current transmission timing opportunity;

[0061] DL PDU arrival time, used to indicate that the CN transmits a PDU of a QoS flow or a PDU session to ensure that the PDU arrives at the wireless communication node based on the DL PDU arrival time;

[0062] the maximum data packet size preferred or supported by the wireless communication node;

[0063] The wireless communication node preferably applies an encoded data rate;

[0064] A CN packet delay budget (PDB) detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing;

[0065] A CN data packet delay budget margin detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing;

[0066] a bit error rate (BER) detected by the wireless communication node;

[0067] a packet error rate (PER) detected by the wireless communication node;

[0068] Network node load information;

[0069] The network node's own computing power margin;

[0070] Requests for excess computing capacity in the core network or cloud native;

[0071] Uu time synchronization error budget;

[0072] Uu packet delay budget;

[0073] Uu packet delay budget margin;

[0074] The duration of the service preferably used for the wireless communication node to determine a DL data transmission opportunity; or

[0075] The start time of the preferably triggered service is used by the wireless communication node to determine the DL data transmission timing.

[0076] Preferably, the recommended QoS assistance information sent to the wireless communication terminal includes at least one of the following parameters:

[0077] The recommended QoS assistance information sent to the wireless communication terminal includes at least one of the following parameters:

[0078] an aggregate maximum bit rate per UE preferred or allowed by the wireless communication node;

[0079] an aggregate maximum bit rate per DRB preferred or allowed by the wireless communication node;

[0080] an aggregate maximum bit rate per logical channel preferred or allowed by the wireless communication node;

[0081] an aggregate maximum bit rate per logical channel group preferred or allowed by the wireless communication node;

[0082] The wireless communication node preferably applies an encoded data rate;

[0083] an uplink (UL) PDU transmission time offset, used to instruct the wireless communication terminal to transmit a PDU of a DRB or a logical channel with a time delay offset or a time advance offset, wherein the UL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity;

[0084] UL PDU transmission time, used to instruct the wireless communication terminal to transmit the PDU of the DRB or logical channel to ensure that the PDU is transmitted based on the indicated transmission time;

[0085] The BER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power;

[0086] The PER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power;

[0087] Network node load information;

[0088] The network node's own computing power margin;

[0089] Requests for excess computing capacity in the core network or cloud native;

[0090] Uu time synchronization error budget;

[0091] Uu packet delay budget;

[0092] Uu packet delay budget margin;

[0093] The duration of the preferably used service is used by the wireless communication terminal to determine the UL data transmission timing; or

[0094] The start time of the preferably triggered service is used by the wireless communication terminal to determine the UL service start time or UL data transmission timing.

[0095] Preferably, the buffer size indication comprises at least one of the following:

[0096] A specific buffer status report (BSR) format indicating that the buffer size is the same as the most recently reported buffer size;

[0097] a specific BSR medium access control (MAC) header with a new logical channel (LC) identifier (ID) indicating a buffer size that is the same as the buffer size most recently reported for the logical channel, logical channel group, or data radio bearer (DRB);

[0098] A specific BSR medium access control (MAC) header with a new logical channel (LC) identifier (ID) indicating a buffer size that is the same as the transmission size of the most recent transmission of the logical channel, logical channel group, or DRB; or

[0099] Uplink control information indicating that the buffer size is the same as the transmission size of the most recent transmission of the logical channel, logical channel group, or DRB.

[0100] Preferably, each C-DRX configuration includes a C-DRX index or a C-DRX identity for indicating the C-DRX configuration.

[0101] Preferably, the C-DRX index or C-DRX identity of each C-DRX configuration is represented by the order of the C-DRX configuration in the sequence.

[0102] Preferably, the wireless communication node sends a request with a C-DRX index or a C-DRX identity to the wireless communication terminal to modify, remove, activate or deactivate one of the C-DRX configurations corresponding to the C-DRX index or the C-DRX identity.

[0103] Preferably, the BSR includes at least one of the following:

[0104] a DL logical channel (LC) identifier (ID) or a DL LC priority, associated with the UL response PDU;

[0105] a DL PDU response indication associated with the UL response PDU; or

[0106] The related DL PDU information includes at least one of a PDU sequence number (SN) or PDU time domain information.

[0107] Preferably, the PDU time domain information includes at least one of system frame number information, time slot information or symbol information.

[0108] Preferably, the first PDU includes at least one of the following:

[0109] an identifier (ID) of the second wireless communication terminal;

[0110] information of the second PDU;

[0111] a quality of service (QoS), a flow ID, a logical channel (LC) ID, or a LC priority associated with the first PDU; or

[0112] A PDU response indication associated with the first PDU.

[0113] The exemplary embodiments disclosed herein are intended to provide some features, which will become more apparent by referring to the following description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. However, it should be understood that these embodiments are presented in an exemplary and non-restrictive manner, and it is obvious to those of ordinary skill in the art who read this disclosure that various modifications can be made to the disclosed embodiments within the scope of this disclosure.

[0114] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged within the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] The above-mentioned aspects and other aspects and their implementations are described in more detail in the drawings, the description and the claims.

[0116] Figure 1 A schematic diagram of a PDU set according to an embodiment of the present disclosure is shown.

[0117] Figure 2a A schematic diagram showing the timing of frames according to an embodiment of the present disclosure.

[0118] Figure 2b A schematic diagram showing different layers according to an embodiment of the present disclosure is shown.

[0119] Figure 3 A schematic diagram of a PDU set according to another embodiment of the present disclosure is shown.

[0120] Figure 4 A schematic diagram of a PDU set according to another embodiment of the present disclosure is shown.

[0121] Figure 5a A schematic diagram of a PDU set according to another embodiment of the present disclosure is shown.

[0122] Figures 5b to 5d A schematic diagram showing PDUs at different layers according to an embodiment of the present disclosure.

[0123] Figure 6a A schematic diagram of a PDU set according to another embodiment of the present disclosure is shown.

[0124] Figure 6b and 6cA schematic diagram of a PDCP PDU according to an embodiment of the present disclosure is shown.

[0125] Figures 7a to 7h A schematic diagram of a PDU according to an embodiment of the present disclosure is shown.

[0126] Figures 8a to 8c A schematic diagram of a PDU according to an embodiment of the present disclosure is shown.

[0127] Figure 8d A schematic diagram of a PDU set according to another embodiment of the present disclosure is shown.

[0128] Figures 8e to 8h A schematic diagram of a PDU according to an embodiment of the present disclosure is shown.

[0129] Figure 9a and 9b A schematic diagram of a communication method according to an embodiment of the present disclosure is shown.

[0130] Figures 10a to 10d A schematic diagram of a PDU or a BSR according to an embodiment of the present disclosure is shown.

[0131] Fig.11 A schematic diagram of a wireless communication terminal according to an embodiment of the present disclosure is shown.

[0132] Fig.12 A schematic diagram of a wireless communication node according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0133] In some embodiments, Figure 1 As shown, an application frame (e.g., an application data unit (ADU)) may include multiple IP (Internet Protocol) data packets, which may be represented in a set of PDUs (protocol data units) in a QoS (quality of service) flow. For example, a sequence of data packets may include all necessary information to reconstruct a video frame (e.g., equivalent to a "media unit" or "slice"), such as video, audio, frame, block, and / or tactile information. The data packets may be, for example, GTP-U (GPRS (General Packet Radio Service) Tunneling Protocol User Plane), NG (Next Generation) User Plane Interface (NG-U), Xn User Plane (Xn-U) Interface, or data packets of user data from NAS (Non Access Stratum).

[0134] Since different application frames have different (de)coding schemes, the QoS priority or importance level of the frames is different. For example, Figure 2a Shows Figure 1 The decoding timing (Decoding Time Sequence) and display timing (Presentation Time Sequence) of ADU.

[0135] In some embodiments, an I frame is a key frame that stores / transmits all the data needed to display the frame. In some embodiments, in compressed video, I frames are interspersed with P frames and B frames. The more I frames included, the better the video quality. However, I frames require many bits, require more space in the storage medium, and consume more wireless resources for transmission.

[0136] In some embodiments, a P frame is a delta frame that contains data that has changed (e.g., color or content changes) compared to the previous I frame. Therefore, a P frame relies on the previous I frame to fill in relevant data.

[0137] In some embodiments, a B frame is also a delta frame, which contains data that has changed from the previous frame and is different from the data in the next frame. Therefore, a B frame depends on the previous frame and the next frame to fill in the relevant data.

[0138] Different application frames may have different QoS priorities or importance levels for ADU decoding. For example, in an application data unit, the higher the QoS priority or importance level of the application frame, the smaller the decoding timing number.

[0139] In some embodiments, the QoS priority or importance level is indicated by the priority in the QoS flow. Because each QoS flow has only one priority, application frames with different priorities can be mapped to different QoS flows. However, there is no PDU sequence dependency information between PDUs in different QoS flows. Therefore, it is still unclear how to represent the PDU decoding timing in one application data unit.

[0140] In addition, after receiving all PDUs in a PDU set, the decoding side can decode the application frame. Figure 2bThe user plane protocol stack shown schedules PDU transmission in the RLC (radio link control) and / or MAC (Medium Access Control) layer, and the PDU corresponding to a PDU set is included in an SDAP (Service Data Adaption Protocol) PDU and / or PDCP (Packet Data Convergence Protocol) PDU, or the transmission entity in the RLC and / or MAC layer knows the PDU set used for wireless resource scheduling (for example, knows that the PDUs belong to the same PDU set) and ensures that all PDUs in a PDU set can arrive at the receiving side at the same time.

[0141] In some embodiments, a method for service characteristic indication in an NG interface, a PDCP entity, an RLC entity, and a MAC entity is provided.

[0142] In some embodiments, the gNB may receive a PDU including identification information from a higher layer; wherein the higher layer includes at least one of: a General Packet Radio Service Tunneling Protocol User Plane (GTP-U), a Next Generation user plane interface (NG-U), an Xn user plane, an Xn-U interface, user data from a non-access stratum (NAS), or user data of a QoS flow. The gNB may identify a PDU set of PDUs and a PDU set timing of the PDU set. For example, the gNB may identify the PDU set and the PDU set timing based on the identification information. Subsequently, the gNB may schedule the PDU for transmission over a Uu interface based on the PDU set and the PDU set timing. The identification information includes at least one of a PDU set sequence number and / or PDU set information. The PDU set information includes at least one of a PDU set start indication and / or a PDU set end indication. In one embodiment, the Uu interface is an interface between the gNB and the UE. Details of the present disclosure are provided in the following embodiments, and the present disclosure is not limited thereto.

[0143] Embodiment 1 (Mapping between PDU set and QoS flow):

[0144] Figure 3The mapping between GTP-U, NG-U, Xn-U or NAS-U (Non Access Stratum User Plane Data) PDU sets and QoS flows is shown, where the PDU set timing is indicated by the PDU set sequence number.

[0145] In one embodiment, the PDU set is identified by a PDU set sequence number, and the PDU set timing is indicated by the PDU set sequence number. The PDU set sequence number is encoded / numbered across multiple QoS flows of each PDU session or each service flow to indicate an application frame sequence and / or an application data unit sequence.

[0146] In one embodiment, the PDU set timing may be the PDU set decoding timing (for example, the next PDU set can be decoded only when the current PDU set is successfully decoded), or the PDU set display timing (for example, for a video stream, picture frames are displayed one by one according to the display timing).

[0147] Since the PDU set is decoded based on the decoding timing in the receiving node, once one PDU set is not successfully transmitted, the next PDU set cannot be successfully decoded. Preferably, the PDU set is transmitted based on the decoding timing.

[0148] exist Figure 3 An example is used in which the PDU set timing is indicated by the PDU set sequence number.

[0149] One application frame includes a plurality of IP data packets (eg, PDUs) constituting one PDU set.

[0150] Since PDU set decoding is based on decoding timing, different PDU sets have different priorities or importance levels. Therefore, different PDU sets are mapped to different QoS flows, and the PDU set sequence number is encoded / numbered across multiple QoS flows based on decoding timing. The QFI (QoS Flow Identifier) ​​sequence number is encoded / numbered per QoS flow.

[0151] For example, in the case corresponding to Figure 3 In the embodiment, the receiving side sequentially decodes I1 frame, P4 frame, B2 frame, etc. based on the decoding timing.

[0152] The I1 frame includes I11, I12, ..., I1n packets (PDUs). These packets correspond to PDU set 1, are mapped to QoS flow identifier #1, and have PDU set sequence number 1.

[0153] The P4 frame includes P41, P42, ..., P4b packets (PDUs). These packets correspond to PDU set 2, are mapped to QoS flow identifier #2, and have PDU set sequence number 2.

[0154] The B2 frame includes B21, B22, ..., B2m packets (PDUs). These packets correspond to PDU set 3, are mapped to QoS flow identifier #3, and have PDU set sequence number 3.

[0155] The same goes for other frames.

[0156] Since the DL (downlink) QFI sequence number is encoded / numbered per QoS flow, the DL QFI sequence number can be the same or different for PDUs in different QoS flows.

[0157] In one embodiment, the numeric number is used only to indicate the serial number.

[0158] Figure 4 The mapping between GTP-U, NG-U, Xn-U or NAS-U PDU sets and QoS flows is shown, where the PDU set timing is indicated by the DL QFI sequence number.

[0159] In one embodiment, the PDU set is identified by PDU set information including a PDU set start indication and / or a PDU set end indication. The PDU set timing is indicated by a DL QFI sequence number, which is encoded / numbered across multiple QoS flows of each PDU session or each service flow to indicate an application frame sequence and / or an application data unit sequence.

[0160] In one embodiment, the PDU set timing may be the PDU set decoding timing (for example, the next PDU set can be decoded only when the current PDU set is successfully decoded), or the PDU set display timing (for example, for a video stream, picture frames are displayed one by one according to the display timing).

[0161] exist Figure 4 An example is used in FIG. 5 to show that the PDU set timing is indicated by the DL QFI sequence number.

[0162] An application frame includes multiple IP data packets constituting a PDU set, and is identified by a PDU set start indication and a PDU set end indication. For example, in PDU set 1: data packet I11 corresponds to the PDU set start indication, and data packet I1n corresponds to the PDU set end indication.

[0163] Since PDU set decoding is based on decoding timing, different PDU sets have different priorities or importance levels. Therefore, different PDU sets are mapped to different QoS flows. When PDU set information (e.g., PDU set start indication or PDU set end indication) is included, the DL QFI sequence number is encoded / numbered across multiple QoS flows based on decoding timing.

[0164] For example, in the case corresponding to Figure 4 In the embodiment, the receiving side sequentially decodes I1 frame, P4 frame, B2 frame, etc. based on the decoding timing.

[0165] The I1 frame includes I11, I12, ..., I1n packets (PDUs). These packets correspond to PDU set 1 and are mapped to QoS flow identifier #1. The DL QFI sequence numbers of packets I11, I12, ..., I1n are encoded / numbered as 11, 12, ..., 1n.

[0166] The P4 frame includes P41, P42, ..., P4b packets (PDUs). These packets correspond to PDU set 2 and are mapped to QoS flow identifier #2. The DL QFI sequence numbers of packets P41, P42, ..., P4b are encoded / numbered as 1n+1, 1n+2, ..., 1n+b.

[0167] The B2 frame includes B21, B22, ..., B2m packets (PDUs). These packets correspond to PDU set 3 and are mapped to QoS flow identifier #3. The DL QFI sequence numbers of packets B21, B22, ..., B2m are encoded / numbered as 1n+b+1, 1n+b+2, ..., 1n+b+m.

[0168] The same goes for other frames.

[0169] In one embodiment, the numeric number is used only to indicate the serial number.

[0170] When PDU aggregation information is included in the PDU session information format, DL QFI sequence numbers are encoded / numbered across multiple QoS flows based on the PDU aggregation decoding timing to indicate the decoding timing. When PDU aggregation information is not included in the PDU session information format, DL QFI sequence numbers are encoded per QoS flow.

[0171] Embodiment 2 (PDUs in a PDU set are mapped to one SDAP PDU):

[0172] Figure 5a The mapping between the PDU set and the SDAP PDU is shown, where the PDUs in the GTP-U, NG-U, Xn-U or NAS-U PDU set are included in one SDAP PDU.

[0173] In some embodiments, one SDAP SDU (service data unit) (eg, GTP-U PDU, NG-U PDU, Xn-U PDU or NAS-U PDU) is included in the SDAP PDU starting from the first bit.

[0174] In one embodiment, through the connection of data packets, all PDUs in a PDU set are included in one SDAP PDU. For example, the PDUs in PDU set 1 are included in one SDAP PDU, the PDUs in PDU set 2 are included in another SDAP PDU, and so on.

[0175] Figure 5b The SDAP data PDU format is shown without the SDAP header but with multiple upper layer PDUs. Figure 5c The DL SDAP data PDU format with the SDAP header is shown. Figure 5d The UL SDAP data PDU format is shown with a SDAP header and multiple upper layer data PDUs.

[0176] like Figure 5b , Figure 5c and Figure 5d As shown, the SDAP PDU includes multiple upper layer data PDUs in one PDU set, where PDUs in one PDU set or QoS flow (e.g., GTP-U, NG-U, Xn-U, or NAS-U PDU) are included in one SDAP PDU. The PDUs are connected one by one based on the PDU sequence number and are included in the data field (Data) of the SDAP PDU starting from the first bit.

[0177] Embodiment 3 (PDUs in a PDU set are mapped to one PDCP PDU):

[0178] Figure 6a The mapping between the PDU set and the PDCP PDU is shown, where the PDUs in one GTP-U, NG-U, Xn-U or NAS-U PDU set are mapped to one PDCP PDU. More specifically, the PDUs in one PDU set (e.g., GTP-U, NG-U, Xn-U or NAS-U PDU set) are included in one or more SDAP PDUs, and all SDAP PDUs corresponding to one PDU set (e.g., GTP-U, NG-U, Xn-U or NAS-U PDU set) are included in one PDCP PDU.

[0179] Figure 6b and 6c A PDCP PDU including a plurality of PDCP SDUs (e.g., SDAP PDUs) is shown, including Figure 6b A plurality of PDCP data fields having corresponding MAC-I fields and connected in sequence, or a plurality of PDCP data fields and a corresponding MAC-I field are connected in sequence (see Figure 6c ).

[0180] A PDCP data field (e.g. Figure 6b and Figure 6c Data1 or Data2) corresponds to a PDCP SDU (e.g., SDAP PDU).

[0181] Embodiment 4 (PDU set indication in SDAP, PDCP and RLC PDU):

[0182] In this embodiment, PDUs in one PDU set are included in a plurality of PDCP PDUs, and PDU set information is included in SDPA PDUs, PDCP PDUs, and / or RLC PDUs to indicate which PDUs belong to one PDU set.

[0183] Based on the corresponding Figure 3 or Figure 4 In the embodiment of the PDU set sequence number and / or PDU set information, the SDAP entity can identify the start and end timing of the PDU set. However, the DL authorization is scheduled in the MAC layer, and the RLC layer and / or the MAC layer decides whether the PDUs in a PDU set are transmitted in a TB (transport block), in a TB group, or in the same time domain position. Therefore, the RLC layer and / or the MAC layer also need information on the start and end timing of the PDU set.

[0184] In some embodiments, all TBs of an RLC PDU are successfully received before connection. The RX (receive) side RLC entity can know whether all TBs of an RLC PDU are successfully received based on the SN (sequence number) and SI (system information) fields and / or the SN, SI and SO (segment offset) fields. The SI and SO fields are for the same RLC SDU (e.g., the same PDCP PDU).

[0185] For PDU sets with multiple PDCP PDUs, there are some possible solutions to indicate to the RLC and / or MAC layer that multiple RLC SDUs belong to the same PDU set.

[0186] Option 1: The SDAP PDU set field, PDCP PDU set field and / or RLC PDU set field including information for PDU set identification are included in the SDAP, PDCP and / or RLC PDU format as temporary header fields, which are maintained on the TX (transmit) side and may not be transmitted over the Uu interface.

[0187] Option 2: An SDAP PDU set field, a PDCP PDU set field and / or an RLC PDU set field including information for PDU set identification is introduced into the SDAP, PDCP and / or RLC PDU format, for example, using reserved bits of the existing PDU format for transmission over the Uu interface without increasing the Uu system overhead, or using a new PDU format for transmission over the Uu interface.

[0188] Figure 7a It is shown that the SDAP PDU includes a PDU set sequence number. In this embodiment, the PDU set sequence number is used to indicate which PDU set the corresponding PDU belongs to. For example, PDUs with the same SDAP PDU set sequence number belong to the same PDU set.

[0189] Figure 7b It is shown that the SDAP PDU includes PDU set information. In this embodiment, the PDU set information is used to indicate which PDUs belong to a PDU set. For example, a PDU set start indication and / or a PDU set end indication may be included in the SDAP PDU. A PDU sequence starting from the first PDU with a PDU set start indication to the last PDU with a PDU set end indication belongs to a PDU set.

[0190] Figure 7c It is shown that PDU set information (PSI) is included in a PDCP data PDU with a 12-bit PDCP SN. Figure 7d It is shown that PDU set information (PSI) is included in the PDCP data PDU of DRBs (data radiobearers) with 18-bit PDCP SN.

[0191] like Figure 7c and Figure 7d As shown, the PDU set information is indicated in the PDCP PDU. Figure 7c and Figure 7d In an embodiment, a PDU set information (PI or PSI) field is included in the PDCP PDU to indicate which PDCP PDUs correspond to a PDU set and are transmitted in a TB, in a TB group, or in the same time domain position.

[0192] Figure 7e It is shown that PDU set information (PSI) is included in a UMD (unacknowledged mode data) RLC PDU with a 12-bit SN (without SO). Figure 7fIt is shown that PDU set information (PSI) is included in the UMD RLC PDU with a 12-bit SN (with SO). Figure 7g It is shown that PDU set information (PSI) is included in an AMD (acknowledged mode data) RLC PDU with an 18-bit SN (without SO). Figure 7h It is shown that PDU set information (PSI) is included in the AMD RLC PDU with 18-bit SN (with SO).

[0193] like Figure 7c , 7d As shown in 7e, 7f, 7g and 7h, the PDU set information is indicated in the PDCP PDU and / or RLC PDU.

[0194] In some embodiments, a PDU set information (PI or PSI) field is included in the PDCP PDU to indicate which RLC PDUs correspond to one PDU set and are transmitted in one TB, one TB group, or the same time domain position.

[0195] The UMD PDU header contains the SN field only when the corresponding RLC SDU is segmented or when PDU aggregation information is included in the UMD PDU. If the PDU aggregation information is included in the PDU, the SN in the PDU is coded / numbered in the PDU aggregation (e.g., across multiple SDUs).

[0196] In some embodiments, the PDU Set Information (PI or PSI) field may be encoded as follows.

[0197] In one embodiment, the PI field may be used. In one embodiment, the PI field may have a length of 2 bits. In one embodiment, the PI field is used to indicate whether some PDUs correspond to the same PDU set. For example, the PI field may indicate that the PDU is at the beginning, middle and / or end of the PDU set, or that the PDU set information is not included. Specifically, the PI field indicates whether the PDU set information is not included, whether the PDU corresponds to the first PDU of the PDU set, whether the PDU corresponds to the last PDU of the PDU set, and whether the PDU corresponds neither to the first PDU of the PDU set nor to the last PDU of the PDU set. An explanation of the PI field is provided in Table 1.

[0198] Table 1: PI field explanation

[0199]

[0200] Alternatively, the PSI field may be used. In one embodiment, the PSI field may have a length of 2 bits. In one embodiment, the PSI field indicates whether the PDU set contains a single SDU, or whether the corresponding PDU is the first PDU, the last PDU, or the middle PDU (neither the first nor the last PDU) of the PDU set, or does not include PDU set information. An explanation of the PSI field is provided in Table 2.

[0201] Table 2: PSI field explanation

[0202]

[0203]

[0204] It should be noted that the mapping between the value and the description may vary. For example, the value "01" may be used to indicate that the PDU is the last PDU of a PDU set, and the value "10" may be used to indicate that the PDU is the first PDU of a PDU set.

[0205] In some embodiments, when segmentation is not supported in PDCP, one PDCP PDU corresponds to one PDCP SDU. The PI (or PSI) of the PDCP PDU can be configured based on the PDU set information of the PDCP SDU (e.g., DL PDU session information (PDU type 0) format enhancement or SDAP PDU). For example, the first PDCP SDU of the PDU set from the upper layer is set to the first PDCP PDU, and the last PDCP SDU of the PDU set from the upper layer is set to the last PDCP PDU.

[0206] In some embodiments, since an RLC SDU may be segmented into multiple RLC PDUs, and multiple RLC PDUs correspond to the same SN number with different SIs and / or SOs, the PI (or PSI) of the RLC PDU may be set using the following options:

[0207] Option 1: Setting PI (or PSI) based on sequence number For example, multiple RLC PDUs with the same RLC SDU SN (eg, PDCP PDU SN) are configured with the same PI (or PSI) value.

[0208] Option 2: PI (or PSI) is set based on RLC PDU. For example, only one RLC PDU is set as the first PDU in the PDU set, and only one RLC PDU is set as the last PDU in the PDU set. That is, the PI (or PSI) of the first PDU (SI=01) of the first RLC SDU is set to the first PDU in the PDU set (e.g., the value "01"), and the PI (or PSI) of the last PDU (SI=10) of the last RLC SDU is set to the last PDU in the PDU set (e.g., the value "10").

[0209] In some embodiments, when segmentation is supported in PDCP, the same rules for setting the PI (or PSI) field of the RLC PDU may be applied to the PDCP PDU.

[0210] Based on the PI (or PSI) field and the SN, the lower layer can know which PDUs correspond to a PDCP PDU set. For example, the lower layer can know the start SN and the end SN of the PDU set.

[0211] In some embodiments, the PDU set information (e.g., PI or PSI) of the RLC PDU and / or PDCP PDU may be used only for TX side scheduling and not for RX side reception and decoding. The PDU set information (e.g., PI or PSI) may be set in a temporary header field of the PDCP PDU and / or RLC PDU, for example, the temporary header field is appended to the PDCP PDU and / or RLC PDU. In this case, when a lower layer entity receives a PDCP PDU and / or RLC PDU with a temporary header field, the lower layer may remove the temporary header field after retrieving the PDU set information. Therefore, the temporary header field may not be transmitted over the Uu interface (e.g., may not be transmitted from a gNB (gNodeB) to a UE (user equipment), or may not be transmitted from a UE to a gNB).

[0212] Embodiment 5 (PDU set dependency indication):

[0213] In some embodiments, PDU sets may be dependent on each other (e.g., in a video streaming service, a B frame depends on its previous adjacent frame; and a P frame depends on its previous adjacent frame and next adjacent frame), and different PDU sets may have different priorities (e.g., importance levels). In some embodiments, various options are provided as follows to identify dependencies and priorities.

[0214] Option 1: Different PDU sets with different priorities are mapped to one DRB, and a PDU set type indication (e.g., the PDU set corresponds to an I frame, corresponds to a B frame, or corresponds to a P frame, a primary frame, a secondary frame, an nth secondary frame, where n is an integer) or a PDU set dependency indication (e.g., the PDU set is separate, depends on the immediately preceding PDU set, depends on the immediately preceding PDU set and the immediately following PDU set) is indicated in the PDCP SDAP PDU.

[0215] Figure 8a It is shown that the PDU set dependency indication is included in the SDAP PDU. Figure 8b It is shown that the PDU set dependency indication is included in the PDCP PDU. Figure 8c It is shown that the PDU set dependency indication is included in the RLC PDU. Whether to use the new SDAP PDU format, PDCP PDU format and / or RLC PDU format can be explicitly indicated through UE-specific signaling.

[0216] Option 2: Different PDU sets with different priorities are mapped to different QoS flows and mapped to different DRBs and / or different logical channels. The PDU set dependency between PDU sets is implicitly indicated by the SN in the PDU. For example, when the PDU set information is included in the PDCP PDU, the SN in the PDCP PDU is encoded / numbered over multiple DRBs and / or multiple logical channels. When the PDU set information is included in the RLC PDU, the SN in the RLC PDU is encoded / numbered over multiple DRBs and / or multiple logical channels.

[0217] Figure 8d It is shown that when PDU aggregation information is included, the SNs in the PDCP PDU and RLC PDU are encoded / numbered across multiple DRBs and / or multiple logical channels.

[0218] In one embodiment, the PDCP PDUs in PDU set 1 are mapped to the DRB#1 tunnel, and the PDCP PDUs in PDU set 2 are mapped to the DRB#2 tunnel.

[0219] In one embodiment, the RLC PDUs in PDU set 1 are mapped to LC#1, and the RLC PDUs in PDU set 2 are mapped to LC#2. LC stands for logical channel.

[0220] In one embodiment, the sequence numbers of the PDCP PDUs in PDU set 1 are encoded / numbered from 1 to n, and the sequence numbers of the PDCP PDUs in the subsequent PDU set (e.g., PDU set 2) are encoded / numbered from n+1 to n+x, and so on.

[0221] In one embodiment, the sequence numbers of the RLC PDUs in PDU set 1 are encoded from 1 to m, the sequence numbers of the RLC PDUs in the subsequent PDU sets (eg, PDU set 2) are encoded from m+1 to m+y, and so on.

[0222] Option 3: Explicitly indicate the dependency / information. For example, the associated sequence number, the associated DRB ID (identifier) ​​and / or the logical channel ID are included in the PDCP PDU and / or the RLC PDU.

[0223] Figure 8e shows that the PDU dependency information is included in the PDCP PDU, and Figure 8f It is shown that the PDU dependency information is included in the RLC PDU.

[0224] In one embodiment, the PDU dependency information is explicitly indicated in the PDU. In one embodiment, the PDU dependency information includes at least one of the following: a dependent DRB ID (e.g., indicating the DRB on which the corresponding PDU depends), a dependent LC ID (e.g., indicating the LC on which the corresponding PDU depends), a dependent PDU SN (e.g., indicating the SN of the PDU on which the corresponding PDU depends), and / or a dependent PDU SN LSB (Least Significant Bit) (e.g., indicating the LSB in the SN of the PDU on which the corresponding PDU depends, the SN LSB is used instead of the SN to reduce the bit requirement).

[0225] In one embodiment, whether to use the new PDCP PDU format and / or RLC PDU format may be explicitly indicated through UE-specific signaling.

[0226] In one embodiment, since the associated sequence number (e.g., “dependent PDU's SN” as described above) and the associated DRB ID (e.g., “dependent DRB ID” as described above) or LC ID (e.g., “dependent LCID” as described above) are only used in TX scheduling and have many bits (overhead), some optimizations can be applied.

[0227] Option 1: Only the LSB of the SN is used as the associated sequence number.

[0228] Option 2: The associated sequence number, the associated DRB ID and / or the logical channel ID are designed as a temporary header field of the PDCP PDU and / or the RLC PDU, and the temporary header field is attached to the PDCP PDU and / or the RLC PDU. When the lower layer receives the PDCP PDU and / or the RLC PDU and obtains the temporary header field information, the lower layer may remove the temporary header field. Therefore, the temporary header field may not be transmitted over the Uu interface (e.g., not transmitted from the gNB to the UE, or not transmitted from the UE to the gNB).

[0229] Option 4: The PDU set sequence number is included in the PDCP PDU and / or RLC PDU, and the PDU set sequence number is encoded / numbered over multiple DRBs and / or multiple logical channels based on the PDU set sequence number in the PDCP SDU. The PDU set in the PDCP PDU or RLC PDU may correspond to the same user data contained in a GTP-U, NG-U, Xn-U or NAS-U PDU set, and a PDU set in a QoS flow, regardless of whether the PDU set is segmented or not, and regardless of whether the PDU set is fused or not.

[0230] Figure 8g It shows that the PDU set SN (sequence number) is included in the PDCP PDU. Figure 8h It is shown that the PDU set SN is included in the RLC PDU.

[0231] In one embodiment, whether to use the new PDCP PDU format and / or RLC PDU format may be explicitly indicated through UE-specific signaling.

[0232] If the PDU set information is included in the corresponding PDU, the PDU set SN is encoded / numbered on multiple DRBs and / or multiple logical channels.

[0233] Based on the PDU set SN and / or the PDU SN, the PDU set timing may be identified.

[0234] Embodiment 6 (Reflective QoS indication):

[0235] Figure 9a The procedures related to reflective QoS indication or proactive QoS update request are shown.

[0236] In one embodiment, based on NW (network) capabilities and / or NW preferences, a reflective QoS indication or an active QoS update request is sent from the gNB to the CN to trigger a QoS parameter update. For example, the RAN (Radio Access Network) provides QoS assistance information to the CN or application layer to request dynamic adjustment of QoS parameters.

[0237] In one embodiment, the QoS assistance information includes at least one of the following parameter types: recommended QoS parameter values, recommended QoS flow priorities, recommended application data and QoS flow mapping, recommended paging strategy, UE mobility information, artificial intelligence related information, machine learning related information, network usage perception, network computing capabilities and / or UE positioning related information.

[0238] In one embodiment, the gNB may provide one or more sets of recommended QoS assistance information, and the CN may determine, select, accept, reject, or recommend QoS information based on the one or more sets of recommended QoS assistance information.

[0239] In one embodiment, the QoS assistance information includes at least one of the following parameters:

[0240] The aggregate maximum bit rate per cell, carried via cell-specific signaling preferred or allowed by the gNB;

[0241] Maximum bit rate per QoS flow carried, either via UE-specific signalling or NG-U PDUs as preferred or allowed by the gNB;

[0242] Aggregate maximum bit rate per PDU session, carried via UE-specific signalling or NG-U PDUs as preferred or allowed by the gNB;

[0243] DL PDU transmission time offset, carried by UE-specific signaling or NG-U PDU, used to instruct the CN to transmit the PDU of the QoS flow and / or PDU session with a time delay offset (e.g., corresponding to the DL PDU transmission time offset) or a time advance offset (e.g., corresponding to the DL PDU transmission time offset). The DL PDU transmission time offset is related to at least one of the current transmission start time, the current transmission end time and / or the current transmission timing opportunity;

[0244] DL PDU arrival time, carried via UE-specific signalling or NG-U PDU, used to indicate to the CN to transmit PDUs of QoS flows and / or PDU sessions to ensure that the PDUs arrive at the gNB based on the indicated DL PDU arrival time;

[0245] The maximum packet size preferred or supported by the gNB, carried via UE-specific signaling or NG-UPDU, to ensure that the received packet size can fit within the gNB;

[0246] The gNB's preferred application coding data rate is carried via UE-specific signaling or NG-U PDUs and is used to dynamically adjust the application coding data rate;

[0247] CN PDB (Packet Delay Budget) detected by the gNB, carried via UE-specific signaling or NG-U PDU, used by the gNB to determine the timing of DL data transmission; BER detected by the gNB;

[0248] PER detected by gNB;

[0249] Network node load information;

[0250] The network node's own computing power margin;

[0251] Requests for excess computing capacity in the core network or cloud native;

[0252] Uu time synchronization error budget;

[0253] Uu packet delay budget;

[0254] Uu packet delay budget margin;

[0255] The duration of the preferred service, carried in UE-specific signalling or in NG-U PDUs, for the gNB to decide on DL data transmission opportunities; and / or

[0256] The start time of the preferentially triggered service is carried by UE-specific signaling or NG-U PDU for gNB to decide the timing of DL data transmission.

[0257] QoS assistance information can be used to trigger DL user data rate adaptation (e.g., applying coding data rate adjustment from HD (high definition) video to SD (standard definition) video or from SD video to HD video) to map traffic patterns and network resources, and / or adjust QoS parameters and improve user experience.

[0258] Figure 9b Another process related to reflective QoS indication or proactive QoS update request is shown.

[0259] In one embodiment, based on NW (network) capabilities and / or NW preferences, a reflective QoS indication or an active QoS update request is sent from the gNB to the UE to trigger a QoS parameter update. For example, the RAN (radio access network) provides QoS assistance information to the UE to request dynamic adjustment of QoS parameters.

[0260] In one embodiment, the QoS assistance information includes at least one of the following parameter types: recommended QoS parameter values, recommended QoS flow priorities, recommended application data and QoS flow mapping, recommended paging strategy, UE mobility information, artificial intelligence related information, machine learning related information, network usage perception, network computing capabilities and / or UE positioning related information.

[0261] In one embodiment, the gNB may provide one or more sets of recommended QoS assistance information, and the UE may determine, select, accept, reject or recommend QoS information based on the one or more sets of recommended QoS assistance information.

[0262] In one embodiment, the QoS assistance information includes at least one of the following parameters:

[0263] The aggregate maximum bit rate per UE preferred or allowed by the gNB;

[0264] The aggregate maximum bit rate per DRB preferred or allowed by the gNB;

[0265] The aggregate maximum bit rate per logical channel preferred or allowed by the gNB;

[0266] The aggregate maximum bit rate per logical channel group preferred or allowed by the gNB;

[0267] The gNB preferably uses an application coding data rate for dynamically adjusting the application coding data rate;

[0268] UL PDU transmission time offset, used to indicate that the UE transmits the PDU of the DRB and / or logical channel with a time delay offset (e.g., corresponding to the UL PDU transmission time offset) or a time advance offset (e.g., corresponding to the UL PDU transmission time offset). The UL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time and / or a current transmission timing opportunity;

[0269] UL PDU transmission time, used to instruct the UE to transmit the PDU of the DRB and / or logical channel to ensure that the PDU is transmitted based on the indicated transmission time;

[0270] The BER detected by the gNB is used by the UE to adjust the coding rate and / or transmission power;

[0271] PER detected by the gNB, which is used by the UE to adjust the coding rate and / or transmit power;

[0272] The network node's own computing power margin;

[0273] Requests for excess computing capacity in the core network or cloud native;

[0274] Uu time synchronization error budget;

[0275] Uu packet delay budget;

[0276] Uu packet delay budget margin;

[0277] The duration of the preferred service, which is used by the UE to determine the UL data transmission timing; and / or

[0278] The start time of the service that is preferably triggered is used by the UE to determine the UL service start time or UL data transmission timing.

[0279] In one embodiment, QoS auxiliary information is carried by at least one of RRC (Radio Resource Control) unicast signaling, MAC CE (control element) or PDCCH (physical downlink control channel) DCI (Downlink Control Information).

[0280] In one embodiment, QoS assistance information can be used to trigger UL user data rate adaptation (e.g., applying coding data rate adjustment from HD video to SD video or from SD video to HD video) to map traffic patterns and network resources and / or improve user experience.

[0281] Embodiment 7 (specific buffer size indication):

[0282] For full buffer services or XR services with fixed buffer size, the UE may indicate the UL buffer size to the gNB in ​​one of the following ways:

[0283] Use a specific BSR format (e.g., including only LCG (logical channel group) ID, LC ID, or DRB ID in a MAC CE format with a new LC ID for MAC CE identification) to indicate that the buffer size is the same as the most recently reported BS;

[0284] Use only the BSR MAC header with a new LC ID (e.g., a zero-byte MAC CE) to indicate that the buffer size is the same as the buffer size most recently reported by the logical channel, logical channel group, or DRB; or

[0285] Only the BSR MAC header with a new LC ID (eg, zero-byte MAC CE) is used to indicate that the buffer size is the same as the transport block size most recently transmitted by the logical channel, logical channel group, or DRB.

[0286] Uplink Control Information (UCI) is used to indicate that the buffer size is the same as the most recently reported buffer size or the most recently transmitted transmission size of a logical channel, a logical channel group, or a DRB.

[0287] With this configuration, BSR MAC CE radio resource consumption can be reduced.

[0288] Embodiment 8 (Multiple C-DRX (Discontinuous Reception in RRC_Connected state) configurations):

[0289] In some embodiments, multiple C-DRX (DRX in RRC connected state) can be configured for each cell group, each DRB, and each logical channel to handle non-integer cycle problems and / or matching business mode problems. For example, in XR services, fps (frames per second) or Hz (Hertz) can be used as units to indicate the service transmission frequency. However, the unit used for the C-DRX cycle is ms (milliseconds), and fps or Hz may not be fully mapped to ms. For example, 60fps or 60Hz can be converted to a period of 16.6666... ​​milliseconds (this is not an integer), and the business mode cannot be fully mapped to the C-DRX configuration. In this case, multiple C-DRX modes can be used to map business modes. For example, the following three C-DRX configurations can be used to map 60fps or 60Hz business modes.

[0290] C-DRX start time cycle C-DRX 1 Start frame = 0, start subframe = 0 50 ms C-DRX 2 Start frame = 1, start subframe = 7 50 ms C-DRX 3 Start frame = 3, start subframe = 4 50 ms

[0291] When multiple C-DRX modes are configured for each cell group, each DRB, and each logical channel, a C-DRX index or a C-DRX identity is used to identify each C-DRX configuration.

[0292] In one embodiment, the C-DRX index or C-DRX identity may be explicitly configured in the C-DRX configuration.

[0293] In one embodiment, the C-DRX index or C-DRX identity may be implicitly indicated based on the C-DRX configuration sequence entries. For example, the first entry of the sequence corresponds to the first C-DRX configuration, the C-DRX index (or C-DRX identity) is equal to 1, the second entry of the sequence corresponds to the second C-DRX configuration, the C-DRX index (or C-DRX identity) is equal to 2, and so on.

[0294] In one embodiment, based on the C-DRX index or C-DRX identity, one or more C-DRX configurations may be independently modified, removed, activated or deactivated using incremental configuration. For example, when removing a certain C-DRX configuration, only the C-DRX index or C-DRX identity corresponding to the C-DRX configuration may be indicated to the UE. In this case, it may be avoided to indicate all new C-DRX configurations to the UE to overwrite the old C-DRX configurations.

[0295] Embodiment 9 (PDU relationship indication between UL and DL or between UEs):

[0296] Fig.10a A buffer size report is shown. Fig.10b Buffer size reporting with DL PDU response information is shown.

[0297] like Fig.10a and Fig.10b As shown, the relationship indication between the UL PDU and DL PDU that triggers the BSR is shown.

[0298] After receiving the DL PDU, the UE may trigger the BSR MAC CE to send a UL response PDU.

[0299] In one embodiment, the BSR MAC CE includes at least one of the following information:

[0300] The DL LC ID or DL ​​LC priority associated with the UL PDU that triggered the BSR, such as Fig.10a As shown;

[0301] DL PDU response indication related to the UL PDU that triggered the BSR, such as Fig.10b as shown; and / or

[0302] Related DL PDU information, such as Fig.10a and Fig.10b As shown, it includes at least one of PDU SN or PDU time domain information (for example, SFN (System Frame Number, system frame number) information, time slot information (Slot information) and / or symbol information (Symbol information)).

[0303] Fig.10c A PDU or BSR including UE ID information and PDU information is shown. Fig.10d A PDU or BSR including UE ID information and PDU response information is shown.

[0304] like Fig.10c and Fig.10dAs shown, a relationship indication between UEs is shown.

[0305] In one embodiment, the PDU or BSR includes at least one of the following:

[0306] The relevant UE ID (e.g., C-RNTI), such as Fig.10c and Fig.10d As shown;

[0307] Related PDU information, such as Fig.10c and Fig.10d As shown, at least one of the PDU SN or PDU time domain information (e.g., SFN information, time slot information and / or symbol information);

[0308] A QoS Flow ID, LC ID, or LC priority associated with a PDU (e.g., the current PDU); and / or

[0309] PDU response indication related to the current PDU.

[0310] In one embodiment, the current PDU includes at least one of a GTP-U PDU, a NG-U PDU, a Xn-UPDU, a NAS-U PDU, a SDAPPDU, a PDCP PDU and / or a RLC PDU.

[0311] In one embodiment, based on the relationship indication as described above, the gNB may determine the resource scheduling priority or UL grant for uplink SR (scheduling request), UL BSR and / or PUSCH transmission.

[0312] Fig.11 A schematic diagram of a wireless communication terminal 30 (e.g., a terminal node or terminal device) according to an embodiment of the present disclosure is provided. The wireless communication terminal 30 may be a user equipment (UE), a remote UE, a relay UE, a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, but is not limited thereto herein. The wireless communication terminal 30 may include a processor 300 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device storing program code 312 accessed and executed by the processor 300. Embodiments of the storage code 312 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 320 may be a transceiver for sending and receiving signals (e.g., messages or data packets) according to the processing results of the processor 300. In one embodiment, the communication unit 320 sends and receives signals via at least one antenna 322.

[0313] In one embodiment, the storage unit 310 and the program code 312 may be omitted, and the processor 300 may include a storage unit storing the program code.

[0314] The processor 300 may implement any one of the steps of the exemplary embodiments on the wireless communication terminal 30 , for example, by executing the program code 312 .

[0315] The communication unit 320 may be a transceiver. The communication unit 320 may alternatively or additionally combine a transmission unit and a reception unit configured to transmit and receive signals to and from a wireless communication node, respectively.

[0316] In some embodiments, the wireless communication terminal 30 may be used to perform the above-mentioned UE operations. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the above-mentioned operations. For example, the processor 300 performs operations and sends or receives signals, messages and / or information through the communication unit 320.

[0317] Fig.12 A schematic diagram of a wireless communication node 40 (e.g., a network device) according to an embodiment of the present disclosure is provided. The wireless communication node 40 may be a satellite, a base station (BS), a gNB, a gNB-DU, a gNB-CU, a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network, a communication node in a core network, or a radio network controller (RNC), but is not limited thereto herein. In addition, the wireless communication node 40 may include (execute) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), an application function (AF), etc. The wireless communication node 40 may include a processor 400 such as a microprocessor or an ASIC, a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device storing a program code 412 accessed and executed by the processor 400. Examples of the storage unit 412 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 420 may be a transceiver for transmitting and receiving signals (eg, messages or data packets) according to the processing result of the processor 400. In an example, the communication unit 420 transmits and receives signals through at least one antenna 422.

[0318] In one embodiment, the storage unit 410 and the program code 412 may be omitted. The processor 400 may include a storage unit storing the program code.

[0319] The processor 400 may implement any of the steps described in the exemplary embodiments on the wireless communication node 40 , for example by executing the program code 412 .

[0320] The communication unit 420 may be a transceiver. The communication unit 420 may alternatively or additionally combine a transmitting unit and a receiving unit configured to transmit and receive signals, messages or information to and from a wireless communication node or a wireless communication terminal, respectively.

[0321] In some embodiments, the wireless communication node 40 may be used to perform the above-mentioned gNB operations. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the above-mentioned operations. For example, the processor 400 performs operations and sends or receives signals through the communication unit 420.

[0322] The details in this regard can be determined by referring to the above paragraphs and will not be repeated in this article.

[0323] Although various embodiments of the present disclosure have been described above, it should be understood that these embodiments are presented only in an exemplary and non-restrictive manner. Similarly, various schematic diagrams can depict example architectures or configurations, and these schematic diagrams are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, it will be appreciated by those of ordinary skill in the art that the present disclosure is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be appreciated by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

[0324] It should also be understood that any reference to an element using names such as "first," "second," etc. herein does not generally limit the number or order of these elements. Instead, these names may be used herein as a convenient means of distinguishing between two or more elements or instances. Thus, reference to a first and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.

[0325] In addition, those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, and symbols mentioned in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0326] Those skilled in the art will further recognize that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design codes containing instructions (for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0327] In order to clearly illustrate this interchangeability of hardware, firmware and software, various schematic components, blocks, units, circuits and steps have been generally described above according to their functions. Whether this functionality is implemented as hardware, firmware or software, or a combination of these technologies, depends on the specific application and design limitations implemented on the entire system. Those skilled in the art can implement the described functions in various ways for each specific application, but these implementation decisions will not lead to deviations from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions described herein. The terms "configured to" or "configured for" used herein for specified operations or functions represent processors, devices, components, circuits, structures, machines, units, etc., which are physically constructed, programmed and / or arranged to perform specified operations or functions.

[0328] In addition, those skilled in the art will appreciate that the various exemplary logic blocks, units, devices, components and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0329] Computer-readable media include computer storage media and communication media, which include any media that can transfer a computer program or code from one place to another. Storage media can be any available media that a computer can access. As an example and not limitation, these computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0330] In this document, the term "unit" used refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various units are described as discrete units; however, it is obvious to those of ordinary skill in the art that two or more units can be combined to form a single unit that performs the associated functions according to the embodiments of the present disclosure.

[0331] In addition, embodiments of the present disclosure may employ memory or other storage and communication components. It should be understood that, for the sake of clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it is apparent that any suitable functional distribution between different functional units, processing logic elements or domains may be used without departing from the present disclosure. For example, functions shown as being performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Therefore, reference to specific functional units is merely a reference to suitable devices for providing the functionality described, rather than representing a strict logical or physical structure or organization.

[0332] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art without departing from the scope of this disclosure, and the general principles defined herein may be applied to other implementations. Therefore, this disclosure is not intended to be limited to the implementations shown herein, but should be given the widest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A wireless communication method, comprising: The wireless communication node receives a protocol data unit PDU from a higher layer, wherein the PDU includes identification information; as well as The wireless communication node identifies at least one of: a PDU set of the PDUs or a PDU set timing of the PDU sets; The higher layer includes at least one of the following: general packet radio tunneling protocol user plane GTP-U, next generation user plane interface NG-U, Xn user plane, Xn-U interface, user data from non-access layer NAS or user data of QoS flow.

2. The wireless communication method according to claim 1, wherein the wireless communication node receives a PDU set sequence number of the PDU set, and the PDU set is determined by the PDU set sequence number.

3. The wireless communication method according to claim 1 or 2, wherein the PDU set timing is indicated by the PDU set sequence number.

4. The wireless communication method according to any one of claims 1 to 3, wherein if a PDU set is mapped to multiple QoS flows, the PDU set sequence number is encoded across the multiple QoS flows based on the decoding timing of the quality of service QoS flows.

5. The wireless communication method according to claim 1, wherein the wireless communication node receives at least one of a PDU set start indication of each PDU set, a PDU set end indication of each PDU set, or a total PDU number of the PDU set, and the PDU set is determined by at least one of the PDU set start indication, the PDU set end indication, or the total PDU number of the PDU set.

6. The wireless communication method according to claim 1 or 5, wherein the PDU set timing is determined by a QoS flow identifier (QFI) sequence number of a PDU in the PDU set.

7. The wireless communication method of claim 6, wherein if the PDU set is mapped to multiple QoS flows, the QFI sequence number is encoded across the multiple QoS flows based on the PDU set timing. 8 . The wireless communication method according to claim 1 , wherein the PDU corresponding to each PDU set is included in a Service Data Adaptation Protocol (SDAP) PDU. 9 . The wireless communication method according to claim 8 , wherein the PDUs corresponding to each PDU set are sequentially included in the SDAP PDU based on PDU sequence numbers of the PDUs.

10. The wireless communication method according to any one of claims 1 to 7, wherein the PDU corresponding to each PDU set in one or more SDAPPDUs is included in a Packet Data Convergence Protocol (PDCP) PDU. 11 . The wireless communication method according to claim 10 , wherein the PDUs corresponding to each PDU set are sequentially included in the PDCP PDU.

12. The wireless communication method according to claim 10 or 11, wherein the PDCP PDU includes one or more message authentication code-integrity MAC-I for the one or more SDAP PDUs.

13. The wireless communication method according to any one of claims 1 to 12, wherein the PDU set is indicated in at least one of an SDAP PDU, a PDCP PDU or a radio link control RLC PDU, and the PDU set is indicated by using at least one of a temporary header or a reserved bit.

14. The wireless communication method according to claim 13, wherein the indication of the PDU set in the at least one of the SDAP PDU, the PDCP PDU or the RLC PDU comprises at least one of a PDU set sequence number or a PDU set indication.

15. The wireless communication method according to claim 14, wherein the information indicated by the PDU set includes at least one of the following: an indication indicating that the information of the PDU set is not included, an indication indicating that the corresponding PDU is in a PDU set having a single PDU, an indication indicating that the corresponding PDU is at the starting position of the corresponding PDU set, an indication indicating that the corresponding PDU is at the ending position of the corresponding PDU set, or an indication indicating that the corresponding PDU is at the middle position of the corresponding PDU set. 16 . The wireless communication method according to claim 1 , wherein the SDAP PDU, PDCP PDU or RLC PDU corresponding to the same PDU set are transmitted in one transport block TB, in one TB group or in the same time domain position.

17. A wireless communication method according to any one of claims 1 to 16, wherein a PDU set type indication or a PDU set dependency indication is included in at least one of an SDAP PDU, a PDCP PDU or an RLC PDU, and the information of the PDU set is indicated by using at least one of a temporary header or a reserved bit.

18. The wireless communication method according to claim 17, wherein the PDU set type indication indicates that the corresponding PDU set corresponds to the video compression type of an I frame, a B frame or a P frame, or indicates the corresponding PDU set decoding timing or PDU set decoding dependency, and the PDU set decoding dependency includes at least one of a main frame, an auxiliary frame or an nth auxiliary frame, where n is an integer.

19. The wireless communication method according to claim 17, wherein the PDU set type indication indicates that the corresponding PDU set is independent, dependent on the immediately preceding PDU set, or dependent on the immediately preceding PDU set and the immediately following PDU set.

20. The wireless communication method according to any one of claims 1 to 16, wherein a sequence number SN is included in at least one of a PDCP PDU or an RLC PDU to indicate a PDU set dependency relationship between PDUs.

21. The wireless communication method of claim 20, wherein the SN in at least one of the PDCP PDU or the RLC PDU is encoded on a plurality of data radio bearers (DRBs).

22. A wireless communication method according to any one of claims 1 to 16, wherein the wireless communication node indicates the PDU set dependency of the PDU by including the SN of the associated PDU and the identifier ID of the associated DRB or the associated logical channel in at least one of the PDCP PDU or the RLC PDU.

23. A wireless communication method according to any one of claims 1 to 16, wherein the wireless communication node indicates a PDU set sequence number in at least one of a PDCP PDU or an RLC PDU, and the PDU set sequence number is encoded on multiple DRBs or multiple logical channels based on the PDU set sequence number in a PDCP service data unit SDU.

24. A wireless communication method, comprising: The wireless communication node sends a reflective quality of service QoS indication or an active QoS update request to the core network CN or the wireless communication terminal; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

25. The wireless communication method according to claim 24, wherein the recommended QoS auxiliary information includes at least one of the following parameter types: recommended QoS parameter values, recommended QoS flow priorities, recommended mappings between application data and QoS flows, recommended paging strategies, user equipment UE mobility information, artificial intelligence related information, machine learning related information, network usage perception, network computing capabilities, or UE positioning related information.

26. The wireless communication method according to claim 24 or 25, wherein the recommended QoS assistance information sent to the CN includes at least one of the following parameters: an aggregate maximum bit rate per cell preferred or allowed by the wireless communication node; The maximum bit rate of each QoS flow carried by the wireless communication node is preferred or allowed; an aggregate maximum bit rate per protocol data unit (PDU) session preferred or allowed by the wireless communication node; a downlink DL PDU transmission time offset, used to indicate that the CN transmits the PDU of the QoS flow or PDU session with a time delay offset or a time advance offset, wherein the DL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time or a current transmission timing opportunity; DL PDU arrival time, used to indicate that the CN transmits a PDU of a QoS flow or a PDU session to ensure that the PDU arrives at the wireless communication node based on the DL PDU arrival time; the maximum data packet size preferred or supported by the wireless communication node; The wireless communication node preferably applies an encoded data rate; A CN data packet delay budget PDB detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing; A CN data packet delay budget margin detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing; A bit error rate BER detected by the wireless communication node; A packet error rate PER detected by the wireless communication node; Network node load information; The network node's own computing power margin; Requests for excess computing capacity in the core network or cloud native; Uu time synchronization error budget; Uu packet delay budget; Uu packet delay budget margin; The duration of the service preferably used for the wireless communication node to determine a DL data transmission opportunity; or The start time of the preferably triggered service is used by the wireless communication node to determine the DL data transmission timing.

27. The wireless communication method according to any one of claims 24 to 26, wherein the recommended QoS assistance information sent to the wireless communication terminal comprises at least one of the following parameters: an aggregate maximum bit rate per UE preferred or allowed by the wireless communication node; an aggregate maximum bit rate per DRB preferred or allowed by the wireless communication node; an aggregate maximum bit rate per logical channel preferred or allowed by the wireless communication node; an aggregate maximum bit rate per logical channel group preferred or allowed by the wireless communication node; The wireless communication node preferably applies an encoded data rate; an uplink UL PDU transmission time offset, used to instruct the wireless communication terminal to transmit a PDU of a DRB or a logical channel with a time delay offset or a time advance offset, wherein the UL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity; UL PDU transmission time, used to instruct the wireless communication terminal to transmit the PDU of the DRB or logical channel to ensure that the PDU is transmitted based on the indicated transmission time; The BER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power; The PER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power; Network node load information; The network node's own computing power margin; Requests for excess computing capacity in the core network or cloud native; Uu time synchronization error budget; Uu packet delay budget; Uu packet delay budget margin; The duration of the preferably used service is used by the wireless communication terminal to determine the UL data transmission timing; or The start time of the preferably triggered service is used by the wireless communication terminal to determine the UL service start time or UL data transmission timing.

28. A wireless communication method, comprising: The wireless communication node receives a buffer size indication from a wireless communication terminal.

29. The wireless communication method of claim 28, wherein the buffer size indication comprises at least one of: A specific buffer status report (BSR) format indicating that the buffer size is the same as the most recently reported buffer size; a specific BSR medium access control MAC header with a new logical channel LC identifier ID indicating a buffer size that is the same as the buffer size most recently reported by the logical channel, logical channel group or data radio bearer DRB; A specific BSR Medium Access Control MAC header with a new logical channel LC identifier ID indicating a buffer size that is the same as the transmission size of the most recent transmission of the logical channel, logical channel group or DRB; or Uplink control information indicating that the buffer size is the same as the transmission size of the most recent transmission of the logical channel, logical channel group, or DRB.

30. A wireless communication method, comprising: The wireless communication node sends a discontinuous reception C-DRX configuration in an RRC connected state to the wireless communication terminal; as well as According to the C-DRX configuration, the wireless communication node communicates with the wireless communication terminal with multiple C-DRX modes for each cell group, each data radio bearer DRB or each logical channel. 31 . The wireless communication method according to claim 30 , wherein each C-DRX configuration comprises a C-DRX index or a C-DRX identity for indicating the C-DRX configuration.

32. The wireless communication method according to claim 30, wherein the C-DRX index or the C-DRX identity of each C-DRX configuration is represented by the order of the C-DRX configuration in the sequence.

33. A wireless communication method according to any one of claims 30 to 32, wherein the wireless communication node sends a request with a C-DRX index or a C-DRX identity to the wireless communication terminal to modify, remove, activate or deactivate one of the C-DRX configurations corresponding to the C-DRX index or the C-DRX identity.

34. A wireless communication method, comprising: The wireless communication node receives a buffer status report BSR of an uplink UL response protocol data unit PDU corresponding to a downlink DLPDU from a wireless communication terminal.

35. The wireless communication method of claim 34, wherein the BSR comprises at least one of: A DL logical channel LC identifier ID or a DL LC priority, associated with the UL response PDU; a DL PDU response indication associated with the UL response PDU; or The related DL PDU information includes at least one of a PDU sequence number SN or PDU time domain information.

36. The wireless communication method according to claim 34 or 35, wherein the PDU time domain information comprises at least one of system frame number information, time slot information or symbol information.

37. A wireless communication method, comprising: The wireless communication node receives a first PDU corresponding to a second protocol data unit PDU of a second wireless communication terminal from the first wireless communication terminal.

38. The wireless communication method of claim 37, wherein the first PDU comprises at least one of: an identifier ID of the second wireless communication terminal; information of the second PDU; Quality of service QoS, flow ID, logical channel LCID or LC priority associated with the first PDU; or A PDU response indication associated with the first PDU.

39. The wireless communication method according to claim 37 or 38, wherein the information of the second PDU includes at least one of system frame number information, time slot information or symbol information.

40. A wireless communication method, comprising: A node in the core network CN receives a reflective quality of service QoS indication or an active QoS update request from a wireless communication node; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

41. The wireless communication method according to claim 40, wherein the recommended QoS auxiliary information includes at least one of the following parameter types: recommended QoS parameter values, recommended QoS flow priorities, recommended mappings between application data and QoS flows, recommended paging strategies, user equipment UE mobility information, artificial intelligence related information, machine learning related information, network usage perception, network computing capabilities, or UE positioning related information.

42. The wireless communication method according to claim 40 or 41, wherein the recommended QoS assistance information sent to the CN includes at least one of the following parameters: an aggregate maximum bit rate per cell preferred or allowed by the wireless communication node; The maximum bit rate of each QoS flow carried by the wireless communication node is preferred or allowed; an aggregate maximum bit rate per protocol data unit (PDU) session preferred or allowed by the wireless communication node; a downlink DL PDU transmission time offset, used to indicate that the CN transmits the PDU of the QoS flow or PDU session with a time delay offset or a time advance offset, wherein the DL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time or a current transmission timing opportunity; DL PDU arrival time, used to indicate that the CN transmits a PDU of a QoS flow or a PDU session to ensure that the PDU arrives at the wireless communication node based on the DL PDU arrival time; the maximum data packet size preferred or supported by the wireless communication node; The wireless communication node preferably applies an encoded data rate; A CN data packet delay budget PDB detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing; A CN data packet delay budget margin detected by the wireless communication node, used by the wireless communication node to determine a DL data transmission timing; A bit error rate BER detected by the wireless communication node; A packet error rate PER detected by the wireless communication node; Network node load information; The network node's own computing power margin; Requests for excess computing capacity in the core network or cloud native; Uu time synchronization error budget; Uu packet delay budget; Uu packet delay budget margin; The duration of the service preferably used for the wireless communication node to determine a DL data transmission opportunity; or The start time of the preferably triggered service is used by the wireless communication node to determine the DL data transmission timing.

43. A wireless communication method, comprising: The wireless communication terminal receives a reflective quality of service (QoS) indication or an active QoS update request from the wireless communication node; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

44. According to the wireless communication method according to claim 43, the recommended QoS auxiliary information includes at least one of the following parameter types: recommended QoS parameter value, recommended QoS flow priority, recommended mapping between application data and QoS flow, recommended paging strategy, user equipment UE mobility information, artificial intelligence related information, machine learning related information, network usage perception, network computing capability or UE positioning related information.

45. The wireless communication method according to claim 43 or 44, wherein the recommended QoS assistance information sent to the wireless communication terminal includes at least one of the following parameters: an aggregate maximum bit rate per UE preferred or allowed by the wireless communication node; an aggregate maximum bit rate per DRB preferred or allowed by the wireless communication node; an aggregate maximum bit rate per logical channel preferred or allowed by the wireless communication node; an aggregate maximum bit rate per logical channel group preferred or allowed by the wireless communication node; The wireless communication node preferably applies an encoded data rate; an uplink UL PDU transmission time offset, used to instruct the wireless communication terminal to transmit a PDU of a DRB or a logical channel with a time delay offset or a time advance offset, wherein the UL PDU transmission time offset is related to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity; UL PDU transmission time, used to instruct the wireless communication terminal to transmit the PDU of the DRB or logical channel to ensure that the PDU is transmitted based on the indicated transmission time; The BER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power; The PER detected by the wireless communication node is used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power; Network node load information; The network node’s own computing power margin; Requests for excess computing capacity in the core network or cloud native; Uu time synchronization error budget; Uu packet delay budget; Uu packet delay budget margin; The duration of the preferably used service is used by the wireless communication terminal to determine the UL data transmission timing; or The start time of the preferably triggered service is used by the wireless communication terminal to determine the UL service start time or UL data transmission timing.

46. ​​A wireless communication method, comprising: The wireless communication terminal sends a buffer size indication to the wireless communication node.

47. The wireless communication method of claim 46, wherein the buffer size indication comprises at least one of: A specific buffer status report (BSR) format indicating that the buffer size is the same as the most recently reported buffer size; a specific BSR medium access control MAC header with a new logical channel LC identifier ID indicating a buffer size that is the same as the buffer size most recently reported by the logical channel, logical channel group or data radio bearer DRB; A specific BSR Medium Access Control MAC header with a new logical channel LC identifier ID indicating a buffer size that is the same as the transmission size of the most recent transmission of the logical channel, logical channel group or DRB; or Uplink control information indicating that the buffer size is the same as the transmission size of the most recent transmission of the logical channel, logical channel group, or DRB.

48. A wireless communication method, comprising: The wireless communication terminal receives a discontinuous reception C-DRX configuration in an RRC connected state from the wireless communication node; as well as According to the C-DRX configuration, the wireless communication node communicates with the wireless communication terminal in a plurality of C-DRX modes for each cell group, each data radio bearer DRB or each logical channel.

49. The wireless communication method according to claim 48, wherein each C-DRX configuration comprises a C-DRX index or a C-DRX identity for identifying the C-DRX configuration.

50. The wireless communication method according to claim 48, wherein the C-DRX index or the C-DRX identity of each C-DRX configuration is represented by the order of the C-DRX configuration in the sequence.

51. A wireless communication method according to any one of claims 48 to 50, wherein the wireless communication node sends a request with a C-DRX index or a C-DRX identity to the wireless communication terminal to modify, remove, activate or deactivate one of the C-DRX configurations corresponding to the C-DRX index or the C-DRX identity.

52. A wireless communication method, comprising: The wireless communication terminal sends a buffer status report BSP of an uplink UL response protocol data unit PDU corresponding to the downlink DLPDU to the wireless communication node.

53. The wireless communication method of claim 52, wherein the BSR comprises at least one of: A DL logical channel LC identifier ID or a DL LC priority, associated with the UL response PDU; a DL PDU response indication associated with the UL response PDU; or The related DL PDU information includes at least one of a PDU sequence number SN or PDU time domain information.

54. The wireless communication method according to claim 52 or 53, wherein the PDU time domain information includes at least one of system frame number information, time slot information or symbol information.

55. A wireless communication method, comprising: The first wireless communication terminal sends a first PDU corresponding to a second protocol data unit PDU of the second wireless communication terminal to the wireless communication node.

56. The wireless communication method of claim 55, wherein the first PDU comprises at least one of: an identifier ID of the second wireless communication terminal; information of the second PDU; Quality of Service QoS flow ID, logical channel LCID or LC priority, associated with the first PDU; or A PDU response indication associated with the first PDU.

57. The wireless communication method according to claim 55 or 56, wherein the information of the second PDU includes at least one of system frame number information, time slot information or symbol information.

58. A wireless communication node, comprising: Communication unit; and The processor is configured to: receive a protocol data unit PDU from a higher layer, wherein the PDU includes PDU set information; and identifying a PDU set of the PDUs and a PDU set timing of the PDU sets; wherein the PDU is scheduled for transmission over the Uu interface according to at least one of the PDU set or the PDU set timing; The higher layer includes at least one of the following: general packet radio tunneling protocol user plane GTP-U, next generation user plane interface NG-U, Xn user plane, Xn-U interface, user data from non-access layer NAS or user data of QoS flow.

59. The wireless communication node according to claim 58, wherein the processor is further configured to perform the wireless communication method according to any one of claims 2 to 23.

60. A wireless communication node, comprising: Communication unit; and The processor is configured to: send a reflective quality of service QoS indication or an active QoS update request to a core network CN or a wireless communication terminal; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

61. The wireless communication node of claim 60, wherein the processor is further configured to perform the wireless communication method of any one of claims 25 to 27.

62. A wireless communication node, comprising: Communication unit; and The processor is configured to receive a buffer size indication from a wireless communication terminal.

63. The wireless communication node according to claim 62, wherein the processor is further configured to execute the wireless communication method according to 29.

64. A wireless communication node, comprising: Communication unit; and The processor is configured to: send a discontinuous reception C-DRX configuration in an RRC connected state to a wireless communication terminal; And according to the C-DRX configuration, communicate with the wireless communication terminal in multiple C-DRX modes for each cell group, each data radio bearer DRB or each logical channel.

65. The wireless communication node of claim 64, wherein the processor is further configured to perform the wireless communication method of any one of claims 31 to 33.

66. A wireless communication node, comprising: Communication unit; and The processor is configured to receive a buffer status report BSP of an uplink UL response protocol data unit PDU corresponding to a downlink DLPDU from a wireless communication terminal.

67. The wireless communication node of claim 46, wherein the processor is further configured to perform the wireless communication method of claim 35 or 36.

68. A wireless communication node, comprising: Communication unit; and The processor is configured to receive, from the first wireless communication terminal, a first PDU corresponding to a second protocol data unit PDU of the second wireless communication terminal.

69. The wireless communication node of claim 68, wherein the processor is further configured to perform the wireless communication method of any one of claims 38 to 39.

70. A communication node, comprising: Communication unit; and A processor configured to: receive a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

71. The communication node of claim 70, wherein the processor is further configured to perform the wireless communication method of any one of claims 41 to 42.

72. A wireless communication terminal, comprising: Communication unit; and A processor configured to: receive a reflective quality of service (QoS) indication or an active QoS update request from a wireless communication node; The reflected QoS indication or the active QoS update request includes one or more sets of recommended QoS auxiliary information.

73. The wireless communication terminal according to claim 72, wherein the processor is further configured to execute the wireless communication method according to any one of claims 44 to 45.

74. A wireless communication terminal, comprising: Communication unit; and A processor is configured to send a buffer size indication to a wireless communication node.

75. The wireless communication terminal according to claim 74, wherein the processor is further configured to execute the wireless communication method according to claim 47.

76. A wireless communication terminal, comprising: Communication unit; and The processor is configured to receive a discontinuous reception C-DRX configuration in an RRC connected state from a wireless communication node; And according to the C-DRX configuration, communicate with the wireless communication terminal in multiple C-DRX modes for each cell group, each data radio bearer DRB or each logical channel.

77. The wireless communication terminal according to claim 76, wherein the processor is further configured to execute the wireless communication method according to any one of claims 49 to 51.

78. A wireless communication terminal, comprising: Communication unit; and The processor is configured to send a buffer status report BSP of an uplink UL response protocol data unit PDU corresponding to a downlink DLPDU to a wireless communication node.

79. The wireless communication terminal according to claim 78, wherein the processor is further configured to execute the wireless communication method according to any one of claims 53 to 54.

80. A wireless communication terminal, comprising: Communication unit; and The processor is configured to send a first PDU corresponding to a second protocol data unit PDU of a second wireless communication terminal to the wireless communication node.

81. The wireless communication terminal according to claim 42, wherein the processor is further configured to execute the wireless communication method according to any one of claims 56 to 57.

82. A computer program product having a computer-readable program medium code stored therein, wherein when the code is executed by a processor, the processor implements the wireless communication method according to any one of claims 1 to 39.

Citation Information

Cited By

  • Data processing method, communication system, storage medium, electronic apparatus and computer program product

    WO2026144412A1