KR20240063760A - Method and apparatus for buffer status report in a wireless communcation system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. The present disclosure includes receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

Description

Method and apparatus for reporting buffer status in a wireless communication system {METHOD AND APPARATUS FOR BUFFER STATUS REPORT IN A WIRELESS COMMUNCATION SYSTEM}

This disclosure relates to the field of communications and to the operations of terminals and base stations. In particular, the present disclosure relates to a buffer status report (BSR) method of a terminal, a BSR acquisition method in a base station, and terminals, base stations, and communication systems related thereto.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss and increase radio wave transmission distance in ultra-high frequency bands. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets 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 the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

The disclosed embodiment seeks to provide an apparatus and method that can effectively provide services in a wireless communication system.

In order to solve the above problems, the present disclosure provides a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

The technical problems to be achieved in the embodiments of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned are clear to those skilled in the art from the description below. It will be understandable.

The present disclosure provides an apparatus and method that can effectively provide services in a wireless communication system.

1 is a diagram showing the structure of an NR system according to an embodiment of the present disclosure.
Figure 2 is a diagram showing a wireless protocol structure in an NR system according to an embodiment of the present disclosure.
FIG. 3 is a diagram illustrating a method for a terminal to determine a Buffer Status Report format in an NR system according to an embodiment of the present disclosure.
FIG. 4 is a diagram illustrating the Short BSR/Short Truncated BSR MAC CE format of the NR system according to an embodiment of the present disclosure.
FIG. 5 is a diagram illustrating the Long BSR/Long Truncated BSR MAC CE format of the NR system according to an embodiment of the present disclosure.
FIG. 6 is a diagram illustrating a Short BSR buffer size reporting table of the NR system according to an embodiment of the present disclosure.
FIG. 7 is a diagram illustrating the MAC Subheader format of the NR system according to an embodiment of the present disclosure.
Figure 8 is a diagram illustrating NBT according to an embodiment of the present disclosure.
Figure 9 is a diagram illustrating NBT according to an embodiment of the present disclosure.
Figure 10 is a diagram illustrating a procedure in which a base station and a terminal determine whether the terminal supports NBT and set NBT-related settings through RRC signaling, according to an embodiment of the present disclosure.
Figure 11 is a diagram illustrating a procedure in which a terminal reports preferred NBT or traffic characteristics to a base station through UAI and a procedure in which the base station sets NBT-related settings in the terminal, according to an embodiment of the present disclosure.
FIG. 12 is a diagram illustrating NBT Short BSR MAC CE according to an embodiment of the present disclosure.
FIG. 13 is a diagram illustrating NBT Short BSR MAC CE according to an embodiment of the present disclosure.
FIG. 14 is a diagram illustrating NBT Short BSR MAC CE according to an embodiment of the present disclosure.
Figure 15 is a diagram illustrating NBT Long BSR MAC CE according to an embodiment of the present disclosure.
FIG. 16 is a diagram illustrating NBT Long BSR MAC CE according to an embodiment of the present disclosure.
Figure 17 is a diagram illustrating NBT Long BSR MAC CE according to an embodiment of the present disclosure.
Figure 18 is a diagram illustrating NBT Long BSR MAC CE according to an embodiment of the present disclosure.
Figure 19 is a diagram illustrating NBT MAC CE according to an embodiment of the present disclosure.
Figure 20 is a diagram illustrating a method of allocating a new LCID Codepoint to NBT Short BSR, NBT Long BSR, and NBT MAC CE, according to an embodiment of the present disclosure.
Figure 21 is a diagram illustrating a method of allocating a new eLCID Codepoint to NBT Short BSR, NBT Long BSR, and NBT MAC CE, according to an embodiment of the present disclosure.
Figure 22 is a diagram illustrating an NBT Long/Short BSR application method according to an embodiment of the present disclosure.
Figure 23 shows a terminal device according to an embodiment of the present disclosure.
Figure 24 shows a base station device according to an embodiment of the present disclosure.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. At this time, it should be noted that in the attached drawings, identical components are indicated by identical symbols whenever possible. Additionally, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

In describing the embodiments in the present disclosure, description of technical content that is well known in the technical field to which the present invention belongs and that is not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

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

At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to what roles. Perform. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, 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 may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

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

Terms used in the following description include terms for identifying a connection node, terms referring to network entities or NFs (network functions), terms referring to messages, terms referring to interfaces between network objects, and various terms. Terms referring to identification information are provided as examples for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

For convenience of description below, 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 invention is not limited by the above terms and names, and can be equally applied to systems complying with other standards.

In next-generation/5G (New Radio, NR) wireless communication systems, in order to help the base station schedule resources more efficiently, the terminal needs to report the buffer status to the base station. BSR (buffer status report) expresses the amount of data stored in the terminal's buffer and is used for reporting. According to the specifications of NR, the terminal selects a section index containing the amount of buffer data to be reported from among the data amount ranges for each section defined for each index in the buffer size table and includes it in the BSR.

However, the buffer size table defined in the prior art is designed to express a larger amount of data in a longer section as the index value increases. The larger the amount of data stored in the terminal's buffer, the larger the index value has to be transmitted, which corresponds to the amount of data in a longer section, making it difficult for the base station to estimate the exact amount of data in that section, and thus efficient scheduling. This becomes difficult.

Therefore, in the present disclosure, a new buffer size table (hereinafter referred to as NBT (New BS (Buffer Size) Table)) is introduced, and the terminal reports the buffer size with reference to the NBT, thereby reporting a more detailed buffer size. proposes.

Buffer status reporting in the NR system can be performed based on MAC (Medium Access Control) layer signaling between the terminal and the base station. That is, when a Buffer Status Report (BSR) is triggered at a specific transmission time, the terminal can include a BSR control element (MAC Control Element, MAC CE) in the MAC PDU and transmit it to the base station. At this time, the BSR control element indicates the amount of packets remaining in the transmission buffer of the terminal after the corresponding MAC PDU is configured, in logical channel group (Logical Channel Group, hereinafter referred to as LCG) units. The base station can use the BSR received from the terminal to estimate the amount of data currently remaining in the terminal's buffer. In the NR system, the terminal can manage the data transmission buffer to be transmitted to the base station for each of eight LCGs.

In this disclosure, in order to convey the amount of data stored in the transmission buffer of the terminal to the base station in more detail, we propose a method by introducing NBT and reporting the buffer size to the base station by the terminal referring to the NBT.

The purpose of this disclosure is to propose a method for improving communication performance between a terminal and a base station. Additionally, the purpose of this disclosure is to propose a BSR reporting method for a terminal and a BSR acquisition method for a base station.

According to various embodiments of the present disclosure, a method for improving communication performance between a terminal and a base station can be provided. In addition, according to various embodiments of the present disclosure, a method for reporting a BSR for a terminal and a method for obtaining a BSR for a base station can be provided.

1 is a diagram showing the structure of an NR system according to an embodiment of the present disclosure.

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

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

In FIG. 1, base stations 100, 110, 120, and 130 are access nodes of a cellular network and can provide wireless access to terminals accessing the network. That is, in order to service users' traffic, the base stations (100, 110, 120, and 130) collect status information such as buffer status, available transmission power status, and channel status of the terminals and schedule them to connect the terminals and the core network (CN). , Core networks; in particular, NR's CN is called 5GC).

In Figure 1, gNB (1a-05, 1a-20) can control a plurality of cells and performs adaptive modulation coding to determine the modulation scheme and channel coding rate according to the channel status of the terminal. (Adaptive Modulation & Coding, hereinafter referred to as AMC) method may be applied.

The core network is a device that handles various control functions as well as mobility management functions for terminals and can be connected to multiple base stations. Additionally, 5GC can also be linked to existing LTE systems.

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

The AMF 140 is a device responsible for various control functions as well as mobility management functions for the terminal and is connected to a plurality of base stations, and the UPF 150 may refer to a type of gateway device that provides data transmission. Although not shown in FIG. 1, the NR wireless communication system may include a Session Management Function (SMF). SMF can manage packet data network connections such as protocol data unit (PDU) sessions provided to the terminal.

Figure 2 is a diagram showing a wireless protocol structure in an NR/LTE system according to an embodiment of the present disclosure.

