Method and apparatus for discarding protocol data unit (PDU) set unit downlink packet in separable mobile communication base station

The method for discarding PDU sets in next-generation mobile communication systems addresses the challenge of resource management by using a discarding timer and control mechanisms within the CU-CP and CU-UP, optimizing radio resource utilization and enhancing system performance.

WO2024232739A1PCT designated stage expired Publication Date: 2024-11-14SAMSUNG ELECTRONICS CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006461
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-13
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Next-generation mobile communication systems face challenges in efficiently using network radio resources, particularly in discarding downlink packets in SET units of protocol data units (PDU) within a split radio access network architecture, which affects the overall performance and resource management.

Method used

A method and apparatus that enables efficient discarding of PDU sets by incorporating a discarding timer and control mechanisms between the central unit (CU)-control plane (CP) and CU-user plane (UP), allowing for adaptive and controlled PDU set discarding based on Quality of Service (QoS) parameters, thereby optimizing radio resource utilization.

Benefits of technology

This approach enhances the efficient use of network radio resources by allowing for controlled and adaptive discarding of PDU sets, improving system performance and resource management in next-generation mobile communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006461_14112024_PF_FP_ABST
    Figure KR2024006461_14112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to the present disclosure, network radio resources can be efficiently used by performing discarding of a downlink PDCP SDU in units of PDU sets in a separable base station.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for discarding downlink packets in units of a set of protocol data units (PDUs) in a separate mobile communication base station

[0001] The present disclosure relates to the operation of a separate mobile communication base station in a wireless communication system. Specifically, the present disclosure relates to a method and device for efficiently servicing application data traffic in a wireless communication system.

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

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

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

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

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

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

[0008] Meanwhile, the need for a method to efficiently use network wireless resources in such next-generation mobile communication systems has emerged.

[0009] The purpose of the present disclosure is to provide a device and method capable of effectively providing a service in a next-generation mobile communication system. More specifically, the present disclosure relates to a method and device for discarding a downlink PDCP SDU (packet data convergence protocol service data unit discarding, hereinafter referred to as PDCP SDU discarding) in a split base station (split Radio Access Network architecture) in a next-generation mobile communication system, and, when configuring a set of PDUs (protocol data units) (hereinafter referred to as PDU sets) corresponding to application data units (ADUs) in 3GPP 5GS, the present disclosure relates to a method and device for performing a PDCP SDU discarding operation in units of PDU sets for efficient use of network radio resources.

[0010] A method performed by a base station according to an embodiment of the present disclosure for solving the above-described problem may include the steps of transmitting, from a central unit (CU)-control plane (CP) to a CU-user plane (UP), at least one piece of information for performing protocol data unit (PDU) set discarding, wherein the at least one piece of information for the PDU set discarding includes discarding timer information, and performing, by the CU-CP, the PDU set discarding.

[0011] Meanwhile, a base station according to another embodiment of the present disclosure may include a control unit that controls a central unit (CU)-control plane (CP) to transmit at least one piece of information for performing protocol data unit (PDU) set discarding to a CU-user plane (UP), wherein the at least one piece of information for performing PDU set discarding includes discarding timer information, and controls the CU-CP to perform the PDU set discarding.

[0012] According to one embodiment of the present disclosure, a service can be effectively provided in a wireless communication system.

[0013] FIG. 1 is a diagram illustrating an example of the structure of a next-generation mobile communication system to which the present disclosure can be applied.

[0014] FIG. 2 is a diagram illustrating a PDU (protocol data unit) SET configuration according to an embodiment of the present disclosure;

[0015] FIG. 3 is a sequence diagram illustrating the operation and signaling procedures of each node or function to support discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0016] FIG. 4 is a flowchart illustrating the operation of a CU-CP within a RAN Node according to the embodiment of FIG. 3, according to one embodiment of the present disclosure;

[0017] FIG. 5a is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0018] FIG. 5b is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0019] FIG. 5c is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0020] FIG. 5d is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0021] FIG. 5e is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0022] FIG. 5f is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0023] FIG. 5g is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0024] FIG. 5h is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0025] FIG. 5i is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0026] FIG. 5j is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0027] FIG. 5k is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0028] FIG. 5l is a diagram illustrating an example configuration of a BEARER CONTEXT SETUP REQUEST message used in an E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0029] FIG. 6a is a diagram illustrating an example configuration of a BEARER CONTEXT MODIFICATION REQUEST message used in the E1 interface to modify a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0030] FIG. 6b is a diagram illustrating an example configuration of a BEARER CONTEXT MODIFICATION REQUEST message used in the E1 interface to modify a bearer context from a CU-CP to a CU-UP within a RAN Node, as used in step S340 of FIG. 3, according to one embodiment of the present disclosure;

[0031] FIG. 7a is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0032] FIG. 7b is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0033] FIG. 7c is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0034] FIG. 7d is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure.

[0035] FIG. 7e is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0036] FIG. 7f is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0037] FIG. 7g is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0038] FIG. 7h is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0039] FIG. 7i is a diagram illustrating an example configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure.

[0040] FIG. 8a is a diagram illustrating an example configuration of a UE CONTEXT MODIFICATION REQUEST message used in the F1 or W1 interface to modify a terminal context (bearer context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0041] FIG. 8b is a diagram illustrating an example configuration of a UE CONTEXT MODIFICATION REQUEST message used in the F1 or W1 interface to modify a terminal context (bearer context) from a CU-CP to a DU in a RAN Node, as used in step S360 of FIG. 3, according to one embodiment of the present disclosure;

[0042] FIG. 9 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0043] FIG. 10 is a sequence diagram showing an operation for performing an operation of discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0044] FIG. 11a is a diagram showing an example of a configuration of a packet transmitted by a UPF (1036) to a CU-UP (1024) in step S1010 of FIG. 10 to support a PDU Set unit operation, and an example of a configuration of information included in a packet transmitted by a CU-UP (1024) to a DU (1026) in step S1020 to support a PDU Set unit operation, according to one embodiment of the present disclosure.

[0045] FIG. 11b is a diagram showing an example of a configuration of a packet transmitted by a UPF (1036) to a CU-UP (1024) in step S1010 of FIG. 10 to support a PDU Set unit operation, and an example of a configuration of information included in a packet transmitted by a CU-UP (1024) to a DU (1026) in step S1020 to support a PDU Set unit operation, according to one embodiment of the present disclosure.

[0046] FIG. 11c is a diagram showing an example of a configuration of a packet transmitted by a UPF (1036) to a CU-UP (1024) in step S1010 of FIG. 10 to support a PDU Set unit operation, and an example of a configuration of information included in a packet transmitted by a CU-UP (1024) to a DU (1026) in step S1020 to support a PDU Set unit operation, according to one embodiment of the present disclosure.

[0047] FIG. 12a is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0048] FIG. 12b is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0049] FIG. 12c is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0050] FIG. 12d is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0051] FIG. 12e is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0052] FIG. 12f is a diagram showing an example of the configuration of information included in a packet used by DU (1026) to transmit PDU Set discarding information to CU-UP (1024) in step S1070 of FIG. 10 according to one embodiment of the present disclosure;

[0053] FIG. 13 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0054] FIG. 14 is a sequence diagram showing an operation for performing an operation of discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0055] FIG. 15a is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14 according to one embodiment of the present disclosure;

[0056] FIG. 15b is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14, according to one embodiment of the present disclosure;

[0057] FIG. 15c is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14, according to one embodiment of the present disclosure;

[0058] FIG. 15d is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14, according to one embodiment of the present disclosure;

[0059] FIG. 15e is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14, according to one embodiment of the present disclosure;

[0060] FIG. 15f is a diagram showing an example of the configuration of information included in a packet used by a CU-UP (1424) to transmit PDU Set discarding information to a DU (1426) in step S1470 of FIG. 14 according to one embodiment of the present disclosure;

[0061] FIG. 16 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in CU-UP and DU of a RAN Node according to an embodiment of the present disclosure.

[0062] FIG. 17a is a diagram showing an example of a configuration of a packet transmitted by a UPF to support a PDU Set unit operation as a CU-UP in step 1640-1 of FIG. 16 and an example of a configuration of information included in a packet transmitted by a CU-UP to support a PDU Set unit operation as a DU in step 1640-2, according to one embodiment of the present disclosure;

[0063] FIG. 17b is a diagram showing an example of a configuration of a packet transmitted by a UPF to support a PDU Set unit operation as a CU-UP in step 1640-1 of FIG. 16 and an example of a configuration of information included in a packet transmitted by a CU-UP to support a PDU Set unit operation as a DU in step 1640-2, according to one embodiment of the present disclosure;

[0064] FIG. 18 is a block diagram showing the configuration of a RAN Node (e.g., a base station) according to one embodiment of the present disclosure;

[0065] FIG. 19 is a block diagram showing the configuration of a terminal according to one embodiment of the present disclosure.

[0066] In describing the embodiments herein, descriptions of technical details that are well-known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present invention by omitting unnecessary explanations and to convey the gist more clearly.

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

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

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

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

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

[0072] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on their functions in the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

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

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

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

[0076] The present disclosure relates to a method and device for discarding packet data convergence protocol service data units (PDCP SDUs) in a next-generation mobile communication system. More specifically, the present disclosure relates to a method and device for performing a PDCP SDU discarding operation on a per-PDU set basis when configuring a set of protocol data units (PDUs) (hereinafter, PDU sets) corresponding to application data units (ADUs) in 3GPP 5GS, for efficient use of network radio resources.

[0077] The present disclosure proposes a PDU set integration processing parameter and a PDU set importance parameter as QoS parameters of various PDU sets that can be used to guarantee QoS (Quality of Service) in units of PDU (protocol data unit) sets, and describes a method for adaptively performing a PDU set discarding operation for various PDU set configurations.

[0078] The present disclosure specifically describes a method for performing a PDU set discarding operation, a method for instructing a PDU set discarding operation in units of PDU sets between CU-CP, CU-UP and DU within a separate base station, and a method for instructing a PDU set discarding operation in units of PDUs, and is characterized by including a step of performing PDU set discarding in a CU-UP or DU, transmitting PDU set discarding information, and then performing a packet discarding operation in units of PDU sets after receiving the same.

