Method and apparatus for reporting data burst in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security- and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. More specifically, the present disclosure relates to a method performed by a terminal in a wireless communication system, and the method may comprise the steps of: transmitting, to a base station, terminal capability information related to whether an end of data burst (EoDB) indication is supported; receiving configuration information related to the EoDB indication from the base station, wherein the configuration information includes information about a logical channel group (LCG) in which the EoDB indication is configured; if the length of padding bits is greater than or equal to the sum of a short buffer status report (BSR) and a sub-header of the short BSR and is smaller than the sum of a long BSR and a sub-header of the long BSR, determining whether there is available data in one or more LCGs or whether the EoDB indication is pending; and transmitting a padding BSR to the base station.

Description

Method and device for reporting data bursts in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for a base station to efficiently allocate uplink resources.

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

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

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

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

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

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

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

[0009] The disclosed embodiment is intended to provide a device and method capable of effectively providing a service in a wireless communication system.

[0010] The technical problems to be achieved in the embodiments of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0011] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may include the steps of: transmitting terminal capability information related to whether an end of data burst (EoDB) indication is supported to a base station; receiving configuration information related to the EoDB indication from the base station, the configuration information including information on a logical channel group (LCG) for which the EoDB indication is set; determining whether there is available data in one or more LCGs or whether the EoDB indication is pending when a length of padding bits is greater than or equal to a size of a short BSR plus a subheader of the short BSR and less than a size of a long BSR plus a subheader of the long BSR; and transmitting a padding buffer status report (BSR) to the base station.

[0012] According to one embodiment of the present disclosure, in a wireless communication system, a terminal includes: a transceiver; and a controller connected to the transceiver, wherein the controller is configured to: transmit terminal capability information related to whether an end of data burst (EoDB) indication is supported to a base station; and receive configuration information related to the EoDB indication from the base station, wherein the configuration information includes information on a logical channel group (LCG) for which the EoDB indication is set, and when a length of padding bits is greater than or equal to a size of a short BSR plus a subheader of the short BSR and less than a size of a long BSR plus a subheader of the long BSR, determine whether one or more LCGs have available data or the EoDB indication is pending, and transmit a padding buffer status report (BSR) to the base station.

[0013] The present disclosure provides a device and method capable of effectively providing a service in a wireless communication system.

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

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

[0016] FIG. 3 is a diagram illustrating a Short BSR / Short Truncated BSR MAC CE format defined in an NR system according to one embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating a Long BSR / Long Truncated BSR MAC CE format defined in an NR system according to one embodiment of the present disclosure.

[0018] FIG. 5 is a diagram illustrating a procedure in which a base station and a terminal, according to one embodiment of the present disclosure, check whether a terminal supports EoDB (End of Data Burst) reporting or XR through RRC signaling and set EoDB reporting-related settings.

[0019] FIG. 6 is a diagram illustrating an EoDB MAC CE that may include EoDB reporting information according to one embodiment of the present disclosure.

[0020] FIG. 7 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0021] FIG. 8 illustrates the structure of a base station according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] XR (Extended Reality)-related traffic can have periodic characteristics. For example, in the case of video, the video frame rate can be determined by application settings, and the traffic generation cycle can be determined by the frame rate. For example, the amount of traffic can vary by cycle, but data of a specific size can be in the form of one or more Protocol Data Units (PDUs) or PDU sets, and is generated within a short period of time. Data generated within a short period of time can be referred to as a data burst. For example, one data burst can be generated per cycle. Of course, the present invention is not limited to the above example, and multiple data bursts can be generated within a cycle. Furthermore, traffic can be generated in the form of the aforementioned data bursts for both uplink (UL) and downlink (DL).

[0056] The terminal buffer size reported by BSR is designed to report the total amount of data stored in the terminal's buffer. However, the base station cannot know whether new traffic will continue to occur after the terminal transmits the data in the buffer reported by BSR, or whether there will be no new traffic temporarily after transmitting the data in the buffer. In other words, the base station cannot know whether the terminal has transmitted the entire data burst. If the terminal reports the end of the data burst to the base station, the base station can temporarily expect that there will be no UL traffic for the corresponding application until the next data burst is generated, and can optimize the UL radio resource allocation / usage through DRX (Discontinuous Reception) operation that can save the terminal's power consumption, UL Dynamic Scheduling, or Configured Grant.

[0057] According to one embodiment of the present disclosure, a method is provided in which a terminal reports to a base station an End of Data Burst (EoDB), which is information that can be utilized by a base station to more efficiently use UL resources and reduce power consumption of a terminal, for one or more LCHs / LCGs.

[0058] FIG. 3 is a diagram illustrating the Short BSR / Short Truncated BSR MAC CE format defined in the NR system.

[0059] Referring to FIG. 3, the BSR MAC CE may include a 3-bit LCG ID (300) and a 5-bit Buffer Size (310) field. The LCG ID may represent the ID (0 to 7) of the LCG, and the Buffer Size field may indicate the UL buffer size (amount of data in the buffer) of the LCG indicated by the LCG ID. The Buffer Size field may indicate the Index / Codepoint of the buffer size range by referencing a predefined BS (Buffer Size) Table.

[0060] FIG. 4 is a diagram illustrating the Long BSR / Long Truncated BSR MAC CE format defined in the NR system.

