KR20240045973A - Electronic device and method for subscription audit - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates after 4G communication systems such as LTE. In embodiments, the electronic device of the E2 node includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to transmit an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The at least one processor may control the at least one transceiver to receive a check response message from the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

Description

Electronic device and method for subscription testing {ELECTRONIC DEVICE AND METHOD FOR SUBSCRIPTION AUDIT}

The descriptions below relate to electronic devices and methods for subscription audit.

In order to meet the increasing demand for wireless data traffic following the commercialization of the 4G ( ^4th generation) communication system, efforts are being made to develop an improved 5G ( ^5th generation) communication system or a pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is called a Beyond 4G Network communication system or a Post LTE (Long Term Evolution) system.

To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (such as the 60 GHz band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, to improve the network of the system, the 5G communication system uses evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), and ultra-dense networks. , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation. Technology development is underway.

In addition, the 5G system uses FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), which are advanced coding modulation (ACM) methods, and FBMC (Filter Bank Multi Carrier), which is an advanced access technology. ), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed.

To meet the demand for wireless data traffic, the 5G system, NR (new radio or next radio), has been commercialized, providing users with high data rate services through the 5G system like 4G, and also for the Internet of Things and specific purposes. It is expected that wireless communication services for various purposes, such as services requiring high reliability, can be provided. Currently, in a system that is mixed with the 4th generation communication system and the 5th generation system, O-RAN (open radio access network), established by operators and equipment providers, is an E2 node and Near-RT (real time) RIC (radio access network (RAN)). In the application protocol of the E2 interface between networks and intelligent controllers, various specifications are defined.

Looking back at the development of wireless communication through successive generations, technologies have been developed mainly for human services, such as voice, multimedia, and data. After the commercialization of the 5G (5th Generation) communication system, it is expected that an explosive increase in connected devices will be connected to communication networks. Examples of objects connected to the network may include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors such as augmented reality glasses, virtual reality headsets, and hologram devices. In the 6G (6th Generation) era, efforts are being made to develop an improved 6G communication system to provide a variety of services by connecting hundreds of billions of devices and objects. For this reason, the 6G communication system is called a beyond 5G system.

In the 6G communication system, which is expected to be realized around 2030, the maximum transmission speed is tera (i.e., 1,000 gigabytes) bps (bit per second), and the wireless delay time is 100 microseconds (μsec). In other words, compared to the 5G communication system, the transmission speed in the 6G communication system is 50 times faster and the wireless delay time is reduced by one-tenth.

To achieve these high data rates and ultra-low latency, 6G communication systems will operate in the Terahertz (THz) band (e.g., from 95 Gigahertz (GHz) to 3 THz). Implementation in the ) band is being considered. The importance of technology that can guarantee signal reach, or coverage, is expected to increase in the terahertz band due to more serious path loss and atmospheric absorption compared to the mmWave band introduced in 5G. The main technologies to ensure coverage are RF (Radio Frequency) elements, antennas, new waveforms that are better in terms of coverage than OFDM (Orthogonal Frequency Division Multiplexing), beamforming, and massive multiple input/output (MASSIVE multiple input/output). Multi-antenna transmission technologies such as Input and Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, and large scale antenna must be developed. . In addition, to improve the coverage of terahertz band signals, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed.

In addition, in order to improve frequency efficiency and system network, the 6G communication system uses full duplex technology where uplink and downlink simultaneously utilize the same frequency resources at the same time, satellite and Network technology that comprehensively utilizes HAPS (High-Altitude Platform Stations), network structure innovation technology that supports mobile base stations and enables network operation optimization and automation, and dynamic frequency sharing through collision avoidance based on spectrum usage prediction. (dynamic spectrum sharing) technology, 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 overcomes the limits of terminal computing capabilities. Next-generation distributed computing technologies that realize complex services using ultra-high-performance communication and computing resources (Mobile Edge Computing (MEC), cloud, etc.) are being developed. In addition, through the design of new protocols to be used in the 6G communication system, the implementation of a hardware-based security environment, the development of mechanisms for safe use of data, and the development of technologies for maintaining privacy, the connectivity between devices is further strengthened and the network is further improved. Attempts are continuing to optimize, promote softwareization of network entities, and increase the openness of wireless communications.

Due to the research and development of these 6G communication systems, a new level of hyper-connected experience (the next hyper-connected) is possible through the hyper-connectivity of the 6G communication system, which includes not only connections between objects but also connections between people and objects. experience) is expected to become possible. Specifically, it is expected that the 6G communication system will be able to provide services such as truly immersive eXtended Reality (XR), high-fidelity mobile hologram, and digital replica. In addition, services such as remote surgery, industrial automation, and emergency response through improved security and reliability are provided through the 6G communication system, enabling application in various fields such as industry, medicine, automobiles, and home appliances. It will be.

In the 6G communication system, it is expected that RAN functions will be further divided into service subscribers and service providers. In a service-based network, the subscription service confirmation process for service subscription status will be applied to various functions.

In embodiments, the method performed by the E2 node may include transmitting an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). . The method may include receiving a test response message from the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a method performed by Near-RT (real time) RIC may include transmitting an audit request message to the E2 node. The method may include receiving a check response message from the E2 node. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a method performed by an E2 node may include receiving an audit request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). . The method may include transmitting a test response message to the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a method performed by Near-RT (real time) RIC may include receiving an audit request message from an E2 node. The method may include transmitting a check response message to the E2 node. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, the electronic device of the E2 node includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to transmit an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The at least one processor may control the at least one transceiver to receive a check response message from the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a Near-RT (real time) RIC electronic device includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to transmit an audit request message to the E2 node. The at least one processor may control the at least one transceiver to receive a test response message from the E2 node. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, the electronic device of the E2 node includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to receive an audit request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The at least one processor may control the at least one transceiver to transmit a check response message to the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a Near-RT (real time) RIC electronic device includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver.

The at least one processor may control the at least one transceiver to receive an audit request message from the E2 node. The at least one processor may control the at least one transceiver to transmit a test response message to the E2 node. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

Figure 1 shows an example of a 4th generation (4G) Long Term Evolution (LTE) core system.
Figure 2A shows an example of a 5th generation (5G) non-standard alone (NSA) system.
Figure 2b shows an example of architecture for O-RAN.
Figure 3 shows a protocol stack of an E2 application protocol message in a wireless access network according to embodiments.
Figure 4 shows an example of a connection between a base station and a radio access network intelligence controller (RIC) in a wireless access network according to embodiments.
Figure 5 shows the configuration of a device in a wireless access network according to embodiments.
FIG. 6 illustrates logical functions related to the E2 message of an E2 node and RIC in a wireless access network according to embodiments.
Figure 7 shows examples of functional separation between an E2 node and RIC in embodiments.
Figure 8 shows an example of implementation of an E2 node and RIC according to embodiments.
Figure 9 shows examples of functional separation between a centralized unit (CU) and RIC according to embodiments.
FIG. 10 illustrates functional blocks of each Near-RT RIC and E2 node according to a subscription procedure, according to embodiments.
Figure 11A shows an example of a subscription audit procedure between a Near-RT RIC and an E2 node, according to one embodiment.
FIG. 11B shows an example of a subscription check procedure between a Near-RT RIC and an E2 node, according to one embodiment.
Figure 12A shows an example of a subscription check procedure triggered by activity time, according to one embodiment.
Figure 12B shows an example of a subscription check procedure initiated based on an event, according to one embodiment.
13 shows an example of subscription management using a subscription check procedure, according to one embodiment.
14 illustrates an example of subscription management using a subscription check procedure, according to one embodiment.
Figure 15 shows an example of subscription management using a subscription check procedure, according to one embodiment.
Figure 16 shows an example of subscription management using a subscription check procedure, according to one embodiment.

본 개시에서 사용되는 용어들은 단지 특정한 실시예를 설명하기 위해 사용된 것으로, 다른 실시예의 범위를 한정하려는 의도가 아닐 수 있다. 단수의 표현은 문맥상 명백하게 다르게 뜻하지 않는 한, 복수의 표현을 포함할 수 있다. 기술적이거나 과학적인 용어를 포함해서 여기서 사용되는 용어들은 본 개시에 기재된 기술 분야에서 통상의 지식을 가진 자에 의해 일반적으로 이해되는 것과 동일한 의미를 가질 수 있다. 본 개시에 사용된 용어들 중 일반적인 사전에 정의된 용어들은, 관련 기술의 문맥상 가지는 의미와 동일 또는 유사한 의미로 해석될 수 있으며, 본 개시에서 명백하게 정의되지 않는 한, 이상적이거나 과도하게 형식적인 의미로 해석되지 않는다. 경우에 따라서, 본 개시에서 정의된 용어일지라도 본 개시의 실시예들을 배제하도록 해석될 수 없다.

Terms used in the present disclosure are merely used to describe specific embodiments and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted to have the same or similar meaning as the meaning they have in the context of related technology, and unless clearly defined in this disclosure, have an ideal or excessively formal meaning. It is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method is explained as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, the various embodiments of the present disclosure do not exclude software-based approaches.

Hereinafter, the present disclosure relates to a device within a radio access network (RAN) and an inter-device control procedure for controlling the RAN in a wireless communication system. Specifically, the present disclosure provides a version number of the E2AP standard (e.g., E2AP 2.02) from the E2 node to the RIC on the E2 interface, so that the E2 node and the RIC perform standardly correct operations and ensure backward compatibility. It relates to procedures, messages, and methods to ensure that

Terms used in the following description refer to configuration (e.g., setup, setting, arrangement, control), and terms that refer 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, resource block (RB), bandwidth part (BWP), opportunity), terms for operational states (e.g. step, operation, procedure), data. Terms (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 plane), O-DU (O-RAN (open radio access network) DU), O-RAN RU (O-RU), O-RAN CU (O-CU), O-RAN CU-CP (O-CU-UP), O-RAN CU-CP (O-CU-CP), device Terms referring to the components of are exemplified for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used. In addition, terms such as '... part', '... base', '... water', and '... body' used hereinafter mean at least one shape structure or a unit that processes a function. It can mean.

