Electronic device and method for identifying throughput of sliced user equipment

Abstract

A method performed by a near real-time (RT) Radio Access Network (RAN) Intelligent Controller (RIC) may comprise the operations of: receiving an indication message including information on a slice related to a cell from an E2 node; identifying a size of a resource allocated to the slice based on the information about the slice; and transmitting a control message including information on the size of the resource to the E2 node. The information about the slice can include a collection duration, a sum of the amount of data during the collection duration, and information about the user equipment associated with the slice.

Description

Technical Field

[0001] The following description relates to an electronic device and method for identifying the throughput of a slice of a user equipment. Background Art

[0002] Network slicing refers to a method of virtualizing a physical network and using it as multiple networks. A network slice (or "slice") can refer to a virtualized network. A service level agreement (SLA) including throughput, latency, and reliability can be defined for each network slice. Summary of the Invention

[0003] Technical Solution

[0004] According to an aspect of the present disclosure, a method performed by a near real-time (RT) radio access network intelligent controller (RIC) may include: receiving an indication message from an E2 node that includes information about a slice associated with a cell; identifying the size of resources allocated for the slice based on the information about the slice; and sending a control message to the E2 node that includes information about the size of the resources. The information about the slice may include a collection duration, a sum of data amounts during the collection duration, and information about terminals associated with the slice.

[0005] The indication message may further include a cell identifier associated with the cell and index information associated with the slice, and the information about the slice may correspond to the index information.

[0006] The information about terminals associated with the slice may include at least one of the number of terminals served by the data amount through the slice or the number of data radio bearers (DRBs) used to serve the data amount through the slice.

[0007] The indication message may further include a physical resource block (PRB) allocation section and information about PRB usage.

[0008] The control message may further include information about a maximum portion of physical resource blocks (PRBs) of a slice associated with the cell.

[0009] According to an aspect of the present disclosure, a near real-time (RT) radio access network intelligent controller (RIC) may include: a memory storing instructions, a transceiver, and a processor. The instructions, when executed by the processor, may cause the near RT RIC to: receive, via the transceiver, an indication message from an E2 node that includes information about a slice associated with a cell; identify the size of resources allocated for the slice based on the information about the slice; and send, via the transceiver, a control message to the E2 node that includes information about the size of the resources. The information about the slice may include a collection duration, a sum of data amounts during the collection duration, and information about terminals associated with the slice.

[0010] The indication message may further include a cell identifier associated with the cell and index information associated with the slice, and the information about the slice may correspond to the index information.

[0011] The information about the terminal associated with the slice may include at least one of the number of terminals served by the data volume through the slice or the number of data radio bearers (DRBs) used to serve the data volume through the slice.

[0012] The indication message may further include a physical resource block (PRB) allocation section and information about PRB usage.

[0013] The control message may further include information about the maximum portion of physical resource blocks (PRBs) of the slice associated with the cell.

[0014] According to one aspect of the present disclosure, a method performed by an E2 node may include: identifying information about a slice associated with a cell; sending an indication message including the information about the slice to a near real-time (RT) radio access network intelligent controller (RIC); and receiving, from the near RT RIC, a control message including information about the size of the resources allocated for the slice. The information about the slice may include a collection duration, a sum of the data volume during the collection duration, and information about the terminal associated with the slice.

[0015] The indication message may further include a cell identifier associated with the cell and index information associated with the slice, and the information about the slice may correspond to the index information.

[0016] The information about the terminal associated with the slice may include at least one of the number of terminals served by the data volume through the slice or the number of data radio bearers (DRBs) used to serve the data volume through the slice.

[0017] The indication message may further include a physical resource block (PRB) allocation section and information about PRB usage.

[0018] The control message may further include information about the maximum portion of physical resource blocks (PRBs) of the slice associated with the cell.

[0019] According to one aspect of the present disclosure, an E2 node may include: a memory storing instructions, a transceiver, and a processor. The instructions, when executed by the processor, may cause the E2 node to: identify information about a slice associated with a cell; send an indication message including the information about the slice to a near real-time (RT) radio access network intelligent controller (RIC) via the transceiver; and receive a control message including information about the size of resources allocated for the slice from the near RT RIC via the transceiver. The information about the slice may include a collection duration, a sum of the amount of data during the collection duration, and information about terminals associated with the slice. The indication message may further include a cell identifier associated with the cell and index information associated with the slice, and the information about the slice may correspond to the index information.

[0020] The information about terminals associated with the slice may include at least one of the number of terminals served by the amount of data through the slice or the number of data radio bearers (DRBs) used to serve the amount of data through the slice.

[0021] The indication message may further include a physical resource block (PRB) allocation section and information about PRB usage.

[0022] The control message may further include information about the maximum portion of physical resource blocks (PRBs) associated with the slice of the cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the drawings, in which:

[0024] Figure 1 An example of a fourth generation (4G) long term evolution (LTE) core system is shown.

[0025] Figure 2a An example of a fifth generation (5G) non-standalone (NSA) system is shown.

[0026] Figure 2b An example of an open radio access network (O-RAN) architecture is shown.

[0027] Figure 3 An example of a protocol stack of E2 application protocol messages in a radio access network (RAN) is shown.

[0028] Figure 4 An example of a connection between a base station and a radio access network intelligent controller (RIC) in a RAN is shown.

[0029] Figure 5 An example of a configuration of a device in a RAN is shown.

[0030] Figure 6 An example showing the logical functions related to E2 messages between an E2 node and a RIC in the RAN.

[0031] Figure 7 An example showing the functional division between an E2 node and a RIC.

[0032] Figure 8 An example showing the implementation of an E2 node and a RIC.

[0033] Figure 9 An example showing the functional division between a Centralized Unit (CU) and a RIC.

[0034] Figure 10a An example showing the connection between a RIC, an E2 node and a User Equipment in the RAN.

[0035] Figure 10b An example showing the data volume according to the time flow for identifying the throughput of a User Equipment.

[0036] Figure 11 An example showing the resource allocation for slice-based user equipment throughput.

[0037] Figure 12 An example showing the resource allocation for slice-based user equipment throughput.

[0038] Figure 13 An example showing the resource allocation for slice-based user equipment throughput.

[0039] Figure 14 An example showing the resource allocation for slice-based user equipment throughput.

[0040] Figure 15a An example showing the operation process of a Digital Unit (DU) that performs resource allocation based on slice-based user equipment throughput.

[0041] Figure 15b An example showing the operation process of a Near Real-Time RIC that sends resource allocation information based on slice-based user equipment throughput. Detailed Description

[0042] The terms used in this disclosure are only used to describe specific embodiments and may not be intended to limit the scope of another embodiment. Singular expressions may include plural expressions unless they are clearly differently indicated in the context. The terms used herein (including technical or scientific terms) may have the same meaning as those commonly understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in a general dictionary may be interpreted with a meaning that is the same as or similar to the meaning in the context of the related art, and are not interpreted in an ideal or overly formal meaning unless clearly defined in this disclosure. In some cases, even terms defined in this disclosure may not be interpreted as excluding embodiments of this disclosure.

[0043] The term "coupled" and its derivatives indicate any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive", and "communicate" and their derivatives include direct and indirect communication. The terms "comprise" and "include" and their derivatives indicate including but not limited to. The term "or" is an inclusive term, meaning "and / or". The phrase "associated with" and its derivatives indicate including, being included within, being interconnected with, containing, being contained within, being connected to or connected with, being coupled to or coupled with, being communicable with, cooperating with, interweaving, juxtaposing, being close to, being bound to or bound with, having, having the attribute of..., having a relationship to or a relationship with, etc. The term "controller" indicates any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functions associated with any particular controller may be centralized or distributed, whether local or remote. The phrase "at least one of..." when used in conjunction with a list of items means that different combinations of one or more of the listed items may be used, and it may only be necessary to have one item from the list. For example, "at least one of A, B, and C" includes any one of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C, and any variations thereof. Similarly, the term "group" means one or more. Thus, the group of items may be a single item or a collection of two or more items.

[0044] In addition, in the disclosure, expressions such as greater than or less than may be used to determine whether a specific condition is met or fulfilled, but this is only a description for illustrative purposes and does not exclude descriptions of greater than or equal to or less than or equal to. A condition described as "more than or equal to" may be replaced with "more than", a condition described as "less than or equal to" may be replaced with "less than", and a condition described as "more than or equal to and less than" may be replaced with "more than and less than or equal to". In addition, "A" to "B" in the following means at least one of the elements from A (including A) to B (including B).

[0045] In one or more embodiments of the present disclosure described below, hardware methods are described as examples. However, since one or more embodiments of the present disclosure include technologies using both hardware and software, one or more embodiments of the present disclosure do not exclude software-based methods.

[0046] Hereinafter, the present disclosure relates to a control process between a device in a radio access network (RAN) and a device controlling the RAN in a wireless communication system. Specifically, the present disclosure relates to a process, message, and method for enabling an E2 node and a RIC to perform a calibration operation on a standard and ensure backward compatibility by providing the RIC with the version number of the E2AP standard (e.g., E2 Application Protocol (E2AP) 2.02) on the E2 interface by the E2 node.

[0047] Terms in configurations (e.g., establish, set, arrange, control), terms in signals (e.g., packet, message, signal, information, signaling), terms in resources (e.g., portion, symbol, time slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms in operation states (e.g., step, operation, process), terms in data (e.g., packet, message, user flow, information, bit, symbol, codeword), terms in channels, terms in network entities (distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP), open radio access network (O-RAN) DU (O-DU), O-RAN CU (O-CU), O-RAN CU-CP (O-CU-CP)), terms in components of a device, etc., used in the following description are illustrated for ease of description. Therefore, the present disclosure is not limited to the terms described below, and another term having an equivalent technical meaning may be used. In addition, terms such as '... unit', '... device', '... material', '... body', etc. used below may mean at least one shape structure or may mean a unit of processing function.

[0048] In addition, in the disclosure, expressions greater than or less than may be used to determine whether a specific condition is satisfied or fulfilled, but this is only for illustrative purposes and does not exclude descriptions of greater than or equal to or less than or equal to. A condition described as "more than or equal to" may be replaced by "more than", a condition described as "less than or equal to" may be replaced by "less than", and a condition described as "more than or equal to and less than" may be replaced by "more than and less than or equal to". In addition, "A" to "B" in the following represents at least one of the elements from A (including A) to B (including B).

[0049] In addition, although the present disclosure uses terms used in a part of communication standards (e.g., the 3rd Generation Partnership Project (3GPP), the extensible radio access network (xRAN), the O-RAN) to describe embodiments, it is only for illustrative purposes. One or more embodiments of the present disclosure can also be easily modified and applied to other communication and broadcast systems.

