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 higher data transmission rates. According to the present disclosure, a base station can efficiently allocate uplink resources on the basis of information transmitted from a terminal.

Description

Method and device for reporting remaining time in a wireless communication system

[0001] The present invention relates to the operation of terminals and base stations in mobile communication systems. Specifically, the present invention relates to a method for enabling a base station to efficiently allocate uplink resources.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] With the development of mobile communication systems as described above, the need for terminals to report various information to base stations has emerged in order for base stations to efficiently allocate uplink resources.

[0009] The purpose of the present invention is to enable a base station to efficiently allocate uplink resources by transmitting various information, including information about the amount of data stored in the buffer of the terminal, to the base station.

[0010] According to one embodiment of the present disclosure for solving the above problem, a method performed by a terminal in a wireless communication system may include the steps of: receiving a control message including information on a remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) from a base station; triggering a DSR for the LCG based on the information on the remaining time, wherein a DSR medium access control (MAC) control element (CE) for the triggered DSR includes a remaining time field and a buffer size field; and transmitting the DSR MAC CE to the base station.

[0011] Meanwhile, according to another embodiment of the present disclosure, a method performed by a base station in a wireless communication system may include the steps of transmitting a control message including information on a remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) to a terminal, and receiving, from the terminal, a DSR medium access control (MAC) control element (CE) including a remaining time field and a buffer size field when a DSR for the LCG is triggered based on the information on the remaining time, wherein the remaining time field corresponds to a remaining time of a PDCP discard timer having a shortest remaining time among at least one PDCP discard timer running for any LCG, and the buffer size field may be characterized in that it corresponds to an amount of data associated with an RLC entity and a PDCP entity determined based on the information on the remaining time.

[0012] Meanwhile, according to another embodiment of the present disclosure, in a wireless communication system, a terminal may receive a control message including information on a remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) from a transceiver and a base station through the transceiver, and control to trigger a DSR for the LCG based on the information on the remaining time, wherein a DSR medium access control (MAC) control element (CE) for the triggered DSR includes a remaining time field and a buffer size field, and may include a control unit controlling to transmit the DSR MAC CE to the base station through the transceiver.

[0013] Meanwhile, according to another embodiment of the present disclosure, in a wireless communication system, a base station transmits a control message including information on a remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) to a transceiver and a terminal through the transceiver, and when a DSR for the LCG is triggered from the terminal based on the information on the remaining time, the control unit controls to receive, through the transceiver, a DSR medium access control (MAC) control element (CE) including a remaining time field and a buffer size field, wherein the remaining time field corresponds to a remaining time of a PDCP discard timer having a shortest remaining time among at least one PDCP discard timer running for any LCG, and the buffer size field corresponds to an amount of data associated with an RLC entity and a PDCP entity determined based on the information on the remaining time.

[0014] According to an embodiment of the present invention, a base station can efficiently allocate uplink resources based on information transmitted from a terminal.

[0015] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

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

[0017] FIG. 3 is a diagram illustrating the buffer status of a terminal according to one embodiment of the present disclosure, the remaining time of data in the buffer and the amount of corresponding data by delay status report (dsr)-logical channel (lch).

[0018] FIG. 4 is a diagram illustrating a reference point of the remaining time according to one embodiment of the present disclosure.

[0019] FIG. 5 is a diagram illustrating a procedure in which a base station and a terminal check whether a terminal supports DSR through RRC signaling and set DSR-related settings according to an embodiment of the present disclosure.

[0020] FIG. 6 is a block diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0021] FIG. 7 is a block diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0022] Figure 8 is a flowchart showing the operation of a terminal according to one embodiment of the present invention.

[0023] FIG. 9 is a flowchart illustrating the operation of a base station according to one embodiment of the present invention.

[0024] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0025] In describing the embodiments of this disclosure, descriptions of technical details that are well known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to more clearly convey the gist of this disclosure without obscuring it by omitting unnecessary explanations.

[0026] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0027] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0028] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0029] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0030] Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0031] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a 5G UE, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0032] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0033] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present disclosure is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0034] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0035] Referring to FIG. 1, the wireless communication system may be composed of multiple base stations (e.g., gNB (100), ng-eNB (110), ng-eNB (120), gNB (130)), an Access and Mobility Management Function (AMF) (140), and a User Plane Function (UPF) (150). Of course, the wireless communication system is not limited to the configuration illustrated in FIG. 1 and may include more or fewer components.

[0036] According to one embodiment of the present disclosure, a user equipment (hereinafter referred to as UE or terminal) (160) can access an external network through base stations (100, 110, 120, 130) and UPF (150).

[0037] In Fig. 1, base stations (100, 110, 120, 130) can serve as access nodes of a cellular network and provide wireless access to terminals accessing the network. For example, base stations (100, 110, 120, 130) can collect status information such as buffer status, available transmission power status, and channel status of terminals (160) to service user traffic, and perform scheduling based on the collected information to support connections between terminals and a core network (CN; in particular, the CN of NR is referred to as 5GC).

[0038] In Fig. 1, the gNB (100, 130) can control multiple cells and apply an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal (160).

[0039] The core network is a device responsible for various control functions, including mobility management for terminals, and can be connected to multiple base stations (100, 110, 120, 130). 5GC can also be integrated with existing LTE systems.

[0040] Meanwhile, in a wireless communication system, a user plane (UP) related to transmission of actual user data and a control plane (CP) such as connection management may be configured separately. The gNB (100) and gNB (130) of FIG. 1 may use the UP and CP technologies defined in NR technology, and the ng-eNB (110) and ng-eNB (120), although connected to 5GC, may use the UP and CP technologies defined in LTE (Long Term Evolution) technology.

[0041] AMF (140) is a device that is responsible for various control functions as well as mobility management functions for terminals (160) and can be connected to multiple base stations (100, 110, 120, 130).

[0042] UPF (150) may refer to a type of gateway device that provides data transmission. Although not illustrated in FIG. 1, the NR wireless communication system may also include a Session Management Function (SMF). The SMF can manage packet data network connections, such as protocol data unit (PDU) sessions, provided to the terminal (160).

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

[0044] Referring to FIG. 2, the wireless protocol of the NR system may be composed of SDAP (Service Data Adaptation Protocol) (200) (290), PDCP (Packet Data Convergence Protocol) (210) (280), RLC (Radio Link Control) (220) (270), MAC (Medium Access Control) (230) (260), and PHY (Physical) (240) (250) in the terminal and the base station, respectively.

[0045] SDAP (Service Data Adaptation Protocol) (200) (290) can perform operations for transmitting user data, mapping QoS (Quality Of Service) flows to specific DRBs (Data Radio Bearers) for uplink and downlink, marking QoS flow IDs (Identifiers) for uplink and downlink, and mapping reflective QoS flows to data bearers for uplink SDAP PDUs. SDAP settings corresponding to each DRB can be provided from a higher RRC layer. Of course, the present invention is not limited to the above examples.

[0046] PDCP (Packet Data Convergence Protocol) (210) (280) can handle operations such as IP (Internet Protocol) header compression / decompression. Furthermore, PDCP (210) (280) can provide sequential and out-of-order transmission functions, reordering, duplicate detection, retransmission, encryption, and decryption functions. Of course, the above examples are not limited thereto.

[0047] Radio Link Control (220)(270) can reconfigure PDCP Protocol Data Unit (PDU) to an appropriate size. In addition, RLC (220)(270) can provide sequential and out-of-order transmission functions, and can provide Automatic Repeat Request (ARQ) functions, joining, segmentation, reassembly functions, re-segmentation functions, reordering functions, duplicate detection functions, and error detection functions. Of course, the present invention is not limited to the above examples.

[0048] MAC (230) (260) is connected to multiple RLC layer devices configured in one terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. In addition, MAC (230) (260) can provide a mapping function, a scheduling information reporting function, a HARQ (Hybrid ARQ) function, a priority control function between logical channels, a priority control function between terminals, an MBMS service confirmation function, a transmission format selection function, and a padding function. Of course, it is not limited to the above examples.