In addition, in the present disclosure, the expressions greater than or less than may be used to determine whether a specific condition is satisfied or fulfilled, but this is only a description for expressing an example, and the description of more or less may be used. It's not exclusion. Conditions written as ‘more than’ can be replaced with ‘more than’, conditions written as ‘less than’ can be replaced with ‘less than’, and conditions written as ‘more than and less than’ can be replaced with ‘greater than and less than’. In addition, hereinafter, 'A' to 'B' means at least one of the elements from A to (including A) and B (including B). Hereinafter, 'C' and/or 'D' means including at least one of 'C' or 'D', i.e. {'C', 'D', 'C' and 'D'}.

In addition, the present disclosure provides various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), extensible radio access network (xRAN), and open radio access network (O-RAN)). However, this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

As ^4th generation (4G)/ ^5th generation (5G) communication systems (e.g., new radio (NR)) are commercialized, differentiated service support for users in virtualized networks has become required. 3GPP is a joint research project between mobile communication organizations and aims to create 3rd generation mobile communication system specifications that can be applied globally within the scope of the IMT-2000 project of the International Telecommunication Union (ITU). 3GPP was established in December 1998, and the 3GPP standard is based on the advanced GSM standard, and includes radio, core network, and service architecture in the scope of standardization. Accordingly, O-RAN (open radio access network) is a 3GPP NE (network entity) and the nodes that make up the base station: RU (radio unit), DU (digital unit), CU (central unit) - CP (control plane) ), CU-UP (user plane) is newly defined as O(O-RAN)-RU, O-DU, O-CU-CP, and O-CU-UP, respectively, and additionally NRT (near-real- time) RIC (radio access network intelligent controller) was standardized. This disclosure is intended to support an operator specific service model in the E2 interface where RIC requests service from O-DU, O-CU-CP or O-CU-UP. Here, O-RU, O-DU, O-CU-CP, and O-CU-UP can be understood as objects constituting the RAN that can operate according to the O-RAN standard, and can be used as an E2 node. can be referred to. The interface with objects constituting the RAN that can operate according to the O-RAN standard between RIC and E2 nodes uses E2AP (application protocol).

RIC is a logical node that can collect information at the cell site where the terminal and O-DU, O-CU-CP or O-CU-UP transmit and receive. RIC can be implemented in the form of servers centrally located in one physical location. Connections can be made via Ethernet between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC. For this purpose, interface specifications for communication between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC are needed, and E2-DU, E2-CU-CP, E2-CU- Definition of message standards such as UP and procedures between O-DU, O-CU-CP, O-CU-UP and RIC is required. In particular, differentiated service support is required for users in virtualized networks, and E2-DU to support services for a wide range of cell coverage by concentrating call processing messages/functions generated in O-RAN on RIC. Function definition of the messages of E2-CU-CP and E2-CU-UP is required.

RIC communicates with O-DU, O-CU-CP, and O-CU-UP using the E2 interface, and can set event occurrence conditions by generating and sending a subscription message. Specifically, RIC can set up a call processing EVENT by generating an E2 subscription request message and delivering it to an E2 node (e.g. O-CU-CP, O-CU-UP, O-DU). there is. Additionally, after setting EVENT, the E2 node delivers the Subscription Request Response message to the RIC.

The E2 node can transmit the current status to the RIC through E2 indication/report. RIC can provide control for O-DU, O-CU-CP, and O-CU-UP using E2 control messages. Various embodiments of the present disclosure propose an E2 indication message in which UE-level measurement information is transmitted for each period set in subscription event conditions in the O-DU. Additionally, various embodiments of the present disclosure propose a message for controlling resources transmitted from RIC to O-DU.

Figure 1 shows an example of a 4 ^th generation (4G) Long Term Evolution (LTE) core system.

Referring to Figure 1, the LTE core system includes a base station 110, a terminal 120, a serving gateway (S-GW) 130, a packet data network gateway (P-GW) 140, and a mobility management entity (MME). (150), HSS (home subscriber server) (160), and PCRF (policy and charging rule function) (170).

The base station 110 is a network infrastructure that provides wireless access to the terminal 120. For example, the base station 110 is a device that performs scheduling by collecting status information such as buffer status, available transmission power, and channel status of the terminal 110. Base station 110 has coverage defined as a certain geographic area based on the distance over which signals 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 includes an 'access point (AP)', an 'eNodeB (eNB)', a 'wireless point', a 'transmission/reception point, TRP)' or other terms with equivalent technical meaning.

The terminal 120 is a device used by a user and communicates with the base station 110 through a wireless channel. In some cases, the terminal 120 may be operated without user involvement. That is, at least one of the terminal 120 and the terminal 130 is a device that performs machine type communication (MTC) and may not be carried by the user. The terminal 120 is a terminal, as well as 'user equipment (UE)', 'mobile station', 'subscriber station', and customer-premises equipment (CPE). It may be referred to as a 'remote terminal', 'wireless terminal', or 'user device' or other terms having equivalent technical meaning.

The S-GW (130) provides a data bearer and creates or controls the data bearer under the control of the MME (150). For example, the S-GW 130 processes packets arriving from the base station 110 or packets to be forwarded to the base station 110. Additionally, the S-GW 130 may perform an anchoring role during handover between base stations of the terminal 120. The P-GW 140 may function as a connection point with an external network (e.g., an Internet network). Additionally, the P-GW 140 allocates an IP (Internet Protocol) address to the terminal 120 and serves as an anchor for the S-GW 130. Additionally, the P-GW 140 can apply the Quality of Service (QoS) policy of the terminal 120 and manage account data.

The MME 150 manages the mobility of the terminal 120. Additionally, the MME 150 may perform authentication and bearer management for the terminal 120. That is, the MME 150 is responsible for mobility management and various control functions for the terminal. The MME 150 can be linked to a serving GPRS support node (SGSN).

HSS 160 stores key information and subscriber profile for authentication of terminal 120. Key information and subscriber profile are transmitted from the HSS 160 to the MME 150 when the terminal 120 connects to the network.

PCRF 170 defines rules for policy and charging. The stored information is transferred from the PCRF 180 to the P-GW 140, and the P-GW 140 controls the terminal 120 (e.g., QoS management, billing, etc.) based on the information provided from the PCRF 180. ) can be performed.

Carrier aggregation (CA) technology combines multiple component carriers, and one terminal transmits and receives signals using these multiple component carriers simultaneously, thereby increasing the frequency from the terminal or base station perspective. It is a technology that increases usage efficiency. Specifically, according to CA technology, the terminal and the base station can transmit and receive signals using a wide bandwidth using a plurality of component carriers in the uplink (UL) and downlink (DL), respectively. At this time, each component carrier are located in different frequency bands. Hereinafter, uplink refers to a communication link through which a terminal transmits a signal to a base station, and downlink refers to a communication link through which a base station transmits a signal to a terminal. At this time, the number of uplink component carriers and downlink component carriers may be different.

