Buffer status reporting method and apparatus considering remaining time information in mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The invention provides a buffer status report (BSR) method for a terminal, a method for a base station to acquire a BSR, and a related terminal, base station and communication system.

Description

Technical Field

[0001] The present disclosure relates to the field of communications, and more particularly, to operations of a terminal and a base station. In particular, the present disclosure relates to a method for a terminal to send a buffer status report (BSR), a method for a base station to obtain a BSR, and related terminals, base stations, and communication systems. Background Art

[0002] 5G mobile communication technology defines wide frequency bands to achieve high transmission rates and new services, and can be implemented not only in the "sub-6 GHz" frequency bands such as 3.5 GHz, but also in the ultra-high frequency "above 6 GHz" frequency bands called millimeter waves (mmWave) such as 28 GHz and 39 GHz. In addition, in order to achieve a transmission rate 50 times faster than 5G mobile communication technology and an ultra-low latency of one-tenth of 5G mobile communication technology, it has been considered to implement 6G mobile communication technology (referred to as a super 5G system) in the terahertz frequency band (for example, 95 GHz to 3 THz frequency band).

[0003] In the initial stage of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (mMTC), standardizations have been carried out on the following: beamforming and massive MIMO to mitigate radio wave path loss in millimeter waves and increase radio wave transmission distance; basic parameter sets (for example, operating multiple subcarrier spacings) for effectively utilizing millimeter wave resources and dynamic operation of time slot formats; initial access technology to support multi-beam transmission and broadband; the definition and operation of BWP (BandWidth Part, bandwidth part); new channel coding methods such as LDPC (Low Density Parity Check) codes for high-capacity data transmission and polarization codes for highly reliable transmission of control information; L2 preprocessing; and network slicing to provide dedicated networks customized for specific services.

[0004] Currently, in view of the services that 5G mobile communication technology will support, discussions are underway regarding the improvement and performance enhancement of initial 5G mobile communication technology, and physical layer standardization of technologies such as Vehicle-to-everything (V2X), which is used to assist in the driving determination of autonomous vehicles based on information about the vehicle's positioning and status sent by the vehicle and to enhance user convenience; New Radio Unlicensed (NR-U) for system operation compliant with various regulatory requirements in the unlicensed band; NR UE energy saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication for ensuring coverage in areas where communication with the terrestrial network is unavailable; and positioning.

[0005] In addition, standardization of technologies such as Industrial Internet of Things (IIoT), which is used to support new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; mobility enhancement, including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access for simplifying the random access procedure (2-step RACH for NR) has been underway in the field of radio interface architecture / protocol. Standardization of the following has also been underway in the system architecture / service field: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE positioning.

[0006] If such a 5G mobile communication system is commercialized, the exponentially increasing connected devices will be connected to the communication network, and accordingly, enhanced functions and performance of the 5G mobile communication system and integrated operation of the connected devices will be necessary. For this purpose, new research related to the following has been planned: Extended Reality (XR) for effectively supporting Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; improving 5G performance and reducing complexity by leveraging Artificial Intelligence (AI) and Machine Learning (ML); AI service support; metaverse service support; and drone communication.

[0007] In addition, such development of the 5G mobile communication system will serve not only as the basis for developing new waveforms for ensuring coverage of the terahertz band for 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), multi-antenna transmission technologies such as array antennas and massive antennas, metamaterial-based lenses and antennas for improving the coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS), but also as the basis for developing full-duplex technologies for increasing the frequency efficiency and improving the system network of 6G mobile communication technology, AI-based communication technologies for implementing system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for implementing service complexity levels exceeding the UE operation ability limit by leveraging ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical Problem

[0009] The embodiments described herein aim to provide an apparatus and method capable of effectively providing services in a wireless communication system. Various embodiments of the present disclosure provide a method for a terminal to transmit a Buffer Status Report (BSR), a method for a base station to obtain a BSR, and a terminal, a base station, and a communication system related thereto.

[0010] Solution to the Problem

[0011] Embodiments of the present disclosure provide a method for buffer status reporting executed by a terminal. The method includes: receiving, from a base station, a capability request message for buffer status reporting; sending, to the base station, capability information for buffer status reporting; receiving, from the base station, configuration information for buffer status reporting; determining a buffer status reporting format based on the configuration information; and sending a buffer status to the base station based on the buffer status reporting format.

[0012] In an embodiment, the capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that meets a remaining time threshold, and the configuration information may include at least one of an upper limit of the remaining time for uplink data and a lower limit of the remaining time for uplink data.

[0013] In an embodiment, determining the buffer status reporting format includes determining the buffer status reporting format based on the number of logical channel groups (LCGs), and when the number of logical channel groups is at least two, the buffer status reporting format includes a field that indicates whether there is a buffer size corresponding to each of at least two logical channel groups.

[0014] In an embodiment, the buffer status reporting format may include information indicating the size of the uplink data stored in the buffer of the terminal that meets the remaining time threshold.

[0015] Embodiments of the present disclosure provide a method for buffer status reporting executed by a base station. The method includes: sending, to a terminal, a capability request message for buffer status reporting; receiving, from the terminal, capability information for buffer status reporting; sending, to the terminal, configuration information for buffer status reporting; and receiving a buffer status from the terminal based on the buffer status reporting format.

[0016] In an embodiment, the capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that meets a remaining time threshold, and the configuration information may include at least one of an upper limit of the remaining time for uplink data and a lower limit of the remaining time for uplink data.

[0017] In an embodiment, the buffer status reporting format is determined based on the number of logical channel groups (LCGs), and when the number of logical channel groups is at least two, the buffer status reporting format includes a field that indicates whether there is a buffer size corresponding to each of at least two logical channel groups.

[0018] In an embodiment, the buffer status reporting format may include information indicating the size of the uplink data stored in the buffer of the terminal that meets the remaining time threshold.

[0019] Advantageous effects of the invention

[0020] The present disclosure provides an apparatus and method capable of effectively providing services in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 The structure of an NR system according to an embodiment of the present disclosure is shown.

[0022] Figure 2 The radio protocol structure in an NR system according to an embodiment of the present disclosure is shown.

[0023] Figure 3 A method for a UE in an NR system to determine a buffer status report (BSR) format according to an embodiment of the present disclosure is shown.

[0024] Figure 4 The short BSR / short truncated BSR MAC CE format of an NR system according to an embodiment of the present disclosure is shown.

[0025] Figure 5 The long BSR / long truncated BSR MAC CE format of an NR system according to an embodiment of the present disclosure is shown.

[0026] Figure 6 The short BSR buffer size report table of an NR system according to an embodiment of the present disclosure is shown.

[0027] Figure 7 The MAC sub-header format of an NR system according to an embodiment of the present disclosure is shown.

[0028] Figure 8 A procedure for a base station and a UE to identify whether the UE supports a delay-aware BSR and configure delay-aware BSR-related configurations via RRC signaling according to an embodiment of the present disclosure is shown.

[0029] Figure 9 A procedure for a UE to report preferred delay-aware BSR-related configurations to a base station via a UE Assistance Information (UAI) message and a procedure for the base station to reconfigure the UE's delay-aware BSR-related configurations via an RRC message according to an embodiment of the present disclosure are shown.

[0030] Figure 10 The short delay-aware BSR MAC CE according to an embodiment of the present disclosure is shown.

[0031] Figure 11 The short delay-aware BSR MAC CE according to another embodiment of the present disclosure is shown.

[0032] Figure 12Shows a short-delay aware BSR MAC CE according to another embodiment of the present disclosure.

[0033] Figure 13 Shows a long-delay aware BSR MAC CE according to an embodiment of the present disclosure.

[0034] Figure 14 Shows a long-delay aware BSR MAC CE according to another embodiment of the present disclosure.

[0035] Figure 15 Shows a long-delay aware BSR MAC CE according to yet another embodiment of the present disclosure.

[0036] Figure 16 Shows a long-delay aware BSR MAC CE according to still another embodiment of the present disclosure.

[0037] Figure 17 Shows a long-delay aware BSR MAC CE according to yet still another embodiment of the present disclosure.

[0038] Figure 18 Shows a long-delay aware BSR MAC CE according to a further embodiment of the present disclosure.

[0039] Figure 19 Shows a method for allocating new LCID code points to short-delay aware BSR MAC CE and long-delay aware BSR MAC CE according to an embodiment of the present disclosure.

[0040] Figure 20 Shows a method for allocating new eLCID code points to short-delay aware BSR MAC CE and long-delay aware BSR MAC CE according to another embodiment of the present disclosure.

[0041] Figure 21 Is a block diagram showing the internal structure of a UE according to an embodiment of the present disclosure.

[0042] Figure 22 Is a block diagram showing the structure of a base station according to an embodiment of the present disclosure. Detailed Description of the Invention

[0043] Exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that in the drawings, identical or similar elements are designated by the same or similar reference numerals as much as possible. In addition, detailed descriptions of known functions or configurations that may obscure the subject matter of the present disclosure will be omitted.