[0049] The physical (PHY) layer (240)(250) channels and modulates upper layer data, converts it into an OFDM (Orthogonal Frequency Division Multiplexing) symbol, and transmits it through a wireless channel, or demodulates and channel decodes an OFDM symbol received through a wireless channel and transmits it to a higher layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiver transmits 1 bit whether or not the packet transmitted by the transmitter has been received. The 1 bit information is called HARQ ACK (Acknowledgement) / NACK (Negative ACK) information.

[0050] Downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the PHICH (Physical Hybrid-ARQ Indicator Channel) physical channel in the case of LTE, and in the case of NR, whether retransmission is necessary or new transmission can be performed through the UE's scheduling information in the PDCCH (Physical Dedicated Control CHannel), which is a channel through which downlink / uplink resource allocation, etc. are transmitted. This is because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted through the PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel) physical channel. PUCCH is generally transmitted in the uplink of the PCell (Primary Cell), which will be described later, but if the UE supports it, the base station may additionally transmit it to the UE from the SCell (Secondary Cell), which will be described later, and this is called the PUCCH SCell.

[0051] Although not shown in Figure 2, an RRC (Radio Resource Control) layer exists above the PDCP layer of each terminal and base station, and the RRC layer can transmit and receive connection and measurement-related setting control messages for radio resource control.

[0052] Meanwhile, the physical layer can be composed of one or more frequencies / carriers, and the technology that sets and uses multiple frequencies simultaneously is called carrier aggregation (CA). CA technology can dramatically increase the transmission capacity by the number of subcarriers by additionally using the main carrier and one or more subcarriers instead of using only one carrier for communication between a terminal (or User Equipment, UE) and a base station (eNB or gNB). Meanwhile, in LTE / NR, a cell within a base station that uses a main carrier is called a primary cell or PCell (Primary Cell), and a cell within a base station that uses a subcarrier is called a secondary cell or SCell (Secondary Cell).

[0053] In next-generation / 5G (New Radio, NR) wireless communication systems, terminals need to report their buffer status to the base station to help the base station more efficiently schedule resources. The Buffer Status Report (BSR) expresses and reports the amount of data stored in the terminal's buffer. According to the NR specification, the terminal selects an interval index containing the amount of buffer data to be reported from the range of interval data amounts defined by index in the Buffer Size Table and includes it in the BSR.

[0054] Buffer status reporting in NR systems can be performed based on MAC (Medium Access Control) layer signaling between the terminal and the base station. For example, when a BSR is triggered at a specific transmission point, the terminal can include a BSR control element (MAC CE) in the MAC PDU and transmit it to the base station. At this time, the BSR control element indicates the amount of packets remaining in the terminal's transmission buffer after the corresponding MAC PDU is configured, in units of Logical Channel Groups (LCGs). The base station can estimate the amount of data currently remaining in the terminal's buffer using the received BSR. In the NR system, the terminal can manage the data transmission buffer to be transmitted to the base station for each of eight LCGs.

[0055] XR (Extended Reality) uplink data has a delay budget, such as the remaining time. Data must arrive at the uplink server within a predetermined delay budget, based on the time generated by the terminal's application layer, to be considered valid. If it fails to arrive at the uplink server within the predetermined delay budget, the data loses its application value. The terminal buffer size reported by BSR is designed to report the total amount of data stored in the terminal's buffer. However, the base station does not know how much of the total data is closer to the deadline, i.e., how much of the remaining time is short. If the base station knows the remaining time of data in the terminal buffer and the corresponding amount of data for each remaining time, it can reflect this when allocating uplink resources, prioritizing transmission of data with a relatively short remaining time. Consequently, more data can be transmitted before the remaining time expires, improving cell capacity. On the other hand, if the remaining time for a specific data is very short, the time between the data being reported to the BSR and its actual transmission may be shorter than the remaining time. In this case, the data may be transmitted after it has lost its application value or may be discarded before transmission. Consequently, the allocated uplink resources may not contain valid data, resulting in resource waste. If the information reported to the base station includes the remaining time or the remaining time and data amount that satisfy predefined remaining time criteria (upper or lower bounds), the base station can utilize this information when allocating uplink resources to terminals, enabling more efficient resource allocation.

[0056] According to one embodiment of the present disclosure, a method is provided for reporting the remaining time of data stored in a transmission buffer of a terminal and the amount of data corresponding to the remaining time to a base station, and utilizing the information for uplink scheduling of the base station.

[0057] A terminal can trigger a BSR (Buffer Status Report) in the corresponding Cell Group when one of the following conditions is satisfied.

[0058] - Condition 1-1: When new UL (Uplink) data is generated on a Logical Channel (LCH) belonging to a Logical Channel Group (LCG), and the priority of the LCH is higher than that of other LCHs that have UL data. In this case, the triggered Regular BSR can be considered to have been triggered by the LCH that generated the new UL data.

[0059] - Condition 1-2: When new UL (Uplink) data is generated on a Logical Channel (LCH) belonging to a Logical Channel Group (LCG), and UL data does not exist on any LCH belonging to any LCG before the generation of the UL data. In this case, the triggered Regular BSR can be considered to have been triggered by the LCH where the new UL data was generated.

[0060] - Condition 1-3: When retxBSR-Timer expires, if UL data exists in at least one LCH and the LCH belongs to an LCG, the triggered Regular BSR can be considered to have been triggered by the LCH with the highest priority among the LCHs that contain the UL data.

[0061] In one embodiment of the present disclosure, when a Regular BSR has already been triggered and the logicalChannelSR-DelayTimer of the LCH that triggered the Regular BSR is not running, the terminal can trigger an SR (Scheduling Request) corresponding to the LCH for the Regular BSR if one of the following conditions is satisfied.

[0062] - Condition 2-1: When there are no UL-SCH (Uplink Shared Channel) resources for initial transmission (or new transmission)

[0063] - Condition 2-2: If the MAC Entity has configured grant(s) and the LCH that triggered the Regular BSR has logicalChannelSR-Mask set to false, or

[0064] - Condition 2-3: If there are UL-SCH resources for initial transmission, but due to LCP (Logical Channel Prioritization) mapping restriction, the UL-SCH resources cannot be used for the LCH that triggered the Regular BSR.

[0065] The above logicalChannelSR-Mask may be a parameter that controls SR triggering when a configured grant is set.

[0066] In one embodiment of the present disclosure, a terminal may report the remaining time status of data in a transmission buffer to a base station via a specific MAC CE. For example, the MAC CE may be referred to as a Delay Status Report (DSR) MAC CE.

[0067] According to one embodiment of the present disclosure, the DSR MAC CE may be an extended MAC CE of the BSR MAC CE. For example, the DSR MAC CE may include the buffer size per LCG reported in the BSR MAC CE. For example, the DSR MAC CE may include information indicating the presence or absence of the buffer size field per LCG included in the BSR MAC CE.

[0068] According to one embodiment of the present disclosure, the DSR MAC CE may not include information included in the BSR MAC CE, separate from the BSR MAC CE.

[0069] According to one embodiment of the present disclosure, in relation to DSR, a base station may set at least one of the following information for a specific MAC Entity (or Cell Group) of a terminal via an RRC message.

[0070] - Whether or not to report the remaining time can be set for each LCH. In one embodiment, the LCH that reports the remaining time can be called dsr-lch.

[0071] - A DSR reporting remaining time criterion can be set. The criterion can be an upper limit for remaining time, a lower limit, or both an upper limit and a lower limit. For example, if an upper limit for remaining time is set, the terminal can report the remaining time for data whose remaining time is less than or equal to the set upper limit for remaining time. For example, if a lower limit for remaining time is set, the terminal can report the remaining time for data whose remaining time is greater than or equal to the set lower limit for remaining time. For example, if an upper limit and a lower limit for remaining time are set, the terminal 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 of the above remaining time criteria can be set per LCH, per LCG, per MAC entity, or per terminal.

[0072] - The upper limit of the number of remaining time fields can be set. For example, the upper limit of the number of pairs of remaining time fields and remaining time-specific buffer size fields can be set. The upper limit of the number can be set for each LCH, each LCG, or the entire DSR MAC CE. When the upper limit of the number of fields is set, the DSR can include a number of remaining time fields or remaining time field and remaining time-specific buffer size field pairs that are less than or equal to the upper limit set by the maximum base station, for each LCH, each LCG, or the entire DSR.

