Method and apparatus for reporting remaining time in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to the present disclosure, a base station may efficiently allocate uplink resources based on information transmitted from a terminal.

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in mobile communication systems. More specifically, this disclosure relates to a method for enabling a base station to efficiently allocate uplink resources. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz (THz) bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, standardization was underway for the following technologies to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC): beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves; dynamic operation supporting parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats for efficient utilization of millimeter wave resources; initial access technologies supporting multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods (such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization already exists for technologies such as: V2X (Vehicle-to-Everything) for assisting autonomous vehicles in determining driving based on information about the location and status of vehicles transmitted by vehicles and for enhancing user convenience; NR-U (New Radio Unlicensed) designed to make system operation in unlicensed bands comply with various regulatory requirements; NR UE power saving; non-terrestrial networks (NTNs) for UE-satellite direct communication to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, standardization is underway in the wireless interface architecture / protocol domain for technologies such as: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul) for nodes to provide network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and two-step random access (2-step RACH for NR) to simplify the random access process. In terms of system architecture / services, standardization is also underway for: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and mobile edge computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices, which has already increased exponentially, will be connected to the communication network. Therefore, enhanced functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices, are expected to be necessary. To this end, new research is planned related to: Extended Reality (XR) for effectively supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; improving 5G performance and reducing 5G complexity by leveraging Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve as a foundation for: not only developing new waveforms for providing terahertz band coverage for 6G mobile communication technologies, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and RIS (reconfigurable smart surfaces), but also developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technologies and enhance system networks, AI-based communication technologies to achieve system optimization by leveraging satellites and AI (artificial intelligence) from the design phase and internalizing end-to-end AI support capabilities, and next-generation distributed computing technologies to achieve services at a complexity level exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] With the advancement of the aforementioned mobile communication systems, UEs need to report various information to base stations so that base stations can effectively allocate uplink resources. Summary of the Invention

[0009] Technical issues

[0010] This disclosure aims to enable a base station to efficiently allocate uplink resources by allowing the UE to send various information to the base station, including information about the amount of data stored in the UE buffer.

[0011] Technical solution

[0012] To address the aforementioned problems, according to embodiments of this disclosure, a method performed by a terminal in a wireless communication system includes: receiving a control message from a base station, the control message including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG); triggering the DSR for the LCG based on the information about the remaining time; a DSR Media Access Control (MAC) control element (CE) for the triggered DSR including a remaining time field and a buffer size field; and sending the DSR MAC CE to the base station.

[0013] Meanwhile, according to another embodiment of this disclosure, a method performed by a base station in a wireless communication system includes: sending a control message to a terminal, the control message including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG); and receiving a DSR Media Access Control (MAC) control element (CE) from the terminal, including a remaining time field and a buffer size field, when the DSR for the LCG is triggered based on the information about the remaining time, wherein the remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer for any LCG, and the buffer size field corresponds to the amount of data associated with the RLC entity and the PDCP entity determined based on the information about the remaining time.

[0014] Meanwhile, according to another embodiment of this disclosure, a terminal in a wireless communication system may include a transceiver and a controller, the controller being configured to receive control messages from a base station via the transceiver, the control messages including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG), controlling the triggering of the DSR for the LCG based on the information about the remaining time, the DSR Media Access Control (MAC) control element (CE) for the triggered DSR including a remaining time field and a buffer size field, and controlling the transmission of the DSR MAC CE to the base station via the transceiver.

[0015] Meanwhile, according to another embodiment of this disclosure, a base station in a wireless communication system may include a transceiver and a controller, the controller being configured to send a control message to a terminal via the transceiver. The control message includes information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG). When the DSR for the LCG is triggered based on the information about the remaining time, the transceiver controls the reception from the terminal of a DSR Media Access Control (MAC) control element (CE) including a remaining time field and a buffer size field. The remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer for any LCG, and the buffer size field corresponds to the amount of data associated with the RLC entity and the PDCP entity determined based on the information about the remaining time.

[0016] Beneficial effects

[0017] According to embodiments of this disclosure, a base station can effectively allocate uplink resources based on information sent from a UE. Attached Figure Description

[0018] Figure 1 This is a diagram illustrating the structure of an NR system according to an embodiment of the present disclosure.

[0019] Figure 2 This is a diagram illustrating the wireless protocol structure in an NR system according to an embodiment of the present disclosure.

[0020] Figure 3 This is a diagram illustrating the buffer state of a UE based on each Delay State Report (DSR)-Logical Channel (LCH) according to an embodiment of the present disclosure, including the remaining time and corresponding amount of data stored in the buffer.

[0021] Figure 4 This is a graph showing the reference time of the remaining time according to an embodiment of the present disclosure.

[0022] Figure 5 This diagram illustrates the process by which a base station and a UE confirm whether the UE supports DSR and configure DSR-related settings via RRC signaling, according to an embodiment of this disclosure.

[0023] Figure 6 This is a block diagram illustrating the configuration of a base station according to an embodiment of the present disclosure.

[0024] Figure 7 This is a block diagram illustrating the configuration of a terminal according to an embodiment of the present disclosure.

[0025] Figure 8 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure.

[0026] Figure 9 This is a flowchart illustrating the operation of a base station according to an embodiment of the present disclosure. Detailed Implementation

[0027] In the following, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same reference numerals denote the same parts. Furthermore, detailed descriptions relating to well-known functions or configurations will be excluded so as not to unnecessarily obscure the subject matter of the disclosure.

[0028] In describing embodiments of this disclosure, descriptions of technical content known in the art to which this disclosure pertains and not directly related to this disclosure will be omitted. This is to convey the main points of this disclosure more clearly and without ambiguity by omitting unnecessary explanations.

[0029] For the same reason, some components in the accompanying drawings are exaggerated, omitted, or shown schematically. Furthermore, the dimensions of the components do not perfectly reflect their actual dimensions. In all the drawings, the same reference numerals are used to denote the same or equivalent components.

[0030] Various advantages and features of this disclosure, as well as methods for achieving these advantages and features, will become apparent from the following detailed description of embodiments with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments described below, but can be implemented in various different forms. These embodiments are provided only to complete this disclosure and to allow those skilled in the art to fully appreciate its scope, and this disclosure is defined by the scope of the claims. Throughout the specification, the same reference numerals denote the same parts.

[0031] In this context, it should be understood that each block of the flowchart and combinations thereof can be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, these computer program instructions, executed by the processor of the computer or other programmable data processing device, create means for performing the functions described in the blocks of the flowchart. Since these computer program instructions can also be stored in computer-usable or computer-readable storage, which can be directed to the computer or other programmable data processing device to implement functions in a particular manner, the computer program instructions stored in computer-usable or computer-readable storage can also produce articles of manufacture including instruction means for performing the functions described in the blocks of the flowchart. Since the computer program instructions can also be mounted on a computer or other programmable data processing device, the instructions for performing a series of operational steps on the computer or other programmable data processing device to create a process executed by the computer, thereby providing steps for performing the functions described in the blocks of the flowchart, are also executed by the computer or other programmable data processing device.

[0032] Additionally, each box may represent some of a module, segment, or code that includes one or more executable instructions for performing a specific logical function. Furthermore, it should be noted that in some alternative embodiments, the functions mentioned in the boxes occur regardless of order. For example, two blocks shown consecutively may actually be executed simultaneously, or in reverse order depending on their corresponding functions.

[0033] In this context, the term "~unit" as used in this embodiment refers to a software or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and the "~unit" performs certain roles. However, the "~unit" is not limited to software or hardware. A "~unit" can be configured to be stored in an addressable storage medium or can be configured to reproduce one or more processors. Thus, as an example, a "~unit" includes components such as software components, object-oriented software components, class components, and task components; processes; functions; attributes; procedures; subroutines; program code segments; drivers; firmware; microcode; circuits; data; databases; data structures; tables; arrays; and variables. Components and functions provided within a "~unit" can be combined into a smaller number of components and "~units," or can be further separated into additional components and "~units." Furthermore, components and "~units" can be implemented to reproduce one or more CPUs in a device or secure multimedia card.

[0034] In the following text, a base station is an entity that performs resource allocation for a terminal and can be at least one of a Node B, a base station (BS), an eNode B (eNB), a gNode B (gNB), a radio access unit, a base station controller, and a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a 5G UE, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, embodiments of this disclosure can be applied to other communication systems having a similar technical background or channel format to the embodiments of this disclosure described below. Additionally, without significantly departing from the scope of this disclosure, as determined by those skilled in the art, embodiments of this disclosure can be applied to other communication systems with certain modifications. For example, fifth-generation (5G) mobile communication technology (New Radio, NR) developed after LTE-A can be included in such other communication systems, and 5G as described below can also be a concept encompassing existing LTE, LTE-A, and other similar services. Furthermore, without significantly departing from the scope of this disclosure, as determined by those skilled in the art, this disclosure can be applied to other communication systems with certain modifications.

[0035] In the following description, terms used to identify access nodes, to refer to network entities or network functions (NFs), to refer to messages, to refer to interfaces between network entities, and to refer to various identifying information are merely examples for ease of description. Therefore, this disclosure is not limited to the terms described below, and other terms may be used to refer to objects with equivalent technical meanings.

[0036] For the purposes of the following description, some terms and names defined in the 3GPP Long Term Evolution (LTE) standard and / or the 3GPP NR (New Radio) standard may be used. However, this disclosure is not limited to the terms and names and may be applied equivalently to systems conforming to other standards.

