Wireless communication method, wireless communication terminal, wireless communication node, computer program, computer-readable program medium

Abstract

A method, device, and computer program product for wireless communication are provided. The method includes receiving, by a wireless communication node, a protocol data unit (PDU) including identification information from an upper layer, and identifying, by the wireless communication node, a PDU set of the PDU and a PDU set time sequence of the PDU set, wherein the PDU is scheduled for transmission via a Uu interface according to at least one of the PDU set or the PDU set time sequence, and the upper 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 (Xn-U) interface, user data from a non-access stratum (NAS), and user data of a QoS flow.

Description

Technical Field

[0001] This document generally relates to wireless communication, particularly 5th generation (5G) wireless communication.

Background Art

[0002] XR (Extended Reality) services are typically video streaming and are represented by multiple application data units. Each application data unit is composed of multiple application frames, such as I-frames, P-frames, and B-frames. These application frames are mutually dependent and may have a specific order for transmission, decoding, or presentation.

Summary of the Invention

[0003] This disclosure relates to a method, device, and computer program product for identifying a PDU set and a PDU set time sequence in wireless communication.

Means for Solving the Problems

[0004] One aspect of this disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes receiving, by a wireless communication node, from an upper layer, a protocol data unit (PDU) including identification information, and identifying, by the wireless communication node, a PDU set of the PDU and / or a PDU set time sequence of the PDU set, where the PDU is scheduled for transmission via a Uu interface according to at least one of the PDU set or the PDU set time sequence, and the upper 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 (Xn-U) interface, user data from a Non-Access Stratum (NAS), and user data of a QoS flow.

[0005] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes transmitting, by a wireless communication node, a reflective quality of service (QoS) indication or a proactive 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. The reflective QoS indication or the proactive QoS update request includes a set of one or more suggested QoS support information. Based on the set of one or more suggested QoS support information, the core network or the wireless communication terminal can determine, select, accept, reject, or recommend QoS information.

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

[0007] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes transmitting, by a wireless communication node, an intermittent reception (C-DRX) configuration in the RRC_Connected state to a wireless communication terminal, and performing communication with the wireless communication terminal using a plurality of C-DRX patterns for each cell group, for each data radio bearer, for each DRB, or for each logical channel according to the C-DRX configuration.

[0008] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes receiving, by a wireless communication node, a buffer status report (BSR) for 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. SomeIn an embodiment, the wireless communication method includes receiving, by a wireless communication node, 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. Some In an embodiment, the wireless communication method includes receiving, by a node in a core network (CN), a reflect-type quality of service (QoS) indication or a proactive QoS update request from a wireless communication node according to at least one of network capabilities or network preferences to trigger an update of QoS parameters, the reflect-type QoS indication or the proactive QoS update request includes a set of one or more indicated QoS support information, and based on the set of one or more indicated QoS support information, the core network can determine, select, accept, reject, or recommend QoS information.

[0011] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes receiving, by a wireless communication node, a reflect-type quality of service (QoS) indication or a proactive QoS update request from a wireless communication terminal according to at least one of network capabilities or network preferences to trigger an update of QoS parameters, the reflect-type QoS indication or the proactive QoS update request includes a set of one or more indicated QoS support information, and based on the set of one or more indicated QoS support information, Wireless communication terminal it becomes possible to determine, select, accept, reject, or recommend QoS information.

[0012] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes transmitting, by a wireless communication terminal, a buffer size indication to a wireless communication node.

[0013] Another aspect of the present disclosure relates to a wireless communication method. SomeIn an embodiment, the wireless communication method includes receiving, by a wireless communication terminal, a discontinuous reception (C-DRX) configuration from a wireless communication node during an RRC_Connected state, and performing communication using a plurality of C-DRX patterns for each cell group, for each data radio bearer, for each DRB, or for each logical channel according to the C-DRX configuration, between the wireless communication Node and the wireless communication Terminal by the wireless communication.

[0014] Another aspect of the present disclosure relates to a wireless communication method. Some In an embodiment, the wireless communication method includes transmitting, by a wireless communication terminal, a buffer status report (BSR) for 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. Some In an embodiment, the wireless communication method includes transmitting, by a first wireless communication terminal, 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. Some In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to receive, from an upper layer, a protocol data unit (PDU) including PDU set information, and to identify a PDU set of the PDU and / or a PDU set time sequence of the PDU set. The PDU is scheduled for transmission via the Uu interface according to at least one of the PDU set or the PDU set time sequence. The upper 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 (Xn-U) interface, user data from a non-access stratum (NAS), and user data of a QoS flow.

[0017] Another aspect of the present disclosure relates to a wireless communication node. Some In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit a reflect-type Quality of Service (QoS) indication or a proactive 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 an update of QoS parameters. The reflect-type QoS indication or the proactive QoS update request includes a set of one or more suggested QoS support information. Based on the set of one or more suggested QoS support information, the core network or the wireless communication terminal can determine, select, accept, reject, or recommend QoS information.

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

[0019] Another aspect of the present disclosure relates to a wireless communication node. Some In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit an intermittent reception (C-DRX) configuration in the RRC_Connected state to the wireless communication terminal, and to perform communication with the wireless communication terminal using multiple C-DRX patterns for each cell group, each data radio bearer, each DRB, or each logical channel according to the C-DRX configuration.

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

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

[0022] Another aspect of the present disclosure relates to a wireless communication node. Some In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to receive, from the wireless communication node, a reflected quality of service (QoS) indication, or a proactive QoS update request, in accordance with at least one of network capabilities or network preferences, to trigger an update of QoS parameters. The reflected QoS indication or the proactive QoS update request includes a set of one or more indicated QoS support information. Based on the set of one or more indicated QoS support information, the core network can determine, select, accept, reject, or recommend QoS information.

[0023] Another aspect of the present disclosure relates to a communication node (e.g., a communication node within a core network). Some In an embodiment, the communication node includes a communication unit and a processor. The processor is configured to receive, from the wireless communication node, a reflected quality of service (QoS) indication, or a proactive QoS update request, in accordance with at least one of network capabilities or network preferences, to trigger an update of QoS parameters. The reflected QoS indication or the proactive QoS update request includes a set of one or more indicated QoS support information. Based on the set of one or more indicated QoS support information, the core network can determine, select, accept, reject, or recommend QoS information.

[0024] Other aspects of the present disclosure relate to a wireless communication terminal. SomeIn an embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to receive, from a wireless communication node, a reflective Quality of Service (QoS) indication or a proactive QoS update request according to at least one of network capabilities or network preferences to trigger an update of QoS parameters. The reflective QoS indication or the proactive QoS update request includes a set of one or more suggested QoS support information, and based on the set of one or more suggested QoS support information, Wireless communication terminal it becomes possible to determine, select, accept, reject, or recommend QoS information.

[0025] Other aspects of the present disclosure relate to a wireless communication terminal. Some In an embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to transmit a buffer size indication to the wireless communication node.

[0026] Other aspects of the present disclosure relate to a wireless communication terminal. Some In an embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to receive, from the wireless communication node, an intermittent reception (C-DRX) configuration in the RRC_Connected state, and according to the C-DRX configuration, perform communication using a plurality of C-DRX patterns for each cell group, for each data radio bearer, for each DRB, or for each logical channel, with the wireless communication Node configured to execute between.

[0027] Other aspects of the present disclosure relate to a wireless communication terminal. Some In an embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to transmit a buffer status report (BSR) for an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU to the wireless communication node.

[0028] Other aspects of the present disclosure relate to a wireless communication terminal. SomeIn an embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to transmit a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal to a wireless communication node.

[0029] -fold Various embodiments can implement the following features. In some embodiments It can be implemented.

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

[0031] In some embodiments The PDU set time sequence is indicated by the PDU set sequence number.

[0032] In some embodiments The PDU set is mapped to different quality of service (QoS) flows, and the PDU set sequence number is encoded across multiple QoS flows based on the decoding time sequence of the QoS flows.

[0033] In some embodiments The wireless communication node receives at least one of a PDU set start indication and 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] In some embodiments The PDU set time sequence is determined by the QoS flow identifier (QFI) and the sequence number of the PDUs within the PDU set.

[0035] In some embodiments The PDU set is mapped to different QoS flows, and the QFI sequence number is encoded across multiple QoS flows based on the PDU set time sequence.

[0036] In some embodiments, The wireless communication node includes PDUs corresponding to each set of PDUs within a Service Data Adaptation Protocol (SDAP) PDU.

[0037] In some embodiments , The PDUs corresponding to each set of PDUs are sequentially included in the SDAP PDU based on the PDU sequence number of the PDUs.

[0038] In some embodiments , The wireless communication node includes PDUs corresponding to each set of PDUs within one or more SDAP PDUs, and the one or more SDAP PDUs are included in Packet Data Convergence Protocol (PDCP) PDUs.

[0039] In some embodiments , The PDUs corresponding to each set of PDUs are sequentially included in the PDCP PDU.

[0040] In some embodiments , The PDCP PDU includes one or more Message Authentication Code - Integrity (MAC-I) for one or more SDAP PDUs.

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

[0042] In some embodiments , The information of the PDU set includes at least one of a PDU set sequence number or a PDU set indication.