[0079] Through the present disclosure, a base station can set control information for a PDU set discarding operation of a terminal and a base station based on QoS requirements and QoS parameters (e.g., PDU set integration processing, PDU set importance) of a PDU set, and can exchange the set control information with the terminal. For example, the base station can transmit the set control information to the terminal. The terminal can report to the base station (e.g., gNB) whether it supports the PDU set discarding operation through UE capability information. The base station (e.g., gNB) can instruct the terminal to perform the PDU set discarding operation with reference to the UE capability information reported by the terminal, and the terminal can perform the PDU set discarding operation according to the instruction of the base station.

[0080] FIG. 1 is a diagram illustrating an example of the structure of a next-generation mobile communication system to which the present disclosure can be applied. The RAN (Radio Access Network) Node (120) specified in the structure illustrated in FIG. 1 may be a mobile communication base station connected to a core network (CN) such as a 5GC (5G Core Network). For example, the RAN Node (120) may be an LTE eNB or an NR gNB. A terminal (110) is connected to a base station (RAN Node) (120) via a radio interface (e.g., a Uu interface) and may transmit and receive control plane signaling (e.g., radio resource control (RRC) signaling) and user plane data (e.g., internet protocol (IP) packets).

[0081] The RAN node (120) is connected to the core network via an interface such as, for example, NG (next generation), and may also be connected to other RAN nodes (not shown) via an interface such as Xn. The RAN node (120) may include a central unit (CU) and a distributed unit (DU, 126). In one embodiment, the RAN node (120) may be composed of one CU and one or more DUs (126) connected to the CU, or may be composed of other combinations. The CU and the DU (126) may support respective base station functions separately. For example, the CU may support an RRC (radio resource control) layer and a PDCP (packet data convergence protocol) layer, and the DU (126) may support an RLC (radio link control) layer, a MAC (medium access control) layer, and a PHY (physical) layer.

[0082] An interface between internal functions of the base station, such as an F1 or W1 interface, may be connected between the CU (122, 124) and the DU (126). In one embodiment, the CU may be composed of one CU-CP (CU-Control Plane, 122) responsible for a control function and one or more CU-UP (CU-User Plane, 124) for processing user packets, and the DU (126) may be configured to be separated into a part supporting RLC / MAC / High-PHY and a part supporting Low-PHY / RF layers.

[0083] In addition, FIG. 1 illustrates functions or entities related to the present disclosure among various functions or entities of the core network, and the following description is about some of the contents supported by each function and entity related to the present disclosure. FIG. 1 illustrates 5GC (5G Core Network) as an example of the core network. AMF (Access and Mobility management Function, 132) included in 5GC is connected to RAN node (120) through NG (next generation) interface (or N2 interface) and can exchange control signals with RAN node (120). SMF (Session Management Function) (134) is responsible for session control function for providing user service, and UPF (User Plane Function) (136) performs functions such as exchanging user data through RAN node (120). Although not shown in Figure 1, the core network may also include functions and entities such as PCF (Policy Control Function), UDM (Unified Data Management), AUSF (Authentication Server Function), etc.

[0084] FIG. 2 illustrates a PDU Set (Protocol Data Unit SET) configuration according to an embodiment of the present disclosure. Referring to FIG. 2, various types of traffic can be classified into ADUs (Application Data Units), which are units of information that can be distinguished at the application level. In one embodiment, an ADU can be a single photo or picture, a single frame of video, or a single unit of audio. An ADU can be classified into units of a PDU set (200), and a PDU set (200) can be divided into at least one or more PDUs (201, 202, 203, 204, 205, 206) and transmitted.

[0085] For example, when using the MPEG (moving picture experts group) standard video compression technology in video traffic, a PDU set may be composed of one of 1) a combination of multiple PDUs (230) corresponding to one I (intra)-frame (220), 2) a combination of multiple PDUs (240) corresponding to one B (bidirectional)-frame, 3) a combination of multiple PDUs (250) corresponding to one P (predicted)-frame, and 4) a combination of multiple PDUs (260) corresponding to an ADU composed of multiple I-frames (261), B-frames (262, 264), and / or P-frames (263). An I-frame (220) is an independent frame and can represent a complete picture or drawing (221) regardless of the presence or absence of other frames. P-frame and B-frame (222) are frames that indicate change information of the previous I-frame (220). If the I-frame (220) is not received normally, it may be difficult to normally express the photo or picture (223) that was intended to be expressed by the P-frame and B-frame (222). In addition, in the case of the B-frame, since it is sandwiched between the I-frame and the P-frame and references both frames to store the movement between the two frames as inferred data, not only the I-frame in front but also the P-frame behind must be received normally in order to normally express the photo or picture that was intended to be expressed by the B-frame.

[0086] For ease of explanation, the embodiments of the present disclosure illustrate the configuration of PDU sets and the PDU set discarding operation by exemplifying the use of MPEG standard video compression technology in video traffic. However, the contents of the present disclosure are not limited to the configuration of PDU sets in video traffic, and can be applied to all PDU set configurations composed of general ADU units.

[0087] In an embodiment of the present disclosure, discarding packets in units of PDU sets in a base station (RAN Node) may be performed in a CU-UP or DU within the base station. Discarding packets in units of PDU sets may mean 'packets that have not yet been transmitted' among the packets (or named PDUs) that constitute the PDU set, or 'packets with a high PDCP SN (sequence number) assigned to the discarded packets'. Discarding packets in units of PDU SETs may enable efficient use of radio resources, reduce unnecessary packet processing and storage within the base station, or reduce waste of resources for unnecessary packet transmission between the CU-UP and the DU when any one of the packets that constitute the PDU set is discarded and transmission of the PDU set becomes meaningless. An example of a method of discarding packets in units of PDU sets in a CU-UP or DU within a base station is as follows, and packets may also be discarded in units of PDU sets in other ways not described herein.

[0088] - When a specific packet among the packets (or named PDU) that constitute a PDU set is discarded (or discarded) due to the expiration of the discard timer set for each packet unit, a PDU set discard operation is performed to discard the remaining packets that constitute the same PDU set.

[0089] - When a specific packet among the packets (or named PDU) that constitute a PDU set is discarded (or discarded) due to the expiration of the PDU set discard timer set for the packets included in the PDU set, a PDU set discard operation is performed to discard the remaining packets that constitute the same PDU set.

[0090] - When a specific packet among the packets (or PDUs) that constitute a PDU set is discarded (or discarded), the PDU set discard operation is performed to discard the remaining packets that constitute the same PDU set only if the PDU set integrated handling indication (or PDU set integrated handling) is set, which indicates that the remaining packets that constitute the PDU set are meaningless if at least one packet belonging to the PDU set is not successfully transmitted.

[0091] - Based on the PDU set importance value, which is information indicating the importance of each PDU set, when a specific packet among the packets (or PDUs) constituting the PDU set is discarded (or discarded), a PDU set discard operation is performed to discard the remaining packets constituting the same PDU set, for a PDU set whose importance is set lower than the reference value of the set PDU set importance, or conversely, when a specific packet among the packets (or PDUs) constituting the PDU set is discarded (or discarded), a PDU set discard operation is performed to discard the remaining packets constituting the same PDU set, for a PDU set whose importance is set higher than the reference value of the set PDU set importance,

[0092] - When a set number of packets (or PDUs) that constitute a PDU set exceeds the set standard number of packets to be discarded (or discarded), a PDU set discard operation is performed to discard the remaining packets that constitute the same PDU set.

[0093] - When a specific packet is discarded (or discarded) due to the expiration of the discard timer set for each packet, a PDU set discard operation is performed to discard the remaining packets that make up the same PDU set.

[0094] Meanwhile, FIG. 3 is a sequence diagram illustrating the operation and signal procedures of each node or function to support discarding packets in units of PDU sets in the CU-UP and DU of the RAN Node according to one embodiment of the present disclosure. The CU-CP of the RAN Node can generate parameters for discarding packets in units of PDU sets based on PDU set QoS parameters received from the Core network and then transmit them to the CU-UP and DU. The CU-CP can transmit the PDU set QoS parameters to at least one node or function among the CU-UP or DU, and the CU-CP can transmit related parameters to at least one node or function among the CU-UP or DU so that discarding packets in units of PDU sets can be performed.

[0095] Referring to FIG. 3, in step S300, the terminal (310) may perform a procedure for connection to a RAN Node and a core network, or in step S350, the terminal (310) may initiate (or trigger) a UE context modification procedure for changing PDU set QoS parameters in the core network while already connected to the RAN Node and the core network. The initiation of the UE context modification procedure for changing PDU set QoS parameters in the core network may be initiated by an SMF or another node or function of the core network, depending on the embodiment.

[0096] In step S320, when the terminal (310) performs a procedure for connection to the RAN Node and the core network, an initial context setup request message may be transmitted to the RAN Node from the core network, or in the case of a 5G core network, from the AMF (332). Alternatively, in the case of UE context modification, a UE context modification request message may be transmitted to the RAN Node. In this case, in a separate base station structure, the message may be transmitted to the CU-CP (322) of the RAN Node. The initial context setup request message or the UE context modification request message transmitted from the core network may include PDU Set QoS parameters information.

[0097] In step S330, the RAN Node or the CU-CP (322) of the RAN Node that has received PDU Set QoS parameters information from the Core network can determine parameter values ​​for performing PDU set unit packet discarding. At least one of the following parameters can be used as a parameter for performing PDU set unit packet discarding, and other parameters may be defined and used.

[0098] - PDU Set Discard Indicator: An indicator that indicates the discard operation of a PDU Set unit.

[0099] - PDU Set Discard Timer: The timer setting value until the packets (or PDUs) that make up the PDU set are discarded without being transmitted.

[0100] - PDU Set Discard Threshold: A value that sets the standard number of packets (or PDUs) that constitute a PDU set to be discarded (or discarded) in order to perform discarding of the PDU set unit.

[0101] - PDU Set Discard Importance Level: PDU set importance standard setting value for performing discard of PDU set units

[0102] In step S340, the CU-CP (322) transmits a Bearer context setup request message or a Bearer context modification request message to the CU-UP (324), which may include PDU Set QoS parameters and PDU Set Discard Indicator, PDU Set Discard Timer, PDU Set Discard Threshold, PDU Set Discard Importance Level information for performing PDU Set unit packet discarding, and at least one parameter among the above information may be included.

[0103] After CU-UP (324) sets PDU set QoS parameters and internal settings for discarding PDU set unit packets according to the information received, CU-UP (324) can transmit a Bearer context setup response message or a Bearer context modification response message to CU-CP (322) in step S350.

[0104] At step S380, the CU-UP (324) may start performing operations related to discarding PDU set unit packets.