[0050] As the fourth generation (4G) / fifth generation (5G) communication systems (e.g., New Radio (NR)) have been commercialized, users in virtualized networks have required differentiated service support. 3GPP is a joint research project among mobile communication-related groups and aims to establish third-generation mobile communication system standards within the scope of the International Telecommunication Union (ITU)'s IMT-2000 project applicable globally. 3GPP was established in December 1998, and the 3GPP standard is based on the advanced GSM standard and includes all radio, core network, and service architectures within the scope of standardization. Therefore, the O-RAN has newly defined radio units (RUs), digital units (DUs), central units (CUs)-control plane (CP), and CUs-user plane (UP), which are nodes that configure 3GPP network entities (NEs) and base stations as O-RAN (O)-RUs, O-DUs, O-CU-CPs, and O-CU-UPs respectively, and has additionally standardized the near real-time (NRT) radio access network intelligent controller (RIC) (hereinafter referred to as the "near RT RIC", sometimes simply referred to as the "RIC"). The present disclosure can support an operator-specific service model on the E2 interface, where the RIC requests services from the O-DU, O-CU-CP, or O-CU-UP. Herein, the O-RU, O-DU, O-CU-CP, and O-CU-UP can be understood as objects that configure a RAN capable of operating according to the O-RAN standard and can be referred to as E2 nodes. The application protocol (E2AP) is used for the interface between the RIC and the E2 node for configuring an object of a RAN capable of operating according to the O-RAN standard.

[0051] The RIC is a logical node capable of collecting information at the cell site that is transmitted and received by the terminal and the O-DU, O-CU-CP, or O-CU-UP. The RIC can be implemented in the form of servers densely arranged in one physical location. The connections between the O-DU and the RIC, between the O-CU-CP and the RIC, and between the O-CU-UP and the RIC can be via Ethernet. For this purpose, interface standards for communication between the O-DU and the RIC, between the O-CU-CP and the RIC, and between the O-CU-UP and the RIC have become necessary, and message standards such as E2-DU, E2-CU-CP, and E2-CU-UP and definitions of procedures between the O-DU, O-CU-CP, O-CU-UP, and the RIC are required. Specifically, since users in the virtualized network require differentiated service support and the call processing messages / functions generated by the O-RAN are concentrated on the RIC, functional definitions of the messages of E2-DU, E2-CU-CP, and E2-CU-UP are needed to support services with a wide range of cell coverage.

[0052] The RIC can communicate with the O-DU, O-CU-CP, and O-CU-UP by using the E2 interface and can set event occurrence conditions by generating and sending subscription messages. Specifically, the RIC can establish call processing events by generating an E2 subscription request message and delivering it to an E2 node (e.g., O-CU-CP, O-CU-UP, and O-DU). In addition, after the event is established, the E2 node delivers a subscription request response message that is delivered to the RIC.

[0053] The E2 node can send the current status to the RIC by an indication / report message (e.g., RIC indication message). The RIC can provide control over the O-DU, O-CU-CP, and O-CU-UP by using a control message (e.g., RIC control message). One or more embodiments of the present disclosure report information for identifying user equipment throughput by network slice and accordingly propose a method for allocating resources by network slice.

[0054] Figure 1 An example of a fourth-generation (4G) Long-Term Evolution (LTE) core system is shown.

[0055] In Figure 1 it, the LTE core system includes a base station 110, a terminal 120, a Serving Gateway (S-GW) 130, a Packet Data Network Gateway (P-GW) 140, a Mobility Management Entity (MME) 150, a Home Subscriber Server (HSS) 160, and a Policy and Charging Rules Function (PCRF) 170.

[0056] The base station 110 is a network infrastructure that provides wireless access to the terminal 120. For example, the base station 110 is a device that performs scheduling by collecting status information such as the buffer status, available transmission power, and channel status of the terminal 120. The base station 110 has a coverage area defined as a certain geographical area based on the distance at which it can send signals. The base station 110 is connected to the MME 150 through the S1-MME interface. In addition to the base station, the base station 110 may also be referred to as an access point (AP), eNodeB (eNB), wireless point, transmit / receive point (TRP), or another term with an equivalent technical meaning.

[0057] The terminal 120 is a device used by a user and performs communication with the base station 110 through a wireless channel. In some cases, the terminal 120 may be operated without user participation. In other words, the terminal 120 is a device that performs machine type communication (MTC) and may not be carried by a user. In addition to the terminal, the terminal 120 may also be referred to as a user equipment (UE), mobile station, subscriber station, client premise equipment (CPE), remote terminal, wireless terminal, or another term with an equivalent technical meaning.

[0058] The S-GW 130 provides data bearers and generates or controls data bearers according to the control of the MME 150. For example, the S-GW 130 processes packets arriving from the base station 110 or packets to be forwarded to the base station 110. In addition, the S-GW 130 can act as an anchor during the handover of the terminal 120 between base stations. The P-GW 140 can act as a connection point to an external network (e.g., the Internet network). In addition, the P-GW 140 assigns an Internet protocol (IP) address to the terminal 120 and acts as an anchor for the S-GW 130. In addition, the P-GW 140 applies the quality of service (QoS) policy of the terminal 120 and can manage account data.

[0059] The MME 150 manages the mobility of the terminal 120. In addition, the MME 150 can perform authentication and bearer management of the terminal 120. In other words, the MME 150 is responsible for the mobility management and various control functions of the terminal. The MME 150 can be linked to a serving GPRS support node (SGSN).

[0060] The HSS 160 stores key information and subscriber profiles for the authentication of the terminal 120. When the terminal 120 accesses the network, the key information and subscriber profiles are sent from the HSS 160 to the MME 150.

[0061] The PCRF 170 defines the rules for policy and charging. The stored information is sent from the PCRF 170 to the P-GW 140, and the P-GW 140 can perform control (e.g., QoS management, charging, etc.) for the terminal 120 based on the information provided by the PCRF 170.

[0062] Carrier aggregation (hereinafter, CA) technology is a technology that combines multiple component carriers. In this technology, a terminal increases the frequency usage efficiency on the terminal or base station side by simultaneously transmitting and receiving signals using these multiple component carriers. Specifically, according to the CA technology, the terminal and the base station can use broadband transmission and reception signals by using multiple component carriers in the uplink (UL) and the downlink (DL) respectively, and in this case, each component carrier is located in a different frequency band. Hereinafter, the uplink refers to the communication link where the terminal sends signals to the base station, and the downlink refers to the communication link where the base station sends signals to the terminal. In this case, the number of uplink component carriers and downlink component carriers can be different from each other.

[0063] Dual connectivity or multi-connectivity is a technology in which a terminal increases the frequency usage efficiency on the terminal or base station side by simultaneously transmitting and receiving signals using carriers within multiple base stations connected to different base stations and located in different frequency bands. The terminal can be simultaneously connected to a first base station (e.g., a base station that provides services using LTE technology or 4G mobile communication technology) and a second base station (e.g., a base station that provides services using new radio (NR) technology or fifth-generation (5G) mobile communication technology) to transmit and receive traffic. In this case, the frequency resources used by each base station can be located in different frequency bands. In this way, a method of operating based on the LTE and NR dual connectivity method can be referred to as 5G non-standalone (NSA).

[0064] Figure 2a An example of a fifth-generation (5G) non-standalone (NSA) system is shown.

[0065] In Figure 2aIn the 5G NSA system, it includes NR RAN 210a, LTE RAN 210b, terminal 220, and evolved packet core (EPC) 250. NR RAN 210a and LTE RAN 210b are connected to EPC 250, and terminal 220 can receive services from either or both of NR RAN 210a and LTE RAN 210b simultaneously. NR RAN 210a includes at least one NR base station, and LTE RAN 210b includes at least one LTE base station. In this article, the NR base station can be referred to as a fifth-generation node, a next-generation node B (gNB), or another term with an equivalent technical meaning. Additionally, the NR base station can have a structure divided into a central unit (CU) and a digital unit (DU). Furthermore, the CU can have a structure divided into a control plane (CU-CP) unit and a user plane (CU-UP) unit.

[0066] In Figure 2a In the structure shown, terminal 220 can perform radio resource control (RRC) access through the first base station (e.g., a base station belonging to LTE RAN 210b) and receive services provided by the control plane (e.g., connection management, mobility management, etc.). Additionally, terminal 220 can be provided with additional radio resources to send and receive data through the second base station (e.g., a base station belonging to NR RAN 210a). This dual-connectivity technology using LTE and NR can be referred to as evolved universal terrestrial radio access (E-UTRA)-NR dual connectivity (EN-DC). Similarly, the dual-connectivity technology where the first base station uses NR technology and the second base station uses LTE technology is called NR-E-UTRA dual connectivity (NE-DC). Moreover, one or more embodiments can be applied to various other forms of multi-connectivity and carrier aggregation technologies. Additionally, one or more embodiments can be applied even when the first system using the first communication technology and the second system using the second communication technology are implemented in one device, or when the first base station and the second base station are located in the same geographical location.

[0067] Figure 2b An example of the O-RAN architecture is shown. For the purpose of key performance indicator (KPI) monitoring of the E2 service model (E2-SM-KPI), although the O-RAN non-standalone mode within the multi-connectivity operation using E-UTRA and NR radio access technologies is considered, it can be assumed that the E2 node is in the O-RAN standalone mode.

[0068] In Figure 2bIn the deployment of the O-RAN non-standalone mode, the eNB is connected to the EPC through the S1-C / S1-U interfaces and to the O-CU-CP through the X2 interface. The O-CU-CP for the deployment of the O-RAN standalone mode can be connected to the 5G Core (5GC) through the N2 / N3 interfaces.

[0069] Considering the services that the 5G mobile communication technology aims to support, discussions are underway for the improvement and performance enhancement of the initial 5G mobile communication technology, and physical layer standardization of technologies such as the following is underway: V2X (Vehicle-to-Everything), which is used to assist the driving determination of autonomous vehicles and enhance user convenience based on the location and status information of vehicles sent by vehicles; New Radio Unlicensed (NR-U), which aims to meet the various specification requirements in the unlicensed band for system operation; NRUE power saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication to provide coverage in areas where communication with the terrestrial network is unavailable; and positioning.

[0070] Standardization of technologies such as the following is also underway in the field of radio interface architecture / protocols: Industrial Internet of Things (IIoT), which is used to support new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB), which is used to integrate and support wireless backhaul links and access links to provide nodes for network service area expansion; mobility enhancement, including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access, which is used to simplify the random access process (two-step RACH for NR); and standardization of the 5G baseline architecture (e.g., service-based architecture, service-based interface) that combines network function virtualization (NFV) and software-defined networking (SDN) technologies, mobile edge computing (MEC) that receives services based on the location of the terminal, etc. is also underway in the field of system architecture / protocols.