[0044] In describing the embodiments of the present disclosure, descriptions related to well-known technical content in the relevant field and not directly related to the present disclosure will be omitted. Omitting such unnecessary descriptions aims to avoid obscuring the gist of the present disclosure and to convey the gist more clearly.

[0045] For the same reason, in the drawings, some elements may be enlarged, omitted, or shown schematically. In addition, the size of each element does not exactly reflect the actual size. In the corresponding drawings, the same or corresponding elements are assigned the same reference numerals.

[0046] By referring in detail to the embodiments described below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will become apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements.

[0047] It will be understood here that each block of the flowchart illustration and combinations of blocks in the flowchart illustration can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture that includes instruction means for implementing the functions specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flowchart blocks.

[0048] In addition, each block in the flowchart illustration can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative embodiments, the functions marked in the blocks may occur out of order. For example, two blocks shown in sequence may actually be executed substantially concurrently, or these blocks may sometimes be executed in the reverse order depending on the functions involved.

[0049] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, the meaning of "unit" is not always limited to software or hardware. A "unit" can be configured to be stored in an addressable storage medium or to execute on one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units", or can be divided into a larger number of elements or "units". In addition, the elements and "units" can be implemented as one or more CPUs within a secure multimedia card or device.

[0050] In the following description, a base station is an entity that allocates resources to a terminal, and can be at least one of a Node B, a base station (BS), an eNode B (eNB), a gNode B (gNB), a radio access unit, a base station controller, and a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. In addition, the embodiments of the present disclosure described below can also be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure. Further, based on the determination of those skilled in the art, the embodiments of the present disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure. Examples of such communication systems can include fifth-generation mobile communication technologies (5G, New Radio, and NR) that go beyond the development of LTE-A, and in the following description, "5G" can be a concept that covers existing LTE, LTE-A, and other similar services. Further, based on the judgment of those skilled in the art, the present disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0051] In the following description, terms for identifying access nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are used illustratively for convenience of description. Thus, the present disclosure is not limited by the terms described below, and other terms referring to subjects having equivalent technical meanings can also be used.

[0052] In the following description, for ease of description, some terms and names defined in the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) standard and / or the 3GPP New Radio (NR) standard may be used. However, the present disclosure is not limited by these terms and names and can be applied to systems compliant with other standards in the same manner.

[0053] In a next-generation / 5G (New Radio (NR)) wireless communication system, a UE needs to report a buffer status to a base station to assist the base station in more effectively scheduling resources. A buffer status report (BSR) indicates the amount of data stored in the buffer of the UE and is used for reporting. According to the specification of the NR system, the UE selects an interval index that includes the amount of buffer data to be reported from the data amount ranges of each interval defined for each index in a buffer size table and includes the selected interval index in the BSR.

[0054] The buffer status report in the NR system can be performed based on media access control (MAC) layer signaling between the UE and the base station. That is, when a BSR is triggered at a specific transmission time point, the UE can include a BSR MAC control element (MAC CE) in a MAC protocol data unit (PDU) and send the MAC PDU to the base station. Here, the BSR MAC CE indicates, in units of logical channel groups (hereinafter simply referred to as LCGs), the amount of packets remaining in the transmission buffer of the UE after the MAC PDU is configured. The base station can use the received BSR to estimate the amount of data remaining in the buffer of the UE. In the NR system, the UE can manage the transmission buffer of the data to be sent to the base station for each of the eight LCGs.

[0055] Extended Reality (XR) uplink data includes a latency budget, i.e., the remaining time. Based on the time when data is generated at the UE application layer, the data should reach the uplink server within a predetermined remaining time to be used as valid data. If the data fails to reach the uplink server within the predetermined remaining time, the data loses its application value. The UE buffer size reported via the BSR is designed to report the total amount of data stored in the UE's buffer. However, the base station does not know how much of the total data is approaching its deadline, i.e., how short the remaining time is. If the base station knows this information, the base station can reflect this information when allocating uplink resources, thereby allowing data with a relatively short remaining time to be sent first. On the other hand, in the case of specific data with a very short remaining time, the time taken for actual transmission after reporting the BSR may be shorter than the remaining time. In this case, the data may be sent after its application value has been lost, or may be discarded before the transmission time. This may result in a waste of uplink resources. When the information reported to the base station includes the amount of data that meets a predefined specific remaining time threshold (upper or lower limit), the base station may be able to use this information to more effectively allocate uplink resources when allocating resources to the UE.

[0056] The present disclosure provides a method that considers the remaining time of data stored in the UE transmission buffer, reports the amount of data whose remaining time meets a specific threshold to the base station, and can use this information for uplink scheduling by the base station.

[0057] The present disclosure will provide a method for enhancing communication performance between a UE and a base station. Another aspect of the present disclosure will provide a method for the UE to report a BSR and a method for the base station to obtain a BSR.

[0058] According to various embodiments of the present disclosure, a method for enhancing communication performance between a UE and a base station can be provided. In addition, according to various embodiments of the present disclosure, a method for the UE to report a BSR and a method for the base station to obtain a BSR can be provided.

[0059] Figure 1 The structure of an NR system according to an embodiment of the present disclosure is shown.

[0060] Reference Figure 1 , the wireless communication system may include several base stations (e.g., gNB 100, ng-eNB 110, ng-eNB120, and gNB 130), an Access and Mobility Management Function (AMF) 140, and a User Plane Function (UPF) 150. Obviously, the wireless communication system is not limited to Figure 1 the structure shown, and may include more or fewer elements.

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

[0062] In Figure 1 , base stations 100, 110, 120, and 130 may serve as access nodes of a cellular network to provide radio access to UEs accessing the network. For example, base stations 100, 110, 120, and 130 may collect and schedule status information such as the buffer status, available transmit power status, and channel status of a UE to serve the traffic of the user, and may support the connection between the UE and the core network (CN) (in particular, the CN of NR may be referred to as 5GC).

[0063] In Figure 1 , gNBs 1a-05 and 1a-20 may control multiple cells and may apply an adaptive modulation and coding (hereinafter simply referred to as AMC) scheme to determine a modulation scheme and a channel coding rate according to the channel status of a UE.

[0064] The core network may be a device that is responsible not only for the mobility management function of a UE but also for various control functions and may be connected to multiple base stations. In addition, 5GC may be interlocked with an existing LTE system.

[0065] Meanwhile, in a wireless communication system, a user plane (UP) related to the transmission of actual user data and a control plane (CP) related to connection management may be configured separately. In Figure 1 , gNBs 100 and 130 may use the UP and CP technologies defined in NR technology, while ng-eNBs 110 and 120, although connected to 5GC, may use the UP and CP technologies defined in long term evolution (LTE) technology.

[0066] AMF 140 may be a device that is responsible not only for the mobility management function of a UE but also for various control functions and may be connected to multiple base stations, while UPF 150 may refer to a gateway device for providing data transmission. Although Figure 1 is not shown, an NR wireless communication system may include a session management function (SMF). The SMF may manage packet data network connections such as protocol data unit (PDU) sessions to be provided to a UE.

[0067] Figure 2 FIG. shows a radio protocol structure in an NR system according to an embodiment of the present disclosure.

[0068] Referring to Figure 2, the radio protocol of the NR system may include, in the UE and the base station respectively, the Service Data Adaptation Protocol (SDAP) 200 or 290, the Packet Data Convergence Protocol (PDCP) 210 or 280, the Radio Link Control (RLC) 220 or 270, the Medium Access Control (MAC) 230 or 260, and the Physical (PHY) 240 or 250.

[0069] The Service Data Adaptation Protocol (SDAP) 200 or 290 may perform the following operations: deliver user data, map QoS flows to specific DRBs for uplink and downlink, mark QoS flow IDs for downlink and uplink, and map reflected QoS flows to data bearers for uplink SDAP PDUs. The SDAP configuration corresponding to each DRB may be provided from a higher RRC layer. Obviously, SDAP is not limited to the above examples.

[0070] The Packet Data Convergence Protocol (PDCP) 210 or 280 may be responsible for IP header compression / decompression operations. In addition, PDCP 210 or 280 may provide in-sequence and out-of-sequence delivery functions, and may provide reordering, duplicate detection, retransmission, encryption, and decryption functions. However, obviously PDCP is not limited to the above examples.

[0071] The Radio Link Control (hereinafter referred to as RLC) 220 or 270 may reconstruct the PDCP protocol data unit (PDU) to an appropriate size. In addition, RLC 220 or 270 may provide in-sequence and out-of-sequence delivery functions, as well as ARQ functions, concatenation functions, segmentation functions, reassembly functions, re-segmentation functions, reordering functions, duplicate detection functions, and error detection functions. Obviously, RLC is not limited to the above examples.

