Method and device for determining logical channel priority in consideration of transmission delay time in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. An operation method of a UE in a wireless communication system according to an embodiment of the present disclosure may include the steps of: receiving, from a base station, an RRC message including at least one of configuration information for delay-aware scheduling and a threshold value associated with delay-aware LCP; transmitting a DSR MAC CE to the base station; receiving a DCI including an uplink grant from the base station; performing the delay-aware LCP on the basis of at least one of the configuration information and the threshold value; and transmitting uplink data to the base station by using the uplink grant on the basis of the delay-aware LCP, wherein the threshold value is configured in units of LCH.

Description

Method and device for determining logical channel priority considering transmission delay time in a wireless communication system

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system, and more particularly, to a method and device for determining a logical channel priority by considering the transmission delay time of an uplink packet during uplink data transmission.

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

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

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

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

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

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

[0008] The disclosed embodiment is intended to provide a device and method capable of effectively providing a delay-sensitive data transmission service in a wireless communication system.

[0009] According to one aspect of an embodiment of the present disclosure, a method of operating a user equipment (UE) includes the steps of: receiving, from a base station, a radio resource control (RRC) message including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware LCP (delay-aware logical channel prioritization); transmitting, to the base station, a delay status report (DSR) medium access control (MAC) control element (CE); receiving, from the base station, downlink control information (DCI) including an uplink grant; performing the delay-aware LCP based on at least one of the configuration information and the threshold; and transmitting uplink data to the base station using the uplink grant based on the delay-aware LCP; wherein the threshold may be set on a per-LCH (Logical channel) basis.

[0010] According to one aspect of an embodiment of the present disclosure, a method of operating a base station includes the steps of: transmitting, to a user equipment (UE), a radio resource control (RRC) message including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware LCP (delay-aware logical channel prioritization); receiving, from the UE, a delay status report (DSR) medium access control (MAC) control element (CE); transmitting, to the UE, downlink control information (DCI) including an uplink grant; and receiving, from the UE, uplink data transmitted using the uplink grant; wherein the uplink data is associated with the delay-aware LCP based on at least one of the configuration information and the threshold, and the threshold is set on a per-LCH (Logical channel) basis.

[0011] According to an aspect of one embodiment of the present disclosure, a UE (user equipment) comprises: a transceiver; and at least one control unit coupled to the transceiver, wherein the at least one control unit is configured to receive, from a base station, an RRC (radio resource control) message including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware LCP (delay-aware logical channel prioritization), transmit a DSR (delay status report) MAC (medium access control) CE (control element) to the base station, receive, from the base station, downlink control information (DCI) including an uplink grant, perform the delay-aware LCP based on at least one of the configuration information and the threshold, and transmit uplink data to the base station using the uplink grant based on the delay-aware LCP, wherein the threshold is set on a per-LCH (logical channel) basis.

[0012] According to an aspect of one embodiment of the present disclosure, a base station comprises: a transceiver; and at least one control unit coupled to the transceiver, wherein the at least one control unit is configured to transmit, to a user equipment (UE), a radio resource control (RRC) message including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware LCP (delay-aware logical channel prioritization), receive, from the UE, a delay status report (DSR) medium access control (MAC) control element (CE), transmit, to the UE, downlink control information (DCI) including an uplink grant, and receive, from the UE, uplink data transmitted using the uplink grant, wherein the uplink data is associated with the delay-aware LCP based on at least one of the configuration information and the threshold, and the threshold is set on a per-LCH (Logical channel) basis.

[0013] The technical problems to be achieved in various embodiments of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0014] The present disclosure provides a device and method capable of effectively providing a delay-sensitive data transmission service in a wireless communication system.

[0015] FIG. 1a is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0016] FIG. 1b is a diagram illustrating a wireless protocol structure in a long term evolution (LTE) and new radio (NR) system according to an embodiment of the present disclosure.

[0017] FIG. 1c is a diagram illustrating a configuration of an application data unit (ADU) unit PDU (protocol data unit) set according to one embodiment of the present disclosure.

[0018] FIG. 1d is a diagram illustrating a signaling procedure between a terminal and a base station for setting and operating a logical channel priority decision (hereinafter referred to as 'Delay-aware LCP') considering a transmission delay time in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0019] FIG. 1e is a diagram illustrating an example of a Logical Channel Prioritization (LCP) operation based on a logical channel priority according to one embodiment of the present disclosure.

[0020] FIG. 1f is a diagram illustrating an example of a delay-aware LCP operation that determines priorities by considering transmission delay time between logical channels having the same priority according to an embodiment of the present disclosure.

[0021] FIG. 1g is a diagram illustrating an example of a delay-aware LCP operation that first performs transmission delay-based resource allocation before logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0022] FIG. 1h is a diagram illustrating an example of a Delay-aware LCP operation that first performs DSR (Delay Status Report) setting and report-based resource allocation prior to logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0023] FIG. 1i is a diagram illustrating an example of a delay-aware LCP operation that first performs resource allocation for delay-critical data prior to logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0024] FIG. 1J is a diagram for explaining terminal operation for performing Delay-aware LCP operation according to one embodiment of the present disclosure.

[0025] FIG. 1k is a diagram illustrating base station operations for setting up delay-aware LCP operations according to one embodiment of the present disclosure.

[0026] FIG. 2 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0027] FIG. 3 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0028] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, in describing the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, such detailed description will be omitted. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents throughout this specification. Embodiments of the present invention will be described below with reference to the attached drawings.

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

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

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

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

[0033] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0034] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0035] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH can also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" can be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0036] Hereinafter, in the present disclosure, upper signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Upper signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0037] For the convenience of explanation below, this disclosure uses terms and names defined in the 3rd Generation Partnership Project NR (New Radio) or 3rd Generation Partnership Project Long Term Evolution (LTE) standards. However, this disclosure is not limited by the above terms and names, and can be equally applied to systems conforming to other standards. In this disclosure, gNB may be used interchangeably with eNB for the convenience of explanation. That is, a base station described as an eNB may represent a gNB. In addition, the term terminal may represent not only a mobile phone, an MTC device, an NB-IoT device, a sensor, but also other wireless communication devices.

[0038] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNodeB (gNB), an eNode B (eNB), a NodeB, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.

[0039] In particular, the present disclosure can be applied to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Furthermore, the term "terminal" may refer to not only mobile phones, NB-IoT devices, and sensors, but also other wireless communication devices.

[0040] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0041] As a representative example of a broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment; UE or MS; Mobile Station) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating the time-frequency resources to be transmitted for each user so that they do not overlap, that is, so as to achieve orthogonality.

[0042] As the future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0043] In some embodiments, eMBB may aim to provide data rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, a 5G communication system may need to provide an increased user-perceived data rate while simultaneously providing the peak data rate. To meet these requirements, a 5G communication system may require improvements in various transmission and reception technologies, including improved multi-antenna (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, a 5G communication system may utilize a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band, thereby meeting the data rates required by the 5G communication system.

[0044] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC may require support for large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, which may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC should be comprised of low-cost terminals, and since frequent battery replacement is unlikely, extremely long battery lifespans, such as 10 to 15 years, may be required.

[0045] Finally, URLLC is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service supporting URLLC may have to satisfy an air interface latency of less than 0.5 milliseconds and may also have a requirement for a packet error rate (PER) of 10-5 or less. Therefore, for services supporting URLLC, 5G systems may be required to provide a smaller Transmit Time Interval (TTI) than other services, while simultaneously allocating a wide range of resources in the frequency band to ensure the reliability of the communication link.

[0046] The three services considered in the aforementioned 5G communication system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted in a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters may be used between the services. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types applicable to this disclosure are not limited to the aforementioned examples.

[0047] Furthermore, while embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0048] FIG. 1a is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0049] Referring to FIG. 1a, as illustrated, a wireless access network of a wireless communication system (hereinafter, a next-generation mobile communication system (New Radio, NR or 5G)) may be composed of a next-generation base station (New Radio Node B, hereinafter, gNB) (1a-10) and an AMF (1a-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter, NR UE or terminal) (1a-15) may access an external network through the gNB (1a-10) and the AMF (1a-05).

[0050] In Fig. 1a, the gNB (1a-10) may correspond to an eNB (Evolved Node B) (1a-30) of an existing LTE system. The gNB (1a-10) is connected to an NR UE (1a-15) via a wireless channel and may provide a service superior to that of an existing Node B (1a-20).

[0051] According to one embodiment of the present disclosure, in a next-generation mobile communication system, all user traffic is serviced through a shared channel, and therefore, a device is required to collect status information such as buffer status, available transmission power status, and channel status of UEs and perform scheduling, and this can be handled by a gNB (1a-10). A single gNB can typically control multiple cells.