[0043] In some embodimentsThe information of the PDU set indication includes at least one of an indication indicating that the corresponding PDU is within a PDU set having a single PDU, an indication indicating that the corresponding PDU is at the start position of the corresponding PDU set, an indication indicating that the corresponding PDU is at the end position of the corresponding PDU set, or an indication indicating that the corresponding PDU is at an intermediate position of the corresponding PDU set.

[0044] In some embodiments The wireless communication node transmits an SDAP PDU, a PDCP PDU, or an RLC PDU corresponding to the same PDU set within one transport block (TB) in one TB group or at the same time domain position.

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

[0046] In some embodiments The PDU set type indication indicates that the corresponding PDU set corresponds to a video compression type of an I-frame, a B-frame, or a P-frame, or indicates a corresponding PDU set decoding time sequence or a PDU set decoding dependency such as a primary frame, a secondary frame, an nth secondary frame, where n is an integer.

[0047] In some embodiments The PDU set Dependency indication indicates that the corresponding PDU set is individual, depends on the previous PDU set, or depends on the previous PDU set and the next PDU set.

[0048] In some embodiments The wireless communication node indicates the PDU set dependency between PDUs by including a sequence number (SN) in at least one of the PDCP PDU or the RLC PDU.

[0049] In some embodiments At least one SN of the PDCP PDU or the RLC PDU is encoded across a plurality of data radio bearers (DRBs).

[0050] In some embodiments The radio 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.

[0051] In some embodiments The radio communication node indicates the PDU set sequence number in at least one of the PDCP PDU or the RLC PDU, and the PDU set sequence number is encoded across a plurality of DRBs or a plurality of logical channels based on the PDU set sequence number in the PDCP service data unit (SDU).

[0052] In some embodiments The suggested QoS support information includes at least one of the following parameter types, namely, the suggested QoS parameter value, the priority level of the suggested QoS flow, the suggested mapping between the application data and the QoS flow, the suggested paging strategy, the user equipment (UE), the mobility information, the artificial intelligence related information, the machine learning related information, the network usage awareness, the network computing ability, or the UE positioning related information.

[0053] In some embodiments At least one SN of the PDCP PDU or the RLC PDU is encoded across a plurality of data radio bearers (DRBs).

[0054] In some embodiments The radio 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.

[0055] In some embodiments The radio communication node indicates the PDU set sequence number in at least one of the PDCP PDU or the RLC PDU, and the PDU set sequence number is encoded across a plurality of DRBs or a plurality of logical channels based on the PDU set sequence number within the PDCP service data unit (SDU).

[0056] In some embodiments The suggested QoS support information sent to the CN includes at least one of the following parameters, namely, The maximum aggregate bit rate per cell that the radio communication node prefers or permits, The maximum bit rate per QoS flow to be carried that the radio communication node prefers or permits, The maximum aggregate bit rate per protocol data unit (PDU) session that the radio communication node prefers or permits, The downlink (DL) PDU transmission time offset used to indicate to the CN to transmit a PDU session having a PDU of the QoS flow or a time delay offset or a time advance offset, where the DL PDU transmission time offset is relative to at least one of the current transmission start time, the current transmission end time, or the current transmission timing opportunity, the DL PDU transmission time offset The DL PDU arrival time, the DL PDU arrival time used to instruct the CN to transmit the PDU of the QoS flow or the PDU session so as to ensure that the PDU arrives at the radio communication node based on the DL PDU arrival time The maximum packet size that the radio communication node prefers or supports, The application encoding data rate that the radio communication node prefers, The CN packet delay budget (PDB) detected by the radio communication node and used by the radio communication node to determine the DL data transmission opportunity The CN packet delay budget headroom used by a wireless communication node to detect and determine a DL data transmission opportunity The bit error rate (BER) detected by the wireless communication node The packet error rate (PER) detected by the wireless communication node Network node load information The network node self - computing capacity headroom The computing capacity headroom requirement for the core network or cloud native The Uu time synchronization error budget The Uu packet delay budget The Uu packet delay budget headroom The duration that a service is preferred and used by the wireless communication node to determine a DL data transmission opportunity, or The start time that a service is preferred and triggered by the wireless communication node to determine a DL data transmission opportunity

[0057] In some embodiments The suggested QoS support information sent to the wireless communication terminal includes at least one of the following parameters, namely The maximum aggregated bitrate per UE preferred or permitted by the wireless communication node The maximum aggregated bitrate per DRB preferred or permitted by the wireless communication node The maximum aggregated bitrate per logical channel preferred or permitted by the wireless communication node The maximum aggregated bitrate per logical channel group preferred or permitted by the wireless communication node The application - encoded data rate preferred by the wireless communication node An uplink (UL) PDU transmission time offset used to indicate to a wireless communication terminal to transmit a PDU of a DRB or a logical channel using a time delay offset or a time advance offset, where the UL PDU transmission time offset is relative to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity. The UL PDU transmission time used to indicate to a wireless communication terminal to transmit a PDU of a DRB or a logical channel in order to guarantee that the PDU is transmitted based on the indicated transmission time. The BER that a wireless communication node detects and that a wireless communication terminal uses to adjust at least one of a coding rate or a transmission power. The PER that a wireless communication node detects and that a wireless communication terminal uses to adjust at least one of a coding rate or a transmission power. Network node load information. Network node self - computing capacity headroom. Computing capacity headroom requirements for a core network or cloud native. Uu time synchronization error budget. Uu packet delay budget. Uu packet delay budget headroom. The duration that a service is preferably used and that is used by a wireless communication terminal to determine a UL data transmission opportunity, or, The start time that a service is preferably triggered and that is used by a wireless communication terminal to determine a UL service start time or a UL data transmission opportunity.

[0058] In some embodiments The buffer size indication includes at least one of the following, that is, A specific buffer status report (BSR) format indicating that the buffer size is the same as the latest reported buffer size. A specific BSR Medium Access Control (MAC) header with a new logical channel (LC) identifier (ID) indicating that the buffer size is the same as the latest reported buffer size for a logical channel, logical channel group, or Data Radio Bearer (DRB). A specific BSR MAC header with a new LC ID indicating that the buffer size is the same as the latest transport size sent for a logical channel, logical channel group, or DRB, or UL control information indicating that the buffer size is the same as the latest transport Block size sent for a logical channel, logical channel group, or DRB.

[0059] In some embodiments Each C-DRX configuration includes a C-DRX index or C-DRX identification information used to identify the C-DRX configuration.

[0060] In some embodiments The C-DRX index or C-DRX identification information of each C-DRX configuration is indicated by the order of the C-DRX configurations within the sequence.

[0061] In some embodiments The wireless communication node sends a request to the wireless communication terminal having the C-DRX index or C-DRX identification information to modify, remove, activate, or deactivate one of the C-DRX configurations corresponding to the C-DRX index or C-DRX identification information.

[0062] In some embodiments The BSR includes a DL logical channel (LC), identifier (ID), or DL LC priority related to the UL response PDU, a DL PDU response indication related to the UL response PDU, or at least one piece of related DL PDU information including at least one of a PDU sequence number (SN) or PDU time domain information.

[0063] In some embodiments The PDU time domain information includes at least one of system frame number information, slot information, or symbol information.

[0064] In some embodiments The first PDU identifies the second wireless communication terminal (ID), information on the second PDU, quality of service (QoS) for the first PDU, flow ID, logical channel (LC), ID, or LC priority for the first PDU, or a PDU response indication related to the first PDU, and includes at least one of them.

[0065] The exemplary embodiments disclosed herein are directed to providing features that will be readily apparent by reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those skilled in the art reading this disclosure that various modifications to the disclosed embodiments can be made within the scope of this disclosure.

[0066] Accordingly, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Further, the particular order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the particular order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Accordingly, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in exemplary orders, and this disclosure is not limited to the particular order or hierarchy presented unless otherwise specified.

[0067] The foregoing and other aspects and embodiments thereof are described in more detail in the drawings, the description, and the claims.

Brief Description of the Drawings

[0068]

Figure 1

Figure 2a

Figure 2b

Figure 3

Figure 4

Figure 5a

Figure 5b

Figure 5c

Figure 5d

Figure 6a

Figure 6b

Figure 6c

Figure 7a

Figure 7b

Figure 7c

Figure 7d

Figure 7e

Figure 7f

Figure 7g

Figure 7h

Figure 8a

Figure 8b

Figure 8c

Figure 8d

Figure 8e

Figure 8f

Figure 8g

Figure 8h

Figure 9a

Figure 9b

Figure 10a

Figure 10b

Figure 10c

Figure 10d

Figure 11

Figure 12

Best Mode for Carrying Out the Invention

[0069] In some embodiments, as illustrated in FIG. 1, one application frame (e.g., an application data unit (ADU)) can include a plurality of IP (Internet Protocol) packets that can be represented by a set of PDUs (protocol data units) in a QoS (Quality of Service) flow. For example, a series of packets can include all the information necessary to reconstruct a video frame (e.g., corresponding to a “media unit” or “slice”), such as video, audio, frames, tiles, and / or tactile information. The packets can be, for example, packets of 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, user data from the NAS (Non-Access Stratum).

[0070] Since different application frames have different (non)-encoding methods, the QoS priority or importance of the frames is different. For example, FIG. 2a shows the decoding time sequence and presentation time sequence of the ADU in FIG. 1.