Dual/multiple connectivity technology (dual connectivity or multi connectivity) allows one terminal to connect to multiple different base stations and simultaneously transmit and receive signals using carriers within multiple base stations located in different frequency bands, from the perspective of the terminal or base station. It is a technology that increases frequency use efficiency. The terminal provides services using a first base station (e.g., a base station that provides services using LTE technology or 4th generation mobile communication technology) and a second base station (e.g., new radio (NR) technology or ^5th generation (5G) mobile communication technology. It can simultaneously connect to a base station that provides and transmit and receive traffic. At this time, the frequency resources used by each base station may be located in different bands. In this way, a method that operates based on the dual connection method of LTE and NR can be called 5G NSA (non-standalone).

Figure 2A shows an example of a 5G NSA system.

Referring to FIG. 2A, the 5G NSA system includes an NR RAN (210a), an LTE RAN (210b), a terminal 220, and an evolved packet core (EPC) 250. The NR RAN (210a) and the LTE RAN (210b) are connected to the EPC 150, and the terminal 220 can receive services from either or both the NR RAN (210a) and the LTE RAN (210b) at the same time. NR RAN 210a includes at least one NR base station, and LTE RAN 210b includes at least one LTE base station. Here, the NR base station may be referred to as '5G node (5th generation node)', 'next generation nodeB (gNB)', or other terms with equivalent technical meaning. In addition, the NR base station may have a structure divided into a central unit (CU) and a digital unit (DU), and the CU is divided into a control plane (CU-CP) unit and a user plane (CU-UP) unit. You can have

In the structure shown in FIG. 2, the terminal 220 performs radio resource control (RRC) access through a first base station (e.g., a base station belonging to the LTE RAN 210b) and functions provided in the control plane. You can receive services (e.g. connection management, mobility management, etc.). Additionally, the terminal 220 may be provided with additional radio resources for transmitting and receiving data through a second base station (e.g., a base station belonging to the NR RAN 210a). This dual connectivity technology using LTE and NR may be referred to as EN-DC (E-UTRA (evolved universal terrestrial radio access) - NR dual connectivity). Similarly, a dual connectivity technology in which the first base station uses NR technology and the second base station uses LTE technology is referred to as NE-DC (NR - E-UTRA dual connectivity). Additionally, various embodiments can be applied to various other types of multiple connectivity and carrier aggregation technologies. In addition, various embodiments may be applied even when a first system using a first communication technology and a second system using a second communication technology are implemented in one device or when the first base station and the second base station are located in the same geographical location. You can.

Figure 2b shows an example of architecture for O-RAN. For the purpose of key performance indicator (KPI) monitoring (E2-SM-KPIMON) of the E2 service model, O- in multi-connectivity operation using E-UTRA and NR radio access technologies. RAN Non-stand alone mode is considered, while the E2 node can be assumed to be in O-RAN Stand Alone mode.

Referring to Figure 2b, in the deployment of O-RAN non-standalone mode, the eNB is connected through the EPC and S1-C/S1-U interface, and connected through O-CU-CP and X2 interface. O-CU-CP for deployment in O-RAN standalone mode can be connected to 5GC (5G core) through N2/N3 interface.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets 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 the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

1 to 2B illustrate the 4G and/or 5G environment as an example, but this description does not limit the scope of the communication environment of the embodiments of the present disclosure. Technical principles according to embodiments of the present disclosure can also be applied to 6G and post-6G communication technologies and network environments.

FIG. 3 illustrates a protocol stack of an E2 application protocol message in a wireless access network according to embodiments of the present disclosure. Referring to FIG. 3, the control plane includes a transport network layer and a radio network layer. The transmission network layer includes a physical layer 310, a data link layer 320, an internet protocol (IP) 330, and a stream control transmission protocol (SCTP) 340.

The wireless network layer includes E2AP (350). E2AP (350) is used to deliver subscription messages, indication messages, control messages, service update messages, and service query messages, It is transmitted at the higher layer of SCTP (340) and IP (330).

Figure 4 shows an example of a connection between a base station and a radio access network intelligence controller (RIC) in a radio access network according to embodiments of the present disclosure.

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

Figure 4 illustrates one RIC 440, however, depending on various embodiments, there may be multiple RICs. Multiple RICs may be implemented with multiple hardware located in the same physical location or may be implemented through virtualization using one hardware.

Figure 5 shows the configuration of a device according to embodiments of the present disclosure. The structure illustrated in FIG. 5 can be understood as the configuration of a device having at least one function among the near-RT RIC, non-RT RIC, O-CU-CP, O-CU-UP, and O-DU of FIG. 5. . Terms such as 'unit' and 'unit' used hereinafter refer to a unit that processes at least one function or operation, and may be implemented as hardware, software, or a combination of hardware and software.

Referring to FIG. 5, the core network device includes a transceiver 510, a memory 520, and a processor 530.

The transceiver 510 provides an interface for communicating with other devices in the network. That is, the transceiver 510 converts a bit string transmitted from a core network device to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the transceiver 510 can transmit and receive signals. Accordingly, the transceiver 510 may be referred to as a communication unit, modem, transmit unit, receive unit, or transmit/receive unit. At this time, the transceiver 510 allows the core network device to communicate with other devices or systems through a backhaul connection (e.g., wired backhaul or wireless backhaul) or through a network. Although only one transceiver 510 is shown in FIG. 5, the device may include one or more transceivers.

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

The processor 530 controls the overall operations of a network element (NE) device, such as an E2 node or Near-RT RIC. For example, the processor 530 transmits and receives signals through the transceiver 510. Additionally, the processor 530 writes and reads data into the memory 520. Although one processor 530 is shown in Figure 5, the device may include one or more processors. According to various embodiments, the processor 530 may control the device to perform operations according to various embodiments described in this disclosure.

FIG. 6 illustrates logical functions related to the E2 message of an E2 node and RIC in a wireless access network according to embodiments of the present disclosure.

Referring to FIG. 6, the RIC 640 and the E2 node 610 can transmit or receive E2 messages to each other. For example, E2 node 610 may be O-CU-CP, O-CU-UP, O-DU, or a base station. The communication interface of the E2 node may be determined depending on the type of E2 node 610. For example, the E2 node 610 may communicate with another E2 node 616 through the E1 interface or the F1 interface. Or, for example, the E2 node 610 may communicate with the E2 node 616 through an X2 interface or an XN interface. Or, for example, the E2 node 610 may perform communication through an S1 interface or a next generation application protocol (NGAP) interface (i.e., an interface between a next generation (NG) RAN node and the AMF).

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, KPI monitor collection S/W is installed in the RIC (640), and the E2 node (610) generates KPI parameters and then sends an E2 message containing the KPI parameters to RIC ( It may include an E2 node function 612 that delivers to the E2 termination 642 located at 640). E2 node 610 may include radio resource management (RRM) 614. The E2 node 610 can manage resources provided to the wireless network for the terminal.

The E2 terminal 642 located in the RIC 640 is an terminal of the RIC 640 for E2 messages, and performs the function of interpreting the E2 message transmitted by the E2 node 610 and then delivering it to xApp 646. do. A database (DB) 644 located in the RIC 640 may be used for the E2 endpoint 624 or xApp 616. The E2 node 610 shown in FIG. 6 is the terminal of at least one interface and can be understood as the terminal of messages delivered to the terminal, surrounding base stations, and core network.

Figure 7 shows examples of functional separation between an E2 node and RIC in embodiments of the present disclosure. The O-RAN specification provides separation of functions between E2 nodes and RIC. For example, the E2 node may be a CU. RIC may be Near RT RIC. RIC can be connected to ONAP (open network automation platform)/MANO (management and orchestration)/NMS (network management system) through the A1 interface. RIC can be connected to the E2 node through the E2 interface. The E2 interface can transmit commands. Function separation options may include function separation (700) in which the entire radio resource management (RRM) is managed by the near-RT RIC, and function separation (750) in which RRM is selectively managed in the near-RT RIC.

Following the WG3 decision from the 2019/01/16 meeting, Near-RT RIC will support E2 with an open logical interface targeting multi-vendor environments, regardless of the specific RRC-RRM algorithm implementation located in the near RT-RIC. In this disclosure, we provide an E2SM-NI paired with an E2SM-NI that can perform inject/modify/configuration of Per UE RRC messages for each I/F and NE (network entity). RIC (E2 Service Model Radio Interface Control) may be proposed. In other words, Near RT RIC can be improved gradually from function separation 750 to function separation 700. E2 is independent of the specific RRC-RRM algorithm implementation in near RT-RIC and can be evolved into an open logical interface targeting multi-vendor environments.

Figure 8 shows an implementation example of an E2 node and RIC according to embodiments of the present disclosure. In the scenario of implementation example 800, E2 nodes (e.g., O-DU, O-CU) and RIC are virtualized on a cloud platform (e.g., open chassis and blade specification edge cloud) and configured on devices (e.g., servers). It can be. These scenarios will support deployments in dense urban areas with ample fronthaul capacity allowing BBU functions to be pooled at a central location, with latency low enough to meet O-DU latency requirements. You can. Therefore, there may be no need to attempt to centralize the RIC closer to the RT than the limit at which O-DU functions can be centralized. According to one embodiment, E2SM-RIC may be optimized for O-RAN deployment scenarios where Near-RT RIC, O-CU, and O-DU are implemented in the O-Cloud Platform.

Figure 9 shows examples of functional separation between a centralized unit (CU) and RIC according to embodiments of the present disclosure. Referring to Figure 9, function separations may be performed according to deployment scenario #1 (900) or function deployment scenario #2 (950).

Deployment Scenario #1 (900): RIC is located at a separate site or exists only as another NE, and several intelligence essential functions are replaced or recommended.

Deployment Scenario #2 (950): RIC can replace almost all functions of CU except 3GPP I/F management.

Figure 9 shows two scenarios, but other scenarios may also be applied. As an example, in deployment scenario #1 (900), the mobility function may be performed by the RIC rather than the CU. Additionally, as an example, in deployment scenario #1 900, the UE context function may be performed by the RIC rather than the CU. Additionally, as an example, in deployment scenario #1 (900), the session establishment function may be performed by the RIC rather than the CU.

FIG. 10 illustrates functional blocks of each Near-RT RIC and E2 node according to a subscription procedure, according to embodiments. The above subscription procedure refers to the RIC subscription procedure. The RIC subscription procedure can be used to establish E2 subscriptions consisting of an event trigger and a sequence of actions. O-RAN Working Group (WG) 3 Near-Real-time RAN Intelligent Controller Architecture & E2 General Aspects and Principles (E2GAP) specifications define Near-RT RIC as a service consumer and E2 nodes as service producers ( service producer). In order to receive services from Near-RT RIC, you can perform the RIC subscription process. The standard specifies that for the RIC subscription procedure, the Near-RT RIC transmits a RIC subscription request message. E2 node 1010 in FIG. 10 exemplifies the E2 node (eg, E2 node 610) described through FIGS. 1 to 9. Near-RT RIC 1020 in FIG. 10 exemplifies the RIC (e.g., RIC 640) described through FIGS. 1 to 9.

Near-RT RIC 1020 may transmit a RIC subscription request message (e.g., RIC SUBSCRIPTION REQUEST message) to the E2 node 1010. The RIC subscription request message may include information about RAN functions. The E2 node 1010 may transmit a RIC subscription response message (e.g., RIC SUBSCRIPTION RESPONSE message) to the Near-RT RIC 1020. If there is no error in the RIC subscription request message and the RAN function of the RIC subscription request message is supported, the E2 node (1010) can transmit a RIC subscription response message to the Near-RT RIC (1020). . If the E2 node 1010 does not allow at least one requested action, detects an inconsistency in the sequence of actions and/or action definitions, or a failure occurs during the RIC subscription procedure, the E2 node 1010 ) may transmit a RIC subscription failure message (e.g., RIC SUBSCRIPTION FAILURE message) to the Near-RT RIC (1020).

The subscription request message transmitted from the Near-RT RIC 1020 to the E2 node 1010 may include a RAN function and an event trigger definition related to the RAN function. For example, the structure of the subscription request message is as shown in the table below.

IE/Group Name Presence Range IE types and references Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Subscription Details M YES reject >RIC Event Trigger Definition M 9.2.9 - >Sequence of Actions 1..<maxofRICactionID> EACH ignore >>RIC Action ID M 9.2.10 - >>RIC Action Type M 9.2.11 - >>RIC Action Definition O 9.2.12 - >>RIC Subsequent Action O 9.2.13 -

As another example, the structure of the subscription request message is as shown in the table below.

IE/Group Name Presence Range IE types and references Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function List 1..<maxofRANFunctionID> > RAN Function ID M 9.2.8 YES reject > RIC Subscription Details M YES reject >>RIC Event Trigger Definition M 9.2.9 - >>Sequence of Actions 1..<maxofRICactionID> EACH ignore >>>RIC Action ID M 9.2.10 - >>>RIC Action Type M 9.2.11 - >>>RIC Action Definition O 9.2.12 - >>>RIC Subsequent Action O 9.2.13 -

As another example, the structure of the subscription request message is as shown in the table below.

IE/Group Name Presence Range IE types and references Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject RIC Subscription Details M YES reject >RIC Event Trigger Definition List 1..<maxnoofRICStyle> >>RIC Event Trigger Definition M 9.2.9 - >>Sequence of Actions 1..<maxofRICactionID> EACH ignore >>>RIC Action ID M 9.2.10 - >>>RIC Action Type M 9.2.11 - >>>RIC Action Definition O 9.2.12 - >>>RIC Subsequent Action O 9.2.13 -