[0071] When such a 5G mobile communication system is commercialized, an explosive growth of connected devices will be connected to the communication network, and therefore, enhancements to the functions and performance of the 5G mobile communication system and integrated operation of the connected devices are expected. To this end, new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication by effectively supporting augmented reality (AR), virtual reality (VR), and mixed reality (MR), artificial intelligence (AI), and machine learning (ML) using extended reality (XR).

[0072] In addition, the development of such a 5G mobile communication system can be used as a basis for the development of: full-duplex technology to enhance the frequency efficiency of 6G mobile communication technology and improve the system network; AI-based communication technology to achieve system optimization by leveraging satellites and artificial intelligence (AI) from the design phase and internalizing end-to-end AI support functions; next-generation distributed computing technology to achieve complex services beyond the limitations of terminal computing capabilities using ultra-high-performance communication and computing resources; and multi-antenna transmission technology, such as new waveforms for ensuring the coverage of 6G mobile communication technology in the terahertz band, full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, high-dimensional spatial multiplexing technology using metasurface-based lenses and antennas for improving the coverage of terahertz band signals and orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS) technology.

[0073] Figures 1 to 2b An example of a 4G and / or 5G environment is shown, but this description does not limit the scope of the communication environment of the embodiments of the present disclosure. The technical principles according to the embodiments of the present disclosure can also be applied to 6G and post-6G communication technologies and network environments.

[0074] Figure 3 An example of the protocol stack of the E2 application protocol message in the radio access network is shown.

[0075] In Figure 3 , the control plane includes a transport network layer and a radio network layer. The transport network layer includes a physical layer 310, a data link layer 320, an Internet protocol (IP) 330, and a stream control transmission protocol (SCTP) 340.

[0076] The radio network layer includes an E2AP 350. The E2AP 350 is used to deliver subscription messages, indication messages, control messages, service update messages, and service query messages, and is sent at a higher layer of the SCTP 340 and the IP 330.

[0077] Figure 4 An example of the connection between a base station and a RIC in the radio access network is shown.

[0078] In Figure 4In it, the RIC 440 is connected to the O-CU-CP 420, O-CU-UP 410, and O-DU 430. The RIC 440 is a device for customizing RAN functions for new services or regional resource optimization. The RIC 440 can provide functions such as network intelligence (e.g., policy enforcement, handover optimization), resource assurance (e.g., radio link management, advanced self-organizing network (SON)), and resource control (load balancing, slicing strategy). The RIC 440 can communicate with the O-CU-CP 420, O-CU-UP 410, and O-DU 430. The RIC 440 can be connected to each node through the E2-CP, E2-UP, and E2-DU interfaces. Additionally, the interfaces between the O-CU-CP and the DU and between the O-CU-UP and the DU can be referred to as the F1 interface. In the following description, the DU and the O-DU, the CU-CP and the O-CU-CP, and the CU-UP and the O-CU-UP can be used interchangeably.

[0079] Figure 4 One RIC 440 is shown, but according to one or more embodiments, there can be multiple RICs. The multiple RICs can be implemented with multiple hardwares located at the same physical location, or can be implemented using one hardware through virtualization.

[0080] Figure 5 An example of the configuration of devices in a radio access network is shown.

[0081] Figure 5 The structure shown can be understood as Figure 5 a configuration of a device having at least one function of a near RT RIC, a non-RT RIC, an O-CU-CP, an O-CU-UP, and an O-DU. Hereinafter, terms such as “… unit” and “… device” used below indicate a unit that processes at least one function or operation, and can be implemented by hardware, software, or a combination of hardware and software.

[0082] In Figure 5 the core network device includes a transceiver 510, a memory 520, and a processor 530.

[0083] The transceiver 510 provides an interface for performing communication with other devices in the network. That is, the transceiver 510 converts the bit string sent from the core network device to another device into a physical signal, and converts the physical signal received from another device into a bit string. That is, the transceiver 510 can send and receive signals. Therefore, the transceiver 510 can be referred to as a communication unit, a modem, a sending unit, a receiving unit, or a sending / receiving unit. At this time, the transceiver 510 enables the core network device to communicate with other devices or systems through a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or a network. Although Figure 5Only one transceiver 510 is shown, but the device may include one or more transceivers.

[0084] The memory 520 stores data for the operation of the core network device, such as basic programs, application programs, and setting information. The memory 520 may be referred to as a storage unit. The memory 520 may be configured with volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the memory 520 provides the stored data according to the request of the processor 530.

[0085] The processor 530 controls the overall operation of network element (NE) devices such as E2 nodes or near RT RICs. For example, the processor 530 transmits and receives signals through the transceiver 510. Additionally, the processor 530 records data in and reads from the memory 520. Although Figure 5 only one processor 530 is shown, the device may include one or more processors. According to one or more embodiments, the processor 530 may control the device to perform operations according to one or more embodiments described in the present disclosure.

[0086] Figure 6 An example of the logical functions related to E2 messages between an E2 node and a RIC in a radio access network is shown. An E2 message may be understood as a message sent through the E2 interface.

[0087] In Figure 6 the RIC 640 and the E2 node 610 may send or receive E2 messages to and from each other. For example, the E2 node 610 may be an O-CU-CP, O-CU-UP, O-DU, or a base station. The communication interface of the E2 node may be determined according to the type of the E2 node 610. For example, the E2 node 610 may communicate with another E2 node 616 through an E1 interface or an F1 interface. Alternatively, for example, the E2 node 610 may communicate with the E2 node 616 through an X2 interface or an XN interface. Alternatively, for example, the E2 node 610 may communicate through an S1 interface or a next generation application protocol (NGAP) interface (i.e., the interface between a next generation (NG) RAN node and an AMF).

[0088] The E2 node 610 may include an E2 node function 612. The E2 node function 612 is a function corresponding to a specific application S / W (xApp) 646 installed in the RIC 640. For example, in the case of KPI monitoring, the KPI monitoring collection S / W is installed in the RIC 640, and the E2 node 610 may include an E2 node function 612. After generating KPI parameters, the E2 node function 612 sends an E2 message including the KPI parameters to the E2 termination 642 located in the RIC 640. The E2 node 610 may include radio resource management (RRM) 614. The E2 node 610 may manage radio network resources provided for the terminal.

[0089] The E2 termination 642 located in the RIC 640 is the termination of the RIC 640 for E2 messages and performs the function of interpreting the E2 messages delivered by the E2 node 610 and then delivering them to the xApp 646. The database (DB) 644 located in the RIC 640 may be used by the E2 termination 624 or the xApp 646. Figure 6 The E2 node 610 shown in is the termination of at least one interface and may be understood as the termination of messages delivered to the terminal, surrounding base stations, and the core network.

[0090] Figure 7 An example of the functional division between the E2 node and the RIC is shown.

[0091] The O-RAN standard provides a functional division between the E2 node and the RIC. For example, the E2 node may be a CU. The RIC may be a near RT RIC. The RIC may be connected to the Open Network Automation Platform (ONAP) / Management and Orchestration (MANO) / Network Management System (NMS) through the A1 interface. The RIC may be connected to the E2 node through the E2 interface. The E2 interface may send commands. The functional division options may include a functional division 700 in which the entire RRM is managed by the near RT RIC, and a functional division 750 in which the RRM is selectively managed by the near RT RIC.

[0092] According to the WG3 decision of the meeting, the near RT RIC will support E2 as an open logical interface targeting a multi-vendor environment, regardless of the specific RRC-RRM algorithm implementation located in the near RT RIC. In this disclosure, an E2 service model radio interface control (E2SM-RIC) paired with E2SM-NI can be proposed, and E2SM-NI is capable of injecting / modifying / configuring each UE RRC message for each interface (I / F) and network entity (NE). In other words, the near RT RIC can be gradually improved in the direction of the functional division 750 from the functional division 700. E2 can be developed as an open logical interface that is independent of the implementation of the specific RRC-RRM algorithm in the near RT-RIC and targets a multi-vendor environment.

[0093] Figure 8 An implementation example of the E2 node and the RIC is shown.

[0094] In Figure 8 In the scenario of the implementation example 800, the E2 node (e.g., O-DU, O-CU) and the RIC can be virtualized on a cloud platform (e.g., open chassis and blade specification edge cloud) to be configured on a device (e.g., a server). This scenario can support deployment in dense urban areas, where the rich front-hole capacity allows the BBU function to be pooled to a central location with a sufficiently low latency to meet the O-DU latency requirements. Therefore, there may be no need to try to centralize the RIC near the RT beyond the limit of centralizing the O-DU function. According to an embodiment, the E2SM-RIC can be optimized for the O-RAN deployment scenario, where the near RT RIC, O-CU, and O-DU are implemented on the O-cloud platform.

[0095] Figure 9 An example of the functional division between the central unit (CU) and the RIC is shown.

[0096] In Figure 9 In it, the functional division can be performed according to the deployment scenario #1 900 or the functional deployment scenario #2 950.

[0097] Deployment scenario #1 900: The RIC is located at a separate site or exists only as a different NE, replacing or recommending some intelligent basic features.

[0098] Deployment scenario #2 950: In addition to 3GPP I / F management, the RIC can replace almost all the functions of the CU.

[0099] Figure 9Two scenarios are shown, but other scenarios can be applied. For example, in deployment scenario #1900, the mobility function can be performed by the RIC instead of the CU. Additionally, for example, in deployment scenario #1900, the UE context function can be performed by the RIC instead of the CU. Additionally, for example, in deployment scenario #1900, the session establishment function can be performed by the RIC instead of the CU.

[0100] Figure 10a An example of the connection between the RIC, the E2 node, and the terminal in the radio access network is shown.

[0101] In Figure 10a this, the near RT RIC (hereinafter referred to as "RIC") 1020 can be connected to the DU 1010, and the DU 1010 is connected to multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4. The DU 1010 can also be referred to as an O-DU. For ease of explanation, Figure 10a the example of the connection state of the RIC 1020, the DU 1010, and the terminals 1030-1, 1030-2, 1030-3, and 1030-4 in this is merely illustrative, and the embodiments of the present disclosure are not limited to Figure 10a the example in this. For example, the DU 1010 is an example of an E2 node, and in the embodiments of the present disclosure, the E2 node connected to the RIC 1020 will not be limited to the DU 1010. For example, the DU 1010 can be understood to be substantially the same as the CU, CU-UP, and CU-CP. Additionally, Figure 10a the example in this shows that the RIC 1020 is connected to the DU1010, but the RIC 1020 can be connected to multiple DUs 1010. Additionally, Figure 10a the example in this shows that the DU 1010 is connected to four terminals 1030-1, 1030-2, 1030-3, and 1030-4, but the DU 1010 can be connected to at least one terminal.

