Device and method for controlling cell access in wireless communication system

Abstract

Provided in embodiments is a method performed by a near-real time (RT) radio access network intelligence controller (RIC). The method may comprise the steps of: generating an RIC control request message including an RIC control header information element (IE) and an RIC control message IE; and transmitting the RIC control request message to an E2 node. The RIC control header IE may include an RIC style type set to a value indicating radio access control, and a control action identifier (ID) set to a value indicating access barring control. The RIC control message IE may include one or more radio access network (RAN) parameters related to the access barring control.

Description

Device and method for cell access control in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. The present disclosure relates to a device and method for cell access control in a wireless communication system.

[0002] 4G(4 th To meet the increasing demand for wireless data traffic since the commercialization of the 5G (5 generation) communication system, the improved 5G (5 th Efforts are being made to develop 5G communication systems or pre-5G communication systems. For this reason, 5G communication systems or pre-5G communication systems are also called Beyond 4G Network communication systems or Post-LTE systems.

[0003] 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, beamforming, massive MIMO (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems.

[0004] Additionally, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.

[0005] In addition, advanced coding modulation (ACM) methods such as Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and Sliding Window Superposition Coding (SWSC), as well as advanced access technologies such as Filter Bank Multi Carrier (FBMC), Non Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA), are being developed in 5G systems.

[0006] In order to meet the demand for wireless data traffic, 5G system, NR (new radio or next radio) is commercialized, and it is expected that it will be able to provide users with high data transmission rate services through 5G system like 4G, and also provide wireless communication services for various purposes such as Internet of Things and services that require high reliability for specific purposes. In the current mixed system of 4th generation communication system, 5th generation system, etc., O-RAN (open radio access network) established by business operators and equipment providers defines E2AP (E2 application protocol) standard in the application protocol of E2 interface between E2 node and Near-RT (real time) RIC (RAN (radio access network) intelligent controller).

[0007] Looking back at the evolution of wireless communication over successive generations, technologies have primarily been developed for human-facing services such as voice, multimedia, and data. With the commercialization of the 5G (5th Generation) communication system, an explosive increase in connected devices is expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction equipment, and factory equipment. Mobile devices are also expected to evolve into diverse form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6G (6th Generation) era, efforts are being made to develop improved 6G communication systems to connect hundreds of billions of devices and objects and provide diverse services. For this reason, 6G communication systems are often referred to as "beyond 5G."

[0008] The 6G communication system, expected to be realized around 2030, will have a maximum transmission speed of terabytes (i.e., 1,000 gigabits) per second (bps) and a wireless latency of 100 microseconds (μsec). In other words, compared to 5G, the transmission speed in a 6G communication system will be 50 times faster and the wireless latency will be reduced to one-tenth.

[0009] To achieve these high data rates and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz (THz) band (e.g., from 95 gigahertz (GHz) to 3 terahertz (THz)). Compared to the millimeter wave (mmWave) band introduced in 5G, the terahertz band is expected to have more severe path loss and atmospheric absorption, making it more important to develop technologies that can guarantee signal reach, or coverage. Key technologies to ensure coverage include Radio Frequency (RF) components, antennas, new waveforms that offer better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming, and multiple antenna transmission technologies such as massive Multiple-Input and Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed to improve the coverage of terahertz band signals.

[0010] In addition, in order to improve frequency efficiency and system network, 6G communication systems are developing full duplex technology that utilizes the same frequency resources at the same time for uplink and downlink; network technology that integrates satellites and HAPS (High-Altitude Platform Stations); network structure innovation technology that supports mobile base stations and enables optimization and automation of network operation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes AI (Artificial Intelligence) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources (Mobile Edge Computing (MEC), cloud, etc.). In addition, efforts are being made to further strengthen connectivity between devices, further optimize networks, promote softwareization of network entities, and increase the openness of wireless communications through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe use of data, and the development of technologies for maintaining privacy.

[0011] Research and development of these 6G communication systems are expected to enable a new level of hyper-connected experience through the hyper-connectivity of 6G communication systems, which encompass not only connections between things but also connections between people and things. Specifically, 6G communication systems are expected to enable services such as truly immersive eXtended Reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems through enhanced security and reliability, will be applied in diverse fields such as industry, medicine, automobiles, and home appliances.

[0012] In 6G communication systems, RAN functions are expected to be further refined, separating them into service subscribers and service providers. In service-based networks, subscription service confirmation procedures for service subscription status will be applied to various functions.

[0013] 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 is applicable as prior art related to the present disclosure.

[0014] In embodiments, a method performed by a Near-RT (real time) radio access network intelligence controller (RIC) is provided. The method may include generating an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and transmitting the RIC control request message to an E2 node. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating access barring control. The RIC control message IE may include one or more radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include: a parameter indicating whether a cell is barred; a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when a highest-ranked cell is barred; a parameter indicating whether a cell is reserved for operator use; or may include at least one parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs).

[0015] In embodiments, a method performed by an E2 node is provided. The method may include receiving, from a near-real time (RT) radio access network intelligence controller (RIC), an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and performing a procedure related to access barring control based on the RIC control request message. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating the access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include: a parameter indicating whether a cell is barred; a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when a highest-ranked cell is barred; A parameter indicating whether the cell is reserved for operator use; or a parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs).

[0016] In embodiments, a Near-RT (real time) radio access network intelligence controller (RIC) is provided. The Near-RT RIC may include at least one processor including processing circuitry; and a memory including one or more storage media and storing instructions. The instructions, when executed by the at least one processor, may cause the Near-RT RIC to generate an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and to transmit the RIC control request message to an E2 node. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include a parameter indicating whether a cell is barred; The apparatus may include at least one of: a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell is prohibited; a parameter indicating whether the cell is reserved for operator use; or a parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs).

[0017] In embodiments, an E2 node is provided. The E2 node may include at least one processor including a processing circuit; and a memory including one or more storage media and storing instructions. The instructions, when executed by the at least one processor, may cause the E2 node to receive an RIC control request message from a Near-RT (real time) radio access network intelligence controller (RIC) including an RIC control header information element (IE) and an RIC control message IE, and to perform a procedure related to access barring control based on the RIC control request message. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating the access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include a parameter indicating whether a cell is barred; The apparatus may include at least one of: a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell is prohibited; a parameter indicating whether the cell is reserved for operator use; or a parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs).

[0018] In embodiments, a method performed by an E2 node is provided. The method may include receiving a RIC control request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller).

[0019] In embodiments, a method is provided that is performed by a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The method may include an operation of transmitting an RIC control request message to an E2 node.

[0020] In embodiments, an electronic device of an E2 node is provided. The electronic device may include at least one processor and a memory storing instructions. The instructions, when executed by the at least one processor, may cause the E2 node to receive an RIC control request message from a real-time (RT) RIC (radio access network (RAN) intelligent controller).

[0021] In embodiments, an electronic device of a Near-RT (real time) RIC (radio access network (RAN) intelligent controller) is provided. The electronic device may include at least one processor and a memory storing instructions. The instructions, when executed by the at least one processor, may cause the Near-RT RIC to transmit an RIC control request message to an E2 node.

[0022] In embodiments, an electronic device of an E2 node is provided. The electronic device may include at least one transceiver and at least one processor. The at least one processor may be configured to receive an RIC control request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller) through the at least one transceiver.

[0023] In embodiments, an electronic device of a Near-RT (real time) RIC (radio access network (RAN) intelligent controller) is provided. The electronic device may include at least one transceiver and at least one processor. The at least one processor may be configured to cause the Near-RT RIC to transmit an RIC control request message to an E2 node through the at least one transceiver.

[0024] In embodiments, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may include instructions that, when executed by a processor, cause an E2 node to perform operations including receiving a RIC control request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller).

[0025] In embodiments, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium may include instructions that, when executed by a processor, cause a Near-RT (real time) RIC (radio access network (RAN) intelligent controller) to perform operations, including transmitting an RIC control request message to an E2 node.

[0026] Figure 1 is 4G (4 th generation) shows an example of the core network of the LTE (Long Term Evolution) communication system.

[0027] Figure 2 is 5G (5 th generation) shows an example of a core network of a communication system.

[0028] Figure 3 shows an example of an architecture for O-RAN.

[0029] 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.

[0030] Figure 4b shows the protocol stack of the E2 application protocol message.

[0031] Figure 5 shows the configuration of electronic devices in a wireless access network.

[0032] Figure 6 illustrates the logical functions associated with E2 messages of an E2 node and RIC in a wireless access network.

[0033] Figure 7 shows examples of functional separation between the E2 node and the RIC.

[0034] Figure 8 shows an implementation example of the E2 node and RIC.

[0035] Figure 9 shows examples of functional separation between the CU (central unit) and the RIC.

[0036] Figures 10a and 10b illustrate examples of the E2 setup procedure.

[0037] Figures 11a and 11b illustrate examples of RIC subscription procedures.

[0038] Figure 12 shows an example of a RIC indication procedure.

[0039] Figures 13a and 13b show examples of RIC control procedures.

[0040] Figure 14 shows an example of a wireless access network.

[0041] Figure 15 shows an example of access barring for energy saving.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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"}.

[0047] 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.

[0048] 4th generation (4 th generation, 4G) / 5th generation (5 thAs 5G (5th generation) 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) IMT-2000 project. Established in December 1998, 3GPP standards are based on the advanced GSM standards, and include radio, core network, and service architecture in 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).

[0049] 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.

[0050] 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 with the E2 node through a subscription procedure. 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.

[0051] Figure 1 is 4G (4 th generation) shows an example of the core network of the LTE (Long Term Evolution) communication system.

[0052] 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).

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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).

[0057] 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.

[0058] 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).

[0059] Figure 2 is 5G (5 th generation) shows an example of a core network of a communication system.

[0060] 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 referred to. For the base station (203), the descriptions of the base station (110) may be referred to. The base station (203) may be connected to the AMF (211) via the N2 interface and to the UPF (231) via the N3 interface. In addition to the base station, the base station (203) may include an 'access point (AP)', a 'radio access network (RAN) node', a '5G node (5 thThe term "next generation node" (GNB), "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. 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. In addition, UPF (231) is connected to a data network (260) and can transmit packets through the Internet.

[0061] 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.

[0062] 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).

[0063] 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.

[0064] 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 multiple base stations located in different frequency bands. The terminal is connected to a first base station (e.g., a base station that provides services using LTE technology or 4th generation mobile communication technology) (e.g., a base station (110)) and a second base station (e.g., NR (new radio) technology or 5G (5 th5G) can be simultaneously connected to a base station (e.g., base station (203)) that provides services using mobile communication technology to transmit and receive traffic. 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 connection 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, a method that operates through 5G technology (or LTE technology and 5G technology) based on the 5G core network may be referred to as 5G SA (standalone).

[0065] 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.

[0066] 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.

[0067] 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).

[0068] 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.

[0069] 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.

[0070] Figure 3 shows an example of an architecture for O-RAN.

[0071] 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).

[0072] 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).

[0073] 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.

[0074] 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) can 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) can collect traffic information (e.g., traffic load, user QoS) and / or system configuration information (e.g., the Near-RT RIC (340) can collect traffic information from an E2 node through an E2 interface). The Near-RT RIC (340) can infer / predict / set / configure ASM (advanced sleep mode) activation policy and system configurations. The Near-RT RIC (340) can be connected to an O-eNB (305), an O-CU-CP (331), an O-CU-UP (332), and / or an O-DU (320). The Near-RT RIC (340) can communicate with the O-eNB (305), the O-CU-CP (331), the O-CU-UP (332), and / or the O-DU (320). The RIC (340) can be connected to each node via an E2 interface. In addition, the interface between the O-CU-CP (331) and the O-DU (320) can be referred to as an F1-c interface. The interface between the O-CU-UP (332) and the O-DU (320) can be referred to as an F1-u interface.In the following description, DU and O-DU, CU-CP and O-CU-CP, CU-UP and O-CU-UP may be used interchangeably.