[0071] In some embodiments, an I-frame is a key frame that stores / transmits all the data necessary to indicate that frame. In some embodiments, I-frames are scattered with P-frames and B-frames in the compressed video. The more I-frames included, the better the video quality. However, I-frames require more bits, more space in the storage medium, and consume more radio resources for distribution.

[0072] In some embodiments, the P-frame is a delta frame, which contains data that has changed from the preceding I-frame (such as a change in color or content). Thus, the P-frame depends on the preceding I-frame to fill in the relevant data.

[0073] In some embodiments, the B-frame is also a delta frame, which contains data that has changed from the preceding frame and is different from the data in the next frame. Thus, the B-frame depends on the frames before and after it to fill in the relevant data.

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

[0075] In some embodiments, the QoS priority or importance level is indicated by the priority within the QoS flow. Since there is only one priority level for each QoS flow, 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. Thus, it remains unclear how to represent the PDU decoding time sequence within one application data unit.

[0076] Furthermore, after all PDUs within a PDU set are received, the decoding side can decode the application frame. Thereafter, as shown in Figure 2b, PDU transmission is scheduled at the RLC (Radio Link Control) and / or MAC (Medium Access Control) layer based on the user plane protocol stack, and the PDUs corresponding to one PDU set are included in one SDAP (Service Data Adaptation Protocol) PDU and / or PDCP (Packet Data Convergence Protocol) PDU, or the transmission entity of the RLC and / or MAC layer recognizes the PDU set for radio resource scheduling (e.g., recognizes that the PDUs belong to the same PDU set) and ensures that all PDUs within one PDU set can arrive at the receiving side simultaneously.

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

[0078] In some embodiments, the gNB can receive a PDU containing identification information from the upper layer, and the upper layer includes at least one of General Packet Radio Service - Tunneling Protocol - User Plane (GTP - U), Next Generation User Plane Interface (NG - U), Xn User Plane (Xn - U) interface, user data from the Non - Access Stratum (NAS), and user data of a QoS flow. The gNB can identify the PDU set of the PDU and the PDU set time sequence of the PDU set. For example, the gNB can identify the PDU set Or PDU set time sequence At least one of according to the identification information. Thereafter, the gNB Or PDU set time sequence At least one ofAccording to this, the PDU can be scheduled for transmission via the Uu interface. The identification information includes at least one of the PDU set sequence number and / or the PDU set information. The PDU set information includes at least one of the PDU set start indication and / or the PDU set end indication. Some In an 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.

[0079] Embodiment 1 (Mapping between PDU set and QoS flow) FIG. 3 shows the mapping between the GTP-U, NG-U, Xn-U, or NAS-U (Non-Access Stratum User Plane Data) PDU set and the QoS flow, and the PDU set time sequence is indicated by the PDU set sequence number.

[0080] Some In an embodiment, the PDU set is identified by the PDU set sequence number, and the PDU set time sequence is indicated by the PDU set sequence number. The PDU set sequence number is encoded / numbered across multiple QoS flows for each PDU session or traffic flow used to indicate the application frame sequence and / or the application data unit sequence.

[0081] Some In an embodiment, the PDU set time sequence can be a PDU set decoding time sequence (for example, the next PDU set can be decoded only when the current PDU set is successfully decoded) or a PDU set presentation time sequence (for example, in the case of video streaming, image frames are presented one by one according to the presentation time sequence).

[0082] Since the PDU set is decoded at the receiving node based on the decoding time sequence, if the PDU set is not transmitted properly, the next PDU set may not be decoded properly. The PDU set is preferably distributed based on the decoding time sequence.

[0083] In FIG. 3, by way of example, it is shown that the PDU set time sequence is indicated by the PDU set sequence number.

[0084] One application frame includes a plurality of IP packets (e.g., PDUs) that make up the PDU set.

[0085] Since the decoding of the PDU set is based on the decoding time sequence, 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 a plurality of QoS flows based on the decoding time sequence. The QFI (QoS flow identifier) sequence number is encoded / numbered for each QoS flow.

[0086] For example, in the embodiment corresponding to FIG. 3, the receiving side decodes sequentially, such as the I1 frame, the P4 frame, the B2 frame, etc., based on the decoding time sequence.

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

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

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

[0090] The rest can be inferred by analogy.

[0091] Since the DL (downlink) QFI sequence number is encoded / numbered for each QoS flow, the DL QFI sequence number may be the same or different for PDUs within different QoS flows.

[0092] Some In an embodiment, the digital number is simply used to indicate the sequence number.

[0093] Figure 4 shows the mapping between the GTP-U, NG-U, Xn-U, or NAS-U PDU set and the QoS flow, and the PDU set time sequence is indicated by the DL QFI sequence number.

[0094] Some In an embodiment, the PDU set is identified by PDU set information including a PDU set start indication and / or a PDU set end indication And / or the total number of PDUs in the PDU set The PDU set time sequence is indicated by the DL QFI sequence number, and the DL QFI sequence number is encoded / numbered across multiple QoS flows for each PDU session or traffic flow used to indicate the application frame sequence and / or the application data unit sequence.

[0095] Some In an embodiment, the PDU set time sequence can be a PDU set decoding time sequence (e.g., the next PDU set can be decoded only if the current PDU set is successfully decoded) or a PDU set presentation time sequence (e.g., in the case of video streaming, image frames are presented one by one according to the presentation time sequence).

[0096] In FIG. 4, using an example, it illustrates that the PDU set time sequence is indicated by the DL QFI sequence number.

[0097] One application frame includes a plurality of IP packets, which construct a PDU set and are identified by the PDU set start indication and the PDU set start indication. For example, in PDU set 1, packet I11 corresponds to the PDU set start indication, and packet I1n corresponds to the PDU set end indication.

[0098] Since the decoding of the PDU set is based on the decoding time sequence, different PDU sets have different priorities or importance levels. Therefore, different PDU sets are mapped to different QoS flows. When PDU set information (for example, the PDU set start indication or the PDU set end indication) is included, the DL QFI sequence number is encoded / numbered across a plurality of QoS flows based on the decoding time sequence.

[0099] For example, in the embodiment corresponding to FIG. 4, the receiving side decodes sequentially such as the I1 frame, the P4 frame, the B2 frame, etc. based on the decoding time sequence.

[0100] The I1 frame includes I11, I12,..., I1n packets (PDUs). The 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.

[0101] The P4 frame includes P41, P42,..., P4b packets (PDUs). The 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.

[0102] The B2 frame contains B21, B22, ..., B2m packets (PDUs). The 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).

[0103] The rest can be inferred by analogy.

[0104] Some In an embodiment, the digital number is used simply to indicate the sequence number.

[0105] When the PDU set information is included in the PDU session information format, the DL QFI sequence numbers are encoded / numbered across multiple QoS flows based on the PDU set decode time sequence to indicate the decode time sequence. When the PDU set information is not included in the PDU session information format, the DL QFI sequence numbers are encoded for each QoS flow.

[0106] Embodiment 2 (PDUs within one PDU set are mapped to one SDAP PDU) Figure 5a shows the mapping between the PDU set and the SDAP PDU, where the PDUs within the GTP-U, NG-U, Xn-U, or NAS-U PDU set are included in one SDAP PDU.

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

[0108] In one embodiment, by concatenating packets, all PDUs within one PDU set are included in one SDAP PDU. For example, the PDUs of PDU set 1 are included in one SDAP PDU, the PDUs of PDU set 2 are included in another SDAP PDU, and so on.

[0109] Figure 5b shows an SDAP data PDU format without an SDAP header and having a plurality of upper layer PDUs. Figure 5c shows a DLSDAP data PDU format having an SDAP header. Figure 5d shows a ULSDAP data PDU format having an SDAP header and a plurality of upper layer data PDUs.

[0110] As shown in Figures 5b, 5c, and 5d, an SDAP PDU includes a plurality of upper layer data PDUs within one PDU set, and the PDUs within 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 concatenated one by one based on the PDU sequence number and are included in the data field of the SDAP PDU starting from the first bit.

[0111] Embodiment 3 (PDUs within one PDU set are mapped to one PDCP PDU) Figure 6a shows the mapping between a PDU set and a PDCP PDU, where the PDUs within one GTP-U, NG-U, Xn-U, or NAS-U PDU set are mapped to one PDCP PDU. More specifically, the PDUs within 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.

[0112] Figures 6b and 6c show a PDCP PDU including a plurality of PDCP SDUs (e.g., SDAP PDUs), which includes a plurality of PDCP data fields having corresponding MAC-I fields, and are concatenated in order as shown in Figure 6b, or the plurality of PDCP data fields are concatenated in order with one corresponding MAC-I field (see Figure 6c).

[0113] One PDCP data field (e.g., Data 1 or Data 2 in Figures 6b and 6c) corresponds to one PDCP SDU (e.g., SDAP PDU).

[0114] Embodiment 4 (PDU set indication in SDAP PDU, PDCP PDU, and RLC PDU) In this embodiment, the PDUs within one PDU set are included in a plurality of PDCP PDUs, and the PDU set information is included in the SDPA PDU, PDCP PDU, and / or RLC pPDU to indicate which PDUs belong to one PDU set.