[0102] Network slicing refers to the method of virtualizing the physical network and using it as multiple networks. A network slice can refer to a virtualized network. A service level agreement (SLA) including throughput, latency, and reliability can be defined for each "network slice" (or "slice"). The SLA can indicate an agreement that defines the target values of the service between the service provider providing the service and the user receiving the service when providing services through the slice. For example, the SLA can include the throughput at different terminal levels according to the slice.

[0103] For example, DU 1010 can configure at least one cell. The cell can be associated with at least one network slice for providing various services. For example, the first cell can be associated with network slice A to provide service x and associated with network slice B to provide service y. Additionally, the second cell can be associated with network slice C to provide service x.

[0104] DU 1010 can allocate resources to serve multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4. For example, DU 1010 can allocate resources to provide services based on the control information received from RIC 1020. For example, in the same cell (e.g., the first cell), DU 1010 can allocate resources to provide service x and service y for multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4. For example, DU 1010 can allocate resources for multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4 based on the resource information received from RIC 1020.

[0105] As described above, DU 1010 can measure the status of the services provided for multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4 (e.g., key performance indicators (KPIs)) and send the measured information to RIC 1020. RIC 1020 can identify resource allocation information to serve multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4 based on the information received from DU 1010. RIC 1020 can send control information including the resource allocation information to DU 1010.

[0106] RIC 1020 can control DU 1010 based on the status (or KPI) of the services provided through the E2 interface. For example, RIC 1020 can identify whether the services provided to terminals 1030-1, 1030-2, 1030-3, and 1030-4 meet the SLA required by the operator. RIC 1020 can control DU 1010 according to the identification result. For example, identifying whether the SLA required by the operator is met can be understood as identifying whether the throughput at the terminal level is greater than or equal to the reference value. The throughput at the terminal level can be identified based on the data volume at a specific time.

[0107] The operator can identify whether the services provided for each of the multiple terminals 1030-1, 1030-2, 1030-3, and 1030-4 meet the SLA and request the best service for each terminal. However, the DU 1010 may have difficulty distinguishing the terminals receiving services through all the cells supported by the DU 1010 and at least one slice associated with each cell, and have difficulty identifying the throughput of each terminal. Since multiple slices can be set for one terminal, identifying the data volume and time provided by each terminal and managing the throughput by each terminal by the DU 1010 may be limited by the complexity and memory limitations of the DU 1010.

[0108] Previously, the DU 1010 could report to the RIC 1020 the total sum of the data volume sent without distinguishing terminals for the slices associated with each cell and the total sum of the time when each data volume was scheduled. Therefore, the RIC 1020 could control the DU 1010 based on the data volume provided for each slice and the information about the time of scheduling the data volume. However, the performance of the network that identifies and provides services based on the data volume provided for each slice and the information about the scheduling time may be different from the actual service provision status. Details related to this will be described in the Figure 10b below.

[0109] Figure 10b An example of the data volume according to the time flow for identifying the user equipment throughput is shown.

[0110] Figure 10b A first example 1050 of allocating a large amount of data in a relatively short period and a second example 1060 of allocating a large amount of data in a relatively long period are shown. The horizontal axis of the first example 1050 and the second example 1060 indicates time, and the vertical axis indicates the data volume.

[0111] In the first example 1050, the resources 1055 for providing services to the terminal can be allocated to have a first data volume during a first time period. In the second example 1060, the resources 1065 for providing services to the terminal can be allocated to have a second data volume lower than the first data volume during a second time longer than the first time. It is assumed that the total sum of the data volume during the entire time interval 1070 of the first example 1050 and the second example 1060 is the same. The entire time interval 1070 can be referred to as the collection period for measuring the data volume so that the DU can identify the throughput of the terminals for each slice.

[0112] In the above-described examples 1050 and 1060, where DU identifies the throughput of resources scheduled to the terminal for each slice, the throughput can be identified based on the ratio of the data volume provided for each slice and the time information during which the data volume is scheduled, and it can be identified whether the throughput is greater than or equal to a reference value. Considering that only the first data volume of the first example 1050 is scheduled during the first time period, the throughput of the first example 1050 can meet the SLA standard. On the other hand, considering that the second data volume of the second example 1060 is scheduled during the second time period, the throughput of the second example 1060 may not meet the SLA standard. However, since resources are not allocated to the terminal of the first example 1050 except at a specific time (e.g., the first time), it may not be possible to substantially provide services. Therefore, identifying the throughput of resources scheduled to the terminal may only indicate the performance at the modem level, and may not be suitable for evaluating the performance at the application level. The performance at the modem level is the performance of the part where data exists, and the performance at the application level is the performance during the time when services are actually provided to users.

[0113] In the following, the present disclosure proposes a method for sending to the RIC the time interval for collecting the data volume sent by the DU, the sum of the data volumes sent by each slice related to the cell, and the number of terminals (or the number of data radio bearers (DRBs)) of each slice, and controlling the resource allocation of the DU based on the user equipment throughput identified thereby.

[0114] Figure 11 An example of resource allocation showing the user equipment throughput based on slices is shown.

[0115] In Figure 11 , in operation 1100, the DU 1110 can send reporting information to the RIC 1120. According to an embodiment, the reporting information may include information about the number of UEs connected to the cell provided to the DU 1110. For example, the reporting information may include the following information.

[0116] [Table 1]

[0117]

[0118] According to an embodiment, the reporting information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for reporting throughput (throughput-report). The information for reporting throughput may include the amount of data sent, the collection duration, and the number of terminals (user equipment (UE)). For example, the amount of data sent may indicate the sum of the amount of data during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving the terminals are measured. The entire time interval may include the time when the amount of data exists and the time when the amount of data does not exist. The number of terminals may indicate the total number of terminals associated with the amount of data of a slice of a specific cell. The reporting information may include an allocated PRB portion and PRB usage. The reporting information may be referred to as performance data (or performance measurement).

[0119] According to an embodiment, the DU 1110 may collect or identify information for reporting throughput. For example, the DU 1110 may collect or identify information for reporting the throughput of each slice associated with a specific cell. For example, the DU 1110 may collect or identify the sum of the amount of data sent during a specific reporting period for each slice. The specific reporting period may be referred to as the collection duration. Additionally, the DU 1110 may collect or identify the total number of terminals receiving service through the amount of data sent through each slice.

[0120] According to an embodiment, the DU 1110 may send the reporting information to the RIC 1120 through the E2 interface. For example, the reporting information may be included in an indication message. For example, the indication message may include a RIC indication message. For example, the RIC indication message may include a message container, and the message container may include the reporting information.

[0121] In operation 1105, the RIC 1120 may send control information to the DU 1110. For example, the RIC 1120 may send the control information to the DU 1110 through the E2 interface. According to an embodiment, the control information may include information about the maximum PRB portion of each slice associated with a specific cell. For example, the control information may be included in a control message. For example, the control message may include a RIC control message.

[0122] According to an embodiment, the RIC 1120 may receive reporting information from the DU 1110 and identify the user equipment throughput (or user equipment-level throughput) of each slice associated with a specific cell based on the received reporting information. For example, the RIC 1120 may identify the average value of the user equipment throughput of each slice based on the reporting information. The average value of the user equipment throughput may be identified based on the sum of the data volume transmitted during the collection duration, the length of the collection duration, and the total number of terminals.

[0123] According to an embodiment, the RIC 1120 may identify whether the SLA of each slice is satisfied based on the average value of the identified user equipment throughput and a reference throughput. The reference throughput may be set to a predetermined value by an operator according to the SLA. The SLA may indicate a metric for indicating service characteristics.

[0124] According to an embodiment, when the average value of the user equipment throughput satisfies the SLA, the RIC 1120 may maintain the current resource allocation state of each slice. On the other hand, when the average value of the user equipment throughput does not satisfy the SLA, the RIC 1120 may identify the resource allocation size to change the resource allocation state of each slice so as to satisfy the SLA. For example, when the average value of the user equipment throughput of the first slice satisfies the first SLA associated with the first slice and the average value of the user equipment throughput of the second slice does not satisfy the second SLA associated with the second slice, the RIC 1120 may change the resource allocation state of the first slice and the resource allocation state of the second slice. For example, the RIC 1120 may change the resource allocation state of the first slice within a range where the changed average value of the user equipment throughput of the first slice satisfies the first SLA. In addition, the RIC 1120 may change the resource allocation state of the second slice such that the changed average value of the user equipment throughput of the second slice satisfies the second SLA. The resource information (or resource allocation size) for changing the resource allocation state may include the maximum portion of PRBs of each slice associated with a specific cell.

[0125] Although Figure 11 not shown in the figure, the DU 1110 may identify the resource size allocated to a terminal for each slice through the control information received in operation 1105 and may allocate resources to the terminal for each slice based on the identified resource size. In addition, the DU 1110 may provide a service corresponding to the slice to the terminal through the allocated resources.

[0126] Figure 11An example of operation 1105 is shown in which the RIC 1120 generates control information based on the reported information received through operation 1100 and sends it to the DU 1110, but embodiments of the present disclosure are not limited thereto. For example, the RIC 1120 may identify and only store the reported information received from operation 1100, and may not immediately generate control information based on the received reported information. In other words, operation 1105 may not have to be continuously performed after operation 1100. Alternatively, the RIC 1120 may send control information based on other information rather than the received reported information.

[0127] Figure 11 An example of the DU 1110 as an E2 node is shown. The DU 1110 sends or receives signals to / from the near RT RIC to explain the operation for controlling resource allocation. However, embodiments of the present disclosure are not limited thereto. For example, in addition to the DU 1110, the E2 node may further include a CU, a CU-CP, or a CU-UP.

[0128] Although not shown in Figure 11 According to another embodiment, the previous process of the E2 interface may be performed first. The DU1110 may be connected to the near RT RIC 1120 (hereinafter referred to as the RIC). For example, the DU 1110 may send an E2 establishment request (establishment request) message to the RIC 1120. The E2 node function located in the DU 1110 may find the RIC using the IP address of the RIC 1120 set for operation - administration - maintenance (OAM) and send an E2 establishment request message. The E2 establishment request message may include information about the RAN functions supported by the DU 1110 (e.g., RAN function definition) and E2 node ID information, etc. The RAN function definition value is a value set for OAM. For example, the RAN function definition value may include a STYLE ID value. The RIC 1120 may determine which call processing functions are supported by the DU 1110 based on the RAN function definition value by receiving information about the value set for OAM.