[0105] In step S360, the CU-CP (322) transmits a UE context setup request message or a UE context modification request message to the DU (326), which may include PDU Set QoS parameters and PDU Set Discard Indicator, PDU Set Discard Timer, PDU Set Discard Threshold, PDU Set Discard Importance Level information for performing PDU Set unit packet discarding, and at least one parameter among the above information may be included.

[0106] DU (326) can perform internal settings for setting PDU set QoS parameters and discarding PDU set unit packets based on the information received in step S360. In step S370, DU (326) can transmit a UE context setup response message or a UE context modification response message to CU-CP (322). In step S390, DU (326) can start performing operations related to discarding PDU set unit packets.

[0107] FIG. 4 is a flowchart illustrating the operation of a CU-CP in a RAN Node according to the embodiment of FIG. 3. In step S400, the CU-CP may receive a PDU session setup request or a PDU session modification request from the Core network. In step S405, the CU-CP may check whether the PDU session setup request or the PDU session modification request includes PDU Set QoS parameters. If the PDU Set QoS parameters are not included in step S405, the CU-CP may perform processing of the existing PDU setup request or PDU session modification request and additional procedures in step S410. If the PDU Set QoS parameters are included in step S405, the CU-CP may check whether the PDU Set Integrity Handling Indication (PSIHI) is included in the PDU Set QoS parameters information received in step S415 and is set to operate.

[0108] If PDU Set Integrity Handling Indication (PSIHI) is not included or is not set to operate in step S415, the CU-CP may transmit PDU Set QoS parameters while transmitting a Bearer context setup request message or a Bearer context modification request message to the CU-UP in step S420. The PDU Set QoS parameters may be included in units of DRBs or QoS flows, or may include both units of DRBs and QoS flows. If the PDU Set QoS parameters are included in units of DRBs, the CU-CP may calculate and include PDU Set QoS parameters for each DRB based on the PDU Set QoS parameters values ​​received in units of QoS flows from the core network for the QoS flows included in the DRB when creating the DRB. In step S425, the CU-CP may transmit PDU Set QoS parameters while performing a UE context setup request procedure or a UE context modification request procedure as a DU. PDU Set QoS parameters can be included in DRB units, QoS flow units, or both DRB units and QoS flow units. When PDU Set QoS parameters are included in DRB units, CU-CP can calculate and include PDU Set QoS parameters for each DRB based on the PDU Set QoS parameters values ​​received in QoS flow units from the core network for the QoS flows included in the DRB when creating the DRB.

[0109] If PDU Set Integrity Handling Indication (PSIHI) is included and set to operate in step S415, the CU-CP can determine an entity or function for discarding packets in units of PDU sets in step S430 and determine parameter values ​​for discarding packets in units of PDU sets.

[0110] In step S435, if the CU-UP decides to discard packets in units of PDU sets based on the entity or function for discarding packets in units of PDU sets, in step S440, the CU-CP may transmit PDU Set QoS parameters and parameter values ​​necessary for discarding packets in units of PDU sets while performing a Bearer context setup or modification procedure to the CU-UP. The PDU Set QoS parameters and parameter values ​​necessary for discarding packets in units of PDU sets may be included in units of DRBs or QoS flows, or may include both units of DRBs and QoS flow. In cases where the PDU Set QoS parameters for each DRB or the parameter values ​​required for discarding packets for each PDU set are included, the CU-CP may calculate and include the PDU Set QoS parameters for each DRB and the parameter values ​​required for discarding packets for each PDU set based on the PDU Set QoS parameters values ​​received for each QoS flow from the core network for the QoS flows included in the DRB when creating the DRB. In step S445, the CU-CP may transmit the PDU Set QoS parameters while performing the UE context setup request procedure or the UE context modification request procedure with the DU. The PDU Set QoS parameters may be included for each DRB or QoS flow, or may include both the DRB and the QoS flow.When PDU Set QoS parameters are included in a DRB unit, CU-CP can calculate and include PDU Set QoS parameters for each DRB based on the PDU Set QoS parameters values ​​received in units of QoS flows from the core network for the QoS flows included in the DRB when creating the DRB.

[0111] In step S435, if the CU-UP and the DU decide to discard packets in units of PDU sets according to the entity or function for discarding packets in units of PDU sets, the CU-CP may transmit the PDU Set QoS parameters and the parameter values ​​necessary for discarding packets in units of PDU sets while performing a Bearer context setup or modification procedure to the CU-UP in step S450. The PDU Set QoS parameters and the parameter values ​​necessary for discarding packets in units of PDU sets may be included in units of DRBs or QoS flows, or may include both units of DRBs and QoS flow. In cases where the PDU Set QoS parameters or the parameter values ​​required for discarding packets in units of PDU sets are included in a DRB, the CU-CP may calculate and include the PDU Set QoS parameters for each DRB and the parameter values ​​required for discarding packets in units of PDU sets based on the PDU Set QoS parameter values ​​received in units of QoS flows from the core network for the QoS flows included in the DRB when creating the DRB. In step S455, the CU-CP may transmit the PDU Set QoS parameters and the parameter values ​​required for discarding packets in units of PDU sets while performing the UE context setup request procedure or the UE context modification request procedure with the DU.The PDU Set QoS parameters and the parameter values ​​required to discard packets in units of PDU sets can be included in units of DRBs or QoS flows, or both in units of DRBs and QoS flows. In cases where the PDU Set QoS parameters or the parameter values ​​required to discard packets in units of PDU sets are included in units of DRBs, the CU-CP can calculate and include the PDU Set QoS parameters for each DRB and the parameter values ​​required to discard packets in units of PDU sets based on the PDU Set QoS parameters values ​​received in units of QoS flows from the core network for the QoS flows included in the DRB when creating the DRB.

[0112] In step S435, if it is decided to discard packets in units of PDU sets in the DU based on the entity or function for discarding packets in units of PDU sets, in step S460, the CU-CP may transmit PDU Set QoS parameters values ​​while performing a Bearer context setup or modification procedure to the CU-UP. The PDU Set QoS parameters values ​​may be included in units of DRBs or QoS flows, or may include both units of DRBs and QoS flows. In the case where the PDU Set QoS parameters values ​​are included in units of DRBs, the CU-CP may calculate and include PDU Set QoS parameters values ​​for each DRB based on the PDU Set QoS parameters values ​​received in units of QoS flows from the core network for the QoS flows included in the DRB when creating the DRB. In step S465, the CU-CP may transmit the PDU Set QoS parameters and the parameter values ​​required for discarding packets in units of PDU sets while performing the UE context setup request procedure or the UE context modification request procedure as a DU. The PDU Set QoS parameters and the parameter values ​​required for discarding packets in units of PDU sets may be included in units of DRBs or QoS flows, or may include both units of DRBs and QoS flows.In cases where the PDU Set QoS parameters for each DRB or the necessary parameter values ​​for discarding packets for each PDU set are included, the CU-CP can calculate and include the PDU Set QoS parameters for each DRB and the necessary parameter values ​​for discarding packets for each PDU set based on the PDU Set QoS parameter values ​​received for each QoS flow from the core network for the QoS flows included in the DRB when creating the DRB.

[0113] Meanwhile, FIGS. 5A to 5L are diagrams showing examples of the configuration of a BEARER CONTEXT SETUP REQUEST message used in the E1 interface to set up a bearer context from a CU-CP to a CU-UP within a RAN Node, which is used in step S340 of FIG. 3.

[0114] The information element (IE) names of FIGS. 5A to 5L are merely examples; other names for the same function may be defined, or the values ​​included in the IE may be defined and used differently. Furthermore, some of the information in the (IE) included in FIGS. 5A to 5L may be added to define other existing messages or new messages used in the E1 interface and used. FIGS. 5A to 5L illustrate information used for the embodiment of FIG. 3, and other IE information that is less relevant to the embodiment of FIG. 3 is omitted.

[0115] Figure 5a illustrates an example of the configuration of a BEARER CONTEXT SETUP REQUEST message. The BEARER CONTEXT SETUP REQUEST message may include a Message Type IE used to distinguish existing E1AP (E1 Application Protocol) message types and a gNB-CU-CP UE E1AP ID IE used to distinguish terminals (UEs) on the E1 interface. In addition, a PDU Session Resource to Setup List IE configured for terminal (UE) services may be included.

[0116] Figure 5b illustrates an example of the configuration of a PDU Session Resource to Setup List IE included in a BEARER CONTEXT SETUP REQUEST message. The PDU Session Resource to Setup List IE may include a PDCP Configuration IE, a QoS Flows Information To Be Setup IE, and a DRB QoS IE for each DRB to be set.

[0117] Fig. 5c shows an example of the configuration of the PDCP Configuration IE included in the PDU Session Resource to Setup List IE. In addition to the existing IE information, the PDCP Configuration IE may include information such as the necessary parameters for discarding packets in units of PDU sets, for example, the PDU Set Discard Indicator IE, the PDU Set Discard Timer IE, the PDU Set Discard Threshold IE, and the PDU Set Discard Importance Level IE. The PDU Set Discard Indicator IE is used as an indicator that indicates a discard operation in units of PDU sets, and when included, may include information that indicates the operation, such as 'true'. The PDU Set Discard Timer IE indicates a timer setting value until the packets (or PDUs named) that constitute the PDU set are not transmitted and are discarded, and Fig. 5h shows an example of the configuration of the PDU Set Discard Timer IE. The PDU Set Discard Threshold IE indicates a reference number setting value for discarding (or discarding) packets (or PDUs) constituting a PDU set in order to discard (or discard) packets constituting a PDU set in units of PDU Sets. Fig. 5i shows an example of the configuration of the PDU Set Discard Threshold IE. The PDU Set Discard Importance Level IE indicates a reference value setting value for PDU set importance in order to discard packets constituting a PDU set in units of PDU Sets. Fig. 5j shows an example of the configuration of the PDU Set Discard Importance Level IE.

[0118] FIG. 5d shows an example of the configuration of a QoS Flow QoS Parameters List IE corresponding to the QoS Flows Information To Be Setup IE included in the PDU Session Resource to Setup List IE. The QoS Flow QoS Parameters List IE may include QoS Flow Identifier IE information and QoS Flow Level QoS Parameters IE information used to distinguish each QoS Flow for each QoS Flow, and may include information such as PDU Set Discard Indicator IE, PDU Set Discard Timer IE, PDU Set Discard Threshold IE, and PDU Set Discard Importance Level IE as necessary parameter information for discarding packets in units of PDU sets.

