Method and apparatus for serving XR traffic of different importance in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. More specifically, a method performed by a user equipment (UE) in a wireless communication system of the present disclosure comprises the steps of: identifying a trigger of a buffer status report (BSR) for a plurality of logical channels; and transmitting a BSR to a base station, in which the BSR may be triggered when an importance of uplink data that has become available to a prescribed logical channel among the plurality of logical channels is higher than an importance of other available uplink data included in other logical channels.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system (or mobile communication system). More specifically, the present disclosure relates to operations of a UE and a base station in the wireless communication system (or mobile communication system), and more specifically, to a method and apparatus for serving extended reality (ER) traffic flows with different importance levels. Background Art

[0002] 5G mobile communications technology defines a wide frequency band to enable high transmission rates and new services, and can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as mmWave, including 28 GHz and 39 GHz. Furthermore, to achieve transmission rates fifty times faster than 5G mobile communications technology and ultra-low latency one-tenth that of 5G mobile communications technology, consideration has been given to implementing 6G mobile communications technology in the terahertz frequency band (e.g., the 95 GHz to 3 THz band) (referred to as "beyond 5G systems").

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

[0004] Currently, discussions are underway on improvements and performance enhancements to initial 5G mobile communication technologies in view of the services they are to support, and there is already standardization of physical layers for technologies such as Vehicle-to-Everything (V2X) for assisting driving determination of autonomous vehicles based on information about the position and status of a vehicle transmitted by the vehicle and for enhancing user convenience, New Radio Unlicensed (NR-U) designed to enable system operation in unlicensed bands to comply with various regulatory requirements, NR UE power saving, Non-Terrestrial Network (NTN) for UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] Furthermore, in the area of ​​radio interface architecture / protocols, standardization is underway on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (NR two-step RACH) for simplifying the random access procedure. In terms of system architecture / services, standardization is also underway on the following: a 5G baseline architecture (e.g., a service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] If such 5G mobile communication systems are commercialized, the already exponentially growing number of connected devices will be connected to the communication network, and it is therefore expected that enhanced functionality and performance of the 5G mobile communication system and the integrated operation of connected devices will be necessary. To this end, new research is planned related to: extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; improving 5G performance and reducing 5G complexity by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, such developments in 5G mobile communication systems will serve as the foundation for the development of not only new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also full-duplex technologies for increasing the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for implementing services at a complexity level that exceeds the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] With the advancement of communication systems, the demand for efficiently providing XR services is increasing. Summary of the Invention

[0009] Technical issues

[0010] The present disclosure is to provide an apparatus and method capable of effectively providing XR services in a wireless communication system.

[0011] Solution to the problem

[0012] According to an embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include: recognizing that a buffer status report (BSR) has been triggered for a plurality of logical channels; and transmitting the BSR to a base station. The BSR may be triggered when a piece of uplink data that has become available for a predetermined logical channel among the plurality of logical channels is more important than a piece of available uplink data belonging to another logical channel.

[0013] According to an embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system, and performed by a base station in the wireless communication system, may include: transmitting an uplink grant to the terminal, the uplink grant being used to allocate uplink resources for transmitting buffer status reports (BSRs) for multiple logical channels of the terminal; and receiving the BSRs from the terminal on the uplink resources used for transmitting the BSRs. The BSR may be triggered when a piece of uplink data that has become available for a predetermined logical channel among the multiple logical channels is more important than a piece of available uplink data belonging to another logical channel.

[0014] According to an embodiment of the present disclosure, a user equipment (UE) in a wireless communication system may include: a transceiver; and a controller connected to the transceiver. The controller may be configured to: identify that a buffer status report (BSR) has been triggered for multiple logical channels; and transmit the BSR to a base station. The BSR may be triggered when a piece of uplink data that has become available for a predetermined logical channel among the multiple logical channels is more important than a piece of available uplink data belonging to another logical channel.

[0015] A base station in a wireless communication system according to an embodiment of the present disclosure may include: a transceiver; and a controller connected to the transceiver. The controller may be configured to: send an uplink grant to a terminal, the uplink grant being used to allocate uplink resources for transmitting buffer status reports (BSRs) for multiple logical channels of the terminal; and receive the BSRs from the terminal on the uplink resources used for BSR transmission. The BSR may be triggered when a piece of uplink data that has become available for a predetermined logical channel among the multiple logical channels is more important than a piece of available uplink data belonging to another logical channel.

[0016] Advantageous Effects of the Invention

[0017] According to various embodiments of the present disclosure, XR business and XR services can be efficiently provided in the next generation wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The structure of a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0019] Figure 2 A radio protocol structure in a Long Term Evolution (LTE) and New Radio (NR) system according to an embodiment of the present disclosure is shown.

[0020] Figure 3 A protocol data unit (PDU) set configuration based on an application data unit (ADU) according to an embodiment of the present disclosure is shown.

[0021] Figure 4 A protocol layer structure for serving PDU sets with different importance levels according to an embodiment of the present disclosure is shown.

[0022] Figure 5 An example of a buffer status report (BSR) triggering operation based on a logical channel (LCH) priority according to an embodiment of the present disclosure is shown.

[0023] Figure 6 An example of an importance-based BSR triggering operation of a PDU set according to an embodiment of the present disclosure is shown.

[0024] Figure 7 and Figure 8 An example of a logical channel priority (LCP) operation according to an embodiment of the present disclosure is shown, where the priority of the LCH and the importance level of the PDU set are considered together.

[0025] Figure 9 A split bearer configuration according to an embodiment of the present disclosure is shown.

[0026] Figure 10 An example of a packet transmission operation when a split bearer operation based on a data radio bearer (DRB) is configured according to an embodiment of the present disclosure is shown.

[0027] Figure 11 An example of a packet transmission operation when a split bearer operation is configured based on the importance of a PDU set according to an embodiment of the present disclosure is shown.

[0028] Figure 12 A signaling process between a UE and a base station for configuring and operating UE operations based on PDU set importance in a next generation mobile communication system according to an embodiment of the present disclosure is shown.

[0029] Figure 13A medium access control (MAC) control element (CE) structure that may be used to activate / deactivate packet data convergence protocol (PDCP) duplication based on the importance of a PDU set according to an embodiment of the present disclosure is shown.

[0030] Figure 14 A UE device according to an embodiment of the present disclosure is shown.

[0031] Figure 15 A base station device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. When describing the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear. The terms described below are defined in consideration of the functions in the present disclosure and may vary depending on the user, the user's intention or custom. Therefore, the definition of terms should be based on the content in the entire specification. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0033] For the same reason, some elements may be exaggerated, omitted or schematically shown in the accompanying drawings. Moreover, the size of each element does not fully reflect the actual size. In the various drawings, the same reference numerals are used to mark the same or equivalent elements.

[0034] The advantages and features of the present disclosure and the manner in which they are achieved will be apparent by reference to the embodiments described in detail below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but may be implemented in a variety of different forms. The following embodiments are provided only to fully disclose the present disclosure and to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0035] In this article, it will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the function specified in the flowchart box. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including an instruction device that implements the function specified in the flowchart box or multiple boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process so that the instructions executed on the computer or other programmable device provide steps for implementing the function specified in the flowchart box.

[0036] In addition, each block in the flow chart may represent a module, segment or portion of code that includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative embodiments, the functions marked in the blocks may not occur in order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved.

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

[0038] In the following description of the present disclosure, detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0039] In the following description, for the sake of convenience, terms used to identify access 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 illustratively used. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to subjects with equivalent technical meanings may also be used.

[0040] In the following description, the terms "physical channel" and "signal" may be used interchangeably with the terms "data" or "control signal." For example, the term "physical downlink shared channel (PDSCH)" refers to a physical channel on which data is transmitted, but PDSCH may also be used to refer to "data." That is, in this disclosure, the expression "transmitting a physical channel" may be interpreted as having the same meaning as the expression "transmitting data or a signal via a physical channel."

[0041] In the following description of this disclosure, upper layer signaling refers to a signal transmission scheme from a base station to a terminal via a downlink data channel of the physical layer, or from a terminal to a base station via an uplink data channel of the physical layer. Upper layer signaling can also be understood as radio resource control (RRC) signaling or medium access control (MAC) control element (CE).

[0042] In the following description of this disclosure, for convenience, terms and names defined in the 3rd Generation Partnership Project New Radio (3GPP NR) or 3GPP Long Term Evolution (3GPP LTE) standards will be used. However, this disclosure is not limited by these terms and names and can be applied in the same manner to systems compliant with other standards. In this disclosure, for convenience, the term "gNB" can be used interchangeably with the term "eNB." That is, a base station described as an "eNB" can also be referred to as a "gNB." Furthermore, the term "terminal" can refer not only to mobile phones, MTC devices, NB-IoT devices, and sensors, but also to other wireless communication devices.

[0043] In the following description, a base station is an entity that allocates resources to a terminal and can be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, examples of base stations and terminals are not limited to those mentioned above.

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

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

[0046] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single-carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the radio link via which a user equipment (UE) or mobile station (MS) transmits data or control signals to a base station (BS) or eNode B, and the downlink refers to the radio link via which a base station transmits data or control signals to a UE. This multiple access scheme separates the data or control information of each user by allocating and operating time-frequency resources for transmitting data or control information to each user, thereby avoiding overlap, that is, establishing orthogonality.

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

[0048] According to some embodiments, eMBB may be designed to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide increased user-perceived data rates and maximum data rates to the UE. To meet such requirements, improvements in transmission / reception technology, including further enhanced multiple-input multiple-output (MIMO) transmission technology, may be necessary. Furthermore, the data rates required by the 5G communication system can be achieved by using frequency bandwidths greater than 20 MHz in frequency bands of 3 to 6 GHz or 6 GHz or higher, rather than using transmission bandwidths of up to 20 MHz to transmit signals in the 2 GHz frequency band used in LTE.

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

[0050] Finally, URLLC (which is a cellular-based mission-critical wireless communication service) can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alerts, and the like. Therefore, URLLC must provide communications with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms and may also require a packet error rate of 10-5 or less. However, mMTC, URLLC, and eMBB as described above are merely examples of different types of services, and the types of services to which the present disclosure is applied are not limited to those mentioned above.

[0051] The three services considered in the 5G communication system, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services to meet the different requirements of each service. However, mMTC, URLLC, and eMBB as described above are only examples of different types of services, and the service types to which the present disclosure is applied are not limited to those mentioned above.

[0052] In the following description of the embodiments of the present disclosure, LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communications) systems will be described by way of example. However, the embodiments of the present disclosure can be applied to other communication systems with similar backgrounds or channel types. In addition, based on the determination of those skilled in the art, the embodiments of the present disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0053] refer to Figure 1 , the radio access network of the next generation mobile communication system (New Radio, NR or 5G) includes a next generation base station (New Radio Node B, hereinafter referred to as gNB) 110 and an access and mobility management function (AMF) 105. User equipment (New Radio User Equipment, hereinafter referred to as NR UE or terminal) 115 accesses external networks via the gNB 110 and AMF 105.

[0054] exist Figure 1 In the present invention, the gNB 110 may correspond to the evolved Node B (eNB) 130 of the conventional LTE system. The gNB 110 may be connected to the NR UE 115 through a radio channel and provide excellent services compared to the conventional Node B (120).