[0073] - The DSR trigger remaining time criterion can be set. For example, the DSR trigger remaining time criterion can be a remaining time upper limit, a lower limit, or both. The DSR trigger remaining time criterion can be set for each LCH, LCG, MAC entity, or terminal. For example, if the DSR trigger remaining time criterion is not separately set, the DSR trigger remaining time criterion can be determined by directly applying the DSR report remaining time criterion of the corresponding LCH / LCG / MAC entity / Cell Group / terminal, or by introducing a specific offset. The offset can be determined in advance, or can be set by the base station through RRC.

[0074] According to one embodiment, all remaining time-related values / fields / variables / parameters of the present disclosure may be expressed in the form of integers having a specific time unit. The integers may express absolute time or relative time based on a specific point in time. For example, the time unit may have one or more composite forms of units such as microsecond, millisecond, second, symbol, subframe, and frame.

[0075] According to one embodiment, a pre-defined remaining time table may be specified in the specification, and each index / codepoint included in the table may indicate a specific remaining time interval. Different indexes / codepoints in the remaining time table may indicate different non-overlapping remaining time intervals. The maximum remaining time included in the table may be equal to the maximum value of the discardTimer set in the PDCP-Config of the 38.331 specification, or may be a value having a specific offset from the maximum value. The last index / codepoint of the table may indicate all time intervals greater than or equal to the maximum remaining time. For example, in the remaining time table, 2 k dog or 2 k Less than or equal to a dog but 2 k-1 When containing a number of indices / codepoints greater than k, the remaining time field or minimum remaining time field of the DSR may have a length of k-bits.

[0076] According to one embodiment, all remaining time-related values / fields / variables / parameters of the present disclosure may be expressed by a specific index / codepoint of the remaining time table. For example, when the value indicated by the remaining time field of the DSR or the upper or lower limit of the remaining time set by the base station is t, this may mean the index / codepoint t of the remaining time table.

[0077] FIG. 3 is a diagram illustrating an embodiment of the present disclosure, showing the buffer status of a terminal by dsr-lch, the remaining time of data in the buffer, and the amount of corresponding data.

[0078] According to one embodiment, the terminal may report the remaining time status of data in the LCH buffer, LCG buffer, or MAC Entity / Cell Group buffer for each dsr-lch, or for each LCG including at least one dsr-lch, or for each MAC Entity / Cell Group including at least one dsr-lch, via DSR. The remaining time status may indicate the remaining time interval by adding a remaining time field when corresponding data exists for each remaining time minimum granularity.

[0079] The minimum division interval of the above remaining time can be the interval indicated by each index / codepoint when the remaining time field indicates an index / codepoint of the remaining time table, and can be the time unit when an integer having a specific time unit is indicated.

[0080] In one embodiment, the remaining time or buffer size per remaining time or on-demand buffer size reported via DSR may be reported only for data remaining in a specific LCH / LCG / MAC Entity / Cell Group buffer, excluding data included in the MAC PDU after the MAC PDU including the DSR MAC CE is constructed.

[0081] A DSR MAC CE may contain one or more of the following information:

[0082] - LCH or LCG indicator

[0083] 1) The LCG / LCH ID field or a specific position bit of the Bitmap can be used to 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 corresponding to the corresponding DSR MAC CE, a minimum remaining time field, a pair of a (minimum) remaining time field and a buffer size field for each remaining time, or an on-demand buffer size field.

[0084] - Remaining time field

[0085] 1) If the base station sets only the remaining time criterion for each LCH, LCG, or MAC Entity / Cell Group and does not set an upper limit on the number of remaining time fields:

[0086] 2) The terminal may indicate the remaining time interval by adding the corresponding remaining time field when there is data corresponding to the buffer, only for the remaining time of data satisfying the remaining time criteria among the data in the corresponding (one or more) dsr-lch buffers for each LCH, LCG, or the entire MAC Entity / Cell Group. Referring to FIG. 3, as an example, if the base station sets the remaining time upper limit to 4 for both LCH 1 and LCH 2 and reports the remaining time for each LCG, there may be two remaining time fields corresponding to LCG 0 (including LCH 1 and LCH 2), each with a remaining time 3 (BS of LCH 1) 1-3 and BS of LCH 2 2-3 ) and 4 (BS of LCH 2) 2-4 ) can be directed to.

[0087] 1) If the base station sets both the remaining time criterion and the upper limit of the number of remaining time fields for each LCH, each LCG, or the entire MAC Entity / Cell Group:

[0088] 2) The terminal may indicate the remaining time section by adding the corresponding remaining time field for each minimum remaining time division interval, only for the remaining time of data satisfying the remaining time criteria among the data in the corresponding (one or more) dsr-lch buffers for each LCH, LCG, or MAC Entity / Cell Group, when there is data corresponding to the buffer. For example, the number of remaining time fields for each LCH, LCG, or MAC Entity / Cell Group may be the upper limit of the number of remaining time fields set for each LCH, LCG, or MAC Entity / Cell Group set by the base station, or up to (the upper limit of the number - 1). For example, the remaining time fields may be added in the order of increasing remaining time, starting from the remaining time field with the shortest remaining time. Referring to FIG. 3, for example, if the base station sets the upper limit of the remaining time for both LCH 1 and LCH 2 to 4 and sets the upper limit of the number of remaining time fields of LCG 0 to 1, there can be one remaining time field corresponding to LCG 0, and the remaining time 3 (BS of LCH 1) 1-3 and BS of LCH 2 2-3 ) can be directed to.

[0089] 1) If the base station does not set the remaining time criterion for each LCH or LCG or for the entire MAC Entity / Cell Group, but only sets the upper limit of the number of remaining time fields:

[0090] 2) The terminal may indicate the remaining time interval by adding the corresponding remaining time field to the minimum segmented interval of data in the corresponding (one or more) dsr-lch buffers for each LCH, LCG, or MAC Entity / Cell Group, if there is corresponding data. For example, the number of remaining time fields per LCH, LCG, or MAC Entity / Cell Group may be the upper limit of the number of remaining time fields set per LCH, LCG, or MAC Entity / Cell Group set by the base station, or (the upper limit - 1). For example, the remaining time fields may be added in the order of increasing remaining time, starting from the remaining time field with the shortest remaining time. Referring to FIG. 3, for example, when the base station sets the upper limit of the number of remaining time fields of LCG 0 to 1 and reports the remaining time for each LCG, there may be one remaining time field corresponding to LCG 0, and the remaining time 3 (BS of LCH 1) 1-3 and BS of LCH 2 2-3 ) can be directed to.

[0091] - Minimum remaining time field: The terminal may indicate the remaining time interval by adding a corresponding remaining time field to the remaining time interval to which the remaining time of the data with the shortest remaining time among the data in the corresponding (one or more) dsr-lch buffers belongs, for each LCH, each LCG, or the entire MAC Entity / Cell Group. The remaining time field may be referred to as a minimum remaining time field. For example, the minimum remaining time field may be added only when the corresponding remaining time interval satisfies the remaining time standard set by the base station when the base station sets the remaining time standard. Referring to FIG. 3, as an example, when the base station sets the remaining time upper limit of LCG 0 to 4 and reports the remaining time for each LCG, LCG 0 may have one minimum remaining time field, and the field may indicate a remaining time of 3.

[0092] 1) (Minimum) Buffer Size Field by Remaining Time: If there is one or more remaining time fields corresponding to a specific LCH / LCG / MAC Entity / Cell Group, or if there is a minimum remaining time field corresponding to a specific LCH / LCG / MAC Entity / Cell Group, a (minimum) Buffer Size by Remaining Time field may be included along with the remaining time or minimum remaining time field, indicating how much data with remaining time belonging to the remaining time interval indicated by the corresponding field is in the corresponding LCH / LCG / MAC Entity / Cell Group buffer. Referring to FIG. 3, as an example, if the upper limit of remaining time set by the base station for LCG 0 is 4 and remaining time reporting is performed for each LCG, LCG 0 may have two remaining time fields, and the fields may indicate remaining times 3 and 4, respectively. For example, one buffer size field for each remaining time corresponding to the remaining time field indicating the remaining time 3 may be added. In this case, the field is BS, which is the buffer size corresponding to the remaining time 3. 1-3 +BS 2-3 can be indicated. For example, one remaining time field corresponding to the remaining time field indicating the remaining time 4 may be added. In this case, the field may be BS, which is the buffer size corresponding to the remaining time 4. 2-4 can be directed.