[0072] MAC 230 or 260 may be connected to various RLC layer devices configured in a UE, and may perform operations such as multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. In addition, MAC 230 or 260 may provide mapping functions, scheduling information reporting functions, HARQ functions, priority handling functions between logical channels, priority handling functions between UEs, MBMS service identification functions, transmission format selection functions, and padding functions. Obviously, MAC is not limited to the above examples.

[0073] The physical (PHY) layer 240 or 240 may perform the following operations: perform channel coding and modulation on the high-layer data to generate orthogonal frequency division multiplexing (OFDM) symbols, and transmit the OFDM symbols through a wireless channel; or demodulate and perform channel decoding on the OFDM symbols received through the wireless channel, and transmit the demodulated and channel-decoded OFDM symbols to the high layer. In addition, hybrid automatic repeat request (HARQ) is used in the physical layer for additional error correction, and the receiving node may transmit information on whether a packet transmitted by the transmitting node is received by using 1 bit. This 1-bit information may be referred to as HARQ acknowledgment / negative acknowledgment (ACK / NACK) information.

[0074] In the case of LTE, the downlink HARQ ACK / NACK information related to uplink data transmission may be transmitted through a physical channel such as the physical hybrid ARQ indicator channel (PHICH). In the case of NR, it may be determined whether retransmission is required or a new transmission should be performed based on the scheduling information of the UE in the physical downlink control channel (PDCCH), which is a channel for transmitting downlink / uplink resource allocation, etc. This is because asynchronous HARQ is applied in NR. The uplink HARQ ACK / NACK information related to downlink data transmission may be transmitted through a physical channel such as the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). Generally, the PUCCH is transmitted through the uplink of the primary cell (PCell) (which will be described), but in the case where the base station supports the UE, the PUCCH may additionally be transmitted to the secondary cell (SCell) in the corresponding UE, which will be described below. This SCell is referred to as the PUCCH SCell.

[0075] Although Figure 2 not shown in the figure, there may be a radio resource control (RRC) layer above the PDCP layer of the UE and the base station, and this RRC layer may transmit and receive access and measurement-related configuration control messages for radio resource control.

[0076] Meanwhile, the physical layer may include one or more frequencies / carriers, and the technology of simultaneously configuring and using multiple frequencies is referred to as carrier aggregation technology (hereinafter referred to as CA). The communication between the terminal (or user equipment (UE)) and the base station (eNB or gNB) has used one carrier, but the CA technology may additionally use the primary carrier and one or more secondary carriers, thereby significantly increasing the amount of data to be transmitted by the multiple secondary carriers. Meanwhile, in LTE / NR, the cell using the primary carrier in the base station may be referred to as the primary cell or PCell, and the cell using the secondary carrier in the base station may be referred to as the secondary cell or SCell.

[0077] Figure 3 A method for a UE in an NR system to determine a buffer status report (BSR) format according to an embodiment of the present disclosure is shown. More specifically, Figure 3 A method for determining a buffer status report (BSR) format when a UE reports an available uplink data amount (hereinafter referred to as an uplink buffer size) to a base station is shown.

[0078] Referring to Figure 3 , when the UE includes a BSR in a MAC PDU (operation 300) and transmits it, the UE may select and transmit one of a long BSR and a short BSR based on the number of logical channel groups (LCGs) for which the uplink buffer size is greater than 0 (operation 310). Specifically, when there are more than one LCG with an uplink buffer size greater than 0, the UE may select a long BSR MACCE (operation 330), and when there is one LCG, the UE may select a short BSR MAC CE (operation 320).

[0079] Figure 4 A short BSR / short truncated BSR MAC CE format of an NR system according to an embodiment of the present disclosure is shown.

[0080] Referring to Figure 4 , the short BSR MAC CE may include a 3-bit LCG identifier (ID) 400 and a 5-bit buffer size field 410. The LCG ID 400 represents the ID of the LCG (0 to 7), and the buffer size field 410 indicates a buffer size (BS) index determined by the uplink buffer size corresponding to the LCG ID 400. The value of the BS index is between 0 and 31. The BS index may indicate an index of a buffer size interval defined in a predefined buffer size table (see Figure 6 ) that includes the corresponding interval of the uplink buffer size corresponding to the LCG ID 400.

[0081] Figure 5 A long BSR / long truncated BSR MAC CE format of an NR system according to an embodiment of the present disclosure is shown.

[0082] Referring to Figure 5, the long BSR MAC CE can indicate the presence or absence of the buffer size field corresponding to each of the eight LCGs ranging from LCG ID 7500 to LCG ID 0507 as 8 bits of the first byte, respectively. When the bit is 0 (indicated by reference numeral 540), it can mean that the buffer size field of the LCG corresponding to this bit of the long BSR MAC CE does not exist. On the contrary, when the bit is 1 (indicated by reference numeral 541), it can mean that the buffer size field of the LCG corresponding to this bit of the long BSR MAC CE exists.

[0083] Therefore, in the long buffer status BSR MAC CE, there may be buffer size fields equal to the number of bits 1 in the first byte. The buffer size fields 510, 520, and 530 of the long BSR MAC CE can have an 8-bit length. The long truncated BSR MAC CE can indicate whether the uplink buffer size of each of the eight LCGs ranging from LCG ID 7500 to LCG ID 0507 is greater than 0 (i.e., whether there is available uplink data) as 8 bits of the first byte, respectively. When the bit is 0 (indicated by reference numeral 550), it can mean that there is available uplink data in the corresponding LCG, while when the bit is 1 (indicated by reference numeral 551), it can mean that there is no available uplink data in the corresponding LCG.

[0084] In the long truncated BSR MAC CE, the number of buffer size fields 510, 520, and 530 can be represented by the L field 750 of the MAC sub-header added before the MAC CE, and the buffer size fields 510, 520, and 530 corresponding to the remaining uplink resources can be added to the MAC CE in descending order by considering the priorities of the LCGs with available data. Similar to the buffer size field of the short BSR, the buffer size field of the long BSR or long truncated BSR can indicate the BS index determined by the uplink buffer size.

[0085] In the NR system, a long BSR buffer size table for the long BSR can be defined, and the index of the buffer size range including the uplink buffer size can be indicated by the buffer size field. The buffer size 410 of the short BSR MAC CE has a 5-bit length, while the buffer size field of the long BSR or long truncated BSR MAC CE has an 8-bit length. The buffer size table referred to in the long BSR defines a total of 255 BS indexes from 0 to 254, and index 255 is "reserved" and not used. After receiving the BS index, the base station can obtain information about the size of the uplink buffer for each LCG by referring to the buffer size table of the long BSR.

[0086] Figure 6 Shows the buffer size table of the short BSR defined in NR according to an embodiment of the present disclosure.

[0087] The buffer size table of the short BSR may define a BS value 610, that is, a buffer size range corresponding to each of the 32 BS indices 600 represented by 0 to 31. For example, if the BS index 600 is 2, it means that the value of the corresponding uplink buffer size is between 11 bytes and 14 bytes. After receiving the short BSR MAC CE, the base station may perform uplink resource allocation by referring to the uplink buffer size range corresponding to the values of the LCG ID 400 and the buffer size field 400.

[0088] Figure 7 Shows the MAC sub-header format defined in the NR system according to an embodiment of the present disclosure.

[0089] Reference Figure 7 , a 1-byte MAC sub-header including fields R 700, F 705, and logical channel identifier (LCID) 710 may be added before the MAC-CE with a fixed length. In this case, the MAC CE may be indicated by the LCID 710. In addition, according to an embodiment, a 2-byte MAC sub-header including fields R 715, F 720, LCID 725, and extended LCID (eLCID) 730 may be added before the MAC CE with a fixed length. At this time, the presence and length of the eLCID 730 may be indicated by the LCID 725, and the MAC CE may be indicated by the eLCID 730.

[0090] According to an embodiment, a 2-byte MAC sub-header including fields R 735, F 740, LCID 745, and L 750 may be added before the MAC CE with a variable length. At this time, F 740 may indicate whether the length of the L field 750 is 1 byte or 2 bytes, and the LCID 750 may indicate the MAC CE. According to an embodiment, a 3-byte MAC sub-header including fields R755, F 760, LCID 765, eLCID 770, and L 775 may be added before the MAC CE with a variable length. At this time, F 760 may indicate whether the length of L775 is 1 byte or 2 bytes, the LCID 765 may indicate the presence and length of the eLCID 770, and the eLCID 770 may indicate the MAC CE. Since the values of the LCIDs of the MAC sub-headers added before the short BSR / short truncated BSR / long BSR / long truncated BSR are different, the base station that has received the BSR can distinguish the format of the received BSR.

[0091] The present disclosure provides a method for reporting to a base station the amount of data that meets a remaining time threshold by using an upper limit value, a lower limit value, or both an upper limit value and a lower limit value of the remaining time of data in an uplink buffer of a UE configured by the base station. Hereinafter, the MAC CE used when reporting the amount of data corresponding to the remaining time threshold is referred to as a delay-aware BSR.