As another example, the structure of the subscription request message is as shown in the table below.

IE/Group Name Presence Range IE types and references Semantics description Criticality Assigned Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function List 1..<maxofRANFunctionID> > RAN Function ID M 9.2.8 YES reject > RIC Subscription Details M YES reject >>RIC Event Trigger Definition List 1..<maxnoofRICStyle> >>>RIC Event Trigger Definition M 9.2.9 - >>>Sequence of Actions 1..<maxofRICactionID> EACH ignore >>>>RIC Action ID M 9.2.10 - >>>>RIC Action Type M 9.2.11 - >>>>RIC Action Definition O 9.2.12 - >>>>RIC Subsequent Action O 9.2.13 -

An E2 setup procedure may be performed between the E2 node 1010 and the Near-RT RIC (1020). In the E2 setup procedure, the E2 node 1010 may transmit an E2 SETUP REQUEST message to the Near-RT RIC 1020. Near-RT RIC (1020) may transmit an E2 SETUP RESPONSE message to the E2 node (1010). The E2 setup request message of the 'E2 setup procedure may include RAN function IDs (identifiers). The E2 setup request message may include a RAN Function Definition corresponding to the RAN Function ID corresponding to each RAN Function ID. The RAN function definition may include a description of the RAN function. RAN functions may be specific to the E2 service model. Thereafter, in the procedure, the RAN function may be indicated through the RAN function ID. After the E2 setup procedure, a subscription procedure may be performed to provide service.

Referring to FIG. 10, through the subscription procedure, the Near-RT RIC (1020) can subscribe to the service provided by the E2 node (1010). Near-RT RIC (1020) can subscribe to a service corresponding to the RAN function ID. Near-RT RIC 1020 may store multiple subscriptions corresponding to a RAN function ID. Each subscription may correspond to one RIC Request ID. RIC Request ID is a local identifier used by Near-RT RIC 1020 to identify a specific RIC subscription procedure. For example, E2 node 1010, as a service producer, may store information about three subscriptions (e.g., RIC Request ID 1, 2, 3) in a RAN function ID (e.g., RAN FUNCTION ID=1). There is (1011). The E2 node 1010 may perform one or more subscription procedures with the communication block 1023 of the Near-RT RIC 1020 through the communication block 1013. Near-RT RIC (1020) can obtain information about three subscriptions (e.g., RIC Request ID 1, 2, 3) to the RAN function ID (e.g., RAN FUNCTION ID=1) (1013).

A network element (NE), such as the E2 node 1010 or the Near-RT RIC 1020, may be implemented by hardware or in the cloud through software. The software function block corresponding to the E2 node 1010 may operate through the cloud, as shown in FIG. 8. The E2 node 1010 may store subscription information in a database (DB). In the same way, a functional block corresponding to the Near-RT RIC 1020 (e.g., a subscription manager of the Near-RT RIC 1020) may operate through the cloud. Near-RT RIC (1020) can store subscription information in the DB.

Let us assume a situation where the function block corresponding to the E2 node 1010 is turned OFF and then turned ON again. The E2 node 1010 can obtain the stored subscription information. If a procedure is in progress between the Near-RT RIC (1020) and the E2 node (1010) while the E2 node (1010) is OFF, there is a mismatch between the subscription information of the E2 node (1010) and the subscription information of the Near-RT RIC (1020). may occur. In the same way, even in a situation where the functional block corresponding to the Near-RT RIC (1020) (e.g., subscription manager of the Near-RT RIC (1020)) is turned OFF and then turned ON again, the E2 node (1010) There may be a discrepancy between the subscription information of and the subscription information of the Near-RT RIC (1020). If a mismatch occurs, the E2 node 1010 or Near-RT RIC 1020 may re-perform the reset procedure or E2 setup procedure. However, after the E2 setup procedure, procedures performed repeatedly to join the RIC may act as resource overhead on the E2 interface.

In order to resolve the above-mentioned discrepancy, that is, to compare the subscription status of the E2 node 1010 with the subscription status of the Near-RT RIC 1020, the E2 node 1010 may initiate a subscription check procedure. The inspection procedure initiated by E2 node 1010 is described in detail through Figure 11A. Likewise, the Near-RT RIC 1020 may initiate a subscription check procedure to compare the subscription status of the Near-RT RIC 1020 with the subscription status of the E2 node 1010. The subscription process initiated by Near-RT RIC 1020 is described in detail through FIG. 11B.

Figure 11A shows an example of a subscription audit procedure between a Near-RT RIC and an E2 node, according to one embodiment.

Referring to FIG. 11A, in operation 1101, the Near-RT RIC 1020 may transmit an audit request message to the E2 node 1010. The subscription request message may include a transaction ID. The transaction ID can uniquely identify a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure must use the same transaction ID. The transaction ID may be determined by the initiating peer of the procedure. In Figure 11A, the transaction ID may be determined by Near-RT RIC 1020. For example, the inspection request message may have the format shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33

'M' stands for 'mandatory' and 'O' stands for 'optional'.

In operation 1103, the E2 node 1010 may transmit an audit response message to the Near-RT RIC 1020. The check response message may include a transaction ID, RAN function ID (e.g., RIC Function ID in Tables 1 to 4), and RIC request ID (e.g., RIC Request ID in Tables 1 to 4). The test response message may be a response to the test request message. According to one embodiment, the inspection response message may include the transaction ID of the inspection request message. RAN Function ID and RIC Request ID may be used to identify the subscription process. According to one embodiment, the check response message may include one or more subscription information. Each subscription information may correspond to a subscription procedure. Each subscription information may include a RAN function ID and a RIC request ID. The check response message may include a set of RAN function ID and RIC request ID. For example, the test response message may have the format shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 Subscription List One >Subscription Item 0..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8

'M' stands for 'mandatory' and 'O' stands for 'optional'. 'maxofRICRequestID' may mean the maximum number of RIC subscription requests to the E2 node (1010) supported by the Near-RT RIC (1020). For example, 'maxofRICRequestID' could be 1024. The IE for 'Message Type' in Tables 5 and 6 may have the format as shown in the table below.

IE/Group Name Presence Range IE types and references Semantics description Message Type >Procedure Code M >Type of Message M CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...)

'M' stands for 'mandatory' and 'O' stands for 'optional'.

Near-RT RIC (1020) can obtain subscription status related to the E2 node (1010) by performing an inspection request. The Near-RT RIC (1020) can compare the subscription information of the E2 node (1010) with the subscription information of the Near-RT RIC (1020) through the check response message. If a discrepancy occurs as a result of the comparison, the Near-RT RIC (1020) may delete the subscription information according to the discrepancy or perform a deletion request procedure. According to one embodiment, the Near-RT RIC (1020) may delete the subscription information of the Near-RT RIC (1020) that does not match the subscription information of the E2 node (1010) from the internal block. Additionally, according to one embodiment, the Near-RT RIC (1020) may transmit a request message for deletion of specific subscription information to the E2 node (1010). Additionally, according to one embodiment, Near-RT RIC 1020 may perform a RIC subscription procedure corresponding to deleted RIC subscription information.

According to one embodiment, the Near-RT RIC (1020) may transmit to the E2 node (1010) the check request message to indicate what subscription information to request. For example, the inspection request message may include one or more subscription information. Each subscription information may correspond to a subscription procedure. Each subscription information may include a RAN function ID and/or RIC request ID. For example, the inspection request message may have a format as shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 RIC subscription list One >RIC subscription item 0.. <maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 >>RAN Function Revision M 9.2.24

'RIC subscription List' IE may indicate a list of RIC subscription(s) for requesting subscription check. 'RIC Request ID' IE may indicate the RIC request ID. 'RAN Function ID' IE may indicate the RAN function ID. 'RAN Function Revision' IE may represent a revision counter.

The E2 node 1010 may transmit a subscription response message to the Near-RT RIC 1020 in response to the subscription request message of the Near-RT RIC 1020. The subscription response message may include a response result to the requested subscription information. For example, the subscription response message may include subscription information mapped in the E2 node 1010. Additionally, for example, the subscription response message may include unknown subscription information indicating subscriptions that have not been confirmed by the E2 node 1010. Additionally, for example, the subscription response message may include subscription information missing from the E2 node 1010. For example, the test response message may have a format as shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 Mapped Subscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 Unknown Subscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 MissedSubscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8

'Mapped Subscription List' IE may indicate the mapped subscription information. Here, the mapped subscription information may indicate subscriptions for which mapping to the RAN function ID and RIC request ID in the E2 node 1010 has been confirmed among subscriptions for which inspection has been requested. 'Unknown Subscription List' IE may display the unknown subscription information. The unknown subscription information may indicate subscriptions that are difficult to confirm because they are not stored in the E2 node 1010 among subscriptions for which inspection has been requested. The E2 node 1010 may transmit a subscription response message including a RAN function ID and RIC request ID for each subscription, which are difficult to confirm, to the Near-RT RIC 1020. 'Missed Subscription List' IE may indicate the missing subscription information. The missing subscription information may indicate subscriptions that are inaccurate because the information stored in the E2 node 1010 is different from the requested information among subscriptions for which inspection has been requested. For example, the E2 node 1010 compares the subscription information of the E2 node 1010 with the subscription information of the Near-RT RIC 1020, and sends a subscription response message containing the subscription information of the subscription in which the discrepancy occurred as a subscription response message. Can be transmitted to Near-RT RIC (1020). The subscription information may include a RAN function ID and RIC request ID for each inconsistent subscription.

FIG. 11B shows an example of a subscription check procedure between a Near-RT RIC and an E2 node, according to one embodiment.

Referring to FIG. 11B, in operation 1151, the E2 node 1010 may transmit an audit request message to the Near-RT RIC 1020. The subscription request message may include a transaction ID. The transaction ID can uniquely identify a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure must use the same transaction ID. The transaction ID may be determined by the initiating peer of the procedure. In Figure 11A, the transaction ID may be determined by E2 node 1010. For example, the inspection request message may have the format shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33

'M' stands for 'mandatory' and 'O' stands for 'optional'.