[0093] 1) On-demand buffer size field: If the base station sets the remaining time criterion for each LCH / LCG / MAC Entity / Cell Group, the On-demand buffer size field may be included to indicate the amount of data in the corresponding (one or more) dsr-lch buffers that has a remaining time that satisfies the remaining time criterion set by the base station. The number of the On-demand buffer size fields may exist for each LCH / LCG / MAC Entity / Cell Group and for each remaining time criterion set by the base station. For example, if the base station sets criterion 1 having an upper limit of 1 for the remaining time and criterion 2 having an upper limit 2 and a lower limit 2 for a specific LCH / LCG / MAC Entity / Cell Group, there may be two On-demand buffer size fields corresponding to the LCH / LCG / MAC Entity / Cell Group. For example, the first On-demand Buffer Size field may indicate the amount of data with remaining time that satisfies Criterion 1, and the second On-demand Buffer Size field may indicate the amount of data with remaining time that satisfies Criterion 2.

[0094] For example, the above (minimum) remaining time-based buffer size field or the On-demand buffer size field may refer to a predefined buffer size table that defines an index for each buffer size section, and may indicate the index of the corresponding buffer size section in the table. The buffer size table may be one of the Long BS (Buffer Size) Table for the 8-bit Buffer Size field defined in the NR system, the Short BS table for the 5-bit Buffer Size field, or one or more New BS Tables that may be newly defined in the future. When there are multiple candidate BS Tables, a BS Table indicator indicating which BS Table the (minimum) remaining time-based buffer size field or the On-demand buffer size field refers to may be included in the DSR MAC CE for each (minimum) remaining time-based buffer size field or On-demand buffer size field, or for each LCH, or for each LCG, or for each MAC Entity / Cell Group.

[0095] FIG. 4 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, according to an embodiment of the present disclosure. According to an embodiment, the reference time for the remaining time can be interpreted as a concept indicating a point in time from which the corresponding remaining time is based.

[0096] Referring to FIG. 4, a terminal can typically transmit a MAC PDU or TB (Transport Block) including a DSR MAC CE to a base station through a PUSCH resource allocated by the base station. According to one embodiment, the base station can allocate a specific PUSCH resource to the terminal through a DCI through dynamic scheduling. Alternatively, multiple periodic PUSCH resources can be allocated to the terminal in the form of a CG (Configured Grant). The remaining time reference point 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, can be one of the following options.

[0097] - Start of the first symbol of the PUSCH resource (Initial Transmission) of the MAC PDU or TB including the corresponding DSR MAC CE (drawing symbol 400)

[0098] - The end of the last symbol of the PUSCH resource for the initial transmission of the MAC PDU or TB including the corresponding DSR MAC CE (drawing symbol 410)

[0099] - The start of the slot to which the PUSCH resource belongs (initial transmission) of the MAC PDU or TB including the corresponding DSR MAC CE (drawing symbol 420)

[0100] - The end of the slot to which the PUSCH resource belongs (drawing symbol 430) for the initial transmission of the MAC PDU or TB including the corresponding DSR MAC CE

[0101] According to one embodiment, the PUSCH resource may be a resource allocated by the base station as a Dynamic Grant through Dynamic Scheduling or a resource allocated by the base station as a Configured Grant.

[0102] According to one embodiment, one or more reference time points indicating the remaining time reference time points may be added to the DSR. For example, the reference time point field may be a field indicating a time point based on which the remaining time value indicated by the remaining time field of the DSR or the data indicated by the on-demand buffer size field was calculated. For example, the reference time point field may indicate an absolute time or a relative time based on a specific time point. For example, the reference time point field may be expressed as one or a combination of multiple units such as Frame, Subframe, Slot, and Symbol. For example, the reference time point field may indicate all or a specific position / number of Bits / LSB (Least Significant Bit) / MSB (Most Significant Bit) of UTC time.

[0103] In one embodiment, the remaining time field of the DSR may be a field indicating a relative difference compared to a specific remaining time upper limit set by the base station, rather than an absolute remaining time. For example, the relative difference may be a value indicating the difference when the remaining time is subtracted from the remaining time upper limit, or may be a value indicating how many times smaller / larger or by how much of a percentage the remaining time is compared to the remaining time upper limit.

[0104] According to one embodiment, at a specific point in time, the remaining time of data in the dsr-lch buffer may be equal to the remaining time value of the PDCP discardTimer of the corresponding data at that point in time, or may be equal to a value obtained by applying a specific offset to the remaining time value of the PDCP discardTimer. The offset may be defined in advance or may be set by the base station via RRC.

[0105] According to one embodiment, at a specific point in time, the remaining time of a specific PDU included in a specific PDU set may be regarded as / set / reset to be the remaining time of the PDU that has the smallest remaining time among all PDUs included in the PDU set at that point in time, or is first generated by the Application, or first arrives at the PDCP.

[0106] According to one embodiment, at a specific point in time, the remaining time of a specific PDU included in a specific PDU set may be regarded as / set / reset as the remaining time of the PDU that has the smallest remaining time among all PDUs included in the PDU set, or is first generated in the Application, or first arrives at the PDCP, if the PDU set has PSIHI (PDU-Set Integrated Handling Information) set.

[0107] According to one embodiment, at a specific point in time, the remaining time of a specific PDU included in a specific PDU set may be regarded as / set / reset to the remaining time of the PDU set level PDCP discardTimer of the PDU set at that point in time or to a value obtained by applying a specific Offset set by the base station to the remaining time, if a PDU set level PDCP discardTimer is set for the PDU set.

[0108] According to one embodiment, the DSR MAC CE trigger condition may be at least one of the following conditions:

[0109] - If data that satisfies the DSR trigger remaining time criteria occurs in a specific dsr-lch and there is no data that satisfies the criteria in the buffers of all dsr-lchs, the DSR MAC CE may be triggered. Data that satisfies the DSR trigger remaining time criteria may occur because new data that satisfies the criteria has occurred, or because the remaining time of existing data has decreased and now satisfies the criteria. For example, a DSR triggered under the above conditions may be referred to as Regular DSR.

[0110] - If data that satisfies the DSR trigger remaining time criteria occurs in a specific dsr-lch and the LCH priority level of the data is higher than the LCH priority level of other data that satisfies the criteria, the DSR MAC CE may be triggered. Data that satisfies the DSR trigger remaining time criteria may occur because new data that satisfies the criteria has occurred, or because the remaining time of existing data has decreased and now satisfies the criteria. For example, a DSR triggered under the above conditions may be referred to as a Regular DSR.

[0111] - In a specific dsr-lch, if data that satisfies the DSR trigger remaining time criteria occurs and the remaining time of the data is less than or equal to the remaining time of other data that satisfies the criteria, a DSR MAC CE may be triggered. Data that satisfies the DSR trigger remaining time criteria may occur because new data that satisfies the criteria has occurred, or because the remaining time of existing data has decreased and now satisfies the criteria. For example, a DSR triggered under the above conditions may be referred to as a Regular DSR.

[0112] - By setting a DSR retransmission timer (e.g., retxDSR-Timer), if at least one dsr-lch contains data that satisfies the DSR trigger remaining time criterion when the timer expires, the DSR MAC CE may be triggered. For example, the DSR MAC CE may be triggered only if the dsr-lch containing data that satisfies the criterion belongs to a specific LCG. For example, the retxDSR-Timer may be a separate timer from the retxBSR-Timer (BSR retransmission timer). For example, the retxDSR-Timer may be the same timer as the retxBSR-Timer (BSR retransmission timer). For example, the size of the retxDSR-Timer may be set by the base station via RRC for each MAC Entity / Cell Group. For example, a DSR triggered by the expiration of retxDSR-Timer can be considered to be triggered by the LCH with the highest priority among the dsr-lchs that have data satisfying the DSR trigger remaining time criterion at the time of expiration of the timer. The timer can be started / restarted if the UL-SCH resource includes a DSR MAC CE and the corresponding subheader after going through LCP (Logical Channel Prioritization) for the available UL-SCH resources. For example, a DSR triggered by the expiration of the timer can be referred to as Regular DSR.

