Method and apparatus for selecting BSR format in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the present disclosure provides a method and apparatus for a terminal and a base station to transmit and receive a BSR according to a BSR format.

Description

Technical Field

[0001] This disclosure relates to wireless communication (or mobile communication). More specifically, this disclosure relates to the operation of terminals and base stations in wireless or mobile communication, and specifically to methods for buffer state reports (BSRs) for terminals, methods for obtaining (or acquiring) BSRs by base stations, and terminals, base stations, and associated communication systems. Background Technology

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

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

[0004] Currently, given the services that 5G mobile communication technology needs to support, there is ongoing discussion about improvements and performance enhancements to the initial 5G mobile communication technology. Furthermore, there is already physical layer standardization for technologies such as: V2X (Vehicle-to-Everything) to assist autonomous vehicles in making driving decisions based on information sent by the vehicle about its location and status and to enhance user convenience; NR-U (New Radio Unlicensed) designed to comply with various regulatory requirements in unlicensed frequency bands; NR UE power saving; non-terrestrial networks (NTNs) for UE-satellite direct communication to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning.

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

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

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

[0008] With the recent development of communication systems, the need to improve the BSR transmission and reception process is constantly growing.

[0009] The above information is presented as background information only to aid in understanding this disclosure. No determination is made, and no assertion is made, regarding whether anything in the foregoing can be used as prior art with respect to this disclosure. Summary of the Invention

[0010] Solution to the problem

[0011] The disclosed embodiments are intended to provide an apparatus and method for efficiently providing services in a wireless communication system. Specifically, this disclosure provides a method and apparatus for efficiently improving the BSR transmission and reception process.

[0012] The technical topics pursued in the embodiments of this disclosure may not be limited to the above-described technical topics, and those skilled in the art to which this disclosure pertains can clearly understand other technical topics not mentioned through the following description.

[0013] This disclosure provides an apparatus and method for efficiently providing services in a wireless communication system.

[0014] According to embodiments of this disclosure, a method executed by a terminal is provided. The method includes: identifying a logical channel group (LCG) configured with an additional buffer size table; and, if the LCG configured with the additional buffer size table has data available for transmission, sending a first long buffer status report (BSR) to a base station, wherein the first long BSR corresponds to the additional buffer size table, and wherein the amount of data available for transmission is within the buffer size of the additional buffer size table.

[0015] According to embodiments of this disclosure, a terminal is provided. The terminal includes a transceiver; and a controller coupled to the transceiver and configured to: identify a logical channel group (LCG) configured with an additional buffer size table, and, if the LCG configured with the additional buffer size table has data available for transmission, send a first long buffer status report (BSR) to a base station, wherein the first long BSR corresponds to the additional buffer size table, and wherein the amount of data available for transmission is within the buffer size of the additional buffer size table.

[0016] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” is inclusive, referring to and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, being included in, interconnected with, containing, contained within, connected to or connected to, coupled to or coupled to, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound to, having, having the properties of, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software or some combination of at least two of these. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0017] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable medium includes media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0018] Definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of the words and phrases defined in this way. Attached Figure Description

[0019] The above and other aspects, features and advantages of certain embodiments of this disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, wherein:

[0020] Figure 1 The structure of a novel radio (NR) system according to an embodiment of this disclosure is shown;

[0021] Figure 2 The radio protocol structure in an NR system according to an embodiment of this disclosure is shown;

[0022] Figure 3 The Media Access Control (MAC) subheader format in an NR system according to an embodiment of this disclosure is shown;

[0023] Figure 4 The format of a short BSR / short truncated BSR MAC control element (CE) for an NR system according to an embodiment of this disclosure is shown;

[0024] Figure 5 The long BSR / long truncated BSR MAC CE format of an NR system according to an embodiment of this disclosure is shown;

[0025] Figure 6 An extended short BSR MAC CE format for an NR system according to an embodiment of this disclosure is shown;

[0026] Figure 7 This illustrates the process by which a base station and a terminal establish an XR-Ext-related configuration via RRC signaling, and whether the terminal supports XR-Ext, according to embodiments of this disclosure.

[0027] Figure 8 The structure of a terminal according to an embodiment of this disclosure is shown; and

[0028] Figure 9 The structure of a base station according to an embodiment of this disclosure is shown. Detailed Implementation

[0029] The following discussion Figures 1 to 9 The various embodiments used to describe the principles of this disclosure in this patent document are merely illustrative and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0030] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, in the drawings, the same or similar elements are represented by the same or similar reference numerals wherever possible. Furthermore, detailed descriptions of known functions or configurations that might obscure the subject matter of the present disclosure will be omitted.

[0031] In describing embodiments, descriptions relating to technical content known in the art and not directly related to this disclosure will be omitted. This omission of unnecessary description is intended to prevent obscuring the main ideas of this disclosure and to more clearly convey them.

[0032] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of each element do not perfectly reflect the actual dimensions. In the various drawings, the same or corresponding elements are given the same or corresponding reference numerals.

[0033] The advantages and features of this disclosure, as well as the ways in which they are implemented, will be apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in a variety of different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0034] In this document, it will be understood that each box in a flowchart illustration, and combinations of boxes in a flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium, which can instruct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing including means for implementing the functions specified in the flowchart boxes or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowchart boxes.

[0035] Furthermore, each box in the flowchart diagram may represent a module, fragment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may occur out of order. For example, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order, depending on the functions involved.

[0036] As used herein, a “cell” refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, a “cell” is not always limited to software or hardware. A “cell” can be configured to reside in addressable memory or execute on one or more processors. Therefore, a “cell” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a “cell” can be combined into a smaller number of elements or “cells”, or divided into a larger number of elements or “cells.” Furthermore, elements and “cells” can be implemented as one or more CPUs within a playback device or secure multimedia card.

[0037] In the following description, a base station is an entity that allocates resources to terminals and can be at least one of a Node B, an eNode B (eNB), a gNode B (gNB), a radio access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0038] Furthermore, the embodiments of this disclosure described below can also be applied to other communication systems with similar technical backgrounds or channel types as those of this disclosure. Moreover, based on the assessment of those skilled in the art, the embodiments of this disclosure can be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure. Examples of other communication systems may include 5th generation mobile communication technologies (5G, New Radio, NR) developed beyond LTE-A, and in the following description, "5G" can be a concept encompassing existing LTE, LTE-A, and other similar services. Additionally, based on the assessment of those skilled in the art, this disclosure can be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure.

[0039] In the following description, for convenience, terms for identifying access nodes, referring to network entities or network functions (NFs), referring to messages, referring to interfaces between network entities, referring to various types of identification information, etc., are used illustratively. Therefore, this disclosure is not limited to the terms used below, and other terms that refer to subjects with equivalent technical meanings may be used.

[0040] In the following description, for ease of description, some terms and names defined in the 3GPP Long Term Evolution (LTE) standard and / or the 3GPP New Radio (NR) standard may be used. However, this disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards.

[0041] Wireless communication systems are evolving into broadband wireless communication systems that use communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, and typical voice-based services to provide high-speed and high-quality packet data services.

[0042] As a typical example of a broadband wireless communication system, the LTE system employs an Orthogonal Frequency Division Multiplexing (OFDM) scheme in the downlink (DL) and a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme in the uplink (UL). The uplink instructs the terminal (or UE) to transmit data or control signals to the base station (BS) (or eNB, gNB) via its radio link, and the downlink instructs the base station to transmit data or control signals to the terminal via its radio link. These multiple access schemes separate the data or control information of each user by allocating and operating time-frequency resources for transmitting data or control information to each user, thus avoiding overlap and establishing orthogonality.

[0043] As a post-LTE communication system, 5G communication systems must freely reflect the various requirements of users, service providers, and others, and therefore must support services that meet diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC), among others.

[0044] According to embodiments, eMBB is designed to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide the UE with increased user-aware data rates, as well as a maximum data rate. To meet these requirements, improvements to transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, may be necessary. Alternatively, the required data rates for 5G communication systems can be achieved using frequency bandwidths greater than 20MHz in the 3 to 6 GHz band or 6 GHz or higher, instead of using up to 20MHz of transmission bandwidth in the 2 GHz band used in LTE.

[0045] Furthermore, mMTC support for application services such as the Internet of Things (IoT) in 5G communication systems is being considered. mMTC has requirements such as supporting a large number of UEs in a cell, enhanced UE coverage, improved battery life, and reduced UE costs in order to effectively deliver IoT. Since IoT provides communication capabilities while being supplied to various sensors and devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UEs / km). 2 Furthermore, mMTC-enabled UEs may require wider coverage than other services offered by 5G communication systems because the UE may be located in shadow areas (such as the basement of a building) that are not covered by the cell due to the nature of the service. mMTC-enabled UEs must be configured to be inexpensive and may require very long battery life, such as 10 to 15 years, because it is difficult to frequently replace the UE's battery.