[0092] Figure 8 A procedure is shown in which a base station and a UE according to an embodiment of the present disclosure identify whether the UE supports a delay-aware BSR and configure delay-aware BSR-related configurations via RRC signaling. In other words, a signaling procedure in which the UE and the base station start to use the delay-aware BSR is shown.

[0093] Referring Figure 8 , the base station may send a UE capability request message (UECapabilityEnquiry) 800 for requesting a capability report to the UE in a connected state. The base station may include a UE capability request for each radio access technology (RAT) type in the UECapabilityEnquiry message 800. The UE capability request for each RAT type may include requested band information.

[0094] In addition, when the base station requests the generation of a UECapabilityInformation message 810 from the UE via the UECapabilityEnquiry message 800, the base station may include filtering information capable of indicating conditions and limitations. At this time, through the filtering information, the base station may indicate whether to report whether the UE supports a delay-aware BSR. The UE may configure a UECapabilityInformation message 810 corresponding to the UECapabilityEnquiry message 800 and report a response to the UECapabilityEnquiry message 800 to the base station. At this time, the UECapabilityInformation message 810 may include a parameter indicating whether the UE supports a delay-aware BSR.

[0095] As an example, the parameter may be 1-bit information. In addition, as an example, when the parameter is included, it may indicate that the UE supports a delay-aware BSR, and when the parameter is not included, it may indicate that the UE does not support a delay-aware BSR. The base station may determine whether the UE supports a delay-aware BSR based on the received UECapabilityInformation message 810.

[0096] When it is determined that the UE supports delay-aware L1-BSR, the base station may indicate the configuration by including delay-aware BSR-related configuration in the RRCReconfiguration message 820. The UE may apply the delay-aware BSR-related configuration information included in the received RRCReconfiguration message 820.

[0097] More specifically, for the delay-aware BSR-related configuration, the RRCReconfiguration message 820 may include at least one of the following information. Of course, this is not limited to the following examples.

[0098] - It may include a list of LCGs (including only one LCG) that can report the delay-aware buffer size through the delay-aware BSR. In an embodiment, the LCG included in the LCG list may include only logical channels (LCHs) that can report the delay-aware buffer size. In another embodiment, the LCG included in the LCG list may include both LCHs that can report the delay-aware buffer size and LCHs that cannot report. Hereinafter, the LCG that can report the delay-aware buffer size through the delay-aware BSR is referred to as the delay-aware LCG.

[0099] - It may include a list of data radio bearers (DRBs) (including only one DRB) that can report the delay-aware buffer size through the delay-aware BSR. In an embodiment, the LCH connected to the DRB included in the DRB list may report the delay-aware buffer size through the delay-aware BSR. Hereinafter, the DRB that can report the delay-aware buffer size is referred to as the delay-aware DRB.

[0100] - It may include a list of LCHs (including only one LCH) that can report the delay-aware buffer size through the delay-aware BSR. Hereinafter, the LCH that can report the delay-aware buffer size through the delay-aware BSR is referred to as the delay-aware LCH.

[0101] - It may include a list of serving cells (including only one serving cell) that can report the delay-aware buffer size through the delay-aware BSR. In an embodiment, only the MAC PDUs sent from the serving cell included in the serving cell list may be configured to include the delay-aware BSR MAC CE.

[0102] - It may include a list of cell groups (including only one cell group) that can report the delay-aware buffer size through the delay-aware BSR. In an embodiment, only the MAC PDUs sent from the cell group included in the cell group list may be configured to include the delay-aware BSR MAC CE. In an embodiment, it may be configured to report the delay-aware buffer size to all LCGs and LCHs of the cell group included in the cell group list.

[0103] - May include a lower bound on the remaining time of uplink data to be reported via a delay-aware BSR. This lower bound can be configured for each LCH, LCG, cell group, or UE. In an embodiment, when the lower bound of the remaining time is configured for each LCG, the corresponding lower bound can be equally applied to all delay-aware LCHs belonging to the configured LCG. In an embodiment, when the lower bound of the remaining time is configured for each LCG, the corresponding lower bound can be equally applied to all delay-aware LCHs belonging to the configured LCG. In an embodiment, when the lower bound of the remaining time is configured for each cell group, the corresponding lower bound can be equally applied to all delay-aware LCHs belonging to the configured cell group. In an embodiment, when the lower bound of the remaining time is configured for each UE, this lower bound can be equally applied to all delay-aware LCHs of the corresponding UE.

[0104] - May include an upper bound on the remaining time of uplink data to be reported via a delay-aware BSR. This upper bound can be configured for each LCH, LCG, cell group, or UE. In an embodiment, when the upper bound of the remaining time is configured for each LCG, the corresponding upper bound can be equally applied to all delay-aware LCHs belonging to the configured LCG. In an embodiment, when the upper bound of the remaining time is configured for each LCG, the corresponding upper bound can be equally applied to all delay-aware LCHs belonging to the configured LCG. In an embodiment, when the upper bound of the remaining time is configured for each cell group, the corresponding upper bound can be equally applied to all delay-aware LCHs belonging to the configured cell group. In an embodiment, when the upper bound of the remaining time is configured for each UE, this upper bound can be equally applied to all delay-aware LCHs of the corresponding UE.

[0105] In the case where the delay-aware BSR-related configuration information included in the RRCReconfiguration message 820 has been configured, the UE that has received the RRCReconfiguration message 820 can update the configured information with the information included in the RRCReconfiguration message 820.

[0106] In an embodiment, a delay-aware LCG may include the LCGs included in the LCG list indicated by RRCReconfiguration.

[0107] In an embodiment, a delay-aware LCH may include the LCHs included in the LCH list indicated by RRCReconfiguration.

[0108] In an embodiment, a delay-aware LCH may include the LCHs connected to the DRBs included in the DRB list indicated by RRCReconfiguration.

[0109] In an embodiment, a delay-aware LCG or a delay-aware LCH may include an LCG or an LCH to which an upper or lower limit of remaining time is configured or applied.

[0110] In an embodiment of the present disclosure, the UE reports to the base station the data size that meets the configured remaining time threshold (requirement) by using a delay-aware buffer size field expressed in units of LCG or LCH included in the delay-aware BSR.

[0111] In an embodiment of the present disclosure, the short delay-aware BSR may include only one delay-aware buffer size field. In an embodiment, the long delay-aware BSR may include one or more delay-aware buffer size fields. In the present disclosure, the order of each field in the formats of the short delay-aware BSR MAC CE and the long delay-aware BSR MAC CE is not restricted. In the present disclosure, the length of each field in the formats of the short delay-aware BSR MAC CE and the long delay-aware BSR MAC CE is not restricted.

[0112] In an embodiment of the present disclosure, when the UE reports the delay-aware buffer size in units of LCG, the data size of the data stored in the uplink buffer of the specific LCG that meets the remaining time threshold may be determined by adding up the sizes of the data that meet the remaining time threshold of the corresponding delay-aware LCH in the uplink buffer of each delay-aware LCH belonging to the corresponding LCG.

[0113] In an embodiment, when configuring the buffer size field included in the delay-aware BSR in units of LCG, the buffer size field of the specific LCG may indicate the following information.

[0114] - Based on the sum of the sizes of the data stored in the uplink buffer of each LCH belonging to the corresponding LCG, the buffer size field may indicate the index of the interval in the buffer size table that contains the corresponding size.

[0115] - Based on the value obtained by subtracting the size of the data that meets the remaining time threshold in the uplink buffer of each delay-aware LCH belonging to the corresponding LCG from the sum of the sizes of the data stored in the uplink buffer of each LCH belonging to the corresponding LCG, the buffer size field may indicate the index of the interval in the buffer size table that contains the corresponding size.

[0116] - By subtracting, from the sum of the sizes of the data stored in the uplink buffers of each LCH belonging to the corresponding LCG, the size of the data that satisfies the remaining time threshold among the data stored in the uplink buffers of each latency-aware LCH belonging to the corresponding LCG, and by subtracting from the obtained value the size of the data that is less than (or less than or equal to) the lower limit among the data stored in the uplink buffer of the latency-aware LCH for which the lower limit of the remaining time is configured, the buffer size field may indicate an index of the interval in the buffer size table that contains the corresponding size.

[0117] In an embodiment, when reporting the latency-aware buffer size included in the latency-aware BSR in units of LCG, the latency-aware buffer size field may indicate an index of the interval in the buffer size table that contains the corresponding size, based on the sum of the sizes of the data that satisfies the remaining time threshold among the data stored in the uplink buffers of each latency-aware LCH belonging to the corresponding LCG.

[0118] In an embodiment, when reporting the latency-aware buffer size included in the latency-aware BSR in units of LCH, the latency-aware buffer size field may indicate an index of the interval in the buffer size table that contains the corresponding size, based on the size of the data that satisfies the remaining time threshold among the data stored in the uplink buffers of each latency-aware LCH belonging to the corresponding LCG.