[0061] Referring to FIG. 4, for example, the Long BSR MAC CE can indicate the presence or absence of a Buffer Size field corresponding to each of the eight LCGs from LCG ID 7 to LCG ID 0 using the eight bits of the first byte. For example, if at least one bit among the eight bits of the first byte is 0, this may mean that the Buffer Size field of the LCG corresponding to Bit 0 does not exist in the Long BSR MAC CE. Conversely, if at least one bit among the eight bits of the first byte is 1, this may mean that the Buffer Size field of the LCG corresponding to Bit 1 exists in the Long BSR MAC CE. Therefore, the Long BSR MAC CE may have as many Buffer Size fields as the number of Bit 1s among the eight bits of the first byte. The length of the Buffer Size field of the Long BSR MAC CE may be 8 bits. Of course, it is not limited to the above example.

[0062] Referring to FIG. 4, as an example, the Long Truncated BSR MAC CE can indicate whether there is available data in the UL buffer of each LCG, for each of the 8 LCGs from LCG ID 7 to LCG ID 0, using the 8 bits of the first byte. For example, if at least one bit among the 8 bits of the first byte is 0, it can mean that there is no UL available data in the LCG corresponding to Bit 0 in the Long Truncated BSR MAC CE, and if at least one bit among the 8 bits of the first byte is 1, it can mean that there is UL available data in the LCG corresponding to Bit 1 in the Long Truncated BSR MAC CE.

[0063] For example, the number of Buffer Size fields in a Long Truncated BSR MAC CE can be expressed by the L (Length) field of the MAC Subheader attached to the front of the MAC CE, and the Buffer Size field can be added to the Long Truncated BSR MAC CE in descending order by considering the priority of the LCG among the LCGs with available data, equal to the number of Padding Bits. The Buffer Size field of a Long BSR or Long Truncated BSR can also indicate the UL buffer size of the corresponding LCG, just like the Buffer Size field of a Short BSR. In the NR system, an 8-bit BS table is defined for the Buffer Size field of a Long / Long Truncated BSR. For example, the Buffer Size field of a Long / Long Truncated BSR can indicate the corresponding Index / Codepoint of the BS table corresponding to the UL buffer size of the corresponding LCG.

[0064] In one embodiment of the present disclosure, a terminal may trigger a BSR in an activated cell group when one of the following conditions is satisfied.

[0065] - If new UL data is generated on a specific LCH belonging to the LCG of the corresponding MAC entity, and the priority of the LCH is higher than all LCHs where the UL data of the corresponding MAC entity exists, a BSR may be triggered. For example, the BSR triggered at this time may be considered to have been triggered by the LCH where the new UL data was generated. For example, the BSR may be referred to as a Regular BSR.

[0066] - If new UL data is generated in a specific LCH belonging to the LCG of the MAC entity, and UL data does not exist in any LCH belonging to any LCG of the MAC entity, a BSR may be triggered. For example, the BSR triggered at this time may be considered to have been triggered by the LCH where the new UL data was generated. For example, the BSR may be referred to as a Regular BSR.

[0067] - When the BSR retransmission timer (e.g., retxBSR-Timer) expires, if at least one LCH contains UL data and the LCH belongs to an LCG, a BSR may be triggered. For example, the triggered BSR may be considered to have been triggered by the LCH with the highest priority among the LCHs containing UL data. For example, the BSR may be referred to as a Regular BSR.

[0068] - A BSR can be triggered when a periodic BSR trigger timer (e.g., periodicBSR-Timer) expires. For example, a BSR triggered at this time can be referred to as a Periodic BSR.

[0069] - After a UL resource of a specific UL Grant is allocated to a terminal, if the resource includes a Padding Bit, and the length of the Padding Bit is greater than or equal to the combined length of the BSR MAC CE and the corresponding Subheader, the BSR may be included instead of the Padding Bit. For example, the BSR may be referred to as a Padding BSR.

[0070] FIG. 5 is a diagram illustrating a procedure in which a base station and a terminal check whether a terminal supports EoDB (End of Data Burst) reporting or XR through RRC signaling and set EoDB reporting-related settings according to one embodiment of the present disclosure.

[0071] Referring to FIG. 5, in step 500, the base station may transmit / send a UE Capability Enquiry message requesting a capability report to a terminal in an RRC_CONNECTED state. The base station may include a UE Capability request for each RAT (Radio Access Technology) type in the UECapabilityEnquiry message. According to one embodiment of the present disclosure, the UE Capability request for each RAT type may include information on the requested frequency band. In addition, when the base station requests the generation of a UECapabilityInformation message from the terminal through the UECapabilityEnquiry message, the base station may include filtering information that may indicate conditions and restrictions. At this time, the base station may indicate through the filtering information whether the terminal should report EoDB reporting or XR support.

[0072] In step 510, the terminal may configure a terminal capability information (UECapabilityInformation) message corresponding to the UECapabilityEnquiry message and report a response to the UECapabilityEnquiry message to the base station. At this time, the UECapabilityInformation message may include a parameter / indicator indicating whether the terminal supports EoDB reporting or XR. For example, the parameter or indicator indicating whether EoDB reporting or XR is supported may be 1-bit information. Of course, the present invention is not limited to the above example, and the size of the parameter or indicator indicating whether EoDB reporting or XR is supported is not limited, and may be expressed as a predetermined field in the message.

[0073] In another embodiment, if a parameter or indicator indicating whether EoDB reporting or XR is supported is included, it may be indicated that EoDB reporting or XR is supported, and if not included, it may be indicated that EoDB reporting or XR is not supported.