In operation 1153, the Near-RT RIC 1020 may transmit an audit response message to the E2 node 1010. The check response message may include a transaction ID, RAN function ID (e.g., RIC Function ID in Tables 1 to 4), and RIC request ID (e.g., RIC Request ID in Tables 1 to 4). The test response message may be a response to the test request message. According to one embodiment, the inspection response message may include the transaction ID of the inspection request message. RAN Function ID and RIC Request ID may be used to identify the subscription process. According to one embodiment, the check response message may include one or more subscription information. Each subscription information may correspond to a subscription procedure. Each subscription information may include a RAN function ID and a RIC request ID. The check response message may include a set of RAN function ID and RIC request ID. For example, the test response message may have the format shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 Subscription List One >Subscription Item 0..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8

'M' stands for 'mandatory' and 'O' stands for 'optional'. 'maxofRICRequestID' may mean the maximum number of RIC subscription requests to the E2 node (1010) supported by the Near-RT RIC (1020). For example, 'maxofRICRequestID' could be 1024. The IE for 'Message Type' in Tables 8 and 9 may have the same format as Table 7.

The E2 node 1010 can obtain the subscription status of the Near-RT RIC (1020) by performing an inspection request. The E2 node 1010 can compare the subscription information of the E2 node 1010 with the subscription information of the Near-RT RIC 1020 through the check response message from the Near-RT RIC 1020. If a discrepancy occurs as a result of the comparison, the E2 node 1010 may delete the subscription information according to the discrepancy or perform a delete required procedure. According to one embodiment, the E2 node 1010 may delete the subscription information of the E2 node 1010 that does not match the subscription information of the Near-RT RIC 1020 from the internal block. Additionally, according to one embodiment, the E2 node 1010 sends a delete required message to the Near-RT RIC 1020 to request deletion of the RIC subscription(s) existing in the E2 node 1010. Can be transmitted. Additionally, according to one embodiment, Near-RT RIC 1020 may perform a RIC subscription procedure corresponding to deleted RIC subscription information.

According to one embodiment, the E2 node 1010 may transmit the check request message to the Near-RT RIC 1020 to indicate what subscription information to request. For example, the inspection request message may include one or more subscription information. Each subscription information may correspond to a subscription procedure. Each subscription information may include a RAN function ID and/or RIC request ID. For example, the inspection request message may have a format as shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 RIC subscription list One >RIC subscription item 0.. <maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 >>RAN Function Revision M 9.2.24

'RIC subscription List' IE may indicate a list of RIC subscription(s) for requesting subscription check. 'RIC Request ID' IE may indicate the RIC request ID. 'RAN Function ID' IE may indicate the RAN function ID. 'RAN Function Revision' IE may represent a revision counter.

Near-RT RIC (1020) may transmit a subscription response message to the E2 node (1010) in response to the subscription request message of the E2 node (1010). The subscription response message may include a response result to the requested subscription information. For example, the subscription response message may include subscription information mapped in the Near-RT RIC (1020). Additionally, for example, the subscription response message may include unknown subscription information indicating subscriptions that have not been confirmed by the Near-RT RIC 1020. Additionally, for example, the subscription response message may include subscription information missing from the Near-RT RIC (1020). For example, the test response message may have a format as shown in the table below.

IE/Group Name Presence Range IE types and references Message Type M 9.2.3 Transaction ID M 9.2.33 Mapped Subscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 Unknown Subscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8 MissedSubscription List 0..1 >Subscription Item 1..<maxofRICRequestID> >>RIC Request ID M 9.2.7 >>RAN Function ID M 9.2.8

'Mapped Subscription List' IE may indicate the mapped subscription information. Here, the mapped subscription information may indicate subscriptions for which mapping to a RAN function ID and RIC request ID has been confirmed in the Near-RT RIC (1020) among subscriptions for which inspection has been requested. 'Unknown Subscription List' IE may display the unknown subscription information. The unknown subscription information may indicate subscriptions that are difficult to confirm because they are not stored in the Near-RT RIC (1020) among subscriptions for which inspection has been requested. Near-RT RIC (1020) may transmit a subscription response message including a RAN function ID and RIC request ID for each subscription that are difficult to confirm to the E2 node (1010). 'Missed Subscription List' IE may indicate the missing subscription information. The missing subscription information may indicate subscriptions that, among subscriptions for which inspection has been requested, are inaccurate because the information stored in the Near-RT RIC 1020 is different from the requested information. For example, the Near-RT RIC (1020) compares the subscription information of the Near-RT RIC (1020) with the subscription information of the E2 node (1010) and sends a subscription response message containing the subscription information of the subscription where the mismatch occurred. A response message can be transmitted to the E2 node (1010). The subscription information may include a RAN function ID and RIC request ID for each inconsistent subscription.

Figure 12A shows an example of a subscription check procedure triggered by activity time, according to one embodiment. Activity time may refer to the time period of periodic signaling or the length of a timer indicating inactivity.

Referring to Figure 12A, at step 1210, an E2 setup procedure may be performed. The E2 node 1010 may transmit an E2 setup request message to the Near-RT RIC (1020). Near-RT RIC (1020) can receive an E2 setup response message from the E2 node (1010). One or more RAN functions may be configured in the E2 node 1010 through the E2 setup procedure.

At step 1220, one or more RIC subscription procedures may be performed. Near-RT RIC (1020) can subscribe to services corresponding to RAN functions through the RIC subscription procedure. For example, the Near-RT RIC (1020) may perform the first RIC subscription procedure (1221) with the E2 node (1010). Near-RT RIC 1020 may transmit a subscription request message including a first RAN ID and a first RIC request ID to the E2 node 1010. Near-RT RIC (1020) may receive a subscription response message from the E2 node (1010). The subscription response message may include the first RAN ID and the first RIC request ID. Near-RT RIC (1020) can perform a second RIC subscription procedure (1223) with the E2 node (1010). Near-RT RIC 1020 may transmit a subscription request message including a second RAN ID and a second RIC request ID to the E2 node 1010. Near-RT RIC (1020) may receive a subscription response message from the E2 node (1010). The subscription response message may include the second RAN ID and the second RIC request ID.

At step 1230, a specified amount of time may elapse from the most recently performed signaling. To achieve reliable synchronization for RIC subscriptions, if there has been no signaling for a certain period of time, a RIC subscription check procedure may be performed. The most recently performed signaling may include the last transmitted or received message among all procedures related to RIC subscriptions. According to one embodiment, Near-RT RIC 1020 may periodically perform a RIC subscription check procedure. That is, the Near-RT RIC 1020 can identify that the specified time has elapsed after the last RIC subscription inspection request message was transmitted. Additionally, according to one embodiment, Near-RT RIC 1020 may be configured to perform periodic reporting. E2 node 1010 may identify that the specified time has elapsed since the last report of Near-RT RIC 1020. E2 node 1010 may trigger the RIC subscription check procedure. Additionally, according to one embodiment, the E2 node 1010 may use a timer for operation time. When E2 node 1010 receives the message, it can start a timer. Each time the E2 node 1010 receives a message, it can restart the timer. E2 node 1010 may trigger the RIC subscription check procedure when the timer elapses.

At step 1240, a RIC subscription check procedure may be performed. E2 node 1010 may initiate a RIC subscription check procedure based on identifying that a specified amount of time has elapsed from signaling. In operation 1241, the E2 node 1010 may transmit a RIC subscription check request message to the Near-RT RIC 1020. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. In operation 1243, the Near-RT RIC 1020 may transmit a RIC subscription check response message to the E2 node 1010. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. According to one embodiment, the RIC subscription check response message may include information about one or more RIC subscriptions (eg, RIC subscription list). For example, the RIC subscription check response message includes the first RAN function ID and the first RIC request ID of the first RIC subscription procedure 1221 and the second RAN function ID and the second RIC of the second RIC subscription procedure 1223. May include a request ID.

Although the subscription check procedure initiated by the E2 node 1010 is illustrated in FIG. 12A, embodiments of the present disclosure are not limited thereto. According to one embodiment, based on identifying that a certain amount of time has elapsed, Near-RT RIC 1020 may initiate a subscription check procedure. For example, the Near-RT RIC 1020, which has not received a RIC indication for the given period of time, may initiate a subscription check procedure.

Figure 12B shows an example of a subscription check procedure initiated based on an event, according to one embodiment.

Referring to FIG. 12B, at step 1260, an E2 setup procedure may be performed. The E2 node 1010 may transmit an E2 setup request message to the Near-RT RIC (1020). Near-RT RIC (1020) can receive an E2 setup response message from the E2 node (1010). One or more RAN functions may be configured in the E2 node 1010 through the E2 setup procedure.

At step 1270, one or more RIC subscription procedures may be performed. Near-RT RIC (1020) can subscribe to services corresponding to RAN functions through the RIC subscription procedure. For example, the Near-RT RIC 1020 may perform the first RIC subscription procedure 1271 with the E2 node 1010. Near-RT RIC 1020 may transmit a subscription request message including a first RAN ID and a first RIC request ID to the E2 node 1010. Near-RT RIC (1020) may receive a subscription response message from the E2 node (1010). The subscription response message may include the first RAN ID and the first RIC request ID. Near-RT RIC (1020) can perform the second RIC subscription procedure (1273) with the E2 node (1010). Near-RT RIC 1020 may transmit a subscription request message including a second RAN ID and a second RIC request ID to the E2 node 1010. Near-RT RIC (1020) may receive a subscription response message from the E2 node (1010). The subscription response message may include the second RAN ID and the second RIC request ID.

At step 1230, a specific event may occur. Specific events may include the fulfillment of conditions to trigger the RIC subscription inspection process. According to one embodiment, Near-RT RIC 1020 may identify the specific event. For example, Near-RT RIC 1020 may identify that at least one functional block of Near-RT RIC 1020 changes from an inactive state to an active state. Near-RT RIC 1020 may initiate a subscription check procedure instead of a reset procedure. Additionally, for example, the Near-RT RIC 1020 may identify that indication information is received from the E2 node 1010 or another entity. The indication information may include status information about the RIC subscription(s), status information of the Near-RT RIC 1020 (e.g., error, reactivation, memory reallocation), or status information of the E2 node 1010 (e.g., may include at least one of error, reactivation, and memory reallocation). Near-RT RIC 1020 may initiate a subscription check procedure. In addition, for example, the Near-RT RIC 1020 may identify that it does not receive a subscription response message or a subscription failure message corresponding to the transmission of the subscription request message within a certain period of time after transmitting the subscription request message. You can. Near-RT RIC 1020 may initiate a subscription check procedure before performing the RIC subscription delete procedure.