Referring to Figure 2, the wireless protocols of the NR system are SDAP (Service Data Adaptation Protocol) (200) (290), PDCP (Packet Data Convergence Protocol) (210) (280), and RLC (Radio Link Control) at the terminal and base station, respectively. ) (220) (270), MAC (Medium Access Control) (230) (260).

SDAP (Service Data Adaptation Protocol) (200) (290) transmits user data, operates to map QoS flows to specific DRBs for uplink and downlink, and marks QoS flow ID for uplink and downlink. An operation of mapping a relective QoS flow to a data bearer for uplink SDAP PDUs can be performed. SDAP settings corresponding to each DRB may be provided from the upper RRC layer. Of course, it is not limited to the above example.

PDCP (Packet Data Convergence Protocol) 210 (280) may be responsible for operations such as IP header compression/restoration. Additionally, the PDCP (210) (280) can provide sequential and non-sequential delivery functions, reordering, duplication detection, retransmission functions, and encryption and decryption functions. Of course, it is not limited to the above examples.

Radio Link Control (hereinafter referred to as RLC) 220, 270 can reconfigure PDCP PDU (Protocol Data Unit) to an appropriate size. Additionally, the RLCs 220 and 270 provide sequential and non-sequential delivery functions, and may provide ARQ functions, joining, splitting, reassembling functions, repartitioning functions, reordering functions, duplication detection functions, and error detection functions. . Of course, it is not limited to the above examples.

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

The physical (PHY) layer 240 and 250 channel-codes and modulates upper layer data, creates OFDM symbols and transmits them over a wireless channel, or demodulates and channel-decodes OFDM symbols received through wireless channels to transmit them to the upper layer. It carries out the operation of transmitting to . In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiving end transmits 1 bit to indicate whether the packet sent from the transmitting end has been received. This is called HARQ ACK/NACK information.

For LTE, downlink HARQ ACK/NACK information for uplink data transmission is transmitted through the PHICH (Physical Hybrid-ARQ Indicator Channel) physical channel, and for NR, PDCCH is a channel where downlink/uplink resource allocation, etc. are transmitted. (Physical Dedicated Control CHannel) can determine whether retransmission is necessary or whether a new transmission can be performed through the terminal's scheduling information. This is because asynchronous HARQ is applied in NR. Uplink HARQ ACK/NACK information for downlink data transmission may be transmitted through PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel) physical channel. The PUCCH is generally transmitted on the uplink of the PCell, which will be described later, but if the base station supports the terminal, it may be transmitted to the corresponding terminal in addition to the SCell, which will be described later, and is called PUCCH SCell.

Although not shown in FIG. 2, there is an RRC (Radio Resource Control) layer above the PDCP layer of the terminal and the base station, and the RRC layer can transmit and receive connection and measurement-related configuration control messages for radio resource control.

Meanwhile, the physical layer may be composed of one or multiple frequencies/carriers, and a technology that simultaneously sets and uses multiple frequencies is called carrier aggregation technology (hereinafter referred to as CA). CA technology is a technology that replaces the use of only one carrier for communication between a terminal (or User Equipment, UE) and a base station (eNB or gNB) by using a main carrier and one or more secondary carriers to increase the number of secondary carriers. Transmission volume can be dramatically increased. Meanwhile, in LTE/NR, a cell within a base station using a main carrier is called a main cell or PCell (Primary Cell), and a cell within a base station using a subcarrier is called a bushel or SCell (Secondary Cell).

Figure 3 shows the Buffer Status Report (BSR, hereinafter referred to as BSR) format when the terminal reports the amount of uplink available data (hereinafter referred to as uplink buffer size) to the base station in the NR system according to an embodiment of the present disclosure. This diagram shows how to make a decision.

Referring to FIG. 3, when a UE transmits a MAC PDU including a BSR (300), the uplink buffer size is selected between Long BSR and Short BSR depending on the number of Logical Channel Groups (LCG) greater than 0. You can select one and transmit it (310). Specifically, if there are more than one LCG with an uplink buffer size larger than 0 (exceeds), the UE may select the Long BSR MAC CE (330), and if there is one, the UE may select the Short BSR MAC CE (320).

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

Referring to FIG. 4, Short BSR MAC CE may include 3-bit LCG ID (400) and 5-bit Buffer Size (410) fields. The LCG ID (400) represents the ID (0 to 7) of the LCG, and the Buffer Size (410) field displays the Buffer Size (BS) Index determined by the uplink buffer size corresponding to the LCG ID (400). BS Index has values between 0 and 31. The BS Index can display the Index of the section that includes the uplink buffer size corresponding to the LCG ID (400) among the buffer size sections defined in the predefined buffer size table (see FIG. 6).

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

Referring to Figure 5, 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 (500) to LCG ID 0 (507) with 8 bits of the first byte. there is. If the bit is 0 (540), it may mean that the Buffer Size field of LCG corresponding to the bit of Long BSR MAC CE does not exist. Conversely, if the bit is 1 (541), it may mean that the Buffer Size field of the LCG corresponding to the bit of the Long BSR MAC CE exists.

Therefore, in Long BSR MAC CE, there may be a Buffer Size field equal to the number of Bit 1s among the first bytes. The length of the Buffer Size field (510, 520, 530) of Long BSR MAC CE may be 8-bit. Long Truncated BSR MAC CE is 8 bits of the first byte and determines whether the uplink buffer size of each LCG is greater than 0 (i.e., available uplink buffer size) for each of the 8 LCGs from LCG ID 7 (500) to LCG ID 0 (507). It can be displayed whether there is link data. If Bit is 0 (550), it may mean that there is available uplink data in the corresponding LCG, and if Bit is 1 (551), it may mean that there is no available uplink data in the corresponding LCG.

In Long Truncated BSR MAC CE, the number of Buffer Size fields (510, 520, 530) can be expressed as the L (750) field of the MAC Subheader that is attached to the front of MAC CE, and the Buffer Size fields (510, 520, 530) are available data. Among the LCGs with , the remaining uplink resources are added to the MAC CE in descending order, considering the priority. Like the Buffer Size field of Short BSR, the Buffer Size field of Long BSR or Long Truncated BSR can also display the BS Index determined by the uplink buffer size.

In the NR system, a Long BSR buffer size table for Long BSR is defined, and the index of the buffer size section that includes the uplink buffer size can be displayed as the Buffer Size field. While the length of the Buffer Size (410) of Short BSR MAC CE is 5-Bit, the length of the Buffer Size field of Long BSR or Long Truncated BSR MAC CE is 8-Bit, and the buffer size table referenced by Long BSR ranges from 0 to 254. A total of 255 BS Indexes have been defined so far, and 255 are Reserved and not in use. After receiving the BS Index, the base station can refer to the buffer size table for Long BSR to obtain information about the uplink buffer size for each LCG.

FIG. 6 is a diagram illustrating a buffer size table for Short BSR defined in NR according to an embodiment of the present disclosure.

The buffer size table for Short BSR can define the BS value (610), that is, the buffer size section, corresponding to each of the 32 BS Indexes (600) expressed as 0 to 31. For example, if the BS Index (600) is 2, it means that the corresponding uplink buffer size has a value between 11 Byte and 14 Byte. After receiving the Short BSR MAC CE, the base station can perform uplink resource allocation by referring to the uplink buffer size section corresponding to the LCG ID (400) and Buffer Size (400) field values.

FIG. 7 is a diagram illustrating the format of the MAC Subheader defined in the NR system according to an embodiment of the present disclosure.

Referring to FIG. 7, a MAC CE with a fixed length may be preceded by a 1-Byte MAC Subheader consisting of R (700), F (705), and LCID (710). At this time, MAC CE can be indicated by LCID (710). Additionally, according to one embodiment, a MAC CE with a fixed length may be preceded by a 2-Byte MAC Subheader consisting of R (715), F (720), LCID (725), and eLCID (730). At this time, the presence and length of the eLCID 730 can be indicated by the LCID 725, and the MAC CE can be indicated by the eLCID 730.

Also, according to one embodiment, a MAC CE of variable length may be preceded by a 2-byte MAC Subheader consisting of R (735), F (740), LCID (745), and L (750) fields. At this time, F (740) can indicate whether the length of the L (750) field is 1-Byte or 2-Byte, and LCID (750) can indicate MAC CE. According to one embodiment, a MAC CE of variable length may be preceded by a 3-Byte MAC Subheader consisting of R (755), F (760), LCID (765), eLCID (770), and L (775). At this time, F (760) can indicate whether the length of L (775) is 1-Byte or 2-Byte, LCID (765) can indicate the presence and length of eLCID (770), and eLCID (770) can be indicated. ) can be used to indicate MAC CE. Since the LCID value of the MAC Subheader attached to the Short BSR/Short Truncated BSR/Long BSR/Long Truncated BSR is different, the base station that received it can distinguish what format the received BSR is.