[0074] For example, the base station can determine whether the terminal supports EoDB reporting or XR based on the received UECapabilityInformation message. If the base station determines that the terminal supports EoDB reporting or XR, it can include EoDB reporting-related settings in the RRCReconfiguration message in step 520. The terminal can apply the EoDB reporting-related settings information included in the received RRCReconfiguration message.

[0075] In one embodiment of the present disclosure, a base station may set at least one of the following information to a terminal, in relation to EoDB reporting, via an RRC message.

[0076] - An EoDB report can be requested for one or more LCHs. An EoDB report request can be indicated by adding a field corresponding to the LCH-specific configuration information of a specific MAC Entity / Cell Group in an RRC message. An LCH that has received an EoDB report request can be referred to as an EoDB-LCH. For example, an LCH that has not received an EoDB report request can be referred to as a NonEoDB-LCH. For example, an LCG that includes at least one EoDB-LCH can be referred to as an EoDB-LCG. For example, an LCG that does not include an EoDB-LCH can be referred to as a NonEoDB-LCG. For example, a specific LCG can be preset so that it does not include two or more EoDB-LCHs. For example, if a specific LCG includes one EoDB-LCH, it can be preset so that other LCHs (EoDB-LCH and NonEoDB-LCH) cannot be included. For example, if a specific LCG includes one or more EoDB-LCHs, it may be preset so that Non-EoDB-LCHs cannot be included. Of course, this is not limited to the above example, and whether and how many EoDB-LCHs and Non-EoDB-LCHs are included within a specific LCG may vary depending on the settings of the base station or terminal.

[0077] - The base station can indicate whether to report EoDB per LCH or per LCG. For example, if the base station indicates to report per LCH, the terminal can report EoDB per EoDB-LCH. For example, if the base station indicates to report per LCG, the terminal can report EoDB per EoDB-LCG. For example, if there is no indication as to whether to report per LCH or per LCG, the terminal can report EoDB per EoDB-LCH. For example, if there is no indication as to whether to report per LCH or per LCG, the terminal can report EoDB per EoDB-LCG. For example, if a specific EoDB-LCG includes multiple EoDB-LCHs, an EoDB report for the EoDB-LCG may be an EoDB report for all EoDB-LCHs included in the EoDB-LCG. For example, if a particular EoDB-LCG contains multiple EoDB-LCHs, an EoDB report for the EoDB-LCG may be an EoDB report for at least one EoDB-LCH among the multiple EoDB-LCHs contained in the EoDB-LCG.

[0078] For example, in the present disclosure, BSR may mean Regular BSR, Periodic BSR, or Padding BSR.

[0079] In one embodiment of the present disclosure, a BSR capable of performing EoDB reporting for each EoDB-LCG may be referred to as an EoDB-BSR. For example, the EoDB-BSR may be a Short / Short Truncated BSR, a Long / Long Truncated BSR, or a New Short / Short Truncated BSR or a New Long / Long Truncated BSR with a new LCID / eLCID assigned. For example, the New Short / Short Truncated BSR may have the same format as the aforementioned Short / Short Truncated BSR, but may be distinguished by including new LCID / eLCID values ​​in the corresponding Subheader. For example, the New Long / Long Truncated BSR may have the same format as the aforementioned Long / Long Truncated BSR, but may be distinguished by including new LCID / eLCID values ​​in the corresponding Subheader.

[0080] For example, New Short / Short Truncated / Long / Long Truncated BSR may include, in addition to the Buffer Size field for each LCG, a BS Table indicator that indicates which table among one or more BS Table candidates (existing BS Table, New BS Table, etc.) was used for each LCG. For example, if there is one or more BS Table candidates for a specific LCG, and if there is one BS Table among the candidate BS Tables that includes a buffer size range corresponding to the buffer size of the LCG, the buffer size may be reported using the corresponding BS Table. For example, if there is one or more BS Table candidates for a specific LCG, and if there are multiple BS Tables among the candidate BS Tables that include a buffer size range corresponding to the buffer size of the LCG, the buffer size may be reported using the BS Table with the smallest Quantization Error when reporting the buffer size. For example, Quantization Error may mean the difference between the upper limit and the lower limit of the buffer size range corresponding to the corresponding buffer size. For example, Quantization Error may mean the difference between the upper limit of the buffer size range corresponding to the corresponding buffer size and the corresponding buffer size. For example, Quantization Error may mean the difference between the corresponding buffer size and the lower limit of the buffer size range corresponding to the corresponding buffer size. For example, New Short / Short Truncated / Long / Long Truncated BSR may include not only the buffer size for each LCG, but also the delay information of the data in the buffer. For example, the delay information of the data may be reported through the Remaining Time field indicating the remaining time of the corresponding data for each LCG / LCH.For example, the remaining time field value may be determined by the remaining value of the PDCP discardTimer of the corresponding data. For example, if the remaining time field is included, a buffer size field for each remaining time may also be included. For example, data delay information may be information indicating the size of the data that meets the remaining time criteria set by the base station. For example, the remaining time criteria may be an upper limit, a lower limit, or both.

[0081] For example, an EoDB-BSR that can report buffer size or EoDB for more than one LCG can be called a Long EoDB-BSR. For example, if EoDB reporting is included, a Long / Long Truncated BSR or a New Long / Long Truncated BSR can be a Long EoDB-BSR. For example, an EoDB-BSR that can report buffer size or EoDB for only one LCG can be called a Short EoDB-BSR. For example, if EoDB reporting is included, a short / short Truncated BSR or a New short / short Truncated BSR can be a short EoDB-BSR.