[0119] In an embodiment, the size of the data that satisfies the remaining time threshold of a specific LCH may be determined as follows.

[0120] - When both the lower limit and the upper limit of the remaining time of the corresponding LCH are configured, the data size may correspond to the size of the data in the uplink buffer of the corresponding LCH whose remaining time is greater than (or greater than or equal to) the lower limit and less than (or less than or equal to) the upper limit.

[0121] - When only the lower limit of the remaining time of the corresponding LCH is configured and the upper limit is not configured, the data size may correspond to the size of the data in the uplink buffer of the corresponding LCH whose remaining time is greater than (or greater than or equal to) the remaining time lower limit.

[0122] - When only the upper limit of the remaining time of the corresponding LCH is configured and the lower limit is not configured, the data size may correspond to the size of the data in the uplink buffer of the corresponding LCH whose remaining time is less than (or less than or equal to) the upper limit.

[0123] - When neither the upper limit nor the lower limit of the remaining time of the corresponding LCH is configured, the data size may correspond to the size of the data in the uplink buffer of the corresponding LCH.

[0124] In an embodiment of the present disclosure, the remaining time of the uplink data by delaying the BSR report may indicate that uplink data transmission is no longer required after the corresponding time.

[0125] In an embodiment of the present disclosure, the measurement criteria for the remaining time of the uplink data by delaying the BSR report may be as follows:

[0126] - The remaining time may be measured based on the time when the delay-aware BSR MAC CE is configured.

[0127] - The remaining time may be measured based on the initial transmission time of the MAC PDU including the delay-aware BSR MAC CE.

[0128] - The remaining time may be measured based on the time when the uplink grant (UL Grant) required to send the MAC PDU including the delay-aware BSR MAC CE is received.

[0129] - The remaining time may be the same as the remaining time of the PDCP discard timer (discardTimer) of the data at the time of calculating the remaining time. In addition, the remaining time may be calculated by subtracting a specific fixed value from the remaining time of the PDCP discardTimer at the time of calculating the remaining time. This fixed value may be predefined or a value configured by the base station through an RRC message.

[0130] Figure 9 The procedure in which a UE reports preferred delay-aware BSR-related configurations to a base station through a UE Assistance Information (UAI) message 900 and the procedure in which the base station reconfigures the delay-aware BSR-related configurations of the UE through an RRC message according to an embodiment of the present disclosure are shown.

[0131] Refer to Figure 9 , when transmitting the UE Assistance Information message 900 to the base station, the UE may include preferred configuration information related to the delay-aware BSR as follows.

[0132] - The UE may include a preferred remaining time lower limit. This lower limit may be greater than or less than the previously configured lower limit. For example, when the remaining time lower limit configured by the base station is too large, since the remaining time of the data is less than this lower limit, the UE may not be able to report most of the uplink data sizes through the delay-aware BSR. At this time, the UE may include a lower limit less than the existing lower limit in order to request a downward adjustment of the remaining time lower limit.

[0133] - The UE may include a preferred remaining time limit. This limit may be greater than or less than a previously configured limit. For example, in the case where the remaining time limit configured by the base station is too small, since the remaining time of the data is greater than this limit, the UE may not be able to report most of the uplink data sizes through the delay-aware BSR. At this time, the UE may include a larger limit to request an upward adjustment of the remaining time limit.

[0134] In addition, for each UE, cell group, delay-aware LCG, delay-aware LCH, or delay-aware DRB, the preferred configuration information of the UE regarding the above-mentioned delay-aware BSR may be included in the UE Assistance Information message 900.

[0135] Reference Figure 9 , after receiving the UE Assistance Information message 900 sent by the UE, the base station may reconfigure the delay-aware BSR-related configuration of the UE through the RRC Reconfiguration message 910.

[0136] Figure 10 Shows a short delay-aware BSR MAC CE format according to an embodiment of the present disclosure.

[0137] Reference Figure 10 , 3 bits of the first byte of the short delay-aware BSR MAC CE may indicate the LCG ID 1000. The LCG ID 1000 may indicate the LCG corresponding to the uplink buffer size to be reported to the short delay-aware BSR MAC CE. The LCG ID 1000 may indicate one LCG ranging from LCG ID 0 to LCG ID 7. The remaining 5 bits of the first byte of the short delay-aware BSR MAC CE except for the 3 bits used for the LCG ID may indicate the buffer size field 1010.

[0138] 3 bits of the second byte of the short delay-aware BSR MAC CE may be used as a reserved field 1020. The remaining 5 bits except for the reserved field 1020 may indicate the delay-aware buffer size field 1030.

[0139] Figure 11 Shows a short delay-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0140] Reference Figure 11, three bits of the first byte of the short latency-aware BSR MAC CE may indicate LCG ID 1100. The LCG ID 1100 may indicate the LCG corresponding to the uplink buffer size to be reported to the short latency-aware BSR MAC CE. The LCG ID 1100 may indicate one LCG ranging from LCG ID 0 to LCG ID 7. The remaining five bits of the first byte of the short latency-aware BSR MAC CE, other than the three bits for the LCG ID, may indicate a buffer size field 1110.

[0141] Figure 12 FIG. shows a short latency-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0142] Reference Figure 12 , three bits 1200 of the first byte of the short latency-aware BSR MAC CE may indicate the LCH ID or LCH index.

[0143] - In the case of the LCH ID, it may indicate the LCH ID.

[0144] - In the case of the LCH index, the LCH index may indicate the sequential position of the LCH in the generated LCHs in ascending or descending order based on the LCH ID, or the sequential position in ascending or descending order based on the LCH priority. In another example, in the case of the LCH index, the LCH index may indicate the sequential position of the LCH in the configured latency-aware LCHs in ascending or descending order based on the LCH ID, or the sequential position in ascending or descending order based on the LCH priority.

[0145] In the first byte of the short latency-aware BSR MAC CE, the remaining five bits other than the LCH field 1200 may be used to indicate the latency-aware buffer size field 1210.

[0146] Figure 13 FIG. shows a long latency-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0147] Reference Figure 13, the eight bits 1300, 1301, 1302, 1303, 1304, 1305, 1306, and 1307 of the first byte of the long - latency - aware BSR MAC CE can be interpreted as a bitmap, where the eight bits respectively correspond to eight LCGs ranging from LCG ID 7 to LCG ID 0. When a specific bit in the eight bits is configured to 1, it can indicate the existence of a buffer - size field of the LCG corresponding to the bit configured to 1 in the long - latency - aware BSR MAC CE. In addition, when a specific bit in the eight bits is configured to 0, it can indicate the non - existence of a buffer - size field of the LCG corresponding to the bit configured to 0 in the long - latency - aware BSR MAC CE. Additionally, the meanings of 1 and 0 of the bits can be interchangeable, and the mapping relationship is not restricted in the present disclosure.

[0148] According to an embodiment, the remaining bytes in the long - latency - aware BSR MAC CE except the first byte can be configured by buffer - size fields 1310 and 1330 corresponding to one or more LCGs. For each LCG configured to 1 in the LCG ID bitmap, there can be a buffer - size field.

[0149] In an embodiment of the present disclosure, among the remaining bytes in the long - latency - aware BSR MAC CE except the first byte, when the specific LCG with available data is a latency - aware LCG, the latency - aware buffer - size field of this LCG can also be included immediately after the buffer - size field of this LCG.

[0150] In an embodiment of the present disclosure, among the remaining bytes in the long - latency - aware BSR MAC CE except the first byte, all buffer - size fields 1350 to 1360 of the LCGs with available data are placed first, and then the latency - aware buffer - size fields 1370 to 1380 of the latency - aware LCGs with available data can be placed.

[0151] The criteria for configuring the bit corresponding to a specific LCG in the LCG bitmap to 1 and including the buffer - size field and the latency - aware buffer - size field of this LCG in the long - latency - aware BSR can be as follows:

[0152] - When the size of the data stored in the uplink buffer of the corresponding LCG is greater than 0

[0153] - When, among the data stored in the uplink buffer of the corresponding LCG, the size of the data that meets the configured remaining - time threshold is greater than 0

[0154] - When the size of the data stored in the uplink buffer corresponding to the LCG is greater than 0, or when the size of the data stored in the uplink buffer corresponding to the LCG, which meets the configured remaining time threshold, is greater than 0

[0155] The buffer size field or the latency-aware buffer size field of each LCG can be arranged in ascending or descending order based on the LCG ID. The buffer size field or the latency-aware buffer size field of each LCG can be arranged in ascending or descending order based on the priority of the LCG.

