Electronic device and method for transmitting information for energy saving

Abstract

A method performed by a device of a near real-time (near-RT) radio access network intelligent controller (RIC), according to one embodiment, comprises an operation of transmitting an RIC control message to an E2 node via an E2 interface. The RIC control message includes information on a 5G quality of service (QoS) identifier (5QI), information on a maximum bit rate for a non-guaranteed bit rate (non-GBR) flow, and information on an averaging window for calculating a non-GBR flow bit rate.

Description

Electronic device and method for transmitting information for energy conservation The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to an electronic device and method for transmitting information for energy conservation in a wireless communication system. To meet the growing demand for wireless data traffic following the commercialization of 4G (4th generation) communication systems, improved 5G (5th generation) communication systems, or pre-5G communication systems, are being developed and expanded. For this reason, 5G communication systems, or pre-5G communication systems, are also referred to as "Beyond 4G Network" communication systems or "Post-LTE" systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, advanced technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed and developed for 5G communication systems. Additionally, for network improvement, 5G communication systems are developing technologies such as advanced small cells, ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation. Additionally, advanced coding modulation (ACM) techniques such as Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and Sliding Window Superposition Coding (SWSC) are under development for 5G communication systems. Furthermore, advanced access technologies such as Filter Bank Multi-Carrier (FBMC), Non-Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA) are also being developed. To meet the growing demand for wireless data traffic, 5G communication systems, also known as new radio (NR), are being commercialized. 5G communication systems, like 4G communication systems, provide users with high data rates. Furthermore, 5G communication systems offer wireless communication services for a variety of purposes, including the Internet of Things (IoT) and services requiring high reliability for specific purposes. In a system that combines 4G and 5G systems, the Open Radio Access Network (O-RAN), established by operators and equipment providers, defines new network elements (NEs) and interface specifications based on the 3rd Generation Partnership Project (3GPP) standards and presents the O-RAN architecture. O-RAN is established by operators and equipment providers. The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above-described matters constitute prior art related to the present disclosure. According to one embodiment, a method performed by a device of a Near-RT (real-time) radio access network intelligent controller (RIC) may include transmitting an RIC control message to an E2 node through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating a Non-GBR flow bit rate. According to one embodiment, a method performed by a device of an E2 node may include receiving, through an E2 interface, an RIC control message from a Near-RT (real-time) RIC (radio access network intelligent controller). The RIC control message may include information about a 5G QoS (quality of service) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. According to one embodiment, a device of a Near-RT (real time) radio access network intelligence controller (RIC) may include a transceiver, a processor, and a memory including instructions. The instructions, when executed by the processor, may cause the device to transmit an RIC control message to an E2 node via an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an averaging window for calculating the Non-GBR flow bit rate. According to one embodiment, a device of an E2 node may include a transceiver, a processor, and a memory including instructions. The instructions, when executed by the processor, may cause the device to receive a radio access network intelligent controller (RIC) control message from a near-real-time (RT) RIC through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the non-GBR flow bit rate. According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of a device of a Near-RT (real time) radio access network intelligence controller (RIC) including a transceiver, cause an E2 node to transmit an RIC control message through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. Figure 1 shows an example of a core network of a 4G (4th generation) LTE (Long Term Evolution) communication system. Figure 2 shows an example of a core network of a 5G (5th generation) communication system. Figure 3 shows an example of an architecture for O-RAN. Figure 4a shows an example of a connection between an E2 node and a radio access network intelligence controller (RIC) in a 5G communication system. Figure 4b shows the protocol stack of the E2 application protocol message. Figure 5 shows the configuration of electronic devices in a wireless access network. Figure 6 illustrates the logical functions associated with E2 messages of an E2 node and RIC in a wireless access network. Figure 7 shows examples of functional separation between E2 nodes, or base stations, and RICs. Figure 8 shows an implementation example of the E2 node and RIC. Figure 9 shows examples of functional separation between the CU (central unit) and the RIC. Figure 10 illustrates an example of the operation of a non-RT RIC, a near-RT RIC, and an E2 node to perform energy saving. Figure 11 illustrates an example of the operation of near-RT RIC and E2 nodes to perform energy saving. Figure 12 illustrates an example of the operation of near-RT RIC and E2 nodes to perform energy saving. Figure 13 illustrates an example of the operation of near-RT RIC and E2 nodes to perform energy saving. Figures 14a and 14b illustrate examples of the operation of the E2 node according to the averaging window. Figure 15 is a flowchart regarding the operation of a near-RT RIC for performing energy saving. Figure 16 is a flowchart regarding the operation of the E2 node for performing energy saving. The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure. The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach. In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to data types (e.g., list, set, subset), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms referring to channels, terms referring to network entities, terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. In the following description, terms referring to configuration (e.g., setup, setting, arrangement, control), terms referring to signals (e.g., packet, message, signal, information, signaling), terms referring to resources (e.g., section, symbol, slot, subframe, radio frame, subcarrier, RE (resource element), RB (resource block), BWP (bandwidth part), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, message, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities (DU (distributed unit), RU (radio unit), CU (central unit), CU-CP (control plane), CU-UP (user Terms such as O-DU (O-RAN (open radio access network) DU), O-RU (O-RAN RU), O-CU (O-RAN CU), O-CU-UP (O-RAN CU-CP), O-CU-CP (O-RAN CU-CP)), which refer to components of the device, are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. In addition, terms such as '... part', '... device', '... object', '... body', etc. used below may mean at least one shape structure or may mean a unit that processes a function. In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}. Although the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), extensible radio access network (xRAN), open-radio access network (O-RAN), etc.), these are merely examples for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems. As 4th generation (4G) / 5th generation (5G) communication systems (e.g., new radio (NR)) become commercialized, differentiated service support for users in virtualized networks has become required. 3GPP is a joint research project among mobile communication-related organizations, and its goal is to create a globally applicable 3rd generation mobile communication system standard within the scope of the International Telecommunication Union (ITU)'s IMT-2000 project. Established in December 1998, 3GPP standards are based on the advanced GSM standards, and include radio, core network, and service architecture within the scope of standardization. Accordingly, the O-RAN (open radio access network) newly defines the RU (radio unit), DU (digital unit), CU (central unit)-CP (control plane), and CU-UP (user plane), which are the nodes that constitute the 3GPP NE (network entity) and base station, as O(O-RAN)-RU, O-DU, O-CU-CP, and O-CU-UP, respectively, and additionally standardizes the NRT (near-real-time) RIC (radio access network intelligent controller). The present disclosure is to support an operator specific service model in the E2 interface where the RIC requests a service from the O-DU, O-CU-CP, or O-CU-UP. Here, the O-RU, O-DU, O-CU-CP, and O-CU-UP can be understood as objects that constitute the RAN that can operate according to the O-RAN standard, and can be referred to as E2 nodes.The interface with objects that constitute the RAN, which can operate according to the O-RAN standard between RIC and E2 nodes, uses E2AP (application protocol). The RIC is a logical node that can collect information related to the RAN. For example, the information related to the RAN may include information related to the cell site where the terminal and the E2 node (e.g., O-DU, O-CU-CP, or O-CU-UP) transmit and receive. The RIC may be implemented in the form of a server centrally located in one physical location. For example, connections may be established via Ethernet between the O-DU and the RIC, between the O-CU-CP and the RIC, and between the O-CU-UP and the RIC. For this purpose, interface specifications 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 are required, and message specifications such as E2-DU, E2-CU-CP, and E2-CU-UP and definition of procedures between the O-DU, O-CU-CP, O-CU-UP, and the RIC are required. In particular, differentiated service support is required for users in a virtualized network. By concentrating call processing messages / functions generated in O-RAN into RIC, it is necessary to define the functions of E2-DU, E2-CU-CP, and E2-CU-UP messages to support services for wide cell coverage. The RIC can communicate with an E2 node (e.g., O-DU, O-CU-CP, and / or O-CU-UP) using the E2 interface. For example, the RIC can establish an event occurrence condition through a subscription procedure with the E2 node. The RIC can establish a call processing event by generating a subscription request message and transmitting the E2 subscription request message to the E2 node. After the call processing event is established, the E2 node can transmit a subscription response message to the RIC. The E2 node can establish services provided by the Near-RT RIC. For example, the E2 node can transmit an RIC indication message (e.g., report information) to the RIC according to the subscription procedure. For example, the RIC can provide control for the E2 node (e.g., O-DU, O-CU-CP, O-CU-UP) using an RIC control message. Figure 1 shows an example of a core network of a 4G (4th generation) LTE (Long Term Evolution) communication system. Referring to FIG. 1, an LTE communication system may include a base station (110), a terminal (120), an S-GW (serving gateway) (130), a P-GW (packet data network gateway) (140), an MME (mobility management entity) (150), an HSS (home subscriber server) (160), and a PCRF (policy and charging rule function) (170). 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 coverage defined as a certain geographical area based on the distance at which a signal can be transmitted. 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 be referred to as an 'access point (AP)', 'eNodeB (eNB)', 'wireless point', 'transmission / reception point (TRP)', RAN node, or other terms having equivalent technical meanings. The terminal (120) is a device used by a user and performs communication with the base station (110) via a wireless channel. In some cases, the terminal (120) may be operated without the user's involvement. That is, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. The terminal (120) may be referred to as a 'user equipment (UE)', a 'mobile station', a 'subscriber station', a 'customer-premises equipment (CPE)', a 'remote terminal', a 'wireless terminal', a 'user device', or other terms having an equivalent technical meaning. The S-GW (130) provides a data bearer and creates or controls the data bearer under 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) may serve as an anchor during handover between base stations of the terminal (120). The P-GW (140) may serve as a connection point with an external network (e.g., the Internet). In addition, the P-GW (140) assigns an IP (Internet Protocol) address to the terminal (120) and serves as an anchor for the S-GW (130). In addition, the P-GW (140) may apply a QoS (Quality of Service) policy of the terminal (120) and manage accounting data. The MME (150) manages the mobility of the terminal (120). In addition, the MME (150) can perform authentication, bearer management, etc. for the terminal (120). In other words, the MME (150) is responsible for mobility management and various control functions for the terminal. The MME (150) can be linked with an SGSN (serving GPRS support node). The HSS (160) stores key information and subscriber profile for authentication of the terminal (120). The key information and subscriber profile are transmitted from the HSS (160) to the MME (150) when the terminal (120) connects to the network. PCRF (170) defines rules for policies and charging. Stored information is transmitted from PCRF (180) to P-GW (140), and P-GW (140) can perform control (e.g., QoS management, charging, etc.) on terminal (120) based on the information provided from PCRF (180). Figure 2 shows an example of a core network of a 5G (5th generation) communication system. Referring to FIG. 2, the 5G communication system may include a terminal (201), a base station (203), an access and mobility management function (AMF) (211), a session management function (SMF) (221), and a user plane function (UPF) (231). For the terminal (201), the descriptions of the terminal (120) of FIG. 1 may be referenced. For the base station (203), the descriptions of the base station (110) may be referenced. The base station (203) may be connected to the AMF (211) via an N2 interface and to the UPF (231) via an N3 interface. The base station (203) may be referred to as an 'access point (AP)', 'radio access network (RAN) node', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission / reception point (TRP)', 'communication node', 'wireless communication device', 'wireless communication equipment', 'network node', 'network entity', or other terms having equivalent technical meanings, in addition to a base station. The AMF (211) may provide functions related to mobility management of the terminal (201), user registration, authentication, connection establishment, and / or release. SMF (221) manages the session and service quality (e.g., QoS (quality of service)) of the terminal (120) in the user plane, and can create and manage a PDU session tunnel using GPT tunneling between UPF (231) and the base station (203). UPF (231) performs the role of processing and routing user data packets, and can provide appropriate processing through classification and priority of traffic as needed.Additionally, UPF (231) is connected to a data network (260) and can transmit packets through the Internet. The area between the terminal (201) and the base station (203) may be referred to as an access network or RAN. The set of network entities connected to the base station (203) may be referred to as a 5G core network. The 5G core network may include various network functions (NFs) in addition to the AMF (211), SMF (221), and UPF (223). For example, a 5G core network may include a network slice selection function (NSSF) (241), a network exposure function (NEF) (242), a network repository function (NRF) (243), a policy control function (PCF) (244), a unified data management (UDM) (245), an application function (AF) (246), an authentication server function (AUSF) (247), and / or a service capability exposure function (SCP) (248). The NSSF (241) may provide network slice selection that matches a user (e.g., a terminal (201)). The NEF (242) may provide implementation of a service by allowing a service provider to access network resources and network functions. The NRF (243) may act as a database that can search and locate services and functions within the network. The PCF (244) may manage and control quality of service and policies in the network. The UDM (245) may manage and provide profile and subscription information of a user. AF (246) can manage network access and resource allocation for specific services or applications. AUSF (247) can manage user authentication information and perform authentication procedures. SCP (248) can expose network service functions to external applications and support service provision. A base station (e.g., base station (203)) may be implemented in a distributed deployment according to a central unit (CU) (or control unit) configured to perform functions of upper layers of an access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC)) and a distributed unit (DU) configured to perform functions of lower layers. For example, between a core (e.g., 5GC (5G core) or NGC (next generation core)) network and a radio network (RAN), the base station may be implemented in a structure in which the CU, DU (or CU, DU, RU) are deployed in that order. The interface between the CU and the DU may be referred to as an F1 interface. A CU may be connected to one or more DUs and may be responsible for functions of a higher layer than a DU. For example, the CU may be responsible for functions of the RRC (radio resource control) layer and the PDCP (packet data convergence protocol) layer, and the DU (or the DU and the RU) may be responsible for functions of lower layers. The DU may perform functions of the RLC (radio link control) layer, the MAC (media access control) layer, and the PHY (physical) layer. As a non-limiting example, if the DU is connected to the RU (radio unit), the DU may perform some functions of the physical layer (high PHY), and the RU may be responsible for the remaining functions of the PHY layer (low PHY). Carrier aggregation (CA) technology is a technology that combines multiple component carriers and allows a single terminal to transmit and receive signals simultaneously using these multiple component carriers, thereby increasing frequency usage efficiency from the perspective of a terminal or a base station. Specifically, according to CA technology, a terminal (e.g., terminal (120), terminal (201)) and a base station (e.g., base station (110), base station (203)) can transmit and receive signals using a wideband using multiple component carriers in uplink (UL) and downlink (DL), respectively, wherein each component carrier is located in a different frequency band. Hereinafter, uplink refers to a communication link through which a terminal transmits a signal to a base station, and downlink refers to a communication link through which a base station transmits a signal to a terminal. At this time, the number of uplink component carriers and downlink component carriers may be different. Dual connectivity or multi-connectivity is a technology that increases frequency usage efficiency from the perspective of a terminal or a base station by allowing a single terminal to be connected to multiple different base stations and simultaneously transmit and receive signals using carriers within each of the multiple base stations located in different frequency bands. The terminal can simultaneously transmit and receive traffic by being connected to a first base station (e.g., a base station that provides a service using LTE technology or 4th generation mobile communication technology) (e.g., base station (110)) and a second base station (e.g., a base station that provides a service using NR (new radio) technology or 5G (5th generation) mobile communication technology) (e.g., base station (203)). At this time, the frequency resources used by each base station may be located in different bands. For example, a method that operates based on the dual connectivity method of LTE and NR based on the LTE core network (e.g., evolved packet core (EPC)) may be referred to as 5G NSA (non-standalone). For example, in a 5G communication system, the method of operating through 5G technology (or LTE technology and 5G technology) based on the 5G core network may be referred to as 5G SA (standalone). Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning. In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal. Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them. Although FIGS. 1 and 2 illustrate 4G and / or 5G environments, this description does not limit the scope of the communication environments of the embodiments of the present disclosure. The technical principles of the embodiments of the present disclosure can also be applied to 6G and post-6G communication technologies and network environments. Figure 3 shows an example of an architecture for O-RAN. Referring to FIG. 3, the logical architecture of O-RAN may include a service management orchestration (SMO) (300), an O-eNB (305), an O-RU (310), an O-DU (320), an O-CU-CP (331), an O-CU-UP (332), a Near-RT RIC (340), and a Non-RT RIC (350). The SMO (300) may be responsible for RAN management among various management domains (e.g., RAN management, core management, transport management, E2E (end-to-end) slice management) in a service provider's network. For RAN management, the SMO (300) may provide RAN optimization using the FCAPS (fault, configuration, accounting, performance, security) interface and the Non-RT RIC (350). The O-eNB (305) may be a node providing an access network in an LTE communication system. For the O-eNB (305), reference may be made to the descriptions of the base station (110) of FIG. 1. The O-RU (310), O-DU (320), O-CU-CP (331), and O-CU-UP (332) may be network entities (or nodes) for providing an access network in an NR communication system. For the O-RU (310), O-DU (320), O-CU-CP (331), and O-CU-UP (332), reference may be made to the descriptions of the base station (203) of FIG. 2. The Near-RT RIC (340) is a logical node for customizing RAN functionality for new services or regional resource optimization. The Near-RT RIC (340) may provide functions such as network intelligence (e.g., policy enforcement, handover optimization), resource assurance (e.g., radio-link management, advanced self-organized network (SON)), and resource control (e.g., load balancing, slicing policy). The Near-RT RIC (340) may be connected to an O-eNB (305), an O-CU-CP (331), an O-CU-UP (332), and / or an O-DU (320). Near-RT RIC (340) can communicate with O-eNB (305), O-CU-CP (331), O-CU-UP (332), and / or O-DU (320). RIC (340) can be connected to each node via E2 interface. In addition, the interface between O-CU-CP (331) and O-DU (320) can be referred to as F1-c interface. The interface between O-CU-UP (332) and O-DU (320) can be referred to as F1-u interface. In the following description, DU and O-DU, CU-CP and O-CU-CP, CU-UP and O-CU-UP can be used interchangeably. The Non-RT RIC (350) is implemented within the SMO (300) and can communicate with the Near-RT RIC (340) via the A1 interface. Policy management services, enrichment information services, and ML (machine learning) model management services can be provided via the A1 interface. The Non-RT RIC (350) can drive content delivered via the A1 interface. O-Cloud (360) is a cloud computing platform consisting of a set of physical infrastructure nodes that meet O-RAN requirements to host relevant O-RAN functions (e.g., Near-RT RIC (340), O-CU-CP (331), O-CU-UP (332), and O-DU (320)), supporting software components (e.g., operating system, virtual machine monitor, container runtime, etc.), and / or appropriate management and orchestration functions. Although the O-CU-CP (331) and the O-CU-UP (332) are illustrated in FIG. 3 according to the separation of the control plane and the user plane, the embodiments of the present disclosure are not limited thereto. As a non-limiting example, the O-CU-CP (331) and the O-CU-UP (332) may be understood as one O-CU (330). In addition, although FIG. 3 exemplifies one Near-RT RIC (340), according to various embodiments, multiple Near-RT RICs may exist for the O-RAN architecture. The multiple Near-RT RICs may be implemented with multiple hardware located at the same physical location or may be implemented through virtualization using one hardware. Figure 4a shows an example of a connection between an E2 node and a radio access network intelligence controller (RIC) in a 5G communication system. Referring to FIG. 4A, the 5G communication system may provide arrangements of entities according to a non-standalone mode (e.g., non-stadalone (NSA)) or a standalone mode (e.g., standalone (SA)). Network entities constituting a base station (e.g., base station (110) and base station (203)) may be referred to as E2 nodes, and each network entity may have arrangements according to a non-standalone mode or a standalone mode. For example, in a non-standalone mode, dual connectivity using an eNB and an E2 node may be provided to a terminal. This dual connectivity using LTE and NR may be referred to as EN-DC (E-UTRA (evolved universal terrestrial radio access) - NR dual connectivity). The CU-CP, CU-UP, and DU for operating as gNB may be connected to a Near-RT RIC (e.g., Near-RT RIC (340)) within the O-RAN architecture, and may be referred to as O-CU-CP (331), O-CU-UP (332), and O-DU (320), respectively. For example, in standalone mode, E2 nodes may be independently connected to 5GC. The E2 nodes may be referred to as O-CU-CP (331), O-CU-UP (332), and / or O-DU (320) within the O-RAN architecture. The O-CU-CP (331) may be connected to an AMF (e.g., AMF (211)) within the 5GC via an N2 interface. The O-CU-UP (332) may be connected to a UPF (e.g., UPF (231)) within the 5GC via an N3 interface. Figure 4b shows the protocol stack of the E2 application protocol message. Referring to FIG. 4b, the control plane includes a transport network layer and a radio network layer. The transport network layer includes a physical layer (410), a data link layer (420), an Internet Protocol (IP) (430), and a stream control transmission protocol (SCTP) (440). The wireless network layer includes E2AP (450). E2AP (450) is used to transmit subscription messages, indication messages, control messages, service update messages, and service query messages, and is transmitted in the higher layer of SCTP (440) and IP (430). Fig. 5 illustrates a configuration of an electronic device in a wireless access network. The structure illustrated in Fig. 5 can be understood as a configuration of an electronic device having at least one function among the Near-RT RIC (340), non-RT RIC (350), O-CU-CP (331), O-CU-UP (332), O-DU (320), and / or O-eNB (305) illustrated through Fig. 3. Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software. Referring to FIG. 5, the electronic device may include a transceiver (510), a memory (520), and a processor (530). The transceiver (510) provides an interface for communicating with other electronic devices within a network. That is, the transceiver (510) converts a bit string transmitted from an electronic device to another electronic device into a physical signal, and converts a physical signal received from another electronic device into a bit string. That is, the transceiver (510) can transmit or receive signals. Accordingly, the transceiver (510) may be referred to as a modem, a communication unit, a transmit unit, a receive unit, or a transmit / receive unit. In this case, the transceiver (510) enables the electronic device to communicate with other electronic devices or systems via a backhaul connection (e.g., a wired backhaul or wireless backhaul) or via a network. The transceiver (510) may include one or more transceivers. The memory (520) stores data such as basic programs, application programs, and setting information for the operation of the electronic device. The memory (520) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Furthermore, the memory (520) provides stored data upon request from the processor (530). The memory (520) may be referred to as a storage unit. The processor (530) controls the overall operations of the electronic device. For example, the processor (530) transmits and receives signals via the transceiver (510). Additionally, the processor (530) writes and reads data to and from the memory (520). The processor (530) may be referred to as a control unit. To this end, the processor (530) may be composed of multiple processors or include at least one sub-processor. According to various embodiments, the processor (530) may control the electronic device to perform operations according to various embodiments described in the present disclosure. Figure 6 illustrates the logical functions associated with E2 messages of an E2 node and RIC in a wireless access network. Referring to FIG. 6, the RIC (640) and the E2 node (610) can transmit or receive E2 messages to each other. For example, the E2 node (610) can be an O-eNB (305), an O-CU-CP (331), an O-CU-UP (332), an O-DU (320), or a base station (e.g., a base station (101), a base station (203)). The communication interface of the E2 node (620) can be determined according to the type of the E2 node (610). For example, the E2 node (610) can communicate with another E2 node (616) through an E1 interface or an F1 interface. Alternatively, for example, the E2 node (610) can communicate with another E2 node (616) through an X2 interface or an XN interface. Or, for example, the E2 node (610) may communicate with the core network entity via an S1 interface or a next generation application protocol (NGAP) interface (e.g., an interface between a next generation (NG) base station (203) and an AMF (211)). The E2 node (610) may include an E2 node function (612). The E2 node function (612) is a function corresponding to a specific xApp (application S / W) (646) installed in the RIC (640). For example, in the case of a KPI monitor, the RIC (640) may have a KPI monitor collection S / W installed, and the E2 node (610) may include an E2 node function (612) that generates KPI parameters and then transmits an E2 message including the KPI parameters to an E2 termination (642) located in the RIC (640). The E2 node (610) may include an RRM (radio resource management) (614). The E2 node (610) may manage resources provided to a wireless network for a terminal. The E2 terminal (642) located in the RIC (640) is the terminal of the RIC (640) for the E2 message, and performs the function of interpreting the E2 message transmitted by the E2 node (610) and then transmitting it to the xApp (646). The database (644) located in the RIC (640) can be used for the E2 terminal (624) or the xApp (646). FIG. 7 illustrates examples of functional separation between an E2 node (e.g., O-eNB (305), O-CU-CP (331), O-CU-UP (332), O-DU (320), or a base station (e.g., base station (101), base station (203)) and a RIC. The RAN standard may provide functional separation between the E2 node and the RIC. For example, the E2 node may be a CU (e.g., CU (330), CU-CP (331), CU-UP (332)). The RIC may be a Near RT RIC (340). The Near RT RIC (340) may be connected to an SMO (300) (e.g., open network automation platform (ONAP) / management and orchestration (MANO) / network management system (NMS)) via an A1 interface. For example, the Near RT RIC (340) may be a non-RT RIC of the SMO (300). The RIC (350) can be connected to the E2 node and the E2 interface. Possible functional separation options may include functional separation (700) in which the entire radio resource management (RRM) is managed by the Near-RT RIC (340) and functional separation (750) in which the RRM is selectively managed by the Near-RT RIC (340). Figure 8 illustrates an implementation example of an E2 node and an RIC. In the scenario of the implementation example (800), the E2 node (e.g., O-eNB (305), O-DU (320), O-CU (330), O-CU-CP (331), O-CU-UP (332)) and the RIC (e.g., Near-RT RIC (340)) can be virtualized on a cloud platform (e.g., open chassis and blade-specific edge cloud) and configured on a device (e.g., server). This scenario can provide latency that is sufficiently low to meet the O-DU latency requirements. This scenario can support deployments in dense urban areas with ample fronthaul capacity that allows base band unit (BBU) functions to be pooled at a central location. Therefore, there may be no need to attempt to centralize the near-real time (RT) RIC beyond the limits of centralizing the O-DU functions. Figure 9 shows examples of functional separation between the CU (central unit) and the RIC. Referring to FIG. 9, functions for CU (910) (e.g., O-CU (330), O-CU-CP (331), O-CU-UP (332)) and RIC (920) (e.g., Near-RT RIC (340)) can be implemented separately or jointly. Depending on the arrangement of the functions, a deployment scenario can be determined. For example, the functions can be distributed according to deployment scenario #1 (900). They can be configured to replace only at least one intelligence-essential function (e.g., traffic steering, cell admission control (CAC) function). In deployment scenario #1 (900), the RIC (920) can be located in a separate site or exist only as another NE. For another example, the functions can be distributed according to deployment scenario #2 (950). In deployment scenario #2 (950), the RIC (920) can replace almost all functions of the CU (910) except for 3GPP I / F management (e.g., mobility function, session function, UE context function, cell context function). In deployment scenario #2 (950), the RIC (920) can be implemented as a device (e.g., server device) similar to the CU (910). For example, the RIC (920) can share all functions with the CU (910) within the same cloud. Although two scenarios are illustrated in FIG. 9, other scenarios may also be applicable. For example, in deployment scenario #1 (900), the mobility function may be performed by the RIC (920) rather than the CU (910). Also, for example, in deployment scenario #1 (900), the UE context function may be performed by the RIC (920) rather than the CU (910). Also, for example, in deployment scenario #1 (900), the session function may be performed by the RIC (920) rather than the CU (910). According to one embodiment, the near-RT RIC may instruct the E2 node to perform an operation for energy saving. For example, the near-RT RIC may determine information for performing energy saving in the E2 node (or at least one parameter for performing energy saving). The near-RT RIC may transmit information about a policy for performing energy saving to the E2 node. The near-RT RIC may receive a response message from the E2 node. Based on the response message, the near-RT RIC may transmit an RIC control message to the E2 node. The E2 node may perform energy saving based on the RIC control message. In the following description, examples of operations of the near-RT RIC and the E2 node for performing energy saving will be described. Figure 10 illustrates an example of the operation of a non-RT RIC, a near-RT RIC, and an E2 node to perform energy saving. Referring to FIG. 10, the network architecture (1000) may include a service management orchestrator (SMO) (1030), a near-RT RIC (1010), and / or an E2 node (1020). The SMO (1030) may be configured to manage network functions. According to one embodiment, the SMO (1030) may perform configuration, alarm, performance, and / or security management using the O1 interface. The O1 interface may include an interface between the SMO (1030) and a near-RT RIC (1010). The O1 interface may include an interface between the SMO (1030) and an E2 node (1020). For example, the SMO (1030) may include a non-RT RIC (1040). The non-RT RIC (1040) may manage deployment, configuration, and / or data regarding a RAN node (e.g., an O-CU-UP, an O-CU-CP, an O-DU, or an O-eNB) (or an E2 node (1020)). The non-RT RIC (1040) may handle services that have delay requirements exceeding a specified time (e.g., 1 second). The non-RT RIC (1040) may provide policy and / or enrichment information to the near-RT RIC (1010) using the A1 interface. The A1 interface may include an interface between the non-RT RIC (1040) and the near-RT RIC (1010). For example, a non-RT RIC (1040) may provide policy and / or enrichment information to a near-RT RIC (1010) via an A1 policy message. According to one embodiment, the near-RT RIC (1010) can process services with delay requirements of less than a specified time (e.g., 1 second). For example, the near-RT RIC (1010) can perform radio resource management, handover control, DC (dual connectivity) control, and load balancing. For example, the near-RT RIC (1010) can transmit messages for controlling and / or managing the E2 node (1020). The near-RT RIC (1010) can acquire (or collect) real-time information (e.g., information about the UE or information about the cell) using the E2 interface and provide services based on the acquired information. According to one embodiment, the E2 node (1020) may include an O-CU-UP, an O-CU-CP, an O-DU, and / or an O-eNB. For example, the E2 node (1020) may be connected to one near-RT RIC (1010). However, the near-RT RIC (1010) may be connected to one or more E2 nodes. According to one embodiment, an energy saving function may be provided through the network architecture (1000). For example, the energy saving function may be performed based on at least one of control for carrier and cell switches, RF channel reconfiguration, advanced sleep mode (ASM), and O-cloud resource energy saving mode. Hereinafter, for convenience of explanation, the energy saving function will be described through ASM, but is not limited thereto. For example, the ASM may be used to control an RU (or O-RU) connected to an E2 node (1020) to operate in one of a plurality of sleep modes. For example, a non-RT RIC (1040) and / or a near-RT RIC (1010) may select one of a plurality of sleep modes of an RU (or O-RU) connected to the E2 node (1020) and transmit information about the ASM to the E2 node (1020) to control the RU through the selected sleep mode. For example, the plurality of sleep modes may include a first mode to a third mode. The first mode may be configured to provide a symbol-level sleep state. The first mode may be referred to as a micro-sleep power state. The second mode may be configured to provide a sleep state between 6 [ms] (milliseconds) and 640 [ms]. The second mode may be referred to as a shallow sleep power state. The third mode can be set to provide a sleep state between 50 [ms] and 10 [s](second). In some embodiments, the non-RT RIC (1040) and / or the near-RT RIC (1010) may control (or limit) the functionality of the RU within the sleep mode. For example, the non-RT RIC (1040) and / or the near-RT RIC (1010) may disable one array carrier of the RU. For example, the non-RT RIC (1040) and / or the near-RT RIC (1010) may disable one of the tx array carrier or the rx array carrier of the RU. For example, the non-RT RIC (1040) and / or the near-RT RIC (1010) may disable both the tx array carrier and the rx array carrier of the RU. For example, the non-RT RIC (1040) of the SMO (1030) can transmit information about a policy for controlling the E2 node (1020) in the near-RT RIC (1010) to the near-RT RIC (1010) through an A1 policy message. The A1 policy message can include information about a policy for controlling the E2 node (1020) in the near-RT RIC (1010). For example, the A1 policy message can be referred to as a policy message. The near-RT RIC (1010) can identify (e.g., obtain, generate) information for controlling the E2 node (1020) based on the A1 policy message. The near-RT RIC (1010) can identify (e.g., obtain, generate) information for controlling the E2 node (1020) through the xApp (1011). For example, the xApp (1011) may correspond to the xApp (646) of FIG. 6. For example, the xApp (1011) may be configured to perform a function related to energy saving. The near-RT RIC (1010) can transmit information for controlling the E2 node (1020) to the E2 node (1020) through the E2 control message. The information for controlling the E2 node (1020) may include control information for energy saving. For example, an E2 control message may be referred to as a control message or a RIC control message. For example, a non-RT RIC (1040) of an SMO (1030) can provide a policy on energy saving to a near-RT RIC (1010) using an A1 policy message. The A1 policy message may include at least one of information about a 5G QoS identifier (5QI), information about a maximum flow bit rate for a non-GBR flow, and / or information about an average window. The near-RT RIC (1010) may provide control information for energy saving to the E2 node (1020) using an E2 control message. For example, the E2 control message may include information for initiating activation or deactivation of energy saving and / or information about an energy saving policy. The information about the energy saving policy may include at least one of information about a 5G QoS identifier (5QI), information about a maximum flow bit rate for a non-GBR flow, and / or information about an average window. The E2 node (1020) can perform an energy-saving operation using the scheduler (1021) based on the E2 control message. The E2 node (1020) can perform an energy-saving operation by controlling the sleep state of the RU connected to the E2 node (1020). The E2 node (1020) may transmit status information regarding energy saving to the near-RT RIC (1010). The status information regarding energy saving may include information indicating whether an energy saving function is performed for a cell, information indicating a status regarding energy saving, and / or information regarding an energy saving policy. For example, the information regarding the energy saving policy may include at least one of information regarding a 5G QoS identifier (5QI), information regarding a maximum flow bit rate for a non-GBR flow, and / or information regarding an average window. For example, control information for energy saving may include control information for energy saving according to a service corresponding to 5QI. For example, according to a service corresponding to 5QI, at least one of information regarding a maximum flow bit rate for a non-GBR flow and / or an average window may be set differently. For example, a service corresponding to 5QI may include a service for file transfer, voice over internet protocol (VoIP), live streaming, transmission and reception of vehicle-to-everything (V2X) messages, and / or augmented reality. In the following specification, specific operations of the near-RT RIC (1010) and / or E2 node (1020) for performing energy saving will be described. Figure 11 illustrates an example of the operation of near-RT RIC and E2 nodes to perform energy saving. Referring to FIG. 11, in operation 1110, a near-RT RIC (1010) may transmit control information for energy saving to an E2 node (1020). For example, the control information for energy saving may include information for initiating activation or deactivation of energy saving and / or information regarding an energy saving policy. The information regarding the energy saving policy may include at least one of information regarding a 5G QoS identifier (5QI), information regarding a maximum flow bit rate for a non-GBR flow, and / or information regarding an average window. For example, the control information regarding energy saving may be configured as shown in the table below. Referring to Table 1, control information for energy saving may include 'energySavingControl' and / or 'asmPolicyList'. 'energySavingControl' may be an example of information for initiating activation or deactivation of energy saving. 'asmPolicyList' may be an example of information regarding energy saving policies. 'asmPolicyList' may represent a list of policies regarding ASM. For example, [6] may refer to the 3GPP TS 28.541 standard. For example, 'asmPolicyList' may contain information according to the table below. Referring to Table 2, 'asmPolicyList' can contain 'asmPolicy'. 'asmPolicy' can contain information according to the table below. Referring to Table 3, 'asmPolicy' (or 'asmPolicyList') can include 'sleepModeConfiguration' and / or 'asmObjective'. 'sleepModeConfiguration' is information for guiding the O-DU to enter a specific sleep mode within a specified time. Based on 'sleepModeConfiguration', the O-DU can perform energy saving by disabling at least one of the array carrier of the O-RU, the tx array carrier of the O-RU, the rx array carrier of the O-RU, or the O-RU. 'asmObjective' is configuration information regarding the ASM performance objective. For example, 'asmObjective' may contain information according to the table below. Referring to Table 4, 'asmObjective' can include 'dataDirection', 'perfObjectiveList', 'perfObjective', and / or 'esObjective'. 'dataDirection' is information indicating the direction in which data is transmitted. 'dataDirection' can indicate either downlink (DL) or uplink (UL). 'perfObjectiveList' is information indicating a list of 'perfObjective'. 'perfObjective' is information indicating the expected performance target to be achieved for 5QI. 'perfObjective' can indicate the expected performance degradation due to energy saving. 'esObjective' is information indicating the expected energy saving target of the cell. For example, 'esObjective' may contain information according to the table below. Referring to Table 5, 'esObjective' may include '5qi', 'mNgbrFbr', and / or 'Averaging Window'. '5qi' may be an example of information regarding 5QI (5G QoS identifier). '5qi' may represent a 5QI value. For example, '5qi' may be configured based on the 3GPP TS 23.501 specification. For QoS characteristics associated with '5qi', the table below may be referred to. 5QIValueResource TypeDefault Priority LevelPacket Delay Budget(NOTE 3)Packet ErrorRateDefault Maximum Data Burst Volume(NOTE 2)DefaultAveraging WindowExample Services1GBR(NOTE 1)20100 ms(NOTE 11,NOTE 13)10 -2 N / A2000 msConversational Voice240150 ms(NOTE 11,NOTE 13)10 -3 N / A2000 msConversational Video (Live Streaming)33050 ms(NOTE 11,NOTE 13)10 -3 N / A2000 msReal Time Gaming, V2X messages (see TS 23.287

[0121] ).Electricity distribution - medium voltage, Process automation monitoring450300 ms(NOTE 11,NOTE 13)10 -6 N / A2000 msNon-Conversational Video (Buffered Streaming)65(NOTE 9,NOTE 12)775 ms(NOTE 7, NOTE 8)10 -2N / A2000 msMission Critical user plane Push To Talk voice (e.g. MCPTT)66(NOTE 12)20100 ms(NOTE 10,NOTE 13)10 -2 N / A2000 msNon-Mission-Critical user plane Push To Talk voice67(NOTE 12)15100 ms(NOTE 10,NOTE 13)10 -3 N / A2000 msMission Critical Video user plane75(NOTE 14)7156150 ms (NOTE 11, NOTE 13, NOTE 15)10 -6 N / A2000 ms"Live" Uplink Streaming (e.g. TS 26.238

[0076] )7256300 ms (NOTE 11, NOTE 13, NOTE 15)10 -4 N / A2000 ms"Live" Uplink Streaming (e.g. TS 26.238

[0076] )7356300 ms (NOTE 11, NOTE 13, NOTE 15)10 -8 N / A2000 ms"Live" Uplink Streaming (e.g. TS 26.238

[0076] )7456500 ms (NOTE 11, NOTE 15)10 -8 N / A2000 ms"Live" Uplink Streaming (e.g. TS 26.238

[0076] )7656500 ms (NOTE 11, NOTE 13, NOTE 15)10 -4 N / A2000 ms"Live" Uplink Streaming (e.g. TS 26.238

[0076] )5Non-GBR(NOTE 1)10100 msNOTE 10,NOTE 13)10 -6 N / AN / AIMS Signalling660300 ms(NOTE 10,NOTE 13)10 -6N / AN / AVideo (Buffered Streaming)TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.)770100 ms(NOTE 10,NOTE 13)10 -3 N / AN / AVoice,Video (Live Streaming)Interactive Gaming880300 ms(NOTE 13)10 -6 N / AN / AVideo (Buffered Streaming)TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressivevideo,etc.)99069(NOTE 9, NOTE 12)560 ms(NOTE 7, NOTE 8)10 -6 N / AN / AMission Critical delay sensitive signalling (e.g. MC-PTT signalling)70(NOTE 12)55200 ms(NOTE 7,NOTE 10)10 -6 N / AN / AMission Critical Data (e.g. example services are the same as 5QI 6 / 8 / 9)796550 ms(NOTE 10,NOTE 13)10 -2 N / AN / AV2X messages (see TS 23.287

[0121] )806810 ms(NOTE 5,NOTE 10)10 -6 N / AN / ALow Latency eMBB applications Augmented Reality82Delay-critical GBR1910 ms(NOTE 4)10 -4 255 bytes2000 msDiscrete Automation (see TS 22.261 [2])832210 ms(NOTE 4)10 -41354 bytes(NOTE 3)2000 msDiscrete Automation (see TS 22.261 [2]);V2X messages (UE - RSU Platooning, Advanced Driving: Cooperative Lane Change with low LoA. See TS 22.186

[0111] , TS 23.287

[0121] )842430 ms(NOTE 6)10 -5 1354 bytes(NOTE 3)2000 msIntelligent transport systems (see TS 22.261 [2])85215 ms(NOTE 5)10 -5 255 bytes2000 msElectricity Distribution- high voltage (see TS 22.261 [2]).V2X messages (Remote Driving. See TS 22.186

[0111] , NOTE 16, see TS 23.287

[0121] )86185 ms(NOTE 5)10 -41354 bytes2000 msV2X messages (Advanced Driving: Collision Avoidance, Platooning with high LoA. See TS 22.186

[0111] , TS 23.287

[0121] )NOTE 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER.NOTE 2: It is required that default MDBV is supported by a PLMN supporting the related 5QIs.NOTE 3: The Maximum Transfer Unit (MTU) size considerations in clause 9.3 and Annex C of TS 23.060