[0119] Figure 5e illustrates an example configuration of a QoS Flow QoS Parameters IE included in a QoS Flow QoS Parameters List IE. The QoS Flow QoS Parameters IE may include Non Dynamic 5QI Descriptor IE information or Dynamic 5QI Descriptor IE information.

[0120] Figure 5e illustrates an example configuration of a Non Dynamic 5QI Descriptor IE included in a QoS Flow QoS Parameters IE. The Non Dynamic 5QI Descriptor IE may include PDU Set QoS Parameters information in addition to existing information.

[0121] Figure 5f illustrates an example configuration of a Dynamic 5QI Descriptor IE included in a QoS Flow QoS Parameters IE. The Dynamic 5QI Descriptor IE may include PDU Set QoS Parameters information in addition to existing information.

[0122] Fig. 5k shows an example of the configuration of the PDU Set QoS Parameters IE included in the Non Dynamic 5QI Descriptor IE or the Dynamic 5QI Descriptor IE. The PDU Set QoS Parameters IE may include PDU Set Delay Budget IE, PDU Set Error Rate IE, and PDU Set Integrated Handling Indication IE information. The PDU Set Delay Budget IE indicates an upper bound of the delay when transmitting packets in units of PDU sets between a terminal (UE) and a UPF. For example, it indicates the delay time from the time of receiving the first packet of a PDU set to the time of receiving all packets in the same PDU set. The PDU Set Error Rate IE indicates an upper bound for the loss in units of PDU sets in a non-congestion state in the network. Fig. 5l shows an example of the configuration of the PDU Set Error Rate IE. The PDU Set error rate value can be composed of a scalar value and an exponent value, and can also be composed in other ways, such as an integer. The PDU Set Integrated Handling Indication IE indicates that the packets included in the PDU Set can be utilized only if all packets belonging to the PDU Set are successfully transmitted.

[0123] Meanwhile, FIGS. 6a and 6b illustrate an example of the configuration of a BEARER CONTEXT MODIFICATION REQUEST message used in the E1 interface to modify a bearer context from a CU-CP to a CU-UP in a RAN Node, which is used in step S340 of FIG. 3. The IE names of FIGS. 6a and 6b are merely examples, and other names for the same function may be defined, or values ​​included in the IE may be defined and used differently. In addition, some of the information in the information elements (IEs) included in FIGS. 6a and 6b may be added and used by defining other existing messages or new messages used in the E1 interface. FIG. 6 illustrates information used for the embodiment of FIG. 3, and other IE information that is less relevant to the embodiment of FIG. 3 is omitted.

[0124] Fig. 6a shows an example of the configuration of a BEARER CONTEXT MODIFICATION REQUEST message. The BEARER CONTEXT MODIFICATION REQUEST message may include a Message Type IE used to distinguish existing E1AP (E1 Application Protocol) message types and a gNB-CU-CP UE E1AP ID IE used to distinguish terminals (UEs) on the E1 interface. In addition, the message may include PDU Session Resource to Setup List IE and PDU Session Resource to Modify List IE information set for terminal (UE) services. The PDU Session Resource to Setup List IE follows the example of the configuration described in Fig. 5b described above and the descriptions of Figs. 5a to 5l described above.

[0125] Fig. 6b shows an example of the configuration of the PDU Session Resource to Modify List IE included in the BEARER CONTEXT MODIFICATION REQUEST message. The PDU Session Resource to Modify List IE may include a PDCP Configuration IE, a QoS Flows Information To Be Setup IE, and a DRB QoS IE for each DRB to be set, and may also include information on the PDCP Configuration IE that needs to be changed and the DRB QoS IE that needs to be changed for each DRB to be changed. The PDCP Configuration IE included in the PDU Session Resource to Modify List IE follows the configuration example described in the aforementioned Fig. 5c and the descriptions of the aforementioned Figs. 5a to 5l. The QoS Flows Information To Be Setup IE included in the PDU Session Resource to Modify List IE follows the configuration example described in the aforementioned Fig. 5d QoS Flow QoS Parameters List IE and the descriptions of the aforementioned Figs. 5a to 5l. The DRB QoS IE included in the PDU Session Resource to Modify List IE follows the configuration example described in the QoS Flow QoS Parameters IE of FIG. 5e described above and the description of FIGS. 5a to 5l described above.

[0126] FIGS. 7a to 7i illustrate examples of the configuration of a UE CONTEXT SETUP REQUEST message used in the F1 or W1 interface to set up a terminal context (UE context) from a CU-CP to a DU within a RAN Node, which is used in step S360 of FIG. 3. The IE names of FIGS. 7a to 7i are merely examples, and other names for the same function may be defined, or values ​​included in the IE may be defined and used differently. In addition, some information of the information elements (IEs) included in FIGS. 7a to 7i may be added and used by defining other existing messages or new messages used in the E1 interface. FIGS. 7a to 7i illustrate information used for the embodiment of FIG. 3, and other IE information that is less relevant to the embodiment of FIG. 3 is omitted.

[0127] Fig. 7a shows an example of the configuration of a UE CONTEXT SETUP REQUEST message. The UE CONTEXT SETUP REQUEST message may include a Message Type IE used to distinguish between existing F1AP (F1 Application Protocol) or W1AP message types and a gNB-CU-CP UE F1AP ID IE used to distinguish between terminals (UEs) on the F1 or W1 interface. In addition, the UE CONTEXT SETUP REQUEST message may include a DRB to Be Setup List IE configured for a terminal (UE) service. The DRB to Be Setup List IE may include information per DRB to be configured and may include configuration information per QoS flow supported by one DRB. The DRB-specific information may include information such as DRB QoS IE information and necessary parameters for discarding packets by PDU set unit. The QoS flow-specific configuration information supported by one DRB may include QoS Flow Identifier IE information and QoS Flow Level QoS Parameters IE information used to distinguish each QoS Flow, and may include necessary parameter information for discarding packets in units of PDU sets.

[0128] This is the parameter information required to discard packets in units of PDU sets, and may include, for example, information such as PDU Set Discard Indicator IE, PDU Set Discard Timer IE, PDU Set Discard Threshold IE, and PDU Set Discard Importance Level IE. The PDU Set Discard Indicator IE is used as an indicator to indicate a discard operation in units of PDU sets, and when included, information indicating an operation such as 'true' may be included. The PDU Set Discard Timer IE indicates a timer setting value until the packets (or names as PDUs) constituting the PDU set are not transmitted and are discarded, and FIG. 7E shows an example of the configuration of the PDU Set Discard Timer IE. The PDU Set Discard Threshold IE indicates a setting value for a standard number of packets (or names as PDUs) constituting the PDU set to be discarded (or discarded) in order to perform discarding in units of PDU sets. Fig. 7f shows an example configuration of the PDU Set Discard Threshold IE. The PDU Set Discard Importance Level IE indicates a PDU set importance criterion setting value for performing discard of a PDU Set unit, and Fig. 7g shows an example configuration of the PDU Set Discard Importance Level IE.

[0129] Figure 7b illustrates an example configuration of a QoS Flow Level QoS Parameters IE that can indicate DRB QoS IE and QoS Flow Level QoS Parameters IE information included in a UE CONTEXT SETUP REQUEST message. The QoS Flow Level QoS Parameters IE can include Non Dynamic 5QI Descriptor IE information or Dynamic 5QI Descriptor IE information.

[0130] Figure 7c illustrates an example configuration of a Non Dynamic 5QI Descriptor IE included in a QoS Flow Level QoS Parameters IE. The Non Dynamic 5QI Descriptor IE may include PDU Set QoS Parameters information in addition to existing information.

[0131] Figure 7d illustrates an example configuration of a Dynamic 5QI Descriptor IE included in a QoS Flow Level QoS Parameters IE. The Dynamic 5QI Descriptor IE may include PDU Set QoS Parameters information in addition to existing information.

[0132] Fig. 7h shows an example of the configuration of the PDU Set QoS Parameters IE included in the Non Dynamic 5QI Descriptor IE or the Dynamic 5QI Descriptor IE. The PDU Set QoS Parameters IE may include PDU Set Delay Budget IE, PDU Set Error Rate IE, and PDU Set Integrated Handling Indication IE information. The PDU Set Delay Budget IE indicates an upper bound of the delay when transmitting packets in units of PDU sets between a terminal (UE) and a UPF. For example, the PDU Set Delay Budget IE may indicate the delay time from the time of receiving the first packet of a PDU set to the time of receiving all packets of the same PDU set. The PDU Set Error Rate IE indicates an upper bound for the loss in units of PDU sets in a non-congestion state in the network. Fig. 7i shows an example of the configuration of the PDU Set Error Rate IE. The above PDU Set Error Rate IE can be composed of a scalar value and an Exponent value for the PDU Set error rate value, and can also be composed in other ways such as an integer. The PDU Set Integrated Handling Indication IE indicates that the packets included in the PDU Set can be utilized only when all packets belonging to the PDU Set are successfully transmitted.

[0133] Meanwhile, FIGS. 8a and 8b illustrate an example of a configuration of a UE CONTEXT MODIFICATION REQUEST message used in the F1 or W1 interface to modify a terminal context (bearer context) from a CU-CP in a RAN Node to a DU, which is used in step S360 of FIG. 3. The IE names of FIGS. 8a and 8b are merely examples, and other names for the same function may be defined, or values ​​included in the IE may be defined and used differently. In addition, some information of the information elements (IEs) included in FIGS. 8a and 8b may be added and used by defining other existing messages or new messages used in the F1 or W1 interface. FIGS. 8a and 8b illustrate information used for the embodiment of FIG. 3, and other IE information that is less relevant to the embodiment of FIG. 3 is omitted.

[0134] Figures 8a and 8b show examples of the configuration of a UE CONTEXT MODIFICATION REQUEST message. The UE CONTEXT MODIFICATION REQUEST message may include a Message Type IE used to distinguish between existing F1AP (F1 Application Protocol) or W1AP message types and a gNB-CU-CP UE F1AP ID IE used to distinguish between terminals (UEs) in the F1 or W1 interface. A DRB to Be Setup List IE configured for a terminal (UE) service may be included. The DRB to Be Setup List IE may include information per DRB to be configured and may include configuration information per QoS flow supported by one DRB. In addition, a DRB to Be Modified List IE that requires a change for a terminal (UE) service may be included. The DRB to Be Modified List IE may include information per DRB to be changed and may include change information per QoS flow supported by one DRB. The DRB-specific information may include information such as DRB QoS IE information and parameters necessary for discarding packets in units of PDU sets, and the DRB QoS IE information follows the configuration example described in the QoS Flow Level QoS Parameters IE of the aforementioned FIG. 7b and the description of the aforementioned FIGS. 7a to 7i. The QoS flow-specific configuration information supported by one DRB may include QoS Flow Identifier IE information and QoS Flow Level QoS Parameters IE information used to distinguish each QoS Flow for each QoS Flow, and may include parameters information necessary for discarding packets in units of PDU sets.The QoS Flow Level QoS Parameters IE information follows the configuration example described in the QoS Flow Level QoS Parameters IE of FIG. 7b described above and the description of FIGS. 7a to 7i described above.