[0082] In one embodiment of the present disclosure, if a Buffer Size field of a specific EoDB-LCG exists in an EoDB-BSR, the value of the Buffer Size field of the corresponding LCG can be pre-restricted so that it cannot be 0 other than an EoDB report. For example, if a Buffer Size field of a specific EoDB-LCG exists in an EoDB-BSR, if the value of the Buffer Size field is 0, this can be regarded as an EoDB report of the corresponding EoDB-LCG.

[0083] In one embodiment of the present disclosure, for Regular and Periodic BSR, a MAC Entity for which logicalChannelGroupIAB-Ext is not set from a higher layer may operate as follows.

[0084] -When constructing a MAC PDU including BSR, if there are two or more LCGs that have data in the UL buffer or that must report EoDB (with EoDB report, with pending EoDB report):

[0085] --If there is at least one LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0086] ---(Option 1) If there is an LCG with data in the UL buffer, the buffer size report for the LCG and the EoDB report for the LCG that needs to report EoDB are performed through Long BSR.

[0087] ---(Option 2) If there is an LCG with data in the UL buffer, the buffer size report for the LCG and the EoDB report for the LCG that needs to report EoDB are performed through the New Long BSR.

[0088] --If there is no LCG that needs to report EoDB (with EoDB report, with pending EoDB report):

[0089] ---Report buffer size for LCGs with data in the UL buffer via Long BSR

[0090] - When configuring a MAC PDU including the above BSR, if there is one LCG that has data in the UL buffer or must report EoDB (with EoDB report, with pending EoDB report):

[0091] --If the LCG in question is required to report EoDB (with EoDB report, with pending EoDB report):

[0092] ---(Option 1) Perform EoDB reporting for the LCG in question via Short BSR

[0093] ---(Option 2) Perform EoDB reporting for the LCG in question via New Short BSR

[0094] In one embodiment of the present disclosure, for Padding BSR, a MAC Entity for which logicalChannelGroupIAB-Ext is not set from a higher layer may operate as follows.

[0095] -If the length of the Padding Bit is greater than or equal to the sum of the lengths of the Short BSR and its Subheader, and less than the sum of the lengths of the Long BSR and its Subheader:

[0096] --If there is data in the UL buffer or there are two or more LCGs that need to report EoDB (with EoDB report, with pending EoDB report):

[0097] ---If the length of the Padding Bit is equal to the sum of the length of the Short BSR and the corresponding Subheader:

[0098] ----If there is data in the UL buffer or the LCG with the highest priority among the LCGs that must report EoDB (with EoDB report, with pending EoDB report) is the LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0099] -----(Option 1) Report EoDB to LCG via Short Truncated BSR

[0100] -----(Option 2) Report EoDB to LCG via New Short Truncated BSR

[0101] ----If the LCG with the highest priority among the LCGs that have data in the UL buffer or that must report EoDB (with EoDB report, with pending EoDB report) is the LCG that has data in the UL buffer:

[0102] -----Report the buffer size for the LCG via Short Truncated BSR.

[0103] ---If the length of the Padding Bit is greater than the sum of the lengths of the Short BSR and the corresponding Subheader:

[0104] ----For LCGs that have data in the UL buffer or that must report EoDB (with EoDB report, with pending EoDB report), reports can be made for the LCGs in order of priority, starting from the LCG with the highest priority and decreasing in priority, up to the number of Buffer Sizes allowed by the Padding Bit.

[0105] -----If the reportable LCGs contain at least one LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0106] ------(Option 1) For reportable LCGs, the UL buffer size or EoDB can be reported via Long Truncated BSR.

[0107] ------(Option 2) For reportable LCGs, the UL buffer size or EoDB can be reported via the New Long Truncated BSR.

[0108] -----If there is no LCG that can report EoDB (with EoDB report, with pending EoDB report) among the LCGs that can report EoDB:

[0109] ------Long Truncated BSR allows reporting of the UL buffer size for reportable LCGs.

[0110] --If there is data in the UL buffer or there is one LCG that needs to report EoDB (with EoDB report, with pending EoDB report):

[0111] ---If the LCG needs to report EoDB (with EoDB report, with pending EoDB report):

[0112] ----(Option 1) Through Short BSR, EoDB of LCG can be reported.

[0113] ----(Option 2) Through New Short BSR, EoDB of LCG can be reported.

[0114] ---If there is data in the UL buffer of the LCG:

[0115] ----With Short BSR, the buffer size of the LCG can be reported.

[0116] -If the length of the Padding Bit is greater than or equal to the sum of the lengths of the Long BSR and the corresponding Subheader:

[0117] --If there is at least one LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0118] ---(Option 1) Long BSR allows buffer size reporting for all LCGs that have data in their UL buffers (if any) and EoDB reporting for all LCGs that need to report EoDB (with EoDB report, with pending EoDB report).

[0119] ---(Option 2) New Long BSR allows buffer size reporting for all LCGs with data in the UL buffer (if any) and EoDB reporting for all LCGs that must report EoDB (with EoDB report, with pending EoDB report).

[0120] --If there is no LCG that needs to report EoDB (with EoDB report, with pending EoDB report):

[0121] ---Long BSR allows buffer size reporting for all LCGs that have data in their UL buffers.

[0122] Referring to FIG. 3, if the LCG indicated by the LCG ID field of the Short / Short Truncated BSR is an EoDB-LCG, the terminal can report the EoDB of the corresponding LCG by setting the Buffer Size field value to 0. For example, a new LCID / eLCID can be allocated to the New Short / Short Truncated BSR for EoDB. For example, the terminal can set the corresponding LCG of the New Short / Short Truncated BSR to EoDB-LCG and set the Buffer Size field value to 0 to report the EoDB. At this time, the base station can use the newly allocated LCID / eLCID to distinguish the report from the existing Short / Short Truncated BSR and know that the report is an EoDB report.