[0113] - By setting a periodic DSR timer (e.g. periodicDSR-Timer), a DSR MAC CE can be triggered when the timer expires. For example, the timer can be a different timer from the periodicBSR-Timer. For example, the timer can be the same timer as the periodicBSR-Timer. For example, the timer can be started / restarted when, after going through LCP (Logical Channel Prioritization) for available UL-SCH resources, the UL-SCH resources include a DSR MAC CE and its subheader, not a truncated DSR. For example, the periodicDSR-Timer size can be set by the base station via RRC for each MAC Entity / Cell Group. For example, if the size of the timer is set to infinity, the timer may not expire, and thus, a DSR trigger due to the expiration of the timer may not occur.

[0114] - When the LCP result for a specific UL-SCH, when a padding bit occurs, if there is data that satisfies the DSR trigger remaining time criterion in at least one dsr-lch, a padding DSR can be triggered that is transmitted instead of the padding bit. For example, a truncated DSR can refer to a DSR MAC CE that transmits only a portion of the DSR field when the padding bit is not enough to accommodate the entire DSR field in a padding DSR transmitted using padding bits.

[0115] According to one embodiment, if there is at least one Regular DSR that has not yet been canceled after being triggered, the SR trigger condition for that Regular DSR may include at least one of the following conditions:

[0116] - When there are no available UL-SCH resources for new transmission.

[0117] - If there are available UL-SCH resources, but the LCP prevents the UL-SCH resources from being used for the LCH that triggered the DSR.

[0118] - When the LCH that triggered the DSR does not have available UL-SCH resources within a specific time period from the time the DSR was triggered. The specific time period may be predefined or set by the base station via RRC.

[0119] According to one embodiment, the base station may configure a common SR Configuration for regular DSR triggered by all dsr-lch of the Cell Group, per specific MAC Entity / Cell Group, via an RRC message, and may include a SchedulingRequestId for DSR (e.g., schedulingRequestID-DSR-r18) indicating the SR Configuration in the Cell Group configuration information.

[0120] According to one embodiment, the base station may include, for each dsr-lch, a SchedulingRequestId indicating an SR Configuration for regular DSR triggered by the dsr-lch in the configuration information of the dsr-lch.

[0121] Any DSR triggered before a specific MAC PDU is assembled and any SR triggered by a DSR are canceled, and the sr-ProhibitTimer corresponding to the canceled SR is stopped, may be at least one of the following conditions:

[0122] - When the MAC PDU is transmitted and the UL Grant of the MAC PDU can accommodate all the pending data in the buffer, but is not sufficient to accommodate the additional DSR MAC CE and its subheader.

[0123] - When the MAC PDU is transmitted, and the MAC PDU contains a DSR MAC CE, and the remaining time status and / or buffer size status reported by the DSR MAC CE reflect all / most recent DSR trigger events that occurred before the MAC PDU was assembled.

[0124] - When the MAC PDU is transmitted and can accommodate all pending data that satisfies the remaining time criteria set by the base station, but is not sufficient to accommodate the additional DSR MAC CE and its subheader.

[0125] - When there is no data that satisfies the remaining time criteria set by the base station in all dsr-lchs of the corresponding MAC entity. For example, when data that satisfies the remaining time criteria occurs, a timer with the same size as the remaining time can be set. When the timer expires, the data can be determined to no longer satisfy the remaining time criteria. For example, when the PDCP discardTimer expires, the data can be considered to no longer satisfy the remaining time criteria.

[0126] When a random access for SR triggered by DSR is in progress due to the absence of valid PUCCH resources, the conditions under which the MAC entity can stop the random access may include at least one of the following conditions.

[0127] - If there is a UL Grant allocated through a Random Access Response or in any other way than a UL Grant for MSGA payload, and if a MAC PDU containing a (new) BSR or DSR MAC CE is transmitted using the UL Grant, and if the buffer status or remaining time status (delay / remaining time status) is reported for all events that triggered the (new) BSR or DSR before assembling the corresponding MAC PDU through the (new) BSR or DSR MAC CE, the Random Access may be stopped. For example, the Random Access may be stopped if the entire pending data or all pending data that satisfies the remaining time criteria have been transmitted through the UL Grant.

[0128] Random Access may stop if no data satisfies the remaining time criterion. For example, data that previously satisfied the remaining time criterion may no longer satisfy it as the remaining time decreases. For example, data that previously satisfied the remaining time criterion may no longer satisfy the remaining time criterion when the PDCP discardTimer expires.

[0129] According to one embodiment, when a particular MAC PDU is transmitted and the MAC PDU includes a DSR MAC CE, and the remaining time status and / or buffer size status reported by the DSR MAC CE reflect all most recent BSR trigger events that occurred before the MAC PDU was constructed, all BSRs triggered before the MAC PDU was constructed and / or SRs triggered by the BSRs may be canceled.

[0130] In one embodiment, a new LCID or eLCID may be assigned to a DSR MAC CE to indicate that the MAC CE is a DSR MAC CE by the LCID or eLCID field of the MAC Subheader.

[0131] In one embodiment, the priorities of DSR MAC CEs may be in the following order (listed from highest priority MAC CE to lowest priority MAC CE):

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

[0133] - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation;

[0134] - MAC CE for Sidelink Configured Grant Confirmation;

[0135] - MAC CE for LBT failure;

[0136] - MAC CE for Timing Advance Report;

[0137] - MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

[0138] - MAC CE for (Extended) BSR, with exception of BSR included for padding;

[0139] - MAC CE for DSR, with exception of DSR included for padding;

[0140] - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR;

[0141] - MAC CE for Positioning Measurement Gap Activation / Deactivation Request;

[0142] - MAC CE for the number of Desired Guard Symbols;

[0143] - MAC CE for Case-6 Timing Request;

[0144] - MAC CE for (Extended) Pre-emptive BSR;

[0145] - MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

[0146] - 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;

[0147] - data from any Logical Channel, except data from UL-CCCH;

[0148] - MAC CE for Recommended bit rate query;

[0149] - MAC CE for BSR included for padding;

[0150] - MAC CE for SL-BSR included for padding.

[0151] - MAC CE for DSR included for padding;

[0152] In one embodiment, the priorities of DSR MAC CEs may be in the following order (listed from highest priority MAC CE to lowest priority MAC CE):

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

[0154] - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation;

[0155] - MAC CE for Sidelink Configured Grant Confirmation;

[0156] - MAC CE for LBT failure;

[0157] - MAC CE for Timing Advance Report;

[0158] - MAC CE for DSR, with exception of DSR included for padding;

[0159] - MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

[0160] - MAC CE for (Extended) BSR, with exception of BSR included for padding;

[0161] - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR;

[0162] - MAC CE for Positioning Measurement Gap Activation / Deactivation Request;

[0163] - MAC CE for the number of Desired Guard Symbols;

[0164] - MAC CE for Case-6 Timing Request;

[0165] - MAC CE for (Extended) Pre-emptive BSR;

[0166] - MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

[0167] - 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;

[0168] - data from any Logical Channel, except data from UL-CCCH;

[0169] - MAC CE for Recommended bit rate query;

[0170] - MAC CE for DSR included for padding.

[0171] - MAC CE for BSR included for padding;

[0172] - MAC CE for SL-BSR included for padding.

[0173] According to one embodiment, when determining the value of the buffer size field indicating buffer size information of a new BSR MAC CE or DSR MAC CE, if there is more than one candidate BS Table that can be referenced, when indicating the corresponding buffer size among the candidate BS Tables, the BS Table with the smallest Quantization Error may be referenced. For example, for each buffer size field / LCH / LCG / MAC CE, an indicator indicating which table among the candidate BS Tables was referenced may 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 may be 0. For example, the buffer size field may mean a (minimum) remaining time-based buffer size field, an on-demand buffer size field, or a (new) BSR MAC CE buffer size field. For example, the Quantization Error may mean the difference or the absolute value of the difference between the amount of data in the actual buffer and the upper or lower limit of the buffer section indicated by the corresponding index / codepoint of the BS Table. For example, the Quantization Error may mean the size of the buffer size range indicated by the corresponding index / codepoint of the BS Table, i.e., the difference between the upper and lower limits or the absolute value of the difference.