Long BSR/Long Truncated BSR/Short BSR/Short Truncated BSR defined in the NR system has the following characteristics. Of course, this is not limited to the examples below.

-The BS Index expressed in the Buffer Size field of MAC CE does not correspond to a specific buffer size, but may correspond to a specific buffer size interval of a predefined table.

-The size of the buffer size section can increase as the BS Index value increases, that is, as the buffer size increases.

Therefore, the larger the uplink buffer size, the more the terminal transmits the BS Index corresponding to the larger buffer size section, and it is difficult for the base station receiving this to predict the exact buffer size, making efficient uplink resource allocation difficult.

In this disclosure, we propose a method of newly introducing NBT and reporting a more detailed buffer size section by referring to NBT when the UE reports the buffer size for each LCG to the base station. The NBT proposed in this disclosure may be a fixed table defined in advance. Of course, it is not limited to the above example. Additionally, the NBT proposed in this disclosure can be changed by the base station transmitting NBT-related parameters through an RRC message or MAC CE. Of course, it is not limited to the above example, and NBT-related parameters may be transmitted through other types of messages.

Figure 8 is a diagram illustrating a method of configuring NBT according to an embodiment of the present disclosure.

As shown in Figure 8, NBT may be composed of a total of 2 ^L indices. L may be equal to the length L-bit of the Buffer Size field of the corresponding LCG reported with reference to NBT in NBT Short BSR MAC CE or NBT Long BSR MAC CE.

For example, if the Buffer Size field of the corresponding LCG reported with reference to NBT is 13-bit, the number of Indexes in NBT may be 2 ¹³ , and the included Index may be from 0 to 2 ¹³ -1. Additionally, if the Buffer Size field of the corresponding LCG reported with reference to the NBT is 16-bit, the number of Indexes in the NBT may be 2 ¹⁶ , and the included Index may be from 0 to 2 ¹⁶ -1.

According to one embodiment, Index 0 (800) of NBT may indicate that the uplink buffer size of the corresponding LCG is 0 and there is no available data. Index 1 (810) of NBT can indicate that the uplink buffer size is greater than 0 and less than or equal to BS ₁ . That is, BS ₁ may indicate the upper limit of the BS section corresponding to Index 1 (810). In addition, NBT specifies the upper limits BS ₁ , BS ₂ , ..., BS ₂ ^L _-2 of the BS section corresponding to each index from Index 1 (810) to Index 2 ^L -2 (820). NBT can interpret the uplink buffer size section corresponding to each Index from Index 1 (810) to Index 2 ^L -2 (820) as a section with the upper limit of the immediately preceding Index as the lower limit and the upper limit of the corresponding Index as the upper limit. You can.

Additionally, as the NBT increases from Index 1 (810) to Index 2 ^L -2 (820), the upper limit of the corresponding uplink buffer size may gradually increase. For example, if Index y is greater than Index x, the corresponding upper limit value BS _y may be greater than BS _x . Index 2 ^L -1 (830) may indicate a section in which the uplink buffer size is larger than the BS ₂ ^L _-2 . In NBT, the sequence of upper limit values of the BS section corresponding to each index from Index 1 (810) to Index 2 ^L -2 (820) BS ₁ , BS ₂ , ..., BS ₂ ^L _-2 is formed by a specific rule. It can be.

-In one embodiment, the sequence may be a geometric sequence in which the ratio of two consecutive terms is constant. For example, BS ₁ can be expressed as B _min . BS ₂ ^L _-2 can be expressed as B _max . BS ₂ , ..., BS ₂ ^L _-2 is the smallest natural number among the values greater than or equal to the immediately preceding value multiplied by p (hereinafter, the smallest natural number among the values greater than or equal to x is expressed as ceil(x)) It may be the same as For example, BS _n can be expressed as ceil(p·BS _n-1 ). p can be expressed as (B _max / B _min ) ^{1 / (N-1)} . N may be equal to 2 ^L -2.

-As another example, the sequence may be an arithmetic sequence in which the difference between two consecutive terms is constant. For example, BS ₁ can be expressed as B _min . BS ₂ ^L _-2 can be expressed as B _max . BS ₂ , ..., BS ₂ ^L _-2 may be equal to the smallest natural number greater than or equal to the immediately preceding value plus p. For example, BS _n can be expressed as ceil(p+BS _n-1 ). p can be expressed as (B _max -B _min )/(N-1). N may be equal to 2 ^L -2.

B _min and B _max can be delivered by the base station to the terminal through an RRC message or MAC CE.

Figure 9 is a diagram illustrating a method of configuring NBT according to an embodiment of the present disclosure.

Referring to FIG. 9, NBT sets the lower limit of each uplink buffer size section corresponding to Index 0 (900) to Index 2 ^L -1 (930) as BS ₀ , BS ₁ , ..., BS ₂ ^L _-1. It can be displayed as . At this time, BS ₀ can be displayed as B _min . At this time, BS ₂ ^L _-1 can be expressed as B _max . Additionally, BS ₀ , BS ₁ , ..., BS ₂ ^L _-1 may be a specific sequence formed by the above-mentioned rule. As an example, BS ₀ , BS ₁ , ..., BS ₂ ^L _-1 may be a geometric sequence in which B _min is the first term and B _max is the last term. As another example, BS ₀ , BS ₁ , ..., BS ₂ ^L _-1 may be an arithmetic sequence in which B _min is the first term and B _max is the last term.

Figure 10 is a diagram illustrating a signaling procedure performed by a terminal and a base station to use NBT, according to an embodiment of the present disclosure.

Referring to FIG. 10, the base station 1010 may transmit a UECapabilityEnquiry message 1020 requesting a capability report to the terminal 1000 in a connected state. The base station may include a terminal capability request for each RAT type in the UECapabilityEnquiry message 1020. Requests for each RAT type may include requested frequency band information.

Additionally, when the base station requests the terminal 1000 to generate a UECapabilityInformation message 1030 through the capability request message 1020, it may include filtering information that can indicate conditions and restrictions. At this time, through filtering information, the base station 1010 can indicate whether the terminal 1000 should report whether or not it supports NBT. The terminal 1000 may configure a UECapabilityInformation message 1030 corresponding to the UECapabilityEnquiry message 1020 and report a response to the capability request message to the base station 1010. At this time, the UECapabilityInformation message 1310 may include a parameter indicating whether the terminal supports NBT.

As an example, a parameter may be 1 bit information. Additionally, as an example, if a parameter is included, it may be indicated that NBT is supported, and if a parameter is not included, it may be indicated that NBT is not supported. The base station 1010 may determine whether the terminal 1000 supports NBT based on the received UECapabilityInformation message 1030. If the base station 1010 determines that the terminal 1000 supports NBT, the base station 1010 sends an RRCReconfiguration message (1040) so that the terminal 1000 can report the uplink buffer size with reference to NBT when a specific condition is satisfied for a specific LCG. It can be instructed through . More specifically, for NBT-related settings, the RRCReconfiguration message 1040 may include at least one of the following configuration information. Of course, this is not limited to the examples below.

-At least one of a specific DRB or DRB List, a specific LCG or LCG List, or a specific LCH or LCH List that forces reporting of the uplink buffer size by referencing the NBT, or allows the NBT to be referenced when reporting the uplink buffer size. It can contain one.

-Can include an NBT Index or NBT number that can indicate the NBT to be referenced.

-Can include B _min, which is the smallest value excluding 0 among the upper or lower limits for each index of NBT.

-Can include B _max , which is the largest value among the upper or lower limits for each Index of NBT.

-L may be included when the number of indices of NBT or the number of indices is expressed as 2 ^L.

-When the upper or lower limit values of NBT's consecutive Indexes are expressed as a sequence, it indicates whether the sequence is a geometric sequence (including modified forms of geometric sequences) or an arithmetic sequence (including modified forms of arithmetic sequences). May contain information.

-Can include conditions that must be satisfied to refer to the NBT. As an example, the Threshold value may be included to indicate that the NBT is referenced only when the uplink buffer size of the LCG is greater than or equal to a specific Threshold value.