[0055] According to an embodiment of the present disclosure, in a next-generation mobile communication system, since all user traffic is served through a shared channel, a device is required to collect status information (such as the UE's buffer status, available transmit power status, and channel status) and perform scheduling accordingly, and gNB 110 serves as this device. Generally, one gNB can control multiple cells.

[0056] According to the embodiments of the present disclosure, in order to achieve ultra-high-speed data transmission beyond the current LTE, the next-generation mobile communication system can provide a bandwidth wider than the existing maximum bandwidth, can adopt orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as a radio access technology, and can further integrate beamforming technology therewith.

[0057] In addition, according to an embodiment of the present disclosure, the next-generation mobile communication system can adopt an adaptive modulation and coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the UE. The AMF 105 can perform functions such as mobility support, bearer configuration, and QoS configuration. The AMF is a device responsible for various control functions for the UE and a mobility management function, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can interwork with the existing LTE system, and the AMF 105 can be connected to the mobility management entity (MME) 125 via a network interface. The MME 125 is connected to the eNB 130, which is an existing base station. A UE supporting LTE-NR dual connectivity can transmit / receive data (135) while maintaining connections with both the gNB 110 and the eNB 130.

[0058] Figure 2 The radio protocol structure in LTE and NR systems according to an embodiment of the present disclosure is shown.

[0059] refer to Figure 2 , the radio protocol of the NR system may include a service data adaptation protocol (SDAP) 205 or 210, a packet data convergence protocol (PDCP) 215 or 220, a radio link control (RLC) 225 or 230, and a medium access control (MAC) 235 or 240 on each side of the UE and the gNB. The SDAP 205 or 210 may perform an operation for mapping each QoS flow to a specific data radio bearer (DRB), and an SDAP configuration corresponding to each DRB may be given from an upper layer (e.g., an RRC layer).

[0060] According to an embodiment of the present disclosure, the PDCP 215 or 220 can be used to perform operations such as IP header compression / reconstruction, and can also perform reordering operations on data packets to provide an in-order data delivery service to higher layers. In addition, the RLC 225 or 230 can reconstruct the PDCP PDU to an appropriate size. The MAC 235 or 240 can be connected to multiple RLC layer devices configured for a single UE and perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing MAC PDUs into RLC PDUs. The physical (PHY) layer 245 or 250 can perform operations of channel coding and modulating upper layer data to obtain OFDM symbols and deliver the OFDM symbols through a radio channel, or demodulate OFDM symbols received through a radio channel, channel decode the OFDM symbols, and deliver the OFDM symbols to upper layers.

[0061] In addition, according to an embodiment of the present disclosure, the PHY layer 245 or 250 may use hybrid automatic repeat request (HARQ) for additional error correction, and the receiving end may send a bit to the transmitting end to indicate whether the packet sent by it has been received. Information regarding whether the receiving end has received the packet from the transmitting end may be referred to as HARQ ACK / NACK information. In the case of an LTE system, downlink HARQ ACK / NACK information regarding uplink data transmission may be transmitted via the Physical HARQ Indicator Channel (PHICH). In the case of an NR system, downlink HARQ ACK / NACK information regarding uplink data transmission may be transmitted via the Physical Dedicated Control Channel (PDCCH), which is used to transmit downlink and / or uplink resource allocations, etc., and the base station may determine whether retransmission is required or whether a new transmission is to be performed based on the UE's scheduling information.

[0062] Unlike LTE, the reason why the base station in the NR system determines whether retransmission is required or whether to perform a new transmission based on the UE's scheduling information is because asynchronous HARQ is applied in NR. 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 primary cell (PCell) (described later). However, if the UE supports the same content, HARQ ACK / NACK information for the secondary cell (SCell) (described later) can be transmitted, and the SCell can be referred to as a PUCCH SCell.

[0063] Although not illustrated in the drawing, a radio resource control (RRC) layer may exist on each upper layer of the PDCP layer of the UE and the base station, and the RRC layer may exchange access / measurement-related configuration control messages for radio resource control.

[0064] The PHY layer 245 or 250 may include one or more frequencies / carriers, and the technology for simultaneously configuring and using multiple frequencies may be referred to as carrier aggregation (hereinafter referred to as CA). CA technology refers to a technology for not using only one carrier for communication between a UE and a base station (e.g., an eNB or gNB), but instead using a primary component carrier and one or more secondary component carriers to increase the transmission throughput by the number of secondary component carriers. Meanwhile, in LTE and NR systems, a cell in a base station using a primary component carrier may be referred to as a primary cell or PCell, and a cell in a base station using a secondary component carrier may be referred to as a secondary cell or SCell.

[0065] Figure 3A PDU set configuration based on an application data unit (ADU) according to an embodiment of the present disclosure is shown.

[0066] refer to Figure 3 , various services can be distinguished by ADU, which is an information unit that can be distinguished at the application level. Depending on the embodiment, the ADU can be a photo or image, a frame of video data, or a unit of audio data. The ADU can be distinguished based on the PDU set 310, and the PDU set 310 can be divided into one or more PDUs 301, 302, 303, 304, 305, and 306 according to size and then transmitted.

[0067] For example, in the case where the Moving Picture Experts Group (MPEG) standard video compression technology is used in conjunction with a video service, the PDU set may be configured by one of the following: 1) a combination 330 of multiple PDUs corresponding to one intra (I) frame, 2) a combination 340 of multiple PDUs corresponding to one bidirectional (B) frame, and 3) a combination 350 of multiple PDUs corresponding to one predicted (P) frame.

[0068] According to an embodiment of the present disclosure, an I frame 320 is an independent frame and can represent a complete photo or picture 321 regardless of whether other frames exist. P frames and B frames 322 are frames that represent information about changes in the previous I frame 320. If the I frame 320 is not received normally, it may be difficult to normally represent the photo or picture 323 intended to be expressed by the P frame and B frame 322. In addition, the B frame is located between the I frame and the P frame and is stored as data that refers to the two frames to estimate the movement between the two frames. Therefore, only when the previous I frame and the following P frame are received normally can the photo or picture expressed by the B frame be normally expressed.

[0069] In the embodiments of the present disclosure, for ease of description, the configuration of the PDU set may be described with reference to an exemplary case in which the MPEG standard video compression technology is used in conjunction with a video service. However, the content of the present disclosure is not limited to the configuration of the PDU set related to the video service and can be applied to all PDU set configurations configured by the general ADU unit.

[0070] According to embodiments of the present disclosure, an XR service flow for a specific extended reality (XR) service can be configured by combining multiple pieces of data (e.g., PDUs, PDU sets, etc.) with different quality of service (QoS) requirements. Taking the aforementioned MPEG as an example, when transmitting MPEG-encoded video services for a specific XR service, an XR service flow can be configured using various PDU sets with different QoS requirements (e.g., latency, reliability, etc.) corresponding to I-frames, B-frames, and P-frames.

[0071] According to embodiments of the present disclosure, to service XR service flows configured with multiple pieces of data having various QoS requirements, the network can map the XR service flow to one or more QoS flows. As described above, when using one or more QoS flows to service a specific XR service flow, the multiple pieces of data constituting the same XR service flow can be transmitted via different QoS flows, depending on the QoS requirements. Different QoS flows can be mapped to different DRBs or the same DRB. Furthermore, PDU sets transmitted via the same QoS flow can have different importance levels. For example, in the case of video services, PDU sets corresponding to I-frames may have a higher importance level than PDU sets corresponding to B-frames or P-frames. The importance level of each PDU set can be represented, for example, by a number ranging from 0 to 8, {true, false}, {0, 1}, etc. For downlink data, the user plane function (UPF) can include importance level information in the General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) header, and the base station can take the importance level into account when transmitting PDU sets via the downlink. In addition, in the case of an uplink, the application layer of the UE may transmit the importance level information to a lower layer (e.g., SDAP, PDCP, RLC, or MAC layer) through an internal interface of the UE, or the SDAP / PDCP / RLC header, etc. may include the importance level information. For example, through the RLC header information of the RLC PDU, the MAC layer may recognize the importance level of the data included in the RLC PDU, and the importance level of the data may be ultimately determined by the importance level of the PDU set consisting of the data.

[0072] Although the following description of the embodiments of the present disclosure will assume that the smaller the importance level value of a PDU set, the higher the importance level, the same scheme can also be applied to the case where the larger the importance level value of a PDU set, the higher the importance level. However, in this case, only the method of comparing the importance level value of each PDU set to determine the relative importance level is changed.

[0073] Figure 4 A protocol layer structure for serving PDU sets with different importance levels according to an embodiment of the present disclosure is shown.

[0074] refer to Figure 4 ,XR service flows can be configured by PDU sets with different importance levels. In order to serve PDU sets with different importance levels, various protocol layer structures can be considered, as follows:

[0075] Structure 1 401: When PDU sets 402 and 403 with different importance levels have different QoS requirements, PDU sets 402 and 403 can be sent via different QoS flows 404 and 405. The QoS flows can be sent via different DRBs 406 and 407 to meet the different QoS requirements. Furthermore, the DRBs can be mapped to different LCHs 408 and 409 to further meet the different QoS requirements. According to current specifications, each LCH can have different priorities. Furthermore, the priority of each LCH can be used for scheduling-related operations performed in the MAC layer (e.g., LCP and BSR triggering operations). Therefore, PDU sets sent via different LCHs can ultimately be scheduled with different priorities. In the above structure 401, PDU sets 402 and 403 with different importance levels are transmitted via different QoS flows, different DRBs, and different LCHs, and can therefore be scheduled with different priorities.

[0076] However, in the case of using the above-mentioned structure 1 401, in-order delivery may not be guaranteed for PDU sets constituting the same XR service flow. For reference, in-order delivery can be guaranteed for packets sent through the same DRB. To this end, the transmitter PDCP layer of each DRB can continuously attach PDCP sequence numbers (SNs) to data segments transmitted from the upper layer and can send them while including the PDCP sequence numbers in the PDCP header. The receiver PDCP layer can continuously transmit data to the upper layer with reference to the PDCP SN. In the above-mentioned structure 401 in which the PDU sets constituting the XR service flow are mapped to different QoS flows according to the importance level and are re-sent through different DRBs respectively, in-order delivery cannot be guaranteed because the order may be changed between the PDU sets during data transmission.

[0077] - Structure 2 410: In the case where PDU sets 411 and 412 with different importance levels have the same QoS requirements, the PDU sets 411 and 412 can be sent through the same QoS flow 413. The QoS flow can be mapped to one DRB 415. In this case, the in-order delivery function provided by the PDCP layer of the DRB 415 can guarantee the in-order delivery of the PDU sets constituting the XR service flow.

[0078] DRBs can be mapped to different LCHs 417 and 419 so that PDU sets 411 and 412 with different importance levels are processed differently according to the importance levels. According to the current specification, each LCH can have different priorities, and the priority of each LCH can be used for scheduling-related operations (e.g., LCP and BSR triggering operations) performed at the MAC layer. Therefore, PDU sets sent through different LCHs according to the importance levels can ultimately be scheduled with different priorities. In the above structure 410, PDU sets 411 and 412 with different importance levels are transmitted through different LCHs and can therefore be scheduled with different priorities. In order to send PDU sets through different LCHs according to the importance levels in the same DRB as in the above scheme, it is necessary to improve the DRB configuration scheme. In the following embodiments 1i, 1j, and 1k of the present disclosure, the method for supporting the above structure 2 410 will be described in detail.