[0056] are also applicable. IP fragmentation may have impacts to CN PDB, and details are provided in clause 5.6.10.NOTE 4: A static value for the CN PDB of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4.NOTE 5: A static value for the CN PDB of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4.NOTE 6: A static value for the CN PDB of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4.NOTE 7: For Mission Critical services, it may be assumed that the UPF terminating N6 is located "close" to the 5G_AN (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation. Hence a static value for the CN PDBof 10 ms for the delay between a UPF terminating N6 and a 5G_AN should be subtracted from this PDB to derive the packet delay budget that applies to the radio interface.NOTE 8: In both RRC Idle and RRC Connected mode, the PDB requirement for these 5QIs can be relaxed (but not to a value greater than 320 ms) for the first packet(s) in a downlink data or signalling burst in order to permit reasonable battery saving (DRX) techniques.NOTE 9: It is expected that 5QI-65 and 5QI-69 are used together to provide Mission Critical Push to Talk service (e.g. 5QI-5 is not used for signalling). It is expected that the amount of traffic per UE will be similar or less compared to the IMS signalling.NOTE 10: In both RRC Idle and RRC Connected mode, the PDB requirement for these 5QIs can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques.NOTE 11: In RRC Idle mode, the PDB requirement for these 5QIs can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques.NOTE 12: This 5QI value can only be assigned upon request from the network side. The UE and any application running on the UE is not allowed to request this 5QI value.NOTE 13: A static value for the CN PDB of 20 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.NOTE 14: This 5QI is not supported in this Release of the specification as it is only used for transmission of V2X messages over MBMS bearers as defined in TS 23.285

[0072] but the value is reserved for future use.NOTE 15: For "live" uplink streaming (see TS 26.238

[0076] ), guidelines for PDB values of the different 5QIs correspond to the latency configurations defined in TR 26.939

[0077] . In order to support higher latency reliable streaming services (above 500ms PDB), if different PDB and PER combinations are needed these configurations will have to use non-standardised 5QIs.NOTE 16: These services are expected to need much larger MDBV values to be signaled to the RAN. Support for such larger MDBV values with low latency and high reliability is likely to require a suitable RAN configuration, for which, the simulation scenarios in TR 38.824

[0112] may contain some guidance. Referring back to Table 5, 'mNgbrFbr' may be an example of information regarding the maximum flow bit rate for a non-GBR flow. 'Averaging Window' may be an example of information regarding an averaging window. 'Averaging Window' may indicate an averaging window for calculating the maximum flow bit rate. 'Averaging Window' may indicate a time interval for calculating the maximum flow bit rate. The default value of 'Averaging Window' may be set to 2000 [ms]. For example, a GBR (or non-GBR) QoS flow may be associated with an averaging window (or 'Averaging Window'). The averaging window may indicate a period of time over which a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR) is calculated. For example, if information about the averaging window is not transmitted to the E2 node (1020), the E2 node (1020) may calculate the GFBR and / or MFBR at the E2 node (1020) using a pre-configured value. For example, if information about the averaging window is transmitted to the E2 node (1020), the E2 node (1020) may calculate the GFBR and / or MFBR based on the received information about the averaging window. According to one embodiment, control information for energy saving may be transmitted via an RIC control message (or control message). As a non-limiting example, the RIC control message may be established by an RIC subscription procedure between a Near-RT RIC (1010) and an E2 node (1020). For example, the Near-RT RIC (1010) may transmit an RIC subscription request message for an RIC control message to the E2 node (1020). The E2 node (1020) may transmit an RIC subscription response message in response to the RIC subscription request message. Thereafter, the Near-RT RIC (1010) may transmit an RIC control message including the control information for energy saving to the E2 node (1020). However, the present invention is not limited thereto. According to an embodiment, the control information for energy saving may also be included in the RIC subscription request message. Depending on the embodiment, control information for energy saving may be included in an RIC instruction message. A specific example of transmitting control information for energy saving via an RIC control message will be described later in FIG. 13. Figure 12 illustrates an example of the operation of near-RT RIC and E2 nodes to perform energy saving. Referring to FIG. 12, at operation 1250, the E2 node (1020) can transmit status information regarding energy saving to the near-RT RIC (1010). The near-RT RIC (1010) can receive status information regarding energy saving from the E2 node (1020). For example, status information regarding energy saving may include information regarding whether an energy saving function for a cell is activated, information regarding specific energy saving statuses, and / or information regarding energy saving policies. For example, status information regarding energy saving may be structured as shown in the table below. Referring to Table 7, state information related to energy saving may include 'cesSwitch', 'energySavingState', and / or 'asmPolicyList'. 'cesSwitch' may be an example of information regarding whether the energy saving function for the cell is activated. 'cesSwitch' may indicate whether the energy saving function for the cell is activated. 'energySavingState' may be an example of information regarding a specific state related to energy saving. 'energySavingState' may indicate the energy saving state according to the value of 'energySavingControl' in Table 1. For example, if the value of 'energySavingControl' is 'toBeEnergySaving', 'energySavingState' may represent a state that attempts to achieve "isEnergySaving". If the value of 'energySavingControl' is 'toBeNotEnergySaving', 'energySavingState' may represent a state that attempts to achieve "isNotEnergySaving". 'asmPolicyList' may correspond to 'asmPolicyList' in Table 1. According to one embodiment, control information for energy saving may be transmitted via an RIC indication message (or indication messages). The RIC indication message may be used for reporting. As a non-limiting example, the RIC indication message may be established by an RIC subscription procedure between a Near-RT RIC (1010) and an E2 node (1020). For example, the Near-RT RIC (1010) may transmit an RIC subscription request message to the E2 node (1020) for transmitting the RIC indication message to the E2 node (1020). The E2 node (1020) may transmit an RIC subscription response message in response to the RIC subscription request message. Thereafter, the E2 node (1020) may transmit an RIC indication message including the control information for energy saving to the Near-RT RIC (1010). Figure 13 illustrates an example of the operation of a near-RT RIC and E2 node for energy saving. In the following embodiments, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. Referring to FIG. 13, in operations 1310 and 1320, the near-RT RIC (1010) and the E2 node (1020) may perform an RIC subscription procedure. The near-RT RIC (1010) may perform the RIC subscription procedure to receive an RIC indication message according to operation 1330 from the E2 node (1020). For example, in operation 1310, a near-RT RIC (1010) may transmit an RIC join request message to an E2 node (1020). The RIC join request message may be related to a RAN function. The RAN function may be related to E2 service model-key performance measurement (E2SM-KPM) for energy saving. For example, the RIC join request message may be transmitted to request measurement information regarding the E2 node (1020) (or measurement information regarding the RAN function). At operation 1320, the E2 node (1020) may transmit an RIC Join Response message to the near-RT RIC (1010). For example, the E2 node (1020) may transmit an RIC Join Response message to the near-RT RIC (1010) in response to the RIC Join Request message. At operation 1330, the E2 node (1020) may transmit an RIC indication message to the near-RT RIC (1010) based on the RIC subscription procedure according to operations 1310 and 1320. For example, the RIC indication message may be configured based on one of a plurality of RIC style types according to the table below. According to one embodiment, the RIC indication message may be constructed based on one of a plurality of formats. For example, the RIC indication message may be constructed based on one of three formats. For RIC style type 1, the RIC indication message may be constructed based on a first format. For RIC style type 2, the RIC indication message may be constructed based on a first format. For RIC style type 3, the RIC indication message may be constructed based on a second format. For RIC style type 4, the RIC indication message may be constructed based on a third format. For RIC style type 5, the RIC indication message may be constructed based on a third format. According to one embodiment, the RIC indication message may include measurement information about the E2 node (1020) (or measurement information about RAN functions). For example, the E2 node (1020) may transmit measurement information about the E2 node (1020) to the near-RT RIC (1010) via the RIC indication message based on the RIC subscription request message. For example, measurement information about the E2 node (1020) may include information about throughput, delay, data size, session activity time, packet data convergence protocol (PDCP) drop rate, IP latency, QoS flow, CQI, and / or modulation coding scheme (MCS). At operation 1340, the near-RT RIC (1010) (or xApp (1011)) may determine (or identify) control information for energy saving. For example, the near-RT RIC (1010) may determine (or identify) control information for energy saving based on measurement information about the E2 node (1020) (or measurement information about the RAN). According to an embodiment, a near-RT RIC (1010) can transmit measurement information about an E2 node (1020) to a non-RT RIC (1040). The non-RT RIC (1040) can determine control information for energy saving based on the measurement information about the E2 node (1020). The non-RT RIC (1040) can transmit control information for energy saving to the near-RT RIC (1010). The near-RT RIC (1010) can identify control information for energy saving by receiving the control information for energy saving from the non-RT RIC (1040). According to one embodiment, the control information for energy saving may correspond to the control information for energy saving according to operation 1110 of FIG. 11. The control information for energy saving may include information according to Tables 1 to 5 described above. For example, the control information for energy saving may include at least one of information regarding a 5G QoS identifier (5QI), information regarding a maximum flow bit rate for a non-GBR flow, and / or information regarding an average window. In operations 1350 and 1360, the near-RT RIC (1010) and the E2 node (1020) may perform an RIC join procedure. The near-RT RIC (1010) may perform the RIC join procedure to transmit an RIC control message according to operation 1370 to the E2 node (1020). For example, in operation 1350, a near-RT RIC (1010) may transmit an RIC join request message to an E2 node (1020). The RIC join request message may be related to a RAN function. The RAN function may be related to E2 service model-cell configuration and control (E2SM-CCC) for energy saving. For example, the RIC join request message may be transmitted to the E2 node (1020) to transmit control information for energy saving. At operation 1360, the E2 node (1020) may transmit an RIC Join Response message to the near-RT RIC (1010). For example, the E2 node (1020) may transmit an RIC Join Response message to the near-RT RIC (1010) in response to the RIC Join Request message. At operation 1370, the near-RT RIC (1010) may transmit an RIC control message to the E2 node (1020) based on the RIC subscription procedure according to operations 1350 and 1360. For example, the RIC control message may be configured based on one of a plurality of RIC style types according to the table below. According to one embodiment, the RIC control message may be constructed based on one of a plurality of formats. For example, the RIC control message may be constructed based on one of two formats. For RIC style type 1, the RIC control message may be constructed based on a first format. For RIC style type 2, the RIC control message may be constructed based on a second format. According to one embodiment, the RIC control message may include control information for energy saving. The operation of the near-RT RIC (1010) transmitting the RIC control message to the E2 node (1020) may correspond to operation 1110 of FIG. 11. Although not shown, the E2 node (1020) may send a RIC instruction message to the near-RT RIC (1010). For example, the RIC control message may be configured based on one of the multiple RIC style types according to the table below. According to one embodiment, the RIC indication message may include status information regarding energy saving. The status information regarding energy saving may include information regarding whether an energy saving function for a cell is activated, information regarding a specific status related to energy saving, and / or information regarding an energy saving policy. The status information regarding energy saving may include information according to Table 7. The operation of the E2 node (1020) transmitting the RIC indication message to the near-RT RIC (1010) may correspond to operation 1250 of FIG. 12 . According to an embodiment, an RIC subscription procedure may be performed to report the RIC indication message. The RIC subscription procedure for reporting the RIC indication message may be distinguished from the RIC subscription procedure according to operations 1350 and 1360. The near-RT RIC (1010) and the E2 node (1020) may perform the RIC subscription procedure after performing operation 1370. The near-RT RIC (1010) may receive the RIC indication message from the E2 node (1020) based on the RIC subscription procedure. However, the present invention is not limited thereto. For example, the RIC indication message may be transmitted from the E2 node (1020) based on the RIC subscription procedure according to operations 1350 and 1360. According to an embodiment, the RIC control message may be configured based on one of a plurality of RIC style types according to Table 8 described above. Figures 14a and 14b illustrate examples of the operation of the E2 node according to the averaging window. Referring to FIGS. 14A and 14B, FIG. 14A illustrates an example of the operation of the E2 node (1020) when the averaging window is not set. FIG. 14B illustrates an example of the operation of the E2 node (1020) when the size of the averaging window is set by the near-RT RIC (1010). Referring to FIG. 14A, the E2 node (1020) can transmit data of 2 [mbit] (megabit) size to the terminal. The scheduler (1021) of the E2 node (1020) can identify that the maximum flow bit rate for the non-GBR flow is 1 mbit / sec. Based on the maximum flow bit rate for the non-GBR flow, the scheduler (1021) of the E2 node (1020) can transmit data of 2 [mbit] to the terminal. Each of the time intervals (1410) and (1420) may represent a time interval for transmitting data. The E2 node (1020) may transmit data to the terminal within the time interval (1410) or the time interval (1420). For example, each of the time intervals (1410) and (1420) may be set to 1 second. For example, if the maximum flow bit rate for a Non-GBR flow is 1 mbits / sec, the E2 node (1020) can transmit 1 [mbit] of data to the terminal within a time interval (1410), and can transmit 1 [mbit] of data to the terminal within a time interval (1420). Within the time interval (1410), 1 [mbit] of data may be transmitted within the time interval (1410-1). Since 1 [mbit] of data is transmitted within the time interval (1410-1), the E2 node (1020) may not transmit data to the terminal within the time interval (1410-2) within the time interval (1410). When the ASM function is applied, the O-RU (or RU) connected to the E2 node (1020) may be set to operate in the sleep mode during the time interval (1410-2) (or at least a part of the time interval (1410-2)). The near-RT RIC (1010) may control the O-RU to operate in the sleep mode within the time interval (1410-2) based on controlling the E2 node (1020). For example, the near-RT RIC (1010) may disable at least one of the array carrier of the O-RU, the tx array carrier of the O-RU, the rx array carrier of the O-RU, or the O-RU while the O-RU is in sleep mode. Within the time interval (1420), 1 [mbit] of data may be transmitted within the time interval (1420-1). Since 1 [mbit] of data is transmitted within the time interval (1420-1), the E2 node (1020) may not transmit data to the terminal within the time interval (1420-2) within the time interval (1420). When the ASM function is applied, the O-RU (or RU) connected to the E2 node (1020) may be set to operate in the sleep mode during the time interval (1420-2) (or at least a part of the time interval (1420-2)). The near-RT RIC (1010) may control the O-RU to operate in the sleep mode within the time interval (1420-2) based on controlling the E2 node (1020). For example, the near-RT RIC (1010) may disable at least one of the array carrier of the O-RU, the tx array carrier of the O-RU, the rx array carrier of the O-RU, or the O-RU while the O-RU is in sleep mode. Referring to FIG. 14b, the near-RT RIC (1010) can transmit control information for energy saving to the E2 node (1020). For example, the near-RT RIC (1010) can transmit information about 5QI (5G QoS identifier) (e.g., '5qi' in Table 5), information about maximum flow bit rate for non-GBR flow (e.g., 'mNgbrFbr' in Table 5), and information about average window (e.g., 'Averaging Window' in Table 5) to the E2 node (1020). For example, the near-RT RIC (1010) can determine the maximum flow bit rate for a service corresponding to 5QI (or a non-GBR flow). The near-RT RIC (1010) can determine an averaging window for calculating the non-GBR flow bit rate. The near-RT RIC (1010) can control an energy saving operation of the E2 node (1020) by transmitting information about 5QI (5G QoS identifier) (e.g., '5qi' in Table 5), information about the maximum flow bit rate for non-GBR flow (e.g., 'mNgbrFbr' in Table 5), and information about the average window (e.g., 'Averaging Window' in Table 5) to the E2 node (1020). The scheduler (1021) of the E2 node (1020) can perform an operation related to energy saving based on control information for energy saving. For example, the E2 node (1020) can transmit data of size 2 [mbit] (megabit) to the terminal. The scheduler (1021) of the E2 node (1020) can identify that the maximum flow bit rate for a service corresponding to 5QI (or a non-GBR flow) is 1 mbit / sec. The scheduler (1021) of the E2 node (1020) can identify that the size of the averaging window is 2 seconds. The scheduler (1021) of the E2 node (1020) can identify that data of size 2 [mbit] can be transmitted within the averaging window based on the fact that the size of the averaging window is 2 seconds and the maximum flow bit rate for a service corresponding to 5QI (or a non-GBR flow) is 1 mbit / sec. The scheduler (1021) of the E2 node (1020) can schedule 2 [mbit] of data to be transmitted within a time interval (1450) corresponding to the averaging window. For example, the scheduler (1021) of the E2 node (1020) can schedule 2 [mbit] of data to be transmitted within a time interval (1450-1) of the time interval (1450). The scheduler (1021) of the E2 node (1020) can schedule not to transmit data within a time interval (1450-2) of the time interval (1450). Within the time interval (1450), 2 [mbit] of data may be transmitted within the time interval (1450-1). Since 2 [mbit] of data is transmitted within the time interval (1450-1), the E2 node (1020) may not transmit data to the terminal within the time interval (1450-2) within the time interval (1450). When the ASM function is applied, the O-RU (or RU) connected to the E2 node (1020) may be set to operate in the sleep mode during the time interval (1450-2) (or at least a part of the time interval (1450-2)). The near-RT RIC (1010) may control the O-RU to operate in the sleep mode within the time interval (1450-2) based on controlling the E2 node (1020). For example, the near-RT RIC (1010) may disable at least one of the array carrier of the O-RU, the tx array carrier of the O-RU, the rx array carrier of the O-RU, or the O-RU while the O-RU is in sleep mode. As described above, the near-RT RIC (1010) can transmit data within a short time interval and schedule the O-RU to operate in sleep mode for a long time by setting the size of the averaging window to be large. Referring to FIGS. 14A and 14B , the near-RT RIC (1010) may set (or determine) a maximum flow bit rate and / or an averaging window for a service corresponding to 5QI (or a non-GBR flow) based on the service corresponding to 5QI. For example, the near-RT RIC (1010) may set a large size of the averaging window (e.g., time interval (1450)) for a service whose traffic pattern tends to increase rapidly. The service may include a file transfer, a file transfer protocol (FTP) file transfer service, and a hypertext transfer protocol (HTTP) streaming service. For example, the near-RT RIC (1010) can set an energy-saving policy based on the characteristics of the traffic in a service with a tendency for a sudden increase in traffic patterns. For example, the near-RT RIC (1010) can set a maximum flow bit rate and / or an averaging window for a non-GBR flow based on the characteristics of the traffic (or a service corresponding to 5QI). The near-RT RIC (1010) can perform an energy-saving function by measuring the amount of transmitted traffic within the averaging window, thereby reducing bandwidth waste. According to the above-described embodiment, the efficiency of the network can be increased. Figure 15 is a flowchart illustrating the operation of a near-RT RIC for energy saving. In the following embodiments, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. In operation 1510, the near-RT RIC (1010) may perform an RIC join procedure with the E2 node (1020). For example, the near-RT RIC (1010) may perform an RIC join procedure to transmit an RIC control message to the E2 node (1020). For example, the near-RT RIC (1010) may transmit an RIC subscription request message to the E2 node (1020). The RIC subscription request message may be related to a RAN function. The RAN function may be related to E2SM-CCC (E2 service model-cell configuration and control) for energy saving. For example, the RIC subscription request message may be transmitted to transmit control information for energy saving to the E2 node (1020). The E2 node (1020) may transmit an RIC subscription response message to the near-RT RIC (1010). For example, in response to the RIC subscription request message, the E2 node (1020) may transmit an RIC subscription response message to the near-RT RIC (1010). At operation 1520, the near-RT RIC (1010) may transmit an RIC control message to the E2 node. For example, the near-RT RIC (1010) may transmit the RIC control message to the E2 node based on the RIC subscription procedure according to operation 1510. Operation 1520 may correspond to operation 1110 of FIG. 11. The RIC control message may be related to a RAN function. The RAN function may be related to E2SM-CCC for energy saving. According to one embodiment, the RIC control message may include information according to Tables 1 to 5. For example, the RIC control message may include information about 5QI (5G quality of service (QoS) identifier), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. An example of information about 5QI may be '5qi' in Table 5. An example of information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow may be 'mNgbrFbr' in Table 5. An example of information about an average window for calculating the Non-GBR flow bit rate may be 'Averaging Window' in Table 5. For example, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. The near-RT RIC (1010) may control the E2 node (1020) to calculate the Non-GBR flow bit rate to be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow through the averaging window. For example, the RIC message may include information for initiating the activation or deactivation of an energy-saving feature for the advanced sleep mode (ASM). An example of information for initiating the activation or deactivation of an energy-saving feature for the advanced sleep mode (ASM) may be 'energySavingControl' in Table 1. The near-RT RIC (1010) can control the E2 node (1020) to activate an energy saving function for an enhanced sleep mode based on an RIC control message. For example, the energy saving function can be performed based on deactivation of at least some of the array carriers of the RU (or O-RU) for the E2 node (1020) or the RU. The near-RT RIC (1010) can control the E2 node (1020) to deactivate at least some of the array carriers of the RU (or O-RU) for the E2 node (1020). For example, a near-RT RIC (1010) may control an E2 node (1020) to transmit data based on a non-GBR flow bit rate calculated through an averaging window via an RIC control message. The near-RT RIC (1010) may deactivate at least some of the array carriers of an RU (or O-RU) for the E2 node (1020) within a second time interval distinct from a first time interval during which the data is transmitted. Within the second time interval, the RU may be set to operate in a sleep mode. According to one embodiment, the near-RT RIC (1010) may receive an RIC indication message from an E2 node (1020). For example, the operation of receiving the RIC indication message from the E2 node (1020) may correspond to operation 1250 of FIG. 12. For example, the RIC instruction message may include information according to Table 7. The RIC instruction message may include state information regarding energy saving. The state information regarding energy saving may include at least one of information regarding whether an energy saving function for a cell is activated, information regarding a specific state related to energy saving, or information regarding an energy saving policy. An example of information regarding whether an energy saving function for a cell is activated may be 'cesSwitch' in Table 7. An example of information regarding a specific state related to energy saving may be 'energySavingState' in Table 7. An example of information regarding an energy saving policy may be 'asmPolicyList' in Table 7. Figure 16 is a flowchart illustrating the operations of the E2 node for energy saving. In the following embodiments, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. At operation 1610, the E2 node (1020) may perform an RIC join procedure with the near-RT RIC (1010). For example, the near-RT RIC (1010) may perform an RIC join procedure to transmit an RIC control message to the E2 node (1020). For example, the E2 node (1020) may receive an RIC subscription request message from the near-RT RIC (1010). The near-RT RIC (1010) may transmit an RIC subscription request message to the E2 node (1020). The RIC subscription request message may be related to a RAN function. The RAN function may be related to E2 service model-cell configuration and control (E2SM-CCC) for energy saving. For example, the RIC subscription request message may be transmitted to transmit control information for energy saving to the E2 node (1020). The E2 node (1020) may transmit an RIC subscription response message to the near-RT RIC (1010). For example, the E2 node (1020) may, in response to the RIC subscription request message, transmit an RIC subscription response message to the near-RT RIC (1010). At operation 1620, the E2 node (1020) may receive an RIC control message from the near-RT RIC (1010). For example, the E2 node (1020) may receive the RIC control message from the near-RT RIC (1010) based on the RIC subscription procedure according to operation 1610. Operation 1620 may correspond to operation 1110 of FIG. 11. The RIC control message may be related to a RAN function. The RAN function may be related to E2SM-CCC for energy saving. According to one embodiment, the RIC control message may include information according to Tables 1 to 5. For example, the RIC control message may include information about 5QI (5G quality of service (QoS) identifier), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. An example of information about 5QI may be '5qi' in Table 5. An example of information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow may be 'mNgbrFbr' in Table 5. An example of information about an average window for calculating the Non-GBR flow bit rate may be 'Averaging Window' in Table 5. For example, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. The E2 node (1020) (or the scheduler (1021) of the E2 node (1020)) may calculate the Non-GBR flow bit rate to be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow through the averaging window based on the RIC control message. For example, the RIC message may include information for initiating the activation or deactivation of an energy-saving feature for the advanced sleep mode (ASM). An example of information for initiating the activation or deactivation of an energy-saving feature for the advanced sleep mode (ASM) may be 'energySavingControl' in Table 1. The E2 node (1020) may activate an energy saving function for an enhanced sleep mode based on a RIC control message. For example, the energy saving function may be performed based on deactivation of at least some of the array carriers of an RU (or an O-RU) for the E2 node (1020) or an RU. The E2 node (1020) may deactivate at least some of the array carriers of an RU (or an O-RU) for the E2 node (1020). For example, data may be transmitted based on a non-GBR flow bit rate calculated through an averaging window of an E2 node (1020). The E2 node (1020) may deactivate at least some of the array carriers of an RU (or O-RU) for the E2 node (1020) or the RU within a second time interval distinct from a first time interval in which the data is transmitted. Within the second time interval, the RU may be set to operate in a sleep mode. The E2 node (1020) may control the RU to operate in the sleep mode within the second time interval. According to one embodiment, the E2 node (1020) may transmit an RIC indication message to the near-RT RIC (1010). For example, the operation of the E2 node (1020) transmitting the RIC indication message may correspond to operation 1250 of FIG. 12. For example, the RIC instruction message may include information according to Table 7. The RIC instruction message may include state information regarding energy saving. The state information regarding energy saving may include at least one of information regarding whether an energy saving function for a cell is activated, information regarding a specific state related to energy saving, or information regarding an energy saving policy. An example of information regarding whether an energy saving function for a cell is activated may be 'cesSwitch' in Table 7. An example of information regarding a specific state related to energy saving may be 'energySavingState' in Table 7. An example of information regarding an energy saving policy may be 'asmPolicyList' in Table 7. According to one embodiment, a method performed by a device of a Near-RT (real-time) radio access network intelligent controller (RIC) may include transmitting an RIC control message to an E2 node through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating a Non-GBR flow bit rate. According to one embodiment, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. According to one embodiment, the RIC control message may include information to initiate activation or deactivation of an energy saving function for advanced sleep mode (ASM). According to one embodiment, the method may include controlling the E2 node to activate the energy saving function based on the RIC control message. The energy saving function may be performed based on at least some of the array carriers of a radio unit (RU) for the E2 node or on deactivation of the RU. In one embodiment, the method may include controlling the E2 node to transmit data based on the Non-GBR flow bit rate calculated through the averaging window via the RIC control message. The method may include controlling the E2 node to deactivate at least some of the array carriers of the RU or the RU for the E2 node within a second time interval distinct from the first time interval during which the data is transmitted. According to one embodiment, the method may include receiving an RIC indication message from the E2 node. The RIC indication message may include at least one of information regarding whether an energy saving function for a cell is activated, information regarding a specific state related to energy saving, or information regarding an energy saving policy. According to one embodiment, the method may include an operation of performing an RIC subscription procedure with the E2 node. The method may include an operation of transmitting the RIC control message to the E2 node based on the RIC subscription procedure. According to one embodiment, a method performed by a device of an E2 node may include receiving, through an E2 interface, an RIC control message from a Near-RT (real-time) RIC (radio access network intelligent controller). The RIC control message may include information about a 5G QoS (quality of service) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. According to one embodiment, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. According to one embodiment, the RIC control message may include information to initiate activation or deactivation of an energy saving function for advanced sleep mode (ASM). According to one embodiment, a device of a Near-RT (real time) radio access network intelligence controller (RIC) may include a transceiver, a processor, and a memory including instructions. The instructions, when executed by the processor, may cause the device to transmit an RIC control message to an E2 node via an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an averaging window for calculating the Non-GBR flow bit rate. According to one embodiment, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. According to one embodiment, the RIC control message may include information to initiate activation or deactivation of an energy saving function for advanced sleep mode (ASM). In one embodiment, the instructions, when executed by the processor, may cause the device to control the E2 node to activate the energy saving function based on the RIC control message. The energy saving function may be performed based on at least some of the array carriers of a radio unit (RU) for the E2 node or on deactivation of the RU. In one embodiment, the instructions, when executed by the processor, may cause the device to control the E2 node to transmit data based on the Non-GBR flow bit rate calculated via the averaging window via the RIC control message. The instructions, when executed by the processor, may cause the device to control the E2 node to deactivate at least some of the array carriers of the RU or the RU for the E2 node within a second time interval distinct from a first time interval during which the data is transmitted. According to one embodiment, the instructions, when executed by the processor, may cause the device to receive an RIC indication message from the E2 node. The RIC indication message may include at least one of information regarding whether an energy saving function for the cell is activated, information regarding a specific state related to energy saving, or information regarding an energy saving policy. According to one embodiment, the instructions, when executed by the processor, may cause the device to perform an RIC subscription procedure with the E2 node. The instructions, when executed by the processor, may cause the device to transmit the RIC control message to the E2 node based on the RIC subscription procedure. According to one embodiment, a device of an E2 node may include a transceiver, a processor, and a memory including instructions. The instructions, when executed by the processor, may cause the device to receive a radio access network intelligent controller (RIC) control message from a near-real-time (RT) RIC through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the non-GBR flow bit rate. According to one embodiment, the Non-GBR flow bit rate calculated through the averaging window may be less than or equal to the maximum bit rate flow for the Non-GBR (guaranteed bit rate) flow. According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of a device of a Near-RT (real time) radio access network intelligence controller (RIC) including a transceiver, cause an E2 node to transmit an RIC control message through an E2 interface. The RIC control message may include information about a 5G quality of service (QoS) identifier (5QI), information about a maximum bit rate flow for a Non-GBR (guaranteed bit rate) flow, and information about an average window for calculating the Non-GBR flow bit rate. According to one embodiment, a method performed by a near-real time radio access network intelligence controller (Near-RT RIC) may include transmitting a radio access network intelligence controller (RIC) subscription request message for energy saving optimization to an E2 node, receiving an RIC subscription response message from the E2 node in response to the RIC subscription request message, and transmitting an RIC control request message to the E2 node, the RIC style type indicating a cell configuration associated with the E2 node and energy saving information. The energy saving information may include a fifth generation quality of service identifier (5QI) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an averaging window indicating a period for calculating the maximum bit rate of the Non-GBR flow. For example, the RIC control request message may include policy information for ASM (advanced sleep mode). The energy saving information may be included in the policy information for ASM. For example, the RIC control request message may include a data direction indicating either uplink (UL) or downlink (DL). For example, the method may include receiving an A1 policy message for energy saving optimization from a non-RT RIC (non-real time RIC), transmitting another subscription request message for key performance measurement to the E2 node based on the A1 policy message, and receiving another subscription response message from the E2 node in response to the other subscription request message. For example, the method may include an operation of receiving, from the E2 node, an RIC indication message including measurement information of the E2 node for energy saving optimization based on the other subscription response message, and an operation of determining the energy saving information based on the measurement information. For example, the E2 node may include a distributed unit (DU). According to one embodiment, a method performed in an E2 node may include receiving a radio access network intelligence controller (RIC) subscription request message for energy saving optimization from a near-real time radio access network intelligence controller (Near-RT RIC), transmitting an RIC subscription response message to the Near-RT RIC in response to the RIC subscription request message, and receiving an RIC control request message from the Near-RT RIC, the RIC style type indicating a cell configuration associated with the E2 node and including energy saving information. The energy saving information may include a fifth generation quality of service identifier (5QI) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an averaging window indicating a period for calculating the maximum bit rate of the Non-GBR flow. For example, the RIC control request message may include policy information for ASM (advanced sleep mode). The energy saving information may be included in the policy information for ASM. For example, the RIC control request message may include a data direction indicating either uplink (UL) or downlink (DL). For example, the method may include receiving another subscription request message from the Near-RT RIC for a key performance measurement, and in response to the another subscription request message, transmitting the another subscription response message to the Near-RT RIC. For example, the method may include transmitting, to the Near-RT RIC, an RIC indication message including measurement information of the E2 node for energy saving optimization based on the other subscription response message. For example, the E2 node may include a distributed unit (DU). According to one embodiment, a network apparatus for performing functions of a near-real time radio access network intelligence controller (Near-RT RIC) may include at least one transceiver including communication circuitry, at least one processor including processing circuitry, and a memory including one or more storage media and storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the network apparatus to transmit a radio access network intelligence controller (RIC) subscription request message for energy saving optimization to an E2 node, receive an RIC subscription response message from the E2 node in response to the RIC subscription request message, and transmit an RIC control request message to the E2 node including an RIC style type and energy saving information indicating a cell configuration associated with the E2 node. The energy saving information may include a fifth generation quality of service identifier (5QI) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating a period for calculating the maximum bit rate of the Non-GBR flow. According to one embodiment, a network apparatus for performing functions of an E2 node may include at least one transceiver including communication circuitry, at least one processor including processing circuitry, and a memory including one or more storage media and storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the network apparatus to receive a radio access network intelligence controller (RIC) subscription request message for energy saving optimization from a Near-RT RIC (near-real time radio access network intelligence controller), to transmit an RIC subscription response message to the Near-RT RIC in response to the RIC subscription request message, and to receive an RIC control request message from the Near-RT RIC that includes an RIC style type and energy saving information indicating a cell configuration associated with the E2 node. The energy saving information may include a fifth generation quality of service identifier (5QI) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating a period for calculating the maximum bit rate of the Non-GBR flow. According to the above-described embodiment, the near-RT RIC can request the E2 node (e.g., the O-DU) to perform an ASM operation for specific cells. Depending on the ASM operation, the non-GBR bearer throughput may be limited. According to the above-described embodiment, the near-RT RIC can transmit to the E2 node information indicating a maximum bit rate flow for a non-GBR flow according to a service corresponding to 5QI in order to limit the non-GBR bearer throughput. The near-RT RIC can transmit to the E2 node information indicating an averaging window for calculating the non-GBR flow bit rate. According to the above-described embodiment, since the target QoS is different for each service, the near-RT RIC can apply ASM to the cell by setting the averaging window differently for each service. According to the above-described embodiment, network resources can be optimized. Since the averaging window is set differently for each service, network resources can be utilized efficiently. As network resources are utilized more efficiently, the performance of the entire network system improves, and more users can be provided with stable services. The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies. Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure. In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements. Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.