If the information included in the RRCReconfiguration message 1040 has already been set, the terminal 1000 that has received the RRCReconfiguration message 1040 can update the information with the information included in the RRCReconfiguration message 1040.

Figure 11 illustrates an operation in which the terminal provides NBT-related information to the base station through UEAssistanceInformation, and the base station updates the NBT settings of the terminal through RRCReconfiguration or NBT MAC CE in consideration of the information, according to an embodiment of the present disclosure. It is a drawing.

Referring to FIG. 11, when transmitting the UEAssistanceInformation message 1100 to the base station, the terminal may include the following NBT-related information.

-Can include parameters related to XR Traffic characteristics. The parameter can be a parameter that expresses the XR Data Burst Size, PDU Set Size, or the size of the XR uplink buffer periodically created in the terminal.

-The UE may include a parameter specifying whether the buffer size table to be referenced or preferred when reporting the uplink buffer size to the base station is Legacy BS Table (including BS Table for Long BSR and Short BSR) or NBT. If there are multiple candidate NBTs, a parameter specifying which NBT it is can be included.

Additionally, the above-described NBT-related information may be included in the UEAssistanceInformation message 1100 for each terminal, DRB of the terminal, LCG of the terminal, or LCH of the terminal.

Referring to FIG. 11, the base station can change the NBT-related settings of the terminal through the RRCReconfiguration message (1110) after receiving the UEAssistanceInformation message (1100) transmitted by the terminal. The RRCReconfiguration message 1110 may include the same type of configuration information as the NBT-related configuration information included in the above-described RRCReconfiguration message 1040.

The terminal that has received the RRCReconfiguration message (1110) can set the NBT-related configuration information according to the NBT-related configuration information included in the RRCReconfiguration message (1110). Referring to FIG. 11, the base station can set the NBT-related configuration information of the terminal through the NBT MAC CE (1120). The NBT MAC CE (1120) may include the same type of configuration information as the NBT-related configuration information included in the RRCReconfiguration message (1110). The NBT MAC CE (1120) may include only some types of NBT-related configuration information included in the RRCReconfiguration message (1110). The NBT MAC CE (1120) may also include other types of configuration information in addition to the NBT-related configuration information included in the RRCReconfiguration message (1110). The terminal that has received the NBT MAC CE (1120) can change the NBT-related settings according to the setting information included in the NBT MAC CE (1120).

Figure 12 is a diagram illustrating the NBT Short BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to FIG. 12, 3-bits of the first byte of NBT Short BSR MAC CE can indicate LCG ID (1200). The LCG ID (1200) can display the LCG corresponding to the uplink buffer size to be reported as NBT Short BSR. The LCG ID 1200 can display one LCG from LCG ID 0 to LCG ID 7. The Buffer Size field can be displayed as 13-bit, which is the combination of the remaining 5-bit (1210) and the second byte (1220) excluding the LCG ID 3-bit (1200) of the first byte of the NBT Short BSR MAC CE.

The Buffer Size field may display the Index of the buffer size section corresponding to the uplink buffer size of the terminal's LCG ID (1200). The buffer section may correspond to one of the index-specific buffer sections defined by NBT. At this time, NBT may include up to 2 ¹³ indices corresponding to different buffer sections.

Additionally, according to one embodiment, the Buffer Size field may directly display the uplink buffer size in bytes of the LCG ID (1200) of the terminal without referring to a specific NBT. At this time, the uplink buffer size that can be displayed as Buffer Size can range from 0 to (2 ¹³ - 1) Bytes. The terminal uses the NBT Short BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing buffer size table for Short BSR, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station.

Figure 13 is a diagram illustrating the NBT Short BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to FIG. 13, 3-bits of the first byte of NBT Short BSR MAC CE can indicate LCG ID (1300). The LCG ID 1300 may indicate the LCG corresponding to the uplink buffer size to be reported in the NBT Short BSR. The LCG ID 1300 can display one LCG from LCG ID 0 to LCG ID 7. Except for LCG ID 3-bit (1300) of the first byte of NBT Short BSR MAC CE, the remaining 5-bit (1310) can be used as a Reserved field. The 16-bit sum of the second byte (1320) and third byte (1330) of NBT Short BSR MAC CE can display the Buffer Size field.

According to one embodiment, the Buffer Size field may indicate the Index of the buffer size section corresponding to the uplink buffer size of the LCG ID (1300) of the terminal. The buffer size section may correspond to one of the index-specific buffer size sections defined by NBT. At this time, NBT may include up to 2 ¹⁶ indices corresponding to different buffer size sections.

Additionally, according to one embodiment, the Buffer Size field may directly display the uplink buffer size in bytes of the LCG ID (1300) of the terminal without referring to a specific NBT. At this time, the uplink buffer size that can be displayed as Buffer Size can range from 0 to (2 ¹⁶ - 1) Bytes. The terminal uses the NBT Short BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing buffer size table for Short BSR, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station. The NBT referenced when using NBT Short BSR MAC CE may be the same NBT as the NBT referenced when using NBT Long BSR MAC CE.

Figure 14 is a diagram illustrating the NBT Short BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to FIG. 14, the 8-bits of the first byte of the NBT Short BSR MAC CE can be interpreted as a Bitmap corresponding to 8 LCGs from LCG ID 7 to LCG ID 0, respectively. When a specific bit among the 8 bits is set to 1, the NBT Short BSR MAC CE can be interpreted as reporting the uplink buffer size of the LCG corresponding to the bit. The Buffer Size field of LCG can be displayed in 16-bit, which is the combination of the second byte (1410) and third byte (1420) of NBT Short BSR MAC CE.

According to one embodiment, the Buffer Size field may display the Index of the buffer size section corresponding to the uplink buffer size of the UE's LCG. The buffer size section may correspond to one of the index-specific buffer size sections defined by NBT. At this time, NBT may include up to 2 ¹⁶ indices corresponding to different buffer size sections.

Additionally, according to one embodiment, the Buffer Size field may directly indicate the uplink buffer size in bytes of the UE's LCG without referring to a specific NBT. At this time, the uplink buffer size that can be displayed as Buffer Size can range from 0 to (2 ¹⁶ - 1) Bytes. The terminal uses the NBT Short BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing buffer size table for Short BSR, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station. The NBT referenced when using NBT Short BSR MAC CE may be the same NBT as the NBT referenced when using NBT Long BSR MAC CE.

Additionally, according to one embodiment, the UE may report the uplink buffer size to the base station as an NBT Short BSR MAC CE that has the same format as the Short BSR MAC CE shown in FIG. 4, but has a new LCID or eLCID. At this time, the Buffer Size field 410 may display an Index corresponding to the buffer size section containing the uplink buffer size of the LCG corresponding to the LCG ID 400. The buffer size section may correspond to one of the index-specific buffer size sections defined by NBT.

Additionally, according to one embodiment, the UE may report the uplink buffer size to the base station using the Short BSR MAC CE shown in FIG. 4. At this time, the Buffer Size field 410 may display an Index corresponding to the buffer size section containing the uplink buffer size of the LCG corresponding to the LCG ID 400. The buffer size section may correspond to one of the index-specific buffer size sections defined by NBT. At this time, the base station that received the Short BSR MAC CE determines that the buffer size table that must be referred to when interpreting the Buffer Size field of the LCG transmitted by the terminal according to the NBT configuration information previously set in the terminal through RRCReconfiguration or NBT MAC CE is NBT. You can see that

Figure 15 is a diagram illustrating the NBT Long BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to Figure 15, the 8-bits (1500, 1501, 1502, 1503, 1504, 1505, 1506, 1507) of the first byte of NBT Long BSR MAC CE correspond to eight LCGs from LCG ID 7 to LCG ID 0, respectively. It can be interpreted as a Bitmap. That a specific bit among 8 bits is set to 1 may indicate that there is a Buffer Size field for reporting the uplink buffer size of the LCG corresponding to the bit set to 1 in the NBT Long BSR MAC CE. In addition, the fact that a specific bit among the 8 bits is set to 0 may indicate that there is no Buffer Size field for reporting the uplink buffer size of the LCG corresponding to the bit set to 0 in the NBT Long BSR MAC CE. .