[0079] Using the above structure 2 410 requires that the base station already have information about the importance level of the PDU sets to be transmitted over the QoS flow when configuring the DRB mapped to a specific QoS flow for the UE. In other words, the core network (CN) must be able to inform the base station in advance of the importance level of the PDU sets to be transmitted over each QoS flow. Otherwise, the base station will not know the importance level of the PDU sets to be transmitted over the QoS flow when mapping the DRB for the UE. Therefore, it is necessary to configure separate LCHs for all possible importance level values ​​(e.g., values ​​from 0 to 8) and map them to DRBs.

[0080] - Structure 3 420: In the case where PDU sets 421 and 422 with different importance levels have the same QoS requirements, the PDU sets 421 and 422 can be sent through the same QoS flow 423. The QoS flow 423 can be mapped to one DRB 425. In this case, the in-order delivery function provided by the PDCP layer of the DRB can guarantee the in-order delivery of the PDU sets constituting the XR service flow.

[0081] The DRB 425 may again be mapped to an LCH 427. In the case where the CN cannot inform the base station in advance of the importance level of the PDU set to be sent through the QoS flow, the base station may configure the LCH with reference only to the QoS requirements of the QoS flow mapped to the DRB, and may map the LCH to the DRB.

[0082] However, in this case, PDU sets with different importance levels transmitted through the QoS flow are mapped to the same LCH and are therefore processed with the same priority at the MAC layer. For reference, according to the current specification, scheduling-related operations (e.g., LCP and BSR triggering operations) performed at the MAC layer are performed based on the priority of the LCH, and therefore data transmitted through the same LCH is served with the same priority at the MAC layer. Therefore, in the case of using the above-mentioned structure 3 420, according to the current MAC standard operation, PDU sets with different importance levels may not be served differently. Therefore, by Figure 5 、 1 The present disclosure proposes a method for improving scheduling-related operations (e.g., LCP and BSR triggering operations) performed at the MAC layer, such that PDU sets with different importance levels can be processed with different priorities at the MAC layer. More specifically, the present disclosure proposes a method in which, in MAC layer operations (LCP and BSR triggering operations), the importance level of the RLC PDU (in other words, the importance level of the PDU set configured by the data included in the RLC PDU) can be considered together with the priority of the LCH.

[0083] Figure 5 An example of a BSR triggering operation based on logical channel (LCH) priority according to an embodiment of the present disclosure is shown.

[0084] refer to Figure 5 When uplink (UL) data to be transmitted arrives in the buffer, the UE's MAC layer can trigger the transmission of a regular buffer status report (BSR) to notify the base station of the presence of UL data. The BSR transmitted by the UE may include the amount of UL data currently buffered according to a logical channel group (LCG), which is a group of logical channels. Upon receiving the BSR from the UE, the base station can allocate an UL grant (or radio resources required for uplink transmission) to the UE based on the information included in the BSR. To reduce the load incurred by triggering a regular BSR each time new UL data arrives in the buffer, the UE's MAC layer can determine whether to trigger a BSR based on the priority of the logical channel for which the UL data has arrived. More specifically, the MAC layer can trigger a regular BSR if at least one of the following two conditions is met when new UL data arrives.

[0085] - Condition 1: UL data arrives at a logical channel with a higher priority than any logical channel that already has UL data to send.

[0086] For example, in the case where new UL data 511 has arrived on LCH A (or LCH A's buffer) as in Example 1 510, the UE may trigger a regular BSR because LCH A (with priority 1) has a higher priority than LCH B (with priority 2) and LCH D (with priority 3) which already have UL data 512 and 514 that can be sent.

[0087] - Condition 2: The LCG including the logical channel for which UL data has arrived has no other logical channel that already has UL data that can be transmitted.

[0088] For example, in the case where new UL data 521 has arrived at LCH B (or the buffer of LCH B) as in Example 2 520, the UE may trigger a regular BSR because LCG 1 522, to which LCH B belongs, has no other logical channels with transmittable UL data (in other words, because LCH A has no transmittable UL data). In this case, even if another LCG 2 524, to which LCH B does not belong, includes LCH C with transmittable UL data 523 and the priority of LCH C (having priority 1) is higher than the priority of LCH B (having priority 2), the UE may trigger a regular BSR to indicate the presence of the new UL data arriving at LCG 1.

[0089] Through the operation corresponding to condition 1 of the two conditions, when UL data has arrived at a logical channel with a high priority, the UE can request the base station to provide UL grant resources for transmitting UL data. In this case, the priority of the newly arrived UL data is determined only by the priority of the logical channel on which the UL data has arrived. However, as mentioned above about Figure 4 As described in structure 3 420 in Example 3 , the PDU sets that make up the XR service flow can have different importance levels and can be mapped to the same QoS flow, the same DRB, and the same LCH and then transmitted. In this case, PDU sets with different importance levels can be mapped to the same LCH. Since the normal BSR triggering conditions are designed considering only the priority of the LCH, even if the priority of the UL data that has arrived at a specific LCH is higher than the priority of the UL data that is already waiting for transmission, a normal BSR cannot be triggered. For example, as in Example 3 530, UL data segments with different importance levels can be mapped to LCH A and then arrive. In the event that a new piece of UL data 531 with an importance level of 2 arrives, even if the UL data has a higher importance level than other UL data 532 with an importance level of 3 (which is already waiting for transmission in LCH A), a normal BSR cannot be triggered because the above conditions 1 and 2 are not met.

[0090] Now, we will describe in more detail whether condition 2 is satisfied: LCG 1, to which LCH A belongs, already has LCH B, which has transmittable UL data 533, and newly arrived UL data 531 on LCH A cannot trigger a regular BSR. We will also describe whether condition 1 is satisfied: among the priorities of the logical channels (LCH A, LCH B, and LCH D) that already have transmittable UL data 532, 533, and 536, the highest priority is 1, and the priority of LCH A, to which the newly arrived UL data belongs, is also 1 (which is not high). As a result, the newly arrived UL data 531 cannot trigger a regular BSR. Therefore, the above two conditions, which only consider the priorities of the logical channels, cannot guarantee that multiple pieces of UL data with different importance levels are handled differently according to their importance levels.

[0091] Therefore, the present disclosure proposes a method for improving the conditions for the MAC layer to trigger a conventional BSR, so that different PDU sets constituting an XR service flow can be processed differently according to importance levels even if mapped to the same LCH.

[0092] For reference, UL data on the MAC layer may refer to an RLC PDU (or a MAC service data unit (SDU)). Furthermore, as used herein, the importance level of UL data may refer to the importance level of a PDU set (RLC PDU) configured by the UL data, and the importance level may be determined by the UE's application layer and then transmitted to the MAC layer. Furthermore, although it is assumed that the smaller the importance level value, the higher the importance level, for the convenience of describing the embodiments of the present disclosure, the methods described in the embodiments of the present disclosure may also be applied to situations where the larger the importance level value, the higher the importance level, or to situations where the importance level value is in the format of {true, false}, for example, such that a "true" value indicates a higher importance level than a "false" value.

[0093] Figure 6 An example of an importance-based BSR triggering operation of a PDU set according to an embodiment of the present disclosure is shown.

[0094] refer to Figure 6 When UL data to be transmitted arrives, the UE's MAC layer can trigger the transmission of a regular BSR to notify the base station of the presence of the UL data. The triggering condition for sending a regular BSR can consider not only the priority of the LCH on which the UL data arrived, but also the importance of the UL data. Two methods are possible for this purpose.

[0095] - Method 1 610: If the newly arrived UL data has a higher importance level than any UL data that may have been sent (and which is already pending for transmission), the UE's MAC layer may trigger a regular BSR. In this regard, this method may be applied only when the configuration information for the UE's MAC operation (e.g., MAC-CellGroupConfig) includes an indicator (e.g., BSRbasedOnImportance) indicating that BSR triggering is to be performed based on the importance level of a PDU set. This operation may be as shown in Table 1 below.

[0096] [Table 1]

[0097]

[0098] More specifically, when new UL data 612 arrives at LCH A as in Example 1 611, the UL data (importance 1) has a higher importance level than any UL data strips 613, 614, 615, and 616 that may have already been sent (and are already pending for transmission). Therefore, the UE's MAC layer can trigger a regular BSR. On the other hand, the UL data that may have already been sent (and is already pending for transmission) includes data 618, whose importance level is higher than or equal to the newly arrived UL importance level 619 as in Example 2, and the UE's MAC layer cannot trigger a regular BSR.

[0099] According to the above-described method 1 610, the importance level of the UL data is considered separately, regardless of the priority of the logical channel related to the normal BSR triggering condition. Therefore, if the importance level of the newly arrived UL data is higher than the importance level of the already waiting UL data, the UE can trigger a normal BSR, and the base station can allocate a new UL grant (uplink transmission resource) to the UE based on the BSR by considering the data with a high importance level.

[0100] Method 2 620: When UL data has arrived at the logical channel with the highest priority among any logical channels on which UL data can be transmitted and has a higher importance level than other UL data segments belonging to logical channels with the corresponding priority, the UE's MAC layer may trigger a regular BSR. Furthermore, this method may only be applied if the UE's MAC operation configuration (e.g., MAC-CellGroupConfig) includes an indicator (e.g., BSRbasedOnImportance) indicating that BSR triggering is to be performed based on the importance level of a PDU set. This operation may be as shown in Table 2 below.

[0101] [Table 2]

[0102]

[0103] More specifically, a case will be described in which new UL data 622 has arrived at LCH A as in Example 1 621. In Example 1 621, in a case in which the UL data 622 has arrived at a logical channel with the highest priority (LCH A with priority 1 and LCH C with priority 1) among any logical channels (LCH A, LCH B, LCHC, and LCH D) that already have transmittable UL data, and in a case in which the newly arrived UL data 622 (with importance 1) has a higher importance level than other UL data 623 (with importance 3) and 624 (with importance 2) belonging to logical channels with corresponding priorities (LCH A and LCH C), the MAC layer of the UE may trigger a normal BSR.

[0104] On the other hand, in the case where new UL data 625 has arrived at LCH B as in Example 2 625, and in the case where LCH B with priority 2 where the UL data 625 has arrived has a lower priority (priority 2) than the highest priority (priority 1) among the priorities of any logical channels (LCHA, LCH B, LCH C, and LCH D) that already have UL data transmittable, the MAC layer of the UE cannot trigger a regular BSR.

[0105] Furthermore, in the case where new UL data 626 has arrived at LCH A as in Example 3 628, the logical channel on which the UL data 626 has arrived (LCH A with priority 1) has the highest priority value among any logical channels (LCH A, LCH B, LCH C, and LCH D) that already have transmittable UL data. However, the newly arrived UL data 626 (with importance 2) has the same importance level as other UL data 627 (with importance 2) belonging to logical channels with corresponding priorities (LCH A and LCH C), and accordingly, the MAC layer of the UE cannot trigger a regular BSR.

[0106] According to the above-described method 2 620, the priority of the logical channel is first considered, as in the previous method incorporating a regular BSR triggering condition, and the importance of the UL data is again considered separately within the logical channel with the highest priority. Therefore, if the importance level of the newly arrived UL data is higher than the importance level of the already pending UL data, the UE can trigger a regular BSR, and the base station can allocate a new UL grant (uplink transmission resource) to the UE based on the BSR, taking into account the data with the higher importance level.

[0107] For reference, UL data on the MAC layer may refer to an RLC PDU (or MAC SDU). Furthermore, the importance level of UL data may refer to the importance level of a PDU set (RLC PDU) configured by the UL data, and the importance level may be determined by the UE's application layer and then transmitted to the MAC layer. Furthermore, although it is assumed that the smaller the importance level value, the higher the importance level, for the convenience of describing the embodiments of the present disclosure, the methods described in the embodiments of the present disclosure may also be applied to situations where the larger the importance level value, the higher the importance level, or to situations where the importance level value is in the format of {true, false}, for example, such that a "true" value indicates a higher importance level than a "false" value.

[0108] Figure 7 and Figure 8 An example of a logical channel priority (LCP) operation according to an embodiment of the present disclosure is shown, where the priority of the LCH and the importance level of the PDU set are considered together.

[0109] refer to Figure 7 and Figure 8 In the case where the UE has a UL grant allocated by the base station, the UE may calculate the size of uplink data that can be transmitted using the UL grant (transport block (TB) size or MAC PDU size) 702. Thereafter, the MAC layer of the UE may perform a logical channel priority (LCP) operation to determine in what order the MAC PDU of the calculated size will be filled with the segments of UL data 703, 704, and 705 waiting to be transmitted in the corresponding LCH (in other words, to determine in what order uplink transmission resources will be allocated to the corresponding logical channels). More specifically, the LCP operation performed on the MAC layer may be performed in one of the following schemes:

[0110] -Scheme 0 701: The MAC layer may perform LCP by considering only the priority of the logical channel. The LCP operation considering only the logical channel may be as shown in Table 3 below:

[0111] [Table 3]

[0112]

[0113] In the above operation, the Bj value is calculated for each LCH in a step before performing LCP, and the Bj value can be calculated based on the prioritized bit rate (PBR) value configured for each LCH. The Bj value can ultimately be understood as the size of the uplink transmission resources expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0114] The process of performing LCP in the above-described method can be described in more detail with reference to Example 701. In this example, it is assumed that LCH A, LCH B, and LCH C are configured as logical channels that should undergo LCP in a step prior to performing LCP. LCH A is a logical channel to which XR traffic is not mapped (in other words, a logical channel to which a PDU set with a high importance level is not mapped), and UL data (RLC PDUs or MAC SDUs) not assigned a specific importance level value can only be present in LCHA. The UE's MAC layer can allocate uplink transmission resources to logical channels (LCH A, LCH B, and LCH C) whose calculated Bj values ​​are greater than 0. For reference, although the Bj values ​​(Bj_a, Bj_b, Bj_c) are assumed to be the same for each LCH in this embodiment, in practice, the corresponding values ​​may be calculated differently for each LCH. Transmission resource allocation can be performed in descending order of priority for each LCH. If LCHs have the same priority, resource allocation priority can be determined based on UE implementation. In this example, LCH A and LCH B have the same priority value of 1, but resources may be allocated first to LCH A, and then resources may be allocated in the order of LCH B and LCH C according to the order of LCHs configured by the UE implementation. More specifically, resources corresponding to Bj_a may be allocated to the segment of UL data 703 that is first on standby in LCH A. Thereafter, resources may be allocated to the segment of UL data 704 that is already on standby in LCH B because there is more free space in the MAC PDU. However, in this example, the LCP operation ends because no resources remain after resources are allocated to UL data with importance 3 among the multiple pieces of UL data 704 that are already on standby in LCH B (in other words, after the UL data with importance 3 is included in the MAC PDU).

