Method and apparatus for delayed status reporting in wireless network

Abstract

A method performed by a UE for delayed status report (DSR) is provided. The method receives configuration information related to a logical channel group (LCG) from a BS. The method generates a DSR medium access control (MAC) control element (CE), the control element including a first field indicating a buffer size of the LCG, and transmits the DSR MAC CE to the BS. The buffer size indicates a total amount of latency critical data for the LCG. The delay key data of the LCG comprises a first packet data convergence protocol PDCP service data unit SDU and a second PDCP SDU belonging to a protocol data unit PDU set. The remaining time value of the first discard timer of the first PDCP SDU is smaller than a time threshold value related to the LCG, the PDU set comprises at least one PDCP SDU, and the remaining time value of the second discard timer of the PDCP SDU is smaller than the time threshold value.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This disclosure claims the benefit of and priority to U.S. Provisional Patent Application Serial No. 63 / 586,194, filed on September 28, 2023, and entitled “DELAY STATUS REPORTING OPERATIONS FOR XR,” the contents of which are incorporated herein by reference in their entirety. Technical Field

[0002] The present disclosure relates to wireless communications, and more particularly, to a method for delay status reporting (DSR) in a user equipment (UE), a base station (BS), and a wireless communication network. Background Art

[0003] Various efforts have been made to improve cellular wireless communication systems such as the fifth generation (5G) by increasing data rates, latency, reliability, and mobility. th 5G NR systems are designed to provide flexibility and configurability to optimize network services and types to accommodate a variety of use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). However, as the demand for wireless access continues to grow, the next generation of wireless communication systems requires further improvements, such as improved DSR procedures. Summary of the invention

[0004] The present disclosure relates to a UE, a BS, and a method for DSR in a wireless communication network.

[0005] In a first aspect of the present application, a method for DSR performed by a UE is provided. The method includes: receiving configuration information related to a logical channel group LCG from a base station BS through radio resource control RRC signaling; triggering a DSR process; generating a DSR medium access control MAC control element CE, the DSR MAC CE including a first field for indicating a buffer size of the LCG; and sending the DSR MAC CE to the BS. The buffer size indicates the total amount of delay-critical data of the LCG. The delay-critical data of the LCG includes: a first packet data convergence protocol PDCP service data unit SDU, the remaining time value of the first discard timer of the first PDCP SDU is less than the time threshold related to the LCG; and a second PDCP SDU belonging to a protocol data unit PDU set, the PDU set including at least one PDCP SDU, the remaining time value of the second discard timer of the at least one PDCP SDU is less than the time threshold.

[0006] In some implementations of the first aspect, the method further includes: receiving the time threshold related to the LCG from the BS through the RRC signaling.

[0007] In some implementations of the first aspect, triggering the DSR process includes: triggering the DSR process when it is determined that the remaining time value of the discard timer associated with the PDCP SDU belonging to the LCG is less than the time threshold and no DSR process is triggered.

[0008] In some implementations of the first aspect, the method further includes: determining a buffer size of the LCG according to a first predefined table or a second predefined table.

[0009] In some implementations of the first aspect, the first predefined table is used for extended reality XR service.

[0010] In some embodiments of the first aspect, determining the buffer size of the LCG includes: determining the buffer size of the LCG based on the first predefined table in response to a table indication received from the BS via the RRC signaling; and determining the buffer size of the LCG based on the second predefined table when the table indication is not received from the BS.

[0011] In some implementations of the first aspect, the DSR MAC CE further includes a second field, where the second field is used to indicate a minimum remaining time for delaying critical data of the LCG.

[0012] In some implementations of the first aspect, the method further includes: sending a scheduling request SR to the BS, where the SR is used to request uplink resources for transmitting the DSR MAC CE.

[0013] In a second aspect of the present application, a UE for DSR is provided. The UE includes: at least one processor; and at least one non-temporary computer-readable medium, coupled to the at least one processor and storing one or more computer-executable instructions. When the one or more computer-executable instructions are executed by the at least one processor, the UE: receives configuration information related to a logical channel group LCG from a base station BS through radio resource control RRC signaling; triggers a DSR process; generates a DSR medium access control MAC control element CE, the DSR MAC CE includes a first field for indicating a buffer size of the LCG; and sends the DSR MAC CE to the BS. The buffer size indicates the total amount of delay-critical data of the LCG. The delay-critical data of the LCG includes: a first packet data convergence protocol PDCP service data unit SDU, the remaining time value of the first discard timer of the first PDCP SDU is less than a time threshold related to the LCG; and a second PDCP SDU belonging to a protocol data unit PDU set, the PDU set including at least one PDCP SDU, the remaining time value of the second discard timer of the at least one PDCP SDU is less than the time threshold.

[0014] In a third aspect of the present application, a BS for configuring DSR is provided. The BS includes: at least one processor; and at least one non-temporary computer-readable medium, the at least one non-temporary computer-readable medium is coupled to the at least one processor and stores one or more computer-executable instructions, when the one or more computer-executable instructions are executed by the at least one processor, the BS: transmits configuration information related to a logical channel group LCG to a user equipment UE through radio resource control RRC signaling; and receives a DSR medium access control MAC control element CE from the UE, wherein the DSR MAC CE includes a first field for indicating a buffer size of the LCG. The buffer size indicates the total amount of delay-critical data of the LCG. The delay-critical data of the LCG includes: a first packet data convergence protocol PDCP service data unit SDU, the remaining time value of the first discard timer of the first PDCP SDU is less than a time threshold related to the LCG; and a second PDCP SDU belonging to a protocol data unit PDU set, the PDU set including at least one PDCP SDU, the remaining time value of the second discard timer of the at least one PDCP SDU is less than the time threshold. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Various aspects of the present disclosure can be best understood through the following detailed disclosure when reading the accompanying drawings. Various features are not drawn to scale. For clarity of discussion, the size of various features may be arbitrarily increased or reduced.

[0016] Figure 1 is a timing diagram of a PDU set based discard operation according to an example implementation of the present disclosure.

[0017] Figure 2 is a timing diagram of different DSR operations according to an example embodiment of the present disclosure.

[0018] Figure 3 is a timing diagram of a discard timer initialization according to an example implementation of the present disclosure.

[0019] Figure 4 is a flowchart of a method / process performed by a UE for DSR according to an example embodiment of the present disclosure.

[0020] Figure 5 is a flowchart of a method / process performed by a BS for configuring DSR according to an example embodiment of the present disclosure.

[0021] Figure 6 is a block diagram of a node for wireless communication according to an example implementation of the present disclosure. DETAILED DESCRIPTION

[0022] Some abbreviations used in this disclosure include: Third Generation Partnership Project (3 rd Generation Partnership Project (3GPP) The fifth generation (5 th Generation, 5G) Acknowledgment (ACK) Augmented Reality (AR) Base Station (BS) Buffer Status Report (BSR) Bandwidth Part (BWP) Cell RNTI (C-RNTI) Carrier Aggregation (CA) Contention Based Random Access (CBRA) Component Carrier (CC) Contention Free Random Access (CFRA) Configured Grant (CG) Conditional Handover (CHO) Cyclic Prefix (CP) Cyclic Redundancy Check (CRC) Configured Scheduling RNTI (CS-RNTI) Channel State Information (CSI) Channel State Information Reference Signal (CSI-RS) Dual Connectivity (DC) Downlink Control Information (DCI) Downlink (DL) Demodulation Reference Signal (DM-RS) Delay Status Reporting (DSR) Data Radio Bearer (DRB) Discontinuous Reception (DRX) Discontinuous Transmission (DTX) Evolved Universal Terrestrial Radio Access (E-UTRA) Extended Logical Channel ID (eLCID) Frequency Division Duplex (FDD) Frequency Range (FR) General Packet Radio Service (GPRS) GPRS Tunnelling Protocol for User Plane (GTP-U) Hybrid Automatic Repeat Request (HARQ) HARQ Acknowledgement (HARQ-ACK) Handover (HO) Identifier (ID) Information Element (IE) Layer 1 / Layer 2 / Layer 3 (L1 / L2 / L3) Logical Channel Group (LCG) Logical Channel ID (LCID) Logical Channel Prioritization (LCP) Long Term Evolution (LTE) Medium Access Control (MAC) MAC Control Element (MAC CE) Master Cell Group (MCG) Modulation and Coding Scheme (MCS) Master Node (MN) Non Access Stratum (NAS) Network Energy Saving (NES) Next Generation RAN (NG-RAN) New Radio (NR) Normal Uplink (NUL) Network (NW) Non-Zero Power (NZP) Orthogonal Frequency Division Multiplexing (OFDM) Primary Cell (PCell) Physical Cell Identifier (PCI) Packet Delay Budget (PDB) Physical Downlink Control Channel (PDCCH) Packet Data Convergence Protocol (PDCP) Physical Downlink Shared Channel (PDSCH) Protocol Data Unit (PDU) Packet Error Rate (PER) Physical (layer) (Physical (layer), PHY) Physical Random Access Channel (PRACH) Primary SCG Cell (PSCell) PDU Set Delay Budget (PSDB) PDU Set Error Rate (PSER) PDU Set Importance (PSI) PDU Set Integrated Handling Information (PSIHI)Physical Uplink Control Channel (PUCCH)Physical Uplink Shared Channel (PUSCH) Quasi Co-Location (QCL) Quality of Service (QoS) Random Access (RA) Random Access Channel (RACH) Radio Access Network (RAN) Random Access Response (RAR) Release (Rel) Radio Frequency (RF) Radio Link Control (RLC) Radio Link Failure (RLF) Radio Network Temporary Identifier (RNTI) Radio Resource Control (RRC) Reference Signal (RS) Reference Signal Received Power (RSRP) Reception (Rx) Secondary Cell (SCell) Secondary Cell Group (SCG) Subcarrier Spacing (SCS) Spatial Division Multiplexing (SDM) Service Data Unit (SDU) System Frame Number (SFN) System Information (SI) System Information Block (SIB) Sidelink (SL) Session Management Function (SMF) Secondary Node (SN) Special Cell (SpCell) Semi-Persistent Scheduling (SPS) Scheduling Request (SR) Sounding Reference Signal (SRS) Synchronization Signal Block (SSB) Supplementary Uplink (SUL) Timing Advance (TA) Timing Advance Group (TAG) Transport Block (TB) Transmission Configuration Indicator (TCI) Time Division Duplex (TDD) Transmission Reception Point (TRP) Technical Report (TR) Technical Specification (TS) Transmission (Tx) User Equipment (UE) Uplink (UL) Uplink Shared Channel (UL-SCH) User Plane Function (UPF) Ultra-Reliable and Low-Latency Communication (URLLC) Vehicle to Everything (V2X) eXtended Reality (XR)

[0023] The following contains specific information related to the embodiments of the present disclosure. The accompanying drawings and their accompanying detailed disclosure are only for the embodiments. However, the present disclosure is not limited to these embodiments. Other variations and embodiments of the present disclosure will be obvious to those skilled in the art.

[0024] Unless otherwise noted, similar or corresponding components in the drawings may be indicated by similar or corresponding reference numerals.In addition, the drawings and illustrations in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0025] For the purpose of consistency and ease of understanding, similar features are identified in the drawings by the same reference numerals (although not shown in some examples). However, features in different embodiments may differ in other aspects and should not be narrowly limited to what is shown in the drawings.