[0174] According to one embodiment, in order to reduce the Quantization Error, a new BS Table may be defined in addition to the Legacy BS Table for the existing 8-bit buffer size field and 5-bit buffer size field. For example, the new BS Table may be called NBT. For example, one or more NBTs may be defined in advance. For example, NBT may be 2 Lcan have index / codepoints of 8 or 16 or greater. For example, NBT can have a predefined buffer size range of 2 L You can divide it into non-overlapping, consecutive sections and define an index / codepoint that indicates each section. For example, 2 L Each section can display the upper or lower limit of the corresponding section in NBT. For example, the above 2 L Each section can have the upper limit of the immediately preceding section as its lower limit, and the lower limit of the immediately following section as its upper limit. For example, if there is one NBT, the corresponding NBT can be set as the Base NBT, and if there are multiple NBTs, one of them can be set as the Base NBT. For example, the base station can set an NBT that can be referenced when the UE reports a BSR, a new BSR, or a DSR. For example, the setting can be set for each LCH / LCG / MAC Entity / UE.

[0175] In one embodiment, a new NBT composed of a new buffer size interval can be constructed by adding or subtracting a specific common offset to the buffer size interval for each index / codepoint of the Base NBT. For example, if the buffer size interval indicated by the kth index of the Base NBT is L k From U k When applying offset +H, the buffer size range indicated by the kth index of the new NBT is L k + H can be from Uk + H. For example, the offset can be positive or negative.

[0176] In one embodiment, the minimum buffer size B included in Base NBT min and maximum buffer size B max Multiply by a specific scaling factor F ((Bmin x F, B max x F) or divided by (B min / F, B max / F) After that, the result buffer size interval is 2 L A new NBT can be constructed by dividing the buffer size into intervals and corresponding each index / codepoint. The buffer size intervals can be divided into equal sizes or by applying an Exponential Function.

[0177] According to one embodiment, the selection of the Base NBT may be determined by the base station and then notified to the terminal via an RRC message or MAC CE. For example, the selection of the Base NBT may be determined by the terminal and then reported to the base station via an RRC message or MAC CE.

[0178] In one embodiment, the base station may configure the terminal with one or more offset values ​​that can be added to or subtracted from the Base NBT via an RRC message or MAC CE. For example, the base station may configure the terminal with one or more scaling factor values ​​that can be multiplied or divided by the Base NBT via an RRC message or MAC CE.

[0179] According to one embodiment, the terminal may include in the (new) BSR or DSR MAC CE, an indicator indicating which candidate BS Table (existing Legacy BS Table or NBT) was referenced when determining the value of the corresponding buffer size field, for each buffer size field / LCH / LCG / MAC Entity / UE. The indicator may be an index / number of a BS Table, or if the corresponding BS Table is an NBT obtained by applying a specific Offset or Scaling Factor based on a Base NBT, the indicator 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 the applied Scaling Factor.

[0180] In one embodiment, the MAC layer of the terminal may request the RLC layer and PDCP layer of the terminal about how much data that satisfies a specific remaining time criterion is in the buffer of each layer. For example, when the terminal reports the amount of data that satisfies a specific remaining time criterion by LCH / LCG / MAC Entity / Cell Group, the amount of data may mean the total amount of data that satisfies the criterion among the data in the buffers of the RLC and PDCP layers of the terminal by LCH / LCG / MAC Entity / Cell Group.

[0181] According to one embodiment, when a MAC of a terminal requests an RLC layer for an amount of data satisfying a specific remaining time criterion, when the RLC layer determines the amount of data satisfying the remaining time criterion, at least one of the following data may be included.

[0182] - RLC SDU and RLC SDU Segment that satisfy the remaining time criterion and are not yet included in the RLC data PDU.

[0183] - RLC data PDU waiting for initial transmission and satisfying the remaining time criterion.

[0184] - In RLC AM mode, an RLC data PDU that satisfies the remaining time criterion and is waiting for RLC retransmission.

[0185] According to one embodiment, the method / method for determining whether a specific RLC SDU / SDU Segment / data PDU satisfies a specific remaining time criterion may be determined by the internal implementation of the terminal.

[0186] In one embodiment, the determination of whether a specific RLC SDU / SDU Segment / data PDU satisfies a specific remaining time criterion may be determined by whether the remaining time of the PDCP discardTimer of the RLC SDU / SDU Segment / data PDU satisfies the remaining time criterion. For example, the determination of the remaining time of the PDCP discardTimer of a specific RLC SDU / SDU Segment / data PDU may be determined by the internal implementation of the terminal.

[0187] According to one embodiment, when a MAC of a terminal requests a PDCP layer for an amount of data that satisfies a specific remaining time criterion, when the PDCP layer determines the amount of data that satisfies the remaining time criterion, at least one of the following data may be included.

[0188] - PDCP SDU that satisfies the remaining time criterion and has not yet formed a PDCP Data PDU.

[0189] - PDCP Data PDUs that satisfy the remaining time criterion and have not yet been delivered to the lower layer (MAC or RLC).

[0190] - PDCP SDUs that satisfy the remaining time criterion and are waiting for retransmission due to PDCP entity re-establishment in AM DRB.

[0191] - PDCP Data PDU that satisfies the remaining time criterion while waiting for retransmission due to PDCP Data Recovery in AM DRB.

[0192] In one embodiment, when a PDCP entity that is associated with at least two RLC entities informs a MAC entity of an amount of DPCP data that satisfies a specific remaining time criterion, the PDCP entity may operate as follows.

[0193] - In case of RB (radio bearer) with PDCP duplication activated:

[0194] 1) The amount of data that satisfies the remaining time criterion of the corresponding PDCP Entity can be notified to the MAC Entity associated with the Primary RLC Entity.

[0195] 1) The remaining amount of data, excluding PDCP Control PDUs, that satisfies the remaining time criteria of the corresponding PDCP Entity can be notified to the MAC Entity associated with the RLC Entity activated for the remaining PDCP duplications, excluding the Primary RLC Entity.

[0196] 1) The amount of data satisfying the remaining time criterion for the MAC entity associated with the RLC entity that has been deactivated for PDCP duplication can be notified to be 0.

[0197] - If the RB or DAPS (dual active protocol stack) bearer has PDCP duplication deactivated:

[0198] 1) When a split secondary RLC entity is established and the amount of PDCP data that satisfies the remaining time criteria and the total amount of RLC data for initial transmission in the primary RLC entity and the split secondary RLC entity is greater than or equal to a specific threshold set by the base station:

[0199] 2) The amount of PDCP data that satisfies the remaining time criterion can be notified to both MAC entities associated with the Primary RLC entity and the split secondary RLC entity. For example, the amount of PDCP data that satisfies the remaining time criterion can be notified as 0 to the MAC entities associated with other RLC entities other than the Primary RLC entity and the Split Secondary RLC entity.

[0200] 1) If the transmitting PDCP entity is a DAPS bearer:

[0201] 2) If uplink data switching is not requested:

[0202] 3) The amount of PDCP data that satisfies the remaining time criterion can be notified to the MAC entity associated with the source cell.

[0203] 2) When uplink data switching is requested:

[0204] 3) The amount of PDCP data that satisfies the remaining time criteria can be notified to the MAC entity associated with the target cell.

[0205] 1) Other cases:

[0206] 2) The amount of PDCP data that satisfies the remaining time criterion can be notified to the MAC entity associated with the Primary RLC Entity.

[0207] 2) The amount of PDCP data that satisfies the remaining time criterion can be notified as 0 to the MAC entity associated with other RLC entities except the Primary RLC Entity.