[0115] If LCP is performed by considering only the priorities of logical channels as in the above-described example 701, multiple pieces of UL data with relatively high importance levels (in other words, UL data belonging to LCH B and LCH C and having relatively high importance levels (2 or 3)) may be ranked low in the LCP process and thus experience high delay. Therefore, the present disclosure proposes an LCP scheme in which not only the priorities of logical channels but also the importance levels of UL data can be considered together, as follows:

[0116] - Option 1 710: The MAC layer performs LCP while prioritizing the priority of logical channels. For logical channels with the same priority, the importance level of the UL data already on standby in each logical channel may also be considered. Furthermore, the UE's MAC layer may only apply the above method if the UE's MAC layer is configured to consider the importance level of UL data in scheduling-related operations (more specifically, if the "Scheduling Based on Importance" indicator is configured for the UE via RRC configuration). LCP operations may be as shown in Table 4 below.

[0117] [Table 4]

[0118]

[0119] In the above operation, the Bj value is calculated for each LCH in a step before performing LCP, and the Bj value can be calculated based on the prioritized bit rate (PBR) value configured for each LCH. The Bj value can ultimately be understood as the size of the uplink transmission resources expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0120] The process of performing LCP in the above-described method can be described in more detail with reference to Example 710. In this example, it is assumed that LCH A, LCH B, and LCH C are configured as logical channels that should undergo LCP in a step prior to performing LCP. LCH A is a logical channel to which XR services are not mapped (in other words, a logical channel to which a PDU set with a high importance level is not mapped), and UL data (RLC PDU or MAC SDU) to which no specific importance level value is assigned can exist only in LCHA. The MAC layer of the UE can allocate uplink transmission resources to the logical channels (LCH A, LCH B, and LCH C) for which the calculated Bj values ​​are greater than 0. For reference, although the Bj values ​​(Bj_a, Bj_b, Bj_c) of each LCH are assumed to be the same in this embodiment, in practice, the corresponding values ​​can be calculated differently for each LCH.

[0121] Transmission resource allocation can be performed in descending order of priority of each LCH, and in the case where the LCHs have the same priority, transmission resources can be allocated in descending order of importance level of each LCH. For reference, as in this example 710, the importance level of each LCH can be determined based on the importance level of UL data waiting in the corresponding LCH. For example, the importance level of a specific LCH can be determined as the importance level value of UL data with the highest importance level among multiple UL data waiting in the corresponding LCH. For example, in this example 710, the importance level of LCH B can be determined as 2, and the importance level of LCH C can be determined as 1. In addition, in the case where the importance level value of the PDU set to be transmitted through the corresponding LCH is pre-configured for each LCH through RRC signaling, the importance level value indicating the highest importance level among them can be determined as the importance level value of the corresponding LCH.

[0122] On the other hand, in the case of an LCH such as LCH A that does not include important UL data (or in the case where the DRB to which the LCHA is connected is not configured to handle the importance level of the PDU set), the specification may require that the LCH have the lowest importance level value or any importance level value. Alternatively, the importance level value of an LCH that does not include important UL data (such as LCH A) can be individually configured for the UE through RRC signaling. In this example, it is assumed that LCH A, which does not include important UL data, has the lowest importance level, and in the case of LCH B and LCH C, which include important UL data, the importance level value of the LCH is determined by the importance level value of the highest UL data among multiple pieces of UL data waiting in the LCH. That is, in this embodiment, the importance level value of LCH B is 2, and the importance level value of LCH C is 1.

[0123] In this example 710, LCH A and LCH B have the same priority value of 1, but LCH B has an importance level of 2, and LCH A has the lowest importance level. Therefore, resources can be allocated to LCH B first in descending order of the LCH importance levels, and resources can be allocated to LCH A, and then to LCH C. More specifically, resources corresponding to B_B can be allocated first to the multiple pieces of UL data waiting in LCH B 712. After that, the MAC PDU still has free space, and therefore resources can be allocated to the multiple pieces of UL data waiting in LCH A. However, in this example, the LCP operation ends because no resources remain after the resources are first allocated to the multiple pieces of UL data waiting in LCH A 711.

[0124] In the case where the logical channels have the same priority values ​​as in the above-described example 710, and LCP is performed by additionally considering the importance level value of each logical channel, a segment of UL data having a relatively high importance level in a logical channel having the same priority value (in other words, a segment of UL data belonging to LCH B and having a relatively high importance level of 2 or 3) may be prioritized in the LCP process. However, resources are allocated later to the segment of UL data 705 belonging to LCH C having a lower priority, resulting in a high delay. Therefore, the present disclosure further proposes an LCP scheme in which the importance level of the UL data included in each LCH may be considered first before comparing the priorities of the logical channels.

[0125] Solution 2-1 720: The MAC layer may prioritize allocating resources to the LCH containing important UL data, and then allocate the remaining resources as described in Solution 1. The UE's MAC layer may apply the above method only if it is configured to consider the importance of UL data in scheduling-related operations (more specifically, if the "SchedulingBasedOnImportance" indicator is configured for the UE via RRC configuration). The LCP operation may be as shown in Table 5 below.

[0126] [Table 5]

[0127]

[0128] In the above operation, the Bj value is calculated for each LCH in a step before performing LCP, and the Bj value can be calculated based on the prioritized bit rate (PBR) value configured for each LCH. The Bj value can ultimately be understood as the size of the uplink transmission resources expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0129] The process of performing LCP in the above-described method 2-1 can be described in more detail with reference to Example 720. In this example, it is assumed that LCH A, LCH B, and LCH C are configured as logical channels that should undergo LCP in a step prior to performing LCP. LCH A is a logical channel to which XR traffic is not mapped (in other words, a logical channel to which a PDU set with importance is not mapped), and UL data (RLC PDU or MAC SDU) to which a specific importance level value is not assigned can exist only in LCH A. The MAC layer of the UE can allocate uplink transmission resources to the logical channels (LCH A, LCH B, and LCH C) for which the calculated Bj value is greater than 0.

[0130] Transmission resource allocation may be preferentially performed with respect to LCHs containing important UL data, and resources may be allocated in descending order of priority of each LCH. For LCHs having the same priority, transmission resources may be allocated in descending order of importance of each LCH. For reference, the above description in conjunction with method 1 710 may be applied identically or similarly to the scheme for determining the importance level of each LCH.

[0131] In this example 720, resource allocation may be preferentially performed on LCH B and LCH C, which include UL data having importance, as in step 1 of Table 5 above. In this regard, LCH B (having priority 1) has a higher priority than LCH C (having priority 2), and accordingly, resource allocation may be performed first on LCH B and then on LCH C in descending order of priority of the LCHs. Specifically, resources corresponding to Bj_b may be first allocated to the plurality of pieces of UL data 722 waiting in LCH B. Thereafter, the MAC PDU still has free space, and thus resources may be allocated to the plurality of pieces of UL data 723 waiting in LCH C (724). In addition, the Bj values ​​(Bj_a and Bj_c) of LCH B and LCH C may be updated to 0.

[0132] Thereafter, resource allocation may be performed in the same manner as described above in connection with Scheme 1 710 in step 2 of Table 5 above. First, LCH A is the only LCH having a Bj value greater than 0, and thus resource allocation may be performed with respect to LCH A (725). Thereafter, the Bj value (Bj_a) of LCH A may be updated to 0.

[0133] Thereafter, in step 3 of Table 5 above, resource allocation may be performed in descending order of priority of the LCHs until the remaining UL grant resources are exhausted. In this example 720, a segment of UL data (e.g., RLC PDU or MAC SDU) is retained in each of LCH A and LCH C. LCH A has a higher priority (1) than the priority (2) of LCH C, and resources are therefore allocated first to LCH A (726). Thereafter, the entire MAC PDU is full (i.e., all available UL grants have been exhausted), and transmission of the UL data with importance 2 retained in LCH C may therefore be delayed.