According to one embodiment, the remaining bytes except the first byte of the NBT Long BSR MAC CE may consist of one or more Buffer Size fields. The Buffer Size field may exist for each LCG for the LCG set to 1 among the LCG ID Bitmap. The Buffer Size field for each LCG can be determined by the number of Indexes for each buffer size section defined by the NBT referenced by the LCG. For example, if the number of NBT indexes is less than or equal to 2 ^L , the Buffer Size field length may be L-bit.

For example, if the number of indices of the referenced NBT is less than or equal to 2 ¹⁶ , the Buffer Size field may have a 16-bit length by combining two consecutive bytes. At this time, the 16-bit sum of the second byte (1510) and the third byte (1520) of the NBT Long BSR MAC CE can be interpreted as the Buffer Size field of a specific LCG.

According to one embodiment, the Buffer Size field may indicate the Index of the buffer size section corresponding to the uplink buffer size of the LCG. The buffer size section may correspond to one of the index-specific buffer size sections defined by NBT. At this time, NBT may include up to 2 ¹⁶ indices corresponding to different buffer size sections.

Additionally, according to one embodiment, the Buffer Size field may directly indicate the uplink buffer size in bytes of the LCG of the terminal without referring to a specific NBT. At this time, the uplink buffer size that can be displayed in the Buffer Size field can range from 0 to (2 ^L - 1) Bytes.

L may mean the length L-bit of the Buffer Size field. For example, when L is 16, the Buffer Size field can display from 0 to (2 ¹⁶ - 1) Bytes. The terminal uses the NBT Long BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing Long BSR buffer size table, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. can be reported to the base station in more detail.

If the NBT Long BSR MAC CE includes multiple Buffer Size fields, the arrangement order of the Buffer Size fields can be determined by referring to the Priority Level of the corresponding LCG. For example, the LCGs can be arranged from the highest priority level to the lowest LCG. The priority level of the LCG can be set to the highest priority level among the priority levels of the LCH included in the LCG.

The NBT Long BSR MAC CE format can add the Buffer Size field only for LCGs that report the uplink buffer size with reference to NBT. At this time, the uplink buffer size can be reported through the existing Long BSR, Short BSR, or Padding BSR for the remaining LCGs except for the LCG reported with reference to the NBT.

Figure 16 is a diagram illustrating the NBT Long BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to Figure 16, the 8-bits (1600, 1601, 1602, 1603, 1604, 1605, 1606, 1607) of the first byte of NBT Long BSR MAC CE are from LCG ID 7 (1600) to LCG ID 0 (1607), respectively. It can be interpreted as a Bitmap corresponding to 8 LCGs. As an example, the fact that a specific bit among 8 bits is set to 1 (1671) indicates that there is a Buffer Size field for reporting the uplink buffer size of the LCG corresponding to the bit set to 1 in the NBT Long BSR MAC CE. can do.

At this time, the fact that a specific bit among the 8 bits is set to 0 (1670) may indicate that there is no Buffer Size field for reporting the uplink buffer size of the LCG corresponding to 0 bit in the NBT Long BSR MAC CE. . At this time, the buffer size table referenced by each LCG may be the buffer size table for Long BSR, or NBT, or a specific NBT among several NBTs, depending on the NBT-related settings for each LCG previously set by the base station as RRC or MAC CE. .

Additionally, according to one embodiment, being set to one of two values (0 (1680) or 1 (1681)) of a specific bit among the eight bits means that the bit corresponding to the bit set to one of the two values in the NBT Long BSR MAC CE This may mean that there is always a Buffer Size field for reporting the uplink buffer size of the LCG, and the uplink buffer size is reported with reference to the NBT.

In addition, the fact that a specific bit among the 8 bits is set to one of two values (0 (1680) or 1 (1681)) means that the uplink of the LCG corresponding to the bit that is set to the other of the two values in the NBT Long BSR MAC CE It can be indicated that the Buffer Size field for reporting the buffer size is always present, and the uplink buffer size is reported by referring to the buffer size table for Long BSR (Legacy table).

Except for the first byte of NBT Long BSR MAC CE, the remaining bytes can be composed of one or multiple Buffer Size fields. The field length allocated to the NBT Long BSR MAC CE may be determined by the buffer size table referenced by the corresponding LCG.

As an example, the Buffer Size field for each LCG may be determined by the number of Indexes included in the buffer size table referenced by the corresponding LCG. For example, when LCG refers to the buffer size table for Long BSR, the Buffer Size field may be 1-Byte. When the LCG refers to an NBT that defines 2 ^L indices, the length of the Buffer Size field may be L-bit. L may be 8. L may be 16. L can be a value greater than 16. Of course, it is not limited to the above example and the value of L is not limited.

The Buffer Size field may display an Index corresponding to the buffer size section including the uplink buffer size of the LCG in the buffer size table referenced by the LCG. The buffer size section may correspond to one of the buffer size sections for each index defined in the referenced buffer size table.

In another embodiment, the Buffer Size field may directly display the uplink buffer size in bytes of the UE's LCG without referring to a specific NBT. At this time, the uplink buffer size that can be displayed in the Buffer Size field can range from 0 to (2 ^L - 1) Bytes. L may mean the length L-bit of the Buffer Size field. For example, if L is 16, the Buffer Size field can display from 0 to (2 ¹⁶ - 1) Bytes. L can have a value greater than 16. Of course, it is not limited to the above example and the value of L is not limited.

The base station can set which LCG to display the uplink buffer size in bytes directly in the Buffer Size field to the terminal through RRC or MAC CE in advance. In the NBT Long BSR MAC CE, whether to directly report the uplink buffer size in bytes of a specific LCG can be notified to the base station by setting the bit corresponding to the LCG in the first byte of the NBT Long BSR MAC CE to a predetermined value.

The terminal uses the NBT Long BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing buffer size table for Long BSR, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station.

If the NBT Long BSR MAC CE includes multiple Buffer Size fields, the arrangement order of the Buffer Size fields can be determined by referring to the Priority Level of the corresponding LCG. For example, the LCGs can be arranged from the highest priority level to the lowest LCG. The priority level of the LCG may be set to the highest priority level among the priority levels of the LCH included in the LCG.

Figure 17 is a diagram illustrating the NBT Long BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to Figure 17, the 8-bits (1700, 1701, 1702, 1703, 1704, 1705, 1706, 1707) of the first byte of NBT Long BSR MAC CE are from LCG ID 7 (1700) to LCG ID 0 (1707), respectively. It can be interpreted as a Bitmap corresponding to 8 LCGs. As an example, the fact that a specific bit among 8 bits is set to 1 (1761) may indicate that a Buffer Size field exists in the NBT Long BSR MAC CE to report the uplink buffer size of the LCG corresponding to the specific bit. there is. At this time, the fact that a specific bit among the 8 bits is set to 0 (1760) indicates that there is no Buffer Size field for reporting the uplink buffer size of the LCG corresponding to the bit set to 0 in the NBT Long BSR MAC CE. can do.

Except for the first byte of NBT Long BSR MAC CE, the remaining bytes can be composed of one or multiple Buffer Size fields. When configuring the Buffer Size field for an LCG for which the base station has previously indicated or permitted NBT reference with RRC or MAC CE, the T field (1710, 1740) can be added in front of the Buffer Size field (1711, 1720, 1741) of the LCG. there is. The T field (1710, 1740) can be used to indicate which buffer size table the Buffer Size field (1711, 1720, 1741) of the corresponding LCG is referencing.

As an example, the T field may have a 1-bit length. At this time, one of the two values of the T field can indicate that the latter Buffer Size field refers to the buffer size table for Long BSR. Additionally, one of the two values of the T field can indicate that what the Buffer Size field refers to is NBT. At this time, the length of the Buffer Size field can be determined by the value of the T field. Of course, the length of the T field is not limited to the above example.

If the T field (1740) indicates that the buffer size table for Long BSR is referenced, the remaining 7-bit (1741) excluding the T field (1740) can be allocated to the Buffer Size field. If the T field (1710) indicates that the NBT is referenced, a total of 15 bits, including the remaining 7 bits (1711) excluding the T field (1710) and the next byte (1720), can be allocated to the Buffer Size field. You can.