[0156] Figure 14 Shows a long latency-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0157] Reference Figure 14 , the 8 bits 1400, 1401, 1402, 1403, 1404, 1405, 1406, and 1407 of the first byte of the long latency-aware BSR MAC CE can be interpreted as a bitmap, where the 8 bits respectively correspond to eight LCGs ranging from LCG ID 7 to LCG ID 0. In the case where a specific bit in the 8 bits is configured as 1, it can indicate the existence of a buffer size field for reporting the uplink buffer size of the LCG corresponding to the bit configured as 1. In addition, in the case where a specific bit in the 8 bits is configured as 0, it can indicate the non-existence of a buffer size field for reporting the uplink buffer size of the LCG corresponding to the bit configured as 0.

[0158] According to an embodiment, the remaining bytes in the long latency-aware BSR MAC CE except the first byte can be configured by buffer size fields 1410 and 1420 corresponding to one or more LCGs. For each LCG configured as 1 in the LCG ID bitmap, there can be a buffer size field.

[0159] According to an embodiment, all the buffer size fields of the LCGs with available data are arranged, and then a latency-aware buffer size field 1430 can be added. The latency-aware buffer size field can indicate the index of the interval in the buffer size table that contains the corresponding size based on the sum of the sizes of all the data stored in the uplink buffer of each latency-aware LCH that meets the remaining time requirement.

[0160] Figure 15 Shows a long latency-aware BSR MAC CE format according to yet another embodiment of the present disclosure.

[0161] Reference Figure 15, the 8 bits from bit 1500 to bit 1501 of the specific byte of the long latency-aware BSR MAC CE can be interpreted as a bitmap, where the 8 bits respectively correspond to 8 LCGs ranging from LCG ID 7 to LCG ID 0. When a specific bit in the 8 bits is configured to 1 (indicated by reference numeral 1551), it can indicate the existence of a buffer size field for the LCG corresponding to the bit configured to 1. In addition, when a specific bit in the 8 bits is configured to 0 (indicated by reference numeral 1550), it can indicate the non-existence of a buffer size field for reporting the uplink buffer size of the LCG corresponding to the bit configured to 0.

[0162] Reference Figure 15 , the 8 bits from bit 1510 to bit 1511 of the specific byte of the long latency-aware BSR MAC CE can be interpreted as a bitmap, where the 8 bits respectively correspond to eight LCGs ranging from LCG ID 7 to LCG ID 0. When a specific bit in the 8 bits is configured to 1 (indicated by reference numeral 1561), it can indicate the existence of a latency-aware buffer size field for the LCG corresponding to the bit configured to 1. In addition, when a specific bit in the 8 bits is configured to 0 (indicated by reference numeral 1560), it can indicate the non-existence of a latency-aware buffer size field for the LCG corresponding to the bit configured to 0.

[0163] The present disclosure does not limit the order between the bitmap indicating the existence or non-existence of the latency-aware buffer size field and the bitmap indicating the existence or non-existence of the buffer size field.

[0164] Figure 16 Shows the long latency-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0165] Reference Figure 16, in an embodiment, the long delay-aware BSR MAC CE may include a delay-aware buffer size field for each of one or more delay-aware LCGs. In an embodiment, bits 1600 to 1601 of the first byte of the long delay-aware BSR MAC CE may be interpreted as a bitmap, where the 8 bits respectively correspond to eight LCGs ranging from LCG ID 7 to LCG ID 0. In the case where a specific bit in the 8 bits is configured to 1 (indicated by reference numeral 1631), it may indicate the presence of a delay-aware buffer size field for the LCG corresponding to the bit configured to 1. Further, in the case where a specific bit in the 8 bits is configured to 0 (indicated by reference numeral 1630), it may indicate the absence of a delay-aware buffer size field for the LCG corresponding to the bit configured to 0. The absence of the delay-aware buffer size field may indicate that there is no data in the delay-aware LCG that satisfies the remaining time requirement when measuring the remaining time.

[0166] Reference Figure 16 , the remaining part of the long delay-aware BSR MAC CE except for the first byte may be configured by the delay-aware buffer size fields of the LCGs corresponding to the bits configured to 1 in the bitmap.

[0167] Figure 17 Fig. shows the long delay-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0168] Reference Figure 17 , in an embodiment, the long delay-aware BSR MAC CE may include a delay-aware buffer size field for each of one or more delay-aware LCHs. In an embodiment, bits 1700 to 1710 of the first four bytes of the long delay-aware BSR MAC CE may be interpreted as a bitmap, where the 32 bits respectively correspond to 32 LCHs from LCH 31 to LCH 0. In the case where a specific bit in the 32 bits is configured to 1 (indicated by reference numeral 1741), it may indicate the presence of a delay-aware buffer size field for the delay-aware LCH corresponding to the bit configured to 1. Further, in the case where a specific bit in the 32 bits is configured to 0 (indicated by reference numeral 1740), it may indicate the absence of a delay-aware buffer size field for the delay-aware LCH corresponding to the bit configured to 0. In the case where the delay-aware buffer size field is absent, it may indicate that there is no data in the corresponding delay-aware LCH that satisfies the remaining time requirement when measuring the remaining time.

[0169] Reference Figure 17, the remaining part of the long delay-aware BSR MAC CE except for the first four bytes can be configured by the delay-aware buffer size fields of the delay-aware LCHs corresponding to the bits configured as 1 in the bitmap.

[0170] Figure 18 Shows a long delay-aware BSR MAC CE format according to another embodiment of the present disclosure.

[0171] Reference Figure 18 , in an embodiment, the long delay-aware BSR MAC CE may include delay-aware buffer size fields for each of one or more delay-aware LCHs. In an embodiment, bits 1800 to 1810 of the first byte of the long delay-aware BSR MAC CE may be interpreted as a bitmap, where the 8 bits respectively correspond to the 1st LCH to the 8th LCH. When a specific bit in the 8 bits is configured as 1 (indicated by reference numeral 1841), it may indicate the existence of a delay-aware buffer size field for the i-th LCH corresponding to the bit configured as 1. In addition, when a specific bit in the 8 bits is configured as 0 (indicated by reference numeral 1840), it may indicate the non-existence of a delay-aware buffer size field for the i-th LCH corresponding to the bit configured as 0. In the present disclosure, the length of the LCH bitmap is not limited.

[0172] In an embodiment, the i-th LCH may refer to the i-th LCH among the configured LCHs in ascending or descending order based on the LCH ID or LCH priority. In an embodiment, the i-th LCH may refer to the i-th LCH among the remaining LCHs except for the LCHs mapped to the SRB among the configured LCHs in ascending or descending order based on the LCH ID or LCH priority. In an embodiment, the i-th LCH may refer to the i-th LCH among the configured delay-aware LCHs in ascending or descending order based on the LCH ID or LCH priority. In an embodiment, the i-th LCH may refer to the i-th LCH among the remaining LCHs except for the LCHs mapped to the SRB among the configured delay-aware LCHs in ascending or descending order based on the LCH ID or LCH priority.

[0173] Reference Figure 18 , the remaining part of the long delay-aware BSR MAC CE except for the LCH bitmap can be configured by the delay-aware buffer size fields of the delay-aware LCHs corresponding to the bits configured as 1 in the bitmap.

[0174] Figure 19 Shows an example of allocating a new LCID for the new MAC CE proposed in the present disclosure according to an embodiment of the present disclosure.

[0175] Reference Figure 19, two reserved values in the LCID code points used in the NR system (e.g., code point 37 and code point 38) can be respectively assigned to the short-delay aware BSR MAC CE 1940 and the long-delay aware BSR MAC CE 1950. At this time, since the short-delay aware BSR MAC CE 1940 can have a fixed length, a MAC sub-header including fields R 700, F705, and LCID 710 can be added to it as Figure 7 described, and LCID 710 can be used to indicate the corresponding code point.

[0176] Since the long-delay aware BSR MAC CE 2050 can have a variable length, a MAC sub-header including fields R 735, F 740, LCID 745, and L 750 can be added to it as Figure 7 described. At this time, the code point of the corresponding MAC CE can be indicated by LCID 745, and the length of the corresponding MAC CE can be indicated by L 750.

[0177] Figure 19 The code point values in are not necessarily limited to specific values. This is an example and is not limited to Figure 19 the values shown in. In addition, the present disclosure is characterized in that the short-delay aware BSR MAC CE and the long-delay aware BSR MAC CE are indicated by specific code points / indexes.

[0178] Figure 20 shows an example of allocating a new eLCID to a newly defined MAC CE according to another embodiment of the present disclosure.

[0179] Referring to Figure 20 , two reserved values in the LCID code points used in the NR system (e.g., code point 0 and code point 1) can be respectively assigned to the short-delay aware BSR MAC CE 2000 and the long-delay aware BSR MAC CE 2010. At this time, since the short-delay aware BSR MAC CE 2000 can have a fixed length, a MAC sub-header including fields R 715, F720, LCID 725, and eLCID 730 can be added to it as Figure 7 described. At this time, the presence and length of eLCID 730 can be indicated by LCID 725, and the code point corresponding to the MAC CE can be indicated by eLCID 730.