[0075] 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 (e.g., ML model deployment) can be provided via the A1 interface. The Non-RT RIC (350) can drive content delivered via the A1 interface. For example, the Non-RT RIC (350) can train an AI / ML model based on data from the O1 interface (e.g., traffic load, QoS per user, system configuration information).

[0076] 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.

[0077] 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.

[0078] 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.

[0079] Referring to FIG. 4A, the 5G communication system may provide arrangements of entities according to a non-standalone mode (e.g., non-standalone (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 the non-standalone mode or the standalone mode. For example, in the 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.

[0080] Figure 4b shows the protocol stack of the E2 application protocol message.

[0081] 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).

[0082] The wireless network layer includes E2AP (450). E2AP (450) is used to transmit subscription request messages / subscription response 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).

[0083] 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. The electronic device may be referred to as a network device. Terms such as '... unit', '... device', etc. used hereinafter mean a unit that processes at least one function or operation, and this may be implemented by hardware, software, or a combination of hardware and software.

[0084] Referring to FIG. 5, the electronic device may include a transceiver (510), a memory (520), and a processor (530).

[0085] 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.

[0086] 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.

[0087] 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.

[0088] FIG. 6 illustrates logical functions related to E2 messages of an E2 node and an RIC in a wireless access network. The RIC (640) of FIG. 6 may exemplify a Near-RT RIC (340). The descriptions of the Near-RT RIC (340) of FIG. 3 may also be applied to the RIC (640). The E2 node (610) of FIG. 6 may exemplify one of the 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)) of FIG. 3. The descriptions of each entity of FIG. 3 may also be applied to the E2 node (610).

[0089] 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)).

[0090] 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.

[0091] 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).

[0092] 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).

[0093] Figure 8 illustrates an implementation example of an E2 node and a 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), E2 node (610)) and the RIC (e.g., Near-RT RIC (340), RIC (640)) can be virtualized on a cloud platform (e.g., open chassis and blade specification edge cloud) and configured on a device (e.g., server). This scenario can provide sufficiently low latency 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 RIC closer to real time (RT) than the limit of how much O-DU functionality can be centralized.

[0094] Figure 9 shows examples of functional separation between the CU (central unit) and the RIC.

[0095] 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.

[0096] 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).

[0097] Below, the procedures on the E2 interface defined in O-RAN are described first. In this document, a table is used to describe the IEs in a message, and 'M' in the table indicates that the inclusion of the corresponding IE in the message is mandatory. 'O' indicates that the inclusion of the corresponding IE in the message is optional. 'Message Type' indicates the message type (e.g., initiation message, successful result, failed result), and 'Transaction ID' can be used to uniquely identify the procedure (e.g., RIC control procedure) among the parallel ongoing procedures of the same type.

[0098] In this disclosure, procedures between an E2 node (610) and a Near-RT RIC (640) are described. Hereinafter, an E2 node for performing an E2AP procedure is referred to as an E2 node (610), and a Near-RT RIC for performing an E2AP procedure is referred to as a Near-RT RIC (640). For the E2 node (610), reference may be made to the description of 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)) described through FIGS. 1 to 9. For the Near-RT RIC (640), reference may be made to the description of a Near-RT RIC (340), an RIC (640) described through FIGS. 1 to 9.

[0099] 1. E2 Setup Procedure

[0100] Figures 10a and 10b illustrate examples of an E2 setup procedure. The purpose of the E2 setup procedure is to exchange application-level data necessary for an E2 node (e.g., E2 node (610)) and a Near-RT RIC (e.g., Near-RT RIC (640)) to interoperate properly on the E2 interface. This procedure is the first E2AP procedure triggered after a transport network layer (TNL) association is established. In this procedure, all existing application-level configuration data of each of the two nodes may be erased and replaced with received data. The E2 setup procedure may utilize E2 support function signaling. The E2 setup procedure may be initiated by the E2 node (610). Figure 10a illustrates an example of signaling when the E2 setup procedure succeeds, and Figure 10b illustrates an example of signaling when the E2 setup procedure fails.

[0101] Referring to FIG. 10A, in operation (1001), an E2 node (610) may transmit an E2 setup request message to a Near-RT RIC (640). The E2 node (610) may initiate an E2 setup procedure by transmitting the E2 setup request message including data. The E2 setup request message may be used to convey initialization information from the E2 node (610) to the Near-RT RIC (640). For example, the E2 setup request message may include a RAN capability addition list information element (IE). For example, the E2 setup request message may include an E2 node component configuration addition list IE. As an example, the E2 setup request message may have the following format.

[0102] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectTransaction IDM9.2.33.YESrejectGlobal E2 Node IDM9.2.6YESrejectRAN Functions Added List1List of RAN functions in E2 nodeYESreject>RAN Function item1.. <maxofranfunctionid>>>RAN Function IDM9.2.8Id of the declared Function->>RAN Function DefinitionM9.2.23Definition of Function->>RAN Function RevisionM9.2.24Revision counter->>RAN Function OIDM9.2.31Object identifier of corresponding E2SM-E2 Node Component Configuration Addition List1List of E2 Node component configuration informationYESreject>E2 Node Component Configuration Addition Item1.. <maxofe2nodecomponents>EACHreject>>E2 Node Component Interface TypeM9.2.26E2 Node component interface type->>E2 Node Component IDO9.2.32E2 Node Component Identifier->>E2 Node Component ConfigurationM9.2.27Contents depends on component interface type-

[0103] Range boundExplanationmaxofRANfunctionIDMaximum no. of RAN Functions supported by E2 Node. Value is 256.maxofE2nodeComponentsMaximum no. of E2 Node components supported by E2 Node. Value is 1024

[0104] For each IE in [Table 1], the descriptions of the O-RAN WG3.E2AP specification may be referenced. The maximum values ​​in [Table 2] are exemplary and are not to be construed as limiting the embodiments of the present disclosure. In addition, an E2 service model indicated through the RAN Function OID may be specified for each RAN Function ID. The RAN Function definition information may be used to provide the necessary information for the Near-RT RIC to support the corresponding RAN Function in the E2 node. The RAN Function OID may be used to identify the RAN Function definition in the RAN Function definition information. The RAN Function Revision indicates the revision counter (or update version information, update count) for the corresponding RAN function. The RAN Function OID is as follows. The RAN Function OID may uniquely indicate a specific E2 SM (service model). The RAN Function OID may be used to indicate the RAN Function Definition for a specific E2SM.

[0105] E2SM short nameOIDSyntax languageE2SM-NIiso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version1 (1) e2sm(2) e2sm-NI-IEs (1)ASN.1E2SM-KPM version1iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version1 (1) e2sm(2) e2sm-KPM-IEs (2)ASN.1E2SM-KPM version2iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version2 (2) e2sm(2) e2sm-KPM-IEs (2)ASN.1E2SM-RCiso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version1 (1) e2sm(2) e2sm-RC-IEs (3)ASN.1E2SM-CCCiso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) oran(53148) e2(1) version1 (1) e2sm(2) e2sm-CCC-IEs (4)JSON

[0106] Referring to [Table 3], it can be confirmed that E2SM-RC and E2SM-CCC differ in their coding methods. If the service model changes, the OID value corresponding to the corresponding RAN function ID may change.

[0107] In operation (1003), the E2 node (610) may receive an E2 setup response message from the Near-RT RIC (640). For example, if the Near-RT RIC (640) successfully processes the RAN Capability Addition List IE, the Near-RT RIC (640) may include a RAN Capability Allow List IE and / or a RAN Capability Deny List IE in the E2 setup response message. For example, if the Near-RT RIC (640) successfully processes the E2 Node Component Configuration Addition List IE, the Near-RT RIC (640) may include an E2 Node Component Configuration Addition Approval List IE in the E2 setup response message. As an example, the E2 setup response message may have the following format.

[0108] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectTransaction IDM9.2.33.YESrejectGlobal RIC IDM9.2.4YESrejectRAN Functions Accepted List0..1Complete list of Functions accepted by Near-RT RIC>RAN Functions ID item1 .. <maxofranfunctionid>YESReject>>RAN Function IDM9.2.8Id of the declared Function->>RAN Function RevisionM9.2.24Revision counter-RAN Functions Rejected List0..1Complete list of Functions not accepted by Near-RT RICRAN Functions ID Cause Item1 .. <maxofranfunctionid>YESreject>>RAN Function IDM9.2.8Id of the declared Function->>CauseM9.2.1Reason for not accepting function-E2 Node Component Configuration Addition Acknowledge List1Complete list of E2 Node Components in the E2 SETUP REQUEST messageYESreject>E2 Node Component Configuration Addition Acknowledge Item1.. <maxofe2nodecomponents>EACHreject>>E2 Node Component Interface TypeM9.2.26E2 Node component interface type->>E2 Node Component IDM9.2.32E2 Node Component Identifier->>E2 Node Component Configuration AcknowledgeM9.2.28Success or failure with Cause-

[0109] Range boundExplanationmaxofRANfunctionIDMaximum no. of RAN Functions supported by E2 Node. Value is 256.maxofE2nodeComponentsMaximum no. of E2 Node components supported by E2 Node. Value is 1024

[0110] For each IE in [Table 4], reference may be made to the descriptions of the O-RAN WG3.E2AP specification. The maximum values ​​in [Table 5] are exemplary and are not to be construed as limiting the embodiments of the present disclosure.

[0111] Referring to FIG. 10b, in operation (1001), the E2 node (610) may transmit an E2 setup request message to the Near-RT RIC (640). For the E2 setup request message, reference may be made to the descriptions of the E2 setup request message of operation (1001) of FIG. 10a.

[0112] In operation (1005), the E2 node (610) may receive an E2 setup failure message from the Near-RT RIC (640). The E2 setup failure message may be transmitted by the Near-RT RIC (640) to indicate an E2 setup failure to the E2 node (610). For example, if the Near-RT RIC (640) cannot accept the setup, it may respond with an E2 setup failure message including an appropriate cause value. The Near-RT RIC (640) may provide an alternative transport layer information (IE) to the E2 setup failure message for the E2 node to use when restarting the E2 setup procedure toward the Near-RT RIC (640). If the E2 Setup Failure message includes a 'Time To Wait' IE, the E2 node (610) may be required to wait at least the indicated time before resuming the E2 setup procedure toward the Near-RT RIC (640). For example, the E2 Setup Failure message may have the following format.

[0113] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectTransaction IDM9.2.33.YESrejectCauseM9.2.1YESignoreTime To WaitO9.2.5YESignoreCriticality DiagnosticsO9.2.2YESIgnoreTransport Layer InformationO9.2.29YESignore

[0114] For each IE in [Table 6], the descriptions of the O-RAN WG3.E2AP specification can be referenced.

[0115] Signaling between an E2 node (610) and a Near-RT RIC (640) for an E2 setup procedure is described through Figures 10a and 10b. As a non-limiting example, if the first message received for a particular TNL connection is not an E2 setup request message, an E2 setup response message, an E2 setup failure message, or an E2 node configuration update message, that message may be treated as a logical error.

[0116] 2. RIC Subscription Procedure