[0208] FIG. 5 is a diagram illustrating a procedure for a base station and a terminal to check whether a terminal supports DSR through RRC signaling and to set DSR-related settings according to an embodiment of the present disclosure. Referring to FIG. 5, in step 520, the base station may transmit / send a terminal capability request (UECapabilityEnquiry) message requesting a capability report to a terminal in an RRC_CONNECTED state. The base station may include a terminal capability (UE Capability) request for each RAT (Radio Access Technology) type in the UECapabilityEnquiry message. The UE Capability request for each RAT type may include information on the requested frequency band. In addition, when the base station requests the terminal to generate a UECapabilityInformation message through the UECapabilityEnquiry message, the base station may include filtering information that can indicate conditions and restrictions. At this time, the base station may indicate through the filtering information whether the terminal should report whether it supports DSR.

[0209] In step 530, the terminal may configure a terminal capability information (UECapabilityInformation) message corresponding to the UECapabilityEnquiry message and report a response to the UECapabilityEnquiry message to the base station. At this time, the UECapabilityInformation message may include a parameter / indicator indicating whether the terminal supports DSR. For example, the parameter or indicator may be 1-bit information. According to another embodiment, if the parameter or indicator is included, it may indicate that DSR is supported, and if it is not included, it may indicate that DSR is not supported.

[0210] The base station can determine whether the terminal supports DSR based on the received UECapabilityInformation message. If the base station determines that the terminal supports DSR, it can include DSR-related settings in an RRCReconfiguration message and instruct the terminal to do so at step 540. The terminal can apply the DSR-related configuration information included in the received RRCReconfiguration message. The DSR-related settings may include all DSR-related settings that the base station can set for the terminal as described above in the present disclosure.

[0211] Figure 6 is a block diagram illustrating the configuration of a base station according to an embodiment of the present invention. Referring to Figure 6, the base station may include a transceiver unit (610), a control unit (620), and a storage unit (630). In the present invention, the control unit may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0212] The transceiver (610) can transmit and receive signals with other network entities. For example, the transceiver (610) can transmit and receive RRC messages with a terminal. In addition, the transceiver (610) can also receive a MAC CE from a terminal.

[0213] The control unit (620) can control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the control unit (620) can control the signal flow between each block to perform the operation according to the flowchart described above. Specifically, the control unit (620) can set the DSR trigger remaining time criterion for any MAC entity or cell group of the terminal through an RRC message. Alternatively, the control unit (620) can control to allocate uplink transmission resources to the terminal based on the DSR MAC CE received from the terminal according to the embodiment of the present invention.

[0214] The storage unit (630) can store at least one of the information transmitted and received through the transmission and reception unit (610) and the information generated through the control unit (620). For example, the storage unit (630) can store information based on a DSR MAC CE received from a terminal according to an embodiment of the present invention, or store information on uplink transmission resources allocated to the terminal.

[0215] Meanwhile, Fig. 7 is a block diagram illustrating the configuration of a terminal according to an embodiment of the present invention. Referring to Fig. 7, the terminal may include a transceiver unit (710), a control unit (720), and a storage unit (730). In the present invention, the control unit may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0216] The transceiver (710) can transmit and receive signals with other network entities. For example, the transceiver (710) can transmit and receive RRC messages with a base station. Additionally, the transceiver (710) can transmit MAC CE to the base station.

[0217] The control unit (720) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (720) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (620) can control the terminal to check the remaining time of data stored in the transmission buffer and the amount of data corresponding to the remaining time according to the embodiment of the present invention, and report the information to the base station.

[0218] The storage unit (730) can store at least one of the information transmitted and received through the transceiver unit (710) and the information generated through the control unit (720). For example, the storage unit (730) can store information based on DSR MAC CE according to an embodiment of the present invention, or store information on uplink transmission resources allocated from a base station.

[0219] Figure 8 is a flowchart showing the operation of a terminal according to one embodiment of the present invention.

[0220] In step S810, the terminal can check information about the remaining time of data stored in the transmission buffer and the amount of data corresponding to the remaining time.

[0221] In step S820, the terminal may generate a MAC CE including information about the remaining time of data stored in the confirmed 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.

[0222] In step S830, the terminal can transmit the generated MAC CE to the base station.

[0223] In step S840, the terminal can receive an uplink grant related to uplink scheduling information from the base station.

[0224] And in step S850, the terminal can generate and transmit uplink data to the base station based on the uplink grant.

[0225] Meanwhile, FIG. 9 is a flowchart showing the operation of a base station according to one embodiment of the present invention.

[0226] In step S910, a MAC CE including information on the remaining time of data stored in the transmission buffer from the terminal and the amount of data corresponding to the remaining time may be received. The MAC CE may be referred to as a Delay Status Report (DSR) MAC CE.

[0227] In step S920, the base station may transmit an uplink grant related to uplink scheduling information to the terminal.

[0228] And in step S930, when uplink data is generated by the terminal based on the uplink grant, the base station can receive the uplink data from the terminal.

[0229] Meanwhile, according to one embodiment of the present disclosure, the base station can configure, via an RRC message, whether to report remaining time via DSR for a specific MAC Entity (or Cell Group) of the terminal, per LCG or LCH. For example, an LCG / LCH configured to report remaining time via DSR may be referred to as dsr-lcg / dsr-lch. For example, the RRC message may include an LCG List / LCH List including an LCG / LCH to be set as dsr-lcg / dsr-lch. For example, when a specific LCG is set as dsr-lcg, remaining time reporting via DSR may be performed for data of all LCHs included in the 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 terminal may generate a DSR MAC CE in the corresponding MAC Entity / Cell Group. Conversely, if there is no LCG / LCH configured as dsr-lcg / dsr-lch for a specific MAC Entity / Cell Group, it can be considered that the terminal is configured not to generate DSR MAC CE in that MAC Entity / Cell Group.

[0230] For example, a base station can set whether to generate a DSR MAC CE for a specific MAC entity of a terminal through an RRC message, through a specific field of configuration information for the MAC entity. For example, if the field has a specific value, a DSR can be generated, and if it has another value, a DSR can be set not to be generated. For example, whether to generate a DSR can be set based on the presence or absence of the field in an RRC message. For example, if the field exists, a DSR can be generated, and if it does not exist, a DSR can be set not to be generated. For example, if the field exists, a DSR can be not generated, and if it does not exist, a DSR can be generated.

[0231] In one embodiment of the present disclosure, one or more DSR trigger remaining time criteria may be set for each LCG / LCH in the RRC message. For example, if the DSR trigger remaining time criteria are set for each LCG, all dsr-lchs included in the corresponding LCG or all LCHs of the corresponding LCG may be subject to the same remaining time criteria for the DSR trigger. For example, one DSR trigger remaining time criteria may include only a DSR trigger remaining time upper limit, only a DSR trigger remaining time lower limit, or both a DSR trigger remaining time upper limit and a DSR trigger remaining time lower limit. For example, if the DSR trigger remaining time criteria of a specific LCG / LCH includes only a remaining time upper limit, if the remaining time of data (PDU Set or PDU) of the corresponding LCG / LCH is less than or equal to the remaining time upper limit, the data may be considered to satisfy the DSR trigger remaining time criteria. For example, if only the lower limit of the remaining time is included in the DSR trigger remaining time criterion of a specific LCG / LCH, and if the remaining time of the data (PDU Set or PDU) of the LCG / LCH is greater than or equal to the lower limit of the remaining time, the data may be considered to satisfy the DSR trigger remaining time criterion. For example, if the upper limit and lower limit of the remaining time are included in the DSR trigger remaining time criterion of a specific LCG / LCH, and if the remaining time of the data (PDU Set or PDU) of the LCG / LCH is less than or equal to the upper limit of the remaining time and greater than or equal to the lower limit, the data may be considered to satisfy the DSR trigger remaining time criterion.

[0232] In one embodiment of the present disclosure, the base station may set one or more LCGs / LCHs as dsr-lcg / dsr-lch by setting one or more DSR trigger remaining time criteria for each LCG / LCH via an RRC message. For example, if the base station sets at least one LCG / LCH as dsr-lcg / dsr-lch for a specific MAC Entity / Cell Group, the terminal may generate a DSR MAC CE in the corresponding MAC entity / cell group. Conversely, if there is no LCG / LCH for which a DSR trigger remaining time criteria is set for the specific MAC Entity / Cell Group, the terminal may not generate a DSR MAC CE in the corresponding MAC Entity / Cell Group.