[0134] Solution 2-2 730: Resources may be preferentially allocated to LCHs with UL data whose importance level is above a threshold configured by the network (e.g., ThreImportance). The remaining resources may then be allocated in the same manner as in Solution 1 above. Furthermore, the UE's MAC layer may only apply the above method if it is configured to consider the importance level of UL data in scheduling-related operations (more specifically, if the "SchedulingBasedOnImportance" indicator is configured for the UE via RRC configuration). Furthermore, the threshold (e.g., ThreImportance) may be set for the UE via RRC signaling. LCP operations may be as shown in Table 6 below.

[0135] [Table 6]

[0136]

[0137] In the above operation, the Bj value is calculated for each LCH in a step before performing LCP, and the Bj value can be calculated based on the prioritized bit rate (PBR) value configured for each LCH. The Bj value can ultimately be understood as the size of the uplink transmission resources expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0138] The process of performing LCP in the above method can be described in more detail with reference to Example 730. In this example, it is assumed that LCH A, LCH B, and LCH C are configured as logical channels that should undergo LCP in a step before performing LCP. LCH A is a logical channel to which XR traffic is not mapped (in other words, a logical channel to which a PDU set with importance is not mapped), and UL data (RLC PDU or MAC SDU) to which no specific importance level value is assigned can exist only in LCH A. The MAC layer of the UE can allocate uplink transmission resources to the logical channels (LCH A, LCH B, and LCH C) whose calculated Bj values ​​are greater than 0.

[0139] Transmission resource allocation may be preferentially performed with respect to LCHs containing UL data having an importance level higher than a specific threshold, and resources may be allocated in descending order of priority of each LCH. For LCHs having the same priority, transmission resources may be allocated in descending order of importance of each LCH. For reference, the method for determining the importance level of each LCH in this example is the same as that described above in conjunction with method 1 710.

[0140] In this example 730, resource allocation may be preferentially performed with respect to LCH B (importance 2) and LCH C (importance 1), which include UL data having an importance level higher than a specific threshold 732, as configured as 3 in step 1 of Table 6 above. In this regard, LCH B (having priority 1) has a higher priority than LCH C (having priority 2), and accordingly, resource allocation may be performed first with respect to LCH B and then with respect to LCH C in descending order of priority of the LCHs. Specifically, resources corresponding to Bj_b may be first allocated to the plurality of pieces of UL data 734 waiting in LCH B. Thereafter, the MAC PDU still has free space, and thus resources may be allocated to the plurality of pieces of UL data 735 waiting in LCH C (736). In addition, the Bj values ​​(Bj_a and Bj_c) of LCH B and LCH C may be updated to 0.

[0141] Thereafter, resource allocation may be performed in the same scheme as described above in conjunction with Scheme 1 710 in step 2 of Table 6 above. First, LCH A is the only LCH having a Bj value greater than 0, and thus resource allocation may be performed with respect to LCH A (737). Thereafter, the Bj value (Bj_a) of LCH A may be updated to 0.

[0142] Thereafter, in step 3 of Table 6 above, resource allocation may be performed in descending order of priority of the LCHs until the remaining UL grant resources are exhausted. In this example 730, a segment of UL data (e.g., RLC PDU or MAC SDU) is retained in each of LCH A and LCH C. LCH A has a higher priority (1) than the priority (2) of LCH C, and resources are therefore allocated first to LCH A (738). Thereafter, the entire MAC PDU is full (i.e., all available UL grants have been exhausted), and transmission of the UL data with importance 2 retained in LCH C may therefore be delayed.

[0143] On the other hand, when the threImportance value is set to 2 as configured in Example 741, resource allocation may be preferentially performed only for LCH C (importance is 1) including UL data having an importance level higher than the importance level. Specifically, resources corresponding to Bj_c may be allocated to the segment of UL data 745 waiting in LCH C (746), and then the Bj_c value may be updated to 0.

[0144] Thereafter, resource allocation may be performed in the same scheme as described above in conjunction with Scheme 1 710 in step 2 of Table 6 above. First, LCH A and LCH B are the remaining LCHs having Bj values ​​greater than 0, and both LCHs have the same priority. Therefore, resource allocation may be performed in descending order of importance level of each LCH. In this case, the importance level (2) of LCH B is higher than the importance level (lowest) of LCH A. Therefore, resources corresponding to Bj_c may be allocated to LCH B, and resources corresponding to Bj_a may then be allocated to LCH A (747). Thereafter, the Bj values ​​(Bj_a and Bj_b) of LCH A and LCH B may be updated to 0.

[0145] Thereafter, in step 3 of Table 6 above, resource allocation may be performed in descending order of priority of the LCHs until the remaining UL grant resources are exhausted. In this example 740, a segment of UL data (e.g., RLC PDU or MAC SDU) is retained in each of LCH A and LCH C. LCH A has a higher priority (1) than the priority (2) of LCH C, and resources are therefore allocated first to LCH A (748). Thereafter, the entire MAC PDU is full (i.e., all available UL grants have been exhausted), and transmission of the UL data with importance 2 retained in LCH C may therefore be delayed.

[0146] - Option 2-3 750: The MAC layer prioritizes allocating resources to LCHs containing important UL data, and performs resource allocation in descending order of importance, rather than LCH priority. Thereafter, the remaining resources may be allocated in the same manner as in Option 1 above. Furthermore, the UE's MAC layer may apply the above method only if the method is configured to consider the importance of UL data in scheduling-related operations (more specifically, if the "SchedulingBasedOnImportance" indicator is configured for the UE via RRC configuration). LCP operations may be as shown in Table 7 below.

[0147] [Table 7]

[0148]

[0149] In the above operation, the Bj value is calculated for each LCH in a step before performing LCP, and the Bj value can be calculated based on the prioritized bit rate (PBR) value configured for each LCH. The Bj value can ultimately be understood as the size of the uplink transmission resources expected to be allocated to each LCH (in other words, the size of the MAC SDU expected to be provided to each LCH).

[0150] The process of performing LCP in the above method can be described in more detail with reference to Example 750. In this example, it is assumed that LCH A, LCH B, and LCH C are configured as logical channels that should undergo LCP in a step prior to performing LCP. LCH A is a logical channel to which XR traffic is not mapped (in other words, a logical channel to which a PDU set with importance is not mapped), and UL data (RLC PDU or MAC SDU) to which no specific importance level value is assigned can exist only in LCH A. The MAC layer of the UE can allocate uplink transmission resources to the logical channels (LCH A, LCH B, and LCH C) for which the calculated Bj value is greater than 0.

[0151] Transmission resource allocation may be performed preferentially with respect to LCHs containing important UL data, and resources may be allocated in descending order of importance of each LCH. For LCHs of equal importance, transmission resources may be allocated in descending order of priority of each LCH. For reference, the method for determining the importance level of each LCH in this example is the same as that described above in conjunction with method 1 710.

[0152] In this example, resource allocation may be preferentially performed on LCH B and LCH C, which include UL data having importance as in step 1 of Table 7 above. In this regard, LCH C (importance is 1) has a higher importance level than LCH B (importance is 2), and accordingly, resource allocation may be performed first for LCH C and then for LCH B in descending order of importance level. Specifically, resources corresponding to BLC may be first allocated to the plurality of pieces of UL data 753 waiting in LCH C. Thereafter, the MAC PDU still has free space, and thus resources may be allocated to the plurality of pieces of UL data 752 waiting in LCH B (754). In addition, the Bj values ​​(Bj_a and Bj_c) of LCH B and LCH C may be updated to 0.

[0153] Thereafter, resource allocation may be performed in the same scheme as described above in conjunction with Scheme 1 710 in step 2 of Table 7 above. First, LCH A is the only LCH with a Bj value greater than 0, and thus resource allocation may be performed with respect to LCH A (755). Thereafter, the Bj value (Bj_a) of LCH A may be updated to 0.

[0154] Thereafter, in step 3 of Table 7 above, resource allocation may be performed in descending order of priority of the LCHs until the remaining UL grant resources are exhausted. In this example 750, a segment of UL data (e.g., RLC PDU or MAC SDU) is retained in each of LCH A and LCH C. LCH A has a higher priority (1) than the priority (2) of LCH C, and resources are therefore first allocated to LCH A (756). Thereafter, the entire MAC PDU is full (i.e., all available UL grants have been allocated), and thus the transmission of the UL data with importance 2 retained in LCH C may be delayed.

[0155] Figure 9 A split bearer configuration according to an embodiment of the present disclosure is shown.

[0156] refer to Figure 9 , the SDAP 910 layer can map each QoS flow 940 to a specific DRB. In the presence of one or more QoS flows, multiple QoS flows can be mapped to one DRB. In the present disclosure, a split bearer is defined as a DRB 950 that sends data by using two or more RLC bearers (or RLC entities) 930, 931 and 932. In a dual connectivity scenario, RLC entities configured for different cell groups (e.g., primary cell group (MCG) secondary cell group (SCG)) can be mapped together to the same split bearer. In addition, each RLC entity can be mapped again to each logical channel. When sending data through a split bearer, multiple RLC bearers can be utilized in the following two methods:

[0157] 1) Replication operation: To increase reliability and security during packet transmission, the PDCP layer repeatedly sends the same packet through different RLC entities.

[0158] 2) Split Operation: To increase data throughput during packet transmission, the PDCP layer sends the packet through one of the different RLC entities.

[0159] When a UE transmits UL data via a split bearer, the PDCP entity 920 can interwork with multiple RLC entities to perform duplication and split operations based on the RRC configuration. To this end, a primary path (or primary RLC entity) 930 can be configured for each split bearer. When neither duplication nor split operations are activated, packets can be sent via the primary path 930. For split operations, a split secondary path (or split secondary RLC entity) 931 and a ul-DataSplitThreshold can be configured for each split bearer. If the split operation conditions for the split bearer are met (e.g., duplication is not activated for the corresponding split bearer and the total amount of data pending in the PDCP and RLC layers to be sent via the primary and split secondary RLC entities is greater than or equal to the ul-DataSplitThreshold), the PDCP layer can deliver packets (PDCP PDUs) via either the primary RLC entity 930 or the split secondary RLC entity 931. This split operation is only permitted when RLC entities configured for different cell groups are mapped to split bearers in a dual connectivity scenario. In this case, the separated secondary RLC entity may be configured only as an RLC entity configured in a different cell group than the cell group in which the primary RLC entity is configured. For the duplication operation, one or more secondary paths (or secondary RLC entities) 932 may be configured for each separated bearer. The secondary path 932 may be explicitly configured through RRC or MAC signaling, or may be mapped to the RLC entity of the corresponding separated bearer without explicit configuration, and all RLC entities other than the primary path may be considered as secondary RLC entities 932. The duplication operation of the separated bearer may be activated and deactivated for each DRB through RRC and MAC layer signaling. In the case where the duplication operation of the separated bearer is activated, the PDCP layer may repeatedly send the same packet (PDCP PDU) through the primary RLC entity 930 and one or more secondary RLC entities 932.

[0160] Figure 10 An example of a packet transmission operation when a split bearer operation based on a data radio bearer (DRB) is configured according to an embodiment of the present disclosure is shown.

[0161] refer to Figure 10 In this embodiment, the XR service flow can be configured by a combination of multiple pieces of data (for example, PDUs or PDU sets corresponding to I-frames 1005, B-frames 1006, and P-frames 1007, respectively, in the case of video services) with different QoS requirements (for example, delay / reliability related requirements) and importance levels, as described above with reference to Figure 3 In addition, multiple pieces of data included in the same XR service flow can be as follows Figure 4As shown in FIG1 , the QoS flows 1001 and 1041 are mapped to one or more QoS flows 1001 and 1041 and then sent to the SDAP layer 1010 and 1050. The SDAP layer can map one or more QoS flows mapped to the same XR service flow to the same DRB. In this case, the corresponding DRB can be configured as a separate bearer that sends data over multiple RLC bearers to handle XR service flows with different QoS requirements and importance levels.