[0052] According to one embodiment of the present disclosure, in order to implement ultra-high-speed data transmission compared to existing LTE, it may have a bandwidth greater than the existing maximum bandwidth, and additionally beamforming technology may be used with orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as a wireless access technology.

[0053] In addition, according to one embodiment of the present disclosure, an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal may be applied. AMF (1a-05) may perform functions such as mobility support, bearer setup, and QoS setup. AMF is a device that is responsible for various control functions as well as mobility management functions for the terminal and may be connected to multiple base stations. In addition, the next-generation mobile communication system may also be interoperable with the existing LTE system, and AMF (1a-05) is connected to MME (1a-25) through a network interface. MME (1a-25) may be connected to eNB (1a-30), which is an existing base station. A terminal that supports LTE-NR Dual Connectivity may transmit and receive data while maintaining a connection to not only gNB (1a-10) but also eNB (1a-30) (1a-35).

[0054] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE and NR system according to an embodiment of the present disclosure.

[0055] Referring to FIG. 1b, the wireless protocol of the NR system may be composed of SDAP (service data adaptation protocol) (1b-05)(1b-10), PDCP (packet data convergence protocol) (1b-15)(1b-20), radio link control (RLC) (1b-25)(1b-30), and MAC (medium access control) (1b-35)(1b-40) in the terminal and gNB, respectively. SDAP (1b-05)(1b-10) may perform an operation to map each QoS flow to a specific DRB (data radio bearer), and SDAP settings corresponding to each DRB may be provided from a higher layer (e.g., RRC layer).

[0056] According to one embodiment of the present disclosure, PDCP (1b-15) (1b-20) may be responsible for operations such as IP header compression and / or restoration, and may additionally perform a re-ordering operation on data packets to provide an in-order delivery service to a higher layer. In addition, RLC (1b-25) (1b-30) may reconfigure PDCP PDUs into an appropriate size. MAC (1b-35) (1b-40) may be connected to a plurality of RLC layer devices configured in one terminal, and may perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The physical (PHY) layer (1b-45)(1b-50) can perform channel coding and modulation of upper layer data, and can perform operations of creating OFDM (orthogonal frequency-division multiplexing) symbols and transmitting them through a wireless channel, or demodulating OFDM symbols received through a wireless channel, decoding the channel, and transmitting them to a higher layer.

[0057] In addition, according to one embodiment of the present disclosure, the PHY layer (1b-45)(1b-50) can use HARQ (hybrid automatic repeat request) for additional error correction, and the receiver can transmit with 1 bit whether or not the packet transmitted by the transmitter has been received. Information on whether or not the packet received by the receiver from the transmitter has been received can be referred to as HARQ ACK / NACK information. In the case of an LTE system, downlink HARQ ACK / NACK information for uplink data transmission can be transmitted through a physical hybrid-arq indicator channel (PHICH). In the case of an NR system, downlink HARQ ACK / NACK information for uplink data transmission can be transmitted through a physical dedicated control channel (PDCCH), which is a channel through which downlink and / or uplink resource allocation, etc. are transmitted, and the base station can determine whether retransmission is necessary or whether a new transmission can be performed through scheduling information of the terminal.

[0058] Unlike LTE, the reason why the base station in the NR system determines whether retransmission is necessary or a new transmission can be performed based on the scheduling information of the terminal may be because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted via the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The PUCCH can generally be transmitted in the uplink of the PCell (primary cell), which will be described later. However, if the terminal supports it, HARQ ACK / NACK information for the SCell (secondary cell), which will be described later, can be transmitted, and in this case, the SCell can be referred to as a PUCCH SCell.

[0059] Although not shown in this drawing, an RRC (radio resource control) layer may exist above the PDCP layer of each terminal and base station, and the RRC layer can exchange connection and measurement-related setting control messages for radio resource control.

[0060] Meanwhile, the PHY layer (1b-45)(1b-50) may be composed of one or more frequencies and / or carriers, and the technology of using multiple frequencies simultaneously may be referred to as carrier aggregation (CA). CA technology refers to a technology that additionally uses a primary carrier and one or more secondary carriers instead of using only one carrier for communication between a terminal and a base station (e.g., eNB or gNB), and by using CA technology, the transmission capacity can be increased by the number of secondary carriers. Meanwhile, in LTE and NR systems, a cell within a base station that uses a primary carrier may be referred to as a primary cell or PCell, and a cell within a base station that uses a secondary carrier may be referred to as a secondary cell or SCell.

[0061] FIG. 1c is a diagram illustrating an application data unit (ADU) unit PDU set configuration according to one embodiment of the present disclosure.

[0062] Referring to FIG. 1c, various types of traffic can be classified into ADUs, which are units of information that can be distinguished at the application level. According to one embodiment, an ADU may be a single photo or picture, a single frame of video data, or a single unit of audio data. An ADU may be classified into PDU sets (1c-10), and a PDU set (1c-10) may be divided into at least one PDU (1c-01, 1c-02, 1c-03, 1c-04, 1c-05, 1c-06) according to its size and transmitted.

[0063] For example, when using the MPEG (moving picture experts group) standard video compression technology in video traffic, a PDU set can be composed of one of 1) a combination of multiple PDUs corresponding to one I (intra)-frame (1c-30), 2) a combination of multiple PDUs corresponding to one B (bidirectional)-frame (1c-40), and 3) a combination of multiple PDUs corresponding to one P (predicted)-frame (1c-50).

[0064] According to one embodiment of the present disclosure, an I-frame (1c-20) can represent a single complete photo or picture (1c-21) as an independent frame regardless of the presence or absence of other frames. The P-frame and B-frame (1c-22) are frames that indicate change information of the previous I-frame (1c-20). If the I-frame (1c-20) is not received normally, it may be difficult to normally express the photo or picture (1c-23) that was intended to be expressed by the P-frame and B-frame (1c-22). In addition, in the case of the B-frame, since it is stored as data that infers the movement between the two frames by referencing both frames between the I-frame and the P-frame, not only the I-frame in front but also the P-frame behind must be received normally in order for the photo or picture that was intended to be expressed by the B-frame to be normally expressed.

[0065] For ease of explanation, one embodiment of the present disclosure may explain the configuration of a PDU set by exemplifying a case in which MPEG standard video compression technology is used in video traffic. However, the contents of the present disclosure are not limited to the configuration of a PDU set in video traffic, and can be applied to all PDU set configurations composed of general ADU units.

[0066] According to one embodiment of the present disclosure, an XR traffic flow for a specific XR (extended reality) service may be composed of a combination of data (e.g., PDUs, PDU sets, etc.) having different quality of service (QoS) requirements. For example, when video traffic coded in MPEG is transmitted for a specific XR service, several types of PDU sets having different QoS requirements (e.g., delay, reliability, etc.) corresponding to I-frame / B-frame / P-frame may constitute a single XR traffic flow.

[0067] According to one embodiment of the present disclosure, in order to service an XR traffic flow composed of data having various QoS requirements, a network may map the XR traffic flow to one or more QoS flows. As described above, when one or more QoS flows are used to service a specific XR traffic flow, data constituting the same XR traffic flow may be transmitted through different QoS flows according to the QoS requirements. At this time, the different QoS flows may be mapped to different DRBs or may be mapped to the same DRB. In addition, PDU sets transmitted through the same QoS flow may have different priorities. For example, in the case of the video traffic, a PDU set corresponding to an I-frame may have a relatively higher priority than a PDU set corresponding to a B-frame or a P-frame. The importance of each PDU set can be expressed as a number from 0 to 8, or {True, false} or {0, 1}, etc., and in the case of downlink data, the UPF can include the importance information in the GTP-U header, and the base station can consider the importance when transmitting the PDU set in the downlink. In addition, in the case of the uplink, the importance information can be transmitted from the application layer of the terminal to the lower layer (e.g., SDAP, PDCP, RLC, MAC) through the terminal internal interface, or the importance information can be included in the SDAP / PDCP / RLC header, etc. For example, the MAC layer can check the importance of the data included in the RLC PDU through the RLC header information of the RLC PDU, and at this time, the importance of the data can be ultimately determined by the importance of the PDU set that the data constitutes.

[0068] The embodiments of the present disclosure below were written under the assumption that a lower importance value of a PDU set indicates a higher importance, but the same method can also be applied to a case where a higher importance value of a PDU set indicates a higher importance. However, in this case, only the method of comparing the importance values ​​of each PDU set to determine relative importance is changed.