Claims

1. A method performed by a near-RT RIC (near-real time radio access network intelligence controller), An action of sending a radio access network intelligence controller (RIC) subscription request message to an E2 node for energy saving optimization; In response to the RIC subscription request message, receiving a RIC subscription response message from the E2 node; and An operation of transmitting to the E2 node an RIC control request message including an RIC style type and energy saving information indicating a cell configuration related to the E2 node, The above energy saving information is: A 5QI (fifth generation quality of service identifier) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating an interval for calculating the maximum bit rate of the Non-GBR flow, method.

2. In the first paragraph, the RIC control request message, Contains policy information for ASM (advanced sleep mode), The above energy saving information is: Included in the policy information for the above ASM, method.

3. In either of paragraphs 1 and 2, the RIC control request message, Further including a data direction indicating either uplink (UL) or downlink (DL), method.

4. In any one of paragraphs 1 to 3, the method comprises: An operation of receiving an A1 policy message for optimizing the above energy saving from a non-RT RIC (non-real time RIC); An operation of transmitting another subscription request message for key performance measurement to the E2 node based on the above A1 policy message; and In response to said other subscription request message, further comprising the action of receiving said other subscription response message from said E2 node. method.

5. In the fourth paragraph, the method, An operation of receiving an RIC indication message including measurement information of the E2 node for energy saving optimization from the E2 node based on the other subscription response message; and Further comprising an operation of determining the energy saving information based on the above measurement information. method.