[0123] Referring to FIG. 4, the terminal can report the EoDB of the corresponding EoDB-LCG by setting the bit of a specific EoDB-LCG among the LCG bits of the Long / Long Truncated BSR to 1 and setting the corresponding Buffer Size field value to 0. For example, the terminal can report the EoDB of the corresponding EoDB-LCG by setting the bit of a specific EoDB-LCG among the LCG bits of the Long / Long Truncated BSR to 0 and not including the corresponding Buffer Size field. For example, when the EoDB-LCG reports the buffer size in advance, the base station can force the BSR MAC CE not to include the Buffer Size field if there is no data in the buffer, rather than setting the Buffer Size field to 0, so that it can be determined that it is an EoDB report unconditionally if the Buffer Size field exists and has a value of 0.

[0124] Also, for example, the base station can force the EoDB-LCG to set the bit to 1 and the corresponding Buffer Size field to 0 if there is no data in the buffer when the corresponding EoDB-LCG reports the buffer size in advance, so that it can be determined that it is an EoDB report unconditionally if the Buffer Size field is absent. For example, the terminal can report the EoDB of the corresponding EoDB-LCG by setting the bit of a specific EoDB-LCG among the LCG Bits of the Long Truncated BSR to 1 and setting the corresponding Buffer Size field value to 0.

[0125] For example, a new LCID / eLCID can be assigned to a New Long / Long Truncated BSR for EoDB. For example, a UE can report EoDB for a specific EoDB-LCG of the New Long / Long Truncated BSR by setting the LCG Bit of the specific EoDB-LCG to 1 and setting the corresponding Buffer Size field value to 0. For example, a UE can report EoDB for a specific EoDB-LCG of the New Long / Long Truncated BSR by setting the LCG Bit of the specific EoDB-LCG of the New Long / Long Truncated BSR to 0 and not including the corresponding Buffer Size field. The base station can recognize the newly assigned LCID / eLCID and know that the corresponding EoDB-LCG is reporting EoDB. For example, a base station may restrict the Buffer Size field from being set to 0 when present in a New Short / Short Truncated / Long / Long Truncated BSR MAC CE that has assigned a new LCID / eLCID, except for EoDB reporting.

[0126] FIG. 6 is a diagram illustrating an EoDB MAC CE that may include EoDB reporting information, as an embodiment of the present disclosure.

[0127] For example, a new LCID / eLCID can be assigned to the EoDB MAC CE in advance to distinguish it from other MAC CEs. For example, the EoDB MAC CE may not include a buffer size field and an indicator indicating the presence or absence of the buffer size field. For example, the EoDB MAC CE may only include an EoDB indicator. For example, the EoDB MAC CE can be included in the same MAC PDU as the BSR MAC CE. The BSR MAC CE may mean a short / short truncated / long / long truncated BSR MAC CE or a New short / short truncated / long / long truncated BSR MAC CE.

[0128] Referring to FIG. 6, as an example, the EoDB indicator of the EoDB MAC CE can be set as follows.

[0129] - EoDB indicator per LCG or LCH: It can include EoDB Bit for corresponding EoDB report per LCG or LCH. For example, when reporting EoDB per EoDB-LCG, it can include one EoDB Bit corresponding to each LCG for every LCG. Referring to Fig. 6, when the number of LCGs is K, it can include a K-bit bitmap composed of Bits corresponding to each LCG. For example, K can be 8. For example, when the Bit of a specific EoDB-LCG is set to 1, it can mean EoDB of the corresponding LCG, and when set to 0, it can mean that the corresponding LCG is not EoDB. For example, when the Bit of a specific EoDB-LCG is set to 0, it can mean EoDB of the corresponding LCG, and when set to 1, it can mean that the corresponding LCG is not EoDB. For example, when reporting EoDB per EoDB-LCH, it may include one EoDB Bit corresponding to each LCH for every LCH. When the number of LCHs is Y, it may include a Y-bit bitmap consisting of Bits corresponding to each LCH. For example, Y may be 32. For example, if the Bit of a specific EoDB-LCH is set to 1, it may mean EoDB of the corresponding LCH, and if it is set to 0, it may mean that the corresponding LCH is not EoDB. Alternatively, if the Bit of a specific EoDB-LCH is set to 0, it may mean EoDB of the corresponding LCH, and if it is set to 1, it may mean that the corresponding LCH is not EoDB.

[0130] Referring to Fig. 6, for example, an EoDB MAC CE may be a MAC CE that adds an EoDB indicator to a BSR MAC CE. When the EoDB indicator is added, the Buffer Size field may be restricted from being used for EoDB reporting. For example, if the value of the Buffer Size field of a specific EoDB-LCG is 0, this may indicate that there is no data in the buffer of the LCG, and may not indicate EoDB.

[0131] For example, the last byte of a specific Data Burst of a specific EoDB LCH can be referred to as the EoDB Byte of that EoDB LCH.

[0132] For example, if a particular MAC PDU contains an EoDB report for a particular EoDB-LCH, the EoDB report for that EoDB-LCH may indicate one or a combination of one or more of the following information:

[0133] - Information 1: It can indicate that the EoDB Byte of the EoDB-LCH is included in the MAC PDU.