[0069] FIG. 1d is a diagram illustrating a signaling procedure between a terminal and a base station for setting and operating a logical channel priority decision (hereinafter referred to as 'Delay-aware LCP') considering a transmission delay time in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0070] Referring to FIG. 1d, a terminal (1d-01) can report UE capability information related to Delay-aware LCP (or Delay-aware scheduling considering transmission delay time) to a base station (1d-03). The base station can set a Delay-aware LCP (or Delay-aware scheduling) operation for the terminal based on the terminal capability information reported by the terminal. Additionally, the base station can {activate and deactivate} or {deactivate} the Delay-aware LCP (or Delay-aware scheduling) according to a network congestion situation and a terminal service situation. When the Delay-aware LCP (or Delay-aware scheduling) operation is set (or activated), the terminal performs the Delay-aware LCP (or Delay-aware scheduling) operation when receiving an uplink transmission resource (UL grant) from the base station, and can perform uplink transmission resource allocation considering the transmission delay time. The specific signaling operation between the terminal (1d-01) and the base station (1d-03) for the above operation is as follows.

[0071] In step 1d-10, the terminal (1d-01) and the base station (1d-03) can exchange at least one of the terminal capability information described below in relation to delay time-based scheduling.

[0072] * delayStatusReport: New terminal capability information may be defined to indicate whether the terminal supports DSR (Delay Status Report). The terminal capability information may be reported per UE and may not be a required support function. In addition, the terminal capability information may not distinguish between FDD and TDD or may not be distinguished according to frequency range (e.g., FR1 and FR2). For reference, DSR may include the minimum value of the remaining time (i.e., the time remaining until the PDCP discardTimer expires) of all packets (PDCP SDUs) waiting for transmission per LCG unit and / or the total amount of delay-critical UL data. Alternatively, DSR may optionally include the minimum value of the remaining time and the total amount of delay-critical UL data. In this case, delay-critical UL data may mean PDCP SDUs in which the remaining time becomes smaller than a network-configured threshold (remainingTimeThreshold). The DSR may be used by the terminal to provide the base station with information on the transmission delay time of uplink transmission data.

[0073] * delayAwareScheduling (or delayAwareLCP): New terminal capability information may be defined to indicate whether the terminal supports delay-aware scheduling (or delay-aware LCP). The terminal capability information may be reported per UE and may not be a mandatory support function. In addition, the terminal capability information may not distinguish between FDD and TDD or distinguish between frequency ranges (e.g., FR1 and FR2). A terminal supporting delay-aware scheduling (or delay-aware LCP) may have an additional constraint that it must support the delayStatusReport function. In addition, a terminal supporting delay-aware scheduling (or delay-aware LCP) must have an additional constraint that it must support the ability to recognize PDU sets and PSI (PDU set Importance) for UL XR traffic. As described in steps 1d-20 below, to support delay-aware scheduling (or delay-aware LCP), a new DCI format, a new RNTI, or a new indicator included in an existing DCI format may be introduced. In this case, whether the terminal supports the new DCI format, the new RNTI, or the new indicator may be indicated together through the delayAwareScheduling (or delayAwareLCP). Alternatively, a separate terminal capability information indicator (e.g., delayAwareSchedulingDCI-FormatX-Y) may be introduced to indicate whether the terminal supports the new DCI format, the new RNTI, or the new indicator.

[0074] In step 1d-12, the base station (1d-03) may transmit an RRCReconfiguration message including DSR configuration and delay-aware scheduling (or delay-aware LCP) configuration information to the terminal (1d-01). At least one of the following information may be included in the RRCReconfiguration message.

[0075] * LCG-DSR-Config: LCG-DSR-Config may refer to configuration information including the ID (Logical Channel Group ID) of the LCG for which DSR is set and the remainingTimeThreshold value to be used in the LCG. The terminal may trigger DSR when the minimum value of the remaining time (i.e., remaining time) of all packets (SDUs) waiting for transmission in the LCG for which DSR is set becomes smaller than the remainingTimeThreshold value set for the LCG.

[0076] To support DSR configuration for multiple LCGs, an AddModList containing multiple LCG-DSR-Configs and / or a ReleaseList containing multiple LCG-IDs may be set.

[0077] * delayAwareLCP (or delayAwareScheduling): An indicator may be introduced to set a delay-aware LCP operation, which may be defined in the same manner as at least one of the embodiments described in FIGS. 1f, 1g, 1h, and 1i below. The indicator may be defined as 1 bit, and the base station may set the delay-aware LCP operation through the indicator. The indicator may be set per MAC Cell group and may be included in MAC-CellGroupConfig.

[0078] * Remaining time threshold for delay-critical UL data: When the delay-aware LCP operation is defined in a manner similar to one of the embodiments described in FIGS. 1f, 1g, 1h, and 1i below, the delay-critical data concept may be used as in DSR. In this case, delay-critical data may mean a PDCP SDU whose remaining time is less than a network-configured threshold (remaining time threshold). Here, the remaining time may mean the time remaining until the expiration of the PDCP discardTimer corresponding to the PDCP SDU. The remaining time threshold used to determine delay-critical data in the delay-aware LCP operation may be set using at least one of the following methods.

[0079] - Method 1: The remaining time threshold can be set for each MAC cell group. In other words, the remaining time threshold can be included in MAC-CellGroupConfig. In this case, the remaining time threshold setting itself can include the delay-aware LCP operation setting, and the delayAwareLCP (or delayAwareScheduling) may not be set separately.

[0080] - Method 2: The remaining time threshold can be set for each logical channel. In other words, the remaining time threshold can be included in LogicalChannelConfig.

[0081] - Method 3: The remaining time threshold can be set for each logical channel group. In this case, remainingTimeThreshold-r18, which was included in the existing DSR setting, can be reused when determining delay-critical data in delay-aware LCP operation. Alternatively, a remaining time threshold can be set separately from the DSR setting to be used when determining delay-critical data in delay-aware LCP operation.

[0082] In step 1d-14, the base station (1d-03) can instruct the terminal (1d-01) to activate the delay-aware scheduling (i.e., delay-aware LCP) operation. At least one of a DCI, a MAC CE, and an RRC message can be used to instruct the terminal (1d-01) to activate the delay-aware scheduling operation. The network can determine whether to activate the delay-aware scheduling (i.e., delay-aware LCP) depending on the network situation and the terminal service situation. If the activation / deactivation operation of the delay-aware scheduling (i.e., delay-aware LCP) operation is not required, the above step 1d-14 and the following step 1d-26 can be omitted.

[0083] In step 1d-16, the terminal (1d-01) can transmit a BSR to the base station (1d-03) when the BSR is triggered according to certain conditions.

[0084] In step 1d-18, the terminal (1d-01) can transmit a DSR to the base station (1d-03) when the DSR is triggered according to certain conditions. More specifically, the terminal can trigger the DSR when the minimum value of the remaining time (in other words, the time remaining until the expiration of the PDCP discardTimer) of all packets (PDCP SDUs) waiting for transmission in the LCG for which the DSR transmission is set by LCG-DSR-Config in step 1d-12 becomes smaller than the remainingTimeThreshold value. For reference, the DSR can include the minimum value of the remaining time of all packets (PDCP SDUs) waiting for transmission in units of LCGs and the total amount of delay-critical UL data.

[0085] In step 1d-20, the base station (1d-03) may transmit DCI for allocating uplink transmission resources (UL grant) to the terminal (1d-01) based on the information in the BSR and DSR transmitted by the terminal (1d-01) in steps 1d-16 and 1d-18. At this time, a new DCI format, a new RNTI, or a new indicator included in an existing DCI format may be defined and used to indicate that the UL grant is for delay-critical data, delay-aware LCP, or delay-aware scheduling. As in the embodiments of FIGS. 1g, 1h, and 1i, when the UL grant is indicated as being for delay-critical data, delay-aware LCP, or delay-aware scheduling, the terminal may additionally perform an operation for delay-aware LCP.

[0086] In step 1d-22, the terminal (1d-01) may perform a Logical Channel Prioritization (LCP) operation to determine uplink data to be transmitted through the UL grant received in step 1d-20. Additionally, the terminal may perform a delay-aware LCP operation in the same manner as one of the embodiments described in FIGS. 1f, 1g, 1h, and 1i based on the delay-aware LCP / Scheduling configuration in step 1d-12, the delay-aware LCP / Scheduling activation in step 1d-14, and the DCI indication in step 1d-20.

[0087] In step 1d-24, the terminal (1d-01) can transmit uplink data, the transmission of which has been determined according to the LCP operation in step 1d-22, to the base station (1d-03) using the UL grant resources received in step 1d-20.

[0088] In step 1d-26, the base station (1d-03) can instruct the terminal (1d-01) to deactivate the delay-aware scheduling (i.e., delay-aware LCP) operation. At least one of a DCI, a MAC CE, and an RRC message can be used to instruct the terminal (1d-01) to deactivate the delay-aware scheduling operation. The network can determine whether to deactivate the delay-aware scheduling (i.e., delay-aware LCP) depending on the network situation and the terminal service situation. If the activation / deactivation operation of the delay-aware scheduling (i.e., delay-aware LCP) operation is not required, steps 1d-14 and 1d-26 can be omitted.