[0180] Since the long-delay aware BSR MAC CE 2010 can have a variable length, it can be as Figure 7As described above, a MAC sub-header including fields R 755, F 760, LCID 765, eLCID 770, and L 775 is added thereto. At this time, the code point corresponding to the MAC CE can be indicated by eLCID 770, and the length of the corresponding MAC CE can be indicated by L 775.

[0181] As Figure 20 shown, the relationship between the code point, the index, and the LCID can be indicated. At the same time, the code point value is not necessarily limited to Figure 20 the index value and LCID information shown in, and this is only an example. The feature of the present disclosure is that a specific code point matches a specific index, and the specific code point and index indicate a short-delay-aware BSR MAC CE and a long-delay-aware BSR MAC CE.

[0182] In an example of the present disclosure, the logical channel priorities of the delay-aware BSR MAC CE can be defined in the following order. Of course, this is not limited to the following examples.

[0183] - The MAC CE for the cell radio network temporary identity (C-RNTI), or data from the uplink common control channel (UL-CCCH);

[0184] - The MAC CE for (enhanced) beam failure recovery (BFR), or the MAC CE for configured grant acknowledgment, or the MAC CE for multi-entry configured grant acknowledgment;

[0185] - The MAC CE for sidelink configured grant acknowledgment;

[0186] - The MAC CE for listen-before-talk (LBT) failure;

[0187] - The MAC CE for timing advance reporting;

[0188] - The MAC CE for SL-BSR preferentially processed according to Clause 5.22.1.6;

[0189] - The MAC CE for (extended) BSR, except for the BSR included for padding;

[0190] - The MAC CE for (enhanced) single-entry power headroom report (PHR), or the MAC CE for (enhanced) multi-entry PHR;

[0191] - The MAC CE for positioning measurement gap activation / deactivation request;

[0192] - The MAC CE for the expected number of guard symbols;

[0193] - MAC CE for case 6 timing request;

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

[0195] - MAC CE for SL-BSR, except for SL-BSRs preferentially processed according to clause 5.22.1.6 and SL-BSRs included for padding;

[0196] - MAC CE for integrated access and backhaul-mobile terminal (IAB-MT) recommended beam indication, or for MAC CE for desired IAB-MT power spectral density (PSD) range, or for MAC CE for desired DL Tx power adjustment;

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

[0198] - MAC CE for delay-aware BSR, except for those included for padding;

[0199] - MAC CE for recommended bitrate query;

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

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

[0202] The logical channel priority of the delay-aware BSR may be lower than that of data from any logical channel, except data from UL-CCCH. By configuring the priority of the delay-aware BSR MAC CE to be lower than that of the data, when the uplink resources are not sufficient to transmit both the delay-aware BSR MAC CE and the data, there may be a more reasonable situation where the priority of data transmission is placed above the delay-aware BSR MAC CE indicating the presence of data.

[0203] According to an embodiment of the present disclosure, the logical channel priority of the delay-aware BSR MAC CE may be the same as that of the MAC CE for (extended) BSR, except for the BSR included for padding.

[0204] According to an embodiment of the present disclosure, the logical channel priority of the delay-aware BSR may be defined in the following order. Of course, this is not limited to the following examples.

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

[0206] - MAC CE for (Enhanced) BFR, or for Configured Grant Acknowledgement, or for Multi-Entry Configured Grant Acknowledgement;

[0207] - MAC CE for Sidelink Configured Grant Acknowledgement;

[0208] - MAC CE for LBT Failure;

[0209] - MAC CE for Timing Advance Report;

[0210] - MAC CE for Delayed-Aware BSR, except for the BSR included for padding;

[0211] - MAC CE for SL-BSR prioritized according to Clause 5.22.1.6;

[0212] - MAC CE for (Extended) BSR, except for the BSR included for padding;

[0213] - MAC CE for (Enhanced) Single-Entry PHR, or for (Enhanced) Multi-Entry PHR;

[0214] - MAC CE for Location Measurement Gap Activation / Deactivation Request;

[0215] - MAC CE for Desired Number of Guard Symbols;

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

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

[0218] - MAC CE for SL-BSR, except for the SL-BSR prioritized according to Clause 5.22.1.6 and the SL-BSR included for padding;

[0219] - MAC CE for IAB-MT Recommended Beam Indication, or for Desired IAB-MT PSD Range, or for Desired DL Tx Power Adjustment;

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

[0221] - MAC CE for Recommended Bitrate Query;

[0222] - MAC CE for the BSR included for padding;

[0223] - For filling the MAC CE for the included SL-BSR.

[0224] Since the latency-aware BSR may be used in situations where there is little remaining time and it is necessary to quickly notify the base station of the presence of data. Therefore, the latency-aware BSR MAC CE may have the highest priority among the BSR-related MAC CEs.

[0225] According to an embodiment of the present disclosure, the logical channel priorities of the latency-aware BSR can be defined in the following order. Of course, this is not limited to the following examples.

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

[0227] - MAC CE for (enhanced) BFR, or MAC CE for configuration grant confirmation, or MAC CE for multi-entry configuration grant confirmation;

[0228] - MAC CE for sidelink configuration grant confirmation;

[0229] - MAC CE for LBT failure;

[0230] - MAC CE for timing advance reporting;

[0231] - MAC CE for the SL-BSR to be preferentially processed according to Clause 5.22.1.6;

[0232] - MAC CE for (extended) BSR, except for filling the included BSR.

[0233] - MAC CE for latency-aware BSR, except for filling the included BSR;

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

[0235] - MAC CE for positioning measurement gap activation / deactivation request;

[0236] - MAC CE for the expected number of guard symbols;

[0237] - MAC CE for case 6 timing request;

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

[0239] - MAC CE for SL-BSR, excluding the SL-BSR preferentially processed according to Clause 5.22.1.6 and for filling the included SL-BSR;

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

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

[0242] - A MAC CE for recommended bitrate query;

[0243] - A MAC CE for filling the included BSR;

[0244] - A MAC CE for filling the included SL-BSR.

[0245] According to an embodiment of the present disclosure, the delay-aware BSR and the BSR can be included in the same MAC PDU simultaneously in a complementary manner. Since the delay-aware BSR and the BSR can be used in a complementary manner, when uplink resources are insufficient, the existing operation method that only uses the BSR can be maintained. Therefore, the delay-aware BSR MAC CE has the lowest priority among the BSR-related MAC CEs.

[0246] Figure 21 is a block diagram showing the internal structure of a UE according to an embodiment of the present disclosure.

[0247] Refer to Figure 21 , the UE may include a radio frequency (RF) processor 2110, a baseband processor 2120, a storage unit 2130, and a controller 2140.

[0248] The RF processor 2110 may perform functions of transmitting and receiving signals via a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 2110 may up-convert a baseband signal provided from the baseband processor 2120 into an RF band signal, transmit the signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processor 2110 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although Figure 21 only one antenna is shown in, the UE may include multiple antennas. In addition, the RF processor 2110 may include multiple RF chains. In addition, the RF processor 2110 may perform beamforming. For beamforming, the RF processor 2110 may adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit 2110 may perform multiple-input multiple-output (MIMO), and may receive multiple layers when performing MIMO operations.

[0249] The baseband processor 2120 can perform the conversion function between the baseband signal and the bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor 2120 can encode and modulate the transmitted bit string to generate complex symbols. In addition, during data reception, the baseband processor 2120 can demodulate and decode the baseband signal provided by the RF processor 2110 to recover the received bit string. For example, when following the orthogonal frequency division multiplexing (OFDM) scheme, during data transmission, the baseband processor 2120 can encode and modulate the transmitted bit string to generate complex symbols, map the complex symbols to subcarriers, and configure OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 2120 can split the baseband signal provided by the RF processor 2110 at the OFDM symbol level, recover the signal mapped to the subcarriers through fast Fourier transform (FFT) operations, and recover the received bit string through demodulation and decoding.

[0250] The baseband processor 2120 and the RF processor 2110 can send and receive signals as described above. Therefore, the baseband processor 2120 and the RF processor 2110 can be referred to as transmitters, receivers, transceivers, or communication units. In addition, at least one of the baseband processor 2120 and the RF processor 2110 can include multiple communication modules to support multiple different radio access technologies. In addition, at least one of the baseband processor 2120 and the RF processor 2110 can include different communication modules to process signals in different frequency bands. For example, different radio access technologies can include wireless local area network (LAN) (e.g., IEEE802.11), cellular network (e.g., LTE), etc. In addition, different frequency bands can include super high frequency (SHF) (e.g., 2NRHz) band and millimeter wave (mmWave) (e.g., 60GHz) band. The UE can send signals to / receive signals from the base station by using the baseband processor 2120 and the RF processor 2110. The signals can include control information and data.

[0251] The storage unit 2130 can store basic programs, application programs, and data for the operation of the main base station, such as configuration information. In particular, the storage unit 2130 can store information related to the second access node that performs wireless communication using the second radio access technology. In addition, the storage unit 2130 provides the stored data in response to the request of the controller 2140.