[0026] The phrases "one embodiment", "an embodiment", "an example embodiment", "various embodiments", "some embodiments", "embodiments of the present application", etc. may indicate that the embodiments of the present application described herein may include specific features, structures or characteristics, but not every possible embodiment of the present application necessarily includes specific features, structures or characteristics. In addition, repeated use of the phrases "in some embodiments", "in an example embodiment", "an embodiment" does not necessarily refer to the same embodiment, although they may refer to the same embodiment. In addition, the use of any phrase "embodiment" related to "the present application" does not mean that all embodiments of the present application must include specific features, structures or characteristics, but should be understood as "at least some embodiments of the present application" include the specific features, structures or characteristics. The term "coupled" is defined as connected, whether directly or indirectly through intermediate components, and is not necessarily limited to physical connections. The term "include" when used means "including but not necessarily limited to", and specifically indicates an open inclusion relationship or affiliation in the described combination, group, series or equivalent.

[0027] The expression "at least one of A, B, and C" or "at least one of the following: A, B, and C" means "only A, or only B, or only C, or any combination of A, B, and C". The terms "system" and "network" may be used interchangeably herein. The term "and / or" is merely used herein to describe the association relationship of associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate: A exists alone, A and B exist at the same time, or B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0028] For the purpose of explanation rather than limitation, specific details (such as functional entities, technologies, protocols, standards, etc.) are set forth to provide an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, architectures, etc. is omitted to avoid obscuring the present disclosure with unnecessary details.

[0029] Those skilled in the art will directly recognize that any one or more network functions or algorithms described in this disclosure may be implemented by hardware, software, or a combination of software and hardware. The disclosed functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof.

[0030] Software implementations may include computer executable instructions stored on a computer readable medium such as a memory or other type of storage device. One or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and execute one or more network functions or algorithms disclosed.

[0031] The microprocessor or general-purpose computer may include an application-specific integrated circuit (ASIC), a programmable logic array, and / or one or more digital signal processors (DSP). Although some of the embodiments of the present disclosure are software for installation and execution on computer hardware, alternative exemplary embodiments implemented as firmware, hardware, or a combination of hardware and software are fully within the scope of the present disclosure. Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), cassettes, tapes, disk storage devices, or any other equivalent medium capable of storing computer-readable instructions.

[0032] A radio communication network architecture (such as a Long Term Evolution (LTE) system, an advanced LTE (LTE-Advanced, LTE-A) system, an advanced LTE Pro system or a 5G NR radio access network (Radio Access Network, RAN) typically includes at least one base station (Base Station, BS), at least one user equipment (UE) and one or more optional network components that provide connections within the network. The UE can communicate with a network (such as a core network (Core Network, CN), an evolved packet core (Evolved Packet Core, EPC) network, an evolved universal terrestrial radio access network (Evolved Universal Terrestrial RAN, E-UTRAN), a 5G core (5G Core, 5GC) or the Internet) through a RAN established by one or more BSs.

[0033] UE may include but is not limited to a mobile station, a mobile terminal or device, a user communication radio terminal. For example, a UE may be a portable radio device, including but not limited to a mobile phone, a tablet, a wearable device, a sensor, a vehicle or a personal digital assistant (PDA) with wireless communication capabilities. A UE is configured to receive signals over an air interface and transmit signals to one or more cells in a RAN.

[0034] The BS may be configured to provide communication services according to at least one of Radio Access Technology (RAT) such as: Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, commonly referred to as 2G), Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS, commonly referred to as 3G) based on basic Wideband-Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE) connected to 5GC, NR (commonly referred to as 5G) and / or LTE-A Pro. However, the scope of the present disclosure should not be limited to the above-mentioned protocols.

[0035] The BS may include, but is not limited to, a Node B (NB) in UMTS, an evolved Node B (eNB) in LTE or LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in GSM / GERAN, a next generation eNB (ng-eNB) in an E-UTRA BS connected to a 5GC, a next generation Node B (gNB) in a 5G-RAN, and any other device capable of controlling radio communications and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. Although gNB is used as an example in some embodiments of the present disclosure, it should be noted that the disclosed embodiments may also be applied to other types of base stations.

[0036] The BS is operable to provide radio coverage to a specific geographical area using multiple cells included in the RAN. The BS can support the operation of the cells. Each cell is operable to provide service to at least one UE within its radio coverage.

[0037] Each cell (usually referred to as a serving cell) can provide services to one or more UEs within the radio coverage so that each cell schedules downlink DL (and optional uplink UL resources) to at least one UE within its radio coverage for DL ​​(and optional UL data packet transmission from the UE). A BS can communicate with one or more UEs in a radio communication system through multiple cells.

[0038] The cell may allocate sidelink (SL) resources to support proximity service (ProSe) or vehicle to everything (V2X) services. Each cell may have a coverage area that overlaps with other cells.

[0039] In the case of Multi-RAT Dual Connectivity (MR-DC), the master cell of the Master Cell Group (MCG) or the Secondary Cell Group (SCG) can be called a Special Cell (SpCell). The Primary Cell (PCell) can include the SpCell of the MCG. The Primary SCG Cell (PSCell) can include the SpCell of the SCG. The MCG can include a group of service cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCell). The SCG can include a group of service cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0040] As discussed above, the frame structure of NR can support flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), Ultra-Reliable and Low-Latency Communication (URLLC), while meeting high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology agreed in the 3rd Generation Partnership Project 3GPP can be used as a benchmark for the NR waveform. Scalable OFDM parameter sets, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used.

[0041] Two coding schemes can be considered for NR: specifically Low-Density Parity-Check (LDPC) codes and polar codes. Coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0042] At least DL transmission data, protection period and UL transmission data should be included in the transmission time interval (TTI) of a single NR frame. The parts of DL transmission data, protection period and UL transmission data should be configured dynamically based on, for example, the NR network. Sidelink resources can also be provided in NR frames to support ProSe services or V2X services.

[0043] Any two or more of the following paragraphs, (sub)items, points, actions, behaviors, terms or claims described in this disclosure may be logically, reasonably and appropriately combined to form a specific method.

[0044] Any sentence, paragraph, (sub)item, point, action, behavior, term or claim described in this disclosure may be implemented independently and separately to form a specific method.

[0045] Dependencies in the present disclosure, such as “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., are only possible examples and do not limit the specific method.

[0046] In some embodiments, all designs / embodiments / implementations described in this disclosure are not limited to application to addressing the issues discussed in this disclosure. For example, the described embodiments can be applied to address other issues present in the RAN of a wireless communication system. In some embodiments, all numbers listed in the designs / embodiments / implementations described in this disclosure are merely examples, for example, to illustrate how to perform the described methods.

[0047] The DL RRC message in the present disclosure may include, but is not limited to, an RRC reconfiguration message (RRCReconfiguration), an RRC recovery message (RRCResume), an RRC reestablishment message (RRCReestablishment), an RRC setup message (RRCSetup) or any other DL unicast RRC message.

[0048] In some embodiments, “a specific configuration is configured for each UE” or “a specific configuration is configured for the UE” described in the present disclosure may mean a specific configuration configured within a DL RRC message, but is not limited thereto.