[0117] Figures 11a and 11b illustrate examples of RIC subscription procedures. The RIC subscription procedure can be used to establish an RIC subscription on an E2 node, consisting of an event trigger and a series of RIC service actions. The RIC subscription procedure can be initiated by a Near-RT RIC (640). The RIC subscription procedure can utilize RIC service signaling.

[0118] Referring to FIG. 11A, in operation (1101), the Near-RT RIC (640) may transmit an RIC subscription request message to the E2 node (610). The RIC subscription request message may be used to create a new RIC subscription in the E2 node. The Near-RT RIC (640) may initiate the RIC subscription procedure by transmitting the RIC subscription request message to the E2 node (610) including a unique RIC request ID IE assigned by the Near-RT RIC (640). When the Near-RT RIC (640) sends the RIC subscription request message, a timer (T RICEVENTcreate ) may be initiated. Upon receiving a RIC subscription request message, the E2 node (610) may perform the following action(s).

[0119] - Determine the target RAN function using the information in the RAN Function ID IE and configure the requested event trigger using the information in the RIC Subscription Details IE.

[0120] - If one or more REPORT, INSERTION and / or POLICY RIC service actions are included in the RIC subscription details IE, the target RAN function verifies the event trigger and the requested action sequence and, if accepted, stores the required RIC Request ID ('RIC Request ID'), the event trigger definition IE ('RIC Event Trigger Definition' IE) and the sequence of RIC service actions.

[0121] - If an optional RIC subscription start time IE ('RIC Subscription Start Time' IE) exists and has expired, the E2 node (610) may ignore the optional RIC subscription start time IE.

[0122] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Subscription DetailsMYESreject>RIC Event Trigger DefinitionM9.2.9->Sequence of Actions1.. <maxofricactionid>EACHignore>>RIC Action IDM9.2.10->>RIC Action TypeM9.2.11->>RIC Action DefinitionO9.2.12->>RIC subsequent ActionO9.2.13->>RIC Action Execution OrderO9.2.35Used to define a specific execution order-RIC Subscription Start TimeO9.2.34YESrejectRIC Subscription End TimeO9.2.34YESreject

[0123] Range boundExplanationmaxofRICActionIDMaximum no. of Actions to be requested by Near-RT RIC. Value is 16.

[0124] For each IE in [Table 7], reference may be made to the descriptions of the O-RAN WG3.E2AP specification. The maximum values ​​in [Table 8] are exemplary and are not to be construed as limiting the embodiments of the present disclosure.

[0125] In operation (1103), the Near-RT RIC (640) may receive an RIC Subscription Response message from the E2 node (610). The RIC Subscription Response message may be used to accept a request from the Near-RT RIC (640) to create a new RIC subscription at the E2 node. If the requested trigger and at least one required RIC service action are accepted by the E2 node (610), the E2 node (610) may reserve the necessary resources for each approved RIC service action and transmit a RIC Subscription Response message to the Near-RT RIC (640). For example, the E2 node (610) may include the RIC service actions for which resources are prepared at the E2 node (610) in the RIC Actions Admitted List IE in the RIC Subscription Response message. For example, the E2 node (610) may include an unapproved RIC service action in the RIC Actions Not Admitted List IE ('RIC Actions Not Admitted List' IE) with an appropriate cause value. Upon receiving the RIC Subscription Response message, the Near-RT RIC (640) may set a timer (T RICEVENTcreate ) and terminate the RIC subscription process.

[0126] When an E2 node (610) accepts two or more RIC service actions, a RIC service action sequence may be executed according to the following considerations whenever a common event trigger occurs.

[0127] - If the optional RIC Action Execution Order IE is not present, or is present and set to 0 ("any order"), then specific RIC service actions in the RIC service action sequence may be executed in any order, regardless of the execution order of other RIC service actions.

[0128] - If the optional RIC Action Execution Order IE is present and set to a value greater than 0, specific RIC Service Actions may be executed in order according to the RIC Action Execution Order IE.

[0129] - If two or more RIC service actions have the same value for the optional RIC Action Execution Order IE, these RIC service actions may be executed in parallel.

[0130] If an optional RIC subscription start time IE ('RIC Subscription Start Time' IE) is present, the E2 node (610) can activate the event trigger only at the indicated start time. If an optional RIC subscription end time IE ('RIC Subscription End Time' IE) is present, the E2 node (610) can deactivate the event trigger when the indicated end time expires.

[0131] Interaction with the RIC Subscription Delete Required procedure: If an optional RIC Subscription End Time IE exists and the indicated end time has expired, the E2 node (610) may send a RIC Subscription Delete Required message to the Near-RT RIC (640) with an appropriate cause value.

[0132] Interaction with RIC Subscription Delete Procedure: If an optional RIC Subscription End Time IE is present, the Near-RT RIC (640) may initiate the RIC Subscription Delete procedure when the expected RIC Subscription End Time expires.

[0133] For example, a RIC subscription response message may have the following format:

[0134] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Actions Admitted List1.. <maxofricactionid>YESreject>RIC Action IDM9.2.10-RIC Actions Not Admitted List0.. <maxofricactionid>YESreject>RIC Action IDM9.2.10->CauseM9.2.1-

[0135] Range boundExplanationmaxofRICActionIDMaximum no. of Actions to be requested by Near-RT RIC. Value is 16.

[0136] For each IE in [Table 9], reference may be made to the descriptions of the O-RAN WG3.E2AP specification. The maximum values ​​in [Table 10] are exemplary and are not to be construed as limiting the embodiments of the present disclosure.

[0137] Referring to FIG. 11b, in operation (1101), the Near-RT RIC (640) may transmit an RIC subscription request message to the E2 node (610). For the RIC subscription request message, reference may be made to the descriptions of the RIC subscription request message of operation (1101) of FIG. 11a.

[0138] At operation (1105), the Near-RT RIC (640) may receive an RIC subscription failure message from the E2 node (610). The RIC subscription failure message may be used to inform the Near-RT RIC (640) that a request to create a new RIC subscription has failed. If an error occurs during the RIC subscription procedure, the E2 node (610) may send an RIC subscription failure message with an appropriate cause value to the Near-RT RIC (640). If the E2 node (610) does not allow a requested RIC service action or detects an inconsistency in the sequence of RIC service actions or in the definition of an optional RIC Subsequent Action IE, the E2 node (640) may send an RIC subscription failure message with an appropriate cause value to the Near-RT RIC (640). If the RIC subscription procedure includes an invalid optional RIC subscription start time IE and / or RIC subscription end time IE, the E2 node (610) may send a RIC subscription failure message with an appropriate cause value to the Near-RT RIC (640). Upon receiving the RIC subscription failure message, the Near-RT RIC (640) may start a timer (T RICEVENTcreate ) and terminate the RIC subscription process.

[0139] Interaction with the RIC subscription deletion procedure: Timer (T) in Near-RT RIC (640) RICEVENTcreate ) if there is no response from the E2 node (610) to the RIC subscription request message before the expiration of the Near-RT RIC (640), the Near-RT RIC (640) may initiate a RIC subscription deletion procedure including the RIC request ID IE previously assigned by the Near-RT RIC (640) to cancel the RIC subscription for the E2 node (610). The Near-RT RIC (640) may ignore any RIC subscription response or RIC subscription failure message including the RIC request ID IE previously assigned by the Near-RT RIC (640) that is received after the RIC subscription deletion procedure is initiated and release all resources associated with the associated E2.

[0140] If the E2 node (610) receives a RIC subscription request message that includes a RIC Subscription Details IE that does not match the E2 service model (E2SM), the E2 node (610) may transmit a RIC subscription failure message that includes an appropriate cause value to the Near-RT RIC (640). If the E2 node (610) receives a RIC subscription request message that includes an unknown RAN Function ID IE, the E2 node (610) may transmit a RIC subscription failure message that includes an appropriate cause value to the Near-RT RIC (640). If the E2 node (610) receives a RIC subscription request message that includes the same content, the E2 node (610) may transmit a RIC subscription failure message that includes an appropriate cause value to the Near-RT RIC (640).

[0141] For example, a RIC subscription failure message may have the following format:

[0142] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectCauseM9.2.1YESrejectCriticality DiagnosticsO9.2.2YESignore

[0143] For each IE in [Table 11], the descriptions of the O-RAN WG3.E2AP specification can be referenced.

[0144] 3. RIC Instruction Procedure

[0145] Figure 12 illustrates an example of a RIC indication procedure. The purpose of the RIC indication procedure is to convey RIC service actions (e.g., reporting and / or insertion) associated with a RIC subscription procedure. The RIC indication procedure may be initiated by the E2 node. The RIC indication procedure may utilize RIC service signaling.

[0146] Referring to FIG. 12, in operation (1201), the E2 node (610) may transmit an RIC indication message to the Near-RT RIC (640). The E2 node (610) may initiate the RIC indication procedure by transmitting an RIC indication message to the Near-RT RIC (640) that includes an RIC Request ID IE previously assigned by the Near-RT RIC (640) during a successful RIC subscription procedure. If the RIC indication message is a response to a RIC service insertion action, the E2 node (610) may provide an RIC call process ID IE ('RIC Call Process ID' IE) within the RIC indication message. The E2 node (610) may store the current call state and start a timer (e.g., 'RIC Time to Wait'). Thereafter, the E2 node (610) may stop further processing of the relevant RAN function. The Near-RT RIC (640) may use the RIC Call Process ID IE in subsequent RIC control procedures. If the RIC Follow-up Action IE is associated with a RIC Service Action, after the RIC Instruction Message is successfully transmitted, the E2 node (610) may proceed as follows.

[0147] - If the RIC Follow-up Action Type IE is set to 'continue' or 'halt' and the associated timer ('RIC Time To Wait') has not expired and a RIC Control Request message is received with the same RIC Call Process ID IE, the E2 node (610) may use the RIC Control Request information together with the stored call state and continue executing the remaining actions according to the RIC action sequence defined in the RIC subscription procedure before resuming normal functioning of the associated RAN function.

[0148] - If the RIC follow-up action type IE is set to 'Continue' and the timer ('RIC Time To Wait') expires, the E2 node (610) can use the saved call state and continue executing the remaining RIC service actions according to the defined RIC service action sequence.

[0149] - If the RIC follow-up action type IE is set to 'Stop' and the timer ('RIC Time To Wait') expires, the E2 node (610) may stop further processing of the relevant RAN function. In this case, the remaining RIC service actions in the RIC action sequence defined in the RIC subscription procedure may also be stopped. The above-described operations can be summarized in the table below.

[0150] Subsequent ActionRIC Time to Wait timerConditionOutcomeContinue or HaltrequiredE2 Node detected the event trigger in the RIC Event Trigger Definition IE.RIC INDICATION message shall provide the RIC Call Process ID IE and E2 Node shall store current call state, start the associated RIC Time to Wait timer, and suspend further processing of the associated RAN function.Continue or Haltnot yet expiredE2 Node received the RIC CONTROL REQUEST message with the same RIC call process ID IE.E2 Node shall use the RIC CONTROL information along with the stored call state and continue to execute any remaining actions in the sequence of RIC Actions defined in the RIC Subscription procedure.ContinueexpiredE2 Node shall use the stored call state and continue to execute any remaining actions in the sequence of RIC Actions defined in the RIC Subscription procedure.HaltexpiredE2 Node shall abort normal functionality of the associated RAN function.

[0151] For example, the RIC instruction message described above may have the following format:

[0152] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Action IDM9.2.10YESrejectRIC Indication SNO9.2.14YESrejectRIC Indication TypeM9.2.15YESrejectRIC Indication HeaderM9.2.17YESrejectRIC Indication MessageM9.2.16YESrejectRIC Call process IDO9.2.18YESreject