[0115] Based on the PDU set sequence number and / or PDU set information in the embodiment corresponding to Figure 3 or Figure 4, the SDAP entity can identify the start opportunity and end opportunity of the PDU set. However, the DL grant is scheduled at the MAC layer, and whether the PDUs within one PDU set are transmitted in one TB (transport block), one TB group, or the same time domain position is determined at the RLC layer and / or MAC layer. Therefore, the RLC layer and / or MAC layer also need information about the opportunities for PDU set start and end.

[0116] In some embodiments, all the TBs for one RLC PDU are successfully received before concatenation. The RX (receive) side RLC entity can know whether all the TBs for one RLC PDU are successfully received according to 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).

[0117] For a set of PDUs having multiple PDCP PDUs, there are several possible solutions to indicate to the RLC layer and / or MAC layer that the RLC SDUs belong to the same set of PDUs.

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

[0119] Option 2: The SDAP PDU set field, PDCP PDU set field, and / or RLC PDU set field containing information for PDU set identification are introduced into the SDAP, PDCP, and / or RLC PDU formats using reserved bits of the existing PDU format transmitted over the Uu interface without increasing the Uu overhead, for example, or using a new PDU format transmitted over the Uu interface.

[0120] Figure 7a shows that the SDAP PDU contains a PDU set sequence number. In this embodiment, the PDU set sequence number is used to indicate to which PDU set the corresponding PDU belongs. For example, PDUs having the same PDU set sequence number belong to the same PDU set.

[0121] Figure 7b shows that the SDAP PDU contains PDU set information. In this embodiment, the PDU set information is used to indicate which PDUs belong to one PDU set. For example, a PDU set start indication and / or a PDU set end indication may be included in the SDAP PDU. The sequence of PDUs from the first PDU having a PDU set start indication to the last PDU having a PDU set end indication belongs to one PDU set.

[0122] Figure 7c shows that the PDU set information (PSI) is included in the PDCP data PDU having a 12-bit PDCP SN. Figure 7d shows that the PDU set information (PSI) is included in the PDCP data PDU for a DRB (data radio bearer) having an 18-bit PDCP SN.

[0123] As shown in FIGS. 7c and 7d, the PDU set information is indicated in the PDCP PDU. In the embodiments corresponding to FIGS. 7c and 7d, 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 one TB, one TB group, or the same time domain position.

[0124] Figure 7e shows that the PDU set information (PSI) is included in the UMD (unauthenticated mode data) RLC PDU having a 12-bit SN (without SO). Figure 7f shows that the PDU set information (PSI) is included in the UMD (unauthenticated mode data) RLC PDU having a 12-bit SN (with SO). Figure 7g shows that the PDU set information (PSI) is included in the AMD (authenticated mode data) RLC PDU having an 18-bit SN (without SO). Figure 7h shows that the PDU set information (PSI) is included in the AMD (authenticated mode data) RLC PDU having an 18-bit SN (with SO).

[0125] As shown in FIGS. 7c, 7d, 7e, 7f, 7g, and 7h, the PDU set information is indicated by PDCP PDUs and / or RLC PDUs.

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

[0127] The UMD PDU header includes an SN field only if the corresponding RLC SDU is segmented or if the PDU set information is included in the UMD PDU. When the PDU set information is included in the PDU, the SN within the PDU is coded / numbered across PDU sets (e.g., across multiple SDUs).

[0128] In some embodiments, the PDU set information (PI or PSI) field can be coded as follows.

[0129] Some In an embodiment, the PI field can be used. Some In an embodiment, the PI field can have a length of 2 bits. Some In an embodiment, the PI field is used to indicate whether several PDUs correspond to the same PDU set. For example, the PI field can indicate that the PDU is at the beginning, in the middle, and / or at the end of the PUD set, or that no PDU set information is included. Specifically, the PI field indicates whether PDU set information is 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 to neither the first nor the last PDU of the PDU set. The interpretation of the PI field is shown in Table 1.

Table 1

[0130] Alternatively, a PSI field can be used. Some In an embodiment, the PSI field can have a length of 2 bits. Some In an 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 an intermediate PDU (neither the first nor the last PDU) of the PDU set, or whether PDU set information is not included. The interpretation of the PSI field is shown in Table 2. [Table 2]

[0131] Note that the mapping between values and descriptions may be subject to change. For example, the value "01" may be used to indicate that the PDU is the last PDU of the PDU set, and the value "10" may be used to indicate that the PDU is the first PDU of the PDU set.

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

[0133] In some embodiments, the RLC SDU may be segmented into a plurality of RLC PDUs, and since the plurality of RLC PDUs correspond to the same SN number with different SI and / or SO, the PI (or PSI) of the RLC PDU can be set with the following options.

[0134] Option 1: Set PI (or PSI) based on SN. For example, multiple RLC PDUs having the same RLC SDU SN (e.g., PDCP PDU SN) are configured with the same PI (or PSI) value.

[0135] Option 2: Set PI (or PSI) based on the 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 as the first PDU in the PDU set (e.g., value "01"), and the PI (or PSI) of the last PDU (SI = 10) of the last RLC SDU is set as the last PDU in the PDU set (e.g., value "10").

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

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

[0138] 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 scheduling on the TX side, rather than for reception and decoding on the RX side. 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 may be added to the PDCP PDU and / or RLC PDU. In such a case, when a lower layer entity receives a PDCP PDU and / or RLC PDU having a temporary header field, the lower layer can delete the temporary header field after obtaining the PDU set information. Thus, the temporary header field may not be transmitted via the Uu interface (e.g., may not be transmitted from the gNB (gNodeB) to the UE (user equipment) or from the UE to the gNB).

[0139] Embodiment 5 (PDU Set Dependency Indication): In some embodiments, PDU sets can be dependent on each other (e.g., in a video streaming service, a B frame depends on the previous adjacent frame, and a P frame depends on the previous adjacent frame and the subsequent adjacent frame), and different PDU sets can have different priorities (e.g., importance levels). In some embodiments, various options are provided to identify dependencies and priorities as follows.

[0140] 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, a B frame, or 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 individual, depends on the previous PDU set, depends on the previous PDU set and the subsequent PDU set) is indicated in the SDAP PDU, PDCP PDU, and / or RLC PDU.

[0141] Figure 8a shows that the PDU set dependency indication is included in the SDAP PDU. Figure 8b shows that the PDU set dependency indication is included in the PDCP PDU. Figure 8c shows that the PDU set dependency indication is included in the RLC PDU. Whether a new SDAP PDU format, PDCP PDU format, and / or RLC PDU format is being used can be explicitly indicated by UE-specific signaling.

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

[0143] Figure 8d shows that when PDU set information is included, the SNs of the PDCP PDU and the RLC PDU are encoded / numbered across multiple DRBs and / or multiple logical channels.

[0144] Some In an embodiment, the PDCP PDU of PDU set 1 is mapped to the DRB#1 tunnel, and the PDCP PDU of PDU set 2 is mapped to the DRB#2 tunnel.

[0145] Some In an embodiment, the RLC PDU within PDU set 1 is mapped to LC#1, and the RLC PDU within PDU set 2 is mapped to LC#2. LC refers to the logical channel.

[0146] SomeIn an embodiment, the sequence numbers of PDCP PDUs in PDU set 1 are encoded / numbered from 1 to n, and the sequence numbers of PDCP PDUs in subsequent PDU sets (for example, PDU set 2) are encoded / numbered from n + 1 to n + x, and so on.

[0147] Some In an embodiment, the sequence numbers of RLC PDUs in PDU set 1 are encoded from 1 to m, and the sequence numbers of RLC PDUs in subsequent PDU sets (for example, PDU set 2) are encoded from m + 1 to m + y, and so on.

[0148] Option 3: Dependencies / information are explicitly indicated. For example, relevant sequence numbers, relevant DRB IDs (identifiers), and / or logical channel IDs are included in the PDCP PDU and / or RLC PDU.

[0149] FIG. 8e shows that PDU dependency information is included in the PDCP PDU, and FIG. 8f shows that PDU dependency information is included in the RLC PDU.

[0150] Some In an embodiment, PDU dependency information is explicitly indicated in the PDU. Some In an embodiment, PDU dependency information includes at least DRB ID dependency (for example, indicating the dependent DRB of the corresponding PDU), LC ID dependency (for example, indicating the dependent LC of the corresponding PDU), PDU-dependent SN (for example, indicating the SN of the dependent PDU of the corresponding PDU), and / or PDU-dependent SN LSB (least significant bit) (for example, indicating the LSB within the SN of the dependent PDU of the corresponding PDU, and the SN LSB is used instead of the SN to reduce bit requirements).

[0151] Some In an embodiment, whether a new PDCP PDU format and / or RLC PDU format is being used can be explicitly indicated by UE-specific signaling.

[0152] Some In an embodiment, since the associated sequence number (e.g., "SN dependence of PDU" as described above) and the associated DRB ID (e.g., "DRB ID dependence" above) or LC ID (e.g., "LC ID dependence" above) are only used in TX scheduling and have many bits (overhead), some optimization can be applied.

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

[0154] Alternative 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 added 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 can remove the temporary header field. Therefore, the temporary header field may not be transmitted via the Uu interface (e.g., not transmitted from the gNB to the UE or from the UE to the gNB).