[0046] Finally, URLLC (a cellular-based mission-critical wireless communication service) can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alerts, and more. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms and require a packet error rate of 10⁻⁵ or less. Therefore, for services supporting URLLC, 5G systems must provide shorter Transmission Intervals (TTIs) than other services and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0047] The three services considered in 5G communication systems—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the different requirements of each service, different transmit / receive technologies and parameters can be used between services. However, mMTC, URLLC, and eMBB are merely examples of different types of services, and the types of services to which this disclosure applies are not limited to these examples.

[0048] Furthermore, in the following description, LTE, LTE-A, LTE Pro, 5G (or NR), or 6G systems will be described by way of example; however, the embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Moreover, based on the determination of those skilled in the art, the embodiments of this disclosure can be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure.

[0049] In next-generation / 5G (New Radio (NR)) wireless communication systems, terminals need to report buffer status to the base station to help the base station schedule resources more efficiently. Buffer Status Reports (BSRs) are used to represent and report the amount of data stored in the terminal's buffers. According to the NR specification, the terminal selects the interval index to report the amount of buffer data within the range of data amounts defined for each interval in the buffer size table, and includes the selected interval index in the BSR.

[0050] However, buffer size tables, as typically defined, are designed to represent larger amounts of data at longer intervals as the index value increases. The larger the amount of data stored in the terminal's buffer, the larger the index value that should be sent. Because larger index values ​​correspond to larger amounts of data in longer intervals, it becomes difficult for the base station to identify the exact amount of data in a given interval, thus making efficient scheduling challenging.

[0051] Therefore, this disclosure proposes a new buffer size (BS) table (hereinafter referred to as NBT). Furthermore, by introducing the new buffer size table (NBT), this disclosure proposes a new BSR format that can be referenced to the NBT, and proposes a method for a terminal to select and report one of several BSR formats including the new BSR format as appropriate.

[0052] In NR systems, buffer status reporting can be performed based on MAC layer signaling between the terminal and the base station. In other words, when a BSR is triggered at a specific transmission time, the terminal can include a BSR control element (MAC CE) in its MAC Protocol Data Unit (MAC PDU) to transmit it to the base station. The BSR control element indicates the number of packets in a logical channel group (LCG) unit. After the corresponding MAC PDU has been configured, the packets are retained in the terminal's transmission buffer. The base station can estimate the amount of data currently remaining in the terminal's buffer by using the BSR received from the terminal. In NR systems, the terminal can manage the transmission buffer for data to be sent to the base station for each of the eight LCGs.

[0053] This disclosure proposes a method in which an NBT is introduced in order to transmit a specific amount of data stored in a transmission buffer at a terminal to a base station, and the terminal reports the buffer size to the base station by referring to the NBT.

[0054] This disclosure aims to provide a method for improving the communication performance of a terminal and a base station. Furthermore, this disclosure aims to provide a method for a terminal to report a Base Station Response Time (BSR) and a method for a base station to obtain a BSR.

[0055] Various embodiments of this disclosure can provide a method for improving the communication performance of a terminal and a base station. Furthermore, various embodiments of this disclosure can provide a method for a terminal to report a BSR and a method for a base station to obtain a BSR.

[0056] Figure 1 The structure of an NR system according to an embodiment of this disclosure is shown.

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

[0058] According to embodiments of this disclosure, user equipment (hereinafter referred to as "UE" or "terminal") 160 can access external networks through base stations 100, 110, 120, 130 and UPF 150.

[0059] exist Figure 1In this context, base stations 100, 110, 120, and 130 can serve as access nodes for the cellular network and provide wireless access to terminals accessing the network. In other words, to serve user services, base stations 100, 110, 120, and 130 can collect terminal status information (such as buffer status, available transmission power status, channel status, etc.) and perform scheduling, thereby supporting the connection between the terminal and the core network (CN, specifically, the CN in NR is referred to as 5GC).

[0060] exist Figure 1 In this context, gNB 100 and 130 can control multiple cells and can apply adaptive modulation and coding (AMC) methods to determine the modulation scheme and channel coding rate based on the channel state of the terminal.

[0061] The core network can serve as a device responsible for terminal mobility management functions and various control functions, and is connected to multiple base stations. 5GC can also be associated with existing LTE systems. In the following text, each of the functions included in the core network can be described as an entity or node.

[0062] On the other hand, in wireless communication, the user plane (UP) related to actual user data transmission and the control plane (CP), such as connection management, can be configured separately. Figure 1 In this context, gNB 100 and 130 can use the UP and CP technologies defined in NR technology, and although ng-eNB 110 and 120 are connected to 5GC, ng-eNB can use the UP and CP technologies defined in LTE technology.

[0063] The AMF 140 is a device configured to perform various control functions and mobility management functions for terminals, and it connects to multiple base stations. The UPF 150 can refer to a gateway device used to provide data transmission. Although not explicitly stated... Figure 1 As shown, however, NR wireless communication systems can also include Session Management Function (SMF). SMF can manage packet data network connections, such as PDU sessions provided to terminals.

[0064] Figure 2 The radio protocol structure in an NR / LTE system according to an embodiment of this disclosure is shown.

[0065] Reference Figure 2 The radio protocols of the NR system may include Service Data Adaptation Protocol (SDAP) 200 and 290, Packet Data Convergence Protocol (PDCP) 210 and 280, Radio Link Control (RLC) 220 and 270, and MAC 230 and 260 in the terminal and base station, respectively.

[0066] SDAP 200 and 290 can perform the following operations: transmit user data and map Quality of Service (QoS) flows to specific data radio bearers (DRBs) for uplink and downlink; tag uplink and downlink QoS flow IDs; and map reflected QoS flows to data bearers for uplink SDAP PDUs. SDAP configurations corresponding to each DRB can be provided from a higher RRC layer. Of course, this is not limited to the examples above.

[0067] PDCP 210 and 280 can handle operations such as compression / reconstruction of Internet Protocol (IP) headers. Furthermore, PDCP 210 and 280 can provide ordered and unordered delivery capabilities, sequence reordering, duplicate detection, retransmission, encryption, and decryption functions. Of course, the examples above are not limited to these.

[0068] Radio Link Control (RLC) 220 and 270 can reconfigure PDCP PDUs to an appropriate size. RLC 220 and 270 can also provide ordered and out-of-order delivery capabilities, Automatic Repeat Request (ARQ) capabilities, concatenation, segmentation and reassembly capabilities, resegmentation capabilities, sequence reordering capabilities, duplicate detection capabilities, and error detection capabilities. Of course, the examples above are not limited to these.

[0069] MAC 230 and 260 can connect to multiple RLC layer devices configured in a single terminal and can perform operations such as multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. MAC 230 and 260 can also provide mapping functions, scheduling information reporting functions, Hybrid ARQ (HARQ) functions, priority processing functions between logical channels, priority processing functions between terminals, Multimedia Broadcast / Multicast Service (MBMS) service identification functions, transmission format selection functions, and padding functions. Of course, the above examples are not limited to these.

[0070] Physical (PHY) layers 240 and 250 can perform the following operations: channel coding and modulation of higher-layer data, forming the higher-layer data into OFDM symbols, transmitting the OFDM symbols via radio channels, or demodulating OFDM symbols received via radio channels, channel decoding of OFDM symbols, and transmitting the OFDM symbols to higher layers. Furthermore, the physical layer uses HARQ for additional error correction, and the receiving node can send information about whether it has received a packet from the transmitting node as a single bit. This information is called a HARQ acknowledgment (ACK) / negative ACK (NACK) message.

[0071] In LTE, downlink (DL) HARQ ACK / NACK information for uplink (UL) data transmission is sent via the Physical Hybrid ARQ Indicator Channel (PHICH). In NR, the need for retransmission and whether to perform a new transmission can be determined by the terminal's scheduling information in the Physical Dedicated Control Channel (PDCCH), which is used to send downlink / uplink resource allocation channels. This is because NR uses asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be sent via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The PUCCH is sent in the uplink within the primary cell (PCell), which will be described later. However, when terminal support is present, the base station may additionally send the PUCCH to the terminal, even in the secondary cell (SCell), which will be described later; in this case, the SCell is referred to as the PUCCH SCell.

[0072] Although not in Figure 2 As shown, however, the Radio Resource Control (RRC) layer exists above the PDCP layer of both the terminal and the base station, and the RRC layer can send and receive access / measurement related configuration control messages to perform radio resource control.