[0089] FIG. 1e is a diagram illustrating an example of a Logical Channel Prioritization (LCP) operation based on logical channel priority according to one embodiment of the present disclosure.

[0090] Referring to FIG. 1e, when a terminal is allocated a UL grant from a base station, the terminal can calculate the size of uplink data (Transmit Block size or MAC PDU size) (1e-02) that can be transmitted using the UL grant. Thereafter, the MAC layer of the terminal can perform an LCP (Logical Channel Prioritization) operation to determine the order in which UL data (1e-03, 1e-04, 1e-05) waiting for transmission in each LCH are included in the MAC PDU of the calculated size (in other words, to determine the order in which uplink transmission resources are allocated to each logical channel (LCH)).

[0091] More specifically, the MAC layer can perform LCP considering the priority of the LCH. The LCP operation of the MAC considering the priority of the logical channel can be specifically defined as 1e-01.

[0092] The operation described in 1e-01 may be performed after the terminal receives an UL grant for uplink data transmission from the base station. In addition, before the operation described in 1e-01 is performed, LCHs that can transmit data using the received UL grant may be selected and screened in advance according to the configuration information of each LCH (e.g., allowedSCS-List, maxPUSCH-Duration, configuredGrantType1Allowed, allowedServingCells, allowedCG-List, allowedPHY-PriorityIndex, allowedHARQ-mode, etc.). Thereafter, resource allocation for the LCH may be performed according to the following three steps as described in 1e-01.

[0093] 1. For LCHs having a Bj value greater than 0 among the selected LCHs, uplink resources may be allocated in descending order of priority of each LCH. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs having a lower priority than the corresponding logical channel. At this time, the Bj value is a value calculated for each LCH in a step before performing LCP, and may be calculated based on a PBR (Prioritized Bit Rate) value that is also set separately for each LCH. At this time, the Bj value may indicate the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0094] 2. For each LCH, the Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in step 1 above.

[0095] 3. If uplink transmission resources remain, resources can be allocated to all selected LCHs in descending priority order, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the corresponding LCH is exhausted. LCHs with the same priority value can be allocated resources fairly (or equally).

[0096] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, and 3 described above may be performed sequentially with the following priorities compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. The items below are listed in order of highest priority.

[0097] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0098] - data from any Logical Channel, except data from UL-CCCH (resource allocation process for LCH corresponding to steps 1, 2, and 3 described above)

[0099] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0100] The process of performing LCP in the above manner can be described in more detail through an example (1e-10). In this example, it can be assumed that LCH A, LCH B, and LCH C are configured as logical channels to be LCP-performed before LCP is performed. At this time, LCH A may be an LCH in which no delay-critical data exists (in other words, no delay-critical data is waiting to be transmitted in the buffer of the corresponding LCH). The delay-critical data may mean data in which the remaining time until the discardTimer of the PDCP SDU corresponding to the data expires is less than a network-configured threshold value (e.g., remainingTimeThreshold). The MAC layer of the terminal may allocate uplink transmission resources to logical channels (e.g., LCH A, LCH B, LCH C) in which the Bj value is calculated to be greater than 0. For reference, in this embodiment, the Bj values ​​(e.g., Bj_a, BJ_b, Bj_c) of each LCH are expressed as the same, but in reality, the values ​​may be calculated differently for each LCH. The transmission resource allocation may be performed in descending order of the priority of each LCH (in other words, ascending order of the priority value), and when the priorities of the LCHs are the same, the resource allocation priority may be determined according to the terminal implementation. In this example, although the priority values ​​of LCH A and LCH B are the same as 1, resource allocation may be performed for LCH A first in the order in which the LCHs are set by the terminal implementation, and then resource allocation may be performed for LCH B and LCH C in that order. More specifically, resource allocation may be performed for Bj_a of UL data (1e-03) waiting for LCH A first.Since there are transmission resources remaining on the MAC PDU that can be allocated to other LCHs, resource allocation can be performed for UL data (1e-04) waiting on LCH B. However, in this example, resource allocation is performed only for some of the UL data (1e-04) waiting on LCH B, and since there are no resources remaining, the LCP operation can be terminated.

[0101] If LCP is performed by considering only the priority of the logical channel as in the example above, delay-critical UL data (i.e., UL data belonging to LCH B and LCH C and whose remaining time until discardTimer expiration is shorter than the network configuration threshold) will be pushed down in the LCP process, have a high delay time, and may eventually be discarded due to discardTimer expiration. Therefore, in the present disclosure, we propose LCP methods that can consider not only the priority of the logical channel but also the transmission delay time of UL data (hereinafter referred to as Delay-aware LCP) as shown in the following Figures 1f, 1g, 1h, and 1i.

[0102] FIG. 1f is a diagram illustrating an example of a delay-aware LCP operation that determines priorities by considering transmission delay time between logical channels having the same priority according to an embodiment of the present disclosure.

[0103] Referring to Fig. 1f, when a terminal is allocated a UL grant from a base station, the terminal can calculate the size of uplink data (Transmit Block size or MAC PDU size) that can be transmitted using the UL grant. Thereafter, the MAC layer of the terminal can perform an LCP (Logical Channel Prioritization) operation to determine the order in which UL data waiting for transmission on each LCH are included in a MAC PDU of the calculated size.

[0104] More specifically, the MAC layer can perform LCP by considering not only the priority of the LCH, but also the presence or absence of delay-critical UL data or the remaining time of the UL data. At this time, delay-critical data may mean data for which the remaining time until the discardTimer of the PDCP SDU corresponding to the data expires is less than a network-configured threshold (e.g., remainingTimeThreshold). In addition, the remaining time may mean the remaining time until the discardTimer for the PDCP SDU corresponding to each UL data expires.

[0105] The LCP operation of the MAC, which takes into account both the priority of the logical channel and the presence or absence of delay-critical UL data (or the remaining time of UL data), can be specifically defined as 1f-01 and 1f-02.

[0106] The operations described in 1f-01 and 1f-02 may be performed after the terminal receives an UL grant for uplink data transmission from the base station. In addition, before the operations described in 1f-01 and 1f-02 are performed, LCHs that can transmit data using the received UL grant may be selected and screened in advance according to configuration information of each LCH (e.g., allowedSCS-List, maxPUSCH-Duration, configuredGrantType1Allowed, allowedServingCells, allowedCG-List, allowedPHY-PriorityIndex, allowedHARQ-mode, etc.). Thereafter, resource allocation for the LCH may be performed according to the two methods described in 1f-01 and 1f-02.

[0107] ● Method 1 (1f-01): Among LCHs with the same priority, resource allocation can be performed preferentially for LCHs that contain delay-critical data (i.e., LCHs that have delay-critical data waiting to be transmitted in the buffer). The LCP method described in 1f-01 can be performed in three stages as follows.

[0108] 1. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If delay-aware LCP operation is configured (or activated), resource allocation may be performed preferentially for LCHs with delay-critical data among LCHs having the same priority. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs having a lower priority than the corresponding logical channel. At this time, the Bj value is a value calculated for each LCH in the stage before performing LCP, and may be calculated based on a PBR (Prioritized Bit Rate) value that is also separately set for each LCH. At this time, the Bj value may represent the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0109] 2. The Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in step 1 above for each LCH.

[0110] 3. If uplink transmission resources remain, resources may be allocated in descending priority order regardless of the Bj value of each LCH until the UL grant or the data to be transmitted for the LCH is exhausted for all selected LCHs. If the delay-aware LCP operation is configured (or enabled), resource allocation may be performed preferentially for an LCH with delay-critical data among LCHs with the same priority. Otherwise (i.e., if the delay-aware LCP operation is not configured or enabled), LCHs with the same priority value may be allocated resources fairly (or equally).

[0111] ● Method 2 (1f-02): Among LCHs with the same priority, resource allocation can be performed in ascending order of the smallest remaining time in each LCH (i.e., the smallest value among the remaining times of all UL data waiting to be transmitted in the corresponding LCH). The LCP method described in 1f-02 can be performed in three steps as follows.

[0112] 1. Among the selected LCHs, resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If delay-aware LCP operation is configured (or activated), resources may be allocated in ascending order of the smallest remaining time for LCHs having the same priority. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs having a lower priority than the corresponding logical channel. At this time, the Bj value is a value calculated for each LCH in a step before performing LCP, and may be calculated based on a PBR (Prioritized Bit Rate) value that is also separately set for each LCH. At this time, the Bj value may represent the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0113] 2. The Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in step 1 above for each LCH.

[0114] 3. If uplink transmission resources remain, resources may be allocated to all selected LCHs in descending priority order, regardless of the Bj value of each LCH, until the UL grant or the data to be transmitted for the corresponding LCH is exhausted. If the delay-aware LCP operation is configured (or enabled), resources may be allocated to LCHs with the same priority in ascending order of the smallest remaining time of each LCH. Otherwise (i.e., if the delay-aware LCP operation is not configured or enabled), LCHs with the same priority value may be allocated resources fairly (or equally).