[0155] Option 4: The PDU set sequence number is included in the PDCP PDU and / or the RLC PDU, and the PDU set sequence number is encoded / numbered across 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 the RLC PDU can correspond to the same user data included in the PDU set in GTP-U, NG-U, Xn-U, or the NAS-U PDU set and the QoS flow, regardless of whether the PDU set is segmented or aggregated.

[0156] FIG. 8g shows that the PDU set SN (sequence number) is included in the PDCP PDU, and FIG. 8h shows that the PDU set SN is included in the RLC PDU.

[0157] Some In an embodiment, whether a new PDCP PDU format and / or RLC PDU format is being used may be explicitly indicated by UE-specific signaling.

[0158] When the PDU set information is included in the corresponding PDU, the PDU set SN is coded / numbered across multiple DRBs and / or multiple logical channels.

[0159] Based on the PDU set SN and / or PDU SN, the PDU set time sequence can be identified.

[0160] Embodiment 6 (Reflective QoS Indication): FIG. 9a shows procedures related to a reflective QoS indication or a proactive QoS update request.

[0161] Some In an embodiment, based on NW (Network) capabilities and / or NW priorities, a reflective QoS indication or a proactive QoS update request is sent from the gNB to the CN to trigger QoS parameter updates. For example, the RAN (Radio Access Network) provides QoS assistance information to the CN or the application layer to request dynamically adjusting QoS parameters.

[0162] Some In an embodiment, the QoS assistance information includes at least one of the following parameter types: i.e., the suggested QoS parameter value, the suggested QoS flow priority level, the suggested application data and QoS flow mapping, the suggested paging strategy, UE mobility information, artificial intelligence-related information, machine learning-related information, network usage awareness, network computing capabilities, and / or UE positioning-related information.

[0163] Some In an embodiment, the gNB can provide one or more sets of the indicated QoS support information, and the CN can determine, select, accept, reject, or recommend QoS information based on one or more sets of the indicated QoS support information.

[0164] Some In an embodiment, the QoS support information includes at least one of the following parameters, namely, The per-cell maximum aggregated bitrate carried on cell-specific signaling that the gNB prefers or permits, The maximum bitrate per QoS flow carried on UE-specific signaling or NG-U PDUs that the gNB prefers or permits, or the maximum bitrate per QoS flow, The per-PDU session maximum aggregated bitrate carried on UE-specific signaling or NG-U PDUs that the gNB prefers or permits, The DL PDU transmission time offset carried via UE-specific signaling or NG-U PDUs, which is used to indicate to the CN to transmit PDUs of QoS flows and / or PDU sessions 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 relative to at least one of the current transmission start time, the current transmission end time, and / or the current transmission timing opportunity, The DL PDU arrival time carried via UE-specific signaling or NG-U PDUs, which is used to instruct the CN to transmit PDUs of QoS flows and / or PDU sessions so as to ensure that the PDUs arrive at the gNB based on the indicated DL PDU arrival time, The maximum packet size that is carried by UE - specific signaling or an NG - U PDU and is preferred or supported by the gNB, used to ensure that the received packet size is suitable for the gNB. The application - encoded data rate preferred by the gNB, which is carried via UE - specific signaling or an NG - U PDU and is used to dynamically adjust the application - encoded data rate. The CN PDB (Packet Delay Budget) detected by the gNB, which is carried by UE - specific signaling or an NG - U PDU and is used by the gNB to determine the DL data transmission opportunity. The PDB headroom used by the gNB to detect and determine the DL data transmission opportunity The BER detected by the gNB. The PER detected by the gNB. Network node load information. Network node self - computing capacity headroom. Computing capacity headroom requirements for the core network or cloud native. Uu time synchronization error budget. Uu packet delay budget. Uu packet delay budget headroom. The duration for which a service is preferably used, which is carried via UE - specific signaling or an NG - U PDU and is used by the gNB to determine the DL data transmission opportunity, and / or The start time at which a service is preferably triggered, which is carried via UE - specific signaling or an NG - U PDU and is used by the gNB to determine the DL data transmission opportunity.

[0165] The QoS support information can be used to trigger DL user data rate adaptation (e.g., application - encoded data rate adjustment from HD (High - Definition) video to SD (Standard - Definition) video or from SD video to HD video), map traffic patterns to network resources, and / or adjust QoS parameters to improve the user experience.

[0166] Figure 9b shows another procedure related to a reflective QoS indication or a proactive QoS update request.

[0167] Some In an embodiment, a reflective QoS indication or a proactive QoS update request is sent from a gNB to a UE to trigger QoS parameter update based on NW (Network) capabilities and / or NW priorities. For example, a RAN (Radio Access Network) provides QoS assistance information to the UE to request dynamic adjustment of QoS parameters.

[0168] Some In an embodiment, the QoS assistance information includes at least one of the following parameter types, namely, the suggested QoS parameter value, the suggested priority level of the QoS flow, the suggested application data and QoS flow mapping, the suggested paging strategy, UE mobility information, artificial intelligence related information, machine learning related information, network usage awareness, network computing capabilities, and / or UE positioning related information.

[0169] Some In an embodiment, the gNB can provide one or more sets of the suggested QoS assistance information, and the UE can determine, select, accept, reject, or recommend QoS information based on one or more sets of the suggested QoS assistance information.

[0170] Some In an embodiment, the QoS assistance information includes at least one of the following parameters, namely, the maximum aggregated bitrate per UE that the gNB prefers or permits, the maximum aggregated bitrate per DRB that the gNB prefers or permits, the maximum aggregated bitrate per logical channel that the gNB prefers or permits, the maximum aggregated bitrate per logical channel group that the gNB prefers or permits, The application-coded data rate preferred by the gNB, which is used to dynamically adjust the application-coded data rate, The UL PDU transmission time offset, which is used to indicate to the UE to transmit PDUs of DRBs and / or logical channels at 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 at least one of the following, namely, the current transmission start time, the current transmission end time, and / or the current transmission timing opportunity, The UL PDU transmission time used to indicate to the UE to transmit PDUs of DRBs and / or logical channels to ensure that the PDUs are transmitted based on the indicated transmission time, The BER detected by the gNB that the UE uses to adjust the coding rate and / or transmission power, The PER detected by the gNB that the UE uses to adjust the coding rate and / or transmission power, Network node load information The network node's self-computation ability headroom, The computation ability headroom requirement for the core network or cloud native, The Uu time synchronization error budget, The Uu packet delay budget, The Uu packet delay budget headroom, The duration in which the service is preferably used and / or the start time at which the service is preferably triggered that the UE uses to determine the UL data transmission opportunity, Related to the start time, which is the start time at which the service is preferably triggered and the UE uses to determine the UL service start time or data transmission opportunity,

[0171] SomeIn an embodiment, the QoS support information is carried via at least one of RRC (Radio Resource Control) unicast signaling, MAC CE (Control Element), or PDCCH (Physical Downlink Control Channel) DCI (Downlink Control Information).

[0172] Some In an embodiment, the QoS support information can be used to trigger UL user data rate adaptation (e.g., adjusting the application-coded data rate from HD video to SD video or from SD video to HD video), map traffic patterns using network resources, and / or improve the user experience.

[0173] Embodiment 7 (Specific buffer size indication): For a full buffer service or an XR service with a fixed buffer size, the UE can indicate the UL buffer size to the gNB by one of the following, i.e., Whether a specific BSR format (e.g., an MAC CE format where only the LCG (Logical Channel Group) ID (LC ID), or DRB ID has a new LC ID for MAC CE identification) is used to indicate that the buffer size is the same as the latest reported BS, Whether only the BSR MAC header with a new LC ID (e.g., 0-byte MAC CE) is used to indicate that the buffer size is the same as the latest buffer size reported for the logical channel, logical channel group, or DRB, or Whether only the BSR MAC header with a new LC ID (e.g., 0-byte MAC CE) is used to indicate that the buffer size is the same as the latest transport block size transmitted for the logical channel, logical channel group, or DRB.

[0174] The uplink control information (UCI) is used to indicate that the buffer size is the same as the latest buffer size reported for a logical channel, a logical channel group, or a DRB, or the transport size transmitted. Block This can be used to reduce the radio resource consumption of the BSR MAC CE.

[0175] With such a configuration, the radio resource consumption of the BSR MAC CE can be reduced.

[0176] Embodiment 8 (Multiple C-DRX (Intermittent Reception in RRC_Connected State) Configurations): In some embodiments, multiple C-DRXs (DRX in the RRC_Connected state) may be configured for each cell group, for each DRB, and for each logical channel to address non-integer periodicity issues and / or to match traffic pattern issues. 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 of C-DRX periodicity is ms (milliseconds), and fps or Hz may not be fully mapped to ms. For example, 60 fps or 60 Hz can be converted to a period of 16.6666... ms, which is not an integer and cannot fully map the traffic pattern to the C-DRX configuration. In such cases, multiple C-DRX patterns can be used to map the traffic pattern. For example, the following three C-DRX configurations can be used to map the traffic pattern at 60 fps or 60 Hz.

Table 3

[0177] When multiple C-DRX patterns are configured for each cell group, for each DRB, and for each logical channel, a C-DRX index or C-DRX identification information is used to identify each C-DRX configuration.

[0178] Some In an embodiment, the C-DRX index or C-DRX identification information can be explicitly configured in the C-DRX configuration.