In Figure 12b, the RIC subscription check procedure initiated by the Near-RT RIC 1020 is illustrated, but the RIC subscription check procedure may also be initiated by the E2 node 1010. The E2 node 1010 can detect the occurrence of a specific event in the same way. For the operations of the examples described above, Near-RT RIC 1020 may be replaced with E2 node 1010.

At step 1240, a RIC subscription check procedure may be performed. Near-RT RIC 1020 may initiate a RIC subscription check procedure based on identifying the occurrence of a specific event. In operation 1291, the Near-RT RIC 1020 may transmit a RIC subscription check request message to the E2 node 1010. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. In operation 1293, the E2 node 1010 may transmit a RIC subscription check response message to the Near-RT RIC 1020. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. According to one embodiment, the RIC subscription check response message may include information about one or more RIC subscriptions (eg, RIC subscription list). For example, the RIC subscription check response message includes the first RAN function ID and the first RIC request ID of the first RIC subscription procedure 1271 and the second RAN function ID and the second RIC of the second RIC subscription procedure 1273. May include a request ID.

In FIG. 12B, a subscription check procedure initiated by the Near-RT RIC 1020 is illustrated, but embodiments of the present disclosure are not limited thereto. According to one embodiment, based on identifying the occurrence of a specific event, E2 node 1010 may initiate a subscription check procedure.

13 shows an example of subscription management using a subscription check procedure, according to one embodiment. In FIG. 13, the inspection procedure or periodic inspection procedure according to rebooting of the subscription manager of the Near-RT RIC (e.g., Near-RT RIC (1020)) is described. RIC subscriptions may be established through one or more subscription procedures between the Near-RT RIC 1020 and the E2 node (e.g., the E2 node 1010).

Referring to FIG. 13, E2 node 1010 has subscription information 1310-a. Subscription information 1310-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1310-a of the E2 node 1010 may include information about three RIC subscriptions. The subscription information 1310-a of the E2 node 1010 includes [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}].

Near-RT RIC 1020 has subscription information 1320-a. Subscription information 1320-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1320-a of the Near-RT RIC 1020 may include information about four RIC subscriptions. The subscription information (1320-a) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In operation 1311, the Near-RT RIC 1020 may transmit a RIC subscription check request ('AUDIT REQUEST') message to the E2 node 1010. Based on configuration information for RIC subscription check (e.g., elapse of a certain time in FIG. 12A or occurrence of a specific event in FIG. 12B), Near-RT RIC 1020 can initiate a subscription check procedure. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check request message including a transaction ID indicating '3'.

In operation 1313, the E2 node 1010 may transmit a RIC subscription check response ('AUDIT RESPONSE') message to the Near-RT RIC 1020. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. For example, E2 node 1010 may transmit a RIC subscription check response message including a transaction ID indicating '3'. The E2 node 1010 may include the subscription information 1310-a of the E2 node 1010 in the RIC subscription check response message. The RIC subscription check response message is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}] It may contain a composed list. Near-RT RIC 1020 may obtain subscription information 1310-a of the E2 node 1010 from the RIC subscription check response message.

In operation 1315, the Near-RT RIC 1020 may compare the subscription information 1310-a of the E2 node 1010 and the subscription information 1320-a of the Near-RT RIC 1020. The Near-RT RIC 1020 may identify that the subscription information 1320-a of the Near-RT RIC 1020 is inconsistent with the subscription information 1310-a of the E2 node 1010. As a result of comparison, the subscription information (1320-a) of the Near-RT RIC (1020) corresponds to 'RIC Request ID: 2' compared to the subscription information (1310-a) of the E2 node (1010). It can be identified that it further includes RIC membership.

In operation 1317, Near-RT RIC 1020 may delete the RIC subscription corresponding to 'RIC Request ID: 2' and 'RIC Request ID: 2'.

The subscription information (1310-b) of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}]. By operation 1317, subscription information 1320-a of the Near-RT RIC 1020 may be updated with subscription information 1320-b. The subscription information (1320-b) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In Figure 13, a procedure for matching the subscription information of the E2 node 1010 and the subscription information of the Near-RT RIC (1020) is described. Although not shown in FIG. 13, the RIC subscription procedure corresponding to 'RIC Request ID: 2' deleted due to mismatch, that is, the RIC subscription procedure, may be additionally performed. Near-RT RIC (1020) is based on RIC subscription information (e.g., 'RIC Request ID: 2', RAN Function ID: 1) registered in the subscription manager of Near-RT RIC (1020), You can perform the RIC membership process. According to one embodiment, Near-RT RIC 1020 may transmit a RIC subscription request message (e.g., RIC SUBSCRIPTION REQUEST message) containing RIC subscription information corresponding to 'RIC Request ID: 2'. The RIC subscription request message may include information about the RAN function (e.g., RAN Function ID: 1). The E2 node 1010 may transmit a RIC subscription response message (e.g., RIC SUBSCRIPTION RESPONSE message) to the Near-RT RIC 1020.

14 illustrates an example of subscription management using a subscription check procedure, according to one embodiment. In Figure 14, the inspection procedure or periodic inspection procedure according to the reboot of the subscription manager of the Near-RT RIC (e.g., the Near-RT RIC 1020) is described. Near-RT RIC (1020) and the E2 node RIC subscriptions may be established through one or more subscription procedures between (e.g., E2 node 1010).

Referring to FIG. 14, E2 node 1010 has subscription information 1410-a. Subscription information 1410-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1410-a of the E2 node 1010 may include information about four RIC subscriptions. The subscription information 1410-a of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, It may include a list consisting of RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

Near-RT RIC 1020 has subscription information 1420-a. Subscription information 1420-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1420-a of the Near-RT RIC 1020 may include information about three RIC subscriptions. The subscription information (1420-a) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In operation 1411, the Near-RT RIC 1020 may transmit a RIC subscription check request ('AUDIT REQUEST') message to the E2 node 1010. Based on configuration information for RIC subscription check (e.g., elapse of a certain time in FIG. 12A or occurrence of a specific event in FIG. 12B), Near-RT RIC 1020 can initiate a subscription check procedure. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check request message including a transaction ID indicating '3'.

In operation 1413, the E2 node 1010 may transmit a RIC subscription check response ('AUDIT RESPONSE') message to the Near-RT RIC 1020. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. For example, E2 node 1010 may transmit a RIC subscription check response message including a transaction ID indicating '3'. The E2 node 1010 may include the subscription information 1410-a of the E2 node 1010 in the RIC subscription check response message. The RIC subscription check response message is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, { It may include a list consisting of [RIC Request ID: 4, RAN Function ID: 4}]. Near-RT RIC 1020 may obtain subscription information 1410-a of the E2 node 1010 from the RIC subscription check response message.

In operation 1415, the Near-RT RIC 1020 may compare the subscription information 1410-a of the E2 node 1010 and the subscription information 1420-a of the Near-RT RIC 1020. The Near-RT RIC 1020 may identify that the subscription information 1420-a of the Near-RT RIC 1020 is inconsistent with the subscription information 1410-a of the E2 node 1010. As a result of comparison, the subscription information (1420-a) of the Near-RT RIC (1020) corresponds to 'RIC Request ID: 2' compared to the subscription information (1410-a) of the E2 node (1010). You can identify that it does not include RIC membership. Near-RT RIC (1020) may request the E2 node (1010) to delete the RIC subscription corresponding to 'RIC Request ID: 2'. Near-RT RIC (1020) can perform a RIC Subscription Delete procedure with the E2 node (1010).

In operation 1417, the Near-RT RIC 1020 may transmit a subscription deletion request ('RIC SUBSCRIPTION DELETE REQUEST') message to the E2 node 1010. The subscription deletion request message may include inconsistent subscription information. The subscription deletion request message may include a RIC request ID and a RAN function ID. For example, the subscription deletion request message may have the format of the table below. For example, according to the format of the table below, the RIC Request ID of the subscription deletion request message may indicate '2', and the RAN Function ID of the subscription deletion request message may indicate '1'.

IE/Group Name Presence Range IE types and references Semantics
description Criticality Assigned
Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject

'M' stands for 'mandatory' and 'O' stands for 'optional'. IE for 'Message Type' may have the format shown in Table 7.

In operation 1419, the E2 node 1010 may delete the RIC subscription corresponding to 'RIC Request ID: 2' and 'RIC Request ID: 2'. The E2 node 1010 can determine a target function using information in the RAN Function ID and delete the corresponding RIC event trigger using information in the RIC Request ID. By operation 1419, subscription information 1410-a of the E2 node 1010 may be updated with subscription information 1410-b.

In operation 1421, the E2 node 1010 may transmit a subscription deletion response ('RIC SUBSCRIPTION DELETE RESPONSE') message to the Near-RT RIC 1020. The subscription deletion response message can be used to accept a request from the Near-RT RIC 1020 and delete an existing subscription in the E2 node 1010. For example, the subscription deletion response message may have the format of the table below. For example, according to the format of the table below, the RIC Request ID of the subscription deletion response message may indicate '2', and the RAN Function ID of the subscription deletion response message may indicate '1'.

IE/Group Name Presence Range IE types and references Semantics
description Criticality Assigned
Criticality Message Type M 9.2.3 YES reject RIC Request ID M 9.2.7 YES reject RAN Function ID M 9.2.8 YES reject

'M' stands for 'mandatory' and 'O' stands for 'optional'. IE for 'Message Type' may have the format shown in Table 7.

The subscription information (1410-b) of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}]. The subscription information (1420-b) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

Figure 15 shows an example of subscription management using a subscription check procedure, according to one embodiment. In FIG. 15, a test procedure or a periodic test procedure according to rebooting of a software block of an E2 node (e.g., E2 node 1010) is described. RIC subscriptions may be established through one or more subscription procedures between the E2 node 1010 and the Near-RT RIC (e.g., Near-RT RIC 1020).

Referring to FIG. 15, E2 node 1010 has subscription information 1510-a. Subscription information 1510-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1510-a of the E2 node 1010 may include information about three RIC subscriptions. The subscription information 1510-a of the E2 node 1010 includes [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}].