[0134] - Information 2: It can indicate that the EoDB Byte of EoDB-LCH is included in the MAC PDU that has already been transmitted.

[0135] - Information 3: It may indicate that the traffic for the next Data Burst or the first byte of the next Data Burst has not yet been generated / arrived.

[0136] - Information 4: It can be indicated that the data remaining in the UL buffer of the EoDB-LCH, excluding the data included in the MAC PDU, contains EoDB Bytes.

[0137] - Information 5: It can indicate that there is no data remaining in the UL buffer of EoDB-LCH, excluding data included in the MAC PDU.

[0138] For example, if a particular MAC PDU contains an EoDB report for a particular EoDB-LCG, the information indicated by that EoDB report is

[0139] - If there is one EoDB-LCH included in an EoDB-LCG: EoDB reporting of an EoDB-LCG can be considered as reporting an EoDB for the EoDB-LCH it contains.

[0140] - If there are two or more EoDB-LCHs included in an EoDB-LCG: EoDB reporting of an EoDB-LCG can be considered as reporting EoDB for all EoDB-LCHs included.

[0141] For example, an EoDB can be reported for an EoDB-LCH only if the MAC PDU contains the EoDB Byte of that EoDB-LCH. For example, an EoDB can be reported for an EoDB-LCG only if the MAC PDU contains the EoDB Byte of all EoDB-LCHs belonging to that EoDB-LCG.

[0142] For example, after performing LCP (Logical Channel Prioritization), if a specific MAC PDU contains an EoDB Byte of a specific EoDB-LCH, an EoDB report may be triggered for the corresponding EoDB-LCH.

[0143] For example, if EoDB reporting is triggered for all EoDB-LCHs contained in a particular EoDB-LCG, EoDB reporting may be triggered for that EoDB-LCG.

[0144] For example, EoDB-LCG / LCH that must report EoDB may mean EoDB-LCG / LCH where EoDB reporting is triggered.

[0145] For example, for an EoDB-LCH where an EoDB report is triggered, the conditions under which the EoDB report can be canceled may include at least one of the conditions below.

[0146] - The first byte of a new data burst in EoDB-LCH arrives / is created.

[0147] - MAC PDUs containing EoDB reports for EoDB-LCH or EoDB-LCG including EoDB-LCH are transmitted.

[0148] For example, if EoDB reporting is canceled for at least one EoDB-LCH contained in an EoDB-LCG for which EoDB reporting is triggered, EoDB reporting for that EoDB-LCG may also be canceled.

[0149] For example, if an EoDB report is triggered for a specific EoDB-LCG / EoDB-LCH and there are no other EoDB-LCGs / EoDB-LCHs for which EoDB reports have been triggered, EoDB-BSR may be triggered. For example, if an EoDB report is triggered for a specific EoDB-LCG / EoDB-LCH and the priority of the EoDB-LCG / EoDB-LCH is higher than the priorities of all EoDB-LCGs / EoDB-LCHs for which EoDB reports have already been triggered, EoDB-BSR may be triggered.

[0150] For example, if an EoDB report is triggered for a specific EoDB-LCG / LCH and there are no other EoDB-LCGs / LCHs for which EoDB reports have been triggered, an EoDB MAC CE may be triggered. For example, if an EoDB report is triggered for a specific EoDB-LCG / LCH and the priority of that EoDB-LCG / LCH is higher than the priorities of all EoDB-LCGs / LCHs for which EoDB reports have already been triggered, an EoDB MAC CE may be triggered.

[0151] In one embodiment of the present disclosure, a base station can instruct a terminal to use a New BS Table for each LCH / LCG of a specific Cell Group via an RRC message. For example, an LCG that can use a New BS Table (NBT) can be referred to as an NBT-LCG. For example, when reporting a buffer size for an NBT-LCG, the terminal can select and use one of the Legacy BS Table and one or more NBTs. For example, the New Short / Short Truncated / Long / Long Truncated BSR can include an indicator of the used BS Table (which can be indicated by a Table Index, Table ID, Table Bit, etc.) for each LCG / LCH / MAC CE.

[0152] For example, when configuring Regular BSR, Periodic BSR, and Padding BSR, if at least one NBT-LCG is included among the LCGs that report the buffer size through the Buffer Size field (other than EoDB reporting) among the BSR format selection conditions, the Short / Short Truncated / Long / Long Truncated BSR can be replaced with the corresponding New Short / Short Truncated / Long / Long Truncated BSR.

[0153] In one embodiment of the present disclosure, for Regular and Periodic BSR, a MAC Entity for which logicalChannelGroupIAB-Ext is not set from a higher layer may operate as follows.

[0154] - When configuring a MAC PDU including the above BSR, if there are two or more LCGs with data in the UL buffer:

[0155] --If there is at least one NBT-LCG in the LCG:

[0156] ---Using New Long BSR

[0157] --If NBT-LCG does not exist in the LCG:

[0158] ---Using Long BSR

[0159] - When configuring a MAC PDU including the above BSR, if there is only one LCG with data in the UL buffer:

[0160] --If the LCG is an NBT-LCG:

[0161] ---(Option 1) Use Short BSR

[0162] ---(Option 2) Use New Short BSR

[0163] ---(Option 3) Use New Long BSR

[0164] --If the LCG is not an NBT-LCG:

[0165] ---Use Short BSR

[0166] In one embodiment of the present disclosure, for Padding BSR, a MAC Entity for which logicalChannelGroupIAB-Ext is not set from a higher layer may operate as follows.