[0073] On the other hand, the PHY layer can be configured with one or more frequencies / carriers, and the technique of configuring multiple frequencies at once and then using multiple frequencies is called carrier aggregation (CA). According to CA, in communication between a terminal (or user equipment (UE)) and a base station (eNB or gNB) that is using a single carrier, a primary carrier and one or more secondary carriers are additionally used, and therefore the transmission capacity can be increased by the number of secondary carriers. In LTE / NR, the cell in a base station using the primary carrier is called the primary cell or PCell, and the cell in a base station using secondary carriers is called the secondary cell or SCell.

[0074] Figure 3 The format of the MAC sub-header defined in the NR system according to an embodiment of the present disclosure is shown.

[0075] refer to Figure 3Alternatively, a 1-byte MAC subheader, including an R field 300, an F field 305, and a Logical Channel Identifier (LCID) field 310, can be appended before the fixed-length MAC CE. In this case, the MAC CE can be represented by the LCID 310. Alternatively, according to an embodiment, a 2-byte MAC subheader, including an R field 315, an F field 320, an LCID field 325, and an Extended LCID (eLCID) field 330, can be appended before the fixed-length MAC CE. In this case, the presence and length of the eLCID field 330 can be represented by the LCID field 325, and the MAC CE can be represented by the eLCID field 330.

[0076] Additionally, according to an embodiment, a 2-byte MAC subheader including an R field 335, an F field 340, an LCID field 345, and an L field 350 can be appended before the variable-length MAC CE. The F field 340 can indicate whether the L field 350 has a length of 1 byte or 2 bytes, and the MAC CE can be represented by the LCID field 345. According to an embodiment, a 3-byte MAC subheader including an R field 355, an F field 360, an LCID field 365, an eLCID field 370, and an L field 375 can be appended before the variable-length MAC CE. In this case, the F field 360 can indicate whether the length of the L field 375 is 1 byte or 2 bytes, the LCID field 365 can indicate the presence and length of the eLCID field 370, and the eLCID field 370 can represent the MAC CE. Short BSRs / short truncated BSRs / long BSRs / long truncated BSRs have different LCID values ​​in the MAC subheader appended to them, and therefore the base station receiving them can distinguish the format of the received BSR. Extended Short BSR, Extended Long BSR, Extended Short Truncated BSR, and Extended Long Truncated BSR have different eICID values ​​in the MAC sub-header attached to them, and therefore the base station receiving them can distinguish the format of the received BSR.

[0077] Figure 4 The short BSR / short truncated BSR MAC CE format defined in an NR system according to an embodiment of this disclosure is shown.

[0078] refer to Figure 4The short BSR MAC CE may include a 3-bit LCG ID field 400 and a 5-bit buffer size field 410. The LCG ID field 400 represents the ID of the LCG (0 to 7), and the buffer size (BS) field 410 represents a buffer size (BS) index determined by the uplink buffer size corresponding to the LCG ID field 400. The BS index has values ​​between 0 and 31. The BS index may represent an index of a corresponding interval, which includes the uplink buffer size corresponding to the LCG ID field 400 within the buffer size intervals defined in the predefined buffer size table for the 5-bit BS field.

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

[0080] refer to Figure 5 The long BSR MAC CE can be represented by using the eight bits of the first byte to correspond to the eight LCGs from LCG7 ID500 to LCG0 ID507. s The presence or absence of the corresponding buffer size field in the table. A bit value "0" 540 indicates that the buffer size field of the LCG corresponding to the bits of the long BSR MAC CE is absent. Conversely, a bit value "1" 541 indicates that the buffer size field of the LCG corresponding to the bits of the long BSR MAC CE is present.

[0081] Therefore, a long BSR MAC CE can contain as many buffer size fields as the number of bits with a value of 1 in the first byte. The buffer size fields 510, 520, and 530 of the long BSR MAC CE can be 8 bits long. A long truncated BSR MAC CE can use eight bits of the first byte to represent eight LCGs from LCG7ID 500 to LCG0ID 507. s The uplink buffer size of each LCG is greater than zero (i.e., whether there is available uplink data). A bit value of "0" (550) indicates that the corresponding LCG has no available uplink data, and a bit value of "1" (551) indicates that the corresponding LCG has available uplink data.

[0082] In a long truncated BSR MAC CE, the number of buffer size fields 510, 520, and 530 can be represented by the L field 350 or 375 in the MAC subheader appended to the MAC CE, and the buffer size (BS) fields 510, 520, and 530 add the remaining uplink resources to the MAC CE in descending order, taking into account the priority of the LCG with available data. The buffer size field in a long BSR or long truncated BSR can also represent a BS index, which is determined by the uplink buffer size, similar to the buffer size field in a short BSR.

[0083] The NR system has defined a buffer size table for the 8-bit BS field of long BSRs / long truncated BSRs, and the BS field can display an index of the buffer size range, including the uplink buffer size. While the BS field 410 of a short BSR is 5 bits long, the BS field of a long or long truncated BSR is 8 bits long. Accordingly, the buffer size table referenced by the long BSR defines a total of 255 BS indices from 0 to 254, with "255" reserved and not in use. After receiving the BS index, the base station can refer to the buffer size table for long BSRs to obtain information about the uplink buffer size for each LCG.

[0084] Figure 6 The extended short BSR / extended short truncated BSRMAC CE format defined in an NR system according to an embodiment of this disclosure is shown.

[0085] refer to Figure 6 The extended short BSR / extended short truncated BSR may include an 8-bit LCG ID field 600 and an 8-bit BS field 610. The LCG ID field 600 represents the ID of the LCG (0 to 255), and the BS field 610 represents the BS index determined by the uplink buffer size corresponding to the LCG ID 600. The BS index may represent an index of a corresponding interval, which includes the uplink buffer size corresponding to the LCG ID field 600 within the buffer size intervals defined in the predefined buffer size table for the 8-bit BS field.

[0086] The long BSR / long truncated BSR / short BSR / short truncated BSR / extended short BSR / extended short truncated BSR defined in the NR system have the following characteristics. They are not limited to the following embodiments.

[0087] - A BS index represented by the BS field of MAC CE can correspond to a specific buffer size interval in a predefined table, rather than a specific buffer size.

[0088] - The size of the buffer size range can increase as the BS index value increases, that is, as the buffer size increases.

[0089] Therefore, the larger the uplink buffer size, the greater the likelihood that the terminal will send a BS index corresponding to a larger buffer size interval, and the base station receiving the BS index may have difficulty predicting the exact buffer size, thus making it difficult to perform effective uplink resource allocation.

[0090] In this disclosure, the BS table used for the aforementioned existing 5-bit BS field and 8-bit BS field is referred to as the existing BS table. For example, according to an embodiment, in addition to the existing BS table, a new BS table (NBT) is introduced, so that the terminal can report the buffer size interval in more detail by referring to the NBT when reporting the buffer size to the base station. The NBT proposed in this disclosure can be a predefined fixed table. Of course, this is not limited to the above example. Furthermore, the NBT proposed herein can also be dynamically configured or changed by the base station transmitting NBT-related parameters to the terminal via RRC messages or MAC CE. Of course, this is not limited to the above example, and NBT-related parameters can be transmitted via other types of messages.

[0091] The NBT-related parameters can be one or more of the following parameters, such as minimum buffer size (Bmin), maximum buffer size (Bmax), BS interval size, number of BS intervals, and method of dividing BS intervals (e.g., uniform or exponential). According to embodiments of this disclosure, if the NBT has a BS index number of 2L, then the NBT can be referred to as an NBT with an L-bit BS field.

[0092] According to embodiments of this disclosure, when a BSR sent by a terminal to a base station includes at least one BS field referencing an NBT report, the BSR may be referred to as an NBT BSR.

[0093] According to embodiments of this disclosure, NBT BSRs can be classified as follows.

[0094] - NBT Short BSR: An NBT short BSR can report the uplink buffer size of a specific LCG or logical channel (LCH) by including only one BS field. For example, an NBT short BSR can indicate the presence of a BS field corresponding to an LCG or LCH by including an indicator that indicates the ID of the LCG or LCH used to report the uplink buffer size. The LCG or LCH indicator can be configured by directly indicating the value of the corresponding LCG or LCH ID in binary format, or by indicating a bit in the corresponding position of the bitmap as "1". For example, the BS field length of an NBT short BSR can be one of 5 bits, 8 bits, 13 bits, 15 bits, or 16 bits. In the example, the BS field length of an NBT short BSR can be greater than 16 bits. In the example, an NBT short BSR can include a reserved field for byte alignment. In the example, an NBT short BSR can include a table indicator to indicate which BS table the reported LCG or LCH BS field is referencing. For example, a candidate BS table can include an existing BS table and one or more NBTs.