[0179] Some In an embodiment, the C-DRX index or C-DRX identification information can be implicitly indicated based on the C-DRX configuration sequence entry. For example, the first entry of SEQUENCE corresponds to the first C-DRX configuration, the C-DRX index (or C-DRX identification information) is equal to 1, the second entry of SEQUENCE corresponds to the second C-DRX configuration, and the C-DRX index (or C-DRX identification information) is equal to 2, and so on.

[0180] Some In an embodiment, based on the C-DRX index or C-DRX identification information, one or more of the C-DRX configurations can be modified, deleted, activated, or deactivated independently of the delta configuration. For example, when deleting a specific C-DRX configuration, only the C-DRX index or C-DRX identification information corresponding to the specific C-DRX configuration can be shown to the UE. In this case, in order to overwrite the old C-DRX configuration, it is possible to avoid showing all the new C-DRX configurations to the UE.

[0181] Embodiment 9 (PDU relationship indication between UL and DL or between UEs): FIG. 10a shows a buffer size report. FIG. 10b shows a buffer size report with DL PDU response information.

[0182] As shown in FIGS. 10a and 10b, a relationship indication between the UL PDU and the DL PDU that triggers the BSR is shown.

[0183] When receiving a DL PDU, the UE can trigger a BSR MAC CE for transmitting a UL response PDU.

[0184] SomeIn an embodiment, the BSR MAC CE includes at least one of the following information, that is, As shown in FIG. 10a, a DL LC ID or DL LC priority related to a UL PDU that triggers a BSR, As shown in FIG. 10b, a DL PDU response indication related to a UL PDU that triggers a BSR, and / or As shown in FIGS. 10a and 10b, related DL PDU information including at least one of a PDU SN or PDU time domain information (for example, SFN (system frame number) information, slot information, and / or symbol information).

[0185] FIG. 10c shows a PDU or BSR including UE ID information and PDU information. FIG. 10d shows a PDU or BSR including UE ID information and PDU response information.

[0186] As shown in FIGS. 10c and 10d, a relationship indication between UEs is shown.

[0187] Some In an embodiment, the PDU or BSR includes As shown in FIGS. 10c and 10d, a related UE ID (for example, C-RNTI), As shown in FIGS. 10c and 10d, related PDU information including at least one of a PDU SN or PDU time domain information (for example, SFN information, slot information, and / or symbol information), A QoS flow ID, LC ID, or LC priority related to the PDU (for example, the current PDU), and / or A PDU response indication related to the current PDU.

[0188] Some In an embodiment, the current PDU includes at least one of a GTP-U PDU, an NG-U PDU, an Xn-U PDU, a NAS-U PDU, an SDAP PDU, a PDCP PDU, and / or an RLC PDU.

[0189] Some In an embodiment, based on the relationship indication as described above, the gNB can determine a resource scheduling priority, or an uplink SR (Scheduling Request), a UL BSR, and / or a UL grant for PUSCH transmission.

[0190] FIG. 11 relates to a schematic diagram of a wireless communication terminal 30 (for example, a terminal node or a terminal device) according to an embodiment of the present disclosure. 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, and is not limited herein. The wireless communication terminal 30 can 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 that stores 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 and is used to transmit and receive signals (for example, messages or packets) according to the processing results of the processor 300. Some Some In an embodiment, the communication unit 320 transmits and receives signals via at least one antenna 322.

[0191] Some In an embodiment, the storage unit 310 and the program code 312 may be omitted, and the processor 300 may include a storage unit having the stored program code.

[0192] The processor 300 can implement any of the steps in the illustrated embodiments on the wireless communication terminal 30, for example, by executing the program code 312.

[0193] The communication unit 320 may be a transceiver. Alternatively or in addition, the communication unit 320 may combine a transmission unit and a reception unit configured to respectively transmit and receive signals with a wireless communication node.

[0194] In some embodiments, the wireless communication terminal 30 may be used to perform the operations of the UE described above. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the operations described above. For example, the processor 300 performs the operations and transmits or receives signals, messages, and / or information via the communication unit 320.

[0195] FIG. 12 is of the present disclosure SomeRelates to a schematic diagram of a wireless communication node 40 (e.g., a network device) according to an embodiment. 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 the core network, or a radio network controller (RNC), and is not limited herein. Further, the wireless communication node 40 can 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), and an application function (AF). The wireless communication node 40 can 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 that stores 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 and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 400. In one example, the communication unit 420 transmits and receives signals via at least one antenna 422.

[0196] Some In an embodiment, the storage unit 410 and the program code 412 may be omitted. The processor 400 can include a storage unit having stored program code.

[0197] The processor 400 can perform any of the steps described in the illustrated embodiments on the wireless communication node 40, for example, by executing the program code 412.

[0198] The communication unit 420 may be a transceiver. Alternatively or in addition, the communication unit 420 may be a combination of a transmission unit and a reception unit configured to transmit and receive signals, messages, or information, respectively, between a wireless communication node or a wireless communication terminal.

[0199] In some embodiments, the wireless communication node 40 may be used to perform the operations of the gNB described above. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described above. For example, the processor 400 performs the operations and transmits or receives signals via the communication unit 420.

[0200] Details regarding this can be verified by referring to the above paragraphs and will not be repeated here.

[0201] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, the various figures can show exemplary architectures or configurations provided so that those skilled in the art can understand the exemplary features and functions of the present disclosure. However, such persons will understand that the present disclosure is not limited to the illustrated exemplary architectures or configurations and can be implemented using various alternative architectures and configurations. Further, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the scope and range of the present disclosure should not be limited by any of the above exemplary embodiments.

[0202] Also, it should be understood that when referring to elements in this specification using terms such as "first", "second", etc., generally these do not limit the quantity or order of those elements. Rather, these terms can be used in this specification as a convenient means of distinguishing two or more elements or examples of elements. Thus, references to the first and second elements do not mean that only two elements can be used, or that the first element must precede the second element in any way.

[0203] Furthermore, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0204] Those skilled in the art will further understand that any one of the various exemplary logical blocks, units, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or "software units"), or any combination of these technologies.

[0205] To clearly illustrate this compatibility of hardware, firmware, and software, various exemplary components, blocks, units, circuits, and steps have been generally described above in terms of their functions. Whether such functions are implemented as hardware, firmware, software, or a combination of these technologies depends on the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each particular application, but such implementation decisions do not depart from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. may be configured to perform one or more of the functions described herein. The terms "configured to" or "configured for" as used herein with respect to a specified operation or function refer to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the particular operation or function.

[0206] Furthermore, those skilled in the art will understand that the various exemplary logical blocks, units, devices, components, and circuits described herein can be implemented in or executed by an integrated circuit (IC) including 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 logical blocks, units, and circuits can further include antennas and / or transceivers for communicating with various components within a network or device. The general-purpose processor may be a microprocessor, but in the alternative, 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, one or more microprocessors cooperating with a DSP core, or any other suitable configuration for performing the functions described herein. When implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Accordingly, the steps of the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium.

[0207] The computer-readable medium includes both a computer storage medium and a communication medium including any medium that can transfer a computer program or code from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0208] As used herein, the term "unit" refers to software, firmware, hardware, and any combination of these elements for performing the related functions described herein. Further, for illustrative purposes, the various units are described as individual units, however, as will be apparent to those skilled in the art, two or more units can be combined to form a single unit that performs the related functions according to embodiments of the present disclosure.

[0209] Furthermore, in embodiments of the present disclosure, memory or other storage, as well as communication components, can be used. For clarity, it will be understood that the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions can be used between different functional units, processing logic elements, or regions without detracting from the present disclosure. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are not intended to indicate a strict logical or physical structure or organization, but rather are merely references to suitable means for providing the described functions.

[0210] Various changes to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the embodiments shown herein, but rather should be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

Claim 1 Receiving, by a wireless communication node, a protocol data unit (PDU) including identification information from an upper layer; and Identifying, by the wireless communication node, at least one of a PDU set of the PDU and a PDU set time sequence of the PDU set; wherein the upper 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 (Xn-U) interface, user data from a Non-Access Stratum (NAS), and user data of a QoS flow. A wireless communication method. Claim 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. Claim 3 The wireless communication method according to claim 1 or 2, wherein the PDU set time sequence is indicated by a PDU set sequence number. Claim 4 The wireless communication method according to any one of claims 1 to 3, wherein when the PDU set is mapped to a plurality of QoS flows, the PDU set sequence number is encoded across the plurality of QoS flows based on a decoding time sequence of the Quality of Service (QoS) flow. Claim 5 The wireless communication method according to claim 1, wherein the wireless communication node receives at least one of a PDU set start indication, a PDU set end indication for each PDU set, or a total number of PDUs of the PDU set, and the PDU set is determined by the at least one of the PDU set start indication, the PDU set end indication, or the total number of PDUs of the PDU set. Claim 6 The wireless communication method according to claim 1 or 5, wherein the PDU set time sequence is determined by a QoS flow identifier, QFI, and sequence number of the PDUs within the PDU set. Claim 7 The wireless communication method according to claim 6, wherein when the PDU set is mapped to a plurality of QoS flows, the QFI sequence number is encoded across the plurality of QoS flows based on the PDU set time sequence. Claim 8 The wireless communication method according to any one of claims 1 to 7, 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 PDU corresponding to each PDU set is sequentially included in the SDAP PDU based on the PDU sequence number of the PDU.

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 SDAP PDUs is included in a packet data convergence protocol (PDCP) PDU.