At this time, the number of indices for each buffer size section defined by NBT may be less than or equal to 2 ¹⁵ . Except for LCGs for which the base station previously indicated or permitted NBT reference through RRC or MAC CE, the length of the corresponding Buffer Size fields (1730, 1750) may always be 1-Byte. At this time, LCG can always refer to the buffer size table for Long BSR. The T field length can be longer than 1-bit. At this time, the different values that the T field can have can be used to indicate which buffer size table each is referencing among several buffer size tables for NBT and Long BSR. At this time, the Buffer Size field of the LCG that indicates or allows NBT use may have 16-(T_length) bits. T_length can indicate the length in bits of the T field. Additionally, the NBT can have up to 2 ^{16-(T_length)} indices for each buffer size section.

As another example, the Buffer Size field immediately following one of the values that the T field can have may indicate that it directly displays the uplink buffer size in bytes without referring to a specific NBT. At this time, the uplink buffer size that can be displayed in the Buffer Size field can range from 0 to (2 ^16-T_length - 1) Bytes.

The terminal uses the NBT Long BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing Long BSR buffer size table, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station.

If the NBT Long BSR MAC CE includes multiple Buffer Size fields, the arrangement order of the Buffer Size fields can be determined by referring to the Priority Level of the corresponding LCG. For example, the LCGs can be arranged from the highest priority level to the lowest LCG. The priority level of the LCG may be set to the highest priority level among the priority levels of the LCH included in the LCG.

In NBT Long BSR MAC CE, which buffer size table is referenced when configuring the Buffer Size field of a specific LCG can be determined by the NBT-related settings set by the base station in advance as RRC or MAC CE. In addition, the terminal can configure and set the Buffer Size field of the LCG with reference to the NBT only when the uplink buffer size of the LCG is greater than or equal to a specific threshold value set by the base station. If the UE does not have a large uplink buffer size for a specific LCG, the signaling overhead of NBT Long BSR MAC CE can be reduced by limiting the length of the Buffer Size field without degrading performance by referring to the buffer size table for Long BSR instead of NBT. .

Figure 18 is a diagram illustrating the NBT Long BSR MAC CE format that can be used when the terminal reports the uplink buffer size to the base station with reference to the NBT, according to an embodiment of the present disclosure.

Referring to Figure 18, the first two bytes of NBT Long BSR MAC CE can be divided into 2 consecutive bits and used as 8 LCG star indicators (1800, 1801, 1802, 1803, 1804, 1805, 1806, 1807). The 2-bit indicator for each LCG can display a total of four cases. One of the four cases may indicate that the NBT Long BSR MAC CE does not have a Buffer Size field of the corresponding LCG (1850).

Among the four cases, the remaining three cases can be used when the Buffer Size field of the corresponding LCG exists. Each of the three cases can be used to indicate that a specific table among the three buffer size tables is referenced (1851, 1852, 1853). As an example, one of the three buffer size tables may be the buffer size table for Long BSR. As an example, the other two of the three buffer size tables may display different NBTs. At this time, two different NBTs may include the same number of indexes for each buffer size section, or may include a different number of indexes for each buffer size section.

Referring to FIG. 18, the remaining space except for the first two bytes of the NBT Long BSR MAC CE may be composed of one or more Buffer Size fields. At this time, the presence or absence of the Buffer Size field for each LCG can be derived by a 2-bit indicator for each LCG. The length of the Buffer Size field for each LCG can be determined by which buffer size table the LCG is referencing.

For example, if the buffer size table referenced by a specific LCG is a buffer size table for Long BSR, the corresponding Buffer Size fields 1830 and 1840 may have a 1-byte length. For example, if the buffer size table referenced by a specific LCG is NBT, and the number of indices for each buffer size section included in the NBT is 2 ^L , the Buffer Size field may have an L-bit length. L may be 8 or 16 or a value greater than 16. Of course, it is not limited to the above example.

Additionally, according to one embodiment, the Buffer Size field may directly display the uplink buffer size in Bytes without referring to a specific NBT. At this time, reporting the uplink buffer size directly through the Buffer Size field can be signaled through the 2-bit indicator of the corresponding LCG. At this time, the uplink buffer size that can be displayed in the Buffer Size field can range from 0 to (2 ^L - 1) Bytes. L may be equal to the length L-bit of the Buffer Size field.

In NBT Long BSR MAC CE, which buffer size table is referenced by each LCG can be determined by the NBT-related settings set by the base station in advance as RRC or MAC CE. Additionally, the terminal can independently determine which buffer size table to refer to based on the uplink buffer size of the LCG. Additionally, it is possible to determine which buffer size table to refer to based on the threshold set by the base station.

For example, when reporting the uplink buffer size of the LCG only if the uplink buffer size of the LCG that allows the base station to refer to the NBT is greater than or equal to a specific threshold set by the base station, the NBT can be reported with reference to the LCG. . If the UE does not have a large uplink buffer size for a specific LCG, the signaling overhead of NBT Long BSR MAC CE can be reduced by limiting the length of the Buffer Size field without degrading performance by referring to the buffer size table for Long BSR instead of NBT. .

The terminal uses the NBT Long BSR MAC CE format to refer to the NBT, which defines a more detailed buffer size section than the existing buffer size table for Long BSR, or directly expresses the uplink buffer size in bytes to determine the uplink buffer size. More details can be reported to the base station.

If the NBT Long BSR MAC CE includes multiple Buffer Size fields, the arrangement order of the Buffer Size fields can be determined by referring to the Priority Level of the corresponding LCG. For example, the LCGs can be arranged from the highest priority level to the lowest LCG. The priority level of the LCG can be set to the highest priority level among the priority levels of the LCH included in the LCG.

Figure 19 is a diagram illustrating the NBT MAC CE format transmitted to change the NBT-related settings of the terminal to the base station, according to an embodiment of the present disclosure.

Referring to FIG. 19, the NBT MAC CE may include at least one of the following information.

-Can include a Bitmap expressing whether NBT is referenced (or whether reference is allowed) for each LCG. Bitmap allocates 1-bit for each LCG, and can indicate whether the LCG should (or can refer to) the NBT with Bit 0 or 1.

-Among the upper or lower limits for each buffer size section defined in NBT, the minimum upper or lower limit excluding 0 can include the B _min value itself or the Index corresponding to B _min in a predefined table. B _min can be displayed as a 2-Byte field. B _min can be displayed as a 1-Byte field. B _min can be displayed as a field longer than 2-Byte. Of course, the length of the B _min field is not limited to the above example.

-You can directly include B _max , the largest value among the upper or lower limits for each buffer size section defined in NBT, or include the Index corresponding to B _max in a predefined table. B _max can display the value as a 1-Byte or 2-Byte or longer field than 2-Byte. Of course, the length of the B _max field is not limited to the above example.

FIG. 20 illustrates allocating a new LCID for a new MAC CE proposed in this disclosure, according to an embodiment of the present disclosure.

Referring to Figure 20, three Reserved values (e.g. 37, 38, 39) among the LCID Codepoints used in the NR system are NBT Short BSR MAC CE (2040), NBT Long BSR MAC CE (2050), and NBT MAC It indicates CE (2060) and can be assigned to each. At this time, since the NBT Short BSR MAC CE (2040) and NBT MAC CE (2060) may have a fixed length, as described in FIG. 7, the MAC consisting of R (700), F (705), and LCID (710) A subheader can be attached, and the corresponding codepoint can be displayed as LCID (710).

Since the NBT Long BSR MAC CE (2050) may be of variable length, a MAC Subheader consisting of R (735), F (740), LCID (745), and L (750) may be attached as described in FIG. 7. At this time, the codepoint 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).

The Codepoint value in FIG. 20 is not necessarily limited to a specific value. This is an example and is not limited to the value in FIG. 20. Additionally, a feature of the present disclosure is that it indicates NBT Short BSR MAC CE, NBT Long BSR MAC CE, and NBT MAC CE through a specific Codepoint/Index.

FIG. 21 is a diagram illustrating an example of assigning a new eLCID to a newly defined MAC CE, according to an embodiment of the present disclosure.

Referring to Figure 21, three Reserved values (e.g. 0, 1, 2) among the eLCID Codepoints used in the NR system are NBT Short BSR MAC CE (2100), NBT Long BSR MAC CE (2120), and NBT MAC. It indicates CE (2120) and can be assigned to each. At this time, the NBT Short BSR MAC CE (2100) and NBT MAC CE (2120) may have a fixed length, so R (715), F (720), LCID (725), and eLCID (730) as described in FIG. ) may be attached to the MAC Subheader. At this time, the existence and length of the eLCID (730) can be indicated with the LCID (725), and the Codepoint corresponding to the MAC CE can be indicated with the eLCID (730).