[0153] For each IE in [Table 13], the descriptions of the O-RAN WG3.E2AP specification can be referenced. In the RIC indication message in [Table 13], the RIC indication Header and RIC indication message can refer to the E2 service model associated with the RAN function.

[0154] 4. RIC control procedure

[0155] Figures 13a and 13b illustrate examples of RIC control procedures. The purpose of an RIC control procedure is to initiate or resume a specific functionality in an E2 node. The RIC control procedure can be initiated by a Near-RT RIC. The RIC control procedure can utilize RIC service signaling.

[0156] Referring to FIG. 13A, in operation (1301), the Near-RT RIC (640) may transmit an RIC control request message to the E2 node (610). The RIC control request message may be used to initiate or resume control function logic. The Near-RT RIC (640) may initiate the RIC control procedure by transmitting an RIC control request message including a unique RIC request ID IE assigned by the Near-RT RIC (640). When the Near-RT RIC (640) sends the RIC control request message and the optional RIC control acknowledge request IE ('RIC Control Ack Request' IE) is set to "Ack" or absent, the Near-RT RIC (640) may start a timer (T RICcontrol ) can be initiated. For example, the RIC control request message may have the following format:

[0157] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Call Process IDO9.2.18YESrejectRIC Control HeaderM9.2.20YESrejectRIC Control MessageM9.2.19YESrejectRIC Control Ack RequestO9.2.21YESreject

[0158] For each IE in [Table 14], the descriptions of the O-RAN WG3.E2AP specification may be referenced. In [Table 14], the E2 service model associated with the 'RIC Control Header' IE and the 'RIC Control message is a RAN function' IE may be referenced. According to one embodiment, the RIC control request message for access barring may include the 'RIC Control Header' IE corresponding to the 'E2SM-RC Control Header Format 1' of [Table 30] described below.

[0159] In operation (1303), the Near-RT RIC (640) may receive an RIC control confirmation message from the E2 node (610). After receiving the RIC control request message, the E2 node (610) may perform the following:

[0160] - Determine the target RAN function using the information in the RAN Function ID IE and initiate the requested RIC control procedure action using the information in the RIC Control Message IE ('RIC Control Message' IE).

[0161] - If the RIC Call Process ID IE is included in the RIC Control REQUEST message, the E2 node (610) can use the IE to identify a specific call process indicated in the RIC instruction message.

[0162] - If the RIC Control Request message contains an optional RIC Control Ack Request IE set to “Ack” or if the optional RIC Control Ack Request IE is not present and the E2 node (610) successfully processed the requested RIC Control procedure operation, the E2 node (610) may respond with a RIC Control Acknowledge message.

[0163] - If the RIC Control Request message includes an optional RIC Control Ack Request IE set to "NoAck" and the E2 node (610) successfully processes the requested RIC control procedure operation, the E2 node (610) may not send a RIC Control Acknowledge message. In this case, operation (1303) may be omitted.

[0164] Upon receiving the RIC control acknowledge message, the Near-RT RIC (640) initiates a timer (T RICcontrol ) and terminate the RIC control procedure. The Near-RT RIC (640) may use the information contained in the optional RIC Control Outcome IE ('RIC Control Outcome' IE) to determine subsequent actions. For example, the RIC Control Confirmation message may have the following format.

[0165] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Call process IDO9.2.18YESrejectRIC Control OutcomeO9.2.25YESreject

[0166] For each IE in [Table 15], the descriptions of the O-RAN WG3.E2AP specification can be referenced.

[0167] Referring to FIG. 13b, in operation (1301), the Near-RT RIC (640) (640) may transmit an RIC control request message to the E2 node (610). For the RIC control request message, reference may be made to the descriptions of the RIC control request message of operation (1301) of FIG. 13a.

[0168] At operation (1305), the Near-RT RIC (640) (640) may receive an RIC control failure message from the E2 node (610). For example, if the RIC control request message includes an invalid RIC Call Process ID IE, the E2 node (610) may respond with an RIC control failure message with an appropriate cause value. For example, if the RIC control request message includes an optional RIC call process ID IE whose timer ('RIC Time To Wait') has expired, the E2 node (610) may respond with an RIC control failure message with an appropriate cause value. For example, if the E2 node (610) fails to execute a requested RIC control procedure E2SM specific task, the E2 node (610) may respond with an RIC control failure message with an appropriate cause value. For example, if the E2 node (610) detects an encoding or functionality error in an E2SM specific IE included in a RIC control request message, the E2 node (610) may respond with a RIC control failure message with an appropriate cause value. For example, if the E2 node (610) receives a RIC control request message with an unknown RAN Function ID IE, the E2 node (610) may respond with a RIC control failure message with an appropriate cause value. For example, if the E2 node (610) does not support a specific RIC control procedure operation, the E2 node (610) may respond with a RIC control failure message with an appropriate cause value. Upon receiving a RIC control failure message, the Near-RT RIC (640) may stop the timer T(RICcontrol) if running and terminate the RIC control procedure. The Near-RT RIC (640) can use information contained in the 'Cause' IE and the optional 'RIC Control Outcome' IE to determine subsequent actions.For example, a RIC control failure message may have the following format:

[0169] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.2.3YESrejectRIC Request IDM9.2.7YESrejectRAN Function IDM9.2.8YESrejectRIC Call process IDO9.2.18YESrejectCauseM9.2.1YESignoreRIC Control OutcomeO9.2.25YESRejectCriticality DiagnosticsO9.2.2YESignore

[0170] For each IE in [Table 16], the descriptions of the O-RAN WG3.E2AP specification can be referenced.

[0171] Upon receiving an ERROR INDICATION message containing a RIC Request ID IE associated with a RIC Control Request message, the Near-RT RIC (640) initiates a timer (T RICcontrol ) is running, the timer can be stopped and the RIC control procedure can be terminated. When sending a RIC control request message, the timer (T RICcontrol ) is set and there is no response from the E2 node (610) before the timer expires, the Near-RT RIC (640) may transmit an error indication message with an appropriate value for the Cause IE.

[0172] The E2 node (610) can operate according to the subscribed (subscribed) service through the RIC subscription procedure. For example, if the RIC subscription subscribed by the request of the Near-RT RIC (640) is the transmission of an RIC indication message, the E2 node (610) can transmit the RIC indication message from the Near-RT RIC (640). At this time, the RAN Function ID is transmitted through the E2 setup procedure and / or the RIC subscription procedure, and the E2 node (610) can know the E2 service model of the currently subscribed service through the OID associated with the RAN Function ID. For example, information included in the 'RIC Indication Header' and the 'RIC Indication message' in the RIC self-message may be specific to the E2 service model. For example, if the RIC subscription subscribed to by the request of the Near-RT RIC (640) is an RIC control procedure, the Near-RT RIC (640) may transmit an RIC control request message to the E2 node (610). At this time, the RAN Function ID is transmitted through the E2 setup procedure and / or the RIC subscription procedure, and the E2 node (610) may know the E2 service model of the currently subscribed service through the OID associated with the RAN Function ID. Depending on the E2 service model, the format of the RIC control request message in the RIC control procedure or the format of the RIC instruction message in the RIC instruction procedure may vary. For example, information included in the 'RIC Control Header' and the 'RIC Control message' in the RIC control request message may be specific to the E2 service model.

[0173] I. RAN Parameters for Access Barring

[0174] Hereinafter, embodiments of the present disclosure describe the access barring function within the E2SM-RC service model. E2SM-RC can have a service style list depending on whether the service style is report, insert, control, policy, or query, and as an example, the type of control service style is described. The RIC control procedure according to embodiments of the present disclosure can be used for access barring in the E2SM-RC service model. In 5G networks, cell access barring is a mechanism that operators use to regulate and manage network traffic by restricting access to specific cells based on criteria such as device type, service type, and time. The access barring can be useful for managing congestion during peak usage periods or in areas with high traffic volume.

[0175] The exact implementation of access barring may vary across operators due to the use of various standards and technologies, but parameters can be determined according to 3GPP specifications. Access barring can be implemented via unified access control (UAC) or enhanced access barring (EAB). Access barring can provide operators with a means to optimize network management by selectively allowing access to specific cells for specific devices and services. Furthermore, parameter(s) related to access barring are broadcast via the master information block (MIB) and system information block type 1 (SIB1), and each user equipment (UE) can be assigned an access ID and category. These parameter(s) allow the operator to fine-tune cell access. Assume that an E2 node (610) subscribes to a Near-RT RIC (640) and an energy-saving service. Access barring can be utilized for this energy-saving. Meanwhile, if the E2SM-RC standard does not include sufficient parameters for access barring, it may be difficult for the Near-RT RIC (640) to effectively control the E2 node (610) through the RIC control request message.

[0176] Access barring in E2SM-RC can be referenced as follows. For example, Section 7.6.1 of E2SM-RC may specify a radio access control function known as "RIC Style Type 4." This function may be used as a means to modify radio access-related functions used to regulate user equipment access to a cell. Currently defined control service types may be referenced as follows.

[0177] RIC Style TypeStyle NameStyle Description1Radio Bearer controlUsed to modify the configuration the Radio Bearer Control (RBC) related parameters and / or behaviours at the E2 Node for a specific UE or a UE group.Belongs to Fundamental level CONTROL Services.2Radio resource allocation controlUsed to modify the configuration the Radio Resource Allocation control related parameters and / or behaviours at the E2 Node for a specific E2 Node, cell, slice, UE and / or QoSBelongs to Fundamental level CONTROL Services.3Connected mode mobility controlUsed to initiate a connected mode mobility procedure (Handover or Conditional Handover), optionally with Dual Active Protocol Stack (DAPS), for a specific UE towards either a target cell (for HO) or a list of candidate cells (for CHO)Belongs to Fundamental level CONTROL Services.4Radio access controlUsed to modify Radio access related functions used to control UE access to cellsBelongs to Fundamental level CONTROL Services.5Dual connectivity (DC) controlUsed to initiate Dual connectivity (DC) mechanismsBelongs to Fundamental level CONTROL Services.6Carrier Aggregation (CA) controlUsed to initiate Carrier Aggregation (CA) mechanismsBelongs to Fundamental level CONTROL Services.7Idle mode mobility controlUsed to modify Idle mode mobility related functions used to control UE reselection of cellsBelongs to Fundamental level CONTROL Services.8UE information and assignmentUsed forExplicit UE listassignment, UE information report generation and to complete UE identification. These services are used to support other RIC services.Belongs to Fundamental level CONTROL Services.9Measurement Reporting Configuration controlUsed to control the measurement report configuration for a given UE or a group of UEs.10Beamforming Configuration controlUsed to control beamforming configuration for a specific UE.255Multiple Actions ControlUsed for multiple actions of the selected fundamental level CONTROL Service style(s).Belongs to integrated level CONTROL Services.

[0178] When the style type is specified as '4', the application may include random access channel (RACH) backoff, radio resource control (RRC) connection rejection, RRC connection release, UE admission and access barring. The control service style with the style type specified as '4' may provide a mechanism to start or resume radio access control related processes using the RIC Control Message IE, the related RIC Control Header IE and an optional RIC Call Process ID IE used when resuming a call process after a previous INSERT service. The INSERT service is service style 4 covered in section 7.5.5 of the E2SM-RC specification. When the style type is specified as '4', the control action for access barring may be determined as follows. In one embodiment, the control action ID may be set to '3'.