[0095] - NBT Long BSR: The NBT Long BSR can report the uplink buffer size of one or more LCGs or LCHs by configuring a BS field for each LCG or LCH. For example, the NBT Long BSR may include a bitmap field, where the NBT Long BSR can configure bits in the positions corresponding to the LCG or LCH to be reported to specific values, and can indicate the presence of a BS field for the LCG or LCH in the NBT Long BSR. For example, the NBT Long BSR may include a table indicator that indicates which BS table the corresponding BS field refers to for each reported LCG or LCH. For example, the table indicator may exist only for LCGs or LCHs for which the base station has previously established specific characteristics (e.g., may be referred to as XR-Ext) using a pre-defined RRC message or MAC CE. For example, BS table candidates may include existing BS tables and one or more NBTs. In the example, the length of the BS field can be one of 8 bits, 15 bits, and 16 bits. In the example, the length of the BS field can be greater than 16 bits. In the example, the NBT Long BSR may include a reserved field for byte alignment.

[0096] According to embodiments of this disclosure, when a terminal reports the uplink buffer size to the base station via the NBT BSR,

[0097] - For example, you can configure all the BS fields included in the corresponding NBT BSR by referring to the NBT.

[0098] - For example, you can configure an LCG with XR-Ext in the BS field included in the corresponding NBT BSR by referring to the NBT.

[0099] - For example, you can configure an LCG with XR-Ext in the BS field included in the corresponding NBT BSR by referring to an existing BS table.

[0100] - For example, for each LCG configured with XR-Ext, an indicator that indicates which BS table to reference and configure can be added to the NBT BSR in the BS field included in the corresponding NBT BSR.

[0101] According to embodiments of this disclosure, the BSRs that a terminal can send to a base station can be classified as follows.

[0102] -5-bit BS field BSR (e.g., it can be called 5B-BSR): The length of all BS fields included in the corresponding BSR can be 5 bits. For example, this type of BSR can be a short BSR or a short truncated BSR.

[0103] - BS fields with more than 5 bits in length (e.g., it can be called an M5B-BSR): All BS fields included in the corresponding BSR can be longer than 5 bits. For example, this type of BSR can be one of a long BSR, a long truncated BSR, an extended short BSR, an NBT short BSR, and an NBT long BSR. For example, when all BS fields included in addition to the above BSRs are longer than 5 bits, the BSR can be called an M5B-BSR.

[0104] Figure 7 The signaling process performed by a terminal and a base station according to embodiments of the present disclosure is illustrated.

[0105] refer to Figure 7 The base station 710 can deliver a UE Capability Enquiry message 720 requesting a capability report to the terminal 700 in a connected state. The base station can include a Radio Access Technology (RAT) type-specific UE capability request in the UE Capability Enquiry message 720. The RAT type-specific request can include the frequency band information to be requested.

[0106] Additionally, when the base station requests the terminal 700 to generate a UECapabilityInformation message 730 via a UECapabilityEnquiry message 720, the base station may include filtering information in the message that can indicate conditions and limitations. The filtering information may allow the base station 710 to instruct the terminal 700 whether it should report whether the terminal supports XR-Ext. The terminal 700 may configure a UE Capability Information message (UECapabilityInformation) 730 corresponding to the UECapabilityEnquiry message 720 and report its response to the UECapabilityEnquiry message to the base station 710. For example, the UECapabilityInformation message 730 may include parameters indicating whether the terminal supports XR-Ext. For example, the parameter may be 1 bit of information. Furthermore, for example, including the parameter may indicate support for XR-Ext, and the absence of the parameter may indicate non-support for XR-Ext. For example, the UECapabilityInformation message 730 may include an indicator indicating which of the aforementioned BSR formats the terminal supports.

[0107] Base station 710 can determine that terminal 700 supports XR-Ext based on the received UECapabilityInformation message 730. Base station 710 can also determine which BSR format terminal 700 supports based on the received UECapabilityInformation message 730. When base station 710 determines that terminal 700 supports XR-Ext, base station 710 can instruct XR-Ext-related configuration via a predetermined RRC message (e.g., RRCReconfiguration message 740).

[0108] More specifically, the XR-Ext-related configuration may include at least one of the following configuration information. Of course, the configuration is not limited to the following examples.

[0109] -XR-Ext can be configured for one or more LCHs or one or more LCGs, one or more MAC entities, or the corresponding terminal.

[0110] - For one or more LCHs or one or more LCGs, one or more MAC entities or corresponding terminals, when only the corresponding LCG or LCH has available data while other LCGs or LCHs do not, the XR-Ext-related configuration can indicate which M5B-BSR format should be used.

[0111] The -XR-Ext-related configuration can include table indicators to be referenced when configuring the BS field for each LCH, LCG, MAC entity, or UE.

[0112] The -XR-Ext-related configuration can include Bmin, which is the smallest non-zero value of the upper or lower bound of each index in the NBT.

[0113] The -XR-Ext-related configuration can include Bmax, which is the maximum non-zero value of the upper or lower bound of the NBT for each index.

[0114] The -XR-Ext-related configuration can include the number of NBT indices, or L when the number of indices is represented by 2L.

[0115] - When the BS intervals of NBTs have the same size, the XR-Ext-related configuration can include the BS interval size.

[0116] The -XR-Ext-related configuration may include indicators that specify the method (e.g., uniform or exponential) used to divide the BS intervals of the NBT.

[0117] According to embodiments of this disclosure, the reserved values ​​of LCID code points used by the NR system can be assigned to indicate NBT short BSR, NBT long BSR, and extended short BSR, respectively.

[0118] According to embodiments of this disclosure, the reserved values ​​of eLCID code points used by the NR system can be assigned to indicate NBT short BSR, NBT long BSR, and extended short BSR, respectively.

[0119] According to embodiments of this disclosure, when a base station establishes an XR-Ext for one or more LCGs or one or more LCHs of a terminal via an RRC message, the terminal may operate as follows.

[0120] - For example, when XR-Ext is configured for a specific LCH, the terminal may assume that XR-Ext is also configured for the LCG to which the corresponding LCH belongs.

[0121] - Within a specific MAC entity, for regular and periodic BSRs, the terminal can operate as follows.

[0122] When constructing a MAC PDU that includes the corresponding BSR, if two or more LCGs have available uplink data,

[0123] When there is no LCG configured with XR-Ext among the LCGs with available data:

[0124] Long BSRs can be used to report the uplink buffer size of all LCGs with available data.

[0125] When at least one LCG with XR-Ext configured exists among the LCGs with available data:

[0126] The NBT long BSR can be applied to report the uplink buffer size for all LCGs with available data.

[0127] If an LCG has available uplink data when constructing a MAC PDU that includes the corresponding BSR,

[0128] If the LCG has a configured XR-Ext:

[0129] M5B-BSR can be used to report the uplink buffer size of the LCG.

[0130] For example, when only the available uplink data for the corresponding LCG is available, if the base station has already configured the terminal with which BSR format should be applied via RRC, the terminal can apply the corresponding BSR format.

[0131] If the LCG is not configured with XR-Ext:

[0132] 5B-BSR can be applied to report the uplink buffer size of the LCG.

[0133] If an LCG with available uplink data does not exist when constructing the MAC PDU that includes the corresponding BSR:

[0134] 5B-BSR can be used to report that no data is available in the uplink buffer.

[0135] According to embodiments of this disclosure, if the base station has configured XR-Ext for one or more MAC entities of the terminal via RRC messages, the terminal can operate as follows.

[0136] - For example, when XR-Ext is configured for a specific LCH or LCG, the terminal may assume that XR-Ext is also configured for the MAC entity to which the LCH or LCG belongs.

[0137] - Within a specific MAC entity, for regular and periodic BSRs, the terminal can operate as follows.

[0138] When constructing a MAC PDU that includes the corresponding BSR, if there is available uplink data in two or more LCGs.

[0139] XR-Ext is not configured for the corresponding MAC entity:

[0140] Long BSRs can be used to report the uplink buffer size of all LCGs with available data.

[0141] When XR-Ext is configured for the corresponding MAC entity:

[0142] The NBT long BSR can be applied to report the uplink buffer size for all LCGs with available data.

[0143] When available uplink data exists in an LCG during the construction of a MAC PDU that includes the corresponding BSR,

[0144] When XR-Ext is configured for the corresponding MAC entity:

[0145] M5B-BSR can be used to report the uplink buffer size of the LCG.