6. In any one of the first to fifth clauses, the E2 node includes a DU (distributed unit). method. In a method performed at node 7.E2, the method comprises: An operation of receiving a subscription request message from a near-real time radio access network intelligence controller (Near-RT RIC) for energy saving optimization; In response to the RIC subscription request message, an operation of transmitting an RIC subscription response message to the Near-RT RIC; and An operation of receiving, from the Near-RT RIC, an RIC control request message including an RIC style type and energy saving information indicating a cell configuration associated with the E2 node; The above energy saving information is: A 5QI (fifth generation quality of service identifier) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating an interval for calculating the maximum bit rate of the Non-GBR flow, method.

8. In the 7th paragraph, the RIC control request message, Contains policy information for ASM (advanced sleep mode), The above energy saving information is: Included in the policy information for the above ASM, method.

9. In any one of paragraphs 7 and 8, the RIC control request message, Further including a data direction indicating either uplink (UL) or downlink (DL), method.

10. In any one of paragraphs 7 to 9, the method, The operation of receiving another subscription request message for key performance measurement from the Near-RT RIC; and In response to said other subscription request message, further comprising the action of transmitting said other subscription response message to said Near-RT RIC. method.

11. In the 10th paragraph, the method, Further comprising an operation of transmitting an RIC indication message including measurement information of the E2 node for energy saving optimization to the Near-RT RIC based on the other subscription response message. method.