[0037] Figure 1 This is a diagram illustrating the structure of an NR system according to an embodiment of the present disclosure.

[0038] Reference Figure 1 The wireless communication system can be configured to include multiple base stations (e.g., gNB 100, ng-eNB 110, ng-eNB 120, and gNB 130), Access and Mobility Management Functions (AMF) 140, User Plane Functions (UPF) 150, etc. Of course, the wireless communication system is not limited to... Figure 1 The configuration shown can include more or fewer components.

[0039] According to embodiments of this disclosure, user equipment (UE or terminal) 160 can access external networks via base stations 100, 110, 120 and 130 and UPF 150.

[0040] exist Figure 1 In this context, base stations 100, 110, 120, and 130 are access nodes of the cellular network and provide radio access to UEs accessing the network. For example, base stations 100, 110, 120, and 130 can collect status information of UE 160, such as buffer status, available transmit power status, and channel status, to serve the user's services and perform scheduling based on the collected information to support the connection between the UE and the core network (CN) (specifically, the CN of NR is referred to as 5GC).

[0041] exist Figure 1 In this context, gNB 100 and 130 can control multiple cells and apply an adaptive modulation and coding scheme (hereinafter referred to as AMC), which determines the modulation scheme and channel coding rate based on the channel state of UE 160.

[0042] The core network is responsible for various control functions and UE mobility management functions, and can connect to multiple base stations 100, 110, 120, and 130. Furthermore, the 5GC can also link with existing LTE systems.

[0043] Meanwhile, in wireless communication systems, the user plane (UP) related to the transmission of actual user data and the control plane (CP) for connection management can be configured separately. Figure 1 The gNB 100 and gNB 130 can use the UP and CP technologies defined in NR technology, and the ng-eNB 110 and ng-eNB 120 are connected to 5GC, but can use the UP and CP technologies defined in LTE technology.

[0044] AMF 140 is a device responsible for various control functions and mobility management functions of UE 160, and can be connected to multiple base stations 100, 110, 120 and 130.

[0045] UPF 150 can refer to a gateway device that provides data transmission. Although in Figure 1 Not shown, but NR wireless communication systems may also include Session Management Function (SMF). SMF manages packet data network connections, such as Protocol Data Unit (PDU) sessions provided to UE160.

[0046] Figure 2 This is a diagram illustrating the wireless protocol structure in an NR system according to an embodiment of the present disclosure.

[0047] refer to Figure 2 The radio protocols of the NR system can be composed of Service Data Adaptation Protocol (SDAP) 200 and 290, Packet Data Convergence Protocol (PDCP) 210 and 280, Radio Link Control (RLC) 220 and 270, Media Access Control (MAC) 230 and 260, and Physical (PHY) 240 and 250 in the UE and base station, respectively.

[0048] Service Data Adaptation Protocols (SDAP) 200 and 290 can transmit user data and perform operations such as mapping Quality of Service (QoS) streams to specific Data Radio Bearers (DRBs) for uplink and downlink, marking QoS stream identifiers (IDs) for uplink and downlink, and mapping reflected QoS streams to data bearers for uplink SDAPPDUs. SDAP configurations corresponding to each DRB can be provided from a higher RRC layer. Of course, this disclosure is not limited to the examples described above.

[0049] Packet Data Convergence Protocol (PDCP) 210 and 280 can handle operations such as Internet Protocol (IP) header compression / decompression. Furthermore, PDCP 210 and 280 can provide in-order and out-of-order delivery capabilities, as well as reordering, duplicate detection, retransmission, and encryption / decryption functions. Of course, this disclosure is not limited to the examples described above.

[0050] Radio link controls 220 and 270 can reconfigure PDCP Protocol Data Units (PDCP PDUs) to an appropriate size. Furthermore, RLCs 220 and 270 can provide in-order and out-of-order delivery capabilities, and offer Automatic Repeat Request (ARQ) functionality, concatenation, segmentation and reassembly capabilities, resegmentation functionality, reordering functionality, duplicate detection functionality, and error detection functionality. Of course, this disclosure is not limited to the examples described above.

[0051] MACs 230 and 260 can connect to multiple RLC layer entities configured in a UE and perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. Additionally, MACs 230 and 260 can provide mapping functions, scheduling information reporting functions, hybrid ARQ (HARQ) functions, priority control functions between logical channels, priority control functions between UEs, MBMS service acknowledgment functions, transmission format selection functions, and padding functions. Of course, this disclosure is not limited to the examples described above.

[0052] Physical (PHY) layers 240 and 250 perform the following operations: channel coding and modulation of higher-layer data, and conversion of higher-layer data into Orthogonal Frequency Division Multiplexing (OFDM) symbols for transmission via the radio channel; or demodulation and channel decoding of OFDM symbols received via the radio channel and delivery of OFDM symbols to higher layers. Additionally, Hybrid ARQ (HARQ) is used even at the physical layer for additional error correction. The receiver transmits a 1-bit indication of whether a packet sent from the transmitter has been received. This 1-bit information is called the HARQ Acknowledgment (ACK) / Negative ACK (NACK) message.

[0053] For LTE, downlink HARQ ACK / NACK information for uplink data transmission is transmitted via the Physical Hybrid ARQ Indicator Channel (PHICH). For NR, the need for retransmission or new transmission can be determined based on UE scheduling information transmitted via the Physical Dedicated Control Channel (PDCCH), which is used to transmit downlink / uplink resource allocation information, etc. This is because NR uses asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). PUCCH is typically transmitted on the uplink of the primary cell (PCell), as described below; however, when the UE supports PUCCH transmission on the secondary cell (SCell), as described below, the base station can allow the UE to additionally transmit PUCCH on the SCell, which is referred to as the PUCCH SCell.

[0054] Despite Figure 2 Although not shown in the diagram, the Radio Resource Control (RRC) layer exists above the PDCP layer in both the UE and the base station. The RRC layer can send and receive access and measurement-related configuration control messages for radio resource control.

[0055] Meanwhile, the physical layer can consist of one or more frequencies / carriers. The technique used to simultaneously configure and use multiple frequencies is called carrier aggregation (hereinafter referred to as CA). CA technology additionally uses a primary carrier and one or more subcarriers for communication between the terminal (or user equipment (UE)) and the base station (eNB or gNB) to significantly increase transmission capacity through the number of subcarriers, rather than using only one carrier for communication between the UE and the base station. In LTE / NR, cells within a base station using the primary carrier are called primary cells (PCell), and cells within a base station using secondary carriers are called secondary cells (SCell).

[0056] In next-generation / 5G (New Radio (NR)) wireless communication systems, the UE needs to report buffer status to the base station to help the base station schedule resources more efficiently. Buffer Status Report (BSR) is used to represent and report the amount of data stored in the UE's buffers. According to the NR specification, the UE selects a segment index from the buffer size table that includes the amount of buffer data to be reported within the range of data amounts defined for each segment, and includes the selected segment index in the BSR.

[0057] In NR systems, buffer status reporting can be performed based on Media Access Control (MAC) layer signaling between the UE and the base station. For example, when a BSR is triggered at a specific transmission time, the UE can send a BSR control element (MAC CE) to the base station by including a BSR MAC CE in the MAC PDU. In this case, the BSR control element indicates the amount of packets remaining in the UE's transmission buffer after assembling the corresponding MAC PDU, in units of Logical Channel Groups (LCGs). The base station can use the received BSR to estimate the amount of data currently remaining in the UE's buffer. In NR systems, the UE can manage the data transmission buffer to be sent to the base station based on eight LCGs.

[0058] Extended Reality (XR) uplink data includes a valid deadline time (delay budget), such as the remaining time as the remaining valid deadline. Data can be used as valid data when it is expected to arrive at the uplink server within the predetermined remaining time based on the time generated by the UE's application layer. When data fails to arrive at the uplink server within the specified remaining time, the corresponding data loses its application value. The UE buffer size reported via BSR is designed to report the total amount of data stored in the UE buffer. However, the base station does not know how much of the total data is closer to the deadline, for example, whether the remaining time is short. When the base station knows the remaining time of the data in the UE buffer and the amount of data corresponding to each remaining time, the base station can reflect the remaining time and data amount when performing uplink resource allocation so that data with relatively short remaining times are sent first. Therefore, more data can be sent before the remaining time expires, thereby improving cell capacity. On the other hand, when a particular data is data with a very short remaining time, the time from the time the data is reported via BSR to the time the data is actually sent can be shorter than the remaining time. In this case, the corresponding data may be sent after it has lost its application value, or it may have been discarded before it is sent. Correspondingly, the allocated uplink resources may not include valid data, resulting in resource waste. When the information reported to the base station includes the remaining time that meets a predefined remaining time standard (upper or lower limit) or includes the remaining time and data volume, the base station can utilize this information when allocating uplink resources to the UE, thereby achieving more efficient resource allocation.

[0059] According to embodiments of this disclosure, a method is provided to report to a base station the remaining time of data stored in the transmission buffer of a UE and the corresponding amount of data, and to use the remaining time and amount of data for uplink scheduling of the base station.

[0060] A UE may trigger a buffer status report (BSR) in the corresponding cell group when one of the following conditions is met:

[0061] - Condition 1-1: New uplink (UL) data is generated on a logical channel (LCH) belonging to a logical channel group (LCG). In this case, the priority of the corresponding LCH is higher than that of other LCHs containing UL data. In this case, the triggered regular BSR can be considered to be triggered by the LCH that has already generated new UL data.

