Method and device for operating device in wireless communication system
The method and device facilitate efficient utilization of devices to assist the CU-UP side of a base station, addressing high-speed and low-latency packet processing challenges in 6G systems by setting up and updating E1 interfaces, enhancing operational efficiency and security.
Patent Information
- Application Number
- PCT/KR2025/001295
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-31
- Filing Date
- 2025-01-23
- Publication Date
- 2025-08-07
AI Technical Summary
Existing wireless communication systems face challenges in efficiently utilizing devices to assist the computational function of the CU-UP side of a base station, particularly in 6G communication systems, which require high-speed and low-latency packet processing.
A method and device for setting up and updating an E1 interface to utilize a device capable of assisting the CU-UP side operation function of a base station, including steps to check for the presence and performance of such devices and transmit relevant information between the CU-UP and CU-CP.
Enables low-latency and high-speed packet processing, enhances security, and facilitates context setting and updates, thereby improving the operational efficiency and security of the base station.
Smart Images

Figure KR2025001295_07082025_PF_FP_ABST
Abstract
Description
Method and device for operating a device in a wireless communication system
[0001] The present disclosure relates to a setting method in a control plane for utilizing a device capable of assisting a CU-UP (Central Unit-User Plane) side operation function of a base station in a wireless communication system.
[0002] Looking back at the evolution of wireless communication over successive generations, technologies have primarily been developed for human-facing services such as voice, multimedia, and data. With the commercialization of 5G (5th-generation) communication systems, an explosive increase in connected devices is expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction equipment, and factory equipment. Mobile devices are expected to evolve into diverse form factors, including augmented reality glasses, virtual reality headsets, and holographic devices. In the 6th-generation (6G) era, efforts are being made to develop improved 6G communication systems to connect hundreds of billions of devices and objects and provide diverse services. For this reason, 6G communication systems are often referred to as "beyond 5G."
[0003] The 6G communication system, expected to be realized around 2030, will have a maximum transmission speed of terabytes per second (i.e., 1,000 gigabits per second) and a wireless latency of 100 microseconds (μsec). In other words, compared to 5G, the transmission speed in a 6G communication system will be 50 times faster, while the wireless latency will be reduced to one-tenth.
[0004] To achieve these high data rates and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz band (e.g., from 95 gigahertz (GHz) to 3 terahertz (THz)). Compared to the millimeter wave (mmWave) band introduced in 5G, the terahertz band is expected to experience more severe path loss and atmospheric absorption, making it more crucial to ensure signal reach, or coverage, in this band. Key technologies to ensure coverage include radio frequency (RF) components, antennas, new waveforms that offer better coverage than OFDM (orthogonal frequency division multiplexing), beamforming, and multiple antenna transmission technologies such as massive multiple-input and multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS) are being discussed to improve the coverage of terahertz band signals.
[0005] In addition, in order to improve frequency efficiency and system network, 6G communication systems are developing full duplex technology that utilizes the same frequency resources for uplink and downlink at the same time; network technology that integrates satellites and high-altitude platform stations (HAPS); network structure innovation technology that supports mobile base stations and enables optimization and automation of network operation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources (mobile edge computing (MEC), cloud, etc.). In addition, efforts are being made to further strengthen connectivity between devices, further optimize networks, promote softwareization of network entities, and increase the openness of wireless communications through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe use of data, and the development of technologies for maintaining privacy.
[0006] Research and development of these 6G communication systems are expected to enable a new level of hyper-connected experience (the next hyper-connected experience) through the hyper-connectivity of 6G communication systems, which encompass not only connections between things but also connections between people and things. Specifically, 6G communication systems are expected to enable services such as truly immersive extended reality (Truly Immersive XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems through enhanced security and reliability, will find application in diverse fields such as industry, medicine, automobiles, and home appliances.
[0007] Meanwhile, the need for settings in the control plane for utilizing a device that can assist the computational function of the CU-UP (Central Unit-User Plane) side of a base station in a wireless communication system is emerging.
[0008] The present disclosure proposes a method for enabling configuration in a control plane for utilizing a device capable of assisting a CU-UP (Central Unit-User Plane) side computational function of a base station in a wireless communication system.
[0009] According to one embodiment, a method performed by a central unit-user plane (CU-UP) of a base station in a wireless communication system may include: a step of checking whether a device connected to the CU-UP of the base station and capable of assisting a computational function of the CU-UP of the base station exists; and a step of transmitting, to a central unit-control plane (CU-CP) of the base station, a first message including first information indicating the existence of the device and second information regarding performance of the device, if the device connected to the CU-UP of the base station exists.
[0010] According to one embodiment, a method performed by a central unit-control plane (CU-CP) of a base station in a wireless communication system may include the steps of: receiving a first message from a central unit-user plane (CU-UP) of the base station, the first message including first information indicating the presence of a device capable of assisting an operational function of the CU-UP of the base station and second information regarding performance of the device; and identifying the device connected to the CU-UP of the base station based on the first message.
[0011] According to one embodiment, in a wireless communication system, a base station including a central unit-user plane (CU-UP) comprises a transceiver; and at least one processor, wherein the at least one processor is configured to determine whether a device capable of assisting a computational function is present in connection with the CU-UP of the base station, and, if the device is present in connection with the CU-UP of the base station, control to transmit a request message to a central unit-control plane (CU-CP) of the base station for setting up an E1 interface to transmit information indicating the presence of the device and information regarding performance of the device.
[0012] According to one embodiment, in a wireless communication system, a base station including a central unit-control plane (CU-CP) of a base station, comprising: a transceiver; and at least one processor, wherein the at least one processor is configured to control transmission of a request message to a CU-UP of the base station for setting up an E1 interface to connect the CU-UP of the base station and the CU-CP of the base station, the request message indicating the presence of a device that is connected to the CU-UP of the base station and can assist a computational function of the CU-UP of the base station and information regarding performance of the device.
[0013] A method and device according to an embodiment of the present disclosure can enable E1 interface setup and update for use of a device that can assist a CU-UP (central unit-user plane) side computational function of a base station in a wireless communication system.
[0014] A method and device according to an embodiment of the present disclosure can enable bearer context setup and update for utilizing a device that can assist a central unit-user plane (CU-UP) side operation function of a base station in a wireless communication system.
[0015] The method and device according to the embodiment of the present disclosure can enable low-latency and high-speed packet processing by utilizing a device that can assist the CU-UP (central unit-user plane) side computational function of a base station in a wireless communication system.
[0016] The method and device according to an embodiment of the present disclosure can enable context setting including security information for each CU-UP (central unit-user plane) of a base station to enhance the security of a base station in a wireless communication system.
[0017] A method and device according to an embodiment of the present disclosure can enable context update including security information for use in a device that can assist a CU-UP (central unit-user plane) side computational function of a base station in a wireless communication system.
[0018] FIG. 1 is a diagram illustrating the structure of a wireless communication system according to an embodiment of the present invention.
[0019] FIG. 2 is a diagram showing a wireless protocol structure in an LTE system according to an embodiment of the present invention.
[0020] FIG. 3 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0021] FIG. 4 illustrates data packet processing of a next-generation mobile communication system according to an embodiment of the present invention.
[0022] FIG. 5 is a diagram for explaining virtualized data packet processing in a CU-UP of a base station according to an embodiment of the present invention.
[0023] FIG. 6 is an example showing a CU-CP of a base station and a CU-UP of a base station according to an embodiment of the present invention.
[0024] FIG. 7 is a diagram for explaining that a CU-CP of a base station according to an embodiment of the present invention communicates with a plurality of CU-UPs through an E1 interface.
[0025] FIG. 8 is a diagram for explaining how a CU-CP of a base station according to an embodiment of the present invention communicates information about the presence and performance of a device capable of assisting a computational function from multiple CU-UPs through an E1 interface.
[0026] FIG. 9 is a drawing for explaining the overall operation according to an embodiment of the present invention.
[0027] FIG. 10 is a diagram for explaining a data packet processing operation when a device capable of assisting general data packet processing and operation functions in a CU-UP of a base station is installed according to an embodiment of the present invention.
[0028] FIG. 11 is a diagram for explaining an operation of setting up an E1 interface to transmit information about a device that can assist the operation function between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention.
[0029] FIG. 12 is a diagram for explaining an operation for updating information when there is a change in information about a device that can assist the operation function between the CU-CP of a base station and the CU-UP of the base station according to an embodiment of the present invention.
[0030] FIG. 13 is a diagram for explaining an operation when information transmission to a device that can assist an operation function between a CU-CP of a base station and a CU-UP of a base station fails according to an embodiment of the present invention.
[0031] FIG. 14 is a diagram for explaining a failure in information change update for a device that can assist the operation function between the CU-CP of a base station and the CU-UP of the base station according to an embodiment of the present invention.
[0032] FIG. 15 is a diagram for explaining bearer setup between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention.
[0033] FIG. 16 is a diagram for explaining a case where a CU-CP of a base station requests a modification of a bearer context to a CU-UP of the base station according to an embodiment of the present invention.
[0034] FIG. 17 is a diagram for explaining a case where a CU-UP of a base station requests a modification of a bearer context to a CU-CP of the base station according to an embodiment of the present invention.
[0035] FIG. 18 is a diagram for explaining a case in which there is content regarding security information when a request for modification of a bearer context is made from a CU-CP of a base station to a CU-UP of the base station according to an embodiment of the present invention.
[0036] FIG. 19 is a block diagram illustrating a base station including a CU-CP according to embodiments of the present invention.
[0037] FIG. 20 is a block diagram illustrating a base station including a CU-UP according to embodiments of the present invention.
[0038] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.
[0039] In describing the embodiments in this specification, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.
[0040] 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.
[0041] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.
[0042] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams 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 flow diagram 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 flow diagram 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).
[0043] 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.
[0044] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ 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.
[0045] In embodiments of the present disclosure, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, an eNB, a Node B, a BS, a radio access unit, a base station controller, or a node on a network. In addition, the base station may be a network entity including at least one of an IAB-donor (Integrated Access and Backhaul - donor), which is a gNB that provides network access to terminal(s) through a network of backhaul and access links in an NR system, and an IAB-node, which is a radio access network (RAN) node that supports NR access link(s) to the terminal(s) and supports NR backhaul links to the IAB-donor or another IAB-node. A terminal may be wirelessly connected through an IAB-node and may transmit and receive data with an IAB-donor connected to at least one IAB-node through a backhaul link.
[0046] In addition, the terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or various devices capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the fifth generation mobile communication technology (5G, new radio, NR) or 6G developed after LTE-A may be included here, and the 5G or 6G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.
[0047] Terms used in the following description to refer to signals, channels, control information, network entities, and device components are provided for convenience of explanation. Furthermore, terms used in the following description to identify nodes, messages, interfaces between network entities, and various pieces of information are provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.
[0048] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems.
[0049] FIG. 1 is a diagram illustrating the structure of a wireless communication system according to an embodiment of the present invention.
[0050] FIG. 1 illustrates an example in which a plurality of base stations and user equipment (UE) move and change the base station to which they are connected in a mobile communication system to which embodiments of the present invention are applied.
[0051] The base stations (1-20, 1-30) may be connected to some of the surrounding base stations, and the base stations (1-20, 1-30) may be connected to a mobile communication core network (CN: Core Network) (1-40) such as an Evolved Packet Core (EPC) or a 5G Core Network (5GC) or a 6G network.
[0052] The radio access technology of the base stations (1-20, 1-30) may be LTE, NR, Wi-Fi, 6G, etc., and is not limited to one example. For example, the base stations (1-20, 1-30) may be mobile communication base stations unrelated to the radio access technology.
[0053] A terminal (1-10) can receive mobile communication services by being connected to a base station, and as the terminal (1-10) moves, the base station to which it is connected can change, and through a handover (HO;: Handover, or handoff) procedure, the terminal (1-10) can receive mobile communication services without interruption. In one example of Fig. 1, the terminal (1-10) is connected to a base station (1-20), and then through a handover, the terminal can disconnect from the base station (1-20) and connect to a new base station (1-30).
[0054] FIG. 2 is a diagram showing a wireless protocol structure in an LTE system according to an embodiment of the present invention.
[0055] Referring to FIG. 2, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 2-110, 2-210), RLC (Radio Link Control 2-120, 2-220), and MAC (Medium Access Control 2-130, 2-230) in the terminal (2-100) and the base station (2-200), respectively. The components of the wireless protocol may be referred to as layers, entities, or devices.
[0056] PDCP (Packet Data Convergence Protocol) (2-110, 2-210) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.
[0057] - Header compression and decompression (ROHC only)
[0058] - User data transfer function
[0059] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM
[0060] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)
[0061] - Duplicate detection of lower layer service data units (SDUs) at PDCP re-establishment procedure for RLC AM
[0062] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)
[0063] - Encryption and decryption functions (Ciphering and deciphering)
[0064] - Timer-based SDU discard in uplink.
[0065] Radio Link Control (RLC) (2-120, 2-220) reconfigures PDCP PDUs (Packet Data Units) to an appropriate size and performs ARQ operations, etc. The main functions of RLC are summarized as follows.
[0066] - Data transfer function (Transfer of upper layer PDUs)
[0067] - ARQ function (Error Correction through ARQ (only for AM data transfer))
[0068] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)
[0069] - Re-segmentation of RLC data PDUs (only for AM data transfer)
[0070] - Reordering of RLC data PDUs (only for UM and AM data transfer)
[0071] - Duplicate detection (only for UM and AM data transfer)
[0072] - Error detection function (Protocol error detection (only for AM data transfer))
[0073] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))
[0074] - RLC re-establishment function
[0075] MAC (2-130, 2-230) connects to multiple RLC layer devices configured in a single terminal, and multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.
[0076] - Mapping function (Mapping between logical channels and transport channels)
[0077] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)
[0078] - Scheduling information reporting function
[0079] - HARQ function (Error correction through HARQ)
[0080] - Priority handling between logical channels of one UE
[0081] - Priority handling between UEs by means of dynamic scheduling
[0082] - MBMS service identification function
[0083] - Transport format selection function
[0084] - Padding function
[0085] The physical layer (2-140, 2-240) performs the operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating OFDM symbols received over a wireless channel and performing channel decoding to transmit them to the upper layer.
[0086] FIG. 3 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0087] Referring to FIG. 3, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (service data application protocol) (3-110, 3-210), NR PDCP (3-120, 3-220), NR RLC (3-130, 3-230), and NR MAC (3-140, 3-240) in the terminal (3-100) and the NR base station (3-200), respectively. The components of the wireless protocol may be referred to as layers, entities, or devices.
[0088] Key features of NR SDAP (3-110, 3-210) may include some of the following:
[0089] - Transfer of user plane data
[0090] - Mapping function between QoS flow and data bearer for both DL and UL
[0091] - QoS flow ID marking function for both uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0092] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0093] For the above SDAP layer device, the terminal can be configured by an RRC (radio resource control) message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can be instructed to update or reset the QoS flow of the uplink and downlink and the mapping information for the data bearer by a 1-bit indicator for NAS QoS reflection configuration (NAS reflective QoS) and a 1-bit indicator for AS QoS reflection configuration (AS reflective QoS) in the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.
[0094] The main functions of NR PDCP (3-120, 3-220) may include some of the following functions:
[0095] Header compression and decompression (ROHC only)
[0096] - User data transfer function
[0097] - In-sequence delivery of upper layer PDUs
[0098] - Out-of-sequence delivery of upper layer PDUs
[0099] - PDCP PDU reordering for reception
[0100] - Duplicate detection of lower layer SDUs
[0101] - Retransmission function (Retransmission of PDCP SDUs)
[0102] - Encryption and decryption functions (Ciphering and deciphering)
[0103] - Timer-based SDU discard in uplink.
[0104] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or may include a function of transmitting data directly without considering the order, may include a function of recording lost PDCP PDUs by reordering the order, may include a function of performing a status report on lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.
[0105] Key features of NR RLC (3-130, 3-230) may include some of the following:
[0106] - Data transfer function (Transfer of upper layer PDUs)
[0107] - In-sequence delivery of upper layer PDUs
[0108] - Out-of-sequence delivery of upper layer PDUs
[0109] - ARQ function (Error Correction through ARQ)
[0110] - Concatenation, segmentation and reassembly of RLC SDUs
[0111] - Re-segmentation of RLC data PDUs
[0112] - Reordering of RLC data PDUs
[0113] - Duplicate detection function
[0114] - Protocol error detection
[0115] - RLC SDU discard function
[0116] - RLC re-establishment function
[0117] The in-sequence delivery function of the NR RLC device above refers to the function of sequentially transmitting RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and transmitting RLC SDUs when an RLC SDU is originally received divided into multiple RLC SDUs, may include a function of reordering received RLC PDUs based on RLC SN (sequence number) or PDCP SN (sequence number), may include a function of recording lost RLC PDUs by reordering the sequence, may include a function of performing a status report on lost RLC PDUs to the transmitting side, may include a function of requesting retransmission of lost RLC PDUs, may include a function of sequentially transmitting only RLC SDUs up to the lost RLC SDU to an upper layer when there is a lost RLC SDU, or may include a function of sequentially transmitting all RLC SDUs received before the timer starts when a predetermined timer expires even when there is a lost RLC SDU. or, if a predetermined timer has expired, even if there are lost RLC SDUs, it may include a function to sequentially deliver all RLC SDUs received up to the upper layer.
[0118] In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number, SN) and delivered to the PDCP device out of order (out-of-sequence delivery). In addition, if the received RLC PDU is a segment, the segments stored in the buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.
[0119] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.
[0120] NR MAC (3-140, 3-240) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.
[0121] - Mapping function (Mapping between logical channels and transport channels)
[0122] - Multiplexing / demultiplexing of MAC SDUs
[0123] - Scheduling information reporting function
[0124] - HARQ function (Error correction through HARQ)
[0125] - Priority handling between logical channels of one UE
[0126] - Priority handling between UEs by means of dynamic scheduling
[0127] - MBMS service identification function
[0128] - Transport format selection function
[0129] - Padding function
[0130] The NR PHY layer (3-150, 3-250) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating OFDM symbols received over a wireless channel and performing channel decoding to transmit them to a higher layer.
[0131] FIG. 4 is a diagram illustrating a data packet processing structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0132] Referring to FIG. 4, the mobile communication system may include a terminal (UE, User Equipment) (410), a DU (+RU) (Distributed Unit + Radio Unit) (420), a CU-UP (Central Unit-User Plane) (430), an UPF (User Plane Function) (440), and a DN (Data Network) (450).
[0133] A mobile communication system includes a data network (DN) (450) and a terminal (UE) (410), and can provide communication services (e.g., phone and / or data services) to the terminal (410) even while moving. In 5G, a control plane (CP) and a user plane (UP) are distinguished. The control plane can form a link with the terminal and control data service functions. The user plane can provide high-quality communication and data services to the terminal. For data services, there is a UPF (440) corresponding to a core network, and there are a CU-UP (Central Unit-User Plane) (430) and a DU (Distributed Unit) (420) corresponding to a base station. In 5G, the functions of the base station can be segmented and the functions can be processed by dividing them into CU-UP and DU.
[0134] In a mobile communication system, a terminal (410) may include a PHY layer (e.g., 3-150 of FIG. 3), a MAC layer (e.g., 3-140 of FIG. 3), an RLC layer (e.g., 3-130 of FIG. 3), a PDCP layer (e.g., 3-120 of FIG. 3), an SDAP layer (e.g., 3-110 of FIG. 3), a PDU layer (Packet Data Unit layer) (412), and an App layer (Application layer) (411).
[0135] Each of the DU (420), CU-UP (430), and UPF (440) may include a GTP-U (GPRS Tunneling Protocol-User plane) (433, 441), UDP (User Datagram Protocol) (422, 434, 442), and IP (Internet Protocol) (435, 443) layer.
[0136] The App layer (411, 451) can serve as an application layer, converting client requests into data understandable by the server and transmitting them to the transport layer. Furthermore, the App layer (411, 451) can use application layer protocols to enable client-side applications to communicate with server-side applications.
[0137] The PDU layers (412, 444, 452) can process data packets transmitted between the terminal (UE) (410) and the DN (450) through a PDU session (Packet Data Unit Session). For example, if the PDU session type is Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), or Internet Protocol version 4 or 6 (IPv4v6), the PDU layers (412, 444, 452) can process IPv4 packets, IPv6 packets, or both through the PDU session. If the PDU session type is Ethernet, the PDU layers (412, 444, 452) can process Ethernet frames.
[0138] GTP-U (433, 441) may refer to a protocol that supports user data tunneling through N3 (between 5G-AN nodes and UPF) and N9 (between different UPFs of 5GC) in the backbone network.
[0139] UDP (422, 434, 442) can support data transmission without going through a connection process when exchanging data. IP (422, 434, 443) is an Internet Protocol address and can serve as a way to identify devices connected to the Internet.
[0140] FIG. 5 is a diagram for explaining virtualized data packet processing in a CU-UP of a base station according to an embodiment of the present invention.
[0141] 5G can provide the ability to segment base station functions and split them into CU-UP and DU functions for processing. Operators can offload base station software (SW) onto a virtualized platform in 5G to provide mobile communication services, reducing base station installation and operating costs.
[0142] For convenience of explanation, FIG. 5 illustrates an embodiment in which a base station's CU-UP is virtualized and implemented as a VM (Virtual Machine) (510). FIG. 5 illustrates a packet flow in a virtualized base station CU-UP when a terminal downloads data. However, the technical idea of the present invention can be applied equally or substantially equally not only to an embodiment in which a base station (or a CU-UP of a base station) is virtualized, but also to an embodiment in which a base station (or a CU-UP of a base station) is not virtualized.
[0143] Referring to FIG. 5, when a data packet is packet-in to a CU-UP, the data packet may be input into the User Space (500) via a Network Interface Controller (NIC) (550) and a Kernel Space (540). The data packet may pass through a virtual Network Interface Controller (vNIC) (520) and a Virtual Machine (VM) (510) in a set of NIC drivers of a Data Plane Development Kit (DPDK) (530) through UDP (513), GTP-U (511), Service Data Association Protocol (SDAP) (515), Packet Data Convergence Protocol (PDCP) (517), and UDP (519). The data packet may be packet-out via the vNIC (520), DPDK (530), Kernel Space (540), and NIC (550).
[0144] A NIC (550) may refer to a hardware device used to connect a computer to a network for communication. It may provide an address allocation system using MAC addresses and enable physical access to the network media.
[0145] vNIC (520) may mean a virtual network interface based on the physical NIC of the host.
[0146] The kernel area (540) is where the kernel resides. The kernel manages the physical and abstract resources of the computer, provides basic services for all other parts of the system, manages hardware, and can allocate system resources.
[0147] When SDAP (515) receives an IP packet and needs to attach an SDAP header, it applies the mapping information between IP flow and QoS flow preset in the network and inserts the QoS flow ID or other necessary information into the SDAP header. The SDAP header can then be attached to the IP packet and forwarded to a bearer or PDCP layer appropriate for QoS.
[0148] PDCP (517) is one of the layers of the wireless traffic stack in UMTS (Universal Mobile Telecommunication System), and can perform IP header compression and decompression, user data transmission, and sequence number maintenance for Radio Bearer.
[0149] DPDK (530) is a high-performance packet processing software that provides libraries and drivers for high-speed packet processing and can improve the network performance of NFV (Network Function Virtualization).
[0150] During data packet processing, the CU provides support for higher layers of the protocol stack, such as SDAP and PDCP. PDCP performs security processing. Meanwhile, the DU can provide support for lower layers of the protocol stack, such as the RLC, MAC, and PHY layers.
[0151] FIG. 6 is an example showing a CU-CP of a base station and a CU-UP of a base station according to an embodiment of the present invention.
[0152] Mobile operators are increasingly able to provide more services within smaller service areas. These smaller service areas can be characterized as small cells. However, communicating across these small service areas presents challenges in terms of capacity, coverage, and interference. Consequently, centralized radio access networks (C-RAN) have been proposed to serve small cells. One of the requirements for implementing C-RAN is a new concept called fronthaul.
[0153] The 5G system can functionally separate the base station (gNB) (600) into a gNodeB-central unit (gNB-CU) (610, 620) and a gNodeB-distributed unit (gNB-DU) (630). Additionally, to implement the concept of cloud RAN, the separation of the CU into a gNodeB-central unit-control plane (gNB-CU-CP) (620) and a gNodeB-central unit-user plane (gNB-CU-UP) (610) has been introduced.
[0154] In this deployment scenario, RAN protocol functions are distributed across different locations, such as gNB-CUs (610, 620) and gNB-DUs (630). The gNB-DU can host RLC, MAC, and physical layers. The gNB-CU-CP (620) can host RRC and PDCP-C protocols. The gNB-CU-UP (610) can host PDCP-U (and SDAP) protocols. The gNB-DU (630) and gNB-CU-CP (620) can be connected via the F1-C interface (603). The gNB-DU (630) and CU-UP (610) can be connected via the F1-U interface (605). The gNB-CU-CP (620) and gNB-CU-UP (610) can be connected via the E1 interface (601).
[0155] Depending on the decoupled deployment scenario, the locations of different RAN functions can be optimally deployed based on the scenario and desired performance. For example, the gNB-CU-CP (620) can be deployed close to the gNB-DU (630). Alternatively, the gNB-CU-CP (620) can be deployed together with the gNB-DU (630). In this case, low latency can be provided for critical CP procedures such as connection (re)establishment, handover, and state transition. On the other hand, the gNB-CU-UP (610) can be centrally deployed in a regional or national data center. Therefore, the gNB-CU-UP (610) is advantageous for cloud implementations and can provide a centralized endpoint for UP traffic in dual connectivity and tight interworking scenarios. Additionally, an additional gNB-CU-UP (610) can be placed close to (or in the same location as) the gNB-DU (630) to provide a local termination point for UP traffic for applications requiring very low latency, for example, ultra-reliable low latency communications (URLLC) traffic.
[0156] FIG. 7 is a diagram for explaining that a CU-CP of a base station according to an embodiment of the present invention communicates with a plurality of CU-UPs through an E1 interface.
[0157] Referring to FIG. 7, a CU-CP (710) of a base station can communicate with a plurality of CU-UPs (720) via an E1 interface (701). The plurality of CU-UPs (720) can include a first CU-UP (721), a second CU-UP (722), a third CU-UP (723), and a fourth CU-UP (721). The plurality of CU-UPs (721, 722, 723, 724) can each have different performances or different functions. In this structure, the CU-CP can communicate with CU-UPs of various performances and functions.
[0158] In FIG. 7, for convenience of explanation, the plurality of CU-UPs (720) are illustrated as including four CU-UPs (720), but the technical idea of the present invention is not limited thereto, and the plurality of CU-UPs (720) may include a variety of numbers of CU-UPs (720).
[0159] In Fig. 7, CU-CP cannot perform high-speed, low-latency packet processing using the device because there is no device that can assist the computational function of the CU-UP side.
[0160] FIG. 8 is a diagram for explaining how a CU-CP of a base station according to an embodiment of the present invention communicates information about the presence and performance of a device capable of assisting a computational function from multiple CU-UPs through an E1 interface.
[0161] Referring to FIG. 8, a CU-CP (810) of a base station can communicate with multiple CU-UPs (821, 822, 831, 832) through an E1 interface (801).
[0162] In Fig. 8, for convenience of explanation, the plurality of CU-UPs (820, 830) are illustrated as including four CU-UPs, but the technical idea of the present invention is not limited thereto, and the plurality of CU-UPs (820, 830) may include various numbers of CU-UPs. In addition, the SND (Smart Network Device) described in Fig. 8 is an example of a device that can assist a computational function.
[0163] Among the multiple CU-UPs, there may be CU-UPs (820) that have devices (823, 824) that can assist computational functions, and CU-UPs (830) that do not. The devices (823, 824) have different performances, so that the CU-CP (810) must be able to know the presence and performance of the devices in the CU-UPs (821, 822) in order to utilize the devices for high-speed, low-latency packet processing. The present disclosure proposes a method for conveying the presence and performance of the devices.
[0164] FIG. 9 is a drawing for explaining the overall operation according to an embodiment of the present invention.
[0165] Referring to FIG. 9, the overall flowchart of the present invention occurring between the CU-CP (910) of the base station and the CU-UP (920) of the base station is disclosed. The SND (Smart Network Device) described in FIG. 9 is an example of a device capable of assisting a computational function.
[0166] In operation 901, the CU-UP (920) may transmit a request message for E1 interface setup to the CU-CP (910) to check the presence and capability of a device capable of assisting the computational function.
[0167] For a request message for E1 interface setup of CU-UP (920), CU-CP (910) can transmit a corresponding response message to CU-UP (920).
[0168] CU-CP (910) can send a request message for E1 interface setup to CU-UP (920).
[0169] For a message for E1 interface setup of CU-CP (910), CU-UP (920) can transmit a response message to confirm the presence and performance of a device that can assist the computational function.
[0170] In operation 903, the CU-UP (920) may transmit a request message to the CU-CP (910) to update the presence and performance of a device capable of assisting the computational function when this has changed.
[0171] For the above update request message of CU-UP (920), CU-CP (910) can transmit a corresponding response message.
[0172] If the presence and performance of a device that can assist the computational function of the CU-CP (910) have changed, the CU-UP (920) can transmit a request message to update it.
[0173] For the above update request message of CU-CP (910), CU-UP (920) can transmit a corresponding response message.
[0174] In operation 905, the CU-CP (910) may make a decision to set up a bearer if the CU-UP (920) has a device that can assist in the computational function.
[0175] In operation 907, the CU-CP (910) may decide whether to set up a bearer context if a device capable of assisting the computational function exists on the CU-UP (920) side.
[0176] In operation 909, the CU-CP (910) may decide to set up a bearer context if there is no device on the CU-UP (920) side that can assist the computational function.
[0177] In 911 operation, CU-UP (920) can determine whether high-speed packet processing is required.
[0178] In operation 913, if a change in high-speed packet processing is required, the CU-UP (920) may send a request message for bearer context modification to the CU-CP (910).
[0179] FIG. 10 is a diagram for explaining a general data packet processing and data packet processing operation in a case where a computational assistance device is equipped in a CU-UP of a base station according to an embodiment of the present invention.
[0180] For convenience of explanation, FIG. 10 illustrates an embodiment in which a base station's CU-UP (gNB-CU-CP) is virtualized and implemented as a VM (Virtual Machine) (1010). FIG. 10 illustrates a packet flow in a virtualized base station CU-UP when a terminal downloads data. However, the technical idea of the present invention can be applied equally or substantially equally not only to an embodiment in which a base station (or a CU-UP of a base station) is virtualized, but also to an embodiment in which a base station (or a CU-UP of a base station) is not virtualized.
[0181] Referring to FIG. 10, when a device capable of assisting a computational function exists in a CU-UP of a base station (1000), the path of a data packet (Packet in / out) may vary depending on the computational function performed by the device. For convenience of explanation, two examples (1001, 1002) of the path of a data packet (Packet in / out) may be indicated in FIG. 10. In addition, the Smart Network Device described in FIG. 10 is an example of a device capable of assisting a computational function.
[0182] According to one embodiment, when a packet is in (1001) to DPDK (1040), it operates similarly to the packet in scenario in FIG. 5, and this operates when a bearer setup is not performed due to a lack of a device that can assist the computational function on the CU-UP side. At this time, the data packet passes through the kernel area (1050) and the vNIC (1030) in the NIC set of User Space (1010) and DPDK (1040). The data packet passes through UDP (1021), GTP-U (1022), SDAP (1023), PDCP (1025), and UDP (1026) in VM (1020) and is packet-out to the vNIC (1030), DPDK (1040), and kernel area (1050).
[0183] According to one embodiment, if there is a device (1060) capable of assisting a computational function on the CU-UP side and a bearer setup is performed, a packet can be input (1002) to the device (1060) capable of assisting a computational function. At this time, a data packet is input (1002) to the device (1060) capable of assisting a computational function, passes through UDP (1061), GTP-U (1062), SDAP (1063), GTP-U (1064), PDCP (1065), and UDP (1066), and is then output (Packet Out).
[0184] According to one embodiment, a device (1060) capable of assisting a computational function may have at least one of the following characteristics.
[0185] - Special hardware devices that perform network-related tasks
[0186] - A device that allows users to program network applications using a high-level language such as P4.
[0187] - Devices that optimize data packet pipeline design and perform independent protocols
[0188] - Devices with an FPGA-based approach for device prototyping
[0189] - A device that allows users to develop designs that can process data packets at line speed.
[0190] According to one embodiment, a device (1060) capable of assisting a computational function may have the following advantages.
[0191] - A subset of network operations can be offloaded from host VNFs (Virtual Network Functions, e.g. UPF).
[0192] - Network operations can be accelerated without CPU intervention.
[0193] - Enables independent programming from specific protocols and / or vendors.
[0194] - Latency is reduced by 2-20 times, and higher throughput is possible than CPU processing.
[0195] FIG. 11 is a diagram illustrating an operation of setting up an E1 interface to transfer information about a computational assistance device between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 11 is an example of a device capable of assisting computational functions.
[0196] In operation 1101, the CU-UP (1100) of the base station checks whether there is a device that is connected to the CU-UP (1100) of the base station and can assist the operation function of the CU-UP (1100) of the base station, and if there is the device connected to the CU-UP (1100) of the base station, an E1 interface setup request message including information indicating the existence of the device and information regarding the performance of the device can be transmitted to the CU-CP (1110) of the base station.
[0197] In operation 1103, when the CU-UP (1100) of the base station transmits the request message according to operation 1101, the CU-UP (1100) of the base station can receive the E1 interface setup response message according to the request message from the CU-CP (1110).
[0198] In operation 1105, the CU-CP (1120) of the base station can transmit an E1 interface setup request message to the CU-UP (1130) of the base station to check whether a device capable of assisting a computational function exists on the CU-UP (1130) side of the base station and to check information about the performance of the device.
[0199] In operation 1107, if the CU-CP (1120) of the base station transmits the request message according to operation 1105, the CU-CP (1120) of the base station may receive the E1 interface setup response message according to the request message from the CU-UP (1130). The response message may include information regarding the performance of the device.
[0200] In operations 1101, 1103, 1105 and 1107, messages about the presence and capabilities of devices capable of assisting the computational function may be structured as shown in [Table 1].
[0201]
[0202] According to one embodiment, in a method performed by a central unit-user plane (CU-UP) (1100) of a base station in a wireless communication system, it is determined whether a device connected to the CU-UP (1100) of the base station and capable of assisting a computational function of the CU-UP (1100) of the base station exists, and if the device connected to the CU-UP (1100) of the base station exists, a first message including first information indicating the existence of the device and second information regarding performance of the device can be transmitted to a central unit-control plane (CU-CP) (1110) of the base station.
[0203] According to one embodiment, if there is a step of transmitting a first message including first information indicating the existence of the device and second information regarding the performance of the device to the CU-CP (1110) of the base station by the CU-UP (1100) of the base station, and a step of receiving a second message corresponding to the first message from the CU-CP (1110) of the base station, and if the first message is a request message (1101) for setting up an E1 interface for connecting the CU-UP (1100) of the base station and the CU-CP (1110) of the base station, the second message is a setup response message (1103) for the E1 interface, and if the second message is a request message (1105) for setting up the E1 interface for connecting the CU-UP (1130) of the base station and the CU-CP (1120) of the base station, the first message is a setup response message (1107) for the E1 interface. Can be.
[0204] In one embodiment, information about the performance of a device capable of assisting a computational function may include at least one of information about availability of the device, throughput provided by the device, throughput available to the device, latency associated with the device, and information about an encryption algorithm used by the device.
[0205] FIG. 12 is a diagram illustrating an operation for updating information when there is a change in information regarding a device capable of assisting the computational function between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 12 is an example of a device capable of assisting the computational function.
[0206] In operation 1201, it is checked whether there is a change in the performance of a device that is connected to the CU-UP (1200) of the base station and can assist the operation function of the CU-UP (1200) of the base station, and if there is a change in the performance of the device, the CU-UP (1200) of the base station can transmit an update request message for the change in the performance of the device to the CU-CP (1210) of the base station.
[0207] In operation 1203, if the CU-UP (1200) of the base station transmits the request message according to operation 1201, the CU-UP (1200) of the base station can receive an update response message according to the request message from the CU-CP (1210).
[0208] In operation 1205, the CU-CP (1220) of the base station can transmit an update request message to the CU-UP (1230) of the base station to check whether there is a change in the performance of a device that can assist the computational function on the CU-UP (1230) side of the base station.
[0209] In operation 1207, if the CU-CP (1220) of the base station transmits the request message according to operation 1205, the CU-CP (1220) of the base station may receive an update response message according to the request message from the CU-UP (1230). The response message may include information regarding a change in the performance of the device.
[0210] In operations 1201, 1203, 1205 and 1207, messages for updates of devices that can assist the computational function can be structured as shown in [Table 2].
[0211]
[0212] According to one embodiment, when there is a device capable of assisting a computational function connected to a CU-UP (1200) of a base station, a first message including information about the performance of the device may be transmitted to a CU-CP (1210) of the base station. According to one embodiment, the CU-UP (1200) of the base station may receive a second message related to the first message from a CU-CP (1220) of the base station. According to one embodiment, if the first message is an update request message (1201) for at least one of the presence or absence of the device or the performance, the second message may be an update response message (1203) corresponding to the first message. According to one embodiment, if the second message is an update request message (1205) for at least one of the presence or absence of the device or the performance, the first message may be an update response message (1207) corresponding to the second message.
[0213] In one embodiment, the change information regarding the performance of the device may include at least one of information regarding availability of the device, throughput provided by the device, throughput available to the device, delay time associated with the device, and information regarding an encryption algorithm used by the device.
[0214] FIG. 13 is a diagram illustrating operations when information transmission fails for a device capable of assisting computational functions between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 13 is an example of a device capable of assisting computational functions.
[0215] In operation 1301, it is checked whether there is a device that is connected to the CU-UP (1300) of the base station and can assist the operation function of the CU-UP (1300) of the base station, and if there is the device connected to the CU-UP (1300) of the base station, the CU-UP (1300) of the base station can transmit (1301) an E1 interface setup request message including information indicating the existence of the device and information regarding the performance of the device to the CU-CP (1310) of the base station.
[0216] In operation 1303, if the CU-UP (1300) of the base station transmits the request message according to operation 1301, the CU-UP (1300) of the base station can receive (1303) the E1 interface setup failure message according to the request message from the CU-CP (1310).
[0217] In operation 1305, the CU-CP (1320) of the base station can transmit (1305) an E1 interface setup request message to the CU-UP (1330) of the base station to check whether a device capable of assisting a computational function exists on the CU-UP (1330) side of the base station and information about the performance of the device.
[0218] In operation 1307, if the CU-CP (1320) of the base station transmits the request message according to operation 1305, the CU-CP (1320) of the base station may receive (1307) the E1 interface setup failure message according to the request message from the CU-UP (1330). The failure message may include cause information for the E1 interface setup failure.
[0219] In operations 1301, 1303, 1305 and 1307, information about the cause of failure included in the E1 interface setup failure message can be configured as in [Table 3].
[0220]
[0221] In one embodiment, if there is a step of transmitting a first message including information indicating the existence of the device and information regarding the performance of the device to the CU-CP (1310) of the base station by the CU-UP (1300) of the base station, the step of receiving a second message corresponding to the first message from the CU-CP (1310) of the base station is further included, and if the first message is a request message (1301) for setting up an E1 interface for connecting the CU-UP (1300) of the base station and the CU-CP (1310) of the base station, the second message may be a setup failure message (1303) for the E1 interface, and if the second message is a request message (1305) for setting up the E1 interface for connecting the CU-UP (1330) of the base station and the CU-CP (1320) of the base station, the first message may be a setup failure message (1307) for the E1 interface.
[0222] According to one embodiment, when the E1 interface setup fails, the cause information for the setup failure message may include at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure.
[0223] FIG. 14 is a diagram illustrating a failure in information change update for a device capable of assisting the computational function between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 14 is an example of a device capable of assisting the computational function.
[0224] In operation 1401, it is checked whether there is a change in the performance of a device that is connected to the CU-UP (1400) of the base station and can assist the operation function of the CU-UP (1400) of the base station, and if there is a change in the performance of the device, the CU-UP (1400) of the base station can transmit an update request message for the change in the performance of the device to the CU-CP (1410) of the base station.
[0225] In operation 1403, if the CU-UP (1400) of the base station transmits the request message according to operation 1401, the CU-UP (1400) of the base station can receive an update failure message according to the request message from the CU-CP (1410).
[0226] In operation 1405, the CU-CP (1420) of the base station can transmit an update request message to the CU-UP (1430) of the base station to check whether there is a change in the performance of a device that can assist the computational function on the CU-UP (1230) side of the base station.
[0227] In operation 1407, if the CU-CP (1420) of the base station transmits the request message according to operation 1405, the CU-CP (1420) of the base station may receive an update failure message according to the request message from the CU-UP (1430). The failure message may include cause information for the update failure.
[0228] In operations 1401, 1403, 1405 and 1407, the message for update failure of a device that can assist the computational function may be structured as shown in [Table 4].
[0229]
[0230] According to one embodiment, when there is a device capable of assisting a computational function connected to a CU-UP (1400) of a base station, the method further includes the step of transmitting a first message including information about the performance of the device to a CU-CP (1410) of the base station, and when there is a change in at least one of the presence or absence of the device or the performance, receiving a fourth message corresponding to the first message from the CU-CP (1410) of the base station, wherein if the first message is an update request message (1401) for at least one of the presence or absence of the device or the performance, the fourth message is an update failure message (1403) corresponding to the first message, and if the fourth message is an update request message (1405) for at least one of the presence or absence of the device or the performance, the first message may be an update failure message (1407) corresponding to the first message.
[0231] According to one embodiment, the cause information for the update failure message may include at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating that the cause of the update failure is unknown.
[0232] FIG. 15 is a diagram illustrating a bearer setup between a CU-CP of a base station and a CU-UP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 15 is an example of a device capable of assisting computational functions.
[0233] In operation 1501, the CU-CP (1500) of the base station can determine whether traffic will be processed by the device by considering the traffic context with the CU-UP (1510) of the base station, the presence or absence of a device capable of assisting the computational function of the CU-UP (1510) of the base station, and the status of the device.
[0234] In one embodiment, the traffic context in operation 1501 may include at least one of the following, but is not limited to the following examples:
[0235] - As information of the terminal (UE), the context of the terminal
[0236] - As traffic information, information about PDU (Packet Data Unit) sessions, information about SDAP, information about PDCP, information about TCP / UDP / IP (Transmission Control Protocol / User Datagram Protocol / Internet Protocol), and information about QUIC (Quick UDP Internet Connections)
[0237] - As security information, the base station's security context and IPsec (Internet Protocol security) information
[0238] - As a security policy, "required," "preferred," or "not required"
[0239] - Information on the CU-UP of the base station, including information on the throughput provided by the device, the throughput available to the device, and the delay time associated with the device.
[0240] According to one embodiment, a state of a device capable of assisting the CU-UP (1510) side operation function of the base station may have at least one of the following, but is not limited to the following examples.
[0241] -The throughput provided by the above device
[0242] -The throughput available to the above device
[0243] - Information about the delay time associated with the above device.
[0244] In operation 1503, the CU-CP (1500) of the base station may determine whether to set up a bearer according to operation 1501, and then transmit a request message for bearer context setup to the CU-UP (1510) of the base station.
[0245] In operation 1505, the CU-CP (1500) of the base station can receive a response message corresponding to the request message according to operation 1503 from the CU-UP (1510) of the base station.
[0246] In operations 1501, 1503, and 1505, the information included in the request message for the bearer context setup can be configured as shown in [Table 5].
[0247]
[0248] According to one embodiment, the method may include a step of transmitting a request message for setting up a bearer context between a CU-CP (1500) of the base station and a CU-UP (1510) of the base station, wherein information included in the request message may include at least one of information on data processing requirements to be provided in the bearer, information on a policy of the device, information on a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device.
[0249] FIG. 16 is a diagram illustrating a case where a CU-CP of a base station requests a CU-UP of the base station to modify a bearer context according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 16 is an example of a device capable of assisting computational functions.
[0250] In operation 1601, the CU-CP (1600) of the base station may transmit a request message to the CU-UP (1610) of the base station to modify the bearer context.
[0251] In operation 1603, the CU-CP (1600) of the base station can receive a response message corresponding to the request message according to operation 1601 from the CU-UP (1610) of the base station.
[0252] In operations 1601 and 1603, the information included in the request message for modifying the bearer context can be configured as shown in [Table 6].
[0253]
[0254] According to one embodiment, information included in a request message for modifying a bearer context between a CU-CP of the base station and a CU-UP of the base station may include at least one of information on data processing requirements to be provided in the bearer, information on a policy of the device, information on a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time associated with the device.
[0255] FIG. 17 is a diagram illustrating a case where a CU-UP of a base station requests a modification of a bearer context from a CU-CP of the base station according to an embodiment of the present invention. The SND (Smart Network Device) described in FIG. 17 is an example of a device capable of assisting computational functions.
[0256] In operation 1701, the CU-UP (1700) of the base station may transmit a request message to the CU-CP (1710) of the base station to modify a bearer context.
[0257] In operation 1703, the CU-UP (1700) of the base station can receive a response message corresponding to the request message according to operation 1701 from the CU-CP (1710) of the base station.
[0258] In actions 1701 and 1703, the information included in the request message for modifying the bearer context can be configured as shown in [Table 7].
[0259]
[0260] According to one embodiment, information included in a request message for modifying a bearer context between a CU-CP (1710) of the base station and a CU-UP (1700) of the base station may include at least one of bearer context information to be modified, information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure.
[0261] FIG. 18 is a diagram for explaining a case in which there is content regarding security information when a request for modification of a bearer context is made from a CU-CP of a base station to a CU-UP of the base station according to an embodiment of the present invention.
[0262] Referring to FIG. 18, when the CU-CP (1800) of the base station performs a security key update (1801), the CU-CP (1800) of the base station may also include information about the security key update in a request message for modifying a bearer context of a device that can assist the operation function of the CU-UP (1810) side of the base station.
[0263] The CU-CP (1800) of the base station can transmit (1803) the request message and receive (1805) a response message corresponding to the request message from the CU-UP of the base station.
[0264] Meanwhile, the security key (1820) within the base station includes security contexts (1821, 1822, 1823, 1824), and performs a security key update when there is a change (1825, 1826) in at least some of them. In Fig. 18, four security contexts (1821, 1822, 1823, 1824) are illustrated for convenience of explanation, but the technical idea of the present invention is not limited thereto and may include a variety of security contexts. The SND (Smart Network Device) described in Fig. 18 is an example of a device that can assist a computational function.
[0265] A security key update may occur when at least one of the following occurs, including but not limited to:
[0266] - Handover between CU-UP and CU-CP of the base station
[0267] - Handover between the above devices when there are multiple devices
[0268] - Expiration of the device's security key usage period
[0269] - When deemed necessary by the base station's CU-CP
[0270] The keys for control plane (RRC, Radio Resource Control) traffic are as follows:
[0271] - K RRCint (1821) is a key used to protect radio resource control (RRC) traffic by a specific integrity algorithm. K RRCint(1821) uses a Key Derivation Function (KDF) with inputs as specified in section A.7 of 3GPP TS 33.401, K gNB In addition, it is derived from the identifier for the Integrity algorithm by the mobile communication device and the macro base station.
[0272] - K RRCenc (1822) is a key used to protect RRC traffic by a specific encryption algorithm. K RRCenc (1822) uses a Key Derivation Function (KDF) with inputs as specified in section A.7 of 3GPP TS 33.401, K gNB In addition, it is derived from identifiers for encryption algorithms, mobile communication devices and macro base stations.
[0273] The keys for user plane (UP) traffic are as follows:
[0274] K UPint (1823) is a key used to protect UP traffic between a relay node (RN) and a donor eNB (DeNB) by a specific integrity algorithm. The key is derived by using a Key Derivation Function (KDF) with inputs as specified in Section A.7 of 3GPP TS 33.401. gNB In addition, from the identifier for the integrity algorithm, it is derived by RN and DeNB.
[0275] - K UPenc(1824) is a key used to protect UP traffic by a specific encryption algorithm. This key is derived by using a Key Derivation Function (KDF) with inputs as specified in Section A.7 of 3GPP TS 33.401. gNB In addition, it is derived by the mobile communication device and the macro base station from the identifier for the encryption algorithm. In case of User-Plane / Control-Plane separation between the pico base station and the macro base station, K UPenc (1824) is obtained from the pico base station for use in protecting UP traffic by a specific encryption algorithm.
[0276] In operation 1801, the CU-CP of the base station performs a security key update (1801) if there is a change (1825, 1826) in the security information (1820) within the base station.
[0277] In operation 1803, the CU-CP (1800) of the base station may transmit a request message to the CU-UP (1810) of the base station to modify a bearer context. The request message may further include an update on security information (at least one of 1823, 1824, 1825, and 1826).
[0278] In operation 1805, the CU-CP (1800) of the base station can receive a response message corresponding to the request message according to operation 1803 from the CU-UP (1810) of the base station.
[0279] In operation 1825, the security key update of the CU-UP (1810) of the base station is generated from the security key (1820) of the base station or the existing K UPint and K UPenc If there is a change in K UPint and K UPenc This may imply a change in context at least once.
[0280] In operation 1826, the security key update of the CU-UP (1810) of the base station is performed independently only when the security key change is performed. UPint and K UPenc This may imply a change in at least one context.
[0281] According to one embodiment, when there is an update of security information in a base station, the update information included in a request message for modifying a bearer context from a CU-CP (1800) of the base station to the CU-UP (1810) may include at least one of information about a handover between the CU-UP and the CU-CP of the base station, information about a handover between the devices when there are multiple devices, information about the expiration of a security key usage period of the device, and information about a decision made by the CU-CP of the base station.
[0282] FIG. 19 is a block diagram illustrating a base station including a CU-CP according to embodiments of the present invention.
[0283] The base station of FIG. 19 may be implemented as a base station, eNB, gNB, source base station, or target base station as illustrated in FIGS. 1 to 18. Referring to FIG. 19, the base station may include a transceiver unit (1910), a memory (1920), and a control unit (1930).
[0284] The transceiver (1910) can transmit and receive signals with a terminal, another base station, or a device. The transceiver (1910) may also be referred to as a transceiver. The transceiver (1910) may include a transmitter and a receiver.
[0285] The memory (1920) can store at least one of information transmitted and received through the transceiver (1910) and information generated through the control unit (1930).
[0286] The control unit (1930) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The control unit (1930) may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (1930) may control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (1930) may control the operation of the base station, eNB, gNB, source base station, or target base station, for example, as illustrated in FIGS. 1 to 18 .
[0287] According to one embodiment, the control unit (1930) may transmit a request message to the CU-UP of the base station for setting up an E1 interface to connect the CU-UP of the base station and the CU-CP of the base station to check information indicating the presence of a device that is connected to the CU-UP of the base station and can assist the computational function of the CU-UP of the base station and information regarding the performance of the device. According to one embodiment, the control unit (1930) may transmit a request message to the CU-UP of the base station for setting up a bearer context between the CU-UP of the base station and the CU-CP of the base station.
[0288] According to one embodiment, the control unit (1930) may receive a first message from the CU-UP (central unit-user plane) of the base station, the first message including first information indicating the presence of a device capable of assisting the computational function of the CU-UP of the base station, and second information regarding the performance of the device.
[0289] According to one embodiment, the control unit (1930) may transmit and receive a second message corresponding to the first message to the CU-UP of the base station, and if the first message is a request message for setting up an E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the second message may be a setup response message for the E1 interface, and if the second message is a request message for setting up the E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the first message may be a setup response message for the E1 interface.
[0290] According to one embodiment, the control unit (1930) may transmit and receive a second message corresponding to the first message to the CU-UP of the base station, and if the first message is a request message for setting up an E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the second message may be a setup response message for the E1 interface, and if the second message is a request message for setting up the E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the first message may be a setup response message for the E1 interface.
[0291] According to one embodiment, the control unit (1930) may transmit and receive a third message corresponding to the first message to the CU-UP of the base station when there is a change in at least one of the first information and the second information, and when the first message is an update request message of the first information and the second information, the third message is an update response message of the first information and the second information, and when the third message is an update request message of the first information and the second information, the first message is an update response message of the first information and the second information.
[0292] According to one embodiment, the control unit (1930) transmits a request message for setting up a bearer context between a CU-CP of the base station and a CU-UP of the base station, wherein the first message is a response message to the request message, and information included in the request message may include at least one of information on a policy of the device, information on a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device.
[0293] FIG. 20 is a block diagram illustrating a base station including a CU-UP according to embodiments of the present invention.
[0294] The base station of FIG. 20 may be implemented as a base station, eNB, gNB, source base station, or target base station as illustrated in FIGS. 1 to 18. Referring to FIG. 18, the base station may include a transceiver unit (2010), a memory (2020), and a control unit (2030).
[0295] The transceiver (2010) can transmit and receive signals with a terminal, another base station, or a device. The transceiver (2010) may also be referred to as a transceiver. The transceiver (2010) may include a transmitter and a receiver.
[0296] The memory (2020) can store at least one of information transmitted and received through the transceiver (2010) and information generated through the control unit (2030).
[0297] The control unit (2030) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The control unit (2030) may control the overall operation of the base station according to the embodiment proposed in the present disclosure. For example, the control unit (2030) may control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (2030) may control the operation of the base station, eNB, gNB, source base station, or target base station, for example, as illustrated in FIGS. 1 to 18 .
[0298] According to one embodiment, the control unit (2030) includes a transceiver; and at least one processor, wherein the at least one processor is configured to determine whether a device capable of assisting a computational function is present in connection with the CU-UP of the base station, and, if the device is present in connection with the CU-UP of the base station, transmit a request message to a CU-CP (central unit-control plane) of the base station to set up an E1 interface to transmit information indicating the presence of the device and information regarding the performance of the device.
[0299] According to one embodiment, if there is a change in information about the performance of the device, the control unit (2030) may transmit at least one of information about availability of the device, throughput provided by the device, throughput available to the device, delay time related to the device, and information about an encryption algorithm used by the device to the CU-CP of the base station.
[0300] According to one embodiment, when there is a modification of a bearer context between a CU-UP of the base station and a CU-CP of the base station, the control unit (2030) may transmit to the CU-CP of the base station at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure.
[0301] According to one embodiment, the control unit (2030) may check whether there is a device connected to the CU-UP of the base station and capable of assisting the computational function of the CU-UP of the base station, and if there is the device connected to the CU-UP of the base station, the control unit may transmit a first message including first information indicating the existence of the device and second information regarding the performance of the device to the CU-CP (central unit-control plane) of the base station.
[0302] According to one embodiment, the control unit (2030) may transmit and receive a second message corresponding to the first message from the CU-CP of the base station, and if the first message is a request message for setting up an E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the second message may be a setup response message for the E1 interface, and if the second message is a request message for setting up the E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the first message may be a setup response message for the E1 interface.
[0303] According to one embodiment, the control unit (2030) may transmit the second information about the performance of the device to the CU-CP of the base station, including at least one of information about availability of the device, throughput provided by the device, throughput available to the device, delay time related to the device, and information about an encryption algorithm used by the device.
[0304] According to one embodiment, the control unit (2030) receives a second message corresponding to the first message from the CU-CP of the base station, and when the E1 interface setup fails, the first message or the second message is a setup failure message including cause information for setup failure for the E1 interface, and the cause information for the setup failure message may include at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure, and may be transmitted to the CU-CP of the base station.
[0305] According to one embodiment, the control unit (2030) may transmit and receive, if there is a change in at least one of the first information and the second information, a third message corresponding to the first message from the CU-CP of the base station, and if the first message is an update request message of the first information and the second information, the third message is an update response message of the first information and the second information, and if the third message is an update request message of the first information and the second information, the first message is an update response message of the first information and the second information.
[0306] According to one embodiment, the control unit (2030) may transmit to the CU-CP of the base station, the update information of the second information included in the first message, including at least one of information on availability of the device, throughput provided by the device, throughput available to the device, delay time related to the device, and information on an encryption algorithm used by the device.
[0307] According to one embodiment, the control unit (2030), if there is a change in at least one of the first information and the second information, receives a fourth message corresponding to the first message from the CU-CP of the base station, and if the first message is an update request message of the first information and the second information, the fourth message is an update failure message of the first information and the second information, and if the fourth message is an update request message of the first information and the second information, the first message is an update failure message of the first information and the second information, and cause information for the update failure message may include at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the update failure, and may transmit the information to the CU-CP of the base station.
[0308] According to one embodiment, the control unit (2030) may receive a request message for setting up a bearer context between a CU-CP of the base station and a CU-UP of the base station, wherein the first message is a response message to the request message, and information included in the request message may include at least one of information on a policy of the device, information on a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device, and may transmit the information to the CU-CP of the base station.
[0309] According to one embodiment, the control unit (2030) may receive a request message for modifying a bearer context between a CU-CP of the base station and a CU-UP of the base station, wherein the first message is a response message to the request message, and information included in the request message may include at least one of information on a policy of the device, information on a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device, and may transmit the information to the CU-CP of the base station.
[0310] According to one embodiment, the control unit (2030) may transmit, in the request message, an update on security information, and the update information on the security information may include at least one of information on handover between the CU-UP and CU-CP of the base station, handover between the devices when there are multiple devices, information on expiration of the security key usage period of the device, and information on a decision made by the CU-CP of the base station, and may transmit the information to the CU-CP of the base station.
[0311] According to one embodiment, the control unit (2030) may transmit to the CU-CP of the base station, the first message being a request message for modifying a bearer context, a response message corresponding to the request message received from the CU-CP of the base station, and information included in the request message including at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure.
[0312] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. If implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute the methods according to the embodiments described in the claims or specification of the present disclosure.
[0313] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0314] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.
[0315] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.
[0316] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. In a method performed by a CU-UP (central unit-user plane) of a base station in a wireless communication system, A step of checking whether there is a device that is connected to the CU-UP of the base station and can assist the computational function of the CU-UP of the base station; and A method characterized by comprising the step of transmitting, to a CU-CP (central unit-control plane) of the base station, a first message including first information indicating the existence of the device and second information regarding the performance of the device, if the device connected to the CU-UP of the base station exists.
2. In paragraph 1, Further comprising the step of receiving a second message corresponding to the first message from the CU-CP of the base station, If the first message is a request message for setting up an E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the second message is a setup response message for the E1 interface, A method characterized in that the first message is a setup response message for the E1 interface, if the second message is a request message for setting up the E1 interface to connect the CU-UP of the base station and the CU-CP of the base station.
3. In paragraph 2, The second information regarding the performance of the device is: A method characterized in that it includes at least one of information about availability of the device, throughput provided by the device, throughput available to the device, delay time associated with the device, and information about an encryption algorithm used by the device.
4. In paragraph 1, Further comprising the step of receiving a second message corresponding to the first message from the CU-CP of the base station, If the E1 interface setup fails, the first message or the second message is characterized in that it is a setup failure message that includes cause information for the failure of the E1 interface setup, A method characterized in that the cause information for the setup failure message includes at least one of information indicating an overload of the control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating that the cause of the setup failure is unknown.
5. In paragraph 1, If there is a change in at least one of the first information and the second information, Further comprising the step of receiving a third message corresponding to the first message from the CU-CP of the base station, If the first message is an update request message of the first information and the second information, the third message is an update response message of the first information and the second information, A method characterized in that if the third message is an update request message of the first information and the second information, the first message is an update response message of the first information and the second information.
6. In paragraph 5, The update information of the second information included in the first message is A method characterized in that it includes at least one of information about availability of the device, throughput provided by the device, throughput available to the device, delay time associated with the device, and information about an encryption algorithm used by the device.
7. In paragraph 1, If there is a change in at least one of the first information and the second information, Further comprising the step of receiving a fourth message corresponding to the first message from the CU-CP of the base station, If the first message is a request message for updating the first information and the second information, the fourth message is a failure message for updating the first information and the second information, If the fourth message is a request message for updating the first information and the second information, the first message is characterized in that it is a message for failing to update the first information and the second information. The cause information for the above update failure message is: A method characterized in that it includes at least one of information indicating an overload of a control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the update failure.
8. In paragraph 1, Further comprising the step of receiving a request message for setting up a bearer context between the CU-CP of the base station and the CU-UP of the base station, The above first message is a response message to the above request message, A method characterized in that the information included in the request message includes at least one of information about a policy of the device, information about a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device.
9. In paragraph 1, Further comprising the step of receiving a request message for modifying a bearer context between a CU-CP of the base station and a CU-UP of the base station, The above first message is a response message to the above request message, A method characterized in that the information included in the request message includes at least one of information about a policy of the device, information about a maximum bitrate transmission rate aggregation of the device, security information of the device, and a maximum delay time related to the device.
10. In paragraph 9, The above request message further includes updates to Security Information, A method characterized in that the update information for the security information includes at least one of: handover between the CU-UP and CU-CP of the base station, handover between the devices when there are multiple devices, information on expiration of the security key usage period of the device, and information on a decision made by the CU-CP of the base station.
11. In paragraph 1, The above first message is a request message to modify the bearer context, Further comprising the step of receiving a response message corresponding to the request message from the CU-CP of the base station, A method characterized in that the information included in the request message includes at least one of information indicating an overload of the control process of the device, information indicating a lack of processing resources of the CU-UP, information indicating that there is no encryption algorithm supported by the device, information indicating a hardware operation failure of the device, and information indicating an unknown cause of the setup failure.
12. In a method performed by a CU-CP (central unit-control plane) of a base station in a wireless communication system, A step of receiving a first message from the CU-UP (central unit-user plane) of the base station, the first message including first information indicating the presence of a device capable of assisting the computational function of the CU-UP of the base station and second information regarding the performance of the device; and A method characterized by comprising a step of identifying the device connected to the CU-UP of the base station based on the first message.
13. In paragraph 12, Further comprising the step of transmitting a second message corresponding to the first message to the CU-UP of the base station, If the first message is a request message for setting up an E1 interface for connecting the CU-UP of the base station and the CU-CP of the base station, the second message is a setup response message for the E1 interface, A method characterized in that the first message is a setup response message for the E1 interface, if the second message is a request message for setting up the E1 interface to connect the CU-UP of the base station and the CU-CP of the base station.
14. In a base station including a CU-UP (central unit-user plane) in a wireless communication system, Transmitter and receiver; and comprising at least one processor, said at least one processor comprising: Check if there is a device that can assist the computational function by being connected to the CU-UP of the above base station, A base station that controls, when the device connected to the CU-UP of the base station exists, to transmit a request message to the CU-CP (central unit-control plane) of the base station for setting up an E1 interface to transmit information indicating the existence of the device and information regarding the performance of the device.
15. In a base station including a CU-CP (central unit-control plane) of the base station in a wireless communication system, Transmitter and receiver; and comprising at least one processor, said at least one processor comprising: To check the information indicating the existence of a device that can assist the computational function of the CU-UP (central unit-user plane) of the base station by being connected to the CU-UP of the base station and information regarding the performance of the device, A base station that controls a request message to be transmitted to the CU-UP of the base station to set up an E1 interface to connect the CU-UP of the base station and the CU-CP of the base station.
Citation Information
Patent Citations
Computing workload transport over control plane in next generation cellular networks
US20220038948A1
Uplink data fast transmission in CU-du split
US20220086944A1
Computing workload management in next generation cellular networks
US20230308853A1