[0049] In some embodiments, the "specific configuration is configured for each cell group" or "specific configuration is configured for the cell group" described in the present disclosure may refer to a specific configuration configured in the cell group configuration (e.g., CellGroupConfig, MAC-CellGroupConfig, or PhysicalCellGroupConfig IE), but is not limited to this.

[0050] In some embodiments, the “specific configuration configured for each serving cell” or “specific configuration configured for a serving cell” described in the present disclosure may refer to a specific configuration configured in the serving cell configuration, but is not limited to this (e.g., ServingCellConfigCommon, ServingCellConfig, PUSCH-ServingCellConfig, or PDSCH-ServingCellConfig IE).

[0051] In some embodiments, "a specific configuration is for each UL BWP or for each BWP configuration" or "a specific configuration is for UL BWP or for BWP configuration" described in the present disclosure may mean a specific configuration configured in one of the following IEs, but is not limited to: BWP-Uplink, BWP-UplinkDedicated, BWP-UplinkCommon, PUSCH-ConfigCommon, and PUSCH-Config.

[0052] In some embodiments, the "specific configuration is for each DL BWP or for each BWP configuration" or "specific configuration is for DL ​​BWP or for BWP configuration" described in the present disclosure may mean a specific configuration configured in one of the following IEs, but is not limited to: BWP-Downlink, BWP-DownlinkDedicated, BWP-DownlinkCommon, PDSCH-ConfigCommon, and PDSCH-Config IE.

[0053] In some embodiments, a PDSCH / PDSCH / PUSCH transmission may span multiple symbols in the time domain. The duration of a PDSCH / PDSCH / PUSCH (transmission) may mean a time interval starting from the beginning of the first symbol of a PDSCH / PDSCH / PUSCH (transmission) and ending at the end of the last symbol of a PDSCH / PDSCH / PUSCH (transmission).

[0054] The term "A and / or B" in the present disclosure means "A", "B", or "A and B". The term "A and / or B and / or C" in the present disclosure means "A", "B", "C", "A and B", "A and C", "B and C", or "A and B and C". The term "A / B" in the present disclosure means "A" or "B".

[0055] The term "(specific) PHY layer signaling" may refer to a specific format of DCI, a specific field of DCI, a specific field of DCI with the field set to a specific value, and / or DCI with CRC bits scrambled with a specific RNTI.

[0056] In the present disclosure, "MAC timer" may include but is not limited to a timer configured by a base station through RRC signaling. The UE may configure an initial value of the timer, and the unit of the value may include but is not limited to frame / subframe / millisecond / sub-millisecond / time slot / symbol. The timer may be started and / or restarted by the UE (e.g., by a MAC entity of the UE). When certain conditions are met, the timer may be started and / or restarted by the UE (e.g., by a MAC entity of the UE).

[0057] Examples of some selected terms in this disclosure are provided below.

[0058] BWP: A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP), and bandwidth adaptation (BA) can be achieved by configuring a BWP for the UE and indicating to the UE which configured BWP is currently the active BWP. To enable BA on PCell, the BS (e.g., gNB) configures UL and DL BWPs for the UE. To enable BA on SCell, the BS configures one or more DL BWPs for the UE when CA is deployed. It should be noted that there may be no BWP in the UL. For PCell, the initial BWP is the BWP used for initial access. For SCell, the initial BWP is the BWP configured for the UE to run after the SCell is activated. The first active uplink BWP can be configured for the UE via the firstActiveUplinkBWP IE. If the first active uplink BWP is configured for the SpCell, the firstActiveUplinkBWP IE field may include the ID of the UL BWP to be activated when performing RRC (re-)configuration. If such a field is not present, the RRC (re-)configuration may not force a BWP switch. If the first active uplink BWP is configured for the SCell, the firstActiveUplinkBWP IE field may include the ID of the uplink bandwidth portion to be used when the SCell's MAC is activated.

[0059] Cell: A wireless network object that can be uniquely identified by a user equipment through a (cell) identity broadcast from a certain geographical area, such as a UTRAN access point. A cell can be in FDD mode or TDD mode.

[0060] Data Burst: A group of multiple PDUs generated and sent by an application in a short period of time as defined in 3GPP TS23.501.

[0061] Field: The content of an information element can be called a field.

[0062] Information Element: A structure element containing single or multiple fields can be called an information element.

[0063] PDCCH: In the downlink, the base station (e.g. gNB) can dynamically allocate resources to the UE via at least C-RNTI / MCS-C-RNTI / CS-RNTI on PDCCH. The UE always monitors PDCCH to find possible allocations when downlink reception is enabled (e.g., activity controlled by DRX when configured). When CA is configured, the same C-RNTI can be applied to all serving cells.

[0064] PDCP data volume: The amount of data available for transmission in a PDCP entity.

[0065] PDSCH / PUSCH: PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH.

[0066] PDU Set: A set of one or more PDUs carrying the payload of an information unit generated at the application level as defined in 3GPP TS 23.501 (e.g., a frame or video segment for an XR service).

[0067] Primary cell: An MCG cell operating on a primary frequency and in which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure may be called a primary cell.

[0068] RLC data volume: The amount of data available for transmission in the RLC entity.

[0069] Secondary cell: For a UE configured with CA, a cell that provides additional radio resources on top of a specific cell may be called a secondary cell.

[0070] Serving cell: For a UE in RRC_CONNECTED state and without CA / DC configured, there is only one serving cell, the primary cell. For a UE in RRC_CONNECTED state and with CA / DC configured, the term "serving cell" is used to refer to a group of cells including a specific cell and all secondary cells.

[0071] Special Cell (SpCell): For dual connectivity operation, the term special cell may include the PCell of the MCG or the PSCell of the SCG. Otherwise, the term special cell may include the PCell.

[0072] Timing Advance Group: A group of service cells configured by RRC signaling, which use the same timing reference cell and the same timing advance value for cells with configured UL, can be called a timing advance group. The timing advance group of the SpCell including the MAC entity can be called the Primary Timing Advance Group (PTAG), while the term Secondary Timing Advance Group (STAG) can refer to other TAGs.

[0073] Timer: The PDCP / MAC entity may set one or more timers for different purposes, e.g., triggering one or more uplink signaling retransmissions or limiting one or more uplink signaling retransmission periods. Once started, a timer runs until it is stopped or expires, otherwise it does not run. If the timer is not running, it may be started, and if it is running, it may be restarted. A timer is always started or restarted from its initial value. The initial value may be (but not limited to) configured by the gNB via downlink RRC signaling, or may be a predefined value / predetermined value specified in some specification.