[0252] The controller 2140 controls the overall operation of the UE. For example, the controller 2140 can transmit / receive signals through the baseband processor 2120 and the RF processor 2110. In addition, the controller 2140 records data in the storage unit 2130 and reads data from the storage unit 2130. To this end, the controller 2140 may include at least one processor. For example, the controller 2140 may include a communication processor (CP) configured to perform communication control, and an application processor (AP) configured to control an upper layer such as an application program.

[0253] Figure 22 is a block diagram showing the structure of a base station according to an embodiment of the present disclosure.

[0254] Reference Figure 22 , the base station may include an RF processor 2210, a baseband processor 2220, a backhaul communication unit 2230, a storage unit 2240, and a controller 2250.

[0255] The RF processor 2210 may perform functions of transmitting and receiving signals via a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 2210 may up-convert a baseband signal provided from the baseband processor 2220 to an RF band signal, may transmit the signal through an antenna, and may down-convert an RF band signal received through the antenna to a baseband signal. For example, the RF processor 2210 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although Figure 22 only one antenna is shown, the base station may include multiple antennas. In addition, the RF processor 2210 may include multiple RF chains. In addition, the RF processor 2210 may perform beamforming. To perform beamforming, the RF processor 2210 may adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processor may transmit one or more layers to perform downlink MIMO operations.

[0256] The baseband processor 2220 can perform the conversion function between baseband signals and bit strings according to the physical layer specifications of the first radio access technology. For example, during data transmission, the baseband processor 2220 can encode and modulate the transmitted bit string to generate complex symbols. In addition, during data reception, the baseband processor 2220 can demodulate and decode the baseband signal provided by the RF processor 2210 to recover the received bit string. For example, when following the OFDM scheme, during data transmission, the baseband processor 2220 can encode and modulate the transmitted bit string to generate complex symbols, map the complex symbols to subcarriers, and configure OFDM symbols through IFFT operations and CP insertion. In addition, during data reception, the baseband processor 2220 can divide the baseband signal provided by the RF processor 2210 into OFDM symbol units, recover the signals mapped to subcarriers via FFT operations, and then recover the received bit stream via demodulation and decoding. The baseband processor 2220 and the RF processor 2210 can send and receive signals as described above. Therefore, the baseband processor 2220 and the RF processor 2210 can be referred to as transmitters, receivers, transceivers, communication units, or wireless communication units. The base station can send signals to / from the UE by using the baseband processor 2220 and the RF processor 2210. The signals can include control information and data.

[0257] The backhaul communication unit 2230 provides an interface for performing communication with other nodes in the network. That is, the backhaul communication unit 2230 can convert the bit string sent from the master base station to other nodes (e.g., secondary base stations, core networks) into a physical signal, and can convert the physical signal received from other nodes into a bit string.

[0258] The storage unit 2240 can store basic programs, application programs, and data for the operation of the master base station, such as configuration information. In particular, the storage unit 2240 can store information about the bearers allocated to the connected UEs, measurement results reported from the connected UEs, etc. In addition, the storage unit 2240 can store information used as a criterion for determining whether to provide or stop multi-connection to the UE. In addition, the storage unit 2240 provides the stored data at the request of the controller 2250.

[0259] The controller 2250 controls the overall operation of the base station. For example, the controller 2250 can send / receive signals through the baseband processor 2220 and the RF processor 2210 or through the backhaul communication unit 2230. In addition, the controller 2250 records data in the storage unit 2240 and reads data from the storage unit 2240. To this end, the controller 2250 can include at least one processor.

[0260] The methods disclosed in the claims and / or the methods according to the embodiments described in the specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0261] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. At least one program includes instructions that cause the electronic device to execute the methods according to various embodiments of the present disclosure, such as those defined in the appended claims and / or disclosed herein.

[0262] These programs (software modules or software) may be stored in non-volatile memory, which includes random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disc-ROM (CD-ROM), digital versatile disc (DVD), or other types of optical storage devices, or magnetic tape. Alternatively, any combination of some or all of them may form the memory in which the program is stored. In addition, multiple such memories may be included in the electronic device.

[0263] In addition, the program may be stored in an attachable storage device, which may access the electronic device through a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device may access the electronic device via an external port. In addition, an independent storage device on the communication network may access a portable electronic device.

[0264] In the drawings depicting the methods of the present disclosure, the order of description does not always correspond to the order in which the steps are performed, and the order relationship between the steps may be changed, or the steps may be performed in parallel.

[0265] Alternatively, in the drawings depicting the methods of the present disclosure, some elements may be omitted without departing from the spirit and scope of the present disclosure, and only some elements may be included therein.

[0266] In addition, in the methods of the present disclosure, some or all of the content of each embodiment may be combined and implemented without departing from the spirit and scope of the present disclosure.

[0267] The embodiments of the present disclosure described and illustrated in the specification and drawings are merely specific examples presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical idea of the present disclosure may be implemented. In addition, if necessary, the above corresponding embodiments may be combined and employed.

Claims

1. A buffer status reporting method performed by a terminal, the method comprising: receiving a capability request message for a buffer status report from a base station; sending capability information for the buffer status report to the base station; receiving configuration information for the buffer status report from the base station; Determining a buffer status report format based on the configuration information; as well as Based on the buffer status reporting format, a buffer status is sent to the base station.

2. The method of claim 1, wherein: The capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that satisfies a remaining time threshold, and The configuration information includes at least one of an upper limit of a remaining time for the uplink data and a lower limit of a remaining time for the uplink data.

3. The method according to claim 1, wherein, The determining of the buffer status reporting format comprises determining the buffer status reporting format based on a number of logical channel groups (LCGs), and Wherein, in a case where the number of the logical channel groups is at least two, the buffer status report format includes a field indicating whether a buffer size corresponding to each of the at least two logical channel groups exists.

4. The method of claim 2, wherein: The buffer status report format contains information indicating a size of data satisfying the remaining time threshold among uplink data stored in a buffer of the terminal.

5. A terminal device for executing a buffer status reporting method, the device comprising: transceiver; and a processor connected to the transceiver, in, The processor is configured to: receiving a capability request message for a buffer status report from a base station; sending capability information for the buffer status report to the base station; receiving configuration information for the buffer status report from the base station; Determining a buffer status report format based on the configuration information; as well as Based on the buffer status reporting format, a buffer status is sent to the base station.

6. The terminal device according to claim 5, wherein: The capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that satisfies a remaining time threshold, and The configuration information includes at least one of an upper limit of a remaining time for the uplink data and a lower limit of a remaining time for the uplink data.

7. The terminal device according to claim 5, wherein, In determining the buffer status report format, determining the buffer status report format based on the number of logical channel groups (LCGs), and Wherein, in a case where the number of the logical channel groups is at least two, the buffer status report format includes a field indicating whether a buffer size corresponding to each of the at least two logical channel groups exists.

8. The apparatus of claim 6, wherein: The buffer status report format contains information indicating the size of data satisfying the remaining time threshold among uplink data stored in the buffer of the terminal device.

9. A buffer status reporting method performed by a base station, the method comprising: Sending a capability request message for a buffer status report to the terminal; receiving capability information for the buffer status report from the terminal; Sending configuration information for the buffer status report to the terminal; and Receive a buffer status from the terminal based on a buffer status report format.

10. The method according to claim 9, wherein, The capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that meets a remaining time threshold, and wherein the configuration information includes at least one of an upper limit of the remaining time for the uplink data and a lower limit of the remaining time for the uplink data.

11. The method according to claim 9, wherein, The buffer status report format is determined based on the number of logical channel groups (LCGs), and wherein, when the number of the logical channel groups is at least two, the buffer status report format includes a field indicating whether there is a buffer size corresponding to each of at least two logical channel groups.

12. The method according to claim 11, wherein, The buffer status report format includes information indicating the size of the uplink data stored in the buffer of the terminal that meets the remaining time threshold.

13. A base station device for performing buffer status reporting, the base station device comprising: a transceiver; and a processor connected to the transceiver, Among them, wherein the processor is configured to: send a capability request message for buffer status reporting to a terminal; receive capability information for the buffer status reporting from the terminal; send configuration information for the buffer status reporting to the terminal; and receive a buffer status from the terminal based on a buffer status report format.

14. The base station device according to claim 13, wherein, The capability information includes information on whether the terminal is capable of reporting to the base station the size of uplink data that meets a remaining time threshold, and wherein the configuration information includes at least one of an upper limit of the remaining time for the uplink data and a lower limit of the remaining time for the uplink data.

15. The base station device according to claim 13, wherein: The buffer status report format is determined based on the number of logical channel groups (LCGs), wherein, when the number of the logical channel groups is at least two, the buffer status report format includes a field indicating whether there is a buffer size corresponding to each of at least two logical channel groups, and wherein the buffer status report format includes information indicating the size of the uplink data stored in the buffer of the terminal that meets the remaining time threshold.

Images