[0179] ControlActionIDControl Action NameControl Action DescriptionAssociated RAN Parameters1UE Admission ControlTo control UE admission.8.4.5.12RACH backoff controlTo control RACH backoff parameters8.4.5.23Access barring controlTo control access barring configuration parameters8.4.5.34RRC Connection Release controlTo control release of RRC connection of the UE8.4.5.45RRC Connection Reject controlTo reject RRC connection request of the UE8.4.5.5

[0180] The RIC Control Message ('RIC Control Message' IE) may include one or more RAN parameters related to the service. The RAN parameters may depend on the RIC Style Type and the Control Action ID. For example, when RAN parameters related to access barring are included in the RIC Control Request message, the RIC Style Type may be set to '4' and the Control Action ID may be set to '3'. As an example, the RIC Control Message ('RIC Control Message' IE) may use the following format.

[0181] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionList of RAN parameters0.. <maxnoofassociatedranparameters>>RAN Parameter IDM9.3.8Refer to table in clause 8.4 for applicable RAN Parameters>RAN Parameter DefinitionO9.3.51Refer to clause 7.6.9 for usage of this IE.

[0182] RangeboundExplanationmaxnoofAssociatedRANParametersMaximum no. of RAN parameters supported by RAN Function for a specific Control action. The value is <65535> .

[0183] For each IE in [Table 19], reference may be made to the descriptions of the O-RAN WG3.E2AP specification. The maximum values ​​in [Table 20] are exemplary and are not to be construed as limiting the embodiments of the present disclosure.

[0184] The E2 node (610) that receives the RIC control request message in operation (1301) may invoke procedures related to access barring control, such as UE context management (or MIB forwarding, SIB1 forwarding), RRC message transmission, etc., and may include an IE corresponding to one or more parameters in the related interface message. Hereinafter, RAN parameters related to the aforementioned access barring control are described.

[0185] The UAC mechanism is responsible for limiting the number of call requests received from UEs based on their access ID and access category. An E2 node (e.g., gNB) can broadcast UAC Radio Resource Control (RRC) information via System Information Block 1 (SIB1), as shown in the table below.

[0186]

[0187] The Near-RT RIC (640) can set relevant parameters related to UAC to the E2 node (610) (e.g., gNB) via an RIC control request message according to E2SM-RC. UAC has minimal or no impact on UE context management or RRC message transmission.

[0188] Access barring control for E2SM-RC is to specify parameters for access barring control defined in 3GPP. The parameters can be included in a message (e.g., RIC control request message) transmitted by the Near-RT RIC (640) and transmitted to the E2 node (610). As RAN parameters for access barring, in addition to UAC-related parameters, it may be required to specify access parameters specified in MIB or SIB1. According to one embodiment, the RAN parameters for access barring control may include parameter(s) included in a MIB message. The table below shows the MIB message. The MIB is a parameter used for cell access barring and can be used to convey the 'cellBarred' and 'intraFreqReselection' IEs.

[0189]

[0190] The parameters defined in the MIB in [Table 22] can be referenced as follows.

[0191] 1) 'cellBarred' IE (value: "barred" or "notBarred")

[0192] A barred value indicates that the cell is barred as defined in 3GPP TS 38.304. For example, a barred cell may be difficult for a UE (User Equipment) to access. In other words, access to a cell where the IE is set to 'barred' may be blocked. If the IE indicates that the cell is barred, the UE may not be allowed to camp on the cell. This field is ignored in the integrated access backhaul (IAB)-MT (mobile terminal) and the network-controlled repeater (NCR)-MT. This field is ignored when connecting to an NTN or air-to-ground (ATG). This field is indicated in the MIB message, and in the case of multiple public land mobile networks (PLMNs) or non-public networks (NPNs) indicated in SIB1, this field is common to all PLMNs and / or NPNs.

[0193] 2) 'intraFreqReselection' IE (value: "allowed" or "notAllowed")

[0194] The above field controls cell selection / reselection for an intra-frequency cell when the highest priority cell is prohibited or treated as prohibited by the UE as specified in 3GPP TS 38.304. For example, assume that the above value is set to 'Allowed'. If the highest priority cell among one or more cells is prohibited (i.e., the UE is prohibited from accessing (or camping on) that cell), the UE may perform cell selection / cell reselection to an intra-frequency cell (e.g., a different cell with the same carrier frequency as the above cell) for that cell. Assume that the above value is set to 'Not Allowed'. If a cell with the highest priority among one or more cells is prohibited (i.e., the UE is prohibited from accessing (or camping on) that cell), the UE may not be allowed to perform cell selection / cell reselection to an intra-frequency cell (e.g., a cell having the same carrier frequency as the cell but a different cell) for that cell. For example, the UE may perform cell selection / cell reselection to an inter-frequency cell (e.g., a cell having a different carrier frequency from the cell). This field is ignored in IAB-MT and NCR-MT.

[0195] In one embodiment, the RAN parameters for access barring control may include parameter(s) included in a SIB 1 message. The table below shows the 'CellAccessRelatedInfo' IE included in the SIB 1 message.

[0196]

[0197] The table below details the 'plmn-IdentityInfoList' IE.

[0198]

[0199] The parameters for access barring defined in SIB1 through [Table 23] and [Table 24] can be referenced as follows.

[0200] 1) cellReservedForOperatorUse(IE type: "Reserved" or "Unreserved")

[0201] The above value may indicate whether the cell is reserved for operator use. A reserved cell is a cell where camping is not allowed except for specific UEs specified in the system information. For example, if the IE is 'reserved', UEs may not be allowed to access the cell (i.e., camping on the cell may not be allowed) except for UEs specified in the system information. This field is indicated in the SIB1 message, and in the case of multiple PLMNs or NPNs indicated in SIB1, this field may be specified for each PLMN or standalone non-public network (SNPN).

[0202] 2) cellReservedForOtherUse(IE type: "true")

[0203] The above value may indicate whether the cell is reserved. A reserved cell is a cell where camping is not allowed except for specific UEs specified in the system information. For example, if the IE is 'reserved', UEs may not be allowed to access the cell (i.e., camping on the cell may not be allowed) except for UEs specified in the system information. It is indicated in the SIB1 message, and if there are multiple PLMNs indicated in SIB1, the above field is common to all PLMNs.

[0204] 3) cellReservedForFutureUse(IE type: "true")

[0205] The above value may indicate whether the cell is reserved for future use. A reserved cell is a cell on which camping is not allowed except for specific UEs specified in the system information. For example, if the IE is 'reserved', UEs may not be allowed to access the cell (i.e., camp on the cell) except for UEs specified in the system information. It is indicated in the SIB1 message, and in the case of multiple PLMNs or NPNs indicated in SIB1, the above field is common to all PLMNs and NPNs.

[0206] The RAN parameters currently defined in the E2SM-RC specification for access barring are as follows. Here, the RIC style type can be '4' and the control action ID can be '3'.

[0207] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics Description1Unified Access Control Barring InfoSTRUCTUREuac-BarringInfoIE in TS 38.331

[0022] Sec 62>UAC Barring for Common ListLISTuac-BarringForCommonIE in TS 38.331

[0022] Sec 63>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 64>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 65>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 66>UAC Barring for PLMN ListLISTuac-BarringPerPLMN-ListIE in TS 38.331

[0022] Clause 67>>UAC-BarringPerPLMNSTRUCTUREUAC-BarringPerPLMNIE in TS 38.331

[0022] Sec 68>>>PLMN Identity IndexELEMENTTRUEplmn-IdentityIndexIE in TS 38.331

[0022] Sec 69>>>CHOICE UAC AC Barring List TypeSTRUCTUREUac-ACBarringListTypeIE in TS 38.331

[0022] Sec 610>>>>UAC Implicit AC Barring ListLISTuac-ImplicitACBarringListIE in TS 38.331

[0022] Clause 611>>>>>UAC Implicit AC Barring ItemSTRUCTURE12>>>>>>UAC Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Sec 613>>>>UAC Explicit AC Barring ListLISTuac-ExplicitACBarringListIE in TS 38.331

[0022] Clause 614>>>>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 615>>>>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 616>>>>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 617>UAC Barring Info Set ListLISTUAC-BarringInfoSetListIE in TS 38.331

[0022] Sec 618>>UAC Barring Info Set ItemSTRUCTUREUAC-BarringInfoSetIE in TS 38.331

[0022] Clause 619>>>UAC Barring FactorELEMENTFALSEuac-BarringFactorIE in TS 38.331

[0022] Sec 620>>>UAC Barring TimeELEMENTFALSEuac-BarringTimeIE in TS 38.331

[0022] Sec 621>>>UAC Barring For Access IdentityELEMENTFALSEuac-BarringForAccessIdentityin TS 38.331

[0022] Clause 622>CHOICE Access Category 1 - Selection Assistance InfoSTRUCTUREuac-AccessCategory1-SelectionAssistanceInfoIE in TS 38.331

[0022] Sec 623>>PLMN CommonELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 624>>Individual PLMN ListLISTindividualPLMNListIE in TS 38.331

[0022] Clause 625>>>PLMN ItemSTRUCTURE26>>>>UAC Access Category 1 Selection Assistance InfoELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 6.

[0208] According to embodiments of the present disclosure, the RAN parameters defined in the current E2SM-RC specification for access barring may include the following parameters in addition to the parameters in [Table 25]. According to one embodiment, the RAN parameters for access barring may include at least one parameter included in a MIB message of 3GPP. For the at least one parameter included in the MIB message of 3GPP, the table below may be referred to. As an example, the value of X may be 36. For each parameter, 3GPP TS 38.331 may be referred to.

[0209] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics Description This field is ignored by IAB-MT. This field is ignored for connectivity to NTN. This field is ignored by IAB-MT.

[0210] In one embodiment, the RAN parameters for the access barring may include at least one parameter included in a 3GPP SIB1 message. For the at least one parameter included in the 3GPP SIB1 message, the table below may be referenced. For each parameter, 3GPP TS 38.331 may be referenced.

[0211] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics DescriptionYcellAccessRelatedInfoSTRUCTURECellAccessRelatedInfoIE in TS 38.331

[0022] Sec 6Y+1> cellReservedForOperatorUse-per-PLMN-config-ListLISTY+2>> cellReservedForOperatorUse-per-PLMN-config-ItemSTRUCTUREY+3>>> PLMN Identity IndexELEMENTTRUEplmn-IdentityIndex IE in TS 38.331

[0022] Sec 6Y+4>>> cellReservedForOperatorUseELEMENTFALSEcellReservedForOperatorUseIE in TS 38.331

[0022] Sec 6Indicates whether the cell is reserved for operator use (per PLMN), as defined in TS 38.304

[0020] . This field is ignored by IAB-MT.Y+5> cellReservedForOtherUseELEMENTFALSEcellReservedForOtherUseIE in TS 38.331

[0022] Sec 6Indicates whether the cell is reserved, as defined in 38.304

[0020] . The field is applicable to all PLMNs. This field is ignored by IAB-MT for cell barring determination, but still considered by NPN capable IAB-MT for determination of an NPN-only cell.

[0212] According to one embodiment, the Near-RT RIC (640) may transmit an RIC control request message to the E2 node (610) that includes at least some of the parameters for access barring in [Table 26] or [Table 27]. For example, the RAN parameters for access barring may be defined as follows.

[0213] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics Description1Unified Access Control Barring InfoSTRUCTUREuac-BarringInfoIE in TS 38.331

[0022] Sec 62>UAC Barring for Common ListLISTuac-BarringForCommonIE in TS 38.331

[0022] Sec 63>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 64>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 65>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 66>UAC Barring for PLMN ListLISTuac-BarringPerPLMN-ListIE in TS 38.331