[0074] In NR, uplink BSR is introduced to support QoS-aware packet scheduling. Specifically, the uplink BSR may correspond to data buffered for a group of logical channels (e.g., LCG) in the UE. In addition, the uplink BSR may be transmitted via MAC signaling (e.g., via BSR MAC CE). When the BSR is triggered (e.g., when new UL data arrives at the UE's transmission buffer), the UE may transmit a scheduling request (SR) (e.g., when there are no available UL resources to transmit the BSR).

[0075] When UL resources are available for new transmission, the MAC SDUs belonging to one or more logical channels can be multiplexed into a transport block (TB) transmitted to the physical layer on the transport channel using a multiplexing and assembly process. More specifically, the Logical Channel Priority (LCP) process can be applied whenever a new transmission is performed. The UE can allocate UL resources to logical channels based on the results of the LCP process.

[0076] In addition, in order to meet the QoS requirements associated with the service, the UE may discard the PDCP SDU that violates the QoS requirements. The base station (e.g., gNB) may configure a discard timer for each PDCP entity for the UE, for example, through RRC signaling, and the PDCP entity may be associated with a radio bearer. The discard timer may be set in milliseconds (ms). The discard timer may be configured only for a data radio bearer (DRB). When the discard timer is configured for a (transmitting) PDCP entity, the PDCP entity may start a new timer for the corresponding PDCP SDU after receiving the SDU from the upper layer. When the discard timer of the PDCP SDU expires, or, for example, when the successful transmission of the PDCP SDU is confirmed by a PDCP status report, the (transmitting) PDCP entity may discard the PDCP SDU and the corresponding PDCP data PDU. If the corresponding PDCP data PDU has been submitted to the lower layer, the discard may also be indicated to the lower layer.

[0077] In XR services, the traffic can be modeled as a series of video frames arriving at the BS / UE based on the considered video frame rate and random jitter. More specifically, the XR application can generate / send multiple PDUs (e.g., a number of video frames or video fragments). A group of multiple PDUs can be further grouped into a PDU set, indicating the dependencies between the PDUs of the PDU set. In order to effectively schedule wireless resources for XR traffic, the BS / UE may need to be aware of the XR traffic (e.g., XR-Awareness), which can be achieved by enabling PDU set QoS flow processing. Due to the delay-sensitive nature of XR traffic, UL Delay Status Report (DSR) can be introduced to inform the BS of the delay status of the buffered data, which helps to improve uplink resource scheduling.

[0078] PDU Set QoS Flow Processing

[0079] XR-Awareness relies on QoS flows, PDU sets, data bursts, and traffic assistance information (e.g., as described in 3GPP TS 23.501). The SMF may provide the following PDU set QoS parameters to the BS as part of the QoS profile for the QoS flow. To implement PDU set-based QoS processing, at least one of the following PDU set QoS parameters may be provided:

[0080] PDU Set Delay Budget (PSDB): As defined in 3GPP TS23.501, the PSDB may include an upper bound on the duration between the reception time of the first PDU (at the UPF for DL, or at the UE for UL) and the time when all PDUs of the PDU set are successfully received (at the UE for DL, or at the UPF for UL). A QoS Flow may be associated with only one PSDB. The PSDB may apply to both DL and UL and may replace the PDB for a QoS Flow.

[0081] -PDU Set Error Rate (PSER): As defined in 3GPP TS23.501, the PSER may include an upper limit on the non-congestion related PDU set loss rate between the RAN and the UE. A QoS flow may be associated with only one PSER. The PSER may apply to both DL and UL and replaces the PER of a QoS flow.

[0082] - PDU Set Integrated Handling Information (PSIHI): PSIHI may indicate whether all PDUs in a PDU set are required for use by the application layer as defined in 3GPP TS 23.501.

[0083] A PDU set is considered successfully delivered only if all PDUs of the PDU set are successfully delivered. The PDU set QoS parameters may be common to all PDU sets in a QoS flow.

[0084] The UPF can identify the PDUs that belong to a PDU set and can indicate the following PDU set information in the GTP-U header to the BS:

[0085] PDU set sequence number;

[0086] Indication of the end PDU of a PDU set;

[0087] The PDU sequence number in the PDU set;

[0088] PDU set size in bytes;

[0089] PDU Set Importance (PSI): PSI identifies the relative importance of a PDU set relative to other PDU sets within the same QoS flow.

[0090] In the uplink, the UE may dynamically identify a PDU set, including the PDU set information and data bursts as described above. How this is done may depend on the implementation of the UE.

[0091] PDCP PDU set discard operation

[0092] When the UE / BS identifies, for example through the application layer, that the use of a PDU set requires all PDUs of the PDU set, once it is known that one PDU in the PDU set is lost, it can be regarded as that the application no longer needs the remaining PDUs of the PDU set, and, for example, a discard operation can be performed at the transmitter to release radio resources.

[0093] In the uplink, the UE can configure a PDU set-based discard operation for a specific DRB. When the PDU set-based discard operation is configured, when a PDU belonging to a PDU set is discarded due to the expiration of a discard timer (e.g., discardTimer), the UE can discard all data packets in the PDU set. In the uplink, the UE may need to dynamically identify that a PDU set includes a PSI and a data burst. How to do this may depend on the implementation of the UE. The UE can configure an indicator (e.g., pdu-SetDiscard) for each PDCP entity. If the indicator is set to true for the PDCP entity, the UE can perform a PDU set-based discard operation for the PDCP entity. For example, when the discardTimer of a PDCP SDU expires, if pdu-SetDiscard is configured, the sending PDCP will discard all PDCP SDUs and the corresponding PDCP data PDUs of the PDU set to which the PDCP SDU belongs; otherwise, the sending PDCP entity will discard the PDCP SDU and the corresponding PDCP data PDU.

[0094] Figure 11 is a timing diagram 100 of a PDU set based discard operation according to an example embodiment of the present disclosure. Figure 1 As shown, PDCP SDU#1 and PDCP SDU#2 belong to the same PDU set. The discard timer of PDCP SDU#1 expires at t1, and the discard timer of PDCP SDU#2 expires at t2. When the discard timer of PDCP SDU#1 expires at t1, the UE may discard the entire PDU set, including PDCP SDU#1 and PDCP SDU#2.

[0095] In case of congestion, PSI can be used for PDU set discard. For the uplink, dedicated downlink signaling can be used to trigger the PSI-based discard mechanism. More specifically, the UE can configure an indicator (e.g., psi-BasedDiscard) for each PDCP entity. If the indicator is configured, the UE can perform PSI-based discard operations for the corresponding PDCP entity. For example, when congestion occurs and / or congestion is indicated, if psi-BasedDiscard is configured, the sending PDCP entity can discard all PDCP SDUs belonging to the PDU set (whose PSI is less than a threshold) and the corresponding PDCP data PDUs. The threshold can be configured by the BS, for example, through RRC signaling.

[0096] Some embodiments of the present disclosure may adopt a delay status report of buffered data via a dedicated MAC CE (e.g., a DSR MAC CE). Generally, the DSR can be triggered based on one or more remaining time thresholds configured by the network. The content of the DSR may include the amount of data cached by each LCG (or the amount of emergency data cached in the relevant logical channel determined according to the time threshold) and delay information related to the cached data (e.g., remaining time). Therefore, the DSR process can be used to provide the delay status of UL data to the serving BS. Regarding the DSR process, the present disclosure will solve the following problems: conditions for DSR triggering and cancellation, enhancement of PDCP / RLC data amount calculation for DSR, and details of the DSR MAC CE.

[0097] DSR Configuration

[0098] To enable DSR operation (e.g., transmitting DSR to the serving BS), the UE may have a DSR configuration (e.g., LCG-DSR-Config) for each LCG configuration (e.g., by the BS through RRC signaling). The gNB may configure one or more logical channels belonging to the LCG, for example, through RRC signaling. In addition, the gNB may control the DSR operation by configuring a time threshold (e.g., remainingTimeThreshold) for the remaining time of UL data for triggering DSR of the LCG, where the time threshold may be included in the DSR configuration. Table 1 below shows an example DSR configuration according to an example embodiment of the present disclosure. Table 1

[0099] In some embodiments, if the UE is configured with a DSR configuration for an LCG, the UE may be allowed to trigger / transmit a DSR for the LCG, otherwise, the UE may not be allowed to trigger / transmit any DSR for the LCG. For example, there may be an indication in the DSR configuration to enable or disable the DSR operation of the relevant LCG. As another example, there may be an indication in the DSR configuration to enable (or set) the DSR operation of the relevant LCG. If there is no indication in the DSR configuration, the DSR operation of the relevant LCG may be disabled. In some embodiments, the UE may be configured with the DSR configuration of the LCG to perform the relevant DSR operation using an initial state (e.g., enabled or disabled) or a default / specified state (e.g., enabled or disabled). Thereafter, the BS may enable / disable the DSR operation of the relevant LCG, for example, through RRC signaling, MAC CE, or DCI.

[0100] In some embodiments, a single time threshold may be configured for one LCG. In other words, one LCG cannot be associated with multiple time thresholds. As an example, the UE may configure two LCGs, including LCG#1 and LCG#2, and the UE may also configure a first time threshold T1 for LCG#1 and a second time threshold T2 for LCG#2. As another example, the UE may configure two LCGs, including LCG#1 and LCG#2, and the UE may also configure the first time threshold T1 only for LCG#1. In this example, the UE may only perform DSR operations associated with LCG#1, and not perform DSR operations associated with LCG#2.

[0101] In some implementations, multiple time thresholds may be configured for each LCG. In other words, one LCG may be associated with multiple time thresholds. For example, the UE may configure a first time threshold T1 and a second time threshold T2 for LCG#1.

[0102] In some implementations, when multiple time thresholds are configured for an LCG, the UE may determine which time threshold to use to trigger the DSR for the LCG.

[0103] In some implementations, when multiple time thresholds are configured for an LCG, the BS may indicate to the UE via RRC / MAC / PHY signaling which time threshold is used to trigger the DSR of the LCG.

[0104] In some embodiments, two time thresholds may be configured for the same LCG, and one of the two time thresholds may be used for congestion conditions. For example, for LCG#1, a first time threshold T1 and a second time threshold T2 for congestion conditions may be configured for the UE. If the UE does not receive a congestion indication from the serving BS (or the UE receives a congestion relief indication), the UE may apply T1 to perform a DSR operation for LCG#1. If the UE receives a congestion indication from the serving BS, the UE may apply T2 to perform a DSR operation for LCG#1.

[0105] DSR Operation

[0106] Figure 2 2 is a timing diagram 200 of different DSR operations according to an example embodiment of the present disclosure. The DSR operation may include one or more of the following sub-processes:

[0107] The UE may configure a time threshold for the LCG. The UE may trigger one or more DSRs based on the time threshold (e.g., at t3 and t4).

[0108] For a triggered DSR, the UE may determine which type (eg, short / long / another type) of DSR to report, and may further determine the format and size of the DSR MAC CE to be transmitted.

[0109] For a DSR that has been triggered but not canceled, when UL-SCH resources are available for new transmission (e.g., when a UL grant is received at t5), the UE may determine whether the UL-SCH resources can accommodate the DSR MAC CE and its subheader (as a result of the LCP). If the determination is positive (e.g., the UL-SCH resources can accommodate the DSR MAC CE and its subheader), the UE may instruct the multiplexing and assembly process to generate the corresponding DSR MAC CE (e.g., at t6).

[0110] After the LCP process, the fields (e.g., buffer size field and remaining time field) in the generated DSR MAC CE may be determined according to the PDCP / RLC delay critical data amount calculation process, where the delay critical data may represent data whose delay budget (e.g., the remaining value of the discard timer) is less than the time threshold. In some embodiments, both logical channel #1 and logical channel #2 may belong to LCG#1 according to the configuration, and LCG#1 may be configured to perform a DSR process (or DSR operation). In the event that the remaining time of an SDU of logical channel #1 or logical channel #2 is less than (or equal to) the time threshold configured for LCG#1, the buffer size reported in the DSR MAC CE may include the total data amount of the PDCP / RLC delay critical data amount of logical channel #1 and the PDCP / RLC delay critical data amount of logical channel #2.

[0111] In some embodiments, depending on the configuration, both logical channel #1 and logical channel #2 may belong to LCG #1, and LCG #1 may be configured to perform a DSR process (or DSR operation). In the case where the remaining time of one SDU of logical channel #1 is less than (or equal to) the time threshold configured for LCG #1, but the remaining time of no SDU of logical channel #2 is less than (or equal to) the time threshold configured for LCG #1, the buffer size reported in the DSR MAC CE may include the amount of PDCP / RLC delay critical data of logical channel #1. That is, the amount of PDCP / RLC delay critical data of logical channel #2 may not be considered for reporting in the DSR MAC CE. The UE may send a corresponding MAC PDU including the DSR MAC CE at t7.

[0112] DSR Trigger

[0113] In some implementations, the UE may configure a discard timer for the (sending) PDCP entity, and the PDCP entity may start a new discard timer after receiving a (PDCP) SDU from upper layers.

[0114] In some implementations, the value of the new discard timer for the PDCP SDU may be set to the value of the configured discard timer.

[0115] In some implementations, the remaining time of a PDU set may be defined as the remaining value of a discard timer of a PDCP SDU corresponding to a PDU with a smallest sequence number in the PDU set.

[0116] In some implementations, the remaining time of a PDU set may be defined as the remaining value of the discard timer of the PDU with the smallest remaining value of the discard timer in the PDU set.

[0117] Figure 3 300 is a timing diagram of initialization of a discard timer according to an example embodiment of the present disclosure. In some embodiments, the value of a new discard timer for a PDCP SDU corresponding to a PDU in a PDU set may be set to the remaining value of a discard timer for a PDCP SDU corresponding to a PDU with a smallest sequence number in the PDU set. Figure 3 As shown, PDCP SDU#1 and PDCP SDU#2 are PDUs in the same PDU set. PDCP SDU#1 corresponds to the PDU with the smallest sequence number in the PDU set. When the PDCP entity receives PDCP SDU#1, the PDCP entity may start a new discard timer for PDCP SDU#1. Thereafter, when the PDCP entity receives PDCP SDU#2, the value of the new discard timer for PDCP SDU#2 may be set to the remaining value of the discard timer for PDCP SDU#1. In this way, the discard timer for PDCP SDU#1 and the discard timer for PDCP SDU#2 both expire at time t1, and the UE may discard the entire PDU set at time t1.

[0118] In some embodiments, the UE may set a discard timer for a (sending) PDCP entity. When the PDCP entity receives a PDCP SDU from an upper layer, if the PDCP SDU corresponds to the PDU with the smallest sequence number in the PDU set, the PDCP entity may start a new discard timer for the PDCP SDU. Otherwise, the PDCP entity may not start a new discard timer for the PDCP entity, and the discard timer of the PDCP entity may correspond to the discard timer of the PDCP SDU corresponding to the PDU with the smallest sequence number in the PDU set.

[0119] In order to determine whether DSR for LCG is needed / triggered, the BS may configure a time threshold associated with LCG for the UE (e.g., through RRC signaling). When the UE is configured with a time threshold associated with LCG by the BS, when the remaining time of the (PDCP / RLC) SDU belonging to the LCG becomes less than (or equal to) the time threshold, the UE may perform a DSR triggering operation, which triggers the DSR of the LCG.

[0120] In some embodiments, the DSR triggering operation may be performed by a (sending) PDCP entity. When the UE (e.g., via RRC signaling) configures a time threshold associated with an LCG, the PDCP entity associated with the LCH of the LCG may determine whether to trigger a DSR for the LCG based on the time threshold. More specifically, when the remaining value of a (running) discard timer associated with the PDCP SDU becomes less than (or equal to) the time threshold, the PDCP entity may trigger a DSR, and the triggered DSR with the remaining value may be indicated to the lower layer (e.g., the MAC layer). In some embodiments, the PDCP entity triggering a DSR may mean that the PDCP entity instructs the lower layer (e.g., the MAC layer) to trigger the DSR.

[0121] In some embodiments, if the remaining time of a PDU set becomes less than (or equal to) a time threshold, the PDCP entity may trigger a DSR. More specifically, when the remaining value of a discard timer associated with a PDCP SDU becomes less than (or equal to) the time threshold, if the PDCP SDU corresponds to a PDU with a minimum sequence number in the PDU set, the PDCP entity may trigger a DSR, and may indicate the triggered DSR (and / or related triggering information) to a lower layer (e.g., a MAC layer). The related triggering information may include at least one of the following: a PDU set ID that triggers the DSR, a sequence number of a PDCP SDU that triggers the DSR, and a remaining value of a discard timer of a PDU set (or PDCP SDU) that triggers the DSR.

[0122] In some embodiments, if the remaining time of the PDU set is less than (or equal to) a time threshold, the PDCP entity may trigger a DSR. More specifically, when the remaining value of a discard timer associated with one of the PDCP SDUs corresponding to the PDUs in the PDU set becomes less than (or equal to) the time threshold, the PDCP entity may trigger a DSR, and may indicate the triggered DSR (and / or associated trigger information) to a lower layer (e.g., a MAC layer). The associated trigger information may include at least one of a PDU set ID that triggers the DSR, a sequence number of a PDCP SDU that triggers the DSR, and a remaining value of a discard timer of a PDU set (or PDCP SDU) that triggers the DSR.

[0123] In some embodiments, when the remaining value of a discard timer associated with a first PDCP SDU corresponding to a first PDU in a PDU set is less than (or equal to) a time threshold, and there is an existing DSR triggered by a second PDCP SDU corresponding to a second PDU in the same PDU set, the PDCP entity may not trigger a DSR. When the remaining value of a discard timer associated with a first PDCP SDU (e.g., corresponding to the first PDU in the PDU set) is less than (or equal to) a time threshold, and there is no DSR triggered by a second PDCP SDU corresponding to the second PDU in the same PDU set, the PDCP entity may trigger a DSR, and may indicate the triggered DSR to a lower layer (e.g., a MAC layer). In some embodiments, a DSR may be triggered when the UE determines that the remaining time value of a discard timer associated with a PDCP SDU belonging to an LCG is less than a time threshold, and no DSR is triggered.

[0124] In some embodiments, when a DSR is triggered due to the remaining time of a PDCP SDU becoming less than a time threshold and the DSR is not cancelled, the PDCP entity may avoid triggering another DSR for the PDCP SDU. For example, even if the remaining time of the PDCP SDU continues to decrease and remains below the time threshold, the PDCP entity may not trigger another DSR for the PDCP SDU.

[0125] In some embodiments, the time threshold (value) may be indicated by a lower layer (e.g., MAC layer). If the time threshold is indicated, the PDCP entity may be allowed to trigger the DSR. If the time threshold is not indicated, the PDCP entity may not be allowed to trigger the DSR.

[0126] In some embodiments, the DSR triggering operation may be performed by a (sending) PDCP entity. Specifically, when a PDCP SDU is discarded, the PDCP entity may trigger a DSR. It should be noted that when a PDCP status report confirms that a PDCP SDU is successfully transmitted, the PDCP entity may discard the PDCP SDU and the corresponding PDCP data PDU.

[0127] In some embodiments, when the PDCP entity discards a first PDCP SDU corresponding to a first PDU in a PDU set, if a second PDCP SDU corresponding to a second PDU in the PDU set is not discarded and the remaining value of the discard timer of the second PDCP SDU is less than (or equal to) a time threshold, the PDCP entity may trigger a DSR, and the triggered DSR with the remaining value (and / or related triggering information) may be indicated to a lower layer (e.g., a MAC layer). The related triggering information may include a PDU set ID of the triggered DSR and / or a sequence number of the PDCP SDU of the triggered DSR.

[0128] In some implementations, when the PDCP entity discards the first PDCP SDU corresponding to the first PDU in the PDU set, and there is a second PDCP SDU corresponding to the second PDU in the PDU set that has not been discarded, if the remaining value of the discard timer associated with the PDCP SDU corresponding to the PDU with the smallest sequence number in the PDU set is less than (or equal to) the time threshold, the UE can trigger the DSR, and the triggered DSR with the remaining value (and / or related triggering information) can be indicated to the lower layer (e.g., MAC layer). The related triggering information may include the PDU set ID of the triggered DSR and / or the sequence number of the PDCP SDU that has triggered the DSR.

[0129] In some embodiments, the PDCP entity triggering the DSR may mean that the PDCP entity instructs a lower layer (eg, a MAC layer) to trigger the DSR.

[0130] In some embodiments, the time threshold (value) may be indicated by a lower layer (e.g., MAC layer). If the time threshold is indicated, the PDCP entity may be allowed to trigger the DSR. If the time threshold is not indicated, the PDCP entity may not be allowed to trigger the DSR.

[0131] In some embodiments, the DSR triggering operation can be performed by a MAC entity. When the UE is configured with a time threshold for an LCG, the PDCP entity associated with the LCH of the LCG can perform a PDCP delay critical data amount calculation process. In addition, the RLC entity associated with the PDCP entity can perform an RLC delay critical data amount calculation process. If delay critical UL data is available for the LCG, the MAC entity can trigger the DSR. The MAC entity can determine the amount of delay critical UL data available for the LCG based on the PDCP / RLC delay critical data amount calculation process.

[0132] In some embodiments, the MAC entity may configure a DSR prohibit timer for each LCG. When the DSR of an LCG is triggered, the MAC entity may start / restart the DSR prohibit timer associated with the LCG. If the DSR prohibit timer associated with the LCG is not running or has expired, the MAC entity may (only) trigger the DSR for the LCG. The DSR prohibit timer for the LCG may be stopped if there is no delay critical data volume in the PDCP buffer and RLC buffer of any logical channel in the LCG.

[0133] DSR Cancellation

[0134] If the UE determines that a triggered DSR has become invalid or expired, the triggered DSR may be discarded or canceled.

[0135] In some embodiments, DSR cancellation may be triggered by a MAC entity, which may maintain a DSR discard timer (e.g., DSRDiscardTimer). More specifically, when a DSR is triggered, the UE may start / restart a new DSR discard timer for the DSR. When the DSR discard timer of the triggered DSR expires, the UE may cancel the triggered DSR.

[0136] In some implementations, the BS may configure a DSR discard timer for each LCG for the UE via, for example, RRC signaling. When DSR is triggered for an LCG, the MAC entity may start / restart a new timer for the DSR, where the new timer may be set by the value of the DSR discard timer configured for the LCG.

[0137] In some embodiments, the value of the DSR discard timer may be indicated by the PDCP entity. More specifically, when the PDCP entity instructs the MAC entity to trigger the DSR, the PDCP entity may also indicate the value of the DSR discard timer used to initialize the DSR. When the MAC entity is instructed to trigger the DSR and the value of the DSR discard timer used to initialize the DSR is indicated, the MAC entity may use the value indicated by the PDCP entity to start / restart the timer of the DSR. For example, for a triggered DSR, the value of the DSR discard timer used to initialize the DSR may be set to the remaining value of the discard timer indicated by the PDCP entity when the DSR was triggered.

[0138] Taking into account the MAC PDU processing delay, the MAC entity can be configured with a discard threshold for each LCG for DSR discard / cancellation. More specifically, if the remaining value of the DSR discard timer of the DSR of the LCG is less than the discard threshold of the LCG, the MAC entity can discard / cancel the DSR.

[0139] In some embodiments, DSR cancellation may be triggered by a PDCP entity. For example, when a PDCP SDU is discarded, the PDCP entity may instruct the lower layer (e.g., MAC layer) to discard / cancel the DSR triggered because the remaining time of the PDCP SDU is less than (or equal to) a time threshold. For example, when all PDCP SDUs belonging to a certain PDU set are discarded, the PDCP entity may instruct the lower layer (e.g., MAC layer) to discard / cancel the DSR triggered because the remaining time of the PDCP SDU corresponding to the PDU with the smallest sequence number in the PDU set is less than (or equal to) a time threshold.

[0140] Calculation of PDCP delay key data volume

[0141] In order to report the MAC delay status (e.g., trigger DSR, generate DSR MAC CE), when the time threshold is configured for the LCG, the (sending) PDCP entity associated with the LCH of the LCG can perform a PDCP delay critical data amount calculation process, which outputs the number of PDCP delay critical data and the remaining time of the PDCP delay critical data. The result of the PDCP delay critical data amount calculation process can be indicated to the lower layer (e.g., MAC layer).

[0142] The PDCP delay critical data amount calculation process can regard the PDCP SDU whose remaining discard timer value is less than the time threshold as a delay critical PDCP SDU, and use the remaining discard timer value as the remaining time of the delay critical PDCP SDU. The PDCP entity can regard all delay critical PDCP SDUs as PDCP delay critical data, and use the minimum remaining time of the delay critical PDCP SDU as the remaining time of the PDCP delay critical data.

[0143] In some embodiments, when the PDCP entity determines that a PDCP SDU is a delay-critical PDCP SDU, if the corresponding PDCP data PDU has been submitted to the lower layer, the PDCP entity may instruct the lower layer to treat the corresponding PDCP data PDU as delay-critical data, and may instruct the lower layer of the remaining time of the delay-critical PDCP SDU.

[0144] In some embodiments, for a PDCP data PDU that has not been submitted to a lower layer, the PDCP delay critical data amount calculation process may regard a PDCP data PDU whose remaining discard timer value is less than a time threshold as a delay critical PDCP data PDU, and regard the remaining discard timer value as the remaining time of the delay critical PDCP data PDU. The PDCP entity may regard all delay critical PDCP data PDUs as PDCP delay critical data. The minimum remaining time of the delay critical PDCP data PDU may be regarded as the remaining time of the PDCP delay critical data.

[0145] In some implementations, the PDCP entity may treat all delay critical PDCP data PDUs and all delay critical PDCP SDUs as PDCP delay critical data.

[0146] In some embodiments, the PDCP delay critical data amount calculation process may be performed from the perspective of a PDU set. For example, if a PDCP SDU belongs to a PDU set including at least one PDU corresponding to a delay critical PDCP SDU, then a PDCP SDU whose remaining discard timer value is not less than a time threshold may be considered a delay critical PDCP SDU. For example, for a PDCP data PDU that has not yet been submitted to a lower layer, if the remaining discard timer value of the PDCP data PDU is not less than a time threshold, and the PDCP data PDU belongs to a PDU set including at least one PDU corresponding to a delay critical PDCP data PDU, then the PDCP data PDU may be considered a delay critical PDCP data PDU.

[0147] In some embodiments, the PDCP delay critical data may include a first PDCP SDU and a second PDCP SDU, wherein the remaining time value of a discard timer of the first PDCP SDU is less than a time threshold, the remaining time value of a discard timer of the second PDCP SDU is not less than the time threshold, and the second PDCP SDU belongs to a PDU set including at least one PDCP SDU (e.g., different from the second PDCP SDU), the remaining time value of an associated discard timer of which is less than the time threshold.

[0148] Calculation of RLC delay key data volume

[0149] In order to report the MAC delay status (e.g., triggering DSR, generating DSR MAC CE), the RLC entity that can be instructed (sent) by the upper layer (e.g., PDCP layer) or the lower layer (e.g., MAC layer) to perform the RLC delay critical data amount calculation process to output the number of RLC delay critical data and the remaining time of the RLC delay critical data. The RLC entity can indicate the result of the RLC delay critical data amount calculation process to the MAC entity.

[0150] In some embodiments, when an upper layer (e.g., a PDCP layer) indicates to the RLC entity a specific RLC SDU with a remaining time, the RLC entity may regard the RLC SDU as a delay critical RLC SDU, and the remaining time may be regarded as the remaining time of the delay critical RLC SDU. The RLC entity may regard all delay critical RLC SDUs as RLC delay critical data. The minimum remaining time of the delay critical RLC SDU may be regarded as the remaining time of the RLC delay critical data.

[0151] In some embodiments, when an upper layer (e.g., a PDCP layer) indicates to the RLC entity a specific RLC data PDU with a remaining time, the RLC entity may regard the RLC data PDU as a delay critical RLC data PDU, and the remaining time may be regarded as the remaining time of the delay critical RLC data PDU. The RLC entity may regard all delay critical RLC data PDUs as RLC delay critical data. The minimum remaining time of the delay critical RLC data PDU may be regarded as the remaining time of the RLC delay critical data.

[0152] In some implementations, the RLC entity may consider all delay critical RLC SDUs and all delay critical RLC data PDUs as RLC delay critical data. The minimum remaining time of delay critical RLC SDUs and delay critical RLC data PDUs may be considered as the remaining time of RLC delay critical data.

[0153] DSR type and corresponding DSR MAC CE

[0154] For a triggered DSR, the UE may determine the DSR type to be reported for the triggered DSR before the LCP, so that when UL-SCH resources are available for new transmissions, the UE may determine whether the DSR MAC CE can be accommodated as a result of the LCP.

[0155] For a triggered DSR, the UE may report a short DSR for the LCG.For a short DSR, the UE may generate a DSR MAC CE with a fixed size.

[0156] In some implementations, for (a) triggered DSR, the UE may report a long DSR with LCGs having delay-critical data available for transmission. For a long DSR, the UE may generate a DSR MAC CE with variable size.

[0157] In some implementations, for a triggered DSR, if multiple LCGs have delay-critical data available for transmission, the UE may report a long DSR when constructing a MAC PDU containing the DSR, otherwise the UE may report a short DSR.

[0158] In some implementations, the Short DSR MAC CE or the Long DSR MAC CE may include at least one of the following fields:

[0159] LCG ID: The LCG ID field may identify a group of logical channels for which delay status is being reported.

[0160] Buffer size: The buffer size field may identify the total amount of delay critical data available based on a delay critical data amount calculation process performed by the PDCP and / or RLC entity on all logical channels of the logical channel group after the MAC PDU is established (e.g., after the logical channel prioritization process). In some embodiments, the value of this field may be determined based on the old BSR table for XR services and / or the newly introduced BSR table. The BS may indicate to the UE via RRC / MAC / PHY signaling whether the newly introduced BSR table is used for DSR. For example, the UE may determine the buffer size field of the LCG based on a first predefined table (e.g., a newly introduced BSR table for XR services) or a second predefined table (e.g., an old BSR table). The UE may determine the buffer size field of the LCG based on the first predefined table in response to receiving a table indication from the BS via RRC signaling. When the table indication is not received from the BS, the UE may determine the buffer size field of the LCG based on the second predefined table.

[0161] Remaining time: The remaining time field may be determined / identified by the minimum remaining time of the available delayed critical data according to the PDCP / RLC delayed critical data amount calculation process performed by the PDCP and RLC entities on all logical channels of the logical channel group after the MAC PDU is established (e.g., after the logical channel prioritization process). For example, LCH#1 and LCH#2 belong to LCG#1, and the MAC entity may obtain the following results: the remaining time of the PDCP delayed critical data from LCH#1 is 10ms, the remaining time of the RLC delayed critical data from LCH#1 is 8ms, the remaining time of the PDCP delayed critical data from LCH#2 is 9ms, and the remaining time of the RLC delayed critical data from LCH#2 is 9ms. Then the remaining time field of the DSRMAC CE of LCG#1 may be identified as 8ms.

[0162] LCGi: For the long DSR format, this field may indicate the presence of the buffer size field and the remaining time field for logical channel group i. For example, an LCGi field set to 1 may indicate that the buffer size field and the remaining time field for logical channel group i have been reported. An LCGi field set to 0 may indicate that the buffer size field and the remaining time field for logical channel group i have not been reported. For the short DSR format, this field may not be present.

[0163] In some embodiments, the UE may report another type of DSR for an LCG, where the DSR may also include the delay status of the LCH belonging to the LCG. This type of DSR may be referred to as an extended or enhanced (short / long) DSR. An extended or enhanced (short / long) DSR may include at least one of the following fields:

[0164] LCH ID: The Logical Channel ID field may identify the logical channel belonging to the LCG for which the delay status is being reported.

[0165] Remaining Time: This field identifies the minimum remaining time of available delay critical data based on the PDCP / RLC delay critical data amount calculation process performed by the PDCP and RLC entities for the logical channels belonging to the LCG after constructing the MAC PDU (e.g., after the logical channel prioritization process).

[0166] In some implementations, the BS may indicate to the UE via RRC / MAC / PHY signaling whether reporting of extended or enhanced (short / long) DSR is allowed.

[0167] In some embodiments, when the time length is greater than 0ms, the remaining time field value may need to be reduced by a time length, where the time length is from the moment when the DSR MAC CE is constructed to the moment when the first symbol of the PUSCH carrying the DSR MAC CE is transmitted. For example, when constructing the DSR MAC CE, according to the PDCP / RLC delay critical data amount calculation process, the remaining time of the delay critical data to be reported can be 10ms. If the time length is 2ms, the remaining time of the delay critical data to be reported in the DSR MAC CE can be 8ms. In some embodiments, the time length can be a fixed value in milliseconds, which can be predefined and / or configured by the BS, for example, via RRC signaling.

[0168] In some embodiments, the DSR format may be identified by a MAC subheader with an LCID for UL-SCH. In some embodiments, the DSR format may be identified by a MAC subheader with an octet / two octet eLCID for UL-SCH.

[0169] Enhanced LCP

[0170] The UE may apply the LCP procedure whenever a new transmission is performed. In some embodiments, in the LCP procedure, the priority of the DSR MAC CE may be lower than the priority of the CG confirmation MAC CE and higher than the priority of the MAC CE for the BSR (excluding the BSR for padding). In some embodiments, the MAC PDU may contain at most one DSR MAC CE even if one or more DSRs are triggered.

[0171] SR for DSR

[0172] Enhanced SR (eSR) may be introduced to request UL-SCH resources for new transmission of delayed critical data. For example, the UE may send an SR or eSR to the BS to request uplink resources for transmission of a DSR MAC CE. The MAC entity may configure zero, one, or multiple eSR configurations. An eSR configuration may include a set of PUCCH resources for eSR across different BWPs and cells. For a logical channel, at most one PUCCH resource for eSR may be configured per BWP.

[0173] In some embodiments, when at least one DSR has been triggered and not cancelled, the MAC entity may trigger an eSR if at least one of the following conditions is met:

[0174] There are no UL-SCH resources available for new transmissions (eg, new transmissions for DSR MAC CE).

[0175] The UL-SCH resources available for new transmissions do not conform to the LCP mapping restrictions configured for the logical channel for which DSR has been triggered.

[0176] The DSR discard timer for the triggered DSR is running.

[0177] The remaining time of the DSR discard timer for the triggered DSR is less than an eSR triggering time threshold, where the eSR triggering time threshold may be configured by the BS, for example, through RRC signaling, and / or may be predefined as a fixed value.

[0178] Each eSR configuration may correspond to one or more logical channels. Each logical channel may be mapped to zero or one eSR configuration, which may be configured via RRC signaling. The eSR configuration of the logical channel for which DSR is triggered (if such configuration exists) may be considered as the corresponding eSR configuration for the triggered eSR.

[0179] In some implementations, if the UE cancels all DSRs triggered by the LCH mapped to the eSR configuration of the triggered eSR, the triggered eSR may be canceled.

[0180] In some implementations, if an eSR is triggered due to a DSR, the eSR may be considered pending until it is canceled.

[0181] In some embodiments, if a pending eSR is triggered by a DSR before MAC PDU assembly and the MAC PDU containing the DSR has been transmitted, the UE may cancel the pending eSR.

[0182] In some embodiments, if at least one eSR is in a pending state and the UE's MAC entity is not configured with valid PUCCH resources, the UE may not initiate a random access procedure. Instead, the UE may cancel the pending eSR and / or cancel the DSR that triggered the pending eSR.

[0183] Figure 4 4 is a flow chart of a method / process 400 for DSR performed by a UE according to an example embodiment of the present disclosure. In action 402, the process 400 may begin by receiving configuration information related to the LCG from the BS through RRC signaling. In action 404, the process 400 may trigger a DSR process. In some embodiments, triggering the DSR process may include triggering the DSR process when it is determined that the remaining time value of the discard timer associated with the PDCP SDU belonging to the LCG has been less than a time threshold and the DSR process has not been triggered.

[0184] In action 406, process 400 may generate a DSR MAC CE including a first field for indicating a buffer size of the LCG. In action 408, process 400 may transmit the DSR MAC CE to the BS. The buffer size may indicate a total amount of delay critical data of the LCG. The delay critical data of the LCG may include a first PDCP SDU, wherein a remaining time value of a first discard timer corresponding to the first PDCP SDU is less than a time threshold associated with the LCG; and a second PDCP SDU belonging to a PDU set, wherein the PDU set includes at least one PDCP SDU, wherein a remaining time value of a second discard timer corresponding to the second PDCP SDU is less than the time threshold. Then, process 400 may end.

[0185] In some implementations, the time threshold associated with the LCG may be received from the BS via RRC signaling.

[0186] In some embodiments, the buffer size of the LCG may be determined based on the first predefined table or the second predefined table. The first predefined table may be used for XR services. In some embodiments, the UE may determine the buffer size of the LCG based on the first predefined table after receiving a table indication from the BS through RRC signaling. In the absence of receiving a table indication from the BS, the UE may determine the buffer size of the LCG based on the second predefined table.

[0187] In some implementations, the DSR MAC CE may further include a second field indicating a minimum remaining time for delaying critical data of the LCG.

[0188] In some implementations, the UE may transmit an SR to the BS to request uplink resources for transmitting the DSR MAC CE.

[0189] Figure 4 The steps / actions shown in the description should not be construed as necessarily having order dependency. The order in which the process is described should not be construed as limiting. In addition, in some embodiments, the steps / actions shown in the description should not be construed as necessarily having order dependency. Figure 4 Some of the actions shown in Figure 4 One or more actions shown in .

[0190] Figure 4 The technical problem solved by the method shown is to improve the accuracy and efficiency of DSR in managing delay-critical data transmission in wireless communication networks. By defining delay-critical data in two different ways, the method combines two standards to better reflect the urgency of data transmission. This enhanced definition of delay-critical data allows a more precise indication of the buffer size in the DSR MAC CE, which helps the BS to allocate resources more efficiently. This improves network performance by preventing unnecessary loss of time-sensitive data.

[0191] Figure 5 is a flowchart of a method / process 500 for configuring DSR performed by a BS according to an example embodiment of the present disclosure. In action 502, process 500 may start by transmitting configuration information related to the LCG to the UE via RRC signaling. In action 504, process 500 may receive a DSR MAC CE from the UE, the DSR MAC CE including a first field for indicating a buffer size of the LCG. The buffer size may indicate the total amount of delay-critical data for the LCG. The delay-critical data of the LCG may include a first PDCP SDU, the remaining time value of a first discard timer corresponding to the first PDCP SDU is less than a time threshold associated with the LCG; and a second PDCP SDU belonging to a PDU set, the PDU set including at least one PDCP SDU, the remaining time value of a second discard timer corresponding to the second PDCP SDU is less than the time threshold. Figure 5 The method shown is similar to Figure 4 The method shown is similar, except that it is described from the perspective of the BS (rather than the UE).

[0192] In some embodiments, the BS may send a time threshold associated with the LCG to the UE via RRC signaling. In some embodiments, the DSR MAC CE may further include a second field indicating a minimum remaining time for delaying critical data of the LCG. In some embodiments, the BS may receive an SR from the UE for requesting uplink resources for transmitting the DSR MAC CE.

[0193] Figure 6 is a block diagram of a node 600 for wireless communication according to various aspects of the present disclosure. Figure 6 As shown, the node 600 may include a transceiver 620, a processor 628, a memory 634, one or more presentation components 638, and at least one antenna 636. The node 600 may also include a radio frequency (RF) spectrum band module, a BS communication module, a network communication module, and a system communication management module, an input / output (I / O) port, an I / O component, and a power supply ( Figure 6 not shown).

[0194] Each component can communicate with each other directly or indirectly via one or more buses 640. Node 600 can be a reference Figures 1 to 5 Disclose various functions of UE or BS.

[0195] The transceiver 620 has a transmitter 622 (e.g., a transmit / transmit circuit) and a receiver 624 (e.g., a receive / receive circuit), and can be configured to send and / or receive time and / or frequency resource partitioning information. The transceiver 620 can be configured to transmit in different types of subframes and time slots, including but not limited to available, unavailable, and flexibly available subframe and time slot formats. The transceiver 620 can be configured to receive data and control channels.

[0196] Node 600 may include a variety of computer-readable media. Computer-readable media may be any available media accessible by node 600, including volatile (and / or nonvolatile) media and removable (and / or non-removable) media.

[0197] Computer readable media may include computer storage media and communication media. Computer storage media may include volatile (and / or non-volatile) media and removable (and / or non-removable) media implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules or data.

[0198] Computer storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other storage technology), CD-ROM, digital versatile disk (DVD) (or other optical disk storage), cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer storage media may not include propagated data signals. Communication media may generally embody computer readable instructions, data structures, program modules, or other data in a modulated data signal (such as a carrier wave) or other transmission mechanism, and include any information delivery media.