[0146] For example, when uplink data for the corresponding LCG is available only, if the base station has already configured the terminal with which BSR format should be applied via RRC, the terminal can apply the corresponding BSR format.

[0147] When XR-Ext is not configured for the corresponding MAC entity:

[0148] 5B-BSR can be applied to report the uplink buffer size of the LCG.

[0149] If an LCG with available uplink data does not exist when constructing the MAC PDU that includes the corresponding BSR:

[0150] 5B-BSR can be used to report that no data is available in the uplink buffer.

[0151] According to embodiments of this disclosure, if the base station has configured XR-Ext for one or more LCHs of the terminal via RRC messages, the terminal can operate as follows.

[0152] - Within a specific MAC entity, for regular and periodic BSRs, the terminal can operate as follows.

[0153] When constructing a MAC PDU that includes the corresponding BSR, if there is available uplink data in two or more LCGs.

[0154] When there is no LCH configured with XR-Ext among the LCHs with available uplink data:

[0155] Long BSRs can be used to report the uplink buffer size of all LCGs with available data.

[0156] When there is at least one LCH configured with XR-Ext among the LCHs with available uplink data:

[0157] The NBT long BSR can be applied to report the uplink buffer size for all LCGs with available data.

[0158] When an LCG with available uplink data exists during the construction of a MAC PDU that includes the corresponding BSR,

[0159] When there is at least one LCH configured with XR-Ext among the LCHs with available uplink data:

[0160] M5B-BSR can be used to report the uplink buffer size of the LCG.

[0161] For example, when uplink data for the corresponding LCG is available only, if the base station has already configured the terminal with which BSR format should be applied via RRC, the terminal can apply the corresponding BSR format.

[0162] When there is no LCH configured with XR-Ext among the LCHs with available uplink data:

[0163] 5B-BSR can be applied to report the uplink buffer size of the LCG.

[0164] If an LCG with available uplink data does not exist when constructing the MAC PDU that includes the corresponding BSR:

[0165] 5B-BSR can be used to report that no data is available in the uplink buffer.

[0166] According to embodiments of this disclosure, if the base station has configured XR-Ext for one or more configured authorizations (CGs) of the terminal via RRC messages, the terminal can operate as follows:

[0167] - Within a specific MAC entity, for regular and periodic BSRs, the terminal can operate as follows.

[0168] When constructing a MAC PDU that includes the corresponding BSR, if there is available uplink data in two or more LCGs.

[0169] The MAC PDU to be sent to the UL license is not the CG configured for XR-Ext:

[0170] Long BSRs can be used to report the uplink buffer size of all LCGs with available data.

[0171] When the corresponding MAC PDU is to be sent to a UL license that is configured with XR-Ext CG:

[0172] The NBT long BSR can be applied to report the uplink buffer size for all LCGs with available data.

[0173] When available uplink data exists in an LCG during the construction of a MAC PDU that includes the corresponding BSR,

[0174] When the MAC PDU is to be sent to a UL license that is configured with XR-Ext:

[0175] M5B-BSR can be used to report the uplink buffer size of the LCG.

[0176] For example, when uplink data for the corresponding LCG is available only, if the base station has already configured the terminal with which BSR format should be applied via RRC, the terminal can apply the corresponding BSR format.

[0177] When the MAC PDU is to be sent to a UL license that is not configured with XR-Ext CG:

[0178] 5B-BSR can be applied to report the uplink buffer size of the LCG.

[0179] If an LCG with available uplink data does not exist when constructing the MAC PDU that includes the corresponding BSR:

[0180] 5B-BSR can be used to report that no data is available in the uplink buffer.

[0181] According to embodiments of this disclosure, when a base station is able to configure XR-Ext for a specific terminal, the terminal can operate as follows.

[0182] - Within a specific MAC entity, for regular and periodic BSRs, the terminal can operate as follows.

[0183] When constructing a MAC PDU that includes the corresponding BSR, if there is available uplink data in two or more LCGs.

[0184] When the terminal is not configured with XR-Ext:

[0185] Long BSRs can be used to report the uplink buffer size of all LCGs with available data.

[0186] When the terminal is configured with XR-Ext:

[0187] The NBT long BSR can be applied to report the uplink buffer size for all LCGs with available data.

[0188] If uplink data is available in an LCG when constructing a MAC PDU that includes the corresponding BSR,

[0189] When the terminal is configured with XR-Ext

[0190] M5B-BSR can be used to report the uplink buffer size of the LCG.

[0191] For example, when uplink data for the corresponding LCG is available only, if the base station has already configured the terminal with which BSR format should be applied via RRC, the terminal can apply the corresponding BSR format.

[0192] When the terminal is not configured with XR-Ext:

[0193] 5B-BSR can be applied to report the uplink buffer size of the LCG.

[0194] When constructing a MAC PDU that includes the corresponding BSR, there is no LCG with available uplink data:

[0195] 5B-BSR can be used to report that no data is available in the uplink buffer.

[0196] According to embodiments of this disclosure, when the length of the padding bits in a padding BSR for a specific MAC entity is at least 3 bytes, the terminal can use an M5B-BSR to send the padding BSR. For example, the MAC subheader of an M5B-BSR transmitted via a padding BSR can indicate the format of the corresponding BSR in the LCID field. In the example, the M5B-BSR sent via a padding BSR can be an extended short BSR.

[0197] According to embodiments of this disclosure, when the LCG corresponding to a BS field included in the M5B-BSR is configured to reference the NBT, the terminal can configure the corresponding BS field by referencing the NBT. According to embodiments of this disclosure, when the LCG corresponding to a BS field included in the M5B-BSR is configured not to reference the NBT, the terminal can configure the corresponding BS field by referring to an existing BS table.

[0198] According to embodiments of this disclosure, a terminal can report the remaining time (RT) of data stored in the uplink buffer to the base station to assist the base station in efficient uplink resource scheduling. For example, the RT of specific uplink data can indicate that sending the corresponding uplink data to the base station after a certain time has elapsed is no longer meaningful. For example, the RT of specific uplink data can indicate that the data should be delivered to the base station before the corresponding time has elapsed.

[0199] According to embodiments of this disclosure, a terminal can report to a base station by adding one or more fields to the delay report MAC CE that correspond to one or more possible combinations of information or conditions described below. For example, the delay report MAC CE may be obtained by adding fields corresponding to the BSR format described above (e.g., 5B-BSR, M5B-BSR), or by adding fields corresponding to a newly defined individual MAC CE.

[0200] - Each LCG can include an RT field indicating the corresponding RT. One or more RT fields can exist corresponding to a specific LCG.

[0201] - Each LCH can include an RT field indicating the corresponding RT. One or more RT fields can exist corresponding to a specific LCH.

[0202] - When an RT field corresponds to a specific LCG or LCH, the presence of the RT field corresponding to the LCG or LCH can be indicated by including an LCG or LCH indicator corresponding to the RT field. The LCG or LCH indicator can represent the ID of the LCG or LCH by using specific bits of the bitmap or directly as a binary value.

[0203] - When a base station has pre-configured the corresponding functions for one or more LCGs or one or more LCHs via a pre-defined RRC message (e.g., RRCReconfiguration), only the LCGs or LCHs for which the corresponding functions have been configured can include the corresponding RT field or have RT attributes. For example, if the above configuration is configured for a specific LCH, the LCG to which the LCH belongs can also be considered to have the configured functions.

[0204] - When the base station has pre-configured RT thresholds for each UE, each MAC entity, each LCG, or each LCH via a pre-defined RRC message (e.g., RRCReconfiguration), only LCGs or LCHs with RTs within the allowable range indicated by the RT threshold, sets of PDUs buffered on the LCH, data bursts buffered on the LCH, or PDUs buffered on the LCH can include the corresponding RT field or have RT attributes. For example, if the RT threshold indicates a single specific RT value, the allowable range can be RT intervals equal to or less than, or equal to or greater than, the indicated value. For example, when the RT threshold includes both an upper and lower limit, the allowable range can be RT intervals equal to or greater than the corresponding lower limit and equal to or less than the upper limit.

[0205] - In the case of configuring an RT field for each LCG:

[0206] The corresponding RT field can be configured based on the minimum RT among the RTs corresponding to LCHs that have RT attributes and belong to LCGs.

[0207] The corresponding RT field can be configured based on the average RT of the LCH that has the RT attribute and belongs to the LCG.

[0208] The corresponding RT field can be configured using the RT corresponding to the representative LCH configured by the base station among the LCHs belonging to the LCG.

[0209] - When configuring one or more RT fields for each LCG:

[0210] The corresponding RT field can be added to each LCH that has the RT attribute and belongs to the LCG, and the RT field can be configured based on the RT corresponding to each LCH.