[0022] Clause 67>>UAC-BarringPerPLMNSTRUCTUREUAC-BarringPerPLMNIE in TS 38.331

[0022] Sec 68>>>PLMN IdentityELEMENTTRUE9.3.599>>>CHOICE UAC AC Barring List TypeSTRUCTUREUac-ACBarringListTypeIE in TS 38.331

[0022] Sec 610>>>>UAC Implicit AC Barring ListLISTuac-ImplicitACBarringListIE in TS 38.331

[0022] Clause 611>>>>>UAC Implicit AC Barring ItemSTRUCTURE12>>>>>>UAC Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Sec 613>>>>UAC Explicit AC Barring ListLISTuac-ExplicitACBarringListIE in TS 38.331

[0022] Clause 614>>>>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 615>>>>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 616>>>>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 617>UAC Barring Info Set ListLISTUAC-BarringInfoSetListIE in TS 38.331

[0022] Sec 618>>UAC Barring Info Set ItemSTRUCTUREUAC-BarringInfoSetIE in TS 38.331

[0022] Clause 619>>>UAC Barring FactorELEMENTFALSEuac-BarringFactorIE in TS 38.331

[0022] Sec 620>>>UAC Barring TimeELEMENTFALSEuac-BarringTimeIE in TS 38.331

[0022] Sec 621>>>UAC Barring For Access IdentityELEMENTFALSEuac-BarringForAccessIdentityin TS 38.331

[0022] Clause 622>CHOICE Access Category 1 - Selection Assistance InfoSTRUCTUREuac-AccessCategory1-SelectionAssistanceInfoIE in TS 38.331

[0022] Sec 623>>PLMN CommonELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 624>>Individual PLMN ListLISTindividualPLMNListIE in TS 38.331

[0022] Clause 625>>>PLMN ItemSTRUCTURE26>>>>UAC Access Category 1 Selection Assistance InfoELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 627Cell Access Control Barring InfoSTRUCTURE28> List of Control plmn-IdentityLIST29>> plmn-IdentityELEMENT9.3.5930>>List of Control cellsLIST31>>>CHOICE Cell TypeSTRUCTURE32>>>>NR CellSTRUCTURE8.1.1.1NR IE in TS 38.423

[0015] Clause 9.2.3.2533>>>>>NR CGIELEMENTNR CGI IE in TS 38.423

[0015] Clause 9.2.2.7Cell Corresponding to same PLMN34>>>>E-UTRA CellSTRUCTURE8.1.1.2E-UTRA IE in TS 38.423

[0015] Clause 9.2.3.2535>>>>>EUTAN CGIELEMENTE-UTRA CGI IE in TS 38.423

[0015] Clause 9.2.2.836>>> cellBarredELEMENTIndicated in the MIB message, applicable to all PLMNs when multiple PLMNs are in SIB1. When set to 'barred', the cell is barred for all UEs including emergency calls. Please refer to TS 38.331

[0022] .37>>> intraFreqReselectionELEMENTIndicated in MIB message. It controls cell selection / reselection to intra-frequency cells when the highest-ranked cell is barred or treated as barred by the UE. In the case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs. Please refer to TS 38.331

[0022] .38>> cellReservedForOperatorUseELEMENTIndicated in SIB1 message, per-PLMN configuration. When set to 'reserved', the cell is treated as a candidate by the UE with access identity (i.e.) 11 and 15 operating in their HPLMN / EHPLMN. UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" for the registered PLMN or the selected PLMN. Please refer to TS 38.331

[0022] .39>> cellReservedForOtherUseIndicated in SIB1 message, applicable to all PLMNs indicated in SIB1. Please refer to TS 38.331

[0022] .

[0214] For example, 'cellBarred' corresponding to the RAN parameter ID of 36 in [Table 28] may correspond to 'cellBarred' in [Table 26]. The Near-RT RIC (640) may transmit an RIC control request message for access barring (e.g., an RIC control request message in which the RIC style type is set to '4' (Radio access control) and the control action ID is set to '3' (Access barring control)) to the E2 node (610). The RIC control request message may include 'cellBarred'. 'cellBarred' may indicate whether the corresponding cell is barred.

[0215] For example, 'cellBarred' corresponding to RAN parameter ID 37 in [Table 28] may correspond to 'intraFreqReselection' in [Table 26]. The Near-RT RIC (640) may transmit an RIC control request message for access barring (e.g., an RIC control request message in which the RIC style type is set to '4' (Radio access control) and the control action ID is set to '3' (Access barring control)) to the E2 node (610). The RIC control request message may include 'intraFreqReselection'. 'intraFreqReselection' may indicate whether the corresponding cell is barred. If the highest-ranked cell is barred, it may indicate whether cell selection and / or cell reselection for an intra-frequency cell is allowed.

[0216] For example, in [Table 28], the corresponding 'cellReservedForOperatorUse' when the RAN parameter ID is 38 may correspond to 'cellReservedForOperatorUse' in [Table 27]. The Near-RT RIC (640) may transmit an RIC control request message for access barring (e.g., an RIC control request message in which the RIC style type is set to '4' (Radio access control) and the control action ID is set to '3' (Access barring control)) to the E2 node (610). The RIC control request message may include 'cellReservedForOperatorUse'. 'cellReservedForOperatorUse' may indicate whether the corresponding cell is reserved for operator use.

[0217] For example, 'cellReservedForOtherUse' corresponding to the RAN parameter ID of 39 in [Table 28] may correspond to 'cellReservedForOtherUse' in [Table 27]. The Near-RT RIC (640) may transmit an RIC control request message for access barring (e.g., an RIC control request message in which the RIC style type is set to '4' (Radio access control) and the control action ID is set to '3' (Access barring control)) to the E2 node (610). The RIC control request message may include 'cellReservedForOtherUse'. 'cellReservedForOtherUse' may indicate whether the corresponding cell is reserved for all PLMNs.

[0218] In addition to the parameters described above, access barring-related parameters recently introduced for network energy saving can also be specified as RAN parameters. For example, SIB1 of release 18 can include 'cellBarredNES-r18'. A terminal supporting energy saving (hereinafter, energy saving terminal) can continue to perform an access procedure for the corresponding cell even if the "cellBarred" IE of the MIB is set to the 'barred' value. When the energy saving terminal obtains 'cellBarredNES-r18' from SIB1, it can perform an access procedure for the cell. However, if the energy saving terminal does not receive 'cellBarredNES-r18' from SIB1 (e.g., 'cellBarredNES-r18' is absent in SIB1), the energy saving terminal can identify that the cell is barred. The energy-saving terminal can perform cell re-selection to other cells having the same frequency as the cell. 'cellBarredNES-r18' is indicated in the SIB1 message, and in case of multiple public land mobile networks (PLMNs) or non-public networks (NPNs) indicated in SIB1, this field is common to all PLMNs and / or NPNs. The IE can be applied only to UEs capable of NES cell DTX / RTX. In other words, 'cellBarredNES-r18' indicates a cell-barred state for UEs supporting 'nes-CellDTX-DRX'. For example, RAN parameters for access barring can be defined as follows.

[0219] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics Description1Unified Access Control Barring InfoSTRUCTUREuac-BarringInfoIE in TS 38.331

[0022] Sec 62>UAC Barring for Common ListLISTuac-BarringForCommonIE in TS 38.331

[0022] Sec 63>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 64>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 65>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 66>UAC Barring for PLMN ListLISTuac-BarringPerPLMN-ListIE in TS 38.331

[0022] Clause 67>>UAC-BarringPerPLMNSTRUCTUREUAC-BarringPerPLMNIE in TS 38.331

[0022] Sec 68>>>PLMN IdentityELEMENTTRUE9.3.599>>>CHOICE UAC AC Barring List TypeSTRUCTUREUac-ACBarringListTypeIE in TS 38.331

[0022] Sec 610>>>>UAC Implicit AC Barring ListLISTuac-ImplicitACBarringListIE in TS 38.331

[0022] Clause 611>>>>>UAC Implicit AC Barring ItemSTRUCTURE12>>>>>>UAC Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Sec 613>>>>UAC Explicit AC Barring ListLISTuac-ExplicitACBarringListIE in TS 38.331

[0022] Clause 614>>>>>Barring Per CatSTRUCTUREUAC-BarringPerCatIE in TS 38.331

[0022] Clause 615>>>>>>Access CategoryELEMENTFALSEaccessCategoryIE in TS 38.331

[0022] Sec 616>>>>>>Barring Info Set IndexELEMENTFALSEUAC-BarringInfoSetIndexIE in TS 38.331

[0022] Clause 617>UAC Barring Info Set ListLISTUAC-BarringInfoSetListIE in TS 38.331

[0022] Sec 618>>UAC Barring Info Set ItemSTRUCTUREUAC-BarringInfoSetIE in TS 38.331

[0022] Clause 619>>>UAC Barring FactorELEMENTFALSEuac-BarringFactorIE in TS 38.331

[0022] Sec 620>>>UAC Barring TimeELEMENTFALSEuac-BarringTimeIE in TS 38.331

[0022] Sec 621>>>UAC Barring For Access IdentityELEMENTFALSEuac-BarringForAccessIdentityin TS 38.331

[0022] Clause 622>CHOICE Access Category 1 - Selection Assistance InfoSTRUCTUREuac-AccessCategory1-SelectionAssistanceInfoIE in TS 38.331

[0022] Sec 623>>PLMN CommonELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 624>>Individual PLMN ListLISTindividualPLMNListIE in TS 38.331

[0022] Clause 625>>>PLMN ItemSTRUCTURE26>>>>UAC Access Category 1 Selection Assistance InfoELEMENTFALSEUAC-AccessCategory1-SelectAssistanceInfoIE in TS 38.331

[0022] Clause 627Cell Access Control Barring InfoSTRUCTURE28> List of Control plmn-IdentityLIST29>> plmn-IdentityELEMENT9.3.5930>>List of Control cellsLIST31>>>CHOICE Cell TypeSTRUCTURE32>>>>NR CellSTRUCTURE8.1.1.1NR IE in TS 38.423

[0015] Clause 9.2.3.2533>>>>>NR CGIELEMENTNR CGI IE in TS 38.423

[0015] Clause 9.2.2.7Cell Corresponding to same PLMN34>>>>E-UTRA CellSTRUCTURE8.1.1.2E-UTRA IE in TS 38.423

[0015] Clause 9.2.3.2535>>>>>EUTAN CGIELEMENTE-UTRA CGI IE in TS 38.423

[0015] Clause 9.2.2.836>>> cellBarredELEMENTIndicated in the MIB message, applicable to all PLMNs when multiple PLMNs are in SIB1. When set to 'barred', the cell is barred for all UEs including emergency calls. Please refer to TS 38.331

[0022] .37>>> intraFreqReselectionELEMENTIndicated in MIB message. It controls cell selection / reselection to intra-frequency cells when the highest-ranked cell is barred or treated as barred by the UE. In the case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs. Please refer to TS 38.331

[0022] .38>> cellReservedForOperatorUseELEMENTIndicated in SIB1 message, per-PLMN configuration. When set to 'reserved', the cell is treated as a candidate by the UE with access identity (i.e.) 11 and 15 operating in their HPLMN / EHPLMN. UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" for the registered PLMN or the selected PLMN. Please refer to TS 38.331

[0022] .39>> cellReservedForOtherUseIndicated in SIB1 message, applicable to all PLMNs indicated in SIB1. Please refer to TS 38.331

[0022] .40>> cellBarredNES-r18The presence of this field indicates that the cell is allowed for UEs supporting NES cell DTX / DRX. Please refer to TS 38.331

[0022] .