[0199] The term "modulated data signal" may refer to a signal whose one or more characteristics are set or changed in order to encode information in the signal. Communication media may include wired media (such as a wired network or direct-wired connection) and wireless media (such as acoustic, RF, infrared and other wireless media). Combinations of any of the above should also be included within the scope of computer-readable media.

[0200] The memory 634 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 634 may be removable, non-removable, or a combination thereof. Example memories may include solid-state memory, hard drives, optical drives, etc. Figure 6 As shown, the memory 634 can store computer-readable and / or computer-executable instructions 632 (eg, software codes) that, when executed, are configured to cause the processor 628 to perform the present disclosure, such as reference 632. Figures 1 to 5 Alternatively, the instructions 632 may not be directly executable by the processor 628, but may be configured to cause the node 600 (eg, when compiled and executed) to perform various functions of the present disclosure.

[0201] The processor 628 (e.g., having a processing circuit) may include an intelligent hardware device, such as a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 628 may include a memory. The processor 628 may process data 630 and instructions 632 received from the memory 634, as well as information sent and received through the transceiver 620, the baseband communication module, and / or the network communication module. The processor 628 may also process information to be sent to the transceiver 620 for transmission to the network communication module via the antenna 636 for transmission to the CN.

[0202] One or more presentation components 638 can present data indications to a person or other device. Examples of presentation components 638 can include a display device, a speaker, a printing component, a vibration component, etc.