[0062] - Condition 1-2: When new uplink (UL) data has been generated on a logical channel (LCH) belonging to a logical channel group (LCG), and no UL data existed on any LCH belonging to any LCG before the corresponding UL data was generated. In this case, the triggered regular BSR can be considered to be triggered by the LCH that has generated the new UL data.

[0063] -Condition 1-3: When the retxBSR-Timer expires, if UL data exists on at least one LCH, and the corresponding LCH belongs to the LCG, then the triggered regular BSR can be considered to have been triggered by the LCH with the highest priority among the LCHs containing UL data.

[0064] In the embodiments of this disclosure, when the logicalChannelSR-DelayTimer of the LCH that has triggered the corresponding regular BSR is not running in the state where a regular BSR has already been triggered, the UE may trigger a scheduling request (SR) corresponding to the corresponding LCH for the regular BSR when one of the following conditions is met.

[0065] -Condition 2-1: When there is no uplink shared channel (UL-SCH) resource available for the initial transmission (or new transmission).

[0066] -Condition 2-2: When the LCH of a MAC entity is configured with authorization and a regular BSR has been triggered, and is configured with a false logicalChannelSR-Mask, or

[0067] - Condition 2-3: When there are UL-SCH resources available for initial transmission, but due to logical channel priority (LCP) mapping restrictions, the UL-SCH resources may not be used for logical channels (LCH) that have already triggered regular BSR.

[0068] logicalChannelSR-Mask can be a parameter that controls SR triggering when configuring the authorization.

[0069] In embodiments of this disclosure, the UE can report the remaining time status of data in the transmission buffer to the base station via a specific MAC CE. For example, the MAC CE may be referred to as a Delay Status Report (DSR) MAC CE.

[0070] According to embodiments of this disclosure, the DSR MAC CE can be an extended MAC CE of the BSR MAC CE. For example, the DSR MAC CE can be based on the buffer size included in the BSR MAC CE for each LCG. For example, the DSR MAC CE can include information per LCG indicating whether or not an LCG buffer size field included in the BSR MAC CE is present.

[0071] According to embodiments of this disclosure, the DSR MAC CE may not include information included in the BSR MAC CE, which is separate from the BSR MAC CE.

[0072] According to embodiments of this disclosure, regarding DSR, the base station can configure at least one of the following information for a specific MAC entity (or cell group) of the UE via RRC messages:

[0073] Whether to report remaining time can be configured on a per-LCH basis. According to an embodiment, the LCH that reports remaining time can be referred to as dsr-lch.

[0074] - The remaining time reporting criteria for DSR can be configured. The corresponding criteria can be an upper or lower limit of the remaining time, or vice versa. For example, with an upper limit of the remaining time configured, the UE can report the remaining time for data whose remaining time is less than or equal to the configured upper limit. Similarly, with a lower limit of the remaining time configured, the UE can report the remaining time for data whose remaining time is greater than or equal to the configured lower limit. Furthermore, with either an upper or lower limit of the remaining time configured, the UE can report the remaining time for data whose remaining time is greater than or equal to the lower limit and less than or equal to the upper limit. For example, one or more remaining time criteria can be configured based on each LCH, each LCG, each MAC entity, or each UE.

[0075] - An upper limit can be configured for the number of remaining time fields. For example, an upper limit can be configured for the number of pairs of remaining time fields and remaining time-specific buffer size fields. The upper limit can be configured based on each LCH, each LCG, or for the entire DSRMAC CE. When an upper limit is configured for the number of fields, the DSR can include, on a per LCH, per LCG, or for the entire DSR, a number of remaining time fields or pairs of remaining time fields and remaining time-specific buffer size fields less than or equal to the upper limit configured by the base station.

[0076] - The remaining time standard for DSR triggering can be configured. For example, the remaining time standard for DSR triggering can be an upper or lower limit of the remaining time, or vice versa. The remaining time standard for DSR triggering can be configured based on each LCH, each LCG, each MAC entity, or each UE. For example, when no separate remaining time standard for DSR triggering is configured, the remaining time standard for DSR reporting can be determined by directly applying the DSR reporting remaining time standard of the corresponding LCH / LCG / MAC entity / cell group / UE, or by introducing a specific offset. The corresponding offset can be predetermined or configured by the base station via RRC.

[0077] According to embodiments, all remaining time-related values / fields / variables / parameters of this disclosure can be represented as integers with a specific time unit. The corresponding integer can represent absolute or relative time relative to a specific point in time. For example, the time unit can be one or more composite forms of units such as microseconds, milliseconds, seconds, symbols, subframes, and frames.

[0078] According to an embodiment, a predefined remaining time schedule can be specified in the specification, such that each index / code point included in the correspondence table can be defined to indicate a specific remaining time interval. Different indexes / code points in the remaining time schedule can indicate other remaining time intervals that do not overlap with each other. The maximum remaining time included in the correspondence table can be equal to the maximum value of discardTimer configured in the PDCP-Config of the 38.331 standard, or it can be a value with a specific offset from the corresponding maximum value. The last index / code point in the correspondence table can indicate all time intervals greater than or equal to the maximum remaining time. For example, when the remaining time schedule includes 2 k One index / code point, or including less than or equal to 2 k But greater than 2 k-1 When dealing with a number of indexes / code points, the remaining time field or minimum remaining time field of the DSR can have a length of k bits.

[0079] According to embodiments, all remaining time-related values / fields / variables / parameters of this disclosure can be represented by a specific index / code point of the remaining time schedule. For example, when the value indicated by the remaining time field of the DSR or the upper or lower limit of the remaining time configured by the base station is t, this can refer to the index / code point t of the remaining time schedule.

[0080] Figure 3 This is a diagram illustrating the buffer state of a UE based on each DSR-LCH according to an embodiment of the present disclosure, including the remaining time and corresponding amount of data stored in the buffer.

[0081] According to an embodiment, the UE can report the remaining time status of data in the corresponding LCH buffer, LCG buffer, or MAC entity / cell group buffer via DSR on a per-dsr-lch basis, on a per-LCG basis including at least one dsr-lch basis, or on a per-MAC entity / cell group basis including at least one dsr-lch basis. When the corresponding data exists, the remaining time status can indicate the corresponding remaining time interval by adding a remaining time field on a minimum granularity basis for each remaining time.

[0082] When the Remaining Time field indicates an index / code point in the remaining time schedule, the minimum remaining time granularity can be the interval indicated by each index / code point, or when the Remaining Time field indicates an integer with a specific time unit, the minimum remaining time granularity can be the corresponding time unit.

[0083] According to the embodiments, the remaining time, remaining time-specific buffer size, or on-demand buffer size reported via DSR can be reported only for the remaining data in the buffer of a specific LCH / LCG / MAC entity / cell group, excluding data included in the MAC PDU after assembling the MAC PDU including the DSR MAC CE.

[0084] A DSR MAC CE may include one or more of the following information:

[0085] -LCH or LCG indicator

[0086] 1) The LCG / LCH ID field or bit at a specific position in the bitmap can indicate the corresponding LCG / LCH. For example, the LCG / LCH indicator can be used to indicate the presence or absence of a remaining time field, a minimum remaining time field, a pair of (minimum) remaining time fields and a corresponding remaining time-specific buffer size field, or an on-demand buffer size field corresponding to the corresponding DSR MAC CE.

[0087] - Remaining Time Field

[0088] 1) When the base station configures the remaining time standard only based on each LCH, each LCG, or for the entire MAC entity / cell group, and does not configure an upper limit on the number of remaining time fields:

[0089] 2) When data corresponding to the buffer exists, the UE can indicate the remaining time interval only for data in the corresponding (one or more) dsr-lch buffers that meets the remaining time criterion, based on each LCH, each LCG, or the entire MAC entity / cell group, by adding a corresponding remaining time field based on each minimum remaining time granularity. (Reference) Figure 3 As an example, when the base station configures the remaining time limit for both LCH1 and LCH2 to 4 and performs remaining time reporting based on each LCG, there can be two remaining time fields (including LCH1 and LCH2) corresponding to LCG 0, and one remaining time field can indicate the remaining time 3 (reflecting the BS of LCH1). 1-3 And LCH 2's BS 2-3 Another indicator can show the remaining time 4 (reflecting the BS of LCH 2). 2-4 ).

[0090] 1) When the base station configures both the remaining time standard and the upper limit of the number of remaining time fields based on each LCH, each LCG, or for the entire MAC entity / cell group.

[0091] 2) When data corresponding to the buffer exists, the UE can indicate the remaining time interval only for data in the corresponding (one or more) dsr-lch buffers that meets the remaining time criterion, based on each LCH, each LCG, or the entire MAC entity / cell group, by adding a corresponding remaining time field based on each minimum remaining time granularity. For example, the number of remaining time fields based on each LCH, each LCG, or each MAC entity / cell group can reach the upper limit (or (upper limit - 1) of the number of remaining time fields configured by the base station based on each LCH, each LCG, or each MAC entity / cell group. For example, remaining time fields can be added in ascending order of remaining time, starting with the remaining time field with the shortest remaining time. (Reference) Figure 3 As an example, when the base station configures the upper limit of the remaining time for both LCH 1 and LCH 2 to 4, and configures the upper limit of the number of remaining time fields for LCG 0 to 1, there can be a remaining time field corresponding to LCG 0, which can indicate the remaining time of 3 (reflecting the BS of LCH 1). 1-3 And LCH 2's BS 2-3 ).

[0092] 1) When the base station does not configure the remaining time standard based on each LCH, each LCG, or for the entire MAC entity / cell group, but only configures the upper limit of the number of remaining time fields:

[0093] 2) When corresponding data exists in the corresponding (one or more) dsr-lch buffers, the UE can indicate the remaining time interval on a per-LCH, per-LCG, or for the entire MAC entity / cell group basis by adding the corresponding remaining time field on a minimum granularity basis. For example, the number of remaining time fields based on each LCH, each LCG, or each MAC entity / cell group can reach the upper limit (or (upper limit - 1) of the number of remaining time fields configured by the base station based on each LCH, each LCG, or each MAC entity / cell group. For example, remaining time fields can be added in ascending order of remaining time, starting with the remaining time field with the shortest remaining time. (Reference) Figure 3 As an example, when the base station configures the remaining time limit for LCH 0 to 1 and performs a remaining time report based on each LCG, there can be a remaining time field corresponding to LCG 0, which can indicate the remaining time 3 (reflecting the BS of LCH 1). 1-3 And LCH 2's BS 2-3 ).

[0094] - Minimum Remaining Time Field: For the data with the shortest remaining time in the corresponding DSR-LCH buffer(s), the UE can indicate the corresponding remaining time interval by adding a corresponding remaining time field, on a per-LCH, per-LCG, or for the entire MAC entity / cell group basis. The remaining time field can be referred to as the minimum remaining time field. For example, when the base station configures a remaining time standard, the minimum remaining time field can only be added if the corresponding remaining time interval meets the remaining time standard configured by the base station. (Reference) Figure 3 As an example, when the base station configures the remaining time limit for LCGs 0 to 4 and performs a remaining time report based on each LCG, LCG 0 can have a minimum remaining time field, and the corresponding field can indicate the remaining time of 3.

[0095] 1) Minimum Remaining Time Specific Buffer Size Field: When one or more remaining time fields exist corresponding to a specific LCH / LCG / MAC entity / cell group, or when a minimum remaining time field exists corresponding to a specific LCH / LCG / MAC entity / cell group, a (minimum) remaining time specific buffer size field may be included based on each remaining time or based on each minimum remaining time field to indicate how much data with remaining time belonging to the remaining time interval indicated by the corresponding field exists in the buffer of the corresponding LCH / LCG / MAC entity / cell group. Reference Figure 3As an example, when the base station configures a remaining time limit of 4 for LCG 0 and performs remaining time reporting based on each LCG, LCG 0 can have two remaining time fields, and the corresponding fields can indicate remaining times of 3 and 4 respectively. As an example, a remaining time-specific buffer size field can be added corresponding to the remaining time field indicating remaining time 3. In this case, the corresponding field can indicate the BS... 1-3 +BS 2-3 This corresponds to the buffer size for the remaining time 3. For example, a remaining time-specific buffer size field could be added corresponding to the remaining time field indicating the remaining time 4. In this case, the corresponding field could indicate BS. 2-4 , which is the buffer size corresponding to the remaining time of 4.

[0096] 1) On-Demand Buffer Size Field: When a base station configures a remaining time standard based on each LCH / LCG / MAC entity / cell group, it may include an on-demand buffer size field, which indicates the amount of data in the corresponding (one or more) dsr-lch buffers that satisfies the remaining time standard configured by the base station. The number of on-demand buffer size fields may exist based on each LCH / LCG / MAC entity / cell group, or based on each remaining time standard configured by the base station. For example, when a base station configures standard 1 with a remaining time upper limit of 1 and standard 2 with an upper limit of 2 and a lower limit of 2 for a specific LCH / LCG / MAC entity / cell group, there may be two on-demand buffer size fields corresponding to the corresponding LCH / LCG / MAC entity / cell group. For example, the first on-demand buffer size field may indicate the amount of data with remaining time satisfying standard 1, and the second on-demand buffer size field may indicate the amount of data with remaining time satisfying standard 2.

[0097] For example, the (minimum) remaining time-specific buffer size field or the on-demand buffer size field can reference a predefined buffer size table that defines an index for each buffer size range, and represent the index of the corresponding buffer size range in the corresponding table. The buffer size table can be a long BS (buffer size) table with an 8-bit buffer size field defined in the NR system, a short BS table with a 5-bit buffer size field, or one or more new BS tables that may be defined in the future. When multiple candidate BS tables exist, the BS table indicator indicating which BS table the corresponding (minimum) remaining time-specific buffer size field or on-demand buffer size field references can be included in the DSR MAC CE based on each (minimum) remaining time-specific buffer size field, each on-demand buffer size field, each LCH, each LCG, or each MAC entity / cell group.

[0098] Figure 4 This is a diagram illustrating a reference time for the remaining time indicated by the Remaining Time field or Minimum Remaining Time field of the DSR MAC CE, or applied by the On-Demand Buffer Size field, as an embodiment of this disclosure. According to an embodiment, the reference time for the remaining time can be interpreted as a concept indicating the point in time on which the corresponding remaining time is based.

[0099] refer to Figure 4 The UE can typically send a MAC PDU, including a DSR MAC CE, or a transport block (TB) to the base station via PUSCH resources allocated by the base station. According to an embodiment, the base station can dynamically schedule specific PUSCH resources to the UE via DCI. Alternatively, multiple periodic PUSCH resources can be allocated to the UE in a configured grant (CG) format. The reference time for the remaining time, indicated by the remaining time field or minimum remaining time field of the DSR MACCE, or applied by the on-demand buffer size field, can be one of the following options.

[0100] - The start of the first symbol of the PUSCH resource used for the initial transfer of the MAC PDU or TB corresponding to the DSR MAC CE (Figure reference 400).

[0101] - The end of the last symbol of the PUSCH resource used for the initial transmission of the MAC PDU or TB corresponding to the DSR MAC CE (Figure 410).

[0102] - The start of the time slot to which the PUSCH resource belongs for the initial transmission of the MAC PDU or TB corresponding to the DSR MAC CE (see attached reference 420).

[0103] - The end of the time slot to which the PUSCH resource belongs for the initial transmission of the MAC PDU or TB corresponding to the DSR MAC CE (see attached label 430).

[0104] According to the embodiments, PUSCH resources can be resources that are dynamically allocated by the base station through dynamic scheduling or resources that are configured and authorized by the base station.

[0105] According to embodiments, one or more reference time fields indicating a reference time for the remaining time can be added to the DSR. For example, the reference time field can be a field indicating a point in time upon which the remaining time value indicated by the DSR's remaining time field is calculated, or data indicated by the on-demand buffer size field. For example, the reference time field can indicate absolute or relative time based on a specific point in time. For example, the reference time field can be represented as one or a combination of units such as frames, subframes, time slots, or symbols. For example, the reference time field can indicate the entire UTC time or a specific location / number of bits / least significant bit (LSB) / most significant bit (MSB).

[0106] According to an embodiment, the remaining time field of the DSR can be a field indicating a relative difference from a specific remaining time upper limit configured by the base station, rather than an absolute remaining time. For example, the corresponding relative difference can be a value representing the difference obtained by subtracting the corresponding remaining time from the remaining time upper limit, indicating how many times smaller or larger the remaining time is relative to the remaining time upper limit when comparing the remaining time upper limit with the corresponding remaining time, or it can represent a percentage of the remaining time relative to the remaining time upper limit.

[0107] According to an embodiment, at a specific time point, the remaining time of the data in the dsr-lch buffer can be equal to the remaining time value of the PDCP discardTimer for the corresponding data at that time point, or it can be equal to the value obtained by applying a specific offset to the remaining time value of the PDCP discardTimer. The offset can be predefined or configured by the base station via RRC.

[0108] According to an embodiment, at a specific point in time, the remaining time of a specific PDU included in a specific PDU set can be considered as / configured as / or reconfigured as the remaining time of the PDU with the smallest remaining time among all PDUs included in the corresponding PDU set at the corresponding point in time, or the remaining time of the PDU generated first in the application, or the remaining time of the PDU that first arrives at the PDCP.

[0109] According to an embodiment, when PDU set integration processing information (PSIHI) is configured for a corresponding PDU set, at a specific point in time, the remaining time of a specific PDU included in a specific PDU set can be considered as / configured as / reconfigured as the remaining time of the PDU with the smallest remaining time among all PDUs included in the corresponding PDU set at the corresponding point in time, or the remaining time of the PDU generated first in the application, or the remaining time of the PDU that first arrives at the PDCP.

[0110] According to an embodiment, at a specific time point, when a PDU set-level PDCP discardTimer is configured for the corresponding PDU set, the remaining time of a specific PDU included in the specific PDU set can be regarded as / configured as / reconfigured as the remaining time of the PDU set-level PDCP discardTimer of the corresponding PDU set or a value obtained by applying a specific offset configured by the base station to the remaining time.

[0111] According to an embodiment, the conditions that trigger DSR MAC CE may include at least one of the following conditions.

[0112] - Generate data that meets the DSR trigger remaining time criteria in a specific DSR-LCH. In this case, a DSR MAC CE can be triggered when no data meeting the corresponding criteria exists in any of the DSR-LCH buffers. Data that meets the DSR trigger remaining time criteria can be generated due to the generation of new data that meets the corresponding criteria, or due to the reduction of the remaining time of existing data, thus satisfying the corresponding criteria. For example, a DSR triggered under the above conditions can be called a regular DSR.