[0129] In response to the E2 establishment request message, the RIC 1120 may receive an E2 establishment response (E2 establishment response) message from the DU 1110. The RIC 1120 may determine whether the E2 establishment response message sent by the DU 1110 is acceptable. When the E2 establishment request message is acceptable, the RIC 1120 may send the E2 establishment response message to the DU 1110.

[0130] The RIC 1120 can send a subscription request (RIC subscription request) message to the E2 node. A specific xApp located in the RIC 1120 requests a subscription (or join) to a function defined by a specific RAN function supported by E2 from the RIC E2 termination function. According to an embodiment, the subscription request message and the E2 establishment response message can be sent separately. According to another embodiment, the subscription request message can be included in the E2 establishment response message and sent together.

[0131] The DU 1110 can send a subscription request response (RIC subscription response) to the RIC 1120. The E2 node function of the DU 1110 can decode the subscription request message. After the RIC 1120 successfully sets the event condition requested by the E2 node function, the E2 node function of the DU 1110 can deliver to the RIC 1120 via the subscription response that the event trigger condition has been successfully set.

[0132] As described above, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can evaluate the application-level performance by sending information about the entire time interval of the measured data volume instead of the sum of the time intervals in which there is an actual data volume. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the performance in the case of providing actual services to the terminal by sending information over the entire time interval, even if a high data volume is allocated in a short time interval. In addition, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the average value of the user equipment throughput by sending the total number of terminals of the slice related to a specific cell. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the throughput of each terminal of each slice and provide a throughput guarantee service for each terminal.

[0133] Figure 12 An example of resource allocation showing slice-based user equipment throughput is presented.

[0134] In Figure 12 In operation 1200, the DU 1210 can send reporting information to the RIC 1220. According to an embodiment, the reporting information can include information about the number of DRBs of the cell provided to the DU 1210. For example, the reporting information can include the following information.

[0135] [Table 2]

[0136]

[0137] According to an embodiment, the reported information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, and the number of DRBs. For example, the amount of data transmitted may indicate the sum of the amount of data during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving a terminal are measured. The entire time interval may include the time when the amount of data exists and the time when the amount of data does not exist. The number of DRBs may indicate the total number of DRBs associated with the amount of data of a slice of a specific cell. In other words, the information for throughput reporting may include the total number of DRBs corresponding to the entire terminal associated with the amount of data of a slice of a specific cell. The reported information may include the allocated PRB portion and PRB usage. The reported information may be referred to as performance data (or performance measurement).

[0138] According to an embodiment, the DU 1210 may identify the information for throughput reporting. For example, the DU 1210 may identify (or collect) the information for throughput reporting for each slice associated with a specific cell. For example, the DU 1210 may identify, for each slice, the sum of the amount of data transmitted during a specific reporting period. The specific reporting period may be referred to as the collection duration. Additionally, the DU 1210 may identify the total number of terminals receiving service based on the amount of data transmitted for each slice.

[0139] According to an embodiment, the DU 1210 may send the reported information to the RIC 1220 via the E2 interface. For example, the reported information may be included in an indication message. For example, the indication message may include a RIC indication message. For example, the RIC indication message may include a message container, and the message container may include the reported information.

[0140] In operation 1205, the RIC 1220 may send control information to the DU 1210. For example, the RIC 1220 may send the control information to the DU 1210 via the E2 interface. According to an embodiment, the control information may include information about the maximum PRB portion for each slice associated with a specific cell. For example, the control information may be included in a control message. For example, the control message may include a RIC control message.

[0141] According to an embodiment, the RIC 1220 may receive reporting information from the DU 1210 and identify the user equipment throughput of each slice associated with a specific cell based on the received reporting information. For example, the RIC 1220 may identify the average value of the user equipment throughput of each slice based on the reporting information. The average value of the user equipment throughput may be identified based on the sum of the data volume transmitted during the collection duration, the length of the collection duration, and the total number of DRBs. For example, when there is a one-to-one correspondence between the UE and the DRB, the total number of DRBs may indicate the total number of terminals for each slice.

[0142] According to an embodiment, the RIC 1220 may identify whether the SLA of each slice is satisfied based on the identified average value of the user equipment throughput and a reference throughput. The reference throughput may be set to a predetermined value by an operator according to the SLA. The SLA may indicate a metric for indicating service characteristics.

[0143] According to an embodiment, when the average value of the user equipment throughput satisfies the SLA, the RIC 1220 may maintain the current resource allocation state of each slice. On the other hand, when the average value of the user equipment throughput does not satisfy the SLA, the RIC 1220 may identify the resource allocation size to change the resource allocation state of each slice so as to satisfy the SLA. For example, when the average value of the user equipment throughput of the first slice satisfies the first SLA associated with the first slice and the average value of the user equipment throughput of the second slice does not satisfy the second SLA associated with the second slice, the RIC 1220 may change the resource allocation state of the first slice and the resource allocation state of the second slice. For example, the RIC 1220 may change the resource allocation state of the first slice within a range where the changed average value of the user equipment throughput of the first slice satisfies the first SLA. In addition, the RIC 1220 may change the resource allocation state of the second slice such that the changed average value of the user equipment throughput of the second slice satisfies the second SLA. The resource information (or resource allocation size) for changing the resource allocation state may include the maximum portion of PRBs for each slice associated with a specific cell.

[0144] Although Figure 12 not shown, the DU 1210 may identify the resource size allocated to a terminal for each slice based on the control information received in operation 1205 and allocate resources to the terminal for each slice based on the identified resource size. In addition, the DU 1210 may provide a service corresponding to the slice to the terminal through the allocated resources.

[0145] Figure 12An example of operation 1205 is shown in which the RIC 1220 generates control information based on the reported information received through operation 1200 and sends the control information to the DU 1210. However, embodiments of the present disclosure are not limited thereto. For example, the RIC 1220 may identify and only store the reported information received from operation 1200 and may not immediately generate control information based on the received reported information. In other words, operation 1205 may not have to be continuously performed after operation 1200. Alternatively, the RIC 1220 may send control information based on other information rather than the received reported information.

[0146] Figure 12 An example of the DU 1210 as an E2 node is shown. The DU 1210 sends or receives signals with the near RT RIC to explain the operation for controlling resource allocation. However, embodiments of the present disclosure are not limited thereto. For example, in addition to the DU 1210, the E2 node may further include a CU, a CU-CP, or a CU-UP.

[0147] Although not shown in Figure 12 According to another embodiment, the previous process of the E2 interface may be performed first. The DU 1210 may be connected to the near RT RIC 1220. For example, the DU 1210 may send an E2 establishment request (establishment request) message to the RIC 1220. The E2 node function located in the DU 1210 may find the RIC using the IP address of the RIC 1220 set for operation - administration - maintenance (OAM) and send an E2 establishment request message. The E2 establishment request message may include information about the functions of the RAN supported by the DU 1210 (e.g., RAN function definition), E2 node ID information, etc. The RAN function definition value is a value set for OAM. For example, the RAN function definition value may include a STYLE ID value. The RIC 1220 may determine which call processing functions are supported by the DU 1210 based on the RAN function definition value by receiving information about the value set for OAM.

[0148] In response to the E2 establishment request message, the RIC 1220 may receive an E2 establishment response (E2 establishment response) message from the DU 1210. The RIC 1220 may determine whether the E2 establishment request message sent by the DU 1210 is acceptable. When the E2 establishment request message is acceptable, the RIC 1220 may send the E2 establishment response message to the DU 1210.

[0149] The RIC 1220 can send a subscription request (RIC subscription request) message to the E2 node. A specific xApp located in the RIC 1220 requests a subscription (or join) to a function defined by a specific RAN function supported by E2 from the RIC E2 termination function. According to an embodiment, the subscription request message and the E2 establishment response message can be sent separately. According to another embodiment, the subscription request message can be included in the E2 establishment response message and sent together.

[0150] The DU 1210 can send a subscription request response (RIC subscription response) to the RIC 1220. The E2 node function of the DU 1210 can decode the subscription request message. After the RIC 1220 successfully sets the event conditions requested from the E2 node function, the E2 node function of the DU 1210 can deliver to the RIC 1220 via the subscription response that the event trigger conditions have been successfully set.

[0151] As described above, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can evaluate the application-level performance by sending information about the entire time interval of the measured data volume rather than the sum of the time intervals in which there is an actual data volume. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the performance in the case of providing actual services to the terminal by sending information over the entire time interval, even if a high data volume is allocated in a short time interval. In addition, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the average value of the user equipment throughput by sending the total number of DRBs of the slice related to a specific cell. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the throughput of each terminal of each slice and provide a throughput guarantee service for each terminal.

[0152] Figure 13 An example of resource allocation showing the user equipment throughput based on slices is presented.

[0153] In Figure 13 In operation 1300, the DU 1310 can send report information to the RIC 1320. According to an embodiment, the report information may include information about the number of UEs connected to the cell provided to the DU 1310 and the number of DRBs of the cell. For example, the report information may include the following information.

[0154] [Table 3]

[0155]

[0156] According to an embodiment, the reporting information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, the number of terminals, and the number of DRBs. For example, the amount of data transmitted may indicate the total amount of data during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving the terminals are measured. The entire time interval may include the time when the amount of data exists and the time when the amount of data does not exist. The number of terminals may indicate the total number of terminals associated with the amount of data of a slice of a specific cell. The number of DRBs may indicate the total number of DRBs associated with the amount of data of a slice of a specific cell. In other words, the information for throughput reporting may include the total number of DRBs corresponding to the entire terminals associated with the amount of data of a slice of a specific cell. The reporting information may include an allocated PRB portion and PRB usage. The reporting information may be referred to as performance data (or performance measurement).

[0157] According to an embodiment, the DU 1310 may identify the information for throughput reporting. For example, the DU 1310 may identify (or collect) the information for throughput reporting for each slice associated with a specific cell. For example, the DU 1310 may identify the total amount of data transmitted during a specific reporting period for each slice. The specific reporting period may be referred to as the collection duration. Additionally, the DU 1310 may identify the total number of terminals receiving service based on the amount of data transmitted for each slice.

[0158] According to an embodiment, the DU 1310 may send the reporting information to the RIC 1320 via the E2 interface. For example, the reporting information may be included in an indication message. For example, the indication message may include a RIC indication message. For example, the RIC indication message may include a message container, and the message container may include the reporting information.