Since the NBT Long BSR MAC CE (2110) can be of variable length, the MAC Subheader consisting of R (755), F (760), LCID (765), eLCID (770), and L (775) is It can stick. At this time, the Codepoint corresponding to the MAC CE can be displayed with eLCID (770), and the length of the MAC CE can be displayed with L (775).

As shown in Figure 21, the relationship between Codepoint, Index, and LCID can be indicated. Meanwhile, the Codepoint value is not necessarily limited to the Index value and LCID information in FIG. 21, and this corresponds to an example. A feature of the present disclosure is that a specific Codepoint matches a specific Index, and the specific Codepoint and Index indicate an LCID such as NBT Short BSR MAC CE, NBT Long BSR MAC CE, and NBT MAC CE.

FIG. 22 is a diagram illustrating a method for a terminal to report an uplink buffer size with reference to an NBT, according to an embodiment of the present disclosure.

Referring to FIG. 22, in the step of configuring the MAC PDU, the UE may decide to include the BSR in the MAC PDU (2200). If the terminal decides to include a BSR in the MAC PDU, it can be checked (2210) whether the number of LCGs with available data among the terminal's LCGs is greater than 1.

If the number of LCGs with available data among LCGs is 1, the terminal can check (2250) whether the LCG with available data refers to the NBT when reporting the uplink buffer size. If the LCG with available data references NBT when reporting the uplink buffer size, the UE can apply the NBT Short BSR MAC CE format to the BSR (2270). If the LCG with available data refers to the buffer size table for Short BSR when reporting the uplink buffer size, the terminal can apply the Short BSR MAC CE format to the BSR (2260).

Referring to FIG. 22, when the number of LCGs with available data is greater than 1, the terminal checks (2220) whether at least one LCG that references the NBT exists when reporting the uplink buffer size among the LCGs with available data. You can. If there is at least one LCG that references NBT when reporting the uplink buffer size among the LCGs with available data, the UE may apply the NBT Long BSR MAC CE format as the BSR format (2240). If, among the LCGs with available data, there is no LCG that references the NBT when reporting the uplink buffer size, the UE may apply the Long BSR MAC CE format as the BSR format (2230).

According to an embodiment of the present disclosure, whether a specific LCG refers to the NBT when reporting the uplink buffer size may be determined by the NBT-related settings set by the base station in advance through RRC or MAC CE. In addition, the terminal may determine whether to refer to the NBT by additionally considering whether the uplink buffer size of the LCG is larger than the threshold preset by the base station.

As an example of the present disclosure, the Logical Channel Priority of NBT Long BSR and NBT Short BSR may be defined in the following order. Of course, this is not limited to the examples below.

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

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

-MAC CE for Sidelink Configured Grant Confirmation;

-MAC CE for LBT failure;

-MAC CE for Timing Advance Report;

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

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

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

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

-MAC CE for the number of Desired Guard Symbols;

-MAC CE for Case-6 Timing Request;

-MAC CE for (Extended) Pre-emptive BSR;

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

-MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

-data from any Logical Channel, except data from UL-CCCH;

-MAC CE for NBT Long/Short BSR, with exception of included for padding;

-MAC CE for Recommended bit rate query;

-MAC CE for BSR included for padding;

-MAC CE for SL-BSR included for padding.

According to an embodiment of the present disclosure, the NBT Long/Short BSR may be simultaneously included in the same MAC PDU in a complementary manner to the Long/Short BSR. Of course, it is not limited to the above example. NBT Long/Short BSR may have a Logical Channel Priority lower than data from any Logical Channel, except data from UL-CCCH. If the same MAC PDU includes both NBT Long/Short BSR and Long/Short BSR, the uplink buffer size of LCG reported in NBT Long/Short BSR will be reported to the base station based on the Buffer Size field value of NBT Long/Short BSR. You can.

According to an embodiment of the present disclosure, the Logical Channel Priority of NBT Long/Short BSR may be equal to MAC CE for (Extended) BSR, with exception of BSR included for padding.

According to an embodiment of the present disclosure, the Logical Channel Priority of LCG data reported in NBT Long/Short BSR can be set as the example below. Of course, this is not limited to the examples below. The Logical Channel Priority of LCG data reported as NBT Long/Short BSR may be at a specific location between MAC CE for BFR and MAC CE for (Extended) BSR, with exception of BSR included for padding.

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

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

-MAC CE for Sidelink Configured Grant Confirmation;

-MAC CE for LBT failure;

-MAC CE for Timing Advance Report;

-data from any LCG reported in NBT Long/Short BSR

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

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

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

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

-MAC CE for the number of Desired Guard Symbols;

-MAC CE for Case-6 Timing Request;

-MAC CE for (Extended) Pre-emptive BSR;

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

-MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

-data from any Logical Channel, except data from UL-CCCH;

-MAC CE for Recommended bit rate query;

-MAC CE for BSR included for padding;

-MAC CE for SL-BSR included for padding.

According to an embodiment of the present disclosure, Logical Channel Priority of NBT Long/Short BSR may be defined in the following order. Of course, this is not limited to the examples below.

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

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

-MAC CE for Sidelink Configured Grant Confirmation;

-MAC CE for LBT failure;

-MAC CE for Timing Advance Report;

-MAC CE for NBT Long/Short BSR, with exception of included for padding;

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

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

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

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

-MAC CE for the number of Desired Guard Symbols;

-MAC CE for Case-6 Timing Request;

-MAC CE for (Extended) Pre-emptive BSR;

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

-MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

-data from any Logical Channel, except data from UL-CCCH;

-MAC CE for Recommended bit rate query;

-MAC CE for BSR included for padding;

-MAC CE for SL-BSR included for padding.

According to an embodiment of the present disclosure, the Logical Channel Priority of the uplink data of the LCG reported as NBT Long/Short BSR and NBT Long/Short BSR may be defined in the following order. Of course, this is not limited to the examples below.

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

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

-MAC CE for Sidelink Configured Grant Confirmation;

-MAC CE for LBT failure;

-MAC CE for Timing Advance Report;

-MAC CE for NBT Long/Short BSR, with exception of included for padding;

-data from any LCG reported in NBT Long/Short BSR

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

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

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

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

-MAC CE for the number of Desired Guard Symbols;

-MAC CE for Case-6 Timing Request;

-MAC CE for (Extended) Pre-emptive BSR;

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

-MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

-data from any Logical Channel, except data from UL-CCCH;

-MAC CE for Recommended bit rate query;

-MAC CE for BSR included for padding;

-MAC CE for SL-BSR included for padding.

According to an embodiment of the present disclosure, NBT Long BSR/NBT Long Truncated BSR is the same MAC CE Format as Long BSR/Long Truncated BSR, but may have different LCID/eLCID. For example, the 8 bits of the first byte of NBT Long BSR/NBT Long Truncated BSR, from LCG 7 to LCG 0, respectively, determine whether the Buffer Size field corresponding to each LCG exists in the corresponding NBT Long BSR/NBT Long Truncated BSR. It can be used as an indicator to indicate something.

Additionally, according to one embodiment, the length of the Buffer Size field of NBT Long BSR/NBT Long Truncated BSR may be 8 Bits, similar to Long BSR/Long Truncated BSR. For example, NBT Long BSR/NBT Long Truncated BSR may include Buffer Size fields corresponding to LCG whose bit is set to 1 among the first bytes. For example, when a plurality of Buffer Size fields are included in NBT Long BSR/NBT Long Truncated BSR, the arrangement order of the Buffer Size fields can be determined by the Ascending Order method based on LCG _i (LCG _i indicates logical channel group i). .

Additionally, according to one embodiment, NBT Long BSR/NBT Long Truncated BSR/Long BSR/Long Truncated BSR determines which MAC CE is the MAC CE transmitted by the terminal through different LCIDs or different eLCIDs of the MAC Subheader of the corresponding MAC CE. The base station can identify (or distinguish) the recognition.