[0211] For each LCH that has an RT attribute and belongs to an LCG, the corresponding RT field can be added only to the RT attribute that belongs to the allowable RT range indicated by the base station, and the RT field can be configured based on the corresponding RT.

[0212] - When data buffered in a specific LCH is configured within a data unit comprising multiple RTs:

[0213] The RT corresponding to LCH can be determined as the smallest RT among multiple RTs in the data unit.

[0214] The multiple RT fields corresponding to the LCH can each indicate multiple RTs in the data unit. For example, the RT field can exist only for RTs that fall within the allowable RT range indicated by the base station.

[0215] A single RT field corresponding to the LCH can indicate the RT corresponding to the LCH. For example, this RT field can exist as long as the base station is within the range of permissible RTs pre-configured by the base station.

[0216] - In the example, the data unit used for a specific RT in the data buffered in the LCH can be a PDU, a set of PDUs, or a data burst.

[0217] - In the example, when an RT field exists, a buffer size field corresponding to the RT indicated by the RT field can be added. In the example, one or more buffer size fields can exist for each LCH or LCG. In the example, one or more buffer size fields can exist for each RT field.

[0218] - In the example, a buffer size field can be added to each LCH or LCG. For example, including an LCH or LCG indicator corresponding to the buffer size field can indicate the existence of a buffer size field corresponding to the LCH or LCG. The LCH or LCG indicator can indicate the ID of the LCH or LCG by a bit at a specific position in the bitmap or directly as a binary value. For example, a specific buffer size field for an LCH or LCG can be added only to LCHs or LCGs with the RT attribute.

[0219] According to embodiments of this disclosure, the RT of a particular data unit can be determined by one of the following examples, in conjunction with the RT field included in the configuration delay report MAC CE.

[0220] -Refer to the configuration latency report for the MAC CE time point and the remaining latency budget (DB).

[0221] -Refer to the remaining DB including the time point at which the initial transmission of the MAC PDU of the delayed report MAC CE occurred.

[0222] -Refer to the remaining DB at the time point when the UL license required to send the MAC PDU including the MAC CE was received.

[0223] According to embodiments of this disclosure, DB may refer to one of the following: PDU setting delay budget (PSDB), 5G access network PSDB (5G-AN PSDB), packet delay budget (PDB), or the PDCP discardTimer time of the corresponding data unit. However, this disclosure is not limited to the above examples.

[0224] According to embodiments of this disclosure, the RT field of the Delay Report MAC CE can indicate the index to which the RT belongs by referring to an RT table that includes a predefined index for each RT interval.

[0225] According to embodiments of this disclosure, the RT field of the delay report MAC CE can indicate RT by using an absolute value in a specific unit or a pre-configured relative value based on a reference time in a specific unit. For example, the specific unit can be represented by a combination of one or more of milliseconds, microseconds, symbols, time slots, subframes, and frames.

[0226] According to embodiments of this disclosure, the triggering conditions for delayed reporting MAC CE may include at least one of the following conditions.

[0227] - UL data for a logical channel belonging to an LCG becomes available to the MAC entity; and the UL data belongs to a logical channel with a higher priority than any logical channel that includes available UL data belonging to any LCG; or the logical channels belonging to an LCG do not contain any available UL data.

[0228] - Allocate UL resources, and the number of padding bits is equal to or greater than the size of the delayed report MAC CE plus its sub-header.

[0229] -periodicDelayReportTimer expires

[0230] - When new uplink data appears, if the LCH or LCG to which the uplink data belongs has the RT attribute and the RT of the uplink data is equal to or less than a specific threshold configured by the base station through a pre-defined RRC message, a delay report MACCE can be triggered.

[0231] - When new uplink data appears, if the LCH or LCG to which the uplink data belongs has the RT attribute and the uplink data with RT exists in the LCH or LCG to which the uplink data belongs, then a delay report MAC CE can be triggered, where the RT is equal to or less than a specific threshold reconfigured by the base station via a predetermined RRC message.

[0232] - A delay report MAC CE can be triggered when new uplink data with an RT equal to or less than a specific threshold predefined by the base station exists in the uplink buffer of an LCG or LCH with an RT attribute, or when the RT of existing data becomes equal to or less than the threshold.

[0233] According to embodiments of this disclosure, a periodicDelayReportTimer can be a timer with the same value as a periodicBSR-Timer configured in a BSR-Config. For example, a periodicDelayReportTimer can be configured to add a new field (e.g., periodicDelayReportTimer) to an existing BSR-Config, and based on the new field, allow the periodicDelayReportTimer to have a value different from the existing periodicBSR-Timer.

[0234] According to embodiments of this disclosure, refined long BSR and NBT long BSR can refer to the same BSR MAC CE format.

[0235] According to embodiments of this disclosure, refined long BSRs and NBT short BSRs can refer to the same BSR MAC CE format.

[0236] According to embodiments of this disclosure, the refined long BSR may include both NBT short BSR and NBT long BSR.

[0237] According to embodiments of this disclosure, in the process of selecting the format for the corresponding BSR when the MAC layer device of the terminal sends the BSR MAC CE by including the BSR MAC CE in a specific MACPDU, the following embodiments may be combined with the time point of determining whether the data exists in the buffer of a specific LCG and / or the time point of determining the buffer size of a specific LCG.

[0238] -Time 1: This can refer to the state before the logical channel priority sorting process is performed for the corresponding MAC PDU when constructing a MAC PDU including the BSR (i.e., the state where the amount of data to be sent for each logical channel is not determined). Determining the LCG state at the appropriate time point can reduce the implementation complexity of the terminal.

[0239] -Time 2: This can refer to a state where, when a MAC PDU including a BSR has been constructed, the logical channel prioritization process for the MAC PDU has been completed (the amount of data to be sent for each logical channel has been determined). The buffer size of each LCG reported in the BSR can refer to the amount of data that remains in the buffer of each LCG after the corresponding MAC PDU is sent, so the MAC layer device can select the most appropriate BSR format for the BSR report.

[0240] - Time 3: This can refer to the point in time when the BSR MAC CE is configured when the BSR is being built. For example, the time point could be Time 1, Time 2, or some other time point, depending on the terminal implementation. Therefore, this can indicate that the appropriate time point is determined by the terminal implementation. For example, in the case of a populated BSR, this time point could refer to the point in time when the populated BSR is generated.

[0241] According to embodiments of this disclosure, the NBT of this disclosure may refer to Tables 6.1.3.1-3 of the TS 38.321 standard. In the example, this table may be a table defining refined buffer size levels (in bytes) of an 8-bit buffer size field.

[0242] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate for regular and periodic BSRs as follows.

[0243] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0244] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0245] 1> Otherwise:

[0246] 2> If more than one LCG has data available for transmission at time 1:

[0247] 3> Report the long BSR of all LCGs with data available for transmission.

[0248] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0249] 3> Report to the Chief Reporter (BSR);

[0250] 2> Otherwise:

[0251] 3> Report a short BSR.

[0252] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0253] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0254] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0255] 1> Otherwise:

[0256] 2> If more than one LCG has data available for transmission at time 1:

[0257] 3> Report the long BSR of all LCGs with data available for transmission.

[0258] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0259] 3> Report to the Chief Reporter (BSR);

[0260] 2> Otherwise:

[0261] 3> Report a short BSR.

[0262] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0263] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0264] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0265] 1> Otherwise:

[0266] 2> If more than one LCG has data available for transmission at time 1:

[0267] 3> Report the long BSR of all LCGs with data available for transmission.

[0268] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0269] 3> Report to the Chief Reporter (BSR);

[0270] 2> Otherwise:

[0271] 3> Report a short BSR.

[0272] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0273] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0274] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0275] 1> Otherwise:

[0276] 2> If more than one LCG has data available for transmission at time 2:

[0277] 3> Report the long BSR of all LCGs with data available for transmission.

[0278] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0279] 3> Report to the Chief Reporter (BSR);

[0280] 2> Otherwise:

[0281] 3> Report a short BSR.

[0282] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0283] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0284] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0285] 1> Otherwise:

[0286] 2> If more than one LCG has data available for transmission at time 2:

[0287] 3> Report the long BSR of all LCGs with data available for transmission.

[0288] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0289] 3> Report to the Chief Reporter (BSR);

[0290] 2> Otherwise:

[0291] 3> Report a short BSR.

[0292] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0293] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0294] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0295] 1> Otherwise:

[0296] 2> If more than one LCG has data available for transmission at time 2;

[0297] 3> Report the long BSR of all LCGs with data available for transmission.