[0203] In view of the present disclosure, it is apparent that various techniques may be used to implement the disclosed concepts without departing from the scope of these concepts. Furthermore, although these concepts have been disclosed with specific reference to certain embodiments, it will be appreciated by those of ordinary skill in the art that changes may be made in form and detail without departing from the scope of these concepts. Therefore, the disclosed embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the specific embodiments disclosed, and that many rearrangements, modifications, and substitutions may be made without departing from the scope of the present disclosure.

Claims

1. A method for delaying status reporting (DSR) performed by a user equipment (UE), characterized in that: The method includes: receiving configuration information related to the logical channel group LCG from the base station BS via radio resource control RRC signaling; Trigger the DSR process; generating a DSR medium access control MAC control element CE, wherein the DSR MAC CE comprises a first field for indicating a buffer size of the LCG; and The DSR MAC CE is sent to the BS, wherein: The buffer size indicates the total amount of delay-critical data for the LCG, and The key data of the LCG delay include: a first Packet Data Convergence Protocol PDCP service data unit SDU, wherein a remaining time value of a first discard timer of the first PDCP SDU is less than a time threshold associated with the LCG; and A second PDCP SDU belongs to a protocol data unit PDU set, wherein the PDU set includes at least one PDCP SDU, and a remaining time value of a second discard timer of the at least one PDCP SDU is less than the time threshold.