[0167] -If the length of the Padding Bit is greater than or equal to the sum of the lengths of the Short BSR and its Subheader, and less than the sum of the lengths of the Long BSR / New Long BSR and its Subheader:

[0168] --If there is data in the UL buffer or there are two or more LCGs that need to report EoDB (with EoDB report, with pending EoDB report):

[0169] ---If the length of the Padding Bit is equal to the sum of the length of the Short BSR and the corresponding Subheader:

[0170] ----If there is data in the UL buffer or the LCG with the highest priority among the LCGs that must report EoDB (with EoDB report, with pending EoDB report) is the LCG that must report EoDB:

[0171] -----(Option 1) Report EoDB to LCG via Short Truncated BSR

[0172] -----(Option 2) Report EoDB to LCG via New Short Truncated BSR

[0173] ----If the LCG with the highest priority among the LCGs that have data in the UL buffer or that must report EoDB (with EoDB report, with pending EoDB report) is the LCG that has data in the UL buffer:

[0174] -----Report the buffer size for the LCG via Short Truncated BSR.

[0175] ---If the length of the Padding Bit is greater than the sum of the lengths of the Short BSR and the corresponding Subheader:

[0176] ----For LCGs that have data in the UL buffer or that must report EoDB (with EoDB report, with pending EoDB report), reports can be made for the LCGs in order of priority, starting from the LCG with the highest priority and decreasing in priority, up to the number of Buffer Sizes allowed by the Padding Bit.

[0177] -----If the reportable LCGs contain at least one LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0178] ------(Option 1) For reportable LCGs, the UL buffer size or EoDB can be reported via Long Truncated BSR.

[0179] ------(Option 2) For reportable LCGs, the UL buffer size or EoDB can be reported via the New Long Truncated BSR.

[0180] -----If there is no LCG that can report EoDB (with EoDB report, with pending EoDB report) among the LCGs that can report EoDB:

[0181] ------(Option 1) For reportable LCGs, the UL buffer size can be reported via Long Truncated BSR.

[0182] ------(Option 2) If at least one NBT-LCG is included among the reportable LCGs, the UL buffer size can be reported for the reportable LCGs through New Long BSR.

[0183] --If there is data in the UL buffer or there is one LCG that needs to report EoDB (with EoDB report, with pending EoDB report):

[0184] ---If LCG needs to report EoDB (with EoDB report, with pending EoDB report):

[0185] ----(Option 1) Through Short BSR, EoDB of LCG can be reported.

[0186] ----(Option 2) Through New Short BSR, EoDB of LCG can be reported.

[0187] ---If there is data in the UL buffer of the LCG:

[0188] ----If LCG is NBT-LCG:

[0189] -----(Option 1) Short BSR can be used to report the buffer size of the LCG.

[0190] -----(Option 2) The buffer size of the LCG can be reported via the New Short BSR.

[0191] -----(Option 3) The buffer size of the LCG can be reported via the New Long BSR.

[0192] ----If LCG is not NBT-LCG:

[0193] -----With Short BSR, the buffer size of the LCG can be reported.

[0194] -If the length of the Padding Bit is greater than or equal to the sum of the lengths of Long BSR / New Long BSR and the corresponding Subheader:

[0195] --If there is at least one LCG that must report EoDB (with EoDB report, with pending EoDB report):

[0196] ---(Option 1) Long BSR allows buffer size reporting for all LCGs that have data in their UL buffers (if any) and EoDB reporting for all LCGs that must report EoDB (with EoDB report, with pending EoDB report).

[0197] ---(Option 2) If there is at least one NBT-LCG among the LCGs that have data in the UL buffer, then the New Long BSR can be used to report buffer size for all LCGs that have data in the UL buffer (if any) and EoDB for all LCGs that must report EoDB (with EoDB report, with pending EoDB report).

[0198] ---(Option 3) If there is no NBT-LCG among the LCGs that have data in the UL buffer, Long BSR can be used to report buffer size for all LCGs that have data in the UL buffer (if any) and EoDB for all LCGs that must report EoDB (with EoDB report, with pending EoDB report).

[0199] ---(Option 4) New Long BSR allows buffer size reporting for all LCGs with data in the UL buffer (if any) and EoDB reporting for all LCGs that must report EoDB (with EoDB report, with pending EoDB report).

[0200] --If there is no LCG that needs to report EoDB (with EoDB report, with pending EoDB report):

[0201] ---If at least one NBT-LCG is included among the LCGs with data:

[0202] ----(Option 1) Long BSR allows buffer size reporting for all LCGs that have data in their UL buffers.

[0203] ----(Option 2) With the New Long BSR, we can perform buffer size reporting for all LCGs that have data in their UL buffers.

[0204] ---For LCGs with data but no NBT-LCG:

[0205] ----Long BSR allows buffer size reporting for all LCGs that have data in their UL buffers.

[0206] For example, the priority of an LCG may be considered (or determined) as the priority of the LCH with the highest priority among the LCHs included in the LCG.

[0207] FIG. 7 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0208] As illustrated in FIG. 7, the terminal of the present disclosure may include a processor (720), a transceiver (700), and a memory (710). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the processor (720), the transceiver (700), and the memory (710) may be implemented in the form of a single chip.