[0159] In operation 1305, the RIC 1320 may send control information to the DU 1310. For example, the RIC 1320 may send the control information to the DU 1310 via the E2 interface. According to an embodiment, the control information may include information about the maximum PRB portion for each slice associated with a specific cell. For example, the control information may be included in a control message. For example, the control message may include a RIC control message.

[0160] According to an embodiment, the RIC 1320 may receive reporting information from the DU 1310 and identify the user equipment throughput of each slice associated with a specific cell based on the received reporting information. For example, the RIC 1320 may identify the average value of the user equipment throughput of each slice based on the reporting information. The average value of the user equipment throughput may be identified based on the sum of the data volume transmitted during the collection duration, the length of the collection duration, the total number of terminals, and the total number of DRBs. For example, the RIC 1320 may identify the average value of the user equipment throughput by the total number of terminals and the total number of DRBs. By considering the number of DRBs corresponding to each terminal, the RIC 1320 may more accurately identify the throughput of each terminal of the slice.

[0161] According to an embodiment, the RIC 1320 may identify whether the SLA of each slice is satisfied based on the identified average value of the user equipment throughput and a reference throughput. The reference throughput may be set to a predetermined value by the operator according to the SLA. The SLA may indicate a metric for indicating service characteristics.

[0162] According to an embodiment, when the average value of the user equipment throughput satisfies the SLA, the RIC 1320 may maintain the current resource allocation state of each slice. On the other hand, when the average value of the user equipment throughput does not satisfy the SLA, the RIC 1320 may identify the resource allocation size to change the resource allocation state of each slice so as to satisfy the SLA. For example, when the average value of the user equipment throughput of the first slice satisfies the first SLA associated with the first slice and the average value of the user equipment throughput of the second slice does not satisfy the second SLA associated with the second slice, the RIC 1320 may change the resource allocation state of the first slice and the resource allocation state of the second slice. For example, the RIC 1320 may change the resource allocation state of the first slice within a range where the changed average value of the user equipment throughput of the first slice satisfies the first SLA. In addition, the RIC 1320 may change the resource allocation state of the second slice such that the changed average value of the user equipment throughput of the second slice satisfies the second SLA. The resource information (or resource allocation size) for changing the resource allocation state may include the maximum portion of the PRBs for each slice associated with a specific cell.

[0163] Although Figure 13 not shown in the figure, the DU 1310 may identify the resource size allocated to the terminal for each slice through the control information received in operation 1305 and allocate resources to the terminal for each slice based on the identified resource size. In addition, the DU 1310 may provide services corresponding to the slice to the terminal through the allocated resources.

[0164] Figure 13An example of operation 1305 is shown in which the RIC 1320 generates control information based on the reported information received through operation 1300 and sends the control information to the DU 1310, but embodiments of the present disclosure are not limited thereto. For example, the RIC 1320 may identify and only store the reported information received from operation 1300 and may not immediately generate control information based on the received reported information. In other words, operation 1305 may not have to be continuously performed after operation 1300. Alternatively, the RIC 1320 may send control information based on other information rather than the received reported information.

[0165] Figure 13 An example of the DU 1310 as an E2 node is shown. The DU 1310 sends or receives signals with a near RT RIC to explain the operations for controlling resource allocation. However, embodiments of the present disclosure are not limited thereto. For example, in addition to the DU 1310, the E2 node may further include a CU, a CU-CP, or a CU-UP.

[0166] Although not shown in Figure 13 According to another embodiment, the previous process of the E2 interface may be performed first. The DU 1310 may be connected to the RIC 1320. For example, the DU 1310 may send an E2 setup request (setup request) message to the RIC 1320. The E2 node function located in the DU 1310 may find the RIC using the IP address of the RIC 1320 set for operation - administration - maintenance (OAM) and send an E2 setup request message. The E2 setup request message may include information about the RAN functions supported by the DU 1310 (e.g., RAN function definition), E2 node ID information, etc. The RAN function definition value is a value set for OAM. For example, the RAN function definition value may include a STYLE ID value. The RIC 1320 may determine which call processing functions the DU 1310 supports based on the RAN function definition value by receiving information about the value set for OAM.

[0167] In response to the E2 setup request message, the RIC 1320 may receive an E2 setup response (E2 setup response) message from the DU 1310. The RIC 1320 may determine whether the E2 setup request message sent by the DU 1310 is acceptable. When the E2 setup request message is acceptable, the RIC 1320 may send the E2 setup response message to the DU 1310.

[0168] The RIC 1320 can send a subscription request (RIC subscription request) message to the E2 node. A specific xApp located in the RIC 1320 requests a subscription (or join) to a function defined by a specific RAN function supported by E2 from the RIC E2 termination function. According to an embodiment, the subscription request message and the E2 establishment response message can be sent separately. According to another embodiment, the subscription request message can be included in the E2 establishment response message and sent together.

[0169] The DU 1310 can send a subscription request response (RIC subscription response) to the RIC 1320. The E2 node function of the DU 1310 can decode the subscription request message. After the RIC 1320 successfully sets the event conditions requested from the E2 node function, the E2 node function of the DU 1310 can deliver, through the subscription response, that the event trigger conditions have been successfully set to the RIC 1320.

[0170] As described above, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can evaluate the application-level performance by sending information about the entire time interval of the measured data volume instead of the sum of the time intervals in which there is an actual data volume. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the performance in the case of providing actual services to the terminal by sending information over the entire time interval, even if a high data volume is allocated in a short time interval. In addition, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the average value of the user equipment throughput by sending the total number of terminals of the slice related to a specific cell. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the throughput of each terminal of each slice and provide a throughput guarantee service for each terminal.

[0171] Figure 14 An example of resource allocation showing the user equipment throughput based on slices is presented.

[0172] In Figure 14 In operation 1400, the DU 1410 can send report information to the RIC 1420. According to an embodiment, the report information can include information about the number of UEs connected to the cell provided to the DU 1410 and the number of DRBs corresponding to each UE. For example, the report information can include the following information.

[0173] [Table 4]

[0174]

[0175] According to an embodiment, the reporting information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices related to the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, the number of terminals, and the number of DRBs per terminal. For example, the amount of data transmitted may indicate the total amount of data during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving the terminals are measured. The entire time interval may include the time when data exists and the time when data does not exist. The number of terminals may indicate the total number of terminals related to the data amount of a slice of a specific cell. The number of DRBs per terminal may indicate the number of DRBs corresponding to the terminal. The reporting information may include an allocated PRB portion and PRB usage. The reporting information may be referred to as performance data (or performance measurement).

[0176] According to an embodiment, the DU 1410 may identify the information for throughput reporting. For example, the DU 1410 may identify (or collect) the information for throughput reporting for each slice related to a specific cell. For example, the DU 1410 may identify, for each slice, the total amount of data transmitted during a specific reporting period. The specific reporting period may be referred to as the collection duration. Additionally, the DU 1410 may identify the total number of terminals receiving service based on the amount of data transmitted per slice.

[0177] According to an embodiment, the DU 1410 may send the reporting information to the RIC 1420 via the E2 interface. For example, the reporting information may be included in an indication message. For example, the indication message may include a RIC indication message. For example, the RIC indication message may include a message container, and the message container may include the reporting information.

[0178] In operation 1405, the RIC 1420 may send control information to the DU 1410. For example, the RIC 1420 may send the control information to the DU 1410 via the E2 interface. According to an embodiment, the control information may include information about the maximum PRB portion for each slice related to a specific cell. For example, the control information may be included in a control message. For example, the control message may include a RIC control message.

[0179] According to an embodiment, the RIC 1420 may receive reporting information from the DU 1410 and identify the user equipment throughput of each slice associated with a specific cell based on the received reporting information. For example, the RIC 1420 may identify the average value of the user equipment throughput of each slice based on the reporting information. The average value of the user equipment throughput may be identified based on the sum of the amount of data transmitted during the collection duration, the length of the collection duration, the total number of terminals, and the number of DRBs of each terminal. For example, the RIC 1420 may identify the average value of the user equipment throughput and the average DRB throughput by the total number of terminals and the number of DRBs of each terminal. By considering the number of DRBs corresponding to each terminal, the RIC 1420 may more accurately identify the throughput of each terminal of the slice.

[0180] According to an embodiment, the RIC 1420 may identify whether the SLA of each slice is satisfied based on the identified average value of the user equipment throughput and the reference throughput. The reference throughput may be set to a predetermined value by the operator according to the SLA. The SLA may indicate a metric for indicating service characteristics.

[0181] According to an embodiment, when the average value of the user equipment throughput satisfies the SLA, the RIC 1420 may maintain the current resource allocation state of each slice. On the other hand, when the average value of the user equipment throughput does not satisfy the SLA, the RIC 1420 may identify the resource allocation size to change the resource allocation state of each slice so as to satisfy the SLA. For example, when the average value of the user equipment throughput of the first slice satisfies the first SLA associated with the first slice and the average value of the user equipment throughput of the second slice does not satisfy the second SLA associated with the second slice, the RIC 1420 may change the resource allocation state of the first slice and the resource allocation state of the second slice. For example, the RIC 1420 may change the resource allocation state of the first slice within a range where the changed average value of the user equipment throughput of the first slice satisfies the first SLA. In addition, the RIC 1420 may change the resource allocation state of the second slice such that the changed average value of the user equipment throughput of the second slice satisfies the second SLA. The resource information (or resource allocation size) for changing the resource allocation state may include the maximum portion of PRBs for each slice associated with a specific cell.

[0182] Although Figure 14 not shown, the DU 1410 may identify the resource size allocated to the terminal for each slice through the control information received in operation 1405 and allocate resources to the terminal for each slice based on the identified resource size. In addition, the DU 1410 may provide services corresponding to the slice to the terminal through the allocated resources.

[0183] Figure 14 An example of operation 1405 is shown in which the RIC 1420 generates control information based on the reported information received through operation 1400 and sends the control information to the DU 1410, but embodiments of the present disclosure are not limited thereto. For example, the RIC 1420 may identify and only store the reported information received from operation 1400, and may not immediately generate control information based on the received reported information. In other words, operation 1405 may not necessarily be continuously performed after operation 1400. Alternatively, the RIC 1420 may send control information based on other information rather than the received reported information.

[0184] Figure 14 An example of the DU 1410 as an E2 node is shown, and the DU 1410 sends or receives signals to / from the near RT RIC to explain the operation for controlling resource allocation. However, embodiments of the present disclosure are not limited thereto. For example, in addition to the DU 1410, the E2 node may further include a CU, a CU-CP, or a CU-UP.