2. The method according to claim 1, characterized in that The method further comprises: The time threshold associated with the LCG is received from the BS through the RRC signaling.

3. The method according to claim 1, characterized in that Triggering the DSR process includes: When it is determined that the remaining time value of the discard timer associated with the PDCP SDU belonging to the LCG is less than the time threshold and no DSR process is triggered, the DSR process is triggered.

4. The method according to claim 1, characterized in that: The method further comprises: The buffer size of the LCG is determined according to the first predefined table or the second predefined table.

5. The method according to claim 4, characterized in that: The first predefined table is used for extended reality XR service.

6. The method according to claim 4, characterized in that Determining the buffer size of the LCG includes: determining a buffer size of the LCG based on the first predefined table in response to a table indication received from the BS through the RRC signaling; and When the table indication is not received from the BS, a buffer size of the LCG is determined based on the second predefined table.

7. The method according to claim 1, characterized in that The DSR MAC CE also includes a second field, and the second field is used to indicate the minimum remaining time of delay critical data of the LCG.

8. The method according to claim 1, characterized in that The method further comprises: A scheduling request SR is sent to the BS, where the SR is used to request uplink resources for transmitting the DSR MAC CE.

9. A user equipment UE for delay status reporting DSR, characterized in that: The UE includes: at least one processor; and At least one non-transitory computer-readable medium, coupled to at least one processor and storing one or more computer-executable instructions, which, when executed by the at least one processor, cause the UE to: receiving configuration information related to the logical channel group LCG from the base station BS via radio resource control RRC signaling; Trigger the DSR process; generating a DSR medium access control MAC control element CE, wherein the DSR MAC CE comprises a first field for indicating a buffer size of the LCG; and The DSR MAC CE is sent to the BS, wherein: The buffer size indicates the total amount of delay-critical data for the LCG, and The key data of the LCG delay include: a first Packet Data Convergence Protocol PDCP service data unit SDU, wherein a remaining time value of a first discard timer of the first PDCP SDU is less than a time threshold associated with the LCG; and A second PDCP SDU belongs to a protocol data unit PDU set, wherein the PDU set includes at least one PDCP SDU, and a remaining time value of a second discard timer of the at least one PDCP SDU is less than the time threshold.