[0135] This is the parameter information required to discard packets in units of PDU sets, and may include, for example, information such as PDU Set Discard Indicator IE, PDU Set Discard Timer IE, PDU Set Discard Threshold IE, and PDU Set Discard Importance Level IE. PDU Set Discard Indicator IE is used as an indicator to indicate discard operation in units of PDU Set, and when included, may include information indicating operation such as 'true'. PDU Set Discard Timer IE indicates a timer setting value until packets (or PDUs named) constituting a PDU set are not transmitted and are discarded, and Fig. 7e shows an example of the configuration of PDU Set Discard Timer IE. PDU Set Discard Threshold IE indicates a setting value for the standard number of packets (or PDUs named) constituting a PDU set to be discarded (or discarded) in order to perform discarding in units of PDU Set. Fig. 7f shows an example configuration of the PDU Set Discard Threshold IE. The PDU Set Discard Importance Level IE indicates a PDU set importance criterion setting value for performing discard of a PDU Set unit, and Fig. 7g shows an example configuration of the PDU Set Discard Importance Level IE.

[0136] FIG. 9 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in a CU-UP and DU of a RAN Node according to an embodiment of the present disclosure. FIG. 9 illustrates a series of procedures for discarding packets belonging to a single PDU set in a DU, discarding packets belonging to the same PDU set stored in the DU, transmitting information about the discarded PDU set to the CU-UP, and causing the CU-UP to discard packets belonging to the corresponding PDU set.

[0137] In step 910 of FIG. 9, if the DU decides to discard packets belonging to PDU Set #2, packets belonging to PDU Set #2 may be discarded. In step 920, the DU may notify the CU-UP that PDU Set #2 has been discarded. The information on the PDU Set to be discarded in step 920 may be transmitted using a packet transmitted to the user plane of the F1-U or W1-U interface between the CU-UP and the DU, or may be transmitted to the CU-UP as an F1AP or W1AP signaling message transmitted to the control plane of the F1-C or W1-C interface, and then as an E1AP signaling message transmitted by the CU-CP to the control plane of the E1 interface. The CU-UP, which receives discarding information of PDU Set #2 from the DU at step 920, discards packets belonging to PDU Set #2 that it is storing at step 930, and can also discard packets belonging to PDU Set #2 that are subsequently received from the UPF.

[0138] FIG. 10 is a sequence diagram showing an operation for performing an operation of discarding packets in units of PDU sets in a CU-UP and DU of a RAN Node according to an embodiment of the present disclosure. Specifically, FIG. 10 specifically shows the operation and signaling procedures of each node or function for supporting, in the case of discarding packets belonging to one PDU set in a DU, discarding packets belonging to the same PDU set stored in the DU, and transmitting information about the discarded PDU set to the CU-UP so that the CU-UP can perform an operation of discarding packets belonging to the corresponding PDU set.