[0298] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0299] 3> Report to the Chief Reporter (BSR);

[0300] 2> Otherwise:

[0301] 3> Report a short BSR.

[0302] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0303] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0304] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0305] 1> Otherwise:

[0306] 2> If more than one LCG has data available for transmission at time 3:

[0307] 3> Report the long BSR of all LCGs with data available for transmission.

[0308] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0309] 3> Report to the Chief Reporter (BSR);

[0310] 2> Otherwise:

[0311] 3> Report a short BSR.

[0312] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0313] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0314] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0315] 1> Otherwise:

[0316] 2> If more than one LCG has data available for transmission at time 3:

[0317] 3> Report the long BSR of all LCGs with data available for transmission.

[0318] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0319] 3> Report to the Chief Reporter (BSR);

[0320] 2> Otherwise:

[0321] 3> Report a short BSR.

[0322] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0323] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 1 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0324] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0325] 1> Otherwise:

[0326] 2> If more than one LCG has data available for transmission at time 3:

[0327] 3> Report the long BSR of all LCGs with data available for transmission.

[0328] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0329] 3> Report to the Chief Reporter (BSR);

[0330] 2> Otherwise:

[0331] 3> Report a short BSR.

[0332] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0333] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0334] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0335] 1> Otherwise:

[0336] 2> If more than one LCG has data available for transmission at time 1:

[0337] 3> Report the long BSR of all LCGs with data available for transmission.

[0338] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0339] 3> Report to the Chief Reporter (BSR);

[0340] 2> Otherwise:

[0341] 3> Report a short BSR.

[0342] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0343] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0344] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0345] 1> Otherwise:

[0346] 2> If more than one LCG has data available for transmission at time 1:

[0347] 3> Report the long BSR of all LCGs with data available for transmission.

[0348] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0349] 3> Report to the Chief Reporter (BSR);

[0350] 2> Otherwise:

[0351] 3> Report a short BSR.

[0352] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0353] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0354] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0355] 1> Otherwise:

[0356] 2> If more than one LCG has data available for transmission at time 1:

[0357] 3> Report the long BSR of all LCGs with data available for transmission.

[0358] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0359] 3> Report to the Chief Reporter (BSR);

[0360] 2> Otherwise:

[0361] 3> Report a short BSR.

[0362] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0363] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0364] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0365] 1> Otherwise:

[0366] 2> If more than one LCG has data available for transmission at time 2:

[0367] 3> Report the long BSR of all LCGs with data available for transmission.

[0368] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0369] 3> Report to the Chief Reporter (BSR);

[0370] 2> Otherwise:

[0371] 3> Report a short BSR.

[0372] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0373] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0374] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0375] 1> Otherwise:

[0376] 2> If more than one LCG has data available for transmission at time 2;

[0377] 3> Report the long BSR of all LCGs with data available for transmission.

[0378] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0379] 3> Report to the Chief Reporter (BSR);

[0380] 2> Otherwise:

[0381] 3> Report a short BSR.

[0382] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0383] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0384] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0385] 1> Otherwise:

[0386] 2> If more than one LCG has data available for transmission at time 2:

[0387] 3> Report the long BSR of all LCGs with data available for transmission.

[0388] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0389] 3> Report to the Chief Reporter (BSR);

[0390] 2> Otherwise:

[0391] 3> Report a short BSR.

[0392] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0393] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0394] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0395] 1> Otherwise:

[0396] 2> If more than one LCG has data available for transmission at time 3:

[0397] 3> Report the long BSR of all LCGs with data available for transmission.

[0398] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0399] 3> Report to the Chief Reporter (BSR);

[0400] 2> Otherwise:

[0401] 3> Report a short BSR.

[0402] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0403] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0404] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0405] 1> Otherwise:

[0406] 2> If more than one LCG has data available for transmission at time 3:

[0407] 3> Report the long BSR of all LCGs with data available for transmission.

[0408] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0409] 3> Report to the Chief Reporter (BSR);

[0410] 2> Otherwise:

[0411] 3> Report a short BSR.

[0412] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0413] 1> If, for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 2 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0414] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0415] 1> Otherwise:

[0416] 2> If more than one LCG has data available for transmission at time 3:

[0417] 3> Report the long BSR of all LCGs with data available for transmission.

[0418] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0419] 3> Report to the Chief Reporter (BSR);

[0420] 2> Otherwise:

[0421] 3> Report a short BSR.

[0422] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0423] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0424] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0425] 1> Otherwise:

[0426] 2> If more than one LCG has data available for transmission at time 1:

[0427] 3> Report the long BSR of all LCGs with data available for transmission.

[0428] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0429] 3> Report to the Chief Reporter (BSR);

[0430] 2> Otherwise:

[0431] 3> Report a short BSR.

[0432] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0433] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0434] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0435] 1> Otherwise:

[0436] 2> If more than one LCG has data available for transmission at time 1:

[0437] 3> Report the long BSR of all LCGs with data available for transmission.

[0438] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0439] 3> Report to the Chief Reporter (BSR);

[0440] 2> Otherwise:

[0441] 3> Report a short BSR.

[0442] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0443] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0444] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0445] 1> Otherwise:

[0446] 2> If more than one LCG has data available for transmission at time 1:

[0447] 3> Report the long BSR of all LCGs with data available for transmission.

[0448] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0449] 3> Report to the Chief Reporter (BSR);

[0450] 2> Otherwise:

[0451] 3> Report a short BSR.

[0452] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0453] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0454] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0455] 1> Otherwise:

[0456] 2> If more than one LCG has data available for transmission at time 2:

[0457] 3> Report the long BSR of all LCGs with data available for transmission.

[0458] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0459] 3> Report to the Chief Reporter (BSR);

[0460] 2> Otherwise:

[0461] 3> Report a short BSR.

[0462] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0463] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0464] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0465] 1> Otherwise:

[0466] 2> If more than one LCG has data available for transmission at time 2:

[0467] 3> Report the long BSR of all LCGs with data available for transmission.

[0468] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0469] 3> Report to the Chief Reporter (BSR);

[0470] 2> Otherwise:

[0471] 3> Report a short BSR.

[0472] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0473] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0474] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0475] 1> Otherwise:

[0476] 2> If more than one LCG has data available for transmission at time 2:

[0477] 3> Report the long BSR of all LCGs with data available for transmission.

[0478] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0479] 3> Report to the Chief Reporter (BSR);

[0480] 2> Otherwise:

[0481] 3> Report a short BSR.

[0482] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0483] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0484] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0485] 1> Otherwise:

[0486] 2> If more than one LCG has data available for transmission at time 3:

[0487] 3> Report the long BSR of all LCGs with data available for transmission.

[0488] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 1 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0489] 3> Report to the Chief Reporter (BSR);

[0490] 2> Otherwise:

[0491] 3> Report a short BSR.

[0492] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0493] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0494] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0495] 1> Otherwise:

[0496] 2> If more than one LCG has data available for transmission at time 3:

[0497] 3> Report the long BSR of all LCGs with data available for transmission.

[0498] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 2 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0499] 3> Report to the Chief Reporter (BSR);

[0500] 2> Otherwise:

[0501] 3> Report a short BSR.

[0502] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0503] 1> If for at least one LCG configured with additionalBSR-TableAllowed (or additionalBS-TableAllowed), the amount of UL data available for transmission at time 3 is within the buffer size specified in Table 6.1.3.1-3 of TS 38.321:

[0504] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission;

[0505] 1> Otherwise:

[0506] 2> If more than one LCG has data available for transmission at time 3:

[0507] 3> Report the long BSR of all LCGs with data available for transmission.

[0508] 2> Otherwise, if an LCG has available data and is configured with additionalBS-TableAllowed, and the amount of UL data available for transmission at time 3 is greater than the maximum buffer size specified in Table 6.1.3.1-3:

[0509] 3> Report to the Chief Reporter (BSR);

[0510] 2> Otherwise:

[0511] 3> Report a short BSR.

[0512] According to embodiments of this disclosure, a MAC layer device that is not configured with logicalChannelGroupIAB-Ext by a higher layer can operate with respect to regular and periodic BSRs as follows.

[0513] For filling BSRs, MAC entities in the upper layer that are not configured with logicalChannelGroupIAB-Ext should:

[0514] 1> If the number of padding bits is equal to or greater than the size of the short BSR plus its subheading, but less than the size of the long BSR plus its subheading:

[0515] 2> If more than one LCG has data available for transmission when constructing a BSR:

[0516] 3> If the number of padding bits equals the size of the short BSR plus its subheading:

[0517] 4> Report a short-truncated BSR for the LCG with the highest priority logical channel, which has data available for transmission.