[0162] In this embodiment, as mentioned above Figure 9 As described above, the configuration related to the split and copy operations of the split bearer (at least one of the primary path, secondary path, split secondary path, ul-DataSplitThreshold, and copy operation activation / deactivation state) can be configured for each DRB. Therefore, all packets sent through the corresponding split bearer can be sent according to the same split bearer operation configuration. In addition, although for ease of description, it is assumed in this embodiment that the XR service flow is configured by video service flows with different QoS requirements and importance levels (for example, PDUs or PDU sets corresponding to I frames, B frames, and P frames, respectively), the operations described through the embodiment can also be applied to general XR service flows.

[0163] The data segments (e.g., PDUs or PDU sets) corresponding to the I-frame 1005, B-frame 1006, and P-frame 1007, respectively, included in the same XR service flow may have different QoS requirements and importance levels and may be transmitted to the SDAP layers 1010 and 1050 through one or more QoS flows (or QoS sub-flows) 1001 and 1041. The SDAP layer may map one or more QoS flows mapped to the same XR service flow to a DRB configured as a separate bearer. When the separate bearer is configured to perform the following steps: Figure 9 In the case of the copy operation (1080) in the embodiment, the PDCP layer 1020 can perform the copy operation on all packets through the primary path 1031 and the secondary path 1032 configured for each DRB without distinguishing packets (PDCP SDUs) corresponding to I frames, B frames, and P frames, respectively. Meanwhile, when the split bearer is configured as Figure 9When performing a split operation (1090) as in the embodiment described above, the PDCP layer 1060 may perform a split operation based on the split operation configuration configured for each DRB (e.g., primary path 1071, split secondary path 1072, ul-DataSplitThreshold, etc.), without distinguishing between packets (PDCP SDUs) corresponding to I frames, B frames, and P frames. When a split bearer operation is configured for each DRB as in the above embodiment, the copying 1080 and splitting 1090 operations are performed similarly for all data transmitted through the corresponding DRB. Therefore, if XR service flows have different QoS requirements and importance levels, there may be limitations on performing the copying and splitting operations based on the requirements for each packet.

[0164] Figure 11 An example of a packet transmission operation when a split bearer operation is configured based on the importance of a PDU set according to an embodiment of the present disclosure is shown.

[0165] refer to Figure 11 In this embodiment, the XR service flow can be configured by a combination of multiple pieces of data (for example, PDUs or PDU sets corresponding to I-frames 1140, P-frames 1141, and B-frames 1142, respectively, in the case of video services) with different QoS requirements (for example, delay / reliability related requirements) and importance levels, as described above with reference to Figure 3 As described. Although for ease of description, it is assumed in this embodiment that the XR service flow is configured by video service flows with different QoS requirements and importance levels (for example, PDUs or PDU sets corresponding to I frames, B frames, and P frames, respectively), the operations described in this embodiment can also be applied to general XR service flows. Multiple pieces of data included in the XR service flow can be mapped to one or more QoS flows (or QoS sub-flows) 1101 and then transmitted to the SDAP layer 1110. The SDAP layer can map one or more QoS flows mapped to the same XR service flow to the same DRB. The corresponding DRB can be configured as a separate bearer for sending data through multiple RLC bearers in order to handle XR service flows (for example, PDU sets) with different importance levels.

[0166] In this embodiment, as mentioned above Figure 9As described above, the configuration related to the splitting and duplication operation of the split bearer (at least one of the primary path, the secondary path, the split secondary path, the ul-DataSplitThreshold, and the duplication operation activation / deactivation state) can be configured based on the importance of the PDU set. Therefore, even packets (e.g., PDCP SDUs) transmitted via the same split bearer can be transmitted according to different split bearer operation configurations depending on the importance level of the packet (e.g., the importance level of the PDU set configured by the packet), thereby ensuring different levels of service.

[0167] This embodiment will describe operations in which a split bearer operation is configured based on the importance of a PDU set. For example, a PDU set corresponding to an I frame 1140 may be assigned a high importance level, and a duplication operation may be configured accordingly to ensure a high level of reliability. Therefore, when transmitting a PDU set corresponding to an I frame, the PDCP layer 1120 may repeatedly transmit the same packet via the primary RLC entity 1131 and the secondary RLC entity 1132. PDU sets corresponding to P frames 1141 and B frames 1142 may be assigned a relatively low importance level, and a split operation may be configured accordingly to increase data transmission throughput. However, if the PDU sets corresponding to P frames 1141 and B frames 1142 have different importance levels, the RLC / MAC configuration (e.g., the number of RLC retransmissions, etc.) appropriate for transmitting the PDU sets corresponding to the respective frame types may be different. Therefore, different primary RLC entities and separate secondary RLC entities may be configured based on the importance levels of the PDU sets. This embodiment shows an example in which RLC1 1131 is configured as a primary path and RLC2 1132 is configured as a separate secondary path with respect to the importance level of the PDU set corresponding to the P frame 1141. Regarding the importance level of the PDU set corresponding to the B frame 1142, RLC2 1132 is configured as a primary path and RLC1 1131 is configured as a separate secondary path.

[0168] Specifically, the following parameters related to the split bearer operation may be configured separately with respect to the importance level of the PDU set.

[0169] - Primary path: Logical channel ID (LCID) and cell group ID values ​​of the primary RLC entity.

[0170] - Split Secondary Path: The LCID value of the split secondary RLC entity. If a split operation is not required, the split secondary path may not be configured. Even if a split operation is necessary, and if there are two RLC entities mapped to the corresponding DRB, the remaining RLC entities other than the primary RLC entity may be split secondary paths without explicit split secondary path configuration.

[0171] - Secondary Path: The LCID value of the secondary path RLC entity. If multiple secondary paths exist, multiple LCID values ​​can be configured. If the replication operation is deactivated, no secondary path may be configured. If the replication operation is activated but the secondary path is not explicitly configured, it may mean that among the RLC entities mapped to the corresponding DRB, the remaining RLC entities other than the primary RLC entity are configured as secondary paths.

[0172] ul-DataSplitThreshold: The threshold used during the split operation. The split operation can only be activated if the total amount of data to be sent in the PDCP and RLC layers via the primary RLC entity and the split secondary RLC entity (if this value is configured for each set, the total amount of data to be used can be calculated separately for each set) is greater than or equal to ul-DataSplitThreshold. If this value is configured to infinity, packets can be sent only via the primary path.

[0173] -pdcp-Duplication (or duplicationState): A parameter indicating the activation state of the duplication operation. If the corresponding value is set to "true", it means that duplication is activated. When two or more secondary RLC entities are configured, whether the duplication operation is activated can be indicated separately for each secondary RLC entity.

[0174] Figure 12 A signaling procedure between a UE and a gNB for configuring and operating UE operations based on PDU set importance in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0175] Figure 12 The signaling process between UE 1201 and gNB 1203 is shown for configuring and manipulating UE operation based on PDU set importance. The procedures in each step are as follows.

[0176] UECapabilityEnquiry (gNB->UE) 1210: gNB 1203 may transmit a UECapabilityEnquiry message to UE 1201 in the RRC Connected state to request UE capability reporting. gNB 1203 may include UE capability requests for each radio access type (RAT) in the UECapabilityEnquiry message. The request for each RAT type may include requested frequency band information. Additionally, when gNB 1203 requests UE 1201 to generate a UECapabilityInformation message, it may include filtering information to indicate conditions and restrictions. Using this filtering information, gNB 1203 can indicate whether UE 1201 needs to report capabilities related to UE operations based on PDU set importance (e.g., BSR triggering operations, LCP operations, split bearer configuration, etc., taking into account PDU set importance).

[0177] UECapabilityInformation (UE->gNB) 1211: UE 1201 may generate a UECapabilityInformation message corresponding to UECapabilityEnquiry message 1210 and may report a response to the request to gNB 1203. The UECapabilityInformation message may include parameters indicating whether UE 1201 supports UE operations based on PDU set importance (e.g., BSR triggering operations, LCP operations, split bearer configuration, etc., taking into account PDU set importance). Based on the received UECapabilityInformation message, gNB 1203 may determine whether UE 1201 supports UE operations based on PDU set importance.

[0178] UEAssistanceInformation (UE->gNB) 1212: UE 1201 may configure assistance information required for UE operation with reference to the PDU set importance in the UEAssistanceInformation message, and may transmit it to the gNB. For example, the UEAssistanceInformation message may include information such as the importance level of each PDU set delivered via one or more QoS flows, the corresponding QoS requirements (e.g., latency and reliability requirements), and traffic characteristics (e.g., periodicity and data size).

[0179] QoS Profile (CN->gNB) 1213: The core network (CN) 1205 may transmit to the gNB the QoS profile information required for the gNB 1203 to configure UE operations based on PDU set importance (e.g., BSR triggering, LCP operation, and split bearer configuration, taking into account PDU set importance). The QoS profile information may include information about the importance level of each PDU set delivered via one or more QoS flows, the corresponding QoS requirements (e.g., latency and reliability requirements), and traffic characteristics (e.g., periodicity and data size). The CN in step 1213 may be, but is not limited to, a session management function (SMF), an AMF, or a policy control function (PCF).

[0180] RRCReconfiguration (gNB->UE) 1214: gNB 1203 may transmit an RRCReconfiguration message to UE 1201 to configure UE operation based on PDU set importance (e.g., BSR triggering operation, LCP operation, split bearer configuration, etc., taking into account PDU set importance). The RRCReconfiguration message may include the following configuration information.

[0181] For example, as referenced above Figure 6 As described above, the configuration information for MAC operation (e.g., MAC-CellGroupConfig) may include an indicator (e.g., BSRbasedOnImportance) for configuring the UE so as to consider the importance of UL data (in other words, the importance of the PDU set configured by the UL data) when performing a BSR triggering operation on the MAC layer.

[0182] For example, as referenced above Figure 7 and Figure 1 As described in gb, the configuration information for MAC operation (e.g., MAC-CellGroupConfig) may include an indicator (e.g., SchedulingBasedonImportance) for configuring the UE so that the importance of UL data (in other words, the importance of the PDU set configured by the UL data) is considered when performing LCP operation on the MAC layer.

[0183] As another example, an indicator (e.g., HandlingImportance) may be configured for each DRB (or each PDCP entity) to indicate whether packets transmitted via PDCP connected to a specific DRB may be handled differently based on the importance of each packet (in other words, the importance of the PDU set configured by the packet). In the case of configuring the indicator, the following parameters related to the split bearer operation configuration may be included based on the importance of the PDU set, as described above with reference to Figure 11 As stated.

[0184] *Primary path, split secondary path, secondary path, ul-DataSplitThreshold, pdcp-Duplication (or duplicationState)

[0185] As another example, in a case where each PDU set has different delay requirements depending on the importance level, a discardTimer value can be configured for the packet discard operation at the PDCP layer according to the importance level of each PDU set. The discardTimer value can be used to discard the PDCP SDU packet corresponding to the importance level of the PDU set. For example, if a PDCP SDU packet arrives at the PDCP layer, a discard timer can be started, and if the timer value reaches the discardTimer value configured for the importance level of the PDU set corresponding to the packet, the timer can expire, thereby discarding the packet. If L2 transmission for the packet succeeds before the discardTimer expires, the UE can end the discardTimer and discard the packet.