11. The wireless communication method according to claim 10, wherein the PDU corresponding to each PDU set is 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 reserved bits.

14. The wireless communication method according to claim 13, wherein the PDU set indication in the at least one of the SDAP PDU, the PDCP PDU, or the RLC PDU includes 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 of the PDU set indication includes at least one of 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 start position of the corresponding PDU set, an indication indicating that the corresponding PDU is at the end position of the corresponding PDU set, or an indication indicating that the corresponding PDU is at an intermediate 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 is transmitted in one transport block (TB), one TB group, or the same time domain position.

17. The 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 the SDAP PDU, PDCP PDU, or RLC PDU, and information of the PDU set is indicated by using at least one of a temporary header or reserved bits.

18. The wireless communication method according to claim 17, wherein the PDU set type indication indicates that the corresponding PDU set corresponds to a video compression type of an I-frame, B-frame, or P-frame, or indicates a corresponding PDU set decoding time sequence or a PDU set decoding dependency including at least one of a primary frame, a secondary frame, or an nth secondary 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 individual, depends on the previous PDU set, or depends on the previous PDU set and the next PDU set.

20. The wireless communication method according to any one of claims 1 to 16, wherein a PDU set dependency between PDUs is indicated by including a sequence number (SN) in at least one of the PDCP PDU or RLC PDU.

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

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

23. 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 across a plurality of DRBs or a plurality of logical channels based on the PDU set sequence number within a PDCP service data unit (SDU). The wireless communication method according to any one of claims 1 to 16.

24. Including transmitting, by a wireless communication node, a reflective quality of service (QoS) indication or a proactive QoS update request to a core network (CN) or a wireless communication terminal, The reflective QoS indication or the proactive QoS update request includes one or more sets of implied QoS support information, Wireless communication method.

25. The implied QoS support information includes at least one of the following parameter types, namely, an implied QoS parameter value, an implied priority level of a QoS flow, an implied mapping between application data and a QoS flow, an implied paging strategy, a user equipment (UE), mobility information, artificial intelligence related information, machine learning related information, network usage awareness, network computing ability, or UE positioning related information. The wireless communication method according to claim 24.

26. The implied QoS support information transmitted to the CN includes the following parameters, namely, The maximum aggregated bitrate per cell that the wireless communication node prefers or permits, The maximum bitrate per carried QoS flow that the wireless communication node prefers or permits, The maximum aggregated bitrate per protocol data unit (PDU) session that the wireless communication node prefers or permits, A downlink (DL) PDU transmission time offset used to instruct the CN to transmit a PDU session having a PDU or a time delay offset or a time advance offset of a QoS flow, where the DL PDU transmission time offset is relative to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity. DL PDU transmission time offset, The DL PDU arrival time, which is used to instruct the CN to transmit the PDU of the QoS flow or PDU session so as to ensure that the PDU arrives at the wireless communication node based on the DL PDU arrival time, The maximum packet size preferred or supported by the wireless communication node, The application encoded data rate preferred by the wireless communication node, The CN packet delay budget (PDB) detected by the wireless communication node and used by the wireless communication node to determine the DL data transmission opportunity, The CN packet delay budget headroom detected by the wireless communication node and used by the wireless communication node to determine the DL data transmission opportunity, The bit error rate (BER) detected by the wireless communication node, The packet error rate (PER) detected by the wireless communication node, Network node load information, Network node self-computation ability headroom, Computing ability headroom requirements for the core network or cloud native, Uu time synchronization error budget, Uu packet delay budget, Uu packet delay budget headroom, The duration preferred and used by the service and used by the wireless communication node to determine the DL data transmission opportunity, or, The start time preferred and triggered by the service and used by the wireless communication node to determine the DL data transmission opportunity, at least one of which is included in the wireless communication method according to claim 24 or 25.

27. The suggested QoS support information transmitted by the wireless communication terminal is the following parameters, namely, The maximum aggregated bit rate per UE preferred or permitted by the wireless communication node, The maximum aggregated bit rate per DRB preferred or permitted by the wireless communication node, The maximum aggregated bit rate per logical channel preferred or permitted by the wireless communication node, The maximum aggregated bit rate per logical channel group preferred or permitted by the wireless communication node, The application encoded data rate preferred by the wireless communication node, An uplink (UL) PDU transmission time offset used to indicate to the wireless communication terminal to transmit the PDU of the DRB or logical channel using a time delay offset or a time advance offset, wherein the UL PDU transmission time offset is relative to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity, the UL PDU transmission time offset The UL PDU transmission time used to indicate to the wireless communication terminal to transmit the PDU of the DRB or logical channel in order to ensure that the PDU is transmitted based on the indicated transmission time The BER detected by the wireless communication node and 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 and used by the wireless communication terminal to adjust at least one of a coding rate or a transmission power Network node load information Network node self-computation ability headroom Computing ability headroom requirements for the core network or cloud native Uu time synchronization error budget Uu packet delay budget Uu packet delay budget headroom A duration in which a service is preferably used and used by the wireless communication terminal to determine a UL data transmission opportunity, or The wireless communication method according to any one of claims 24 to 26, including at least one of a start time in which the service is preferably triggered and used by the wireless communication terminal to determine a UL service start time or the UL data transmission opportunity

28. A wireless communication method including receiving a buffer size indication from a wireless communication terminal by a wireless communication node A wireless communication method

29. The buffer size indication is A specific buffer status report (BSR) format indicating that the buffer size is the same as the latest reported buffer size A specific BSR medium access control (MAC) header with a new logical channel (LC) identifier (ID) indicating that the buffer size is the same as the latest reported buffer size for a logical channel, a logical channel group, or a data radio bearer (DRB) A specific BSR medium access control (MAC) header having a new logical channel (LC) identifier (ID) indicating that the buffer size is the same as the latest transport size transmitted for a logical channel, a logical channel group, or a DRB, or, The wireless communication method according to claim 28, comprising at least one of the above, or uplink control information indicating that the buffer size is the same as the latest transport size transmitted for a logical channel, a logical channel group, or a DRB.

30. Transmitting an RRC_Connected state discontinuous reception (C-DRX) configuration to a wireless communication terminal by a wireless communication node; Performing communication using a plurality of C-DRX patterns for each cell group, each data radio bearer, each DRB, or each logical channel according to the C-DRX configuration, by the wireless communication node with the wireless communication terminal; A wireless communication method.

31. The wireless communication method according to claim 30, wherein each C-DRX configuration includes a C-DRX index or C-DRX identification information used to identify the C-DRX configuration.

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

33. The wireless communication method according to any one of claims 30 to 32, wherein the wireless communication node transmits a request to the wireless communication terminal using the C-DRX index or C-DRX identification information to change, delete, activate, or deactivate one of the C-DRX configurations corresponding to the C-DRX index or the C-DRX identification information.

34. A wireless communication method including receiving, by a wireless communication node, a buffer status report, an uplink (UL) BSR, and a response protocol data unit (PDU) PDU corresponding to a downlink (DL) from a wireless communication terminal. A wireless communication method.

35. The BSR is a DL logical channel (LC), identifier (ID), or DL LC priority related to the UL response PDU, including at least one of the DL PDU response indications related to the UL response PDU, or, The wireless communication method according to claim 34, wherein 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 includes at least one of system frame number information, slot information, or symbol information.

37. A wireless communication method, comprising receiving, by a wireless communication node, from a first wireless communication terminal, a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal. Wireless communication method.

38. The first PDU includes an identifier (ID) of the second wireless communication terminal, information of the second PDU, quality of service (QoS) related to the first PDU, flow ID, logical channel (LC) ID, or LC priority, or a PDU response instruction related to the first PDU, and the wireless communication method according to claim 37 includes at least one of them.

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, slot information, or symbol information.

40. A wireless communication method, comprising receiving, by a node in a core network (CN), from a wireless communication node, a reflective quality of service (QoS) instruction or a proactive QoS update request, wherein the reflective QoS instruction or the proactive QoS update request includes one or more sets of implied QoS support information. Wireless communication method.

41. The wireless communication method according to claim 40, wherein the implied QoS support information includes at least one of the following parameter types, namely, an implied QoS parameter value, an implied priority level of a QoS flow, an implied mapping between application data and a QoS flow, an implied paging strategy, user equipment, UE, mobility information, artificial intelligence related information, machine learning related information, network usage awareness, network computing ability, or UE positioning related information.