[0518] 3> Otherwise:

[0519] 4> The long truncated BSR of the LCG is reported, wherein the logical channels with data available for transmission follow the descending order of the highest priority logical channel (with or without data available for transmission) in each of these LCGs, and in the case of equal priority, in ascending order of LCGID.

[0520] 2> Otherwise:

[0521] 3> Report a short BSR.

[0522] 1> Otherwise, if for at least one LCG configured with additionalBS-TableAllowed, the amount of UL data available for transmission when constructing a BSR is within the buffer size specified in Table 6.1.3.1-3, and the number of padding bits is equal to or greater than the size of the refined long BSR plus its subheadings:

[0523] 2> The report contains a detailed long BSR of all LCGs that can be used for transmission.

[0524] 1> Otherwise, if the number of padding bits is equal to or greater than the length of the BSR plus the size of its subheading:

[0525] 2> Report the long BSR of all LCGs with data available for transmission.

[0526] Figure 8 The structure of a terminal according to an embodiment of this disclosure is shown.

[0527] like Figure 8As shown, the terminal disclosed herein may include a transceiver 810, a memory 820, and a controller (or at least one processor) 830. The controller 830, transceiver 810, and memory 820 of the terminal can operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the foregoing examples. For example, the terminal may include more or fewer components than those described above. Furthermore, the controller 830, transceiver 810, and memory 820 may be implemented as a single chip.

[0528] Transceiver 810 (which is a term collectively referred to as a receiver of a terminal and a transmitter of a terminal) can transmit signals to a base station, network entity, or another terminal and receive signals from a base station, network entity, or another terminal. Signals transmitted to and received from a base station may include control information and data. For this purpose, transceiver 810 may include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of the transmitted signals, and an RF receiver that amplifies and down-converts the frequency of the received signals with low noise. However, this is only one embodiment of transceiver 810, and the components of transceiver 810 are not limited to RF transmitters and RF receivers.

[0529] Furthermore, transceiver 810 may include a wired or wireless transceiver and may include various configurations for transmitting and receiving signals. Additionally, transceiver 810 can receive signals via a wireless channel and output the received signals to controller 830, and can transmit signals output from controller 830 via a wireless channel. Furthermore, transceiver 810 can receive communication signals and output communication signals to controller 830, and can transmit signals output from controller 830 to a base station or network entity via a wired or wireless network.

[0530] The memory 820 can store programs and data required for the operation of the terminal. Furthermore, the memory 820 can store control information or data included in signals acquired by the terminal. The memory 820 may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0531] Controller 830 can control a series of processes to enable the terminal to operate according to the embodiments of the present disclosure described above. Controller 830 may include at least one or more processors. For example, controller 830 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls higher layers (such as applications).

[0532] Figure 9 The structure of a base station according to an embodiment of this disclosure is shown.

[0533] like Figure 9As shown, the base station of this disclosure may include a transceiver 910, a memory 920, and a controller (or at least one processor) 930. The controller 930, transceiver 910, and memory 920 of the base station can operate according to the communication method of the base station described above. However, the components of the base station are not limited to the foregoing examples. For example, the base station may include more or fewer components than those described above. Furthermore, the controller 930, transceiver 910, and memory 920 may be implemented as a single chip.

[0534] Transceiver 910 (a term collectively referred to as a base station receiver and a base station transmitter) can transmit signals to and / or receive signals from terminals and / or network entities. The transmitted / received signals may include control information and data. For this purpose, transceiver 910 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of the received signal. However, this is only one embodiment of transceiver 910, and the components of transceiver 910 are not limited to RF transmitters and RF receivers. Transceiver 910 may include wired or wireless transceivers and may include various components for transmitting and receiving signals.

[0535] Furthermore, transceiver 910 can receive signals via a communication channel (e.g., a wireless channel) and output the received signals to controller 930, and transmit signals output from controller 930 via a wireless channel. Additionally, transceiver 910 can receive communication signals and output communication signals to processor, and can transmit signals output from processor to a terminal or network entity via a wired or wireless network.

[0536] The memory 920 can store programs and data required for the operation of the base station. Furthermore, the memory 920 can store control information or data included in signals acquired by the base station. The memory 920 may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0537] Controller 930 can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. Controller 930 may include at least one or more processors. The methods disclosed in the claims and / or the methods described in the embodiments of the present disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0538] The methods disclosed in the claims and / or the methods of the embodiments described in this disclosure may be implemented by hardware, software, or a combination of hardware and software.

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

[0540] The program (software module or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc-ROM (CD-ROM), digital universal disc (DVD), or other types of optical storage devices or magnetic tape cassettes. Alternatively, any combination of some or all of these can form the memory in which the program is stored. Furthermore, multiple such memories can be included in an electronic device.

[0541] Additionally, the program can be stored in an attachable storage device that can access the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide LAN (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Furthermore, a separate storage device on a communication network can access portable electronic devices.

[0542] In the detailed embodiments described above, elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form is suitably chosen for the presented situation, and this disclosure is not limited to elements expressed in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

[0543] Although specific embodiments have been described in detail in this disclosure, it will be apparent that various modifications and changes can be made thereto without departing from the scope of this disclosure. For example, parts or all of the embodiments may be combined with parts or all of one or more other embodiments, and naturally, implementations of such combinations also correspond to the embodiments presented in this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

[0544] Although specific embodiments have been described in detail in this disclosure, it will be apparent that various modifications and changes can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

[0545] Although this disclosure has been described with reference to various embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Identify logical channel groups (LCGs) configured with additional buffer size tables. and When an LCG with an additional buffer size table has data available for transmission, it sends a first long buffer status report (BSR) to the base station. Among them, the first long BSR corresponds to the additional buffer size table, and The amount of data available for transmission is within the buffer size specified in the additional buffer size table.

2. The method according to claim 1, further comprising: When constructing a Media Access Control (MAC) Protocol Data Unit (PDU), if more than one LCG has data available for transmission, a second long BSR is sent to the base station; and When an LCG has data available for transmission when constructing a MAC PDU, it sends a short BSR to the base station.

3. The method according to claim 2, wherein, The first long BSR is identified by a MAC subheader that includes an Extended Logical Channel Identifier (eLCID) corresponding to a specific value.

4. The method according to claim 1, wherein, The first long BSR includes a logical channel group field indicating the existence of a buffer size field for logical channel groups, and a buffer table field indicating which buffer size table is used to set the buffer size field for logical channel groups.

5. The method according to claim 1, wherein, The additional buffer size table is configured for LCG via Radio Resource Control (RRC) signaling; and The buffer size field of the first long BSR consists of 8 bits.

6. The method according to claim 2, wherein, The additional buffer size table differs from the traditional buffer size table used for the second long BSR. The buffer size intervals for specific buffer size levels used in the appended buffer size table are narrower than those for the corresponding buffer size levels used in the traditional buffer size table.

7. The method according to claim 1, wherein, The first long BSR includes the refined long BSR.

8. A terminal in a wireless communication system, the terminal comprising: transceiver; and The controller, coupled to the transceiver, is configured as follows: Identify logical channel groups (LCGs) configured with additional buffer size tables, and When an LCG with an additional buffer size table has data available for transmission, it sends a first long buffer status report (BSR) to the base station. Among them, the first long BSR corresponds to the additional buffer size table, and The amount of data available for transmission is within the buffer size specified in the additional buffer size table.

9. The terminal according to claim 8, wherein, The controller is also configured to: When constructing a Media Access Control (MAC) Protocol Data Unit (PDU), if more than one LCG has data available for transmission, a second long BSR is sent to the base station. When an LCG has data available for transmission when constructing a MAC PDU, it sends a short BSR to the base station.

10. The terminal according to claim 9, wherein, The first long BSR is identified by a MAC subheader that includes an Extended Logical Channel Identifier (eLCID) corresponding to a specific value.

11. The terminal according to claim 8, wherein, The first long BSR includes a logical channel group field indicating the existence of a buffer size field for logical channel groups, and a buffer table field indicating which buffer size table is used to set the buffer size field for logical channel groups.

12. The terminal according to claim 8, wherein, The additional buffer size table is configured for LCG via Radio Resource Control (RRC) signaling, and The buffer size field of the first long BSR consists of 8 bits.

13. The terminal according to claim 9, wherein, The additional buffer size table differs from the traditional buffer size table used for the second-longest BSR.

14. The terminal according to claim 13, wherein, The buffer size intervals for a specific buffer size level used in the appended buffer size table are narrower than the buffer size intervals for the corresponding buffer size level used in the traditional buffer size table.

15. The terminal according to claim 8, wherein, The first long BSR includes the refined long BSR.

Images