[0186] -RRRCReconfigurationComplete(UE->gNB) 1215: UE 1201 may apply the configuration included in the RRCReconfiguration message received from gNB 1203 in step 1214 and may send an RRCReconfigurationComplete message to report to the gNB that the configuration has been completed.

[0187] - MAC CE for per-set duplication activation / deactivation (gNB->UE) 1216: The gNB 1203 may send a MAC CE to the UE 1201 to activate or deactivate duplication of split bearers based on the importance of the configured PDU set. To this end, the duplication activation / deactivation MAC CE may be recycled (e.g., the UE operation may be changed upon receipt of the MAC CE), or a new MAC CE may be defined, as will be referenced below. Figure 13 Descriptive.

[0188] - MAC CE for Duplicate RLC Activation per Set (gNB->UE) 1217: In the case where two or more RLC entities can be used as secondary paths (or secondary RLC paths) for the duplicate operation (or in the case where three or more RLC entities are connected to the corresponding DRB), the gNB 1203 may send a MAC CE to the UE 1201 to activate or deactivate the duplicate operation for each RLC entity based on the importance of the PDU set. To this end, the Duplicate RLC Activation / Deactivation MAC CE may be recycled (e.g., the UE operation may be changed upon receipt of the MAC CE), or a new MAC CE may be defined, as will be referenced below. Figure 13 Descriptive.

[0189] In case a HandlingImportance indication (true value) is configured with respect to a specific DRB (or a PDCP entity corresponding to a DRB), and in case the UE has received retransmission resources addressed to the configured Scheduling Radio Network Temporary Identifier (CS-RNTI) value (i.e., a retransmission grant addressed to the CS-RNTI), all RLC entities connected to the PDCP entity may be activated for PDCP duplication operation.

[0190] Figure 13 A MAC CE structure that can be used to activate / deactivate PDCP duplication based on the importance of a PDU set according to an embodiment of the present disclosure is shown.

[0191] refer to Figure 13 , reference numerals 1301 , 1302 and 1303 correspond to examples of newly defined MAC CEs for activating or deactivating a copy operation of a split bearer based on a PDU set importance configuration, as in step 1216 above.

[0192] In conjunction with reference numeral 1301, a DRB ID may indicate the DRB to which the corresponding MAC CE is to be applied, and each IPT_i value may indicate the activation status of the copy operation for the corresponding PDU set importance. Therefore, when a MAC CE is defined as in 1301, the activation or deactivation of the copy operation for multiple PDU set importance levels can be indicated via a single MAC CE transmission. In conjunction with IPT_i, i may correspond to the ascending or descending order of the PDU set importance levels configured for the DRB indicated by the DRB ID. If the IPT_i value is configured as 1, it may indicate activation of the copy function for the corresponding PDU set importance level. If the IPT_i value is configured as 0, it may indicate deactivation of the copy function for the corresponding PDU set importance level. Although this example assumes that a maximum of three PDU set importance levels are mapped to one DRB (three bits for the IPT_i value), the MAC CE structure may be expanded so that four or more bits may be used for the IPT_i value if four or more PDU set importance levels can be transmitted via the same DRB.

[0193] In conjunction with reference numeral 1302, the DRB ID may indicate the DRB to which the corresponding MAC CE is to be applied, and the IPT ID value may indicate the PDU set importance value for which the copy operation is to be activated or deactivated. Therefore, in the case where the MAC CE is defined as in 1302, the activation or deactivation of the copy operation for one PDU set importance level may be indicated by a single MAC CE transmission. In the case where the copy operation for multiple PDU set importance levels configured for a specific DRB is simultaneously activated or deactivated by using the same structure, the 1302 structure may be extended to include multiple IPT IDs.

[0194] In conjunction with reference numeral 1303, each IPT_i value may indicate the activation status of the copy operation for the corresponding PDU set importance. Therefore, when a MAC CE is defined as in 1303, the activation or deactivation of the copy operation for multiple PDU set importance levels can be indicated via a single MAC CE transmission. In conjunction with IPT_i, i may correspond to the ascending or descending order of the PDU set importance levels configured for the corresponding UE. (In this case, it is assumed that the PDU set importance for each PDU set importance level is uniquely configured in the corresponding UE.) If the IPT_i value is configured as 1, the IPT_i value may indicate that the copy function is activated for the corresponding set. If the IPT_i value is configured as 0, the copy function may be deactivated for the corresponding set. Although this example assumes that a maximum of eight PDU set importance levels are mapped to the corresponding UE (eight bits for the IPT_i value), the MAC CE structure may be expanded so that, if nine or more PDU set importance levels can be configured for the same UE, nine or more bits may be used for the IPT_i value.

[0195] In conjunction with reference numeral 1304, the DRB ID may indicate the DRB to which the corresponding MAC CE is to be applied, and the IPT threshold may indicate a threshold of a PDU set importance value for which a duplication operation is to be activated or deactivated. Therefore, in the case where the MAC CE is defined as in 1304, the IPT threshold for duplication operation activation or deactivation may be indicated by referring to the PDU set importance value in a specific DRB through a single MAC CE transmission. The UE may activate duplication only for packets (i.e., PDCP SDUs) having an importance level higher than the IPT threshold among packets transmitted through the corresponding DRB.

[0196] Reference numerals 1310 and 1311 correspond to a MAC CE structure, which can be used to activate or deactivate the duplication operation of each RLC entity based on the PDU set importance in a case where two or more RLC entities can be used as a secondary path (or secondary RLC path) for the duplication operation with respect to a specific PDU set importance level (or in a case where three or more RLC entities are connected to the corresponding DRB).

[0197] In conjunction with reference numeral 1310, the IPT ID may indicate the PDU set importance level to which the corresponding MAC CE applies. (In this case, it is assumed that each PDU set importance level is uniquely configured in the corresponding UE.) In addition, each RLC_i value may indicate the activation status of the duplication operation for the corresponding RLC entity. In conjunction with RLC_i, i may correspond to the ascending or descending order of the LCID values ​​of the RLC entities configured as the secondary path for the PDU set importance level indicated by the IPT ID (or for the DRB to which the PDU set importance level indicated by the IPT ID is mapped). If the RLC_i value is configured as 1, it may indicate that the duplication function for the corresponding RLC entity is activated. If the RLC_i value is configured as 0, it may indicate that the duplication function for the corresponding RLC entity is deactivated. Although it is assumed in this example that a maximum of three secondary paths are configured with respect to one PDU set importance level (three bits are used for the RLC_i value), the MAC CE structure can be extended so that in the case where four or more RLC entities are configured as secondary paths with respect to the corresponding PDU set importance level, four or more bits can be used for the RLC_i value.

[0198] In conjunction with reference numeral 1311, the DRB ID and IPT ID may respectively indicate the DRB and PDU set importance to which the corresponding MAC CE is to be applied. (In this case, it is assumed that the IPT ID regarding the PDU set importance is uniquely configured for each DRB.) In addition, each RLC_i value may indicate the activation state of the duplication operation for the corresponding RLC entity. In conjunction with RLC_i, i may correspond to ascending or descending order of the LCID values ​​of the RLC entities configured as the secondary path with respect to the PDU set importance level indicated by the IPT ID (or with respect to the DRB indicated by the IPT ID). If the RLC_i value is configured as 1, it may indicate activation of the duplication function for the corresponding RLC entity. If the RLC_i value is configured as 0, it may indicate deactivation of the duplication function for the corresponding RLC entity. Although it is assumed in this example that a maximum of eight secondary paths are configured for one PDU set importance level (eight bits are used for the RLC_i value), the MAC CE structure can be extended so that in the case where nine or more RLC entities are configured as secondary paths with respect to the corresponding set, nine or more bits can be used for the RLC_i value.

[0199] Figure 14 is a block diagram illustrating an internal structure of a UE according to an embodiment of the present disclosure.

[0200] refer to Figure 14, the UE includes a radio frequency (RF) processing unit 1410, a baseband processing unit 1420, a memory 1430, and a controller 1440. Of course, the examples given above are not limiting, and the UE may include more than Figure 14 The RF processor 1410 may perform functions for sending and receiving signals via wireless channels, such as frequency band conversion and signal amplification. That is, the RF processing unit 1410 up-converts the baseband signal provided from the baseband processing unit 1420 into an RF band signal, transmits the RF band signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1410 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. Although in Figure 14 Only one antenna is shown in the figure, but the UE may include multiple antennas. In addition, the RF processor 1410 may include multiple RF chains. In addition, the RF processor 1410 may perform beamforming. For beamforming, the RF processor 1410 may adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit 1410 may perform multiple-input multiple-output (MIMO) and may receive multiple layers when performing MIMO operations. The RF processing unit 1410 may appropriately configure multiple antennas or antenna elements under the control of the controller 1440 to perform receive beam scanning, or may adjust the direction and beam width of the receive beam so that the receive beam is coordinated with the transmit beam.

[0201] The baseband processor 1420 can perform conversion functions between baseband signals and bit streams according to the system's physical layer specifications. For example, during data transmission, the baseband processor 1420 may encode and modulate the transmitted bit stream to generate complex symbols. Furthermore, during data reception, the baseband processor 1420 may demodulate and decode the baseband signal provided by the RF processor 1410 to recover the received bit stream. For example, when using an orthogonal frequency division multiplexing (OFDM) scheme, during data transmission, the baseband processor 1420 may encode and modulate the transmitted bit stream to generate complex symbols, map the complex symbols to subcarriers, and configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. Furthermore, during data reception, the baseband processor 1420 may separate the baseband signal provided by the RF processor 1410 at the OFDM symbol level, recover the signals mapped to the subcarriers through a fast Fourier transform (FFT) operation, and recover the received bit stream through demodulation and decoding.

[0202] The baseband processor 1420 and the RF processor 1410 can transmit and receive signals as described above. Therefore, the baseband processor 1420 and the RF processor 1410 can be referred to as transmitters, receivers, transceivers, or communication units. Furthermore, at least one of the baseband processor 1420 and the RF processor 1410 can include multiple communication modules to support a variety of different radio access technologies. Furthermore, at least one of the baseband processor 1420 and the RF processor 1410 can include different communication modules to process signals in different frequency bands. For example, different radio access technologies can include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), and so on. Furthermore, different frequency bands can include super high frequency (SHF) (e.g., 2NRHz) bands and millimeter wave (mmWave) bands (e.g., 60GHz). Using the baseband processor 1420 and the RF processor 1410, the UE can transmit and receive signals with the base station. These signals can include control information and data.

[0203] The memory 1430 may store basic programs, applications, and data, such as configuration information, for the operation of the master base station. Specifically, the memory 1430 may store information about a second access node configured to perform wireless communication using a second radio access technology. Furthermore, the memory 1430 may provide stored data upon request from the controller 1440. Furthermore, the memory 1430 may be configured from multiple memories. Depending on the embodiment, the memory 1430 may store a program for executing the split bearer operation method of the present disclosure.