42. The implied QoS support information transmitted to the CN includes the following parameters, namely, the maximum aggregated bit rate for each cell preferred or permitted by the wireless communication node, the maximum bit rate for each carried QoS flow preferred or permitted by the wireless communication node. The maximum aggregated bitrate for each protocol data unit (PDU) session preferred or permitted by the wireless communication node A downlink (DL) PDU transmission time offset used to indicate to the CN to transmit a PDU session having a PDU of a QoS flow or a time delay offset or a time advance offset, wherein the DL PDU transmission time offset is relative to at least one of a current transmission start time, a current transmission end time, or a current transmission timing opportunity, the DL PDU transmission time offset A DL PDU arrival time used to instruct the CN to transmit a PDU of the QoS flow or PDU session so as to guarantee that the PDU arrives at the wireless communication node based on the DL PDU arrival time, the DL PDU arrival time The maximum packet size preferred or supported by the wireless communication node The application coding data rate preferred by the wireless communication node The CN packet delay budget (PDB) detected by the wireless communication node and used by the wireless communication node to determine a DL data transmission opportunity The CN packet delay budget (PDB) headroom detected by the wireless communication node and used by the wireless communication node to determine a DL data transmission opportunity The bit error rate (BER) detected by the wireless communication node The packet error rate (PER) detected by the wireless communication node Network node load information Network node self-computation ability headroom Computing ability headroom requirements for the core network or cloud native Uu time synchronization error budget Uu packet delay budget Uu packet delay budget headroom The duration, or, of a service that is preferred and used and used by the wireless communication node to determine the DL data transmission opportunity The wireless communication method according to claim 40 or 41, comprising at least one of a start time that is preferred and triggered by the service and used by the wireless communication node to determine the DL data transmission opportunity

43. Receiving, by a wireless communication terminal, from a wireless communication node, a reflected quality of service (QoS) indication or a proactive QoS update request The reflected QoS indication or the leading QoS update request includes one or more sets of the suggested QoS support information. Wireless communication method.

44. The wireless communication method according to claim 43, wherein the suggested QoS support information includes at least one of the following parameter types, namely, a suggested QoS parameter value, a priority level of a suggested QoS flow, a suggested mapping between application data and a QoS flow, a suggested paging strategy, a user equipment, a UE, mobility information, artificial intelligence related information, machine learning related information, network usage recognition, network computing ability, or UE positioning related information.

45. The suggested QoS support information transmitted to the wireless communication terminal is the following parameters, namely, The maximum aggregated bit rate for each UE preferred or permitted by the wireless communication node. The maximum aggregated bit rate for each DRB preferred or permitted by the wireless communication node. The maximum aggregated bit rate for each logical channel preferred or permitted by the wireless communication node. The maximum aggregated bit rate for each logical channel group preferred or permitted by the wireless communication node. The application encoded data rate preferred by the wireless communication node. An uplink (UL) PDU transmission time offset used to indicate to the wireless communication terminal to transmit the PDU of the DRB or logical channel using a time delay offset or a time advance offset, wherein the UL PDU transmission time offset is relative to at least one of the current transmission start time, the current transmission end time, or the current transmission timing opportunity. The UL PDU transmission time used to indicate to the wireless communication terminal to transmit the PDU of the DRB or logical channel in order to ensure that the PDU is transmitted based on the indicated transmission time. The BER detected by the wireless communication node and used by the wireless communication terminal to adjust at least one of the coding rate or the transmission power. The PER detected by the wireless communication node and used by the wireless communication terminal to adjust at least one of the coding rate or the transmission power. Network node load information. Network node self-computing ability headroom. Computing power headroom requirements for core network or cloud native, Uu time synchronization error budget, Uu packet delay budget, Uu packet delay budget headroom, Duration, or, a service is preferably used and the wireless communication terminal is used to determine a UL data transmission opportunity, The wireless communication method according to claim 43 or 44, comprising at least one of: a start time at which the service is preferably triggered and the wireless communication terminal is used to determine a UL service start time or the UL data transmission opportunity.

46. A wireless communication method, comprising transmitting a buffer size indication from a wireless communication terminal to a wireless communication node.

47. The buffer size indication is A specific buffer status report (BSR) format indicating that the buffer size is the same as the latest reported buffer size, A specific BSR media access control (MAC) header with a new logical channel (LC) identifier (ID) indicating that the buffer size is the same as the latest reported buffer size for a logical channel, logical channel group, or data radio bearer DRB, A specific BSR media access control (MAC) header with a new logical channel (LC) identifier (ID) indicating that the buffer size is the same as the latest transport size transmitted for a logical channel, logical channel group, or DRB, or The wireless communication method according to claim 46, comprising at least one of: uplink control information indicating that the buffer size is the same as the latest transport size transmitted for a logical channel, logical channel group, or DRB.

48. Receiving, by a wireless communication terminal, an intermittent reception (C-DRX) configuration from a wireless communication node; and Performing communication using a plurality of C-DRX patterns for each cell group, each data radio bearer, each DRB, or each logical channel according to the C-DRX configuration, between the wireless communication terminal and the wireless communication node.

49. The wireless communication method according to claim 48, wherein each C-DRX configuration includes a C-DRX index or C-DRX identification information used to identify the C-DRX configuration.

50. ​ ​ The wireless communication method according to claim 48, wherein the C-DRX index or C-DRX identification information of each C-DRX configuration is indicated by the order of the C-DRX configurations in the sequence.

51. The wireless communication method according to any one of claims 48 to 50, wherein the wireless communication node transmits a request to the wireless communication terminal using the C-DRX index or C-DRX identification information to change, delete, activate, or deactivate one of the C-DRX configurations corresponding to the C-DRX index or the C-DRX identification information.

52. A wireless communication method including transmitting, by a wireless communication terminal, a buffer status report (BSR) for an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU to a wireless communication node. Wireless communication method.

53. The BSR includes at least one of a DL logical channel (LC), an identifier (ID), or a DL LC priority related to the UL response PDU, or the wireless communication method according to claim 52, wherein related DL PDU information includes at least one of a PDU sequence number (SN) or PDU time domain information.

54.

55. 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, slot information, or symbol information.

56. A wireless communication method including transmitting, by a first wireless communication terminal, a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal to a wireless communication node. Wireless communication method.

57. The first PDU includes at least one of an identifier (ID) of the second wireless communication terminal, information of the second PDU, a quality of service (QoS), a flow ID, a logical channel (LC) ID, or an LC priority related to the first PDU, or a PDU response indication related to the first PDU.

58. 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, slot information, or symbol information.

59. A communication unit, A processor configured to receive a Protocol Data Unit (PDU) including PDU set information from an upper layer and to identify a PDU set of the PDU and a PDU set time sequence of the PDU set, wherein the PDU is scheduled for transmission via a Uu interface according to at least one of the PDU set or the PDU set time sequence, and the upper 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 (Xn-U) interface, user data from a Non-Access Stratum (NAS), and user data of a QoS flow. A wireless communication node.

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

60. A communication unit and A processor configured to transmit a Reflective Quality of Service (QoS) indication or a Proactive QoS update request to a core network (CN) or a wireless communication terminal, wherein the Reflective QoS indication or the Proactive QoS update request includes one or more sets of implied QoS support information. A wireless communication node.

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

62. A communication unit and A processor configured to receive a buffer size indication from a wireless communication terminal. A wireless communication node.

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

64. A communication unit and A processor configured to transmit an RRC_Connected state discontinuous reception (C-DRX) configuration to a wireless communication terminal and to perform communication with the wireless communication terminal using a plurality of C-DRX patterns for each cell group, each data radio bearer, each DRB, or each logical channel according to the C-DRX configuration. A wireless communication node.

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

66. A communication unit, a processor configured to receive from a wireless communication terminal a buffer status report (BSR) of an uplink (UL) response protocol data unit (PDU) corresponding to a downlink (DL) PDU, a wireless communication node.

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

68. A communication unit, a processor configured to receive from a first wireless communication terminal a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal, a wireless communication node.

69. The wireless communication node according to claim 68, wherein the processor is further configured to execute the wireless communication method according to claim 38 or 39.

70. A communication unit, a processor configured to receive from a wireless communication node a reflected quality of service (QoS) indication or a proactive QoS update request, wherein the reflected QoS indication or the proactive QoS update request includes one or more sets of suggested QoS support information, a communication node.

71. The communication node according to claim 70, wherein the processor is further configured to execute the wireless communication method according to claim 41 or 42.

72. A communication unit, a processor configured to receive from a wireless communication node a reflected quality of service (QoS) indication or a proactive QoS update request, wherein the reflected QoS indication or the proactive QoS update request includes one or more sets of suggested QoS support information, a wireless communication terminal.

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

74. A communication unit, a processor configured to transmit a buffer size indication to a wireless communication node, a wireless communication terminal.

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 communication unit, configured to receive an intermittent reception (C-DRX) configuration in the RRC_Connected state, and configured to perform communication with a plurality of C-DRX patterns for each cell group, for each data radio bearer, for each DRB, or for each logical channel with a wireless communication terminal according to the C-DRX configuration, a processor, A wireless communication terminal. **Claim 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. **Claim 78** A communication unit, a processor configured to transmit a buffer status report (BSR) of an uplink (UL) protocol data unit (PDU) corresponding to a downlink (DL) PDU to a wireless communication node, A wireless communication terminal. **Claim 79** The wireless communication terminal according to claim 78, wherein the processor is further configured to execute the wireless communication method according to claim 53 or 54. **Claim 80** A communication unit, a processor configured to transmit a first protocol data unit (PDU) corresponding to a second PDU of a second wireless communication terminal to a wireless communication node, A wireless communication terminal. **Claim 81** The wireless communication terminal according to claim 42, wherein the processor is further configured to execute the wireless communication method according to claim 56 or 57. **Claim 82** A computer program product comprising computer-readable program media code stored therein, wherein when the code is executed by a processor, the processor is caused to execute the wireless communication method according to any one of claims 1 to 39.

Images