[0115] FIG. 1g is a diagram illustrating an example of a delay-aware LCP operation that first performs transmission delay-based resource allocation before logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0116] Referring to Fig. 1g, when a terminal is allocated a UL grant from a base station, the terminal can calculate the size of uplink data (Transmit Block size or MAC PDU size) that can be transmitted using the UL grant. Thereafter, the MAC layer of the terminal can perform an LCP (Logical Channel Prioritization) operation to determine the order in which UL data waiting for transmission on each LCH are included in a MAC PDU of the calculated size.

[0117] More specifically, the MAC layer can perform LCP by considering not only the priority of the LCH but also the presence or absence of delay-critical UL data or the remaining time of the UL data. At this time, delay-critical data may mean data for which the remaining time until the discardTimer of the PDCP SDU corresponding to the data expires is less than a network-configured threshold (e.g., remainingTimeThreshold). In addition, the remaining time may mean the remaining time until the discardTimer of the PDCP SDU corresponding to each UL data expires.

[0118] The LCP operation of the MAC, which takes into account both the priority of the logical channel and the presence or absence of delay-critical UL data (or the remaining time of UL data), can be specifically defined as 1g-01 and 1g-02.

[0119] The operations described in 1g-01 and 1g-02 may be performed after the terminal receives an UL grant for uplink data transmission to the base station. In addition, before the operations described in 1g-01 and 1g-02 are performed, LCHs that can transmit data using the received UL grant may be selected and screened in advance according to configuration information of each LCH (e.g., allowedSCS-List, maxPUSCH-Duration, configuredGrantType1Allowed, allowedServingCells, allowedCG-List, allowedPHY-PriorityIndex, allowedHARQ-mode, etc.). Thereafter, resource allocation for the LCH may be performed according to the two methods described in 1g-01 and 1g-02.

[0120] ● Method 1 (1g-01): Resource allocation can be performed preferentially for LCHs that contain delay-critical data (i.e., LCHs that have delay-critical data waiting to be transmitted in the buffer). The LCP method described in 1g-01 can be comprised of five steps as follows. For reference, steps 3 to 5 below can be identical to steps 1 to 3 of the embodiment described in FIG. 1e-01.

[0121] 1. If the delay-aware LCP operation is configured (or the delay-aware LCP operation is activated, or the UL grant is for delay-critical data / delay-aware scheduling), among the selected LCHs, resource allocation for LCHs having delay-critical data among LCHs having a Bj value greater than 0 may be performed in descending order of priority of each LCH (or ascending order of the smallest remaining time of each LCH, or descending order of the largest importance). In this case, the largest importance of each LCH may mean the largest importance among the importance of the PDU set corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. In addition, the smallest remaining time of each LCH may mean the smallest value among the remaining times corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. The above delay-critical data may refer to data for which the remaining time until the discardTimer of the PDCP SDU corresponding to the data expires is less than a network configuration threshold value (e.g., remainingTimeThreshold). If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources to all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the logical channel. At this time, the Bj value is a value calculated for each LCH in the stage before LCP execution, and may be calculated based on the PBR (Prioritized Bit Rate) value that is also set separately for each LCH.At this time, the Bj value may indicate the size of uplink transmission resources expected to be allocated to each LCH (in other words, the size of MAC SDUs expected to be provided to each LCH).

[0122] 2. For each LCH, the Bj value of each LCH may be reduced by the sum of the MAC SDU sizes processed in step 1. Although not shown in the drawing, if additional uplink transmission resources remain, a step of allocating resources in descending priority order regardless of the Bj value of each LCH may be additionally included, until the UL grant or data to be transmitted for the corresponding LCH is consumed, for all LCHs on which all delay-critical data selected in step 1 exist. After the resource allocation step, if additional uplink transmission resources remain, the resource allocation process continues by proceeding to step 3 below. Otherwise, steps 3, 4, and 5 below may be omitted.

[0123] 3. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with a lower priority than the corresponding logical channel.

[0124] 4. The Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in the above 3 steps for each LCH.

[0125] 5. If uplink transmission resources remain, resources can be allocated in descending priority order, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the selected LCH is exhausted. At this time, LCHs with the same priority value can be allocated resources fairly (or equally).

[0126] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, 3, 4, and 5 described above may be sequentially performed with a priority such as Option 1 or Option 2 below compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. Items listed as Option 1 or Option 2 below are listed in order of highest priority.

[0127] * Option 1:

[0128] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0129] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1, 2, 3, 4, and 5 described above)

[0130] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0131] * Option 2:

[0132] - Data form UL-CCCH and Very Higher priority MAC CEs (e.g. MAC CE for C-RNTI, etc.)

[0133] - data from any Logical Channel having delay-critical data, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1 and 2 described above)

[0134] - Higher priority MAC CE (e.g. MAC CE for DSR, (sidelink) BSR, PHR, etc.)

[0135] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 3, 4, and 5 described above)

[0136] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0137] ● Method 2 (1g-02): Resource allocation for each LCH can be performed with priority based on the remaining time of UL data. The LCP method described in 1g-02 can be performed in 5 steps as follows. For reference, steps 3 to 5 below can be identical to steps 1 to 3 of the embodiment described in FIG. 1e-01.

[0138] 1. If the delay-aware LCP operation is configured (or the delay-aware LCP operation is activated, or the UL grant is for delay-critical data / delay-aware scheduling), resource allocation for LCHs among the selected LCHs having Bj values ​​greater than 0 may be performed in ascending order of the smallest remaining time of each LCH (or descending order of the largest importance). At this time, the largest importance of each LCH may mean the largest importance among the importances (PDU set importance) of the PDU set corresponding to the data waiting to be transmitted in the buffer of the LCH. In addition, the smallest remaining time of each LCH may mean the smallest value among the remaining times corresponding to the data waiting to be transmitted in the buffer of the LCH. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources to all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs that have a lower priority than the corresponding logical channel. At this time, the Bj value is a value calculated for each LCH in the stage before LCP execution, and can be calculated based on the PBR (Prioritized Bit Rate) value that is separately set for each LCH. At this time, the Bj value can indicate the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0139] 2. For each LCH, the Bj value of each LCH may be reduced by the sum of the sizes of the MAC SDUs processed in the above step 1. Although not shown in the drawing, if additional uplink transmission resources remain, a step of allocating resources in ascending order of the smallest remaining time (or descending order of the largest importance) of each LCH, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the corresponding LCH is exhausted, may be additionally included. After the step of allocating resources, if additional uplink transmission resources remain, the resource allocation process proceeds to step 3 below and continues; otherwise, steps 3, 4, and 5 below may be omitted.

[0140] 3. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the corresponding logical channel.

[0141] 4. For each LCH, the Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in the above 3 steps.

[0142] 5. If uplink transmission resources remain, resources can be allocated in descending priority order, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the selected LCH is exhausted. LCHs with the same priority value can be allocated resources fairly (or equally).

[0143] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, 3, 4, and 5 described above may be sequentially performed with a priority such as Option 1 or Option 2 below compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. Items listed as Option 1 or Option 2 below are listed in order of highest priority.

[0144] * Option 1:

[0145] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0146] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1, 2, 3, 4, and 5 described above)

[0147] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0148] * Option 2:

[0149] - Data form UL-CCCH and Very Higher priority MAC CEs (e.g. MAC CE for C-RNTI, etc.)

[0150] - data from any Logical Channel having delay-critical data, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1 and 2 described above)

[0151] - Higher priority MAC CE (e.g. MAC CE for DSR, (sidelink) BSR, PHR, etc.)

[0152] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 3, 4, and 5 described above)

[0153] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0154] FIG. 1h is a diagram illustrating an example of a Delay-aware LCP operation that first performs DSR (Delay Status Report) setting and report-based resource allocation prior to logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0155] Referring to Figure 1h, when a terminal is allocated a UL grant from a base station, the terminal can calculate the size of uplink data (Transmit Block size or MAC PDU size) that can be transmitted using the UL grant. Thereafter, the MAC layer of the terminal can perform an LCP (Logical Channel Prioritization) operation to determine the order in which UL data waiting for transmission on each LCH are included in the MAC PDU of the calculated size.

[0156] More specifically, the MAC layer can perform LCP by considering whether the Delay Status Report (DSR) is set for the Logical Channel Group (LCG) to which each LCH belongs or whether a DSR report is performed. The LCP operation of the MAC can be specifically defined as 1h-01 and 1h-02.

[0157] The operations described in 1h-01 and 1h-02 may be performed after the terminal receives an UL grant for uplink data transmission from the base station. In addition, before the operations described in 1h-01 and 1h-02 are performed, LCHs that can transmit data using the received UL grant may be selected and screened in advance according to configuration information of each LCH (e.g., allowedSCS-List, maxPUSCH-Duration, configuredGrantType1Allowed, allowedServingCells, allowedCG-List, allowedPHY-PriorityIndex, allowedHARQ-mode, etc.). Thereafter, resource allocation for the LCH may be performed according to the two methods described in 1h-01 and 1h-02.