[0204] The controller 1440 can control the overall operation of the UE. For example, the controller 1440 can send / receive signals through the baseband processor 1420 and the RF processor 1410. In addition, the controller 1440 can record data in the memory 1430 and read data from the memory 1430. To this end, the controller 1440 may include at least one processor. For example, the controller 1440 may include a communication processor (CP) configured to perform control for communication and an application processor (AP) configured to control upper layers such as application programs. In addition, at least one component in the UE may be implemented as a single chip. In addition, according to an embodiment of the present disclosure, the controller 1440 may include a multi-connection processor 1442, which is configured to handle processes operating in a multi-connection mode.

[0205] Figure 15 is a block diagram illustrating a structure of a base station according to an embodiment of the present disclosure.

[0206] refer to Figure 15, the base station may include an RF processor 1510, a baseband processor 1520, a backhaul communication unit 1530, a memory 150, and a controller 1550. Of course, the examples given above are not limiting, and the base station may include more than Figure 3 Fewer or greater numbers of components may be shown.

[0207] The RF processor 1510 may perform functions for transmitting and receiving signals via wireless channels, such as frequency band conversion and signal amplification. That is, the RF processor 1510 may up-convert the baseband signal provided by the baseband processor 1520 into an RF band signal, may transmit the RF band signal through an antenna, and may down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1510 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although in Figure 15 Only one antenna is shown in the figure, but the base station may include multiple antennas. In addition, the RF processor 1510 may also include multiple RF chains. In addition, the RF processor 1510 can perform beamforming. For beamforming, the RF processor 1510 can adjust the phase and amplitude of each signal sent and received through multiple antennas or antenna elements. The RF processing unit 1510 can transmit one or more layers to perform downward MIMO operations. The RF processor 1510 can appropriately configure multiple antennas or antenna elements to perform receive beam scanning, or can adjust the direction and beam width of the receive beam so that the receive beam resonates with the transmit beam under the control of the controller.

[0208] The baseband processor 1520 can perform conversion functions between baseband signals and bit streams according to the physical layer specifications of the first radio access technology. For example, during data transmission, the baseband processor 1520 can encode and modulate the transmitted bit stream to generate complex symbols. Furthermore, during data reception, the baseband processor 1520 can demodulate and decode the baseband signal provided by the RF processor 1510 to recover the received bit stream. For example, when using the OFDM scheme, during data transmission, the baseband processor 1520 can encode and modulate the transmitted bit stream to generate complex symbols, map the complex symbols to subcarriers, and configure OFDM symbols through IFFT operations and CP insertion. Furthermore, during data reception, the baseband processor 1520 can separate the baseband signal provided by the RF processor 1510 at the OFDM symbol level, recover the signals mapped to the subcarriers through FFT operations, and recover the received bit stream through demodulation and decoding. The baseband processor 1520 and the RF processor 1510 can transmit and receive signals as described above. Therefore, the baseband processor 1520 and the RF processor 1510 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The base station may transmit / receive signals with the UE using the baseband processor 1520 and the RF processor 1510, and the signals may include control information and data.

[0209] The backhaul communication unit 1530 may provide an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1530 may convert a bit stream sent from the master base station to another node (e.g., a secondary base station, a core network, etc.) into a physical signal, and may convert a physical signal received from another node into a bit stream.

[0210] The memory 1540 may store basic programs, applications, and data for the operation of the master base station, such as configuration information. Specifically, the memory 1540 may store information about the bearers assigned to connected UEs, measurement results reported from connected UEs, and the like. In addition, the memory 1540 may store information used as a criterion for determining whether to provide multiple connections to the UE or suspend multiple connections. Furthermore, the memory 1540 may provide stored data at the request of the controller 1550. The memory 1540 may store a program for executing the split bearer operation method disclosed herein.

[0211] The controller 1550 can control the overall operation of the base station. For example, the controller 1550 can send / receive signals through the baseband processor 1520 and the RF processor 1510 or through the backhaul communication unit 1530. In addition, the controller 1550 can record data in the memory 1540 and read data from the memory 1540. To this end, the controller 1550 may include at least one processor. In addition, at least one component in the base station may be implemented as a single chip. In addition, according to an embodiment of the present disclosure, the controller 1550 may include a multi-connection processor 1552, which is configured to process processes operating in a multi-connection mode. In addition, the various components of the base station can be operated to perform the above-mentioned embodiments of the present disclosure.

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

[0213] When the method is implemented via 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 may be configured to be executed by one or more processors within an electronic device. At least one program includes instructions that cause the electronic device to perform the method according to the various embodiments of the present disclosure as defined in the appended claims and / or disclosed herein.

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

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

[0216] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiment presented. However, for ease of description, the singular form or plural form is appropriately selected for the situation presented, and the present disclosure is not limited to elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

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

[0218] In addition, the above Figures 1 to 13 The method of the present disclosure described in the accompanying drawings may include a method in which one or more of the accompanying drawings are combined according to various implementations. For example, Figures 1 to 15 In addition, all or part of one embodiment may be combined with all or part of one or more other embodiments to be performed. The present disclosure may include methods of combining one or more figures according to various implementations.

Claims

1. A method performed by a terminal (user equipment (UE)) in a wireless communication system, the method comprising: identifying that a buffer status report (BSR) has been triggered with respect to a plurality of logical channels; and Sending the BSR to the base station, The BSR is triggered in a case where importance of a piece of uplink data that has become available for a predetermined logical channel among the plurality of logical channels is higher than importance of a piece of available uplink data belonging to another logical channel.

2. The method according to claim 1, comprising: performing uplink transmission on the uplink resources allocated based on the BSR, Therein, uplink transmission is performed by allocating resources in descending order of priority of the multiple logical channels, so that for logical channels with the same priority, resources are allocated in ascending order of importance of data belonging to the logical channels with the same priority.

3. The method according to claim 1, comprising: performing uplink transmission on the uplink resources allocated based on the BSR, Among them, uplink transmission is performed by: preferentially allocating resources to a logical channel to which important data belongs among the plurality of logical channels; Allocate resources to logical channels with important data in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data with importance belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels to which data having no importance belongs among the plurality of logical channels in descending order of priority.

4. The method according to claim 1, comprising: performing uplink transmission on the uplink resources allocated based on the BSR, Among them, uplink transmission is performed by: preferentially allocating resources to a logical channel to which data having importance higher than a predetermined threshold belongs among the plurality of logical channels; Allocating resources to logical channels to which data having importance higher than a predetermined threshold belongs in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data having importance higher than a predetermined threshold belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels among the multiple logical channels to which data having importance equal to or lower than a predetermined threshold belongs in descending order of priority, so that for logical channels having the same priority, resources are allocated in descending order of the importance of data belonging to logical channels having the same priority.

5. A method performed by a base station in a wireless communication system, the method comprising: sending, to the terminal, an uplink grant for allocating uplink resources for transmission of a buffer status report (BSR) for a plurality of logical channels of the terminal; and receiving the BSR on an uplink resource used for transmission of the BSR from a terminal, The BSR is triggered in a case where importance of a piece of uplink data that has become available for a predetermined logical channel among the plurality of logical channels is higher than importance of a piece of available uplink data belonging to other logical channels.

6. The method according to claim 5, comprising: receiving an uplink signal on an uplink resource allocated based on the BSR from the terminal, Therein, uplink transmission is performed by allocating resources in descending order of priority of the multiple logical channels, so that for logical channels with the same priority, resources are allocated in ascending order of importance of data belonging to the logical channels with the same priority.

7. The method according to claim 5, comprising: receiving an uplink signal on an uplink resource allocated based on the BSR from the terminal, The uplink signal is received via: preferentially allocating resources to a logical channel to which important data belongs among the plurality of logical channels; Allocate resources to logical channels with important data in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data with importance belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels to which data having no importance belongs among the plurality of logical channels in descending order of priority.

8. The method according to claim 5, comprising: receiving an uplink signal on an uplink resource allocated based on the BSR from the terminal, The uplink signal is received via: preferentially allocating resources to a logical channel to which data having importance higher than a predetermined threshold belongs among the plurality of logical channels; Allocating resources to logical channels to which data having importance higher than a predetermined threshold belongs in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data having importance higher than a predetermined threshold belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels among the multiple logical channels to which data having importance equal to or lower than a predetermined threshold belongs in descending order of priority, so that for logical channels having the same priority, resources are allocated in descending order of the importance of data belonging to logical channels having the same priority.

9. A terminal (user equipment (UE)) in a wireless communication system, the terminal comprising: transceiver; and A controller, connected to the transceiver, Wherein, the controller is configured as follows: identifying that a buffer status report (BSR) has been triggered with respect to a plurality of logical channels; and Sending the BSR to the base station, and The BSR is triggered in a case where importance of a piece of uplink data that has become available for a predetermined logical channel among the plurality of logical channels is higher than importance of a piece of available uplink data belonging to other logical channels.

10. The terminal according to claim 9, wherein: The controller is further configured to: perform uplink transmission on the uplink resources allocated based on the BSR, and Therein, uplink transmission is performed by allocating resources in descending order of priority of the multiple logical channels, so that for logical channels with the same priority, resources are allocated in ascending order of importance of data belonging to the logical channels with the same priority. The terminal according to claim 9 , wherein: The controller is further configured to: perform uplink transmission on uplink resources allocated based on the BSR, and Among them, uplink transmission is performed by: preferentially allocating resources to a logical channel to which important data belongs among the plurality of logical channels; Allocate resources to logical channels with important data in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data with importance belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels to which data having no importance belongs among the plurality of logical channels in descending order of priority.

12. The terminal according to claim 9, wherein: The controller is further configured to perform uplink transmission on uplink resources allocated based on the BSR, Among them, uplink transmission is performed by: preferentially allocating resources to a logical channel to which data having importance higher than a predetermined threshold belongs among the plurality of logical channels; Allocating resources to logical channels to which data having importance higher than a predetermined threshold belongs in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data having importance higher than a predetermined threshold belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels among the multiple logical channels to which data having importance equal to or lower than the predetermined threshold belongs in descending order of priority, so that for logical channels having the same priority, resources are allocated in descending order of the importance of data belonging to logical channels having the same priority.

13. A base station in a wireless communication system, the base station comprising: transceiver; and A controller, connected to the transceiver, Wherein, the controller is configured as follows: sending an uplink grant to the terminal for allocating uplink resources for transmission of a buffer status report (BSR) for a plurality of logical channels of the terminal; and receiving the BSR on an uplink resource used for transmission of the BSR from a terminal, and The BSR is triggered in a case where importance of a piece of uplink data that has become available for a predetermined logical channel among a plurality of logical channels is higher than importance of a piece of available uplink data belonging to other logical channels.

14. The base station according to claim 13, wherein: The controller is further configured to: receive an uplink signal on an uplink resource allocated based on a BSR from the terminal, and Therein, uplink transmission is performed by allocating resources in descending order of priority of the multiple logical channels, so that for logical channels with the same priority, resources are allocated in ascending order of importance of data belonging to the logical channels with the same priority.

15. The base station according to claim 13, wherein: The controller is further configured to receive an uplink signal on an uplink resource allocated based on the BSR from the terminal, and The uplink signal is received via: preferentially allocating resources to a logical channel to which important data belongs among the plurality of logical channels; Allocate resources to logical channels with important data in descending order of priority; allocating resources to logical channels with the same priority among logical channels to which data with importance belongs, in descending order of importance of the data belonging to the logical channels with the same priority; and Resources are allocated to logical channels to which data having no importance belongs among the plurality of logical channels in descending order of priority.

Images