[0139] Referring to FIG. 10, in step S1000, the terminal (1010) performs a procedure for connection to a RAN Node and a core network. At this time, settings for transmitting packets in units of PDU sets and discarding packets in units of PDU sets can be set in the terminal (1010), UPF (1036), CU-CP (1022), CU-UP (1024), and DU (1026) of the RAN Node. In step S1010, the UPF (1036) can transmit packets in which the PDU Set number (#) is set to 2, for example, and transmit six packets with serial numbers from 1 to 6 corresponding to packets belonging to PDU Set 2 to the CU-UP (1024) of the RAN Node. After storing the packets received from the UPF (1036), the CU-UP (1024) can perform a series of processing (for example, packet processing operations in the PDCP layer) and then forward the packets to the DU (1026). In the embodiment of FIG. 10, in step S1020, the CU-UP (1024) can transmit packets with serial numbers 1 to 3 among the six packets belonging to PDU Set 2 received from the UPF (1036) to the DU (1026), and in step S1030, packets with serial numbers 4 to 6 belonging to PDU Set 2 can be stored for transmission to the DU (1026). The serial number of the packet belonging to PDU Set 2 transmitted from the CU-UP (1024) to the DU (1026) in step S1020 may be the same as the serial number of the PDU used when transmitting from the UPF (1036) to the CU-UP (1024), or may be used by setting a different serial number again in the CU-UP (1024). In the embodiment of Fig. 10, the same number is used to indicate this for ease of understanding. The DU (1026) that has received the packets belonging to PDU Set 2 from the CU-UP (1024) may transmit the packets to the terminal (UE, 1010) in step S1040.In step S1040, among the packets belonging to PDU Set 2 received from CU-UP (24), only the packet with serial number 1 has been transmitted, and in step S1050, DU (1026) can store the remaining packets belonging to PDU Set 2 (e.g., packets with serial numbers 2 and 3) for transmission to the terminal (UE, 1010).

[0140] In step S1060, discarding of packet(s) belonging to PDU Set 2 stored in DU (1026) may be determined. In step S1070, DU (1026) may transmit information to CU-UP (1024) that PDU Set 2 has been discarded. At this time, packets belonging to PDU Set 2 stored in DU (1026) may be discarded in step S1080. The discarding decision of PDU Set 2 in DU (1026) may be determined according to the method described above in the present invention (e.g., discarding decision according to expiration of discard timer set for each packet unit). The CU-UP (1024), which has received information from the DU (1026) at step S1070 that PDU Set 2 has been discarded, can discard packets belonging to PDU Set 2 stored in the CU-UP (1024) at step S1090.

[0141] FIGS. 11A to 11C are diagrams showing an example of a configuration of a packet transmitted by the UPF (1036) to the CU-UP (1024) in step S1010 of FIG. 10 to support a PDU Set unit operation, and an example of a configuration of information included in a packet transmitted by the CU-UP (1024) to the DU (1026) in step S1020 to support a PDU Set unit operation. The field names included in FIGS. 11A to 11C are only examples and may be defined as different names for the same function, or the values ​​included in the fields may be defined and used differently. For example, a user plane protocol of an NG-U interface may be used between the UPF (1036) and the CU-UP (1024). For example, a user plane protocol of an F1-U interface may be used between the CU-UP (1024) and the DU (1026). The configuration examples of FIGS. 11a to 11c can also be used in the user plane protocols of other user plane interfaces used in mobile communication networks, such as interfaces such as S1-U, X2-U, Xn-U, and W1-U.

[0142] Figure 11a (a) shows an example of a header configuration of the GTP-U protocol used for packet transmission between UPF (36) and CU-UP (24) and packet transmission between CU-UP (24) and UPF (36). In addition to basic header information, the GTP-U header can define and include an extension header. Figure 11a (b) shows an example of a configuration of an extension header. The extension header can include length information and contents, and can additionally include an extension header.

[0143] Figure 11b (c) shows an example of a frame format configuration included in an extension header used when transmitting packets between UPF (36) and CU-UP (24). In addition to the existing information used when transmitting packets between UPF (36) and CU-UP (24), a 1-bit PDU Set Indicator field may be added for PDU Set unit operation. When the PDU Set Indicator bit is set to '1', 'DL PDU Set Sequence Number', 'PDU Sequence Number within a PDU Set', 'PDU Set Size', 'End PDU in a PDU Set' and 'PDU Set Importance' information may be included, and all information may be included, or one or more information may be included according to a separate definition or setting. 'DL PDU Set Sequence Number' indicates the sequence number of the PDU Set to which the packet being transmitted belongs, and 'PDU Sequence Number within a PDU Set' indicates the sequence number of the packet within the PDU Set of the corresponding packet. 'PDU Set Size' indicates the total size of the PDU Set, and 'End PDU in a PDU Set' indicates an indicator indicating that the packet being transmitted is the last packet transmitted among the packets belonging to the corresponding PDU Set. 'PDU Set Importance' indicates the relative importance level of the PDU Set to which the packet being transmitted belongs with respect to other PDU Sets or a predefined importance level.

[0144] Figure 11c (d) shows an example of a frame format configuration included in an extension header used when transmitting packets between CU-UP (1024) and DU (1026). In addition to the existing information used when transmitting packets between CU-UP (1024) and DU (1026), a 1-bit PDU Set Indicator field may be added for PDU Set unit operation. When the PDU Set Indicator bit is set to '1', 'DL PDU Set Sequence Number', 'PDU Sequence Number within a PDU Set', 'PDU Set Size', 'End PDU in a PDU Set', and 'PDU Set Importance' information may be included, and all information may be included, or one or more information may be included according to a separate definition or setting. 'DL PDU Set Sequence Number' indicates the sequence number of the PDU Set to which the packet being transmitted belongs, and 'PDU Sequence Number within a PDU Set' indicates the sequence number of the packet within the PDU Set of the corresponding packet. 'PDU Set Size' indicates the total size of the PDU Set, and 'End PDU in a PDU Set' indicates an indicator indicating that the packet being transmitted is the last packet transmitted among the packets belonging to the corresponding PDU Set. 'PDU Set Importance' indicates the relative importance level of the PDU Set to which the packet being transmitted belongs with respect to other PDU Sets or a predefined importance level.

[0145] Meanwhile, FIGS. 12a to 12f illustrate an example of the configuration of information included in a packet used by the DU (1026) to transmit PDU Set discarding information to the CU-UP (1024) in step S1070 of FIG. 10 described above according to one embodiment. In order for the DU (1026) to transmit PDU Set discarding information to the CU-UP (1024), the DL DATA DELIVERY STATUS (PDU Type 1) format used in F1-U or W1-U may be used, for example. In addition, the field names included in FIGS. 12a to 12f are just examples, and may be defined as different names for the same function, or the values ​​included in the fields may be defined and used differently. In order for DU (1026) to transmit PDU Set discarding information to CU-UP (1024), other formats may be used, but the information exemplified in FIGS. 12a to 12f may be transmitted. FIGS. 12a to 12f illustrate that the PDU Set discarding information transmitted by DU (1026) to CU-UP (1024) may be transmitted in the following manner, for example, and other methods may be defined and used.

[0146] - Method 1: Discarded PDU Set Sequence Number

[0147] - Method 2: List of discarded PDU Set Sequence Numbers

[0148] - Method 3: First and last sequence numbers of discarded PDU sets (First & Last DL discarded PDU Set Sequence Number)

[0149] - Method 4: First discard PDU Set Sequence Number and discarded block size

[0150] - Method 5: List of discard PDU Set Sequence Number start and block size

[0151] - Method 6: First discard PDU Set Sequence Number & bitmap for the following PDU Set Sequence Number indicating whether the first discard PDU Set and the subsequent PDU Sets are discarded.

[0152] FIG. 12a illustrates an example of a DATA DELIVERY STATUS format of a method (Method 1) for transmitting a discarded PDU Set sequence number to transmit PDU Set discarding information transmitted from a DU (1026) to a CU-UP (1024). In addition to the existing information used when transmitting DATA DELIVERY STATUS from a DU (1026) to a CU-UP (1024), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN' information may be included. The 'DL discard PDU Set SN' may include the sequence number of the PDU Set to be discarded.

[0153] FIG. 12b illustrates an example of the configuration of the DATA DELIVERY STATUS format of a method (Method 2) for transmitting a List of Discarded PDU Set Sequence Numbers (LSN) information to transmit PDU Set discarding information transmitted from the DU (1026) to the CU-UP (1024). In addition to the existing information used when transmitting DATA DELIVERY STATUS from the DU (1026) to the CU-UP (1024), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'Number of DL discard PDU Set SN' and 'DL discard PDU Set SN' information may be included. 'Number of DL discard PDU Set SN' indicates the number of PDU Set serial numbers included, and 'DL discard PDU Set SN' information can be included as many times as the number indicated by 'Number of DL discard PDU Set SN'. 'DL discard PDU Set SN' can include the serial number of the PDU Set to be discarded.

[0154] FIG. 12c illustrates an example of the DATA DELIVERY STATUS format of a method (Method 3) for transmitting PDU Set discarding information from a DU (1026) to a CU-UP (1024) by including information on the first and last sequence numbers (First & Last DL discarded PDU Set Sequence Number) of discarded PDU Sets. In addition to the existing information used when transmitting DATA DELIVERY STATUS from a DU (1026) to a CU-UP (1024), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'DL discard PDU Set SN (last SN)' information may be included. This indicates that all PDU sets from the PDU Set serial number specified in 'DL discard PDU Set SN (first SN)' to the PDU Set serial number specified in 'DL discard PDU Set SN (last SN)' have been discarded.

[0155] FIG. 12d illustrates an example configuration of a DATA DELIVERY STATUS format of a method (Method 4) for transmitting PDU Set discarding information from a DU (1026) to a CU-UP (1024) by including the first sequence number of discarded PDU Sets and the number of consecutive discarded PDU Sets (First discard PDU Set Sequence Number and discarded block size). In addition to the existing information used when transmitting DATA DELIVERY STATUS from a DU (1026) to a CU-UP (1024), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block size' information may be included. This indicates that all PDU sets with consecutive PDU set serial numbers equal to the number of PDU sets in the 'Discarded PDU Set block size' starting from the PDU set serial number specified in 'DL discard PDU Set SN (first SN)' have been discarded.

[0156] Fig. 12e illustrates an example of the DATA DELIVERY STATUS format of a method (Method 5) for transmitting discarding information from a DU (1026) to a CU-UP (1024) by including the first sequence number of discarded PDU Sets and a list of consecutive discarded PDU Set numbers (List of discard PDU Set Sequence Number start and block size). In addition to the existing information used when transmitting DATA DELIVERY STATUS from a DU (1026) to a CU-UP (1024), a 1-bit 'DL Discard PDU Set' field may be added to indicate that discarding information per PDU Set is included. When the 'DL Discard PDU Set' bit is set to '1', 'Number of DL discard PDU Set SN block', 'DL discard PDU Set SN (first SN)', and 'Discarded PDU Set block size' information may be included. 'Number of DL discard PDU Set SN block' indicates the number of 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block size' included, and indicates that all PDU Sets having consecutive PDU Set serial numbers equal to the number of PDU sets of 'Discarded PDU Set block size' from the PDU Set serial number specified in 'DL discard PDU Set SN (first SN)' are discarded.

[0157] FIG. 12f illustrates an example of a DATA DELIVERY STATUS format according to a method (Method 6) for transmitting PDU Set discarding information transmitted from a DU (1026) to a CU-UP (1024) by including information such as the first sequence number of discarded PDU Sets and a bitmap (First discard PDU Set Sequence Number & bitmap for the following PDU Set Sequence Number) indicating whether or not to discard the PDU Sets that follow. In addition to the existing information used when transmitting DATA DELIVERY STATUS from a DU (1026) to a CU-UP (1024), a 1-bit 'DL Discard PDU Set' field indicating that it includes PDU Set unit discarding information may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block bitmap' information may be included. 'DL discard PDU Set SN (first SN)' indicates the first PDU Set sequence number to be discarded. 'Discarded PDU Set block bitmap' is mapped to each bit of the block bitmap in the order of the succeeding PDU set sequence numbers to indicate whether the PDU Set of the corresponding PDU set sequence number is discarded.

[0158] Meanwhile, FIG. 13 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in a CU-UP and DU of a RAN Node according to an embodiment of the present disclosure. FIG. 13 illustrates a series of procedures for discarding packets belonging to a single PDU set in a CU-UP, discarding packets belonging to the same PDU set stored in the CU-UP, and transmitting information about the discarded PDU set to the DU, thereby discarding packets belonging to the corresponding PDU set in the DU.

[0159] In step 1310 of FIG. 13, if the CU-UP decides to discard packets belonging to PDU Set #2, packets belonging to PDU Set #2 may be discarded. In step 1320, the CU-UP may inform the DU that PDU Set #2 has been discarded. The information on the PDU Set to be discarded in step 1320 may be conveyed using a packet transmitted to the user plane of the F1-U or W1-U interface between the CU-UP and the DU, or may be conveyed to the DU by an E1AP signaling message transmitted by the CU-UP to the control plane of the E1 interface, and then by the CU-CP to the DU by an F1AP or W1AP signaling message transmitted to the control plane of the F1-C or W1-C interface. The DU, which receives discarding information of PDU Set #2 from the CU-UP at step 1320, discards packets belonging to PDU Set #2 that it is storing at step 1330, and can also discard packets belonging to PDU Set #2 that are subsequently received from the CU-UP.

[0160] FIG. 14 is a sequence diagram showing an operation for performing an operation of discarding packets in units of PDU sets in a CU-UP and DU of a RAN Node according to an embodiment of the present disclosure. Specifically, FIG. 14 specifically shows the operation and signaling procedures of each node or function for supporting, in the case where a packet belonging to one PDU set is discarded in a CU-UP, discarding packets belonging to the same PDU set stored in the CU-UP, and transmitting information about the discarded PDU set to the DU so that the DU can perform an operation of discarding packets belonging to the corresponding PDU set.

[0161] Referring to FIG. 14, in step S1400, the terminal (1410) performs a procedure for connection to the RAN Node and the core network. At this time, settings for transmitting packets in units of PDU sets and discarding packets in units of PDU sets are set in the terminal (1410), UPF (1436), CU-CP (1422), CU-UP (1424), and DU (1426) of the RAN Node. In step S1410, the UPF (1436) may transmit packets in which the PDU Set number (#) is set to 2, for example, and transmit six packets with serial numbers from 1 to 6 corresponding to packets belonging to PDU Set 2 to the CU-UP (24) of the RAN Node. When transmitting a packet from the UPF (1436) to the CU-UP (1424) in step S1410, an example of the configuration of information included in the transmitted packet may be included to support a PDU Set unit operation as illustrated in FIGS. 11a to 11c. The CU-UP (1424) stores the packet received from the UPF (1436), and then performs a series of processing (for example, packet processing operation in the PDCP layer), after which the CU-UP (1424) can transmit the packet to the DU (1426). In the embodiment of FIG. 14, among the six packets belonging to PDU Set 2 received from the UPF (1436) in step S1420, packets with serial numbers 1 to 3 may be transmitted to the DU (1426), and packets with serial numbers 4 to 6 belonging to PDU Set 2 may be stored in step S1430 for transmission to the DU (1426). The serial number of the packet belonging to PDU Set 2 transmitted from CU-UP (1424) to DU (1426) in step S1420 may be the same as the serial number of the PDU used when transmitting from UPF (1436) to CU-UP (1424), or may be used by setting a different serial number again in CU-UP (1424).When transmitting a packet from CU-UP (1424) to DU (1426) in step S1420, an example of the configuration of information included in the transmitted packet may be included to support PDU Set unit operation as illustrated in FIGS. 11a to 11c. In the embodiment of FIG. 14, the same numbers are used to indicate the packets for easy understanding. DU (1426), which receives packets belonging to PDU Set 2 from CU-UP (1424), can transmit the packets to terminal (UE, 1410). In step S1440, among the packets belonging to PDU Set 2 received from CU-UP (24), only the packet with serial number 1 has been transmitted, and in step S1450, DU (26) can store the remaining packets belonging to PDU Set 2 (e.g., packets with serial numbers 2 and 3) for transmission to the terminal (UE, 1410).

[0162] If discarding of packet(s) belonging to PDU Set 2 stored in CU-UP (1424) is decided in step S1460, CU-UP (1424) can transmit information that PDU Set 2 has been discarded to DU (1426) in step S1470. At this time, packets belonging to PDU Set 2 stored in CU-UP (1424) can be discarded in step S1480. The discarding decision of PDU Set 2 in CU-UP (1424) can be decided according to the method described above in the present invention (e.g., discarding decision according to expiration of discard timer set for each packet unit). In step S1470, the DU (1426), which has received information from the CU-UP (1424) that PDU Set 2 has been discarded, can discard packets belonging to PDU Set 2 stored in the DU (1426) in step S1490.

[0163] Meanwhile, FIGS. 15a to 15f illustrate an example of the configuration of information included in a packet used by the CU-UP (1424) to transmit PDU Set discarding information to the DU (1426) in step S1470 of FIG. 14 according to one embodiment. In order for the CU-UP (1424) to transmit PDU Set discarding information to the DU (1426), the DL DL USER DATA (PDU Type 0) format used in F1-U or W1-U may be used, for example. In addition, the field names included in FIGS. 15a to 15f are just examples, and may be defined as different names for the same function, or the values ​​included in the fields may be defined and used differently. In order for CU-UP (1424) to transmit PDU Set discarding information to DU (1426), other formats may be used, but may be transmitted including the information exemplified in FIGS. 15a to 15f. FIGS. 15a to 15f illustrate that the PDU Set discarding information transmitted by CU-UP (1424) to DU (1426) may be transmitted in the following manner, for example, and other methods may be defined and used.

[0164] - Method 1: Discarded PDU Set Sequence Number

[0165] - Method 2: List of discarded PDU Set Sequence Numbers

[0166] - Method 3: First and last sequence numbers of discarded PDU sets (First & Last DL discarded PDU Set Sequence Number)

[0167] - Method 4: First discard PDU Set Sequence Number and discarded block size

[0168] - Method 5: List of discard PDU Set Sequence Number start and block size

[0169] - Method 6: First discard PDU Set Sequence Number & bitmap for the following PDU Set Sequence Number indicating whether the first discard PDU Set and the subsequent PDU Sets are discarded.

[0170] FIG. 15a illustrates an example of the configuration of the DL USER DATA format of the method (Method 1) for transmitting, including the Discarded PDU Set Sequence Number, PDU Set discarding information transmitted from the CU-UP (1424) to the DU (1426). In addition to the existing information used when transmitting DL USER DATA from the CU-UP (1424) to the DU (1426), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN' information may be included. The 'DL discard PDU Set SN' may also include the sequence number of the PDU Set to be discarded.

[0171] FIG. 15b illustrates an example of the configuration of the DL USER DATA format of a method (Method 2) for transmitting, including a list of discarded PDU Set Sequence Numbers, information on discarded PDU Sets to transmit PDU Set discarding information from a CU-UP (1424) to a DU (1426). In addition to the existing information used when transmitting DL USER DATA from a CU-UP (1424) to a DU (1426), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'Number of DL discard PDU Set SN' and 'DL discard PDU Set SN' information may be included. 'Number of DL discard PDU Set SN' indicates the number of PDU Set serial numbers included, and 'DL discard PDU Set SN' information can be included as many times as the number indicated by 'Number of DL discard PDU Set SN'. 'DL discard PDU Set SN' can include the serial number of the PDU Set to be discarded.

[0172] FIG. 15c illustrates an example of the DL USER DATA format of a method (Method 3) for transmitting PDU Set discarding information from a CU-UP (1424) to a DU (1426) by including information on the first and last sequence numbers (First & Last DL discarded PDU Set Sequence Number) of discarded PDU Sets. In addition to the existing information used when transmitting DL USER DATA from a CU-UP (1424) to a DU (1426), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'DL discard PDU Set SN (last SN)' information may be included. This indicates that all PDU sets from the PDU Set serial number specified in 'DL discard PDU Set SN (first SN)' to the PDU Set serial number specified in 'DL discard PDU Set SN (last SN)' have been discarded.

[0173] FIG. 15d illustrates an example of the DL USER DATA format of a method (Method 4) for transmitting PDU Set discarding information transmitted from a CU-UP (1424) to a DU (1426) by including the first sequence number of discarded PDU Sets and the number of consecutive discarded PDU Sets (First discard PDU Set Sequence Number and discarded block size). In addition to the existing information used when transmitting DL USER DATA from a CU-UP (24) to a DU (26), a 1-bit 'DL Discard PDU Set' field indicating that PDU Set unit discarding information is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block size' information may be included. This indicates that all PDU sets with consecutive PDU set serial numbers equal to the number of PDU sets in the 'Discarded PDU Set block size' starting from the PDU set serial number specified in 'DL discard PDU Set SN (first SN)' have been discarded.

[0174] FIG. 15e illustrates an example of the DL USER DATA format of a method (Method 5) for transmitting discarded PDU Set information from a CU-UP (1424) to a DU (1426), including the first sequence number of discarded PDU Sets and a list of consecutive discarded PDU Set numbers (List of discard PDU Set Sequence Number start and block size). In addition to the existing information used when transmitting DL USER DATA from a CU-UP (1424) to a DU (1426), a 1-bit 'DL Discard PDU Set' field indicating that discarding information per PDU Set is included may be added. When the 'DL Discard PDU Set' bit is set to '1', 'Number of DL discard PDU Set SN block', 'DL discard PDU Set SN (first SN)', and 'Discarded PDU Set block size' information may be included. 'Number of DL discard PDU Set SN block' indicates the number of 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block size' included, and indicates that all PDU Sets having consecutive PDU Set serial numbers equal to the number of PDU sets of 'Discarded PDU Set block size' from the PDU Set serial number specified in 'DL discard PDU Set SN (first SN)' are discarded.

[0175] FIG. 15f illustrates an example of a DL USER DATA format according to a method (Method 6) for transmitting PDU Set discarding information transmitted from a CU-UP (1424) to a DU (1426) by including information such as the first sequence number of discarded PDU Sets and a bitmap (First discard PDU Set Sequence Number & bitmap for the following PDU Set Sequence Number) indicating whether or not to discard the PDU Sets that follow. In addition to the existing information used when transmitting DL USER DATA from a CU-UP (1424) to a DU (1426), a 1-bit 'DL Discard PDU Set' field indicating that it includes PDU Set unit discarding information may be added. When the 'DL Discard PDU Set' bit is set to '1', 'DL discard PDU Set SN (first SN)' and 'Discarded PDU Set block bitmap' information may be included. 'DL discard PDU Set SN (first SN)' indicates the first PDU Set sequence number to be discarded. 'Discarded PDU Set block bitmap' is mapped to each bit of the block bitmap in the order of the succeeding PDU set sequence numbers to indicate whether the PDU Set of the corresponding PDU set sequence number is discarded.

[0176] Meanwhile, FIG. 16 is a diagram illustrating an operation for performing an operation of discarding packets in units of PDU sets in a CU-UP and a DU of a RAN Node according to an embodiment of the present disclosure. FIG. 16 illustrates a series of procedures for determining whether to discard PDU Set units in a CU-UP or a DU based on PDU Set Integrated Handling Indication (PSIHI) information transmitted together with PDU Set information in packets transmitted from a UPF to a CU-UP or from a CU-UP to a DU, and performing discarding in units of PDU Sets.

[0177] In step 1610 of FIG. 16, the SMF may transmit PDU Set QoS parameters, for example, PDU Set Delay Budget and PDU Set Error Rate information, for each QoS flow of a PDU session through the AMF. The CU-CP may determine whether to set resources for a QoS flow service of a PDU session including PDU Set QoS parameters from the SMF / AMF, and in step 1620, the CU-CP may transmit PDU Set QoS parameters information to be set for each QoS flow or DRB to the CU-UP. In step 1630, the CU-CP may transmit PDU Set QoS parameters information to be set for each QoS flow or DRB to the CU-UP. In steps 1620 and 1630, the CU-CP may also transmit additional information to support discarding at the PDU Set level, for example, a PDU set discard timer value. In step 1640-1, when a packet is transmitted from the UPF to the CU-UP, PDU Set Integrated Handling Indication (PSIHI) information may be transmitted together for each PDU Set. In step 1640-2, when the CU-UP transmits a packet to the DU, PDU Set Integrated Handling Indication (PSIHI) information may be transmitted together for each PDU Set. The PDU Set Integrated Handling Indication (PSIHI) information set for each PDU Set may indicate that if at least one packet belonging to the corresponding PDU Set is not successfully transmitted, the remaining packets belonging to the corresponding PDU Set are meaningless.Therefore, in steps 1650-1 and 1650-2, if the CU-UP and the DU discard at least one packet belonging to a PDU Set for which the PDU Set Integrated Handling Indication (PSIHI) is set, they will also discard other packets belonging to the PDU Set. In addition, the CU-UP can convey information about the discarded PDU Set to the DU, and the DU can convey information about the discarded PDU Set to the CU-UP.

[0178] Meanwhile, FIGS. 17a and 17b are diagrams showing an example of the configuration of a packet transmitted by the UPF to the CU-UP to support the PDU Set unit operation in step 1640-1 of FIG. 16 and an example of the configuration of information included in a packet transmitted by the CU-UP to support the PDU Set unit operation in DU in step 1640-2. The field names included in FIGS. 17a and 17b are only examples and may be defined as different names for the same function, or the values ​​included in the fields may be defined and used differently. For example, a user plane protocol of the NG-U interface may be used between the UPF and the CU-UP, and for example, a user plane protocol of the F1-U interface may be used between the CU-UP and the DU. The configuration examples of FIGS. 17a and 17b may also be used in the user plane protocol of other user plane interfaces used in mobile communication networks, for example, interfaces such as S1-U, X2-U, Xn-U, and W1-U.

[0179] Fig. 17a shows an example of a frame format included in an Extension Header used when transmitting packets between a UPF and a CU-UP. In addition to the existing information used when transmitting packets between a UPF and a CU-UP, a 1-bit PDU Set Indicator field may be added for PDU Set unit operation. When the PDU Set Indicator bit is set to '1', 'DL PDU Set Sequence Number', 'PDU Sequence Number within a PDU Set', 'PDU Set Size', 'End PDU in a PDU Set', 'PDU Set Integrated Handling Indication (PSIHI)', and 'PDU Set Importance' information may be included, and all information may be included, or one or more information may be included according to a separate definition or setting. 'DL PDU Set Sequence Number' indicates the sequence number of the PDU Set to which the packet being transmitted belongs, 'PDU Sequence Number within a PDU Set' indicates the sequence number of the packet within the PDU Set of the corresponding packet. 'PDU Set Size' indicates the total size of the PDU Set, and 'End PDU in a PDU Set' indicates an indicator indicating that the packet being transmitted is the last packet transmitted among the packets belonging to the corresponding PDU Set.'PDU Set Integrated Handling Indication (PSIHI)' indicates that if at least one packet belonging to the corresponding PDU Set is not successfully transmitted, the remaining packets belonging to the corresponding PDU Set are meaningless, and 'PDU Set Importance' indicates the relative importance level of the PDU Set to which the transmitted packet belongs, or a predefined importance level.

[0180] Fig. 17b shows an example of a frame format included in an Extension Header used when transmitting packets between a CU-UP and a DU. In addition to the existing information used when transmitting packets between a CU-UP and a DU, a 1-bit PDU Set Indicator field may be added for PDU Set unit operation. When the PDU Set Indicator bit is set to '1', 'DL PDU Set Sequence Number', 'PDU Sequence Number within a PDU Set', 'PDU Set Size', 'End PDU in a PDU Set', 'PDU Set Integrated Handling Indication (PSIHI)', and 'PDU Set Importance' information may be included, and all information may be included, or one or more information may be included according to a separate definition or setting. 'DL PDU Set Sequence Number' indicates the sequence number of the PDU Set to which the packet being transmitted belongs, 'PDU Sequence Number within a PDU Set' indicates the sequence number of the packet within the PDU Set of the corresponding packet. 'PDU Set Size' indicates the total size of the PDU Set, and 'End PDU in a PDU Set' indicates an indicator indicating that the packet being transmitted is the last packet transmitted among the packets belonging to the corresponding PDU Set.'PDU Set Integrated Handling Indication (PSIHI)' indicates that if at least one packet belonging to the corresponding PDU Set is not successfully transmitted, the remaining packets belonging to the corresponding PDU Set are meaningless, and 'PDU Set Importance' indicates the relative importance level of the PDU Set to which the transmitted packet belongs, or a predefined importance level.

[0181] FIG. 18 is a block diagram showing the configuration of a RAN Node (e.g., a base station) according to an embodiment of the present invention. As shown in the drawing, the RAN Node is configured to include an RF processing unit (1810), a baseband processing unit (1820), a backhaul communication unit (1830), a storage unit (1840), and a control unit (1850). If the RAN Node is separated into a CU (Central Unit) and a DU (Distributed Unit), a configuration of blocks other than those included in FIG. 18 is also possible. For example, the RF processing unit (1810) and the baseband processing unit (1820) may be configured to include a control unit, a storage unit, and a backhaul communication unit for communication with the CU in the DU, and for example, the backhaul communication unit (1830) may be configured to include a control unit, a storage unit, and a backhaul communication unit for communication with the DU in the CU.

[0182] The RF processing unit (1810) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (1810) up-converts the baseband signal provided from the baseband processing unit (1820) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1810) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may have multiple antennas. In addition, the RF processing unit (1810) may include multiple RF chains. Furthermore, the RF processing unit (1810) may perform beamforming. For the beamforming, the RF processing unit (1810) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The above RF processing unit (1810) can perform a downlink MIMO operation by transmitting one or more layers.

[0183] The baseband processing unit (1820) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1820) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1820) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1810). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1820) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1820) divides the baseband signal provided from the RF processing unit (1810) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (1820) and the RF processing unit (1810) transmit and receive signals as described above. Accordingly, the baseband processing unit (1820) and the RF processing unit (1810) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0184] The backhaul communication unit (1830) provides an interface for communicating with other nodes within the network. The backhaul communication unit (1830) converts a bit stream transmitted from the primary RAN Node to other nodes, such as auxiliary base stations and core networks, into a physical signal, and converts a physical signal received from the other nodes into a bit stream.