[0185] Although not shown in Figure 14 According to another embodiment, the previous procedure of the E2 interface may be performed first. The DU 1410 may be connected to the RIC 1420. For example, the DU 1410 may send an E2 setup request (setup request) message to the RIC 1420. The E2 node function located in the DU 1410 may find the RIC using the IP address of the RIC 1420 set for operation - administration - maintenance (OAM) and send an E2 setup request message. The E2 setup request message may include information about the RAN functions supported by the DU 1410 (e.g., RAN function definition), E2 node ID information, etc. The RAN function definition value is a value set for OAM. For example, the RAN function definition value may include a style ID value. The RIC 1420 may determine which call processing functions the DU 1410 supports based on the RAN function definition value by receiving information about the value set for OAM.

[0186] In response to the E2 setup request message, the RIC 1420 may receive an E2 setup response (E2 setup response) message from the DU 1410. The RIC 1420 may determine whether the E2 setup request message sent by the DU 1410 is acceptable. When the E2 setup request message is acceptable, the RIC 1420 may send the E2 setup response message to the DU 1410.

[0187] The RIC 1420 can send a subscription request (RIC subscription request) message to the E2 node. A specific xApp located in the RIC 1420 requests a subscription (or join) to a function defined by a specific RAN function supported by E2 from the RIC E2 termination function. According to an embodiment, the subscription request message and the E2 establishment response message can be sent separately. According to another embodiment, the subscription request message can be included in the E2 establishment response message and sent together.

[0188] The DU 1410 can send a subscription request response (RIC subscription response) to the RIC 1420. The E2 node function of the DU 1410 can decode the subscription request message. After the RIC 1420 successfully sets the event conditions requested from the E2 node function, the E2 node function of the DU 1410 can deliver the successfully set event trigger conditions to the RIC 1420 through the subscription response.

[0189] As described above, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can evaluate the application-level performance by sending information about the entire time interval of the measured data volume instead of the sum of the time intervals in which there is an actual data volume. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the performance in the case of providing actual services to the terminal by sending information over the entire time interval, even if a high data volume is allocated in a short time interval. Additionally, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the average value of the user equipment throughput by sending the total number of terminals of the slice related to a specific cell. Therefore, the device and method for identifying the user equipment throughput of each slice according to the embodiments of the present disclosure can identify the throughput of each terminal of each slice and provide a throughput guarantee service for each terminal.

[0190] Figure 15a An example of the operation flow of a digital unit (DU) that performs resource allocation based on slice-based user equipment throughput is shown.

[0191] Figure 15a The operation shows the operation of a DU as an example of an E2 node, but the embodiments of the present disclosure are not limited thereto. For example, the E2 node can include a DU, a CU, a CU-CP, and a CU-UP.

[0192] In Figure 15aIn operation 1500, the DU can identify information about slices. For example, the DU can identify information about slices related to a specific cell. The information about slices can be referred to as information for throughput reporting. According to an embodiment, the DU can identify (or collect) information for throughput reporting for each slice related to a specific cell. For example, the DU can identify, for each slice, the sum of the amount of data transmitted during a specific reporting period. The specific reporting period can be referred to as the collection duration. Additionally, the DU 1110 can identify the total number of terminals receiving the service based on the amount of data transmitted per slice. Figure 15a An example of identifying information about each of at least one slice related to a cell is shown, but embodiments of the present disclosure are not limited thereto. For example, the DU can identify information about each of at least one slice related to each cell for a plurality of cells related to the DU.

[0193] In operation 1505, the DU can send the reporting information to the RIC. For example, the DU can send the reporting information including information about slices to the RIC through the E2 interface. The RIC can include a near RT RIC. The reporting information can be included in a message container. The message container can be included in a RIC indication message and sent from the DU to the RIC. Figure 15a An example of sending information about each of at least one slice related to a cell is shown, but embodiments of the present disclosure are not limited thereto. For example, for a plurality of cells related to the DU, the DU can send the identified reporting information about each of at least one slice related to each cell to the RIC for each slice.

[0194] According to an embodiment, the reported information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data sent, the collection duration, the number of terminals, and the number of DRBs. For example, the amount of data sent may indicate the sum of the data volume during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving the terminals are measured. The entire time interval may include the time when the data volume exists and the time when the data volume does not exist. The number of terminals may indicate the total number of terminals associated with the data volume of a slice of a specific cell. The number of DRBs may indicate the total number of DRBs associated with the data volume of a slice of a specific cell. In other words, the information for throughput reporting may include the total number of DRBs corresponding to the entire terminals associated with the data volume of a slice of a specific cell. The reported information may include the allocated PRB portion and PRB usage. The reported information may be referred to as performance data (or performance measurement).

[0195] According to an embodiment, the reported information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data sent, the collection duration, and the number of DRBs. For example, the amount of data sent may indicate the sum of the data volume during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving the terminals are measured. The entire time interval may include the time when the data volume exists and the time when the data volume does not exist. The number of DRBs may indicate the total number of DRBs associated with the data volume of a slice of a specific cell. In other words, the information for throughput reporting may include the total number of DRBs corresponding to the entire terminals associated with the data volume of a slice of a specific cell. The reported information may include the allocated PRB portion and PRB usage. The reported information may be referred to as performance data (or performance measurement).

[0196] According to an embodiment, the reported information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data sent, the collection duration, the number of terminals, and the number of DRBs. For example, the amount of data sent may indicate the sum of the data volume during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving terminals are measured. The entire time interval may include the time when the data volume exists and the time when the data volume does not exist. The number of terminals may indicate the total number of terminals associated with the data volume of a slice of a specific cell. The number of DRBs may indicate the total number of DRBs associated with the data volume of a slice of a specific cell. In other words, the information for throughput reporting may include the total number of DRBs corresponding to the entire terminals associated with the data volume of a slice of a specific cell. The reported information may include the allocated PRB portion and PRB usage. The reported information may be referred to as performance data (or performance measurement).

[0197] According to an embodiment, the reported information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indices of slices associated with the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data sent, the collection duration, the number of terminals, and the number of DRBs per terminal. For example, the amount of data sent may indicate the sum of the data volume during the collection duration. The collection duration may indicate the entire time interval (or reporting period) during which resources for serving terminals are measured. The entire time interval may include the time when the data volume exists and the time when the data volume does not exist. The number of terminals may indicate the total number of terminals associated with the data volume of a slice of a specific cell. The number of DRBs per terminal may indicate the number of DRBs corresponding to the terminal. The reported information may include the allocated PRB portion and PRB usage. The reported information may be referred to as performance data (or performance measurement).

[0198] In operation 1510, the DU can receive control information from the RIC. The control information can include information about the size of the resources allocated to a slice. For example, the DU can receive, via the E2 interface, information about the size of the resources allocated to a slice identified based on information about the slice. The control information can include information about the maximum portion of PRBs for each slice associated with a specific cell. For example, the control information can be included in a control message. For example, the control message can include an RIC control message.

[0199] Although Figure 15a not shown, the DU can identify, for each slice, the size of the resources allocated to a terminal based on the information about the size of the resources allocated to the slice received in operation 1510, and allocate resources to the terminal for each slice based on the identified resource size. Additionally, the DU can provide a service corresponding to the slice to the terminal via the allocated resources.

[0200] Figure 15b An example of the operation procedure of a near-RT RIC that transmits resource allocation information based on slice-based terminal throughput is shown.

[0201] Figure 15b The operation shows the near-RT RIC operation connected to a DU as an example of an E2 node, but embodiments of the present disclosure are not limited thereto. For example, the E2 node can include a DU, a CU, a CU-CP, and a CU-UP.

[0202] In operation 1550, the RIC can receive report information from the DU. The report information can include information about the slice. Information about the slice can be received via the E2 interface. The report information can be sent from the DU to the RIC via a message container included in an RIC indication message.

[0203] According to an embodiment, the report information can include information for cell resource control (CellResourceControlList). For example, the information for cell resource control can include a cell ID and a slice report list. The slice report list can include an index of the slice associated with the cell ID and information for throughput reporting. The information for throughput reporting can include the amount of data transmitted, the collection duration, and the number of terminals.

[0204] According to an embodiment, the report information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indexes of slices related to the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, and the number of DRBs.

[0205] According to an embodiment, the report information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indexes of slices related to the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, the number of terminals, and the number of DRBs.

[0206] According to an embodiment, the report information may include information for cell resource control (CellResourceControlList). For example, the information for cell resource control may include a cell ID and a slice report list. The slice report list may include indexes of slices related to the cell ID and information for throughput reporting (throughput-report). The information for throughput reporting may include the amount of data transmitted, the collection duration, the number of terminals, and the number of DRBs per terminal.

[0207] In operation 1555, the RIC may identify the terminal throughput of each slice related to a specific cell based on information about the received slices. For example, the RIC may identify the average user equipment throughput of each slice based on information about the slices. For example, the average user equipment throughput may be identified based on the sum of the amount of data transmitted during the collection duration, the length of the collection duration, and the total number of terminals. For example, the average user equipment throughput may be identified based on the sum of the amount of data transmitted during the collection duration, the length of the collection duration, and the total number of DRBs. For example, the average user equipment throughput may be identified based on the sum of the amount of data transmitted during the collection duration, the length of the collection duration, the total number of terminals, and the total number of DRBs. For example, the average user equipment throughput may be identified based on the sum of the amount of data transmitted during the collection duration, the length of the collection duration, the total number of terminals, and the number of DRBs per terminal.

[0208] In operation 1560, the RIC can identify whether the SLA for each slice is met based on the average of the identified user equipment throughput and the reference throughput. The reference throughput can be set by the operator to a predetermined value according to the SLA. The SLA can indicate a metric for indicating service characteristics.

[0209] According to an embodiment, in operation 1565, the RIC can identify the size of the resources allocated for each slice. For example, when the average of the user equipment throughput meets the SLA, the RIC can maintain the current resource allocation status for each slice. On the other hand, when the average of the user equipment throughput does not meet the SLA, the RIC can identify the resource allocation size to change the resource allocation status for each slice so as to meet the SLA. For example, when the average of the user equipment throughput of the first slice meets the first SLA related to the first slice, and the average of the user equipment throughput of the second slice does not meet the second SLA related to the second slice, the RIC can change the resource allocation status of the first slice and the resource allocation status of the second slice. For example, the RIC can change the resource allocation status of the first slice within the range where the changed average of the user equipment throughput of the first slice meets the first SLA. Additionally, the RIC can change the resource allocation status of the second slice such that the changed average of the user equipment throughput of the second slice meets the second SLA. The resource information (or resource allocation size) for changing the resource allocation status can include the maximum portion of PRBs for each slice related to a specific cell.