According to one embodiment, NBT Long BSR/NBT Long Truncated BSR includes only LCGs that report buffer sizes with reference to NBT, and can be used to report the buffer sizes of corresponding LCGs. For example, if a specific LCG is capable of/allowed to refer to NBT by the base station RRC or MAC CE settings, the UE may set the Buffer Size field of the LCG to refer to the NBT, and the Buffer Size field of the LCG will be set to NBT Long BSR. /NBT Long Truncated May be included and reported in BSR. Conversely, if the Buffer Size field of the relevant LCG is set by referring to the Legacy BS Table (e.g., equivalent to Table 6.1.3.1-2 of TS 38.321), the Buffer Size field of the relevant LCG is reported through Long BSR/Long Truncated BSR. It can be. For example, due to the base station RRC or MAC CE settings, other LCGs excluding LCGs that are possible/allowed to reference NBT can only refer to the Legacy BS Table. Of course, it is not limited to the above example, and the LCGs that can be referenced in the NBT and Legacy BS Table may be set separately depending on the settings of the base station, and all LCGs may refer to the NBT and Legacy BS Table.

According to an embodiment of the present disclosure, when the Buffer Size field for a specific LCG is reported through NBT Long BSR/NBT Long Truncated BSR, the base station may interpret it with reference to the NBT when interpreting the Buffer Size field of the LCG. there is. Conversely, if the Buffer Size field for a specific LCG is reported through Long BSR/Long Truncated BSR, the base station uses the Legacy BS Table (e.g., Table 6.1.3.1 of TS 38.321) when interpreting the Buffer Size field of the LCG. It can be interpreted by referring to -2).

For example, for an LCG for which NBT reference is possible/allowed through the base station's RRC setting or MAC CE, the UE determines that the buffer size of the corresponding LCG falls within the buffer size range covered by/included in the NBT. In this case, the buffer size can be reported by referring to the NBT. Conversely, if the buffer size of the LCG does not fall within the buffer size range covered by/included in the NBT, the UE reports the buffer size of the LCG in the Legacy BS Table (e.g., TS 38.321 (corresponding to Table 6.1.3.1-2).

According to an embodiment of the present disclosure, after a Regular or Periodic BSR is triggered, when a BSR is included in a specific MAC PDU, the terminal may operate as follows.

-If logicalChannelGroup-IAB-Ext is not set by the upper layer in that MAC Entity:

--When a MAC PDU containing the corresponding BSR is created, if there is data available in more than one LCG:

---If, among the LCGs for which data is available, at least one LCG references an NBT:

----NBT Long BSR reports buffer size for all LCGs that reference NBT among those with available data

---If among the LCGs with available data, there is only one LCG that references the Legacy BS Table:

----Option 1: Through Short BSR, report the buffer size of the corresponding LCG

----Option 2: Through Long BSR, report the buffer size of the corresponding LCG

---If there are two or more LCGs that refer to the Legacy BS Table among the LCGs with available data:

----Through Long BSR, among LCGs with available data, report the buffer size of all LCGs that refer to the Legacy BS Table

--Other cases:

---If there is one LCG with available data and that LCG references an NBT:

----NBT Through Long BSR, report the buffer size of the corresponding LCG

---If there is one LCG with available data and that LCG references the Legacy BS Table:

----If the LCG in question is an LCG capable/allowed for NBT referencing:

-----Option 1: Through Long BSR, report the buffer size of the corresponding LCG

-----Option 2: Through Short BSR, report the buffer size of the corresponding LCG

----If the LCG is not an LCG capable/allowed for NBT referencing:

-----Option 1: Through Short BSR, report the buffer size of the corresponding LCG

-----Option 2: Through Long BSR, report the buffer size of the corresponding LCG

For example, among LCGs with available data, if more than one LCG refers to the Legacy BS Table and more than one LCG refers to the NBT at the same time, one Legacy BSR (Long BSR, Long Truncated BSR, Short BSR, Short Truncated BSR, etc.) and one NBT BSR (NBT Long BSR, NBT Long Truncated BSR, NBT Short BSR, NBT Short Truncated BSR, etc.) may be included together.

For example, a MAC PDU that has one Legacy BSR (Long BSR, Long Truncated BSR, Short BSR, Short Truncated BSR, etc.) and one NBT BSR (NBT Long BSR, NBT Long Truncated BSR, NBT Short BSR, NBT Short Truncated BSR, etc.) When included, buffer size reporting for a specific LCG may only be included in one of the two BSRs, based on the referencing BS Table.

For example, the NBT Long BSR may include only a Buffer Size field (one Buffer Size field) for one LCG.

For example, NBT's Index/Codepoint 0 may be designed to indicate that there is no data available in the buffer.

For example, the number of Buffer Size fields included in NBT Long BSR may be 0.

For example, if the MAC PDU reflects all BSR trigger events immediately before MAC PDU assembly: 1) only Long BSR without NBT Long BSR, or 2) only NBT Long BSR without Long BSR, or 3) Long BSR and NBT Long BSR If all are included, all BSRs triggered up to just before MAC PDU assembly can be cancelled.

Figure 23 shows a terminal device according to an embodiment of the present disclosure.

As shown in FIG. 23, the terminal of the present disclosure may include a processor 2320, a transceiver 2300, and a memory 2310. 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 aforementioned components. In addition, the processor 2320, the transceiver 2300, and the memory 2310 may be implemented in the form of a single chip.

According to an embodiment of the present disclosure, the processor 2320 can control a series of processes in which the terminal can operate according to the above-described embodiment of the present disclosure. For example, the processor 2320 may control components of the terminal to perform the method for reporting buffer status according to the above-described embodiments. The processor 2320 may control the components of the terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory 2310. Additionally, the processor 2320 may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the present disclosure, the transceiver 2300 can transmit and receive signals with a network entity, another terminal, or a base station. Signals transmitted and received from network entities, other terminals, or base stations may include control information and data. The transceiver 2300 may be comprised of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 2300, and the components of the transceiver 2300 are not limited to the RF transmitter and RF receiver. Additionally, the transceiver 2300 may receive a signal through a wireless channel and output it to the processor 2320, and transmit the signal output from the processor 2320 through a wireless channel.

According to an embodiment of the present disclosure, the memory 2310 can store programs and data necessary for operation of the terminal. Additionally, the memory 2310 may store control information or data included in signals transmitted and received by the terminal. The memory 2310 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories 2310. Additionally, according to one embodiment, the memory 2310 may store a program for performing the method for reporting the buffer status described above.

Figure 24 shows a base station device according to an embodiment of the present disclosure.

As shown in FIG. 24, the base station of the present disclosure may include a processor 2420, a transceiver 2400, and a memory 2410. However, the components of the base station are not limited to the above examples. For example, a base station may include more or fewer components than those described above. In addition, the processor 2420, the transceiver 2400, and the memory 2410 may be implemented in the form of a single chip.

According to an embodiment of the present disclosure, the processor 2420 can control a series of processes by which the base station can operate according to the above-described embodiment of the present disclosure. For example, the processor 2420 may control components of the base station to perform the method for buffer status reporting according to the above-described embodiments. The processor 2420 may control the components of the base station to perform the above-described embodiments of the present disclosure by executing a program stored in the memory 2410. Additionally, the processor 2420 may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the present disclosure, the transceiver 2400 can transmit and receive signals with a network entity, another base station, or a terminal. Signals transmitted and received from network entities, other base stations, or terminals may include control information and data. The transceiver 2400 may be comprised of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 2400, and the components of the transceiver 2400 are not limited to the RF transmitter and RF receiver. Additionally, the transceiver 2400 may receive a signal through a wireless channel and output it to the processor 2420, and transmit the signal output from the processor 2420 through a wireless channel.

According to an embodiment of the present disclosure, the memory 2410 can store programs and data necessary for the operation of the base station. Additionally, the memory 2410 may store control information or data included in signals transmitted and received by the base station. The memory 2410 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories 2410. Additionally, according to one embodiment, the memory 2410 may store a program for performing the method for reporting the buffer status described above.

Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, a plurality of each configuration memory may be included.

In addition, the program can be accessed through a communication network such as the Internet, Intranet, LAN (Local Area Network), WLAN (Wide LAN), or SAN (Storage Area Network), or a combination of these. It may be stored in an attachable storage device that can be accessed. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the present disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, 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, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it is obvious to those skilled in the art that other modifications based on the technical idea of the present disclosure can be implemented. Additionally, each of the above embodiments can be operated in combination with each other as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure and another embodiment. Additionally, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical idea of the embodiments may also be implemented.

Claims (1)

Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
A control signal processing method comprising transmitting a second control signal generated based on the processing to the base station.

Images