[0185] The storage unit (1840) stores data such as basic programs, application programs, and configuration information for the operation of the primary RAN Node. In particular, the storage unit (1840) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (1840) can store information that serves as a basis for determining whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (1840) provides the stored data at the request of the control unit (1850).

[0186] The control unit (1850) controls the overall operations of the RAN Node. For example, the control unit (1850) transmits and receives signals through the baseband processing unit (1820) and the RF processing unit (1810) or through the backhaul communication unit (1830). In addition, the control unit (1850) records and reads data in the storage unit (1840). For this purpose, the control unit (1850) may include at least one processor. In addition, the control unit (1850) may be used to control the overall operations of the RAN Node.

[0187] According to one embodiment of the present disclosure, the control unit (1850) can control to perform an operation of discarding packets in units of PDU sets. When the RAN Node is divided into CU and DU, the control unit (1850) can control to generate and transmit a message transmitted from CU-CP to CU-UP or from CU-CP to DU. Fig. 19 is a block diagram illustrating an example of the structure of a terminal (UE) according to one embodiment of the present invention. Referring to the drawing, the terminal includes an RF (Radio Frequency) processing unit (1910), a baseband processing unit (1920), a storage unit (1930), and a control unit (1940). The RF processing unit (1910) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (1910) up-converts the baseband signal provided from the baseband processing unit (1920) into an RF band signal and transmits the up-converted signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1910) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is shown, but the terminal may have multiple antennas. In addition, the RF processing unit (1910) may include multiple RF chains. Furthermore, the RF processing unit (1910) may perform beamforming. For the beamforming, the RF processing unit (1910) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements.Additionally, the RF processing unit can perform MIMO and receive multiple layers when performing MIMO operation.