10. The UE according to claim 9, characterized in that: When the one or more computer executable instructions are executed by the at least one processor, the UE is further caused to: The time threshold associated with the LCG is received from the BS through the RRC signaling.

11. The UE according to claim 9, characterized in that: Triggering the DSR process includes: When it is determined that the remaining time value of the discard timer associated with the PDCP SDU belonging to the LCG is less than the time threshold and no DSR process is triggered, the DSR process is triggered.

12. The UE according to claim 9, characterized in that When the one or more computer executable instructions are executed by the at least one processor, the UE is further caused to: The buffer size of the LCG is determined according to the first predefined table or the second predefined table.

13. The UE according to claim 12, characterized in that: The first predefined table is used for extended reality XR service.

14. The UE according to claim 12, characterized in that: Determining the buffer size of the LCG includes: determining a buffer size of the LCG based on the first predefined table in response to a table indication received from the BS through the RRC signaling; and When the table indication is not received from the BS, a buffer size of the LCG is determined based on the second predefined table.

15. The UE according to claim 9, characterized in that The DSR MAC CE also includes a second field, and the second field is used to indicate the minimum remaining time of delay critical data of the LCG.

16. The UE according to claim 9, characterized in that: When the one or more computer executable instructions are executed by the at least one processor, the UE is further caused to: A scheduling request SR is sent to the BS, where the SR is used to request uplink resources for transmitting the DSR MAC CE.

17. A base station BS for configuring a delayed status report DSR, characterized in that: The BS comprises: at least one processor; and at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium being coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: Transmitting configuration information related to the logical channel group LCG to the user equipment UE through radio resource control RRC signaling; and A DSR medium access control MAC control element CE is received from the UE, wherein the DSR MAC CE includes a first field for indicating a buffer size of the LCG, wherein: The buffer size indicates the total amount of delay-critical data for the LCG, and The key data of the LCG delay include: a first Packet Data Convergence Protocol PDCP service data unit SDU, wherein a remaining time value of a first discard timer of the first PDCP SDU is less than a time threshold associated with the LCG; and A second PDCP SDU belongs to a protocol data unit PDU set, wherein the PDU set includes at least one PDCP SDU, and a remaining time value of a second discard timer of the at least one PDCP SDU is less than the time threshold.

18. The BS according to claim 17, characterized in that: When the one or more computer executable instructions are executed by the at least one processor, the BS is further caused to: A time threshold associated with the LCG is sent to the UE through the RRC signaling.

19. The BS according to claim 17, wherein: The DSR MAC CE also includes a second field, and the second field is used to indicate the minimum remaining time of delay critical data of the LCG.

20. The BS according to claim 17, wherein: When the one or more computer executable instructions are executed by the at least one processor, the BS is further caused to: A scheduling request SR for requesting uplink resources for transmitting the DSR MAC CE is received from the UE.

Images