[0209] According to one embodiment of the present disclosure, the processor (720) may control a series of processes by which the terminal may operate according to the embodiments of the present disclosure described above. For example, the processor (720) may control components of the terminal to report the end of a data burst according to the embodiments described above. The processor (720) may control components of the terminal so that the embodiments of the present disclosure described above are performed by executing a program stored in the memory (710). In addition, the processor (720) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0210] According to one embodiment of the present disclosure, a transceiver (700) can transmit and receive signals with a network entity, a base station, or another terminal. The signals transmitted and received with the network entity, the base station, or another terminal may include control information and data. The transceiver (700) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (700) is only one embodiment, and the components of the transceiver (700) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (700) may receive a signal through a wireless channel, output it to the processor (720), and transmit the signal output from the processor (720) through the wireless channel.

[0211] According to one embodiment of the present disclosure, the memory (710) can store programs and data necessary for the operation of the terminal. In addition, the memory (710) can store control information or data included in signals transmitted and received by the terminal. The memory (710) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be multiple memories (710). In addition, according to one embodiment, the memory (710) can store a program for performing the method for reporting the end of the data burst described above.

[0212] FIG. 8 illustrates the structure of a base station according to one embodiment of the present disclosure.

[0213] As illustrated in FIG. 8, the base station of the present disclosure may include a processor (820), a transceiver (800), and a memory (810). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the processor (820), the transceiver (800), and the memory (810) may be implemented in the form of a single chip.

[0214] According to one embodiment of the present disclosure, the processor (820) may control a series of processes by which a base station may operate according to the embodiments of the present disclosure described above. For example, the processor (820) may control components of the base station to perform a method for reporting the end of a data burst according to the embodiments described above. The processor (820) may control components of the base station to perform the embodiments of the present disclosure described above by executing a program stored in the memory (810). In addition, the processor (820) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0215] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with a network entity, another base station, or a terminal. The signals transmitted and received with the network entity, another base station, or a terminal can include control information and data. The transceiver (800) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (800) is only one embodiment, and the components of the transceiver (800) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (800) can receive a signal through a wireless channel, output it to the processor (820), and transmit the signal output from the processor (820) through the wireless channel.

[0216] According to one embodiment of the present disclosure, the memory (810) may store programs and data necessary for the operation of the base station. Furthermore, the memory (810) may store control information or data included in signals transmitted and received by the base station. The memory (810) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. Furthermore, there may be a plurality of memories (810). Furthermore, according to one embodiment, the memory (810) may store a program for performing the method for reporting the end of the data burst described above.

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

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

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

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

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

[0222] Meanwhile, the embodiments of the present disclosure disclosed in the present disclosure and the drawings are merely specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. In addition, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical idea of ​​the embodiments can also be implemented.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of transmitting terminal capability information related to whether an end of data burst (EoDB) indication is supported to a base station; A step of receiving, from the base station, configuration information related to the EoDB instruction, the configuration information including information on a logical channel group (LCG) to which the EoDB instruction is set; If the length of the padding bit is greater than or equal to the size of the short BSR plus the subheader of the short BSR and less than the size of the long BSR plus the subheader of the long BSR, a step of determining whether there is data available in one or more LCGs or whether the EoDB instruction is pending; and A method comprising the step of transmitting a padding buffer status report (BSR) to the base station.

2. In paragraph 1, A method wherein the buffer status report is a short truncated BSR for an LCG containing the highest priority logical channel on which the available data or the EoDB indication is pending, when the length of the padding bits is equal to the size of the short BSR plus the subheader of the short BSR.

3. In paragraph 1, A method wherein if the length of the padding bits is greater than the size of the short BSR plus the subheader of the short BSR, the buffer status report is a long truncated BSR for LCGs in decreasing priority order from the highest priority.

4. In paragraph 1, A method wherein the above BSR includes a buffer size field for LCG.

5. In paragraph 4, A method wherein the value of the buffer size field of the above BRS is set to 0 only when the EoDB instruction indicates EoDB for a pending LCG.

6. In paragraph 5, A method wherein the buffer size field of the above BSR is set to 0 to indicate EoDB for the LCG for which the EoDB instruction is pending.

7. In paragraph 5, The above EoDB is reported by LCG, how.

8. In paragraph 5, The above EoDB is reported by logical channel (LCH) included in LCG.

9. In a wireless communication system, the terminal comprises: transceiver; and Including a controller connected to the above transceiver, The above controller: Transmit terminal capability information related to whether or not the base station supports the end of data burst (EoDB) indication, A step of receiving configuration information related to the EoDB instruction from the base station, wherein the configuration information includes information on a logical channel group (LCG) to which the EoDB instruction is set, If the length of the padding bits is greater than or equal to the size of the short BSR plus the subheader of the short BSR, and less than the size of the long BSR plus the subheader of the long BSR, determine whether there is data available in one or more LCGs or whether the EoDB instruction is pending, A terminal configured to transmit a padding buffer status report (BSR) to the base station.

10. In paragraph 9, The terminal, wherein the buffer status report is a short truncated BSR for the LCG containing the highest priority logical channel for which the available data or the EoDB indication is pending, if the length of the padding bits is equal to the size of the short BSR plus the subheader of the short BSR.

11. In paragraph 9, If the length of the padding bits is greater than the size of the short BSR plus the subheader of the short BSR, the buffer status report is a long truncated BSR for LCGs in decreasing priority order from the highest priority.

12. In paragraph 9, The above BSR is a terminal including a buffer size field for LCG.

13. In paragraph 12, A terminal in which the value of the buffer size field of the above BRS is set to 0 only when the EoDB instruction indicates EoDB for a pending LCG.

14. In paragraph 13, The buffer size field of the above BSR is set to 0 to indicate EoDB for the LCG for which the EoDB instruction is pending.

15. In paragraph 13, The above EoDB is reported by LCG terminal.

Images