[0188] The baseband processing unit (1920) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1920) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1920) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1910). For example, in the case of an orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (1920) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols by performing an inverse fast Fourier transform (IFFT) operation and inserting a cyclic prefix (CP). In addition, when receiving data, the baseband processing unit (1920) divides the baseband signal provided from the RF processing unit (1910) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.

[0189] The baseband processing unit (1920) and the RF processing unit (1910) transmit and receive signals as described above. Accordingly, the baseband processing unit (1920) and the RF processing unit (1910) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (1920) and the RF processing unit (1910) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (1920) and the RF processing unit (1910) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.

[0190] The storage unit (1930) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In addition, the storage unit (1930) provides the stored data upon request from the control unit (1940).

[0191] The control unit (1940) controls the overall operations of the terminal. For example, the control unit (1940) transmits and receives signals through the baseband processing unit (1920) and the RF processing unit (1910). In addition, the control unit (1940) records and reads data in the storage unit (1940). For this purpose, the control unit (1940) may include at least one processor. For example, the control unit (1940) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0192] Meanwhile, according to one embodiment of the present disclosure, a method for processing a control signal in a communication system is characterized by including: a step of receiving a first control signal between a CU-CP (Central Unit-Control Plane) and a CU-UP (Central Unit-User Plane) in a separated base station, and between the CU-CP and a DU (Distributed Unit); a step of processing the received first control signal; and a step of transmitting a second signal generated based on the processing. In addition, the method is characterized by including a step of transmitting a third control signal between the CU-UP and the DU after performing a PDCP SDU discard operation in units of PDU sets in the CU-UP and the DU; and a step of performing a PDCP SDU discard operation in units of PDU sets after processing the received third control signal.

[0193] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples intended to facilitate easy explanation of the technical content of the present invention and aid understanding thereof, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical concepts of the present invention are possible in addition to the embodiments disclosed herein.

Claims

1. A method performed by a base station in a wireless communication system, A step of transmitting at least one piece of information for performing protocol data unit (PDU) set discarding from a central unit (CU)-control plane (CP) to a CU-user plane (UP), wherein the at least one piece of information for discarding the PDU set includes discarding timer information; and A method comprising: performing PDU set discarding by the CU-CP; 2. In paragraph 1, A step of transmitting a message including information about the setting of the PDU set discarding to a distributed unit (DU) by the CU-CP; and A method characterized by further comprising: a step of transmitting, by the DU, to the CU-UP, at least one parameter associated with the PDU set discarding; 3. In paragraph 1, A method characterized in that the above discarding timer information is transmitted as included in packet data convergence protocol (PDCP) configuration information.

4. In paragraph 1, The above message containing information about the setting of the above PDU set discarding, A method characterized by at least one of a user equipment (UE) context setup request message or a UE context modification request message.

5. In paragraph 1, Information about the setting of the above PDU set discarding is: A directive indicating that the above PDU set discarding setting includes information about the setting, The number of at least one PDU set for performing the above PDU set discarding, or A method characterized by including at least one sequence number (SN) of at least one PDU set for performing the above PDU set discarding.

6. In paragraph 1, A method, further comprising: receiving, from an access and mobility management function (AMF) entity, a message including at least one PDU set quality of service (QoS) parameter with a PDU set integrity handling indication (PSIHI) set; 7. In paragraph 5, A step of applying the PSIHI according to a PDU set for a QoS flow based on a message including at least one QoS parameter for which the PSIHI is set; and A method characterized by further comprising: a step of determining whether to discard the PDU set based on the PSIHI; 8. In paragraph 1, A step of determining discarding for an arbitrary PDU set by the CU-UP - at least one downlink packet included in the arbitrary PDU set is stored in a buffer of the CU-UP; A method characterized by further comprising: a step of instructing, by the CU-UP, the DU to discard at least one downlink packet included in the arbitrary PDU set and stored in the buffer of the DU; 9. In a base station in a wireless communication system, Controlling to transmit at least one piece of information for performing protocol data unit (PDU) set discarding from a central unit (CU)-control plane (CP) to a CU-user plane (UP), wherein at least one piece of information for discarding the PDU set includes discarding timer information. A base station including a control unit that controls to perform the PDU set discarding by the CU-CP.

10. In paragraph 9, The above control unit, Transmitting a message including information about the setting of the PDU set discarding to a distributed unit (DU) by the CU-CP, A base station characterized in that it controls to transmit at least one parameter associated with the PDU set discarding to the CU-UP by the DU.

11. In paragraph 9, A base station characterized in that the above discarding timer information is transmitted as included in packet data convergence protocol (PDCP) configuration information.

12. In paragraph 9, The above message containing information about the setting of the above PDU set discarding, A base station characterized by at least one of a user equipment (UE) context setup request message or a UE context modification request message.

13. In paragraph 9, Information about the setting of the above PDU set discarding is: A directive indicating that the above PDU set discarding setting includes information about the setting, The number of at least one PDU set for performing the above PDU set discarding, or A base station characterized by including at least one sequence number (SN) of at least one PDU set for performing the above PDU set discarding.

14. In paragraph 9, further comprising a transceiver; The above control unit, Controlling the reception of a message including at least one PDU set quality of service (QoS) parameter with a PDU set integrity handling indication (PSIHI) set from an access and mobility management function (AMF) entity through the transceiver, Based on a message including at least one QoS parameter for which the PSIHI is set, control to apply the PSIHI according to the PDU set for the QoS flow, A base station characterized by controlling whether to discard the PDU set based on the PSIHI.

15. In paragraph 9, The above control unit, By the above CU-UP, control is made to decide discarding for an arbitrary PDU set, and - at least one downlink packet included in the arbitrary PDU set is stored in the buffer of the CU-UP, A base station characterized in that the control is performed so as to instruct the DU, by the CU-UP, to discard at least one downlink packet included in the arbitrary PDU set and stored in the buffer of the DU.

Citation Information

Patent Citations

  • Fuel measurement display system

    KR1020220136809A

  • Buffer handling utilizing in-band control signaling

    WO2019003088A1