[0220] In the present disclosure, an example is described in which the parameters are included in the RIC control request message of the RIC control procedure in the E2 service model corresponding to RAN Control, but the embodiments of the present disclosure are not limited thereto. If parameters related to access boring (e.g., at least some of the parameters in Table X, at least some of the parameters in Table Y) are transmitted on the E2 interface, it can be understood as an embodiment of the present disclosure.

[0221] II. Control Header Format

[0222] The control header format (e.g., 'RIC Control Header' IE) of the above RIC control request message may be one of various formats. The RIC control header IE ('RIC Control Header' IE) of the RIC control request message may use a specified format. For example, examples of the above formats are as follows.

[0223]

[0224] According to one embodiment, the RIC control request message for access barring may include the 'RIC Control Header' IE corresponding to the 'E2SM-RC Control Header Format 1' of [Table 30] described below. On the other hand, if the UE ID is mandatory, the access barring performed on a cell-by-cell basis requires parameters to be provided on a UE-by-UE basis, which may be detrimental to signaling. In the 'E2SM-RC Control Header Format 3', since the UE Group ID is mandatory in the header, it may be unsuitable for access barring performed on a cell-by-cell basis. Considering that all parameters related to access barring described in the present disclosure are included in MIB and SIB 1 and are cell-specific, the UE ID may be unnecessary. According to one embodiment, the 'E2SM-RC Control Header Format 2' of [Table 30] may be used as the RIC control request message header format for access barring. This avoids the 'mandatory' constraints related to the UE ID or UE Group ID included in the control header.

[0225] The RAN parameters for access barring described in [Table 26], [Table 27], [Table 28], and [Table 29] are cell-specific. In one embodiment, the RIC control request message may include cell information (e.g., cell identification information, cell ID, physical cell identity (PCI), cell global identity (CGI)). Referring to [Table 30], since the control header format including the current cell ID is not defined, the cell ID may be included in the form of a RAN parameter. In other words, since the access barring parameter(s) of the MIB and SIB1 must be defined for each cell in the body of the control message (e.g., RIC Control Message IE), the cell information (e.g., cell identification information, cell ID, CGI, PCI) may be supported in the form of a RAN parameter. For example, the following RAN parameters may be defined for access barring.

[0226] RAN Parameter IDRAN ParameterRAN Parameter Value TypeKey ParamRAN Parameter DefinitionSemantics DescriptionZTarget Cell IDSTRUCTUREThis is for the target cell for access control. The structuring of this parameter is based onTarget Cell Global IDIE in TS 38.423

[0015] clause 9.2.3.25

[0227] For example, the target cell ID ('Target Cell ID') of [Table 31] may be a cell subject to access control and may be in the form of a CGI. For example, the target cell DI may include an NR CGI. As another example, the CGI may include an E-UTRA CGI. According to an embodiment, the target cell ID may be included in a control request message (e.g., an RIC Control Request message) together with at least one of the RAN parameters (e.g., cellBarred, intraFreqReselection in MIB, cellReservedForOperatorUse-per-PLMN-config-List, cellReservedForOtherUse in SIB1) of [Table 26] and / or [Table 27].

[0228] In one embodiment, the RIC control request message may utilize a new control header format instead of the existing control header format. For example, the table below may be referenced for the new control header format.

[0229]

[0230] For example, the table below may be referenced for the new control header format.

[0231]

[0232] At least one of the control header formats described above can be used for at least one of the RAN parameter(s) described in the present disclosure (e.g., at least one of the parameters μ of [Table 26], [Table 27], [Table 28], [Table 29]). That is, the descriptions regarding the control header format are compatible with the 'RIC Control Header' IE in the RIC control request message, and the descriptions regarding the RAN parameters for access barring are compatible with the 'RIC Control Message' IE. For example, a RIC control request message having a 'RIC Control Header' IE including a target cell ID and a 'RIC Control Message' IE including 'cellBarred' of the MIB can be understood as an embodiment of the present disclosure.

[0233] Figure 14 shows an example of a wireless access network.

[0234] Referring to FIG. 14, FIG. 14 illustrates a base station (1410) (e.g., base station (110) of FIG. 1, base station (203) of FIG. 2) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 14 illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (1410). For example, the base station (1410) may correspond to a transmitting device, and the terminal (120) may correspond to a receiving device. In another example, the base station (1410) may correspond to a receiving device, and the terminal (120) may correspond to a transmitting device.

[0235] The base station (1410) is a network infrastructure that provides wireless access to the terminal (120). The base station (1410) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (1410) includes an 'access point (AP)', a 'RAN (radio access network) node', an 'eNodeB (eNB)', and a '5G node (5 th The term "network node" may be referred to as "next generation node (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 meaning.

[0236] The base station (1410) may be implemented as a single entity or may be implemented through multiple entities. In the past, in a communication system with a relatively large cell radius of a base station, each base station (e.g., base station (1410)) was installed so that each base station included the functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or radio unit (RU)). However, as high frequency bands are used in 4G (4th generation) and / or subsequent communication systems (e.g., 5G) and the cell coverage of base stations becomes smaller, the number of base stations to cover a specific area has increased. The burden of installation costs on operators for installing base stations has also increased. In order to minimize the installation cost of base stations, a structure has been proposed in which the DU and RU of a base station are separated, one or more RUs are connected to one DU through a wired network, and one or more RUs are geographically distributed to cover a specific area. In addition, the base station (1410) is installed so that each base station includes the functions of a digital processing unit (or distributed unit (DU)) and a radio frequency (RF) processing unit (or radio unit (RU)) of an access network. It can be implemented in a distributed deployment according to a centralized unit (CU) configured to perform the function of RRC (radio resource control) and a distributed unit (DU) configured to perform the function of a lower layer. At this time, the distributed unit (DU) can include a digital unit (DU) and a radio unit (RU). Between the core (e.g., 5GC (5G core) or NGC (next generation core)) network and the radio network (RAN), the base station can be implemented in a structure in which the CU, DU, and RU are arranged in that order.The interface between the CU and the DU (distributed unit) may be referred to as the F1 interface. The implementation scenarios described above are exemplary, and a specific implementation is not to be construed as limiting the embodiments of the present disclosure. For example, an eNB or gNB operating as an independent node as a base station (1410) may correspond to an E2 node (610). For example, in a distributed deployment, a DU or CU as a component of the base station (1410) may correspond to an E2 node (610).

[0237] The terminal (120) is a device used by a user and communicates with the base station (1410) via a wireless channel. The link from the base station (1410) to the terminal (120) is referred to as a downlink (DL), and the link from the terminal (120) to the base station (1410) is referred to as an uplink (UL). In addition, although not shown in FIG. 14, the terminal (120) and another terminal may communicate with each other via a wireless channel. In this case, the link between the terminal (120) and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal (120) may be operated without the involvement of a user. In one embodiment, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal (120) may be an NB (narrowband)-IoT (internet of things) device.

[0238] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.

[0239] Figure 15 shows an example of access barring for energy saving.

[0240] Referring to FIG. 15, in example (1501), a terminal (120) may be connected to a first cell (1510). An E2 node (e.g., E2 node (610)) (e.g., gNB) providing the first cell (1510) may be connected to a Near-RT RIC (640). The terminal (120) may not be connected to an E2 node providing the second cell (1520). According to one embodiment, the E2 node (610) and the Near-RT RIC (640) may perform an E2 setup procedure. For example, the E2 node (610) may transmit an E2 setup request message including RAN functions associated with E2SM-RC and / or E2SM-CCC to the Near-RT RIC (640). The Near-RT RIC (640) may transmit an E2 setup response message to the E2 node (610). In one embodiment, the E2 node (610) and the Near-RT RIC (640) may perform an RIC subscription procedure. For example, the Near-RT RIC (640) may transmit an RIC subscription request message including an energy saving-related RIC subscription to the E2 node (610). The E2 node (610) may transmit an RIC subscription response message to the Near-RT RIC (640). In one embodiment, the Near-RT RIC (640) may transmit an RIC control request message to the E2 node (610). The RIC control request message may include at least one parameter related to access barring of the first cell (1510). The at least one parameter may include a parameter to be broadcast in an MIB on the first cell (1510) and / or a parameter to be broadcast in an SIB1 on the first cell (1510). For example, the at least one parameter may include at least one of 'cellBarred', 'intraFreqReselection', 'cellReservedForOtherUse' and / or 'cellReservedForOperatorUse'.For example, the Near-RT RIC (640) may transmit a RAN parameter with the value of 'cellBarred' set to 'barred' to the E2 node (610). Under the control of the E2 node (610), the first cell (1510) may be barred.

[0241] In example (1502), the terminal (120) may no longer be able to access the first cell (1510). For example, the terminal (120) may perform cell selection or cell re-selection. For example, the terminal (120) may perform a handover. The terminal (120) may perform an access procedure on the second cell (1520). As access to the first cell (1510) is prohibited, the number of terminals accessing the first cell (1510) may decrease. Accordingly, power consumption associated with the first cell (1510) in the E2 node (610) may decrease.

[0242] In embodiments, a method performed by a near-real time (RT) radio access network intelligence controller (RIC) is provided. The method may include generating an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and transmitting the RIC control request message to an E2 node. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating access barring control. The RIC control message IE may include one or more radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include: a parameter indicating whether a cell (e.g., a cell provided by an E2 node) is barred; The method may include at least one of: a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell (e.g., the cell provided by the E2 node) is prohibited; a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for operator use; or a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for all public land mobile networks (PLMNs).

[0243] For example, the RIC style type may be set to 4, which is a value indicating the wireless access control. The control action ID may be set to 3, which is a value indicating the access barring control. The RIC control request message may include a RAN function identifier (ID). An object identifier (OID) associated with the RAN function ID may indicate E2SM (E2 service model)-RC (RAN control).

[0244] For example, the method may include receiving an E2 setup request message from the E2 node, and, in response to the E2 setup request message, transmitting an E2 setup response message to the E2 node. The E2 setup request message may include the RAN function ID and the OID associated with the RAN function ID.

[0245] For example, the one or more RAN parameters may include at least one PLMN identity. The parameter indicating whether the cell is prohibited may be associated with all PLMNs. The parameter indicating whether the cell is reserved for operator use may be indicated on a per PLMN configuration basis.

[0246] For example, the one or more RAN parameters may include a cell global identity (CGI) indicating a cell for the access barring control. For example, a parameter indicating whether the cell is barred may correspond to a 'cellBarred' IE for use in a master information block (MIB). A parameter for controlling the cell selection and / or cell reselection may correspond to an 'intraFreqReselection' IE for use in the MIB. A parameter indicating whether the cell is reserved for operator use may correspond to a 'cellReservedForOperatorUse' IE for use in a system information block (SIB) 1. A parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs) may correspond to a 'cellReservedForOtherUse' IE for use in the SIB 1.

[0247] In embodiments, a method performed by an E2 node is provided. The method may include receiving, from a near-real time (RT) radio access network intelligence controller (RIC), an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and performing a procedure related to access barring control based on the RIC control request message. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating the access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include: a parameter indicating whether a cell (e.g., a cell provided by the E2 node) is barred; The method may include at least one of: a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell (e.g., the cell provided by the E2 node) is prohibited; a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for operator use; or a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for all public land mobile networks (PLMNs).

[0248] For example, the RIC style type may be set to 4, which is a value indicating the wireless access control. The control action ID may be set to 3, which is a value indicating the access barring control. The RIC control request message may include a RAN function identifier (ID). An object identifier (OID) associated with the RAN function ID may indicate E2SM (E2 service model)-RC (RAN control).