[0113] - A DSR MAC CE can be triggered when data that meets the DSR trigger remaining time criterion is generated in a specific DSR-LCH, and the LCH priority of the corresponding data is higher than the LCH priority of other data that meet the corresponding criterion. Data that meets the DSR trigger remaining time criterion can be generated due to the generation of new data that meets the corresponding criterion, or due to the reduction of the remaining time of existing data, thus satisfying the corresponding criterion. For example, a DSR triggered under the above conditions can be called a regular DSR.

[0114] A DSR MAC CE can be triggered when data that meets the DSR trigger remaining time criterion is generated in a specific DSR-LCH, and the remaining time of the corresponding data is less than or equal to the remaining time of other data that meets the corresponding criterion. Data that meets the DSR trigger remaining time criterion can be generated due to the generation of new data that meets the corresponding criterion, or due to the reduction of the remaining time of existing data, thus satisfying the corresponding criterion. For example, a DSR triggered under the above conditions can be called a regular DSR.

[0115] - By configuring a DSR retransmission timer (e.g., retxDSR-Timer), a DSR MAC CE can be triggered when data satisfying the DSR trigger remaining time criterion exists in at least one dsr-lch at the expiration of the corresponding timer. For example, a DSR MAC CE can only be triggered if a dsr-lch containing data satisfying the corresponding criterion belongs to a specific LCG. For example, retxDSR-Timer can be a separate timer from retxBSR-Timer (BSR retransmission timer). For example, retxDSR-Timer can be the same timer as retxBSR-Timer (BSR retransmission timer). For example, the size of retxDSR-Timer can be configured by the base station via RRC based on each MAC entity / cell group. For example, a DSR triggered by the expiration of retxDSR-Timer can be considered as the LCH with the highest priority among the DSR-LCHs containing data satisfying the DSR trigger remaining time criterion being triggered at the expiration time of the corresponding timer. The corresponding timer can undergo Logical Channel Prioritization (LCP) for available UL-SCH resources, and can then be started / restarted when the UL-SCH resources include the DSR MAC CE and the corresponding subheading. For example, a DSR triggered by the expiration of a timer can be referred to as a regular DSR.

[0116] - A periodic DSR timer (e.g., periodicDSR-Timer) can be configured to trigger a DSR MAC CE when the corresponding timer expires. For example, the corresponding timer can be a separate timer from the periodicBSR-Timer (periodic BSR timer). For example, the corresponding timer can be the same timer as the periodicBSR-Timer (periodic BSR timer). For example, the corresponding timer can undergo logical channel priority (LCP) ordering of available UL-SCH resources and then start / restart when the UL-SCH resources include a DSR MAC CE and the corresponding sub-header instead of a truncated DSR. For example, the size of the periodicSR-Timer can be configured by the base station via RRC based on each MAC entity / cell group. For example, when the size of the corresponding timer is configured to infinity, the corresponding timer may not expire, and therefore, DSR triggering may not occur due to the expiration of the corresponding timer.

[0117] - When padding bits are generated as a result of LCP for a specific UL-SCH, a padded DSR can be triggered instead of the padding bits if data satisfying the DSR trigger remaining time criterion exists in at least one dsr-lch. For example, a truncated DSR can refer to a DSR MAC CE where only a portion of the DSR field is sent when the padding bits are insufficient to accommodate the entire DSR field in a padded DSR sent using the padding bits.

[0118] According to an embodiment, when there is at least one regular DSR that has not been canceled after being triggered, the SR triggering condition for the corresponding regular DSR may include at least one of the following conditions.

[0119] - When no available UL-SCH resource exists for the new transfer.

[0120] - When a UL-SCH resource is available, but due to LCP, the corresponding UL-SCH resource may not be used for an LCH that has already triggered the corresponding DSR.

[0121] - When there are no available UL-SCH resources for an LCH that has already triggered the corresponding DSR within a specific time period starting from the time the corresponding DSR is triggered. The specific time period can be predefined or configured by the base station via RRC.

[0122] According to an embodiment, the base station can configure a common SR configuration for regular DSRs triggered by all DSR-LCHs via RRC messages on a per-specific MAC entity / cell group basis, and may include a SchedulingRequestId (e.g., schedulingRequestID-DSR-r18) for the DSR, which indicates the SR corresponding configuration in the corresponding cell group configuration information.

[0123] According to an embodiment, the base station may include a ScheduledRequestId in the configuration information of the corresponding dsr-lch, which is based on the SR configuration of the regular DSR triggered by the corresponding dsr-lch for each dsr-lch.

[0124] The conditions under which all DSRs triggered before the assembly of a specific MAC PDU and all sr triggered by DSRs are cancelled, and the sr-ProhibitTimers corresponding to the cancelled sr are stopped, may include at least one of the following conditions:

[0125] - When the corresponding MAC PDU is sent and the UL authorization of the corresponding MAC PDU can accommodate all pending data in the buffer, but is insufficient to accommodate the additional DSR MAC CE and the corresponding subheader.

[0126] - When the corresponding MAC PDU is sent, the corresponding MAC PDU includes a DSR MAC CE, and the remaining time status and / or buffer size status reported by the corresponding DSR MAC CE reflect all / most recent DSR triggering events that have occurred before the corresponding MAC PDU was assembled.

[0127] - When the corresponding MAC PDU is sent and the corresponding MAC PDU can hold all pending data that meets the remaining time standard configured by the base station, but is insufficient to hold the DSR MAC CE and the corresponding subheading.

[0128] - When no data meets the remaining time criterion configured by the base station in any of the DSR-LCHs of the corresponding MAC entity. For example, when generating data that meets the remaining time criterion, a timer with the same size as the remaining time can be configured. When the corresponding timer expires, it can be determined that the corresponding data no longer meets the remaining time criterion. For example, when the PDCPdiscardTimer expires, it can be considered that the corresponding data no longer meets the remaining time criterion.

[0129] When there is no valid PUCCH resource and random access for a DSR-triggered SR is in progress, the corresponding MAC entity may stop the corresponding random access under the following conditions:

[0130] - Random access can be stopped when there is a UL authorization assigned via a random access response or via a scheme other than the UL authorization used for MSGA payloads, and a MAC PDU including a (new) BSR or DSR MAC CE is sent using the UL authorization, and when the corresponding buffer status or remaining time status (delay / remaining time status) for all events that have triggered the (new) BSR or DSR is reported before assembling the corresponding MAC PDU via the (new) BSR or DSR MAC CE. For example, random access can be stopped when all pending data or all pending data that meets the remaining time criterion has been sent via the UL authorization.

[0131] Random access can stop when no data meets the remaining time criteria. For example, as the remaining time decreases, data that currently meets the remaining time criteria may no longer meet them. For example, when the PDCP DiscardTimer expires, data that currently meets the remaining time criteria may no longer meet them.

[0132] According to an embodiment, when a specific MAC PDU is sent, the corresponding MAC PDU includes a DSR MAC CE, and the remaining time status and / or buffer size status reported by the corresponding DSR MAC CE reflect all the most recent BSR triggering events that occurred before the assembly of the corresponding MAC PDU. All BSRs triggered before the assembly of the corresponding MAC PDU and / or SRs triggered by BSRs can be cancelled.

[0133] According to an embodiment, by assigning a new LCID or eLCID to the DSR MAC CE, the LCID or eLCID field in the MAC sub-header can be used to indicate that the corresponding MAC CE is a DSR MAC CE.

[0134] According to an embodiment, the priorities of DSR MAC CEs can be as follows (listed from the highest priority MAC CE to the lowest priority MAC CE):

[0135] - MAC CE for C-RNTI, or data from UL-CCCH;

[0136] - MAC CE for (enhanced) BFR, or MAC CE for authorization verification for configuration, or MAC CE for authorization verification for multi-entry configuration;

[0137] - MAC CE for authorization confirmation in side link configuration;

[0138] - MAC CE for LBT failure;

[0139] - MAC CE for scheduled advance reporting;

[0140] - MAC CE of SL-BSR prioritized according to Clause 5.22.1.6;

[0141] - MAC CE for (extended) BSR, excluding BSR for filling;

[0142] - MAC CE for DSR, excluding DSR for filling;

[0143] - MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;

[0144] - MAC CE used to locate the gap activation / deactivation request;

[0145] - MAC CE for the number of symbols expected to be protected;

[0146] - MAC CE for case 6 timed request;

[0147] - MAC CE for (extended) preemptive BSR;

[0148] - MAC CE for SL-BSR, in addition to SL-BSRs prioritized according to Clause 5.22.1.6 and including SL-BSRs for filling;

[0149] - MAC CE for IAB-MT recommended beam indication, or MAC CE for desired IAB-MT PSD range, or MAC CE for desired DL Tx power adjustment;

[0150] - Data from any logical channel, except for data from UL-CCCH;

[0151] - MAC CE for recommending bitrate queries;

[0152] -Includes MAC CE for filling BSR;

[0153] - Includes MAC CE for filling SL-BSR.

[0154] -Includes MAC CE for filling DSR;

[0155] According to an embodiment, the priorities of DSR MAC CEs can be as follows (listed from the highest priority MAC CE to the lowest priority MAC CE):

[0156] - MAC CE for C-RNTI, or data from UL-CCCH;

[0157] - MAC CE for (enhanced) BFR, or MAC CE for authorization verification for configuration, or MAC CE for authorization verification for multi-entry configuration;

[0158] - MAC CE for authorization confirmation in side link configuration;

[0159] - MAC CE for LBT failure;

[0160] - MAC CE for scheduled advance reporting;