12. In any one of clauses 7 to 11, the E2 node includes a DU (distributed unit). method.

13. In a network apparatus for performing the functions of a near-real time radio access network intelligence controller (Near-RT RIC), At least one transceiver comprising communication circuitry; At least one processor comprising a processing circuit; and A memory comprising one or more storage media and storing instructions, The above instructions, when individually or collectively executed by the at least one processor, Send a radio access network intelligence controller (RIC) subscription request message to the E2 node for energy saving optimization, In response to the RIC subscription request message, a RIC subscription response message is received from the E2 node, Causing the network device to transmit to the E2 node an RIC control request message including an RIC style type and energy saving information indicating a cell configuration associated with the E2 node; The above energy saving information is: A 5QI (fifth generation quality of service identifier) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating an interval for calculating the maximum bit rate of the Non-GBR flow, Network devices.

14. In a network apparatus for performing the functions of an E2 node, At least one transceiver comprising communication circuitry; At least one processor comprising a processing circuit; and A memory comprising one or more storage media and storing instructions, The above instructions, when individually or collectively executed by the at least one processor, Receive a subscription request message for energy saving optimization from a Near-RT RIC (near-real time radio access network intelligence controller), In response to the RIC subscription request message, a RIC subscription response message is transmitted to the Near-RT RIC, Causing the network device to receive from the Near-RT RIC an RIC control request message including an RIC style type and energy saving information indicating a cell configuration associated with the E2 node; The above energy saving information is: A 5QI (fifth generation quality of service identifier) value, a maximum bit rate for a Non-GBR (guaranteed bit rate) flow having the 5QI value, and an average window indicating an interval for calculating the maximum bit rate of the Non-GBR flow, Network devices.

Images