[0158] ● Method 1 (1h-01): Resource allocation for LCHs belonging to LCGs with DSR set can be performed with priority. The LCP method described in 1h-01 can be comprised of five steps as follows. For reference, steps 3 to 5 below can be identical to steps 1 to 3 of the embodiment described in FIG. 1e-01.

[0159] 1. If the delay-aware LCP operation is set (or the delay-aware LCP operation is activated, or the UL grant is for delay-critical data / delay-aware scheduling), among the selected LCHs, among the LCHs having a Bj value greater than 0, resource allocation for the LCHs belonging to the LCG for which DSR is set may be performed in descending order of priority of each LCH (or ascending order of the smallest remaining time of each LCH, or descending order of the largest importance). At this time, the largest importance of each LCH may mean the largest importance among the importance of the PDU set corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. In addition, the smallest remaining time of each LCH may mean the smallest value among the remaining times corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. If the PBR value of a specific LCH is set to 'infinity', the MAC entity can allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the logical channel. At this time, the Bj value is a value calculated for each LCH before performing LCP, and can be calculated based on the PBR (Prioritized Bit Rate) value that is also set separately for each LCH. At this time, the Bj value can indicate the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0160] 2. For each LCH, the Bj value of each LCH may be reduced by the sum of the MAC SDU sizes processed in step 1. Although not shown in the drawing, if additional uplink transmission resources remain, a step may additionally be included of allocating resources in descending order of priority (or ascending order of the smallest remaining time of each LCH, or descending order of the largest importance) regardless of the Bj value of each LCH until the UL grant or data to be transmitted for the LCH is consumed, for the LCHs belonging to the LCG for which the DSR selected in step 1 is set. After the resource allocation step, if additional uplink transmission resources remain, the resource allocation process may be continued by proceeding to step 3 below. Otherwise, steps 3, 4, and 5 below may be omitted.

[0161] 3. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the corresponding logical channel.

[0162] 4. For each LCH, the Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in the above 3 steps.

[0163] 5. If uplink transmission resources remain, resources can be allocated in descending priority order for all selected LCHs, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the corresponding LCH is exhausted. LCHs with the same priority value can be allocated resources fairly (or equally).

[0164] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, 3, 4, and 5 described above may be sequentially performed with a priority such as Option 1 or Option 2 below compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. Items listed as Option 1 or Option 2 below are listed in order of highest priority.

[0165] * Option 1:

[0166] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0167] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1, 2, 3, 4, and 5 described above)

[0168] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0169] * Option 2:

[0170] - Data form UL-CCCH and Very Higher priority MAC CEs (e.g. MAC CE for C-RNTI, etc.)

[0171] - data from any Logical Channel configured with DSR, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1 and 2 described above)

[0172] - Higher priority MAC CE (e.g. MAC CE for DSR, (sidelink) BSR, PHR, etc.)

[0173] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 3, 4, and 5 described above)

[0174] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0175] ● Method 2 (1h-02): Resource allocation for LCHs belonging to the LCG included (or reported) in the most recently transmitted DSR can be performed with priority. The LCP method described in 1h-02 can be performed in five steps as follows. For reference, steps 3 to 5 below can be identical to steps 1 to 3 of the embodiment described in FIG. 1e-01.

[0176] 1. If the delay-aware LCP operation is configured (or the delay-aware LCP operation is enabled, or the UL grant is for delay-critical data / delay-aware scheduling), resource allocation may be performed for the LCHs belonging to the LCG included (or reported) in the last transmitted DSR among the LCHs having a Bj value greater than 0 among the selected LCHs in descending order of priority of each LCH (or ascending order of the smallest remaining time of each LCH, or descending order of the largest importance). In this case, the largest importance of each LCH may mean the largest importance among the importances (PDU set importance) of the PDU set corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. In addition, the smallest remaining time of each LCH may mean the smallest value among the remaining times corresponding to the data waiting to be transmitted in the buffer of the corresponding LCH. If the PBR value of a specific LCH is set to 'infinity', the MAC entity can allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the logical channel. At this time, the Bj value is a value calculated for each LCH before performing LCP, and can be calculated based on the PBR (Prioritized Bit Rate) value that is also set separately for each LCH. At this time, the Bj value can indicate the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0177] 2. For each LCH, the Bj value of each LCH may be decreased by the sum of the sizes of the MAC SDUs processed in the step 1 above. Although not shown in the drawing, if additional uplink transmission resources remain, a step may additionally be included of allocating resources in descending order of priority (or ascending order of the smallest remaining time of each LCH, or descending order of the largest importance) regardless of the Bj value of each LCH until the UL grant or data to be transmitted for the LCH is exhausted, for the LCHs belonging to the LCG included (or reported) in the last transmitted DSR selected in the step 1 above. After the step of allocating resources, if additional uplink transmission resources remain, the resource allocation process may be continued by proceeding to step 3 below. Otherwise, steps 3, 4, and 5 below may be omitted.

[0178] 3. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the corresponding logical channel.

[0179] 4. The Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in the above 3 steps for each LCH.

[0180] 5. If uplink transmission resources remain, resources can be allocated in descending priority order, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the selected LCH is exhausted. LCHs with the same priority value can be allocated resources fairly (or equally).

[0181] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, 3, 4, and 5 described above may be sequentially performed with a priority such as Option 1 or Option 2 below compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. Items listed as Option 1 or Option 2 below are listed in order of highest priority.

[0182] * Option 1:

[0183] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0184] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1, 2, 3, 4, and 5 described above)

[0185] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0186] * Option 2:

[0187] - Data form UL-CCCH and Very Higher priority MAC CEs (e.g. MAC CE for C-RNTI, etc.)

[0188] - data from any Logical Channel belonging to LCH included in the latest DSR, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1 and 2 described above)

[0189] - Higher priority MAC CE (e.g. MAC CE for DSR, (sidelink) BSR, PHR, etc.)

[0190] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 3, 4, and 5 described above)

[0191] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0192] FIG. 1i is a diagram illustrating an example of a delay-aware LCP operation in which resource allocation for delay-critical data is performed first before logical channel priority-based resource allocation according to an embodiment of the present disclosure.

[0193] Referring to Fig. 1i, when a terminal is allocated a UL grant from a base station, the terminal can calculate the size of uplink data (Transmit Block size or MAC PDU size) that can be transmitted using the UL grant. Thereafter, the MAC layer of the terminal can perform an LCP (Logical Channel Prioritization) operation to determine the order in which UL data waiting for transmission on each LCH are included in a MAC PDU of the calculated size.

[0194] More specifically, the MAC layer can perform LCP by preferentially allocating resources to delay-critical data. At this time, delay-critical data may mean data for which the remaining time until the discardTimer of the PDCP SDU corresponding to the data expires is less than a network-configured threshold value (e.g., remainingTimeThreshold). The LCP operation of the MAC can be specifically defined as 1i-01.

[0195] The operation described in 1i-01 may be performed after the terminal receives an UL grant for uplink data transmission from the base station. In addition, before the operation described in 1i-01 is performed, LCHs that can transmit data using the received UL grant may be selected and screened in advance according to configuration information of each LCH (e.g., allowedSCS-List, maxPUSCH-Duration, configuredGrantType1Allowed, allowedServingCells, allowedCG-List, allowedPHY-PriorityIndex, allowedHARQ-mode, etc.). Thereafter, resource allocation for the LCH may be performed according to the following method described in 1i-01.

[0196] ● Resource allocation for delay-critical data can be performed with priority. The LCP method described in 1i-01 can be performed in five steps as follows. For reference, steps 3 to 5 below can be identical to steps 1 to 3 of the embodiment described in FIG. 1e-01.

[0197] 1. If delay-aware LCP operation is configured (or delay-aware LCP operation is activated, or the UL grant is for delay-critical data / delay-aware scheduling), resource allocation may be performed for transmittable delay-critical data among the data waiting to be transmitted in the buffers of the selected LCHs (in ascending order of remaining time of each data or descending order of importance). At this time, the importance of each data may mean the importance (PDU set importance) of the PDU set corresponding to the data. In addition, the remaining time of each data may mean the remaining time until the discardTimer for the PDCP SDU corresponding to each data expires. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources to all transmittable data within the LCH before satisfying the PBR values ​​of LCHs with a lower priority than the corresponding logical channel. At this time, the Bj value is a value calculated for each LCH in the stage before LCP execution, and can be calculated based on the PBR (Prioritized Bit Rate) value that is separately set for each LCH. At this time, the Bj value can indicate the size of the uplink transmission resource expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0198] 2. For each LCH, the Bj value of each LCH may be reduced by the sum of the sizes of the MAC SDUs processed in the above step 1. Although not shown in the drawing, if additional uplink transmission resources remain, a step of allocating resources for transmittable delay-critical data among the data waiting to be transmitted in the buffers of the LCHs selected in the above step 1 in ascending order of the remaining time of each data (or descending order of importance) regardless of the Bj value of each LCH before the UL grant or delay-critical data is consumed may be additionally included. After the step of allocating the resources, if additional uplink transmission resources remain, the resource allocation process may be continued by proceeding to step 3 below; otherwise, steps 3, 4, and 5 below may be omitted.