[0210] In operation 1570, the RIC can receive control information. For example, the control information can be included in a control message. For example, the control message can include an RIC control message. For example, the RIC can send the control information to the DU via the E2 interface. The control information can include the resource information for changing the resource allocation status. For example, the resource information for changing the resource allocation status can include the resource allocation size for changing the resource allocation status for each slice. According to an embodiment, the resource information (or resource allocation size) for changing the resource allocation status can include the maximum portion of PRBs for each slice related to a specific cell.

[0211] Figure 15b An example of operation 1570 is shown in which the RIC generates control information based on the report information received through operation 1550 and sends the control information to the DU, but embodiments of the present disclosure are not limited thereto. For example, the RIC can identify and only store the report information received from operation 1550, and may not immediately generate control information based on the received report information. In other words, operation 1570 does not have to be continuously executed after operation 1550. Alternatively, the RIC can send control information based on other information rather than the received report information.

[0212] In Figures 1 to 15b this, according to an embodiment of the present disclosure, the near RT RIC may receive information required for calculating the terminal throughput from the DU in order to provide a service with an ensured terminal throughput. For example, the DU may report the information to the near RT RIC via the E2 interface. This information may be used to identify the throughput at the application level. In other words, the near RT RIC may identify the performance of the service actually provided at the application level. Different from the case of reporting the throughput information measured for each terminal or each bearer, the device and method for identifying the terminal throughput of each slice according to an embodiment of the present disclosure may send report information for identifying the throughput of the terminals of each specific cell and the slice associated with the specific cell. In addition, the device and method for identifying the terminal throughput of each slice according to an embodiment of the present disclosure may include report information including information on the number of terminals (or the number of DRBs) providing services for each slice. The device and method for identifying the terminal throughput of each slice according to an embodiment of the present disclosure may identify the throughput at the terminal level through the report information including the number of terminals or the number of DRBs. In other words, by identifying the average user equipment throughput, the near RT RIC may identify the throughput of each terminal of each slice and more accurately identify the degree of service provision (or the performance at the application level) of each terminal. According to an embodiment of the present disclosure, a guaranteed service based on the throughput perceived by the user may be provided by identifying the throughput of each terminal of each slice and evaluating the degree of service provision.

[0213] The effects that can be obtained from the present disclosure are not limited to the effects described above, and those of ordinary skill in the art to which the present disclosure pertains will clearly understand any other effects not mentioned herein from the following description.

[0214] As described above, a method performed by a near RT RIC may include receiving an indication message including information about a slice associated with a cell from an E2 node. The method may include identifying the size of the resources allocated for the slice based on the information about the slice. The method may include sending a control message including information about the size of the resources to the E2 node. The information about the slice may include a collection duration, the total amount of data during the collection duration, and information about the terminals associated with the slice.

[0215] According to an embodiment, the indication message may include a cell identifier associated with the cell and index information associated with the slice. The information about the slice may correspond to the index information.

[0216] According to an embodiment, the information about the terminals associated with the slice may include at least one of the number of terminals served by the data volume through the slice or the number of DRBs used to serve the data volume through the slice.

[0217] According to an embodiment, the indication message may include a PRB (Physical Resource Block) allocation part and information on PRB usage.

[0218] According to an embodiment, the control message may include information on the maximum part of PRBs for a slice associated with a cell.

[0219] As described above, a near RT RIC may include a memory containing instructions. The near RT RIC may include a transceiver. The near RT RIC may include a processor. The instructions, when executed by the processor, may cause the near RT RIC to receive, via the transceiver, an indication message from an E2 node, the indication message including information on a slice associated with a cell. The instructions, when executed by the processor, may cause the near RT RIC to identify the size of resources allocated for the slice based on the information on the slice. The instructions, when executed by the processor, may cause the near RT RIC to send, via the transceiver, a control message to the E2 node, the control message including information on the size of the resources. The information on the slice may include a collection duration, the sum of data amounts during the collection duration, and information on terminals associated with the slice.

[0220] According to an embodiment, the indication message may include a cell identifier associated with the cell and index information associated with the slice. The information on the slice may correspond to the index information.

[0221] According to an embodiment, the information on terminals associated with the slice may include at least one of the number of terminals served by the data amount through the slice or the number of DRBs used to serve the data amount through the slice.

[0222] According to an embodiment, the indication message may include a PRB (Physical Resource Block) allocation part and information on PRB usage.

[0223] According to an embodiment, the control message may include information on the maximum part of PRBs for a slice associated with a cell.

[0224] As described above, a method performed by an E2 node may include identifying information on a slice associated with a cell. The method may include sending an indication message including the identified information on the slice to a near RT RIC. The method may include receiving, from the near RT RIC, a control message including information on the size of resources allocated for the slice. The information on the slice may include a collection duration, the sum of data amounts during the collection duration, and information on terminals associated with the slice.

[0225] According to an embodiment, the indication message may include a cell identifier associated with the cell and index information associated with the slice. The information on the slice may correspond to the index information.

[0226] According to an embodiment, information about a terminal associated with a slice may include at least one of the number of terminals served by the data volume through the slice or the number of DRBs used to serve the data volume through the slice.

[0227] According to an embodiment, the indication message may further include a PRB (Physical Resource Block) allocation section and information about PRB usage.

[0228] According to an embodiment, the control message may include information about the maximum PRB portion of a slice associated with a cell.

[0229] As described above, an E2 node may include a memory containing instructions. The E2 node may include a transceiver. The E2 node may include a processor. The instructions, when executed by the processor, cause the E2 node to identify information about a slice associated with a cell. The instructions, when executed by the processor, cause the E2 node to send, via the transceiver, an indication message including information about the identified slice to a near RT RIC. The instructions, when executed by the processor, cause the E2 node to receive, via the transceiver, control information including information about the size of resources allocated for the slice from the near RT RIC. Information about the slice may include a collection duration, the sum of the data volume during the collection duration, and information about a terminal associated with the slice.

[0230] According to an embodiment, the indication message may include a cell identifier associated with the cell and index information associated with the slice. The information about the slice may correspond to the index information.

[0231] According to an embodiment, information about a terminal associated with a slice may include at least one of the number of terminals served by the data volume through the slice or the number of DRBs used to serve the data volume through the slice.

[0232] According to an embodiment, the indication message may include a PRB (Physical Resource Block) allocation section and information about PRB usage.

[0233] According to an embodiment, the control message may include information about the maximum PRB portion of a slice associated with a cell.

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

[0235] When implemented as software, a computer-readable storage medium storing one or more programs (software modules) can be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in 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 the specification of the present disclosure.

[0236] Such programs (software modules, software) can be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, CD-ROMs (compact disc read-only memories), DVDs (digital versatile discs) or other forms of optical memory, magnetic tape cartridges. Alternatively, it can be stored in a memory configured with some or all of their combinations. In addition, each configured memory can include multiple ones.

[0237] In addition, the program can be stored in an attachable storage device that can be accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN) or a combination thereof. Such a storage device can be connected to the device implementing the embodiments of the present disclosure through an external port. Additionally, a separate storage device on the communication network can access the device implementing the embodiments of the present disclosure.

[0238] In the above-described specific embodiments of the present disclosure, the components included in the present disclosure are represented in the singular or plural. However, for ease of explanation, the singular or plural representation is appropriately selected for the presented situation, and the present disclosure is not limited to singular or plural components, and even if the components are represented in the plural, they can be configured in the singular, or even if represented in the singular, they can be configured in the plural.

[0239] In the detailed description of the present disclosure, specific embodiments have been described, but it goes without saying that various modifications are possible without departing from the scope of the present disclosure.

Claims

1. A method performed by a near-real-time (RT) radio access network intelligent controller (RIC), the method comprising: Receiving, from an E2 node, an indication message including information about a slice associated with a cell; Identifying, based on the information about the slice, the size of the resources allocated for the slice; And Sending, to the E2 node, a control message including information about the size of the resources, Wherein the information about the slice includes a collection duration, the sum of the data volume during the collection duration, and information about terminals associated with the slice.

2. The method according to claim 1, wherein The indication message further includes a cell identifier associated with the cell and index information associated with the slice, and Wherein the information about the slice corresponds to the index information.

3. The method according to claim 1, wherein The information about the terminals associated with the slice includes at least one of the following: the number of terminals served by the data volume through the slice, or the number of data radio bearers (DRBs) used to serve the data volume through the slice.

4. The method according to claim 1, wherein The indication message further includes a physical resource block (PRB) allocation section and information about PRB usage.

5. The method according to claim 1, wherein The control message further includes information about the maximum portion of the physical resource block (PRB) of the slice associated with the cell.

6. A near-real-time (RT) radio access network (RAN) intelligent controller (RIC) comprising: A memory including instructions; A transceiver; And A processor, Wherein the instructions, when executed by the processor, cause the near-RT RIC to: Receive, via the transceiver, from an E2 node, an indication message including information about a slice associated with a cell; Identify, based on the information about the slice, the size of the resources allocated for the slice; and Send, via the transceiver, to the E2 node, a control message including information about the size of the resources, Wherein the information about the slice includes a collection duration, the sum of the data volume during the collection duration, and information about terminals associated with the slice.

7. The near RT RIC according to claim 6, wherein, The indication message further includes a cell identifier associated with the cell and index information associated with the slice, and Wherein the information about the slice corresponds to the index information.

8. The near RT RIC according to claim 6, wherein, The information about the terminals associated with the slice includes at least one of the following: the number of terminals served by the data volume through the slice, or the number of data radio bearers used to serve the data volume through the slice.

9. The near RT RIC according to claim 6, wherein The indication message further includes a physical resource block (PRB) allocation section and information about PRB usage.

10. The near RT RIC according to claim 6, wherein, The control message includes information about the maximum portion of the physical resource block (PRB) of the slice associated with the cell.

11. A method performed by an E2 node, the method comprising: Identifying information about a slice associated with a cell; Sending, to a near-real-time (RT) radio access network intelligent controller (RIC), an indication message including the information about the slice; And Receiving, from the near-RT RIC, a control message including information about the size of the resources allocated for the slice, Among them, the information about the slice includes the collection duration, the sum of the data volume during the collection duration, and the information about the terminal associated with the slice.

12. The method according to claim 11, wherein, The indication message further includes a cell identifier associated with the cell and index information associated with the slice, and among them, the information about the slice corresponds to the index information.

13. The method according to claim 11, wherein, The information about the terminal associated with the slice includes at least one of the following: the number of terminals served by the data volume through the slice, or the number of data radio bearers (DRBs) used to serve the data volume through the slice.

14. The method according to claim 11, wherein The indication message further includes a physical resource block (PRB) allocation section and information about PRB usage.

15. The method according to claim 11, wherein, The control message further includes information about the maximum portion of the physical resource block (PRB) of the slice associated with the cell.

Images