[0233] At a given point in time, all PDUs included in a given PDU set may be calculated as the remaining PDU Set Delay Budget (PSDB) or remaining AN (Access Network) PSDB of the PDU set as of that point in time, or as a value obtained by applying a given offset to the remaining time value. The offset may be defined in advance or set via an RRC transmitted by the base station.

[0234] For example, the PSDB of a specific QoF Flow can be defined as follows.

[0235] - The PDU Set Delay Budget (PSDB) defines an upper bound for the delay that a PDU Set may experience for the transfer between the UE and the N6 termination point at the UPF, ie the duration between the reception time of the first PDU (at the N6 termination point for DL ​​or the UE for UL) and the time when all PDUs of the Set have successfully received a PDU ( UE for DL ​​or N6 termination point for UL).

[0236] 본 개시의 일 실시 예로, 특정 QoS Flow의 AN(Access Network) PSDB는 해당 QoS Flow의 PSDB에서 해당 QoS Flow Network(Core) 값으로 계산될 수 있다.

[0237] When a MAC of a terminal requests an RLC entity or a PDCP entity for the size of data that satisfies a specific remaining time criterion (e.g., which may include an upper limit, a lower limit, or both an upper limit and a lower limit), when the RLC entity or PDCP entity calculates the size of data that satisfies the remaining time criterion, a Data Unit (e.g., a PDCP SDU, a PDCP PDU, an RLC SDU, an RLC PDU, an RLC SDU Segment) that includes data for which the PDCP discardTimer is not set or is set to infinity may not be included in the size of the data. For example, since a PDCP control PDU may not have the discardTimer set, a Data Unit including the data may be excluded when the PDCP or RLC entity calculates the size of data that satisfies the remaining time criterion. For example, a Data Unit containing data corresponding to a Signaling Radio Bearer (SRB) for which the discardTimer is not set or a Data Radio Bearer (DRB) for which the discardTimer is set to infinity may be excluded when calculating the size of data satisfying the remaining time criterion in the RLC or PDCP Entity. For example, in the case of RLC AM, the UE may exclude the size of data pending for RLC retransmission when calculating the size of data satisfying a specific remaining time criterion reported through DSR.

[0238] According to one embodiment, for a particular dsr-lcg, the condition for triggering DSR may be at least one of the following conditions:

[0239] - If data that satisfies the DSR trigger remaining time criteria of the LCG occurs in a dsr-lch belonging to a specific dsr-lcg and DSR has not yet been triggered for the dsr-lcg, DSR can be triggered for the dsr-lcg.

[0240] - If data that satisfies the DSR trigger remaining time criteria of the LCG occurs in a dsr-lch belonging to a specific dsr-lcg, and there is no data that satisfies the criteria in the buffers of all dsr-lchs of the dsr-lcg, DSR may be triggered for the dsr-lcg.

[0241] - When data that satisfies the DSR trigger remaining time criteria of the LCG occurs in a dsr-lch belonging to a specific dsr-lcg, and the LCH priority level of the dsr-lch is higher than the LCH priority level of another dsr-lch that satisfies the remaining time criteria of the dsr-lcg, DSR can be triggered for the dsr-lcg.

[0242] - When data that satisfies the DSR trigger remaining time criteria of the LCG occurs in a dsr-lch belonging to a specific dsr-lcg, and the remaining time of the data is less than or equal to the remaining time of data that satisfies the criteria of other dsr-lchs of the dsr-lcg, DSR can be triggered for the dsr-lcg.

[0243] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

[0244] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.

[0245] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0246] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.

[0247] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0248] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. A method performed by a terminal in a wireless communication system, A step of receiving a control message including information on remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) from a base station; A step of triggering a DSR for the LCG based on the information about the remaining time, wherein a DSR medium access control (MAC) control element (CE) for the triggered DSR includes a remaining time field and a buffer size field; and A method comprising: transmitting the DSR MAC CE to the base station; 2. In paragraph 1, The remaining time field above is, A method characterized in that for any LCG, the remaining time corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one PDCP discard timer running.

3. In paragraph 1, The above buffer size field is, A method characterized by an amount of data associated with an RLC entity and a PDCP entity determined based on information about the remaining time.

4. In paragraph 3, The amount of data associated with the above RLC entity is: At least one RLC SDU and RLC SDU segment that does not consist of an RLC data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and A method characterized in that it comprises at least one RLC SDU and RLC SDU segment satisfying a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and is determined based on an RLC data PDU pending for initial transmission.

5. In paragraph 3, The amount of data associated with the above PDCP entity is: A PDCP SDU that does not consist of a PDCP data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and A method characterized in that the PDCP data PDU is determined based on a PDCP SDU that is not transmitted to a lower layer and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer.

6. In paragraph 1, The above DSR MAC CE is, Further comprising an LCG indicator indicating an LCG corresponding to the remaining time field and the buffer size field; A method characterized in that the information about the remaining time is in millisecond units.

7. A method performed by a base station in a wireless communication system, A step of transmitting a control message including information about the remaining time to trigger a delay status report (DSR) for a logical channel group (LCG) to a terminal; and When DSR for the LCG is triggered based on information about the remaining time from the terminal, a step of receiving a DSR medium access control (MAC) control element (CE) including a remaining time field and a buffer size field; including; The remaining time field above is, For any LCG, the remaining time corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer, The above buffer size field is, A method characterized by an amount of data associated with an RLC entity and a PDCP entity determined based on information about the remaining time.

8. In a wireless communication system, at the terminal, Transmitter and receiver; and Receive a control message including information on the remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) from a base station through the transceiver, Based on the information about the remaining time, control to trigger a DSR for the LCG, - the DSR medium access control (MAC) control element (CE) for the triggered DSR includes a remaining time field and a buffer size field; A terminal including a control unit that controls transmission of the above DSR MAC CE to the base station through the transceiver unit.

9. In paragraph 8, The remaining time field above is, A terminal characterized in that the remaining time corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one PDCP discard timer running for any LCG.

10. In paragraph 8, The above buffer size field is, A terminal characterized by an amount of data associated with an RLC entity and a PDCP entity determined based on information about the remaining time.

11. In paragraph 10, The amount of data associated with the above RLC entity is: At least one RLC SDU and RLC SDU segment that does not consist of an RLC data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and A terminal characterized in that it includes at least one RLC SDU and RLC SDU segment satisfying a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and is determined based on an RLC data PDU pending for initial transmission.

12. In paragraph 10, The amount of data associated with the above PDCP entity is: A PDCP SDU that does not consist of a PDCP data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and A terminal characterized in that the PDCP data PDU is determined based on a PDCP SDU that is not transmitted to a lower layer and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer.

13. In paragraph 8, The above DSR MAC CE is, Further comprising an LCG indicator indicating an LCG corresponding to the remaining time field and the buffer size field; A terminal characterized in that the information about the remaining time is in millisecond units.

14. In a base station in a wireless communication system, Transmitter and receiver; and Transmitting a control message including information on the remaining time for triggering a delay status report (DSR) for a logical channel group (LCG) to the terminal through the transceiver, A control unit for controlling reception of a DSR medium access control (MAC) control element (CE) including a remaining time field and a buffer size field through the transceiver when a DSR for the LCG is triggered based on information about the remaining time from the terminal; The remaining time field above is, For any LCG, the remaining time corresponds to the remaining time of the PDCP discard timer with the shortest remaining time among at least one running PDCP discard timer, The above buffer size field is, A base station characterized by an amount of data associated with an RLC entity and a PDCP entity determined based on information about the remaining time.

15. In paragraph 14, The amount of data associated with the above RLC entity is: At least one RLC SDU and RLC SDU segment that does not consist of an RLC data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and At least one RLC SDU and RLC SDU segment that satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and is determined based on the RLC data PDU pending for initial transmission, The amount of data associated with the above PDCP entity is: A PDCP SDU that does not consist of a PDCP data PDU and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, and A base station characterized in that the PDCP data PDU, which includes a PDCP SDU that is not transmitted to a lower layer and satisfies a condition based on information about the remaining time with respect to the value of the PDCP discard timer, is determined based on the same.

Images