[0199] 3. Among the selected LCHs, uplink resources may be allocated in descending order of priority for LCHs having a Bj value greater than 0. If the PBR value of a specific LCH is set to 'infinity', the MAC entity may allocate resources for all data that can be transmitted within the LCH before satisfying the PBR values ​​of LCHs with lower priorities than the corresponding logical channel.

[0200] 4. For each LCH, the Bj value of each LCH can be reduced by the sum of the MAC SDU sizes processed in the above 3 steps.

[0201] 5. If uplink transmission resources remain, resources can be allocated in descending priority order for all selected LCHs, regardless of the Bj value of each LCH, until the UL grant or data to be transmitted for the corresponding LCH is exhausted. LCHs with the same priority value can be allocated resources fairly (or equally).

[0202] As an example, resource allocation for data received from the LCH corresponding to steps 1, 2, 3, 4, and 5 described above may be sequentially performed with a priority such as Option 1 or Option 2 below compared to other uplink MAC CE transmissions and UL-CCCH data transmissions. Items listed as Option 1 or Option 2 below are listed in order of highest priority.

[0203] * Option 1:

[0204] - Data form UL-CCCH and Higher priority MAC CEs (e.g. MAC CE for C-RNTI, BFR, (sidelink) CG confirm, (sidelink) LBT failure, TA report, DSR, (sidelink) BSR, PHR, etc.)

[0205] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1, 2, 3, 4, and 5 described above)

[0206] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0207] * Option 2:

[0208] - Data form UL-CCCH and Very Higher priority MAC CEs (e.g. MAC CE for C-RNTI, etc.)

[0209] - Delay-critical data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 1 and 2 described above)

[0210] - Higher priority MAC CE (e.g. MAC CE for DSR, (sidelink) BSR, PHR, etc.)

[0211] - data from any Logical Channel, except data from UL-CCCH (LCH resource allocation process corresponding to steps 3, 4, and 5 described above)

[0212] - Lower priority MAC CEs (e.g. MAC CE for RBR query, (sidelink) padding BSR)

[0213] FIG. 1J is a diagram for explaining terminal operation for performing Delay-aware LCP operation according to one embodiment of the present disclosure.

[0214] The terminal may transmit its capability information to the base station in step 1j-03. The capability information may include indicator information indicating whether the proposed delay-aware LCP (or delay-aware scheduling) operation is supported. More specifically, the terminal may configure the terminal capability information as described in step 1d-10 of the above drawing.

[0215] In step 1j-05, the terminal may receive DSR and / or delay-aware LCP (or delay-aware scheduling) configuration information from the base station. More specifically, the delay-aware LCP (or delay-aware scheduling) configuration may be configured and included in an RRCReconfiguration message as described in step 1d-12 of the drawing.

[0216] In step 1j-07, the terminal may be instructed to activate delay-aware LCP (or delay-aware scheduling) operation from the base station through at least one of DCI, MAC CE, and RRC messages. This step may be optionally performed as needed.

[0217] In step 1j-10, the terminal may transmit a BSR and / or a DSR. More specifically, when the terminal has data to transmit on the uplink, the terminal may transmit a BSR and / or a DSR if the BSR and / or DSR triggering conditions described in steps 1d-16 and 1d-18 are satisfied.

[0218] In step 1j-12, the terminal may receive DCI including a UL grant for uplink data transmission from the base station. At this time, as described in step 1d-20 of the drawing, it may be indicated that the UL grant is for delay-critical data, delay-aware LCP, or delay-aware scheduling through a new DCI format, a new RNTI, or a new indicator.

[0219] In step 1j-15, the terminal can determine whether the delay-aware LCP (or delay-aware scheduling) operating condition is satisfied based on the delay-aware LCP (or delay-aware scheduling) setting in step 1j-05, the activation indication in step 1j-07, and the UL grant usage indication in step 1j-12. More specifically, the terminal can determine whether the delay-aware LCP (or delay-aware scheduling) operating condition is satisfied by a combination of at least one of the conditions described below.

[0220] * Condition 1: If delay-aware LCP (or delay-aware Scheduling) operation is set by the above 1j-05 step operation.

[0221] * Condition 2: If the delay-aware LCP (or delay-aware Scheduling) operation is activated by the above step 1j-07 operation.

[0222] * Condition 3: If the above steps 1j-12 indicate that the UL grant is for delay-critical data, delay-aware LCP, or delay-aware scheduling.

[0223] If one of the three conditions described above is satisfied or if one or more combinations of the conditions are satisfied, the terminal may proceed to steps 1j-19 and perform delay-aware LCP operation in one of the embodiments described in FIGS. 1f, 1g, 1h, and 1i. If the delay-aware LCP (or delay-aware scheduling) operation condition is not satisfied, the terminal may proceed to steps 1j-17 and perform logical channel priority-based LCP operation as in the embodiment of FIG. 1e.

[0224] In step 1j-17, the terminal can perform a logical channel priority-based LCP operation as in the embodiment of FIG. 1e.

[0225] In steps 1j-19, the terminal may perform delay-aware LCP operation in one of the embodiments described in FIGS. 1f, 1g, 1h, and 1i.

[0226] FIG. 1k is a diagram illustrating base station operations for setting up delay-aware LCP operations according to one embodiment of the present disclosure.

[0227] In step 1k-03, the base station receives terminal capability information transmitted by the terminal. The capability information may include indicator information indicating whether the proposed delay-aware LCP (or delay-aware scheduling) operation is supported. More specifically, the base station may receive terminal capability information configured as described in step 1d-10 of the above drawing.

[0228] In step 1k-05, the base station can configure DSR and delay-aware LCP (or delay-aware scheduling) for the terminal. More specifically, the delay-aware LCP (or delay-aware scheduling) configuration can be configured and included in the RRCReconfiguration message as described in step 1d-12 of the above drawing.

[0229] At step 1k-07, the base station can receive BSR and / or DSR from the terminal.

[0230] In step 1k-10, the base station can determine whether a UL grant is needed for delay-critical data, delay-aware LCP, or delay-aware scheduling (i.e., prioritizing transmission of delay-critical data) based on information included in the BSR and / or DSR received from the terminal in step 1k-07. For example, the base station can receive the BSR and / or DSR from the terminal in step 1k-07, determine that delay-critical data exists among the uplink data to be transmitted by the terminal, and determine that a UL grant is needed to instruct the terminal to prioritize transmission of the delay-critical data. If the base station determines that a UL grant is needed for delay-critical data, delay-aware LCP, or delay-aware scheduling (i.e., prioritizing transmission of delay-critical data), the base station may proceed to step 1k-15 and transmit a DCI including the UL grant while indicating that the UL grant is for delay-critical data, delay-aware LCP, or delay-aware scheduling as described in step 1d-20 of the drawing. Conversely, if the base station determines that a UL grant is not needed for delay-critical data, delay-aware LCP, or delay-aware scheduling (i.e., prioritizing transmission of delay-critical data), the base station may proceed to step 1k-12 and transmit a DCI including an existing UL grant without any other instructions.

[0231] At step 1k-12, the base station can transmit DCI including existing UL grant without any special instructions.

[0232] In step 1k-15, the base station may transmit DCI including a UL grant, indicating that the UL grant is for delay-critical data, delay-aware LCP, or delay-aware scheduling, as described in step 1d-20 of the drawing.