[0249] For example, the method may further include transmitting an E2 setup request message to the Near-RT RIC, and receiving an E2 setup response message corresponding to the E2 setup request message from the E2 node. The E2 setup request message may include the RAN function ID and the OID associated with the RAN function ID.

[0250] For example, the one or more RAN parameters may include at least one PLMN identity. The parameter indicating whether the cell is prohibited may be associated with all PLMNs. The parameter indicating whether the cell is reserved for operator use may be indicated on a per PLMN configuration basis.

[0251] For example, the one or more RAN parameters may include a cell global identity (CGI) indicating a cell for the access barring control. For example, a parameter indicating whether the cell is barred may correspond to a 'cellBarred' IE for use in a master information block (MIB). A parameter for controlling the cell selection and / or cell reselection may correspond to an 'intraFreqReselection' IE for use in the MIB. A parameter indicating whether the cell is reserved for operator use may correspond to a 'cellReservedForOperatorUse' IE for use in a system information block (SIB) 1. A parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs) may correspond to a 'cellReservedForOtherUse' IE for use in the SIB 1.

[0252] In embodiments, a Near-RT (real time) radio access network intelligence controller (RIC) is provided. The Near-RT RIC may include at least one processor including processing circuitry; and a memory including one or more storage media and storing instructions. The instructions, when executed by the at least one processor, may cause the Near-RT RIC to generate an RIC control request message including an RIC control header information element (IE) and an RIC control message IE, and to transmit the RIC control request message to an E2 node. The RIC control header IE may include an RIC style type set to a value indicative of radio access control and a control action identifier (ID) set to a value indicative of access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control. The one or more RAN parameters may include: a parameter indicating whether a cell (e.g., a cell provided by an E2 node) is barred; The method may include at least one of: a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell (e.g., the cell provided by the E2 node) is prohibited; a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for operator use; or a parameter indicating whether the cell (e.g., the cell provided by the E2 node) is reserved for all public land mobile networks (PLMNs).

[0253] For example, the RIC style type may be set to 4, which is a value indicating the wireless access control. The control action ID may be set to 3, which is a value indicating the access barring control. The RIC control request message may include a RAN function identifier (ID). An object identifier (OID) associated with the RAN function ID may indicate E2SM (E2 service model)-RC (RAN control).

[0254] For example, the instructions, when executed by the at least one processor, may cause the Near-RT RIC to receive an E2 setup request message from the E2 node and, in response to the E2 setup request message, to transmit an E2 setup response message to the E2 node. The E2 setup request message may include the RAN function ID and the OID associated with the RAN function ID.

[0255] For example, the one or more RAN parameters may include at least one PLMN identity. The parameter indicating whether the cell is prohibited may be associated with all PLMNs. The parameter indicating whether the cell is reserved for operator use may be indicated on a per PLMN configuration basis.

[0256] For example, the one or more RAN parameters may include a cell global identity (CGI) indicating a cell for the access barring control. For example, a parameter indicating whether the cell is barred may correspond to a 'cellBarred' IE for use in a master information block (MIB). A parameter for controlling the cell selection and / or cell reselection may correspond to an 'intraFreqReselection' IE for use in the MIB. A parameter indicating whether the cell is reserved for operator use may correspond to a 'cellReservedForOperatorUse' IE for use in a system information block (SIB) 1. A parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs) may correspond to a 'cellReservedForOtherUse' IE for use in the SIB 1.

[0257] In embodiments, a network device providing functions of an E2 node is provided. The network device may include at least one processor including a processing circuit; and a memory including one or more storage media and storing instructions. The instructions, when executed by the at least one processor, may cause the network device to receive an RIC control request message including an RIC control header information element (IE) and an RIC control message IE from a Near-RT (real time) radio access network intelligence controller (RIC), and to perform a procedure related to access barring control based on the RIC control request message. The RIC control header IE may include an RIC style type set to a value indicating radio access control and a control action identifier (ID) set to a value indicating the access barring control. The RIC control message IE may include radio access network (RAN) parameters related to the access barring control.The one or more RAN parameters may include at least one of: a parameter indicating whether a cell (e.g., a cell provided by a network device) is prohibited; a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when a highest-ranked cell (e.g., a cell provided by a network device) is prohibited; a parameter indicating whether a cell (e.g., a cell provided by a network device) is reserved for operator use; or a parameter indicating whether a cell (e.g., a cell provided by a network device) is reserved for all public land mobile networks (PLMNs).

[0258] For example, the RIC style type may be set to 4, which is a value indicating the wireless access control. The control action ID may be set to 3, which is a value indicating the access barring control. The RIC control request message may include a RAN function identifier (ID). An object identifier (OID) associated with the RAN function ID may indicate E2SM (E2 service model)-RC (RAN control).

[0259] For example, the instructions, when executed by the at least one processor, may cause the network device to transmit an E2 setup request message to the Near-RT RIC and to receive an E2 setup response message corresponding to the E2 setup request message from the Near-RT RIC. The E2 setup request message may include the RAN function ID and the OID associated with the RAN function ID.

[0260] For example, the one or more RAN parameters may include at least one PLMN identity. The parameter indicating whether the cell is prohibited may be associated with all PLMNs. The parameter indicating whether the cell is reserved for operator use may be indicated on a per PLMN configuration basis.

[0261] For example, the one or more RAN parameters may include a cell global identity (CGI) indicating a cell for the access barring control. For example, a parameter indicating whether the cell is barred may correspond to a 'cellBarred' IE for use in a master information block (MIB). A parameter for controlling the cell selection and / or cell reselection may correspond to an 'intraFreqReselection' IE for use in the MIB. A parameter indicating whether the cell is reserved for operator use may correspond to a 'cellReservedForOperatorUse' IE for use in a system information block (SIB) 1. A parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs) may correspond to a 'cellReservedForOtherUse' IE for use in the SIB 1.

[0262] For one or more embodiments, at least one of the components described in one or more of the preceding drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a processor (e.g., a baseband processor) described herein with respect to one or more of the preceding drawings may be configured to operate according to one or more examples described herein. For another example, circuitry associated with a user equipment (UE), a base station, a network element, and the like, as described above with respect to one or more of the preceding drawings, may be configured to operate according to one or more examples described herein.

[0263] Any of the embodiments described above may be combined with any other embodiment (or combination of embodiments) unless explicitly stated otherwise. The foregoing description of one or more implementations provides examples and descriptions, but is not intended to be exhaustive or limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be learned from practicing various embodiments.

[0264] 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.

[0265] 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 in 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 specifications of the present disclosure. The one or more programs may be provided as included in a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or an application store (e.g., Play Store). ™ ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0266] 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.

[0267] 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.

[0268] 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.

[0269] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0270] 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.< / maxnoofassociatedranparameters> < / maxofricactionid> < / maxofricactionid> < / maxofricactionid> < / maxofranfunctionid> < / maxofranfunctionid> < / maxofranfunctionid>

Claims

1. In a method performed by a near-RT (real time) RIC (radio access network intelligence controller), An action for generating a RIC control request message including a RIC control header IE (information element) and a RIC control message IE; Including an action of transmitting the above RIC control request message to the E2 node, The above RIC control header IE includes a RIC style type set to a value indicating radio access control and a control action identifier set to a value indicating access baring control, The RIC control message IE includes one or more RAN (radio access network) parameters related to the access barring control, wherein said one or more RAN parameters include a parameter indicating whether a cell provided by said E2 node is prohibited, method.

2. In claim 1, If the above parameter indicates that the cell is prohibited, the UE (user equipment) is not allowed to camp on the cell. method.

3. In claim 1, the one or more RAN parameters further include a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell provided by the E2 node is prohibited. method.

4. In claim 3, One or more of the above RAN parameters: A parameter indicating whether the cell is reserved for operator use; or further comprising at least one parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs). method.

5. In claim 4, The above RIC style type is set to 4, which is a value indicating the wireless access control, The above control action ID is set to 3, which is a value indicating the above access barring control, The parameter indicating whether the above cell is barred corresponds to the 'cellBarred' IE for use in the master information block (MIB), The parameters for controlling the above cell selection and / or cell reselection correspond to the 'intraFreqReselection' IE for use in the above MIB, The parameter indicating whether the above cell is reserved for operator use corresponds to the 'cellReservedForOperatorUse' IE for use in SIB (system information block) 1, The parameter indicating whether the above cell is reserved for all PLMNs (public land mobile networks) corresponds to the 'cellReservedForOtherUse' IE for use in the above SIB 1. method.

6. In claim 1, An operation of receiving an E2 setup request message from the above E2 node, In response to the E2 setup request message, further comprising an action of transmitting an E2 setup response message to the E2 node, The above E2 setup request message includes an RAN function ID (identifier) ​​and an OID (object identifier) ​​pointing to E2SM (E2 service model)-RC (RAN control), The above RIC control request message includes the RAN function ID, method.

7. In claim 1, The one or more RAN parameters include a cell global identity (CGI) pointing to the cell for the access barring control, method.

8. In the method performed by the E2 node, An operation of receiving an RIC control request message including an RIC control header information element (IE) and an RIC control message IE from a Near-RT (real time) RIC (radio access network intelligence controller), The above RIC control header IE includes a RIC style type set to a value indicating radio access control and a control action identifier set to a value indicating access barring control, The RIC control message IE includes RAN (radio access network) parameters related to the access barring control, and the one or more RAN parameters include a parameter indicating whether a cell provided by the E2 node is prohibited. method.

9. In claim 8, If the above parameter indicates that the cell is prohibited, the UE (user equipment) is not allowed to camp on the cell. method.

10. In claim 8, the one or more RAN parameters further include a parameter for controlling cell selection and / or cell reselection for an intra-frequency cell when the highest-ranked cell provided by the E2 node is prohibited. method.

11. In claim 10, One or more of the above RAN parameters: A parameter indicating whether the cell is reserved for operator use; or further comprising at least one parameter indicating whether the cell is reserved for all public land mobile networks (PLMNs). method.

12. In claim 11, The above RIC style type is set to 4, which is a value indicating the wireless access control, The above control action ID is set to 3, which is a value indicating the above access barring control, The parameter indicating whether the above cell is barred corresponds to the 'cellBarred' IE for use in the master information block (MIB), The parameters for controlling the above cell selection and / or cell reselection correspond to the 'intraFreqReselection' IE for use in the above MIB, The parameter indicating whether the above cell is reserved for operator use corresponds to the 'cellReservedForOperatorUse' IE for use in SIB (system information block) 1, The parameter indicating whether the above cell is reserved for all PLMNs (public land mobile networks) corresponds to the 'cellReservedForOtherUse' IE for use in the above SIB 1. method.

13. In claim 8, An action of transmitting an E2 setup request message to the Near-RT RIC; Further comprising an operation of receiving an E2 setup response message corresponding to the E2 setup request message from the Near-RT RIC, The above E2 setup request message includes an RAN function ID (identifier) ​​and an OID (object identifier) ​​pointing to E2SM (E2 service model)-RC (RAN control), The above RIC control request message includes the RAN function ID, method.

14. In the near-RT(real time) RIC(radio access network intelligence controller), At least one processor comprising a processing circuit; and A memory comprising one or more storage media and storing instructions, The instructions, when executed by the at least one processor, are configured to cause the Near-RT RIC to perform any one of the methods of claims 1 to 7. Near-RT RIC.

15. In a network device for performing the functions of an E2 node, At least one processor comprising a processing circuit; and A memory comprising one or more storage media and storing instructions, The instructions, when executed by the at least one processor, are configured to cause the network device to perform any one of the methods of claims 8 to 13. Network devices.

Images