Near-RT RIC 1020 has subscription information 1520-a. Subscription information 1520-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1520-a of the Near-RT RIC 1020 may include information about four RIC subscriptions. The subscription information (1520-a) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In operation 1511, the E2 node 1010 may transmit a RIC subscription check request ('AUDIT REQUEST') message to the Near-RT RIC 1020. Based on configuration information for RIC subscription check (e.g., elapse of a certain time in FIG. 12A or occurrence of a specific event in FIG. 12B), Near-RT RIC 1020 can initiate a subscription check procedure. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check request message including a transaction ID indicating '3'.

In operation 1513, the Near-RT RIC 1020 may transmit a RIC subscription check response ('AUDIT RESPONSE') message to the E2 node 1010. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check response message including a transaction ID indicating '3'. Near-RT RIC 1020 may include subscription information 1520-a of Near-RT RIC 1020 in the RIC subscription check response message. The RIC subscription check response message is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, { It may include a list consisting of [RIC Request ID: 4, RAN Function ID: 4}]. The E2 node 1010 may obtain subscription information 1520-a of the Near-RT RIC 1020 from the RIC subscription check response message.

In operation 1515, the E2 node 1010 may compare the subscription information 1510-a of the E2 node 1010 and the subscription information 1520-a of the Near-RT RIC 1020. The E2 node 1010 may identify that the subscription information 1520-a of the Near-RT RIC 1020 does not match the subscription information 1510-a of the E2 node 1010. As a result of comparison, the subscription information (1520-a) of the Near-RT RIC (1020) compared to the subscription information (1510-a) of the E2 node (1010) is the RIC corresponding to 'RIC Request ID: 2'. It is possible to identify points that further include subscriptions.

In operation 1517, the E2 node 1010 may transmit a subscription deletion request ('RIC SUBSCRIPTION DELETE REQUIRED') message to the Near-RT RIC 1020. The subscription deletion request message allows the E2 node 1010 to request deletion of the existing RIC subscription(s) of the E2 node 1010, previously created for the Near-RT RIC 1020 ( enable) can be used. The subscription deletion request message may include inconsistent subscription information. The subscription deletion request message may include a RIC request ID and a RAN function ID. The subscription deletion request message may include information on the cause for each RIC subscription requesting removal. For example, the subscription deletion request message may have the format of the table below. For example, according to the format of the table below, the RIC Request ID of the subscription deletion request message may indicate '2', and the RAN Function ID of the subscription deletion request message may indicate '1'.

IE/Group Name Presence Range IE types and references Semantics
description Criticality Assigned
Criticality Message Type M 9.2.3 YES reject List of RIC Subscriptions To Be Removed 1..<maxofRICreque
stID> EACH Ignore >RIC Request ID M 9.2.7 YES reject >RAN Function ID M 9.2.8 YES reject >Cause

'M' stands for 'mandatory' and 'O' stands for 'optional'. IE for 'Message Type' may have the format shown in Table 7. 'Cause' IE may refer to Table 13 below.

IE/Group Name Presence Range IE types and references Semantics
description CHOICE Cause Group >RIC services >>RIC Request O ENUMERATED (RAN Function ID invalid,
Action not supported,
Excessive actions,
Duplicate action,
Duplicate Event Trigger,
Function resource limit,
RIC Request ID unknown,
Inconsistent Action/subsequent Action sequence,
Control message invalid,
RIC Call process ID invalid,
Control timer expired,
Control failed to execute,
System not ready,
unspecified, ??) >>RIC Service O ENUMERATED RAN Function not supported,
Excessive functions,
RIC resource limit, ??) >>E2 node O ENUMERATED (E2 node component unknown, ??) >Transport Layer >>Transport Layer Cause M >Protocol >>Protocol Cause M ENUMERATED (Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Abstract Syntax Error (Falsely Constructed Message),
Unspecified, ...) >Misc >>Miscellaneous Cause M ENUMERATED (Control Processing Overload,
Hardware Failure,
O&M Intervention,
Unspecified, ...)

In operation 1519, the Near-RT RIC 1020 may transmit a subscription deletion request ('RIC SUBSCRIPTION DELETE REQUEST') message to the E2 node 1010. The subscription deletion request message may include inconsistent subscription information. The subscription deletion request message may include a RIC request ID and a RAN function ID. For example, the subscription deletion request message may have the format of Table 10. The RIC Request ID of the subscription deletion request message may indicate '2', and the RAN Function ID of the subscription deletion request message may indicate '1'.

In operation 1521, the E2 node 1010 may transmit a 'RIC SUBSCRIPTION DELETE FAILURE' message to the Near-RT RIC 1020. For example, the subscription deletion response message may have the format of Table 11. The RIC Request ID of the subscription deletion response message may indicate '2', and the RAN Function ID of the subscription deletion response message may indicate '1'. According to one embodiment, the subscription deletion failure message may include reason information. The reason information is 'Cause' IE, and Table 13 may be referred to. According to one embodiment, the E2 node 1010 may transmit a subscription deletion failure message including reason information set to 'RIC Request ID unknown' to the Near-RT RIC 1020.

In operation 1523, Near-RT RIC 1020 may delete the RIC subscription corresponding to 'RIC Request ID: 2' and 'RIC Request ID: 2'.

The subscription information (1510-b) of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}]. Through operations 1517 to 1521, subscription information 1520-a of the Near-RT RIC 1020 may be updated to subscription information 1520-b. The subscription information (1520-b) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In FIG. 15, a procedure for matching the subscription information of the E2 node 1010 and the subscription information of the Near-RT RIC (1020) is described. Although not shown in FIG. 15, the RIC subscription procedure corresponding to 'RIC Request ID: 2' deleted due to mismatch, that is, the RIC subscription procedure, may be additionally performed. Near-RT RIC (1020) is based on RIC subscription information (e.g., 'RIC Request ID: 2', RAN Function ID: 1) registered in the subscription manager of Near-RT RIC (1020), You can perform the RIC membership process. According to one embodiment, Near-RT RIC 1020 may transmit a RIC subscription request message (e.g., RIC SUBSCRIPTION REQUEST message) containing RIC subscription information corresponding to 'RIC Request ID: 2'. The RIC subscription request message may include information about the RAN function (e.g., RAN Function ID: 1). The E2 node 1010 may transmit a RIC subscription response message (e.g., RIC SUBSCRIPTION RESPONSE message) to the Near-RT RIC 1020.

16 illustrates an example of subscription management using a subscription check procedure, according to one embodiment. In FIG. 16, a test procedure or a periodic test procedure according to rebooting of a software block of an E2 node (e.g., E2 node 1010) is described. RIC subscriptions may be established through one or more subscription procedures between the E2 node 1010 and the Near-RT RIC (e.g., Near-RT RIC 1020).

Referring to FIG. 16, E2 node 1010 has subscription information 1610-a. Subscription information 1610-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1610-a of the E2 node 1010 may include information about four RIC subscriptions. The subscription information 1610-a of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 2, RAN Function ID: 1}, {RIC Request ID: 3, It may include a list consisting of RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

Near-RT RIC 1020 has subscription information 1620-a. Subscription information 1620-a may include information about one or more RIC subscriptions. RIC subscription can be specified by RAN function ID (i.e., RAN Function ID) and RIC request ID (i.e., RIC Request ID). For example, the subscription information 1620-a of the Near-RT RIC 1020 may include information about three RIC subscriptions. The subscription information (1620-a) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In operation 1611, the E2 node 1010 may transmit a RIC subscription check request ('AUDIT REQUEST') message to the Near-RT RIC 1020. Based on configuration information for RIC subscription check (e.g., elapse of a certain time in FIG. 12A or occurrence of a specific event in FIG. 12B), Near-RT RIC 1020 can initiate a subscription check procedure. For the RIC subscription check request message, Table 5, Table 8, Table 10, or Table 12 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check request message including a transaction ID indicating '3'.

In operation 1613, the Near-RT RIC 1020 may transmit a RIC subscription check response ('AUDIT RESPONSE') message to the E2 node 1010. For the RIC subscription check response message, Table 6, Table 9, Table 11, or Table 13 may be referred to. For example, Near-RT RIC 1020 may transmit a RIC subscription check response message including a transaction ID indicating '3'. Near-RT RIC 1020 may include subscription information 1620-a of Near-RT RIC 1020 in the RIC subscription check response message. The RIC subscription check response message is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}] It may contain a composed list. The E2 node 1010 may obtain subscription information 1620-a of the Near-RT RIC 1020 from the RIC subscription check response message.

In operation 1615, the E2 node 1010 may compare the subscription information 1610-a of the E2 node 1010 and the subscription information 1620-a of the Near-RT RIC 1020. The E2 node 1010 may identify that the subscription information 1620-a of the Near-RT RIC 1020 does not match the subscription information 1610-a of the E2 node 1010. As a result of comparison, the subscription information (1620-a) of the Near-RT RIC (1020) compared to the subscription information (1610-a) of the E2 node (1010) is the RIC corresponding to 'RIC Request ID: 2'. It is possible to identify points that further include subscriptions.

In operation 1617, the E2 node 1010 may delete the RIC subscription corresponding to 'RIC Request ID: 2' and 'RIC Request ID: 2'. The subscription information (1610-b) of the E2 node 1010 is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, It may contain a list consisting of [RAN Function ID: 4}]. The subscription information (1620-b) of Near-RT RIC (1020) is [{RIC Request ID: 1, RAN Function ID: 1}, {RIC Request ID: 3, RAN Function ID: 2}, {RIC Request ID: 4, RAN Function ID: 4}].

In this disclosure, an audit procedure is described as a procedure for confirming RIC subscription information. The term 'audit' for the above-described operations can be used in other words with equivalent technical meanings such as 'confirmation', 'examination', 'status request/report', etc. It can be replaced by the term

In embodiments, the method performed by the E2 node may include transmitting an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). . The method may include receiving a test response message from the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

According to one embodiment, the inspection request message may include a transaction ID. The check response message may include the transaction ID.

According to one embodiment, the inspection request message is sent to the Near-RT RIC based on the arrival of a specified period or identifying rebooting of the functional block of the E2 node. can be transmitted.