[0233] FIG. 2 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0234] Referring to FIG. 2, the terminal includes an RF (Radio Frequency) processing unit (2-10), a baseband processing unit (2-20), a storage unit (2-30), and a control unit (2-40). Of course, the present invention is not limited to the above example, and the terminal may include fewer or more components than those illustrated in FIG. 2. The RF processing unit (2-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (2-10) up-converts a baseband signal provided from the baseband processing unit (2-20) into an RF band signal and then transmits it through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (2-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In Fig. 2, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (2-10) may include multiple RF chains. Furthermore, the RF processing unit (2-10) may perform beamforming. For beamforming, the RF processing unit (2-10) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit (2-10) may perform MIMO (multi-input multi-output) and may receive multiple layers when performing MIMO operation. The RF processing unit (2-10) may perform reception beam sweeping by appropriately setting multiple antennas or antenna elements under the control of the control unit (2-40), or may adjust the direction and beam width of the reception beam so that the reception beam is coordinated with the transmission beam.

[0235] The baseband processing unit (2-20) can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (2-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (2-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (2-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (2-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (2-20) divides the baseband signal provided from the RF processing unit (2-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then restores the received bit string through demodulation and decoding.

[0236] The baseband processing unit (2-20) and the RF processing unit (2-10) can transmit and receive signals as described above. The baseband processing unit (2-20) and the RF processing unit (2-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (2-20) and the RF processing unit (2-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (2-20) and the RF processing unit (2-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. In addition, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band. The terminal may transmit and receive signals with the base station using the baseband processing unit (2-20) and the RF processing unit (2-10), and the signals may include control information and data.

[0237] The storage unit (2-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (2-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (2-30) can provide the stored data upon request from the control unit (2-40). In addition, the storage unit (2-30) may be configured with multiple memories. According to one embodiment, the storage unit (2-30) may store a program for performing the split bearer operation method of the present disclosure.

[0238] The control unit (2-40) can control the overall operations of the terminal. For example, the control unit (2-40) can transmit and receive signals through the baseband processing unit (2-20) and the RF processing unit (2-10). In addition, the control unit (2-40) can record and read data in the storage unit (2-40). For this purpose, the control unit (2-40) can include at least one processor. For example, the control unit (2-40) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. In addition, at least one component within the terminal can be implemented as a single chip. In addition, according to one embodiment of the present disclosure, the control unit (2-40) can include a multi-connection processing unit (2-42) that performs processing for operating in a multi-connection mode.

[0239] FIG. 3 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0240] Referring to FIG. 3, the base station may include an RF processing unit (3-10), a baseband processing unit (3-20), a backhaul communication unit (3-30), a storage unit (3-40), and a control unit (3-50). Of course, the present invention is not limited to the above example, and the base station may include fewer or more components than the configuration illustrated in FIG. 3.

[0241] The RF processing unit (3-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (3-10) can up-convert the baseband signal provided from the baseband processing unit (3-20) into an RF band signal and transmit it through an antenna, and down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (3-10) can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In Fig. 3, only one antenna is illustrated, but the base station can be equipped with multiple antennas. In addition, the RF processing unit (3-10) can include multiple RF chains. Furthermore, the RF processing unit (3-10) can perform beamforming. For beamforming, the RF processing unit (3-10) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit (3-10) can perform a downlink MIMO operation by transmitting one or more layers. The RF processing unit (3-10) can perform reception beam sweeping by appropriately setting multiple antennas or antenna elements under the control of the control unit, or can adjust the direction and beam width of the reception beam so that the reception beam is in coordination with the transmission beam.

[0242] The baseband processing unit (3-20) can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (3-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (3-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (3-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (3-20) can generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (3-20) divides the baseband signal provided from the RF processing unit (3-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (3-20) and the RF processing unit (3-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (3-20) and the RF processing unit (3-10) may be referred to as a transmitting unit, a receiving unit, a transceiver unit, a communication unit, or a wireless communication unit. The base station can transmit and receive signals with the terminal using the baseband processing unit (3-20) and the RF processing unit (3-10), and the signals may include control information and data.

[0243] The backhaul communication unit (3-30) can provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit (3-30) can convert a bit string transmitted from a primary base station to another node, such as an auxiliary base station or core network, into a physical signal, and can convert a physical signal received from another node into a bit string.

[0244] The storage unit (3-40) can store data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (3-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, etc. In addition, the storage unit (3-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to the terminal. In addition, the storage unit (3-40) can provide the stored data at the request of the control unit (3-50). The storage unit (3-40) can also store a program for performing the split bearer operation method of the present disclosure.

[0245] The control unit (3-50) can control the overall operations of the base station. For example, the control unit (3-50) can transmit and receive signals through the baseband processing unit (3-20) and the RF processing unit (3-10) or through the backhaul communication unit (3-30). In addition, the control unit (3-50) can record and read data in the storage unit (3-40). For this purpose, the control unit (3-50) can include at least one processor. In addition, at least one component of the base station can be implemented as a single chip. In addition, at least one component of the base station can be implemented as a single chip. In addition, each component of the base station can operate to perform the embodiments of the present disclosure described above.

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

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

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

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

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

[0251] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of operating a UE (user equipment) in a wireless communication system, A step of receiving, from a base station, a radio resource control (RRC) message including at least one of configuration information for delay-aware scheduling and a threshold value associated with delay-aware logical channel prioritization (LCP); A step of transmitting a DSR (delay status report) MAC (medium access control) CE (control element) to the above base station; A step of receiving DCI (downlink control information) including an uplink grant from the above base station; A step of performing the delay-aware LCP based on at least one of the above setting information and the above threshold value; and A step of transmitting uplink data to the base station using the uplink grant based on the delay-aware LCP; A method, characterized in that the above threshold is set in units of LCH (Logical channel).

2. In paragraph 1, The steps of performing the above delay-aware LCP are: A method comprising: a step of allocating resources in descending order of priority for one or more LCHs; characterized in that resources are allocated in ascending order of the smallest remaining time of each LCH for LCHs having the same priority.

3. In paragraph 1, A method further comprising the step of receiving a message from the base station instructing activation of the delay-aware LCP.

4. In paragraph 1, A method, characterized in that the DCI includes an indicator indicating that the uplink grant is for delay-aware scheduling.

5. In paragraph 1, A method further comprising the step of transmitting, to the base station, UE capability information indicating that the UE supports the delay-aware scheduling or the delay-aware LCP.

6. In a method of operating a base station in a wireless communication system, A step of transmitting, to a UE (user equipment), an RRC (radio resource control) message including at least one of configuration information for delay-aware scheduling and a threshold value associated with delay-aware logical channel prioritization (LCP); A step of receiving a DSR (delay status report) MAC (medium access control) CE (control element) from the UE; A step of transmitting DCI (downlink control information) including an uplink grant to the UE; and A step of receiving uplink data transmitted using the uplink grant from the UE; The above uplink data is associated with the delay-aware LCP based on at least one of the setting information and the threshold value, A method, characterized in that the above threshold is set in units of LCH (Logical channel).

7. In paragraph 6, Further comprising the step of transmitting a message to the UE indicating activation of the delay-aware LCP, A method, characterized in that the DCI includes an indicator indicating that the uplink grant is for delay-aware scheduling.

8. In paragraph 6, A method further comprising the step of receiving, from the UE, UE capability information indicating that the UE supports the delay-aware scheduling or the delay-aware LCP.

9. In the UE (user equipment) of a wireless communication system, Transmitter and receiver; and At least one control unit coupled to the above transceiver unit, At least one of the above control units, Receive, from a base station, a radio resource control (RRC) message including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware logical channel prioritization (LCP), To the above base station, transmit DSR (delay status report) MAC (medium access control) CE (control element), From the above base station, DCI (downlink control information) including an uplink grant is received, Performing the delay-aware LCP based on at least one of the above setting information and the above threshold value, Based on the above delay-aware LCP, uplink data is configured to be transmitted to the base station using the uplink grant, A UE, characterized in that the above threshold is set per LCH (Logical channel).

10. In paragraph 9, A UE, wherein at least one control unit is configured to allocate resources in descending order of priority for one or more LCHs, and resources are allocated in ascending order of the smallest remaining time of each LCH for LCHs having the same priority.

11. In paragraph 9, The at least one control unit is configured to receive a message from the base station instructing activation of the delay-aware LCP, A UE, characterized in that the DCI includes an indicator indicating that the uplink grant is for delay-aware scheduling.

12. In paragraph 9, The UE, wherein at least one control unit is configured to transmit, to the base station, UE capability information indicating that the UE supports the delay-aware scheduling or the delay-aware LCP.

13. In a base station in a wireless communication system, Transmitter and receiver; and At least one control unit coupled to the above transceiver unit, At least one of the above control units, Transmitting an RRC (radio resource control) message to a UE (user equipment) including at least one of configuration information for delay-aware scheduling and a threshold associated with delay-aware logical channel prioritization (LCP), From the above UE, a DSR (delay status report) MAC (medium access control) CE (control element) is received, To the above UE, DCI (downlink control information) including uplink grant is transmitted, configured to receive uplink data transmitted from the above UE using the above uplink grant, The above uplink data is associated with the delay-aware LCP based on at least one of the setting information and the threshold value, The base station is characterized in that the above threshold value is set per LCH (Logical channel) unit.

14. In paragraph 13, The at least one control unit is configured to transmit a message to the UE indicating activation of the delay-aware LCP, A base station, characterized in that the DCI includes an indicator indicating that the uplink grant is for the delay-aware scheduling.

15. In paragraph 13, A base station, wherein said at least one control unit is configured to receive, from said UE, UE capability information indicating that said UE supports said delay-aware scheduling or said delay-aware LCP.

Images