[0161] - MAC CE for DSR, excluding DSR for filling;

[0162] - MAC CE of SL-BSR prioritized according to Clause 5.22.1.6;

[0163] - MAC CE for (extended) BSR, excluding BSR for filling;

[0164] - MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;

[0165] - MAC CE used to locate the gap activation / deactivation request;

[0166] - MAC CE for the number of symbols expected to be protected;

[0167] - MAC CE for case 6 timed request;

[0168] - MAC CE for (extended) preemptive BSR;

[0169] - MAC CE for SL-BSR, in addition to SL-BSRs prioritized according to Clause 5.22.1.6 and including SL-BSRs for filling;

[0170] - MAC CE for IAB-MT recommended beam indication, or MAC CE for desired IAB-MT PSD range, or MAC CE for desired DL Tx power adjustment;

[0171] - Data from any logical channel, except for data from UL-CCCH;

[0172] - MAC CE for recommending bitrate queries;

[0173] - Includes MAC CE for filling DSR.

[0174] -Includes MAC CE for filling BSR;

[0175] - Includes MAC CE for filling SL-BSR.

[0176] According to an embodiment, when determining the buffer size field value indicating buffer size information for a new BSR MAC CE or DSR MAC CE, when at least one candidate BS table can be referenced, and when indicating the corresponding buffer size in the candidate BS table, the BS table with the smallest quantization error can be referenced. For example, for each buffer size field / LCH / LCG / MAC CE, an indicator indicating which table in the candidate BS table is referenced can be included in the corresponding MAC CE for each buffer size field / LCH / LCG / MAC CE. For example, the value of the buffer size field can be 0. For example, the buffer size field can refer to the (minimum) remaining time-specific buffer size field, the on-demand buffer size field, or the buffer size field of the (new) BSR MAC CE. For example, the quantization error can represent the difference or absolute value of the difference between the actual amount of data in the buffer and the upper or lower limit of the buffer range indicated by the corresponding index / code point of the BS table. For example, the quantization error can refer to the size of the buffer size range indicated by the corresponding index / code point of the BS table, i.e., the difference or absolute value of the difference between the upper and lower limits.

[0177] According to an embodiment, to reduce quantization errors, in addition to the traditional BS tables used for existing 8-bit buffer size fields and 5-bit buffer size fields, a new BS table can be defined. For example, the corresponding new BS table can be called an NBT. For example, one or more NBTs can be predefined. For example, an NBT can have 2... L 1 index / code point. For example, L can be 8, 16, or a number greater than 16. For example, NBT can divide a predefined range of specific buffer sizes into 2. L Non-overlapping consecutive intervals, and an index / code point can be defined to indicate each interval. For example, 2 L Each interval in the intervals can indicate its upper or lower limit in the NBT. For example, 2 L Each interval can have the upper limit of the immediately preceding interval as its lower limit, and the lower limit of the immediately following interval as its upper limit. For example, when there is one NBT, the corresponding NBT can be set as the base NBT; when there are multiple NBTs, one of the NBTs can be set as the base NBT. For example, the base station can configure the NBTs that the UE can refer to when reporting BSR, new BSR, or DSR. For example, corresponding configurations can be set for each LCH / LCG / MAC entity / UE.

[0178] According to an embodiment, a new NBT consisting of a new buffer size range can be configured using a scheme of adding or subtracting a specific common offset to the buffer size range for each index / code point of the base NBT. For example, when the buffer size range indicated by the k-th index of the base NBT is L...k to U k When offset+H is applied, the buffer size indicated by the k-th index of the new NBT can be in the range L. k +H to U k +H. For example, the offset can be positive or negative.

[0179] According to an embodiment, the minimum buffer size B included in the basic NBT can be increased. min and maximum buffer size B max Multiply by (B) min ×F, B max ×F) or divided by (B) min / F, B max / F) A specific scaling factor F is used, and then the resulting buffer size range is divided into 2 L A new NBT is constructed using a range of buffer sizes corresponding to each index / code point. The range of buffer sizes can be divided into equal sizes or by applying an exponential function.

[0180] According to an embodiment, the selection of the basic NBT can be determined by the base station and then notified to the UE via an RRC message or MAC CE. For example, the selection of the basic NBT can be determined by the UE and then reported to the base station via an RRC message or MAC CE.

[0181] According to an embodiment, the base station can configure one or more offset values ​​for the UE via RRC messages or MAC CE that can be added to or subtracted from the base NBT. For example, the base station can configure one or more scaling factor values ​​for the UE via RRC messages or MAC CE that can be multiplied or divided by the base NBT.

[0182] According to an embodiment, when determining the value of the corresponding buffer size field, the UE may include an indicator in the (new) BSR or DSR MAC CE that indicates which candidate BS table (traditional BS table or NBT) the UE references for each buffer size field / LCH / LCG / MAC entity. The corresponding indicator may be an index / number of the BS table, or, when the corresponding BS table is an NBT obtained by applying a specific offset or scaling factor based on the underlying NBT, it may include an indicator indicating the corresponding offset or scaling factor, or an indicator indicating the index of the corresponding NBT or the applied offset or scaling factor.

[0183] According to an embodiment, the UE's MAC layer can request, from each of the UE's RLC and PDCP layers, how much data in the corresponding layer's buffer meets a specific remaining time criterion. For example, when the UE reports the amount of data meeting a specific remaining time criterion based on each LCH / LCG / MAC entity / cell group, the corresponding data amount can refer to the total amount of data in the buffers of the corresponding UE's RLC and PDCP layers based on each LCH / LCG / MAC entity / cell group that meets the corresponding criterion.

[0184] According to an embodiment, when the UE's MAC requests the amount of data that meets a specific remaining time standard from the RLC layer, the RLC layer may include at least one of the following data when determining the amount of data that meets the corresponding remaining time standard.

[0185] - RLC SDUs and RLC SDU segments that are not yet included in the RLC data PDUs and meet the corresponding remaining time criteria.

[0186] - RLC data PDUs awaiting initial transmission and meeting the corresponding remaining time standard.

[0187] - In RLC AM mode, RLC data PDUs wait for RLC retransmission and meet the corresponding remaining time standard.

[0188] According to the embodiments, the scheme / method for determining whether a specific RLC SDU / SDU segment / data PDU meets a specific remaining time criterion can be determined by the internal implementation of the UE.

[0189] According to the embodiment, whether a specific RLC SDU / SDU segment / data PDU meets a specific remaining time standard can be determined based on whether the remaining time of the PDCP DiscardTimer of the corresponding RLC SDU / SDU segment / data PDU meets the corresponding remaining time standard. For example, the UE's internal implementation can determine how much remaining time to leave for the PDCP DiscardTimer of the RLC SDU / SDU segment / data PDU.

[0190] According to an embodiment, when the UE's MAC requests the amount of data that meets a specific remaining time standard from the PDCP layer, the PDCP layer may include at least one of the following data when determining the amount of data that meets the corresponding remaining time standard.

[0191] - PDCP SDUs that have not yet been assembled and meet the corresponding remaining time standard.

[0192] - PDCP data PDUs that have not yet been delivered to the lower layer (MAC or RLC) and meet the corresponding remaining time criteria.

[0193] - Waiting for retransmissions caused by PDCP entity reconstruction in AM DRB and PDCPSDU that meet the corresponding remaining time standard.

[0194] - Waiting for retransmissions of PDCP data PDUs caused by the recovery of PDCP data in AM DRB and meeting the corresponding remaining time standard.

[0195] According to an embodiment, when a PDCP entity associated with at least two RLC entities notifies a MAC entity of the amount of DPCP data that meets a specific remaining time criterion, the corresponding PDCP entity can operate as follows:

[0196] -For radio bearers (RBs) with PDCP replication activated:

[0197] 1) The data volume of the corresponding PDCP entity that meets the corresponding remaining time standard can be notified to the MAC entity associated with the main RLC entity.

[0198] 1) The remaining data in the corresponding PDCP entity that meets the corresponding remaining time standard, excluding the PDCP control PDU, can be notified to the MAC entity associated with the RLC entity that is activated for the remaining PDCP replication, other than the main RLC entity.

[0199] 1) The amount of data that meets the corresponding remaining time standard can be notified as zero to the MAC entity associated with the RLC entity that is deactivated for PDCP replication.

[0200] - When PDCP replication is performed on a deactivated RB or a dual active protocol stack (DAPS) bearer:

[0201] 1) When a separate secondary RLC entity is configured, and the total amount of PDCP data and RLC data used for initial transmission in both the primary RLC entity and the separate secondary RLC entity that meet the corresponding remaining time standard is greater than or equal to a specific threshold configured by the base station:

[0202] 2) The amount of PDCP data that meets the corresponding remaining time criterion can be notified to the MAC entity associated with the primary RLC entity and the separate auxiliary RLC entity. For example, the amount of PDCP data that meets the corresponding remaining time criterion can be notified as 0 to the MAC entity associated with RLC entities other than the primary RLC entity and the separate auxiliary RLC entity.

[0203] 1) When the corresponding PDCP sending entity is a DAPS bearer:

[0204] 2) When uplink data handover is not requested:

[0205] 3) The amount of PDCP data that meets the corresponding remaining time standard can be notified to the MAC entity associated with the source cell.

[0206] 2) When requesting uplink data switching:

[0207] 3) The amount of PDCP data that meets the corresponding remaining time standard can be notified to the MAC entity associated with the target cell.

[0208] 1) Other situations:

[0209] 2) The amount of PDCP data that meets the corresponding remaining time standard can be notified to the MAC entity associated with the main RLC entity.

[0210] 2) The amount of PDCP data that meets the corresponding remaining time standard can be notified as 0 to the MAC entity associated with other RLC entities besides the main RLC entity.

[0211] Figure 5 This diagram illustrates the process by which a base station and a UE, according to an embodiment of this disclosure, confirm whether the UE supports DSR and configure DSR-related settings via RRC signaling. (Refer to...) Figure 5 In step 520, the base station may transmit / send a UECapabilityEnquiry message requesting a capability report to the UE in the RRC_CONNECTED state. The base station may include a UE capability query for each Radio Access Technology (RAT) type in the UECapabilityEnquiry message. The UE capability query for each RAT type may include information about the requested frequency band. Additionally, when requesting the UE to generate a UECapabilityInformation message via the UECapabilityEnquiry message, the base station may include filtering information indicating conditions and limitations. In this case, the base station may indicate to the UE whether UE Report DSR support is required based on the filtering information.

[0212] In step 530, the UE may construct a UECapabilityInformation message corresponding to the UECapabilityEnquiry message and report its response to the UECapabilityEnquiry message to the base station. In this case, the UECapabilityInformation message may include a parameter / indicator indicating whether the UE supports DSR. For example, the parameter or indicator may be 1 bit of information. According to another embodiment, when the parameter or indicator is included, it may indicate that DSR is supported, and when the parameter or indicator is not included, it may indicate that DSR is not supported.

[0213] The base station can determine whether the UE supports DSR based on the received UECapabilityInformation message. When the base station determines that the UE supports DSR, in step 540, the base station can indicate the DSR-related configuration by including DSR-related configuration in the RRCReconfiguration message. The corresponding UE can apply the DSR-related configuration information included in the received RRCReconfiguration message. The DSR-related configuration can include all DSR-related configurations that the base station can configure for the UE, as described above in this disclosure.

[0214] Figure 6 This is a block diagram illustrating the configuration of a base station according to an embodiment of the present disclosure. (See reference...) Figure 6 The base station may include a transceiver 610, a controller 620, and a memory 630. In this disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0215] Transceiver 610 can send signals to and receive signals from other network entities. Transceiver 610 can send and receive, for example, RRC messages from and from a terminal. Furthermore, transceiver 610 can receive MAC CEs from the UE.

[0216] According to embodiments of this disclosure, controller 620 can control the overall operation of the base station. For example, controller 620 can control the signal flow between each block to perform operations according to the flowchart above. Specifically, controller 620 can configure DSR trigger remaining time criteria for any MAC entity or cell group of the UE via RRC messages. Alternatively, according to embodiments of this disclosure, controller 620 can control the uplink transmission resources allocated to the UE based on the DSR MAC CE received from the UE.

[0217] The memory 630 may store at least one of information transmitted and received by the transceiver 610 and information generated by the controller 620. For example, the memory 630 may store information based on DSR MAC CE received from the UE according to embodiments of the present disclosure, or information regarding uplink transmission resources allocated to the UE.

[0218] at the same time, Figure 7 This is a block diagram illustrating the configuration of a terminal according to an embodiment of the present disclosure. (See reference...) Figure 7 The terminal may include a transceiver 710, a controller 720, and a memory 730. In this disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0219] Transceiver 710 can send signals to and receive signals from other network entities. Transceiver 710 can send and receive, for example, RRC messages to and from the base station. Additionally, transceiver 710 can send MAC CE messages to the base station.

[0220] The controller 720 can control the overall operation of the terminal according to the embodiments proposed in this disclosure. For example, the controller 720 can control the signal flow between each block to perform operations according to the flowchart above. Specifically, according to the embodiments of this disclosure, the controller 720 can confirm the remaining time of data stored in the UE's transmit buffer and the corresponding amount of data, and control the UE to report the confirmed remaining time and amount of data to the base station.

[0221] The memory 730 may store at least one of the information transmitted and received by the transceiver 710 and the information generated by the controller 720. For example, the memory 730 may store information based on DSR MAC CE according to embodiments of the present disclosure, or information about uplink transmission resources allocated from the base station.

[0222] Figure 8 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure.

[0223] In step S810, the UE can confirm information about the remaining time of the data stored in the transmission buffer and the amount of data corresponding to the remaining time.

[0224] In step S820, the UE can generate a MAC CE, which includes information about the remaining time of the data stored in the acknowledged transmission buffer and the amount of data corresponding to the remaining time. The MAC CE may be referred to as a Delay Status Report (DSR) MAC CE.

[0225] In step S830, the UE can send the generated MAC CE to the base station.

[0226] In step S840, the UE can receive uplink authorization related to uplink scheduling information from the base station.

[0227] In step S850, the UE can generate uplink data based on uplink authorization and send it to the base station.

[0228] at the same time, Figure 9 This is a flowchart illustrating the operation of a base station according to an embodiment of the present disclosure.

[0229] In step S910, a MAC CE can be received from the UE. This MAC CE includes information about the remaining time of data stored in the transmission buffer and the amount of data corresponding to the remaining time. The MAC CE may be referred to as a Delay Status Report (DSR) MAC CE.

[0230] In step S920, the base station may send an uplink grant related to uplink scheduling information to the UE.

[0231] In step S930, when uplink data is generated by the UE based on uplink authorization, the base station can receive uplink data from the UE.

[0232] Furthermore, according to embodiments of this disclosure, the base station can configure whether to report the remaining time of a specific MAC entity (or cell group) of the UE via DSR via RRC messages based on each LCG or each LCH. For example, an LCG / LCH configured to report the remaining time via DSR can be referred to as dsr-lcg / dsr-lch. For example, the RRC message may include a list of LCGs / LCHs that include LCGs / LCHs to be configured as dsr-lcg / dsr-lch. For example, when a specific LCG is configured as dsr-lcg, remaining time reporting via DSR can be performed on data from all LCHs included in the corresponding LCG. For example, when there is at least one LCG / LCH configured as dsr-lcg / dsr-lch for a specific MAC entity / cell group, the UE can generate a DSR MAC CE in the corresponding MAC entity / cell group. Conversely, when there is no LCG / LCH configured for dsr-lcg / dsr-lch for a specific MAC entity / cell group, the UE can be considered configured not to generate DSR MAC CE in the corresponding MAC entity / cell group.

[0233] For example, a base station can use specific fields in the configuration information for the corresponding MAC entity to configure whether to generate a DSR MAC CE for a specific MAC entity of the UE via an RRC message. For example, when the field has a specific value, it can be configured to generate a DSR, and when the field has another value, it can be configured not to generate a DSR. For example, whether to generate a DSR can be configured based on the presence or absence of a field in the RRC message. For example, when the field exists, a DSR can be generated, and when the field does not exist, a DSR can be configured not to be generated. For example, when the field exists, a DSR can not be generated, and when the field does not exist, a DSR can be configured to be generated.

[0234] In embodiments of this disclosure, one or more DSR trigger remaining time criteria can be configured in the RRC message on a per LCG or per LCH basis. For example, when configuring a DSR trigger remaining time criterion based on each LCG, all DSR-LCHs or all LCHs of the corresponding LCG can be applied to DSR triggering with the same remaining time criterion. For example, a DSR trigger remaining time criterion may include only the upper limit of the DSR trigger remaining time, only the lower limit of the DSR trigger remaining time, or both the upper and lower limits of the DSR trigger remaining time. For example, when the DSR trigger remaining time criterion for a specific LCG / LCH only includes the upper limit of the remaining time, if the remaining time of the data (PDU set or PDU) of the corresponding LCG / LCH is less than or equal to the upper limit of the remaining time, the corresponding data can be considered to meet the DSR trigger remaining time criterion. For example, when the DSR trigger remaining time criterion for a specific LCG / LCH only includes the lower limit of the remaining time, if the remaining time of the data (PDU set or PDU) of the corresponding LCG / LCH is greater than or equal to the lower limit of the remaining time, the corresponding data can be considered to meet the DSR trigger remaining time criterion. For example, when the DSR trigger remaining time criterion for a specific LCG / LCH includes both an upper and lower limit of remaining time, if the remaining time of the corresponding LCG / LCH data (PDU set or PDU) is less than or equal to the upper limit of remaining time and greater than or equal to the lower limit of remaining time, then the corresponding data can be considered to meet the DSR trigger remaining time criterion.

[0235] In embodiments of this disclosure, the base station can configure one or more LCG / LCHs as dsr-lcg or dsr-lch via RRC messages, based on a scheme that configures one or more LCG / LCHs with one or more DSR trigger remaining time standards for each LCG / LCH. For example, when the base station configures at least one LCG / LCH as dsr-lcg / dsr-lch for a specific MAC entity / cell group, the UE can generate a DSR MAC CE in the corresponding MAC entity / cell group. On the other hand, when there are no LCG / LCHs configured with DSR trigger remaining time standards for a specific MAC entity / cell group, the UE may not generate a DSR MAC CE in the corresponding MAC entity / cell group.

[0236] At a specific point in time, the remaining time of all PDUs included in a specific PDU set can be calculated using the remaining PDU set delay budget (PSDB) or remaining access network (AN) PSDB of the PDU set at the corresponding point in time, or it can be obtained as a value obtained by applying a specific offset to the corresponding remaining time value. The offset can be predefined or can be configured by the base station via RRC.

[0237] For example, the PSDB for a specific QoF stream can be defined as follows:

[0238] - The PDU set delay budget (PSDB) defines the upper limit of the delay that the PDU set may experience during transmission between the UE and the N6 termination point at the UPF. It is the duration between the reception time of the first PDU (at the N6 termination point for DL ​​or at the UE for UL) and the time when all PDUs in the PDU set have been successfully received (at the UE for DL ​​or at the N6 termination point for UL).

[0239] In embodiments of this disclosure, the access network (AN) PSDB for a specific QoS flow can be calculated as a value obtained by subtracting the core network (CN) PDB for the corresponding QoS flow from the PSDB for the corresponding QoS flow.

[0240] When the UE's MAC requests the size of data that meets a specific remaining time criterion (e.g., upper remaining time limit, lower remaining time limit, or both), and when the RLC or PDCP entity calculates the size of data that meets the corresponding remaining time criterion, data units (e.g., PDCP SDUs, PDCP PDUs, RLC SDUs, RLC PDUs, RLC SDU segments) that do not have a PDCP discardTimer configured or are configured to be infinite may not be included in the corresponding data size. For example, since a PDCP control PDU may not have a discardTimer configured, data units that include the corresponding data can be excluded when the PDCP or RLC entity calculates the size of data that meets the remaining time criterion. For example, when calculating the size of data that meets the remaining time criterion in the RLC or PDCP entity, data units that correspond to signaling radio bearers (SRBs) without a discardTimer or data that correspond to data radio bearers (DRBs) with a discardTimer configured to be infinite can be excluded. For example, in the case of RLC AM, when calculating the size of data that meets a specific remaining time criterion reported via DSR, the UE can exclude the size of data waiting for RLC retransmission.

[0241] According to an embodiment, for a specific DSR-lcg, the condition for triggering DSR can be at least one of the following conditions:

[0242] - When data that meets the DSR trigger remaining time standard for the corresponding LCG is generated in the DSR-LCH belonging to a specific DSR-lcg, and DSR has not yet been triggered for the corresponding DSR-lcg, DSR can be triggered for the corresponding DSR-lcg.

[0243] - Generate data that meets the DSR trigger remaining time criteria for the corresponding LCG in the DSR-LCH belonging to a specific DSR-lcg. In this case, if there is no data that meets the corresponding criteria in the buffers of all DSR-LCHs in the corresponding DSR-lcg, the DSR can be triggered for the corresponding DSR-lcg.

[0244] - When data that meets the DSR triggering remaining time criteria for the corresponding LCG is generated in a DSR-LCH belonging to a specific DSR-lcg, and the LCH priority of the corresponding DSR-LCH is higher than the LCH priority of other DSR-LCHs that meet the corresponding remaining time criteria of the corresponding DSR-lcg, the DSR can be triggered for the corresponding DSR-lcg.

[0245] - When data that meets the DSR triggering remaining time criteria for the corresponding LCG is generated in a DSR-LCH belonging to a specific DSR-lcg, and the remaining time of the corresponding data is less than or equal to the remaining time of data that meets the corresponding criteria of other DSR-LCHs of the corresponding DSR-lcg, the DSR can be triggered for the corresponding DSR-lcg.

[0246] The methods described in the claims or specification of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0247] When implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device. The one or more programs include instructions for causing the electronic device to perform methods according to the embodiments described in the claims or specification of this disclosure.

[0248] Such programs (software modules, software) can be stored in random access memory, including non-volatile memory such as flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile optical disc (DVD), any other form of optical storage device, and magnetic tape cassettes. Alternatively, it can be stored in a memory consisting of some or all of these components. Furthermore, each memory component can include multiple components.

[0249] Additionally, the program can be stored in an attachable storage device accessible via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or a combination thereof. Such a storage device can be connected to a device implementing embodiments of this disclosure via an external port. Furthermore, a separate storage device on the communication network can be connected to a device implementing embodiments of this disclosure.

[0250] In the specific embodiments of this disclosure described above, the components included in this disclosure are represented in a singular or plural form according to the presented specific embodiments. However, the singular or plural expression is appropriately chosen for the context presented for ease of description, and this disclosure is not limited to singular or plural components, and even if a component is expressed in a plural form, the component may be configured in a singular form, or even if a component is expressed in a singular form, the component may be configured in a plural form.

[0251] Although this disclosure has been described in conjunction with exemplary embodiments thereof, various modifications and changes may be made without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be construed as limited to the described exemplary embodiments, but rather as defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Receive a control message from the base station, the control message including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG); The DSR for LCG is triggered based on information about the remaining time. The DSR Media Access Control (MAC) control element (CE) used to trigger the DSR includes a remaining time field and a buffer size field; and Send DSR MAC CE to the base station.

2. The method according to claim 1, wherein, The remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer used for any LCG.

3. The method according to claim 1, wherein, The buffer size field corresponds to the amount of data associated with the RLC entity and PDCP entity, determined based on information about the remaining time.

4. The method according to claim 3, wherein, The amount of data associated with an RLC entity is determined based on at least one RLCSDU and RLC SDU segment and an RLC data PDU, wherein the at least one RLC SDU and RLC SDU segment are not assembled into an RLC data PDU and satisfy a condition based on information about the remaining time related to the value of the PDCP discard timer, and the RLC data PDU includes at least one RLC SDU and RLC SDU segment that satisfy the condition based on information about the remaining time related to the value of the PDCP discard timer and is awaiting initial transmission.

5. The method according to claim 3, wherein, The amount of data associated with a PDCP entity is determined based on PDCP SDUs and PDCP data PDUs, wherein the PDCP SDUs are not assembled into PDCP data PDUs and satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer, and the PDCP data PDUs are not sent to the lower layer and include PDCP SDUs that satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer.

6. The method according to claim 1, wherein, The DSR MAC CE also includes an LCG indicator that indicates the LCG corresponding to the remaining time field and the buffer size field, as well as information about the remaining time in milliseconds.

7. A method performed by a base station in a wireless communication system, comprising: Send a control message to the terminal, the control message including information about the remaining time for triggering the Delay Status Report (DSR) for the Logical Channel Group (LCG); and When the DSR used for LCG is triggered based on information about the remaining time, the DSR Media Access Control (MAC) control element (CE) including the remaining time field and the buffer size field is received from the terminal. Wherein, the remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer for any LCG, and The buffer size field corresponds to the amount of data associated with the RLC entity and PDCP entity, determined based on information about the remaining time.

8. A terminal in a wireless communication system, comprising: transceiver; and The controller is configured to receive control messages from the base station via the transceiver, the control messages including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG); Based on information about the remaining time, the triggering of the DSR used for LCG is controlled. The DSR Media Access Control (MAC) control element (CE) for triggering the DSR includes a remaining time field and a buffer size field; and The transceiver controls the transmission from the DSR MAC CE to the base station.

9. The terminal according to claim 8, wherein, The remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer used for any LCG.

10. The terminal according to claim 8, wherein, The buffer size field corresponds to the amount of data associated with the RLC entity and PDCP entity, determined based on information about the remaining time.

11. The terminal according to claim 10, wherein, The amount of data associated with an RLC entity is determined based on at least one RLCSDU and RLC SDU segment and an RLC data PDU, wherein the at least one RLC SDU and RLC SDU segment are not assembled into an RLC data PDU and satisfy a condition based on information about the remaining time related to the value of the PDCP discard timer, and the RLC data PDU includes at least one RLC SDU and RLC SDU segment that satisfy the condition based on information about the remaining time related to the value of the PDCP discard timer and is awaiting initial transmission.

12. The terminal according to claim 10, wherein, The amount of data associated with a PDCP entity is determined based on PDCP SDUs and PDCP data PDUs, wherein the PDCP SDUs are not assembled into PDCP data PDUs and satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer, and the PDCP data PDUs are not sent to the lower layer and include PDCP SDUs that satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer.

13. The terminal according to claim 8, wherein, The DSR MAC CE also includes an LCG indicator that indicates the LCG corresponding to the remaining time field and the buffer size field, as well as information about the remaining time in milliseconds.

14. A base station in a wireless communication system, comprising: transceiver; and The controller is configured to send control messages to the terminal via the transceiver, the control messages including information about the remaining time for triggering a Delay Status Report (DSR) for a Logical Channel Group (LCG); When the DSR used for LCG is triggered based on information about the remaining time, the control receives a DSR Media Access Control (MAC) control element (CE) from the terminal via the transceiver, which includes a remaining time field and a buffer size field. Wherein, the remaining time field corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer for any LCG, and The buffer size field corresponds to the amount of data associated with the RLC entity and the PDCP entity, determined based on information about the remaining time.

15. The base station according to claim 14, wherein, The amount of data associated with an RLC entity is determined based on at least one RLCSDU and RLC SDU segment and an RLC data PDU, wherein the at least one RLC SDU and RLC SDU segment are not assembled into an RLC data PDU and satisfy a condition based on information about the remaining time related to the value of the PDCP discard timer, and the RLC data PDU includes at least one RLC SDU and RLC SDU segment that satisfy the condition based on information about the remaining time related to the value of the PDCP discard timer and is awaiting initial transmission. The amount of data associated with a PDCP entity is determined based on PDCP SDUs and PDCP data PDUs, wherein the PDCP SDUs are not assembled into PDCP data PDUs and satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer, and the PDCP data PDUs are not sent to the lower layer and include PDCP SDUs that satisfy conditions based on information about the remaining time related to the value of the PDCP discard timer.

Images