According to one embodiment, the method may include receiving a RIC subscription deletion request message from the Near-RT RIC. The method may include transmitting a RIC subscription deletion response message to the Near-RT RIC. The RIC subscription deletion request message is information about the RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. may include. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

According to one embodiment, the method may include receiving a RIC subscription request message from the Near-RT RIC. The method may include transmitting a RIC subscription response message to the Near-RT RIC. The RIC subscription request message includes information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. It can be included. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

In embodiments, a method performed by Near-RT (real time) RIC may include transmitting an audit request message to the E2 node. The method may include receiving a check response message from the E2 node. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

According to one embodiment, the inspection request message may include a transaction ID. The check response message may include the transaction ID.

According to one embodiment, the inspection request message is to be transmitted to the E2 node based on the arrival of a specified period or identifying rebooting of a functional block of the E2 node. You can.

According to one embodiment, the method may include transmitting a RIC subscription deletion request message to the E2 node. The method may include receiving a RIC subscription deletion response message from the E2 node. The RIC subscription deletion request message is information about the RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. may include. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

According to one embodiment, the method may include transmitting a RIC subscription request message to the E2 node. The method may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message includes information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. It can be included. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

In embodiments, a method performed by an E2 node may include receiving an audit request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). . The method may include transmitting a test response message to the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

According to one embodiment, the inspection request message may include a transaction ID. The check response message may include the transaction ID.

According to one embodiment, the inspection request message is received from the Near-RT RIC based on the arrival of a specified period or identifying rebooting of the functional block of the E2 node. can be received.

According to one embodiment, the method may include receiving a RIC subscription deletion request message from the Near-RT RIC. The method may include transmitting a RIC subscription deletion response message to the Near-RT RIC. The RIC subscription deletion request message is information about the RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. may include. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

According to one embodiment, the method may include receiving a RIC subscription request message from the Near-RT RIC. The method may include transmitting a RIC subscription response message to the Near-RT RIC. The RIC subscription request message includes information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. It can be included. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

In embodiments, a method performed by Near-RT (real time) RIC may include receiving an audit request message from an E2 node. The method may include transmitting a check response message to the E2 node. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

According to one embodiment, the inspection request message may include a transaction ID. The check response message may include the transaction ID.

According to one embodiment, the inspection request message is to be received from the E2 node based on the arrival of a specified period or identifying rebooting of a functional block of the E2 node. You can.

According to one embodiment, the method may include transmitting a RIC subscription deletion request message to the E2 node. The method may include receiving a RIC subscription deletion response message from the E2 node. The RIC subscription deletion request message is information about the RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. may include. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

According to one embodiment, the method may include transmitting a RIC subscription request message to the E2 node. It may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message includes information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in the subscription manager of the Near-RT RIC. It can be included. The information may include a RAN function ID and RIC request ID corresponding to the RIC subscription.

In embodiments, the electronic device of the E2 node includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to transmit an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The at least one processor may control the at least one transceiver to receive a check response message from the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a Near-RT (real time) RIC electronic device includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to transmit an audit request message to the E2 node. The at least one processor may control the at least one transceiver to receive a test response message from the E2 node. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, the electronic device of the E2 node includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to receive an audit request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller). The at least one processor may control the at least one transceiver to transmit a check response message to the Near-RT RIC. The RIC subscription check response message may include one or more subscription information within the E2 node. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

In embodiments, a Near-RT (real time) RIC electronic device includes at least one transceiver; And it may include at least one processor coupled to the at least one transceiver. The at least one processor may control the at least one transceiver to receive an audit request message from the E2 node. The at least one processor may control the at least one transceiver to transmit a test response message to the E2 node. The RIC subscription check response message may include one or more subscription information within the Near-RT RIC. Each of the one or more pieces of subscription information may include a RAN function ID (identifier) and a RIC request ID for the corresponding RIC subscription.

The apparatus and method according to embodiments of the present disclosure are, in a wireless communication system, a radio access network (RAN) intelligent controller (RIC) (e.g., Near-RT RIC (1020)) is connected to an E2 node (e.g., E2 node (1010)). By requesting a subscription check from the RIC or the E2 node, resource efficiency can be improved by reducing the inconsistency in subscription information between the two nodes and preventing unnecessary procedures (e.g., reset procedures). By comparing the subscription information registered in the subscription manager of the Near-RT RIC with the subscription information stored in the software block of the E2 node, a procedure for deleting a RIC subscription or a RIC subscription request procedure can be performed. According to one embodiment, the procedure for deleting a RIC subscription of the present disclosure may include a RIC subscription deletion request procedure (i.e., a RIC subscription deletion request message and a RIC subscription deletion procedure) initiated by the E2 node. According to one embodiment, the procedure for deletion of a RIC subscription may include a RIC subscription deletion procedure (i.e., a RIC subscription deletion request message and a RIC subscription deletion response message) initiated by the Near-RT RIC. According to one embodiment, the RIC subscription request procedure may be initiated by Near-RT RIC and may include a RIC subscription request message and a RIC subscription response message.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program may be distributed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, 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, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure.

Claims (24)

The method performed by the E2 node is:
An operation of transmitting an audit request message to a Near-RT (real time) RIC (radio access network (RAN) intelligent controller),
Including the operation of receiving a test response message from the Near-RT RIC,
The RIC subscription check response message includes one or more subscription information in the Near-RT RIC,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
method.
In claim 1,
The inspection request message includes a transaction ID,
The check response message includes the transaction ID,
method.
In claim 1,
The inspection request message is transmitted to the Near-RT RIC based on the arrival of a specified period or identifying rebooting of the functional block of the E2 node.
method.
In claim 1,
An operation of receiving a RIC subscription deletion request message from the Near-RT RIC,
Further comprising transmitting a RIC subscription deletion response message to the Near-RT RIC,
The RIC subscription deletion request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
In claim 1,
An operation of receiving a RIC subscription request message from the Near-RT RIC,
Further comprising transmitting a RIC subscription response message to the Near-RT RIC,
The RIC membership request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
The method performed by Near-RT (real time) RIC is:
The operation of transmitting an audit request message to the E2 node,
Including the operation of receiving a check response message from the E2 node,
The RIC subscription check response message includes one or more subscription information within the E2 node,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
method.
In claim 6,
The inspection request message includes a transaction ID,
The check response message includes the transaction ID,
method.
In claim 6,
The inspection request message is transmitted to the E2 node based on the arrival of a specified period or identifying rebooting of a functional block of the E2 node.
method.
In claim 6,
An operation of transmitting a RIC subscription deletion request message to the E2 node,
Further comprising the operation of receiving a RIC subscription deletion response message from the E2 node,
The RIC subscription deletion request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
In claim 6,
An operation of transmitting a RIC subscription request message to the E2 node,
Further comprising receiving a RIC subscription response message from the E2 node,
The RIC membership request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
The method performed by the E2 node is:
An operation of receiving an audit request message from a Near-RT (real time) RIC (radio access network (RAN) intelligent controller),
Including transmitting a test response message to the Near-RT RIC,
The RIC subscription check response message includes one or more subscription information within the E2 node,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
method.
In claim 11,
The inspection request message includes a transaction ID,
The check response message includes the transaction ID,
method.
In claim 11,
The inspection request message is received from the Near-RT RIC based on the arrival of a specified period or identifying rebooting of the functional block of the E2 node.
method.
In claim 11,
An operation of receiving a RIC subscription deletion request message from the Near-RT RIC,
Further comprising transmitting a RIC subscription deletion response message to the Near-RT RIC,
The RIC subscription deletion request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
In claim 11,
An operation of receiving a RIC subscription request message from the Near-RT RIC,
Further comprising transmitting a RIC subscription response message to the Near-RT RIC,
The RIC membership request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
The method performed by Near-RT (real time) RIC is:
The operation of receiving an audit request message from the E2 node,
Including transmitting a check response message to the E2 node,
The RIC subscription check response message includes one or more subscription information in the Near-RT RIC,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
method.
In claim 16,
The inspection request message includes a transaction ID,
The check response message includes the transaction ID,
method.
In claim 16,
The inspection request message is received from the E2 node based on the arrival of a specified period or identifying rebooting of a functional block of the E2 node.
method.
In claim 16,
An operation of transmitting a RIC subscription deletion request message to the E2 node,
Further comprising the operation of receiving a RIC subscription deletion response message from the E2 node,
The RIC subscription deletion request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
In claim 16,
An operation of transmitting a RIC subscription request message to the E2 node,
Further comprising receiving a RIC subscription response message from the E2 node,
The RIC membership request message is:
Contains information on RIC subscription, identified based on the result of comparison of one or more subscription information in the E2 node and subscription information registered in a subscription manager of the Near-RT RIC,
The information includes a RAN function ID and a RIC request ID, corresponding to the RIC subscription.
method.
The electronics of the E2 node are:
at least one transceiver; and
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
Sends an audit request message to the Near-RT (real time) RIC (radio access network) intelligent controller,
To receive a test response message from the Near-RT RIC,
Controlling the at least one transceiver,
The RIC subscription check response message includes one or more subscription information in the Near-RT RIC,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
Electronic devices.
The electronic device of Near-RT (real time) RIC is,
at least one transceiver; and
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
Send an audit request message to the E2 node,
To receive a check response message from the E2 node,
Controlling the at least one transceiver,
The RIC subscription check response message includes one or more subscription information within the E2 node,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
Electronic devices.
The electronics of the E2 node are:
at least one transceiver; and
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
Receives an audit request message from a Near-RT (real time) RIC (radio access network) intelligent controller,
To transmit a test response message to the Near-RT RIC,
Controlling the at least one transceiver,
The RIC subscription check response message includes one or more subscription information within the E2 node,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
Electronic devices.
The electronic device of Near-RT (real time) RIC is,
at least one transceiver; and
Comprising at least one processor coupled to the at least one transceiver,
The at least one processor,
Receive an audit request message from the E2 node,
To transmit a check response message to the E2 node,
Controlling the at least one transceiver,
The RIC subscription check response message includes one or more subscription information in the Near-RT RIC,
Each subscription information of the one or more subscription information includes a RAN function ID (identifier) and RIC request ID for the corresponding RIC subscription,
Electronic devices.

Images