Apparatus and method for providing standard version

Abstract

The present disclosure relates to a 5th-Generation (5G) or pre-5G communication system for supporting a data transmission rate higher than that of a 4th-Generation (4G) communication system such as Long Term Evolution (LTE). In an embodiment, a method performed by an E2 node may include the operation of sending an E2 setup request message to a near real-time (RT) Radio Access Network (RAN) Intelligent Controller (RIC). The method may include the operation of receiving an E2 setup response message from the RIC. The E2 setup request message may include information for indicating an E2 interface between a near RT RIC and an E2 node among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer of the E2 interface.

Description

Technical Field

[0001] The present disclosure relates to an apparatus and method for providing a standard version. Background Art

[0002] Since the commercialization of the 4th generation (4G) communication system, the 5th generation (5G) communication system or quasi-5G communication system has been developed or improved to meet the growing demand for wireless data services. Therefore, the 5G communication system or quasi-5G communication system is often referred to as a super 4G network communication system or a post-LTE (Long Term Evolution) system.

[0003] In order to achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 gigahertz (GHz) bands). In addition, in order to mitigate the path loss of radio waves in the ultra-high frequency bands and increase the transmission distance of radio waves, advanced technologies for 5G communication systems such as beamforming, massive MIMO and full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are being discussed and developed.

[0004] In addition, in order to improve the network in the 5G communication system, technologies for evolved small cells and advanced small cells are being developed, such as cloud radio access network (cloud RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), reception interference cancellation, etc.

[0005] In addition, in 5G communication systems, advanced coding modulation (ACM) methods such as FQAM (hybrid frequency shift keying and quadrature amplitude modulation) and SWSC (sliding window superposition coding) are being developed. In addition, advanced access technologies such as FBMC (filter bank multi-carrier), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) are being developed.

[0006] In order to meet the needs of radio data services, 5G communication systems (NR (New Radio or Next Generation Radio)) have been commercialized. The 5G communication system provides high data rate services to users like the 4G communication system. In addition, the 5G communication system provides wireless communication services with various purposes (such as the Internet of Things (IoT) and services that require high reliability for specific purposes, etc.). In a system where the fourth-generation communication system is mixed with the fifth-generation system, the open radio access network (O-RAN) defines the E2 application protocol (E2AP) specification for the application protocol of the E2 interface between the E2 node and the near real-time (RT) radio access network (RAN) intelligent controller (RIC). O-RAN is jointly established by operators and equipment vendors. Summary of the invention

[0007] Solution to the problem

[0008] Provided are an apparatus and method for controlling an E2 node by a radio access network (RAN) intelligent controller (RIC) in a radio access network. Provided are an apparatus and method for controlling an E2 node through an E2 message compliant with an open radio access network (O-RAN) specification of a wireless communication system.

[0009] In addition, an apparatus and method for transmitting a specification number (eg, a version of a specification) of an O-RAN E2 Application Protocol (E2AP) regarding an E2 node to an RIC in a wireless communication system are provided.

[0010] According to one or more embodiments, a method performed by a first base station includes: sending an E2 setup request message to a network controller; and receiving an E2 setup response message from the network controller. The E2 setup request message includes version information indicating a standard version number of a communication protocol, and the communication protocol includes an E2 application protocol (E2AP). For example, the network controller may be a near real-time (RT) radio access network (RAN) intelligent controller (RIC), and the first base station may be an E2 node.

[0011] According to one or more embodiments, a method performed by a network controller includes: receiving an E2 setup request message from a first base station; and sending an E2 setup response message to the first base station. The E2 setup request message includes version information indicating a standard version number of a communication protocol, and the communication protocol includes an E2 application protocol (E2AP).

[0012] According to one or more embodiments, the first base station includes: at least one transceiver; and at least one processor electrically connected to the at least one transceiver. The at least one processor is configured to: send an E2 setup request message to a network controller, and receive an E2 setup response message from the network controller. The E2 setup request message includes version information indicating a standard version number of a communication protocol, and the communication protocol includes an E2 application protocol (E2AP).

[0013] According to one or more embodiments, a network controller includes: at least one transceiver; and at least one processor electrically connected to the at least one transceiver. The at least one processor is configured to: receive an E2 setup request message from a first base station, and send an E2 setup response message to the first base station. The E2 setup request message includes version information indicating a standard version number of a communication protocol, and the communication protocol includes an E2 application protocol (E2AP).

[0014] According to one or more embodiments, a method performed by an E2 node may include sending an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (RIC). The method may include receiving an E2 setup response message from the RIC. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near-RT RIC.

[0015] According to one or more embodiments, a method performed by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) may include receiving an E2 setup request message from an E2 node. The method may include sending an E2 setup response message to the E2 node. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near RT RIC.

[0016] According to one or more embodiments, the apparatus of the E2 node may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to send an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to receive an E2 setup response message from the RIC. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near-RT RIC.

[0017] According to one or more embodiments, a device of a near real-time (RT) radio access network (RAN) intelligent controller (RIC) may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to receive an E2 setup request message from an E2 node. The at least one processor may be configured to send an E2 setup response message to the E2 node. The E2 setup request message includes information for indicating an E2 interface between an E2 node and a near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near-RT RIC. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0021] Figure 2b An example of an architecture of an Open Radio Access Network (O-RAN) is shown;

[0022] Figure 3 shows a protocol stack for E2 application protocol messages in a radio access network according to one or more embodiments;

[0023] Figure 4 illustrates an example of a connection between a base station and a radio access network (RAN) intelligent controller (RIC) in a radio access network according to one or more embodiments;

[0024] Figure 5 shows a configuration of an apparatus in a radio access network according to one or more embodiments;

[0025] Figure 6 illustrates logical functions related to E2 messages and E2 nodes of a RIC in a radio access network according to one or more embodiments;

[0026] Figure 7 illustrates an example of functional separation between an E2 node and a RIC according to one or more embodiments;

[0027] Figure 8shows an example of implementation of an E2 node and a RIC according to an embodiment;

[0028] Fig. 9 illustrates an example of functional separation between a centralized unit (CU) and a RIC according to one or more embodiments;

[0029] Fig.10 An example of sending a version number of an E2 Application Protocol (E2AP) specification according to one or more embodiments is shown;

[0030] Figures 11a to 11d illustrates an example of an E2 Setup Request message for providing a version number of an E2AP specification in accordance with one or more embodiments; and

[0031] Fig.12 An example of identifying compatibility according to a version number of the E2AP specification according to one or more embodiments is shown. DETAILED DESCRIPTION

[0032] The terms used in this disclosure are only used to better describe a certain embodiment and are not intended to limit the scope of other embodiments thereto. Unless the context clearly stipulates otherwise, singular expressions may include plural expressions. The terms used herein (including technical and scientific terms) may have the same meaning as the meanings commonly understood by those skilled in the art to which the disclosure belongs. The terms defined in the general dictionary of the terms used in this disclosure may be interpreted as having the same or similar meanings as those in the context of the relevant art, and they should not be interpreted as ideal or overly formal meanings unless clearly defined in this disclosure. In some cases, even the terms defined in this disclosure should not be interpreted as excluding embodiments of the disclosure.

[0033] In various examples of the present disclosure described below, a hardware method will be described as an example. However, since one or more embodiments of the present disclosure include techniques utilizing both hardware and software, they are not intended to exclude software-based methods.

[0034] Hereinafter, the present disclosure relates to a control process between a device in a radio access network (RAN) in a wireless communication system and a device controlling the RAN. More specifically, the present disclosure relates to a process, a message, and a method for performing appropriate operations according to specifications and ensuring backward compatibility by providing a version number (e.g., E2AP 2.02) of the E2AP specification to a RAN intelligent controller (RIC) by an E2 node.

[0035] As used in the following description, terms referring to configuration (e.g., establishment, setting, arrangement, control), terms referring to signals (e.g., packets, messages, signals, information, signaling), terms referring to resources (e.g., sections, symbols, time slots, subframes, radio frames, subcarriers, resource elements (REs), resource blocks (RBs), bandwidth parts (BWPs), opportunities), terms indicating operation states (e.g., steps, operations, procedures), terms referring to data (e.g., packets, messages, user flows, information, bits, symbols, codewords), terms referring to channels, terms referring to network entities (Distributed Unit (DU), Radio Unit (RU), Central Unit (CU), Control Plane (CU-CP), O-DU (O-RAN (Open Radio Access Network) DU), O-RU (O-RAN RU), O-CU (O-RAN CU), O-CU-UP (O-RAN CU-CP), O-CU-CP (O-RAN CU-CP), O-CU-UP (O-RAN CU-CP), O-CU-CP (O-RAN CU-CP)), terms referring to components of the device, etc. are explained. Therefore, the present disclosure is not limited to those terms described below, and therefore other terms with technical meanings equivalent thereto may be used. In addition, as used herein, terms such as "... unit", "... module", "... group", "... part", etc. may mean a structure or unit of at least one form that processes a specific function.

[0036] In addition, throughout this disclosure, expressions such as "higher than (or exceeds)" or "lower than" may be used to determine whether a specific condition is met or satisfied, but it is merely a description for expressing an example and is not intended to exclude the meaning of "greater than or equal to" or "less than or equal to". A condition described as "greater than or equal to" may be replaced with "above", a condition described as "less than or equal to" may be replaced with "below", and a condition described as "greater than or equal to" and "below" may be replaced with "above" and "less than or equal to", respectively. In addition, unless otherwise expressly specified, "A" to "B" is intended to represent at least one of the elements from A to (including A) and B (including B).

[0037] In addition, the present disclosure uses terms used in some communication standard specifications (e.g., 3rd Generation Partnership Project (3GPP), Scalable Radio Access Network (xRAN), Open Radio Access Network (O-RAN)) to describe one or more embodiments, but they are merely examples for description. One or more embodiments of the present disclosure can be easily modified and even applied to other communication systems.

[0038] With the commercialization of 4G communication systems and 5G communication systems (e.g., New Radio (NR)), users in virtualized networks have been demanding differentiated service support. Therefore, 3GPP originated as a joint research project between several mobile communication-related organizations to create globally applicable 3G mobile communication system specifications within the scope of the IMT-2000 project of the International Telecommunication Union (ITU).

[0039] 3GPP was established in December 1998, and the 3GPP specifications are based on advanced GSM standards, including all radio, core network and service architectures within the scope of standardization. Therefore, O-RAN has newly defined RU (Radio Unit), DU (Digital Unit), CU (Central Unit)-CP (Control Plane) and CU-UP (User Plane), which are nodes constituting 3GPP network entities (NE) and base stations, respectively as O (O-RAN)-RU, O-DU, O-CU-CP and O-CU-UP, and in addition, the near real-time (near RT) RIC (Radio Access Network Intelligent Controller) is standardized.

[0040] According to one or more embodiments, the present disclosure relates to an operator-specific service model in an E2 interface, where the RIC requests a service from an O-DU, an O-CU-CP, or an O-CU-UP. Here, the O-RU, O-DU, O-CU-CP, and O-CU-UP may be understood as objects constituting a RAN capable of operating according to the O-RAN standard, and may be referred to as an "E2 node". The interface between the RIC and the E2 node with the objects constituting the RAN capable of operating according to the O-RAN standard uses E2AP, which is an application protocol.

[0041] RIC is a logical node that can collect information about the cell site where the terminal, O-DU, O-CU-CP or O-CU-UP sends and receives. RIC can be implemented in the form of a server concentrated in one physical location. Connections can be established between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC through Ethernet. To this end, interface standard specifications for communication between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC are required, and the definition of message specifications of E2-DU, E2-CU-CP, E2-CU-UP, etc. and the processes between O-DU, O-CU-CP, O-CU-UP and RIC are also required. In particular, it is necessary to define the functions of E2-DU, E2-CU-CP and E2-CU-UP messages to support services with a wide range of cell coverage, because users in virtualized networks require differentiated service support, and the call processing messages / functions generated in O-RAN are concentrated on RIC.

[0042] RIC can use the E2 interface to perform communication with O-DU, O-CU-CP and O-CU-UP, and generate and send subscription messages to set event occurrence conditions. More specifically, RIC can generate an E2 subscription request message and transmit it to an E2 node (e.g., O-CU-CP, O-CU-UP, O-DU) to set a call processing event. In addition, after setting the call processing event, the E2 node can send a subscription request response message that is transmitted to the RIC.

[0043] The E2 node can send the current status to the RIC through E2 indication / report. The RIC can use E2 control messages to control the O-DU, O-CU-CP, and O-CU-UP. One or more embodiments of the present disclosure propose an E2 indication message that sends a UE unit of measurement information for each period set in the subscription event condition in the O-DU. In addition, one or more embodiments of the present disclosure propose a message for controlling resources sent from the RIC to the O-DU.

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

[0045] refer 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 , a mobility management entity (MME) 150 , a home subscriber server (HSS) 160 , and a policy and charging rules function (PCRF) 170 .

[0046] 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 collects status information of the terminal 120 (such as buffer status, available transmission power, or channel status) to perform scheduling. The base station 110 has a coverage range defined as a specific geographical area based on the distance at which a signal can be transmitted. The base station 110 is connected to the MME 150 through the S1-MME interface. In addition, the base station 110 may also be referred to as an "access point (AP)", "eNodeB (eNB)", "radio point", "transmission / reception point (TRP)" or other terms having technical meanings equivalent thereto.

[0047] The terminal 120, which is a device used by a user, performs communication with the base station 110 through a radio channel. In some cases, the terminal 120 may be operated without any user participation. For example, the terminal 120 may be a device that performs machine type communication (MTC) and may not be carried by a user. In addition, the terminal 120 may be referred to as a "user equipment (UE)", "mobile station", "subscriber station", "customer terminal equipment (CPE)", "remote terminal", "wireless terminal", "user equipment" or any other term having equivalent meanings thereto.

[0048] The S-GW 130 provides a data bearer and generates or controls the data bearer under the control of the MME 150. For example, the S-GW 130 may process a packet arriving from the base station 110 or a packet to be forwarded to the base station 110. In addition, the S-GW 130 may be used as an anchor point during handover of the terminal 120 between base stations. The P-GW 140 may be used as a connection point with an external network (e.g., an Internet network). In addition, the P-GW 140 may allocate an Internet Protocol (IP) address to the terminal 120 and serve as an anchor point for the S-GW 130. In addition, the P-GW 140 may apply a Quality of Service (QoS) policy for the terminal 120 and manage account data.

[0049] The MME 150 manages the mobility of the terminal 120. In addition, the MME 150 may perform authentication, bearer management, etc. for the terminal 120. That is, the MME 150 is responsible for the mobility management and various control functions of the terminal. The MME 150 may be associated with a Serving GPRS Support Node (SGSN).

[0050] The HSS 160 stores key information and a subscriber profile used for authentication of the terminal 120. The key information and the subscriber profile are transmitted from the HSS 160 to the MME 150 when the terminal 120 accesses the network.

[0051] PCRF 170 defines rules for policy and charging. The stored information is transmitted from PCRF 170 to P-GW 140, and P-GW 140 may perform control (eg, QoS management, charging, etc.) of terminal 120 based on the information provided from PCRF 170.

[0052] Carrier aggregation (hereinafter, referred to as "CA") may be able to combine multiple component carriers and use such multiple component carriers to send / receive signals at the same time, thereby improving the efficiency of frequency usage from the perspective of a terminal or a base station. Specifically, according to the CA technology, a terminal and a base station may use multiple component carriers in an uplink (UL) and a downlink (DL) to send and receive signals using a broadband, respectively. Each of the component carriers is located in a different frequency band. Hereinafter, the term "uplink" refers to a communication link through which a terminal sends a signal to a base station, and the term "downlink" refers to a communication link through which a base station sends a signal to a terminal. In this case, the number of uplink component carriers and downlink component carriers may be different from each other.

[0053] Dual connectivity or multi-connectivity can improve the efficiency of frequency usage from the perspective of a terminal or a base station by enabling one terminal to connect to multiple base stations to simultaneously send and receive signals using carriers in multiple base stations located in different frequency bands. The terminal can be simultaneously connected to a first base station (e.g., a base station providing services using LTE technology or 4G mobile communication technology) and a second base station (e.g., a base station providing services using NR technology or 5G mobile communication technology) to send and receive services. In such a case, the frequency resources used by each base station may be located in different frequency bands. In this way, a scheme operating based on dual connectivity with LTE and NR may be referred to as 5G non-standalone (NSA).

[0054] Figure 2a An example of a 5G NSA system is shown.

[0055] refer to Figure 2a , the 5G NSA system includes NR RAN 210a, LTE RAN 210b, terminal 220, and evolved packet core (EPC) 250. NR RAN 210a and LTE RAN 210b are connected to EPC 250, and terminal 220 can receive services from either or both of NR RAN 210a and LTE RAN 210b 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 a "fifth generation (5G) node", "next generation Node B (gNB)" or other terms with equivalent technical meanings. Further, the NR base station may have a structure separated by a central unit (CU) and a digital unit (DU), and the CU may also have a structure separated by a control plane (CU-CP) unit and a user plane (CU-UP) unit.

[0056] exist Figure 2aIn the structure shown, the terminal 220 can perform a radio resource control (RRC) connection through a first base station (e.g., a base station belonging to the LTE RAN 210b), and can be served by functions provided in the control plane (e.g., connection management, mobility management, etc.). In addition, the terminal 220 can be provided with additional radio resources for sending and receiving data through a second base station (e.g., a base station belonging to the NR RAN210a). This dual connection technology using LTE and NR can be referred to as EN-DC Evolved Universal Terrestrial Radio Access (E-UTRA)-NR dual connection). Similarly, the dual connection technology in which the first base station uses NR technology and the second base station uses LTE technology can be referred to as NR-DC (NR-E-UTRA dual connection). In addition, one or more embodiments can be applied to various other forms of multi-connection and carrier aggregation technologies. In addition, one or more embodiments can also be applied when the first system (using the first communication technology) and the second system (using the second communication technology) are implemented in one device, or when the first base station and the second base station are located in the same geographical location.

[0057] Figure 2b An example of the architecture of O-RAN is shown. For the purpose of E2-SM-KPIMON (Key Performance Indicator (KPI) Monitoring) of the E2 service model, O-RAN NSA mode in multi-connectivity operation using E-UTRA and NR radio access technologies may be considered, while the E2 nodes may be assumed to be in O-RAN Standalone (SA) mode.

[0058] refer to Figure 2b In the deployment of O-RAN NSA mode, the eNB can be connected to the EPC via the S1-C / S1-U interface and can be connected to the O-CU-CP via the X2 interface. The O-CU-CP for deploying O-RAN SA mode can be connected to the 5GC (5G Core) via the N2 / N3 interface.

[0059] Figure 3 An example of a protocol stack for an E2 application protocol message in a radio access network according to one or more embodiments of the present disclosure is shown. Figure 3 , the control plane includes a transport network layer and a radio network layer. The transport network layer includes a physical layer 310 , a data link layer 320 , an Internet Protocol (IP) 330 , and a stream control transmission protocol (SCTP) 340 .

[0060] The radio network layer includes E2AP 350. E2AP 350 may be used to deliver a subscription message, an indication message, a control message, a service update message, and a service query message, and may be sent from a higher layer of SCTP 340 and IP 330.

[0061] Figure 4 An example of a connection between a base station and a RIC in a radio access network according to one or more embodiments of the present disclosure is shown.

[0062] refer to Figure 4 , RIC 440 is connected to O-CU-UP 410, O-CU-CP 420 and O-DU 430. RIC 440 can customize RAN functions for new services or regional resource optimization. RIC 440 can provide network intelligence (e.g., policy implementation, switching optimization), resource guarantee (e.g., radio link management, advanced self-organizing network (SON)), resource control (e.g., load balancing, slicing strategy), etc. 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 E2-CP, E2-UP and E2-DU interfaces. In addition, the interface between O-CU-CP and DU and / or the interface between O-CU-UP and DU can be referred to as F1 interface. In the following description, DU and O-DU, CU-CP and O-CU-CP, and CU-UP and O-CU-UP can be used interchangeably.

[0063] although Figure 4 One RIC 440 is shown, but according to one or more embodiments, there may be multiple RICs. The multiple RICs may be implemented using multiple hardware located in the same physical location, or may be implemented through virtualization using one hardware.

[0064] Figure 5 An example of a configuration of an apparatus according to one or more embodiments of the present disclosure is shown. Figure 5 The configuration shown in can be understood as having Figure 4 The configuration of a device for at least one function of near-RT RIC, non-RT RIC, O-CU-CP, O-CU-UP and O-DU. As used hereinafter, terms such as "~module", "~unit", "~group", "~part" and the like may refer to a unit that processes at least one function or operation, which may be implemented as hardware, software, or a combination of hardware and software.

[0065] refer to Figure 5 , the core network device includes a communication unit 510, a storage unit 520 and a controller 530.

[0066] The communication unit 510 provides an interface for performing communication with other devices in the network. In other words, the communication unit 510 converts a bit string sent 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 communication unit 510 can send and receive signals. Therefore, the communication unit 510 can be referred to as a modem, a sending unit, a receiving unit, or a sending / receiving unit. In this case, the communication unit 510 enables the core network device to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network. The communication unit 510 may include one or more transceivers.

[0067] The storage unit 520 stores data such as basic programs, application programs, and setting information for the overall operation of the core network device. The storage unit 520 may include a volatile memory, a nonvolatile memory, or a combination of a volatile memory and a nonvolatile memory. In addition, the storage unit 520 provides the stored data according to the request of the controller 530.

[0068] The controller 530 controls the overall operation of the core network device. For example, the controller 530 sends and receives signals through the communication unit 510. In addition, the controller 530 records data in the storage unit 520 / reads data from the storage unit 520. To this end, the controller 530 may include at least one processor. According to one or more embodiments, the controller 530 may control the device to perform operations according to one or more embodiments described in the present disclosure.

[0069] Figure 6 Logical functions related to E2 messages and RIC of an E2 node in a radio access network according to one or more embodiments of the present disclosure are shown.

[0070] refer to Figure 6 , the RIC 640 and the E2 node 610 can send or receive E2 messages to / from each other. For example, the E2 node 610 can be an O-CU-CP, an O-CU-UP, an O-DU, or a base station. The communication interface of the E2 node can be determined according to the type of the E2 node 610. For example, the E2 node 610 can communicate with another E2 node 616 through an E1 interface or an F1 interface. Alternatively, for example, the E2 node 610 can communicate with the E2 node 616 via an X2 interface or an XN interface. Optionally, for example, the E2 node 610 can 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 an AMF).

[0071] The E2 node 610 may include an E2 node function 612. The E2 node function 612 corresponds to a specific xApp (application S / W) 646 installed in the RIC 640. For example, in the case of a KPI monitor, a KPI monitor set S / W may be installed in the RIC 640, and the E2 node 610 may include an E2 node function 612, which generates KPI parameters and then delivers an E2 message including the KPI parameters to an E2 terminal 642 located in the RIC 640. The E2 node 610 may include a radio resource management (RRM) 614. The E2 node 610 may manage resources of a radio network provided to a terminal.

[0072] The E2 terminal 642 (located in the RIC 640) is a terminal of the RIC 640 for the E2 message, and performs a function of interpreting the E2 message delivered (or sent) by the E2 node 610, and then delivering the E2 message to the xApp 646. The database 644 (located in the RIC 640) can be used for the E2 terminal 642 and the xApp 646. The E2 node 610 ( Figure 6 As shown) is a terminal of at least one interface and can be understood as the termination of messages sent to the terminal, the neighboring base station and the core network.

[0073] Figure 7 An example of functional separation between an E2 node and a RIC according to one or more embodiments of the present disclosure is shown. The O-RAN specification provides for functional separation between an E2 node and a RIC. For example, the E2 node may be a CU and the RIC may be a near-RT RIC. The RIC may be connected to an Open Network Automation Platform (ONAP) / Management and Orchestration (MANO) / Network Management System (NMS) via an A1 interface. The RIC may be connected to an E2 node via an E2 interface. The E2 interface may deliver commands. Functional separation options may include functional separation 700 of managing the entire radio resource management (RRM) in a near-RT RIC, and optionally functional separation 750 of managing the RRM in a near-RT RIC.

[0074] In the related art, the near-RT RIC can support E2 with an open logical interface for multiple vendor environments, regardless of the implementation of a specific RRC-RRM algorithm or operation located in the near-RT RIC. In one embodiment, the E2SM-RIC (E2 Service Model Radio Interface Control) can be paired with the E2SM-NI that is capable of performing injection / modification / configuration of per-UE RRC messages for each I / F and network entity. In other words, the near-RT RIC can be gradually improved from functional separation 750 to functional separation 700. E2 can evolve into an open logical interface that can be independent of the implementation of a certain RRC-RRM algorithm or operation in the near-RT RIC and can be targeted at a multi-vendor environment.

[0075] Figure 8 An example of an implementation of an E2 node and RIC 810 according to one or more embodiments of the present disclosure is shown. In example 800, the E2 node (e.g., O-DU 820, O-CU 830) and RIC 810 can be virtualized on a cloud platform 840 (e.g., an open chassis and blade specification edge cloud) and configured in a device (e.g., a server). Such a scenario can support deployments in dense urban areas with abundant fronthaul capacity, enabling baseband unit (BBU) functions to be pooled at a central location with sufficiently low latency to meet O-DU latency requirements. In one embodiment, there may be no need to attempt to centralize the RIC near the RT, beyond the limitation of being able to centralize the O-DU functions. According to an embodiment, the E2SM-RIC can be optimized for an O-RAN deployment scenario, where near-RT RICs, O-CUs, and O-DUs are implemented in the O-Cloud platform.

[0076] Fig. 9 An example of functional separation between a centralized unit (CU) 910 and a RIC 920 is shown in accordance with one or more embodiments of the present disclosure. Fig. 9 , functional separation can be performed according to deployment scenario #1 (example 900) or functional deployment scenario #2 (example 950).

[0077] Deployment scenario #1 (900): RIC is located at a separate site or exists only as a different network element (NE) and replaces or recommends some intelligent required features.

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

[0079] although Fig. 9Two scenarios are shown, but other scenarios may apply. For example, in deployment scenario #1 (900), mobility functions may be performed by RIC 920 instead of CU 910. Also, for example, in deployment scenario #1 (900), UE context functions may be performed by RIC 920 instead of CU 910. Also, for example, in deployment scenario #1 (900), session setup functions may be performed by RIC 920 instead of CU 910.

[0080] The E2 setup process may be used to establish an E2 interface between a near-RT RIC and an E2 node. The E2 node may send an E2 setup request message to the near-RT RIC. The E2 setup request message may include RIC service and E2 node configuration information. The near-RT RIC may send an E2 setup response message to the E2 node. The E2 setup response message may include RIC service and E2 node configuration confirmation.

[0081] Through the E2 establishment process, the E2 node can provide a mapping list of services to the near-RT RIC services and functions supported within the E2 node. The information provided can be specific to each RAN function in the E2 node and can be defined by a specific E2 service model. The near-RT RIC can extract a mapping list of services to supported near-RT RIC services and functions and can store the information. Through the E2 establishment process, the E2 node can provide E2 node configuration information. The information provided can be defined by the E2 node type and the E2 node system specification. The near-RT RIC can extract a list of E2 node configuration information and can store the information.

[0082] Fig.10 An example of sending the version number of the E2 Application Protocol (E2AP) specification according to one or more embodiments is shown. The interface between the E2 node 1000 and the RIC 1100 (in other words, the version of the E2AP) may vary. The RIC 1100 may be required to identify the E2AP specification information of the E2 node 1000 in order to control the E2 node 1000.

[0083] refer to Fig.10, the E2 node 1000 may provide the E2AP specification number to the RIC 1100 (e.g., a near-RT RIC). The E2AP specification number may indicate a version number (e.g., 2.02) of the O-RAN specification. In the E2AP specification, non-backward compatibility (NBC) occurs continuously from the initial version (e.g., 1.0) to the current version (2.02). As the specification is updated, additional IEs (e.g., transaction ID, RAN function addition list, and E2 node component configuration addition list) are introduced. For example, the "transaction id" IE is not included in E2AP 1.0 and E2AP 2.01, but is introduced in E2AP 2.02. In addition, for example, the "E2 node component configuration addition list" IE is not included in E2AP 1.0 and E2AP 2.01, but is introduced in E2AP 2.02. As the E2AP specification evolves in the future and the current E2AP specification progresses, NBC may appear additionally and repeatedly.

[0084] Whenever the function of the E2 interface is updated, the NBC of the E2AP specification causes the trouble of forcing the user to install a new driver or update the entire software in the device. In order to solve the above problem, the E2 node and the near-RT RIC according to one or more embodiments of the present disclosure propose a device and method for sharing the version number of the E2AP specification through the process defined in the O-RAN specification.

[0085] According to an embodiment, the E2 node may share the version number of the E2AP specification through the E2 establishment process for establishing the near RT RIC and the E2 interface. Hereinafter, in the embodiments of the present disclosure, the E2 establishment process is described as an example, but the embodiments of the present disclosure are not limited thereto. The method for providing the version of the specification described in the embodiments of the present disclosure may be applied to at least one of a reset process, an error indication, a RIC service update process, an E2 node configuration update process, or an E2 connection update process.

[0086] Figures 11a to 11d An example of an E2 setup request message for providing a version number of the E2AP specification according to an embodiment is shown. In the E2 setup process according to the defined process, there is a problem that the RIC 1100 (e.g., near-RT RIC) does not know the E2AP specification version of the interface supported in the E2 node 1000. Therefore, by Figures 11a to 11d , describes a method for notifying the E2AP specification version of the interface supported in the E2 node 1000 to the RIC (eg, near RT RIC) 1100. According to an embodiment, the E2 node 1000 may add information about the E2AP version number to the end of the E2 Setup Request message in order to meet backward compatibility.

[0087] refer to Fig.11a, the E2 node 1000 may send an E2 setup request message to the RIC (e.g., near-RT RIC) 1100. The RIC (e.g., near-RT RIC) 1100 may send an E2 setup response message to the E2 node 1000. O-RAN designates the base station as the E2 node 1000, but based on the 3GPP specification, it may have an integrated deployment or a distributed deployment depending on the implementation method (e.g., virtualization). For example, a base station (e.g., gNB) may have an integrated deployment in which the CU and DU are configured together. For another example, a base station (e.g., gNB) may have a 2-split deployment in which the CU and DU are separated. For another example, a base station (e.g., gNB) may have a 3-split deployment in which the CU-CP, CU-UP, and DU are separated from each other.

[0088] The E2 Setup Request message (sent to the Near-RT RIC) may include a structure defined in an E2 Application Protocol (E2AP) specification (eg, O-RAN specification E2AP 2.02).

[0089]

Table 1

[0090]

[0091] Fig.11b An example of an E2 setup request message including an IE for indicating a version number of an E2AP specification of the E2 node 1000 according to an embodiment is shown. The E2 node 1000 (e.g., gNB, gNB-CU, gNB-DU, eNB, eNB-CU, eNB-DU) may add an IE for indicating a version number of the E2AP specification to the structure of the E2 setup request message defined in the O-RAN E2AP specification during an E2 setup request process to the RIC 1100 (e.g., near-RT RIC). For example, the E2 node 1000 may add the IE specified in the following table to the end of the E2 setup request message.

[0092]

Table 2

[0093]

[0094] The E2 setup request message including the IE can be used to encode up to seven 3GPP specification numbers for each I / F of each 3GPP and send them in a 3-octet string. The 3-octet string is an example of an IE, which can include strings of other sizes, such as a two-octet string.

[0095] According to an embodiment, the E2 establishment request message may include an IE indicating the version number of the E2AP specification. The version number may be indicated in the form of "x, y, z" or "x.yz". In Table 2 above, three octet strings are described to indicate the version number in the form of "x, y, z" or "x.yz", but the embodiments of the present disclosure are not limited thereto. According to another embodiment, in order to reduce the size of the field, the E2 node may indicate the specification version of the E2AP based on the form of "x, y". The E2 node may indicate the specification version of the E2AP through two octet strings.

[0096] According to an embodiment, the E2 establishment request message may include an IE indicating an interface type. For example, "E2 node component interface type" may indicate an interface type. For example, the interface type may indicate the following types:

[0097] 1) NG interface,

[0098] 2) XN interface,

[0099] 3) E1 interface,

[0100] 4) F1 interface,

[0101] 5) W1 interface,

[0102] 6) S1 interface,

[0103] 7) X2 interface, and

[0104] 8) E2 interface.

[0105] According to one or more embodiments, in order to indicate the version number of the E2AP specification, the interface type of the E2 setup request message may be required to indicate the E2 interface. In the case where the interface type of the E2 node indicates "e2", there is an IE (e.g., the E2AP version number) for indicating the version number of the E2AP specification. In the case where the interface type of the E2 setup request message indicates a type other than the E2 interface, the IE for indicating the version number of the E2AP specification may not be included in the E2 node component configuration information. In the E2 setup request message, an "E2 node E2AP version" IE may be included. In one embodiment, including the "E2AP version number" IE in the "E2 node E2AP version" IE may be optional. In one embodiment, including the "E2AP version number" IE in the "E2 node E2AP version" IE may be mandatory.

[0106] In one embodiment, the structure of the E2 setup request message may be defined to indicate the version number of the E2AP and the version number of the 3GPP specification. For example, the structure of the E2 setup request message may be defined as follows.

[0107]

Table 3

[0108]

[0109]

[0110] According to an embodiment, information for indicating a version number (e.g., "Interface Protocol Version" IE) may depend on information for indicating an interface type (e.g., "E2 Node Component Interface Type" IE). For example, in the case where the "E2 Node Component Interface Type" IE of the E2 Setup Request message indicates "xn", the version number may indicate a specification version (e.g., 16.8.0) of 3GPP TS 38.423. In addition, for example, in the case where the "E2 Node Component Interface Type" IE of the E2 Setup Request message indicates "e2", the version number may indicate a specification version (e.g., 2.02) of E2AP.

[0111] refer to Fig.11c According to an embodiment, for backward compatibility, information indicating the version number of the E2AP specification may be set at the end of the configuration information of each type of E2 node. Fig.11c As shown, information indicating the version number of the E2AP specification (eg, E2 Node E2AP Version IE) may be added after the "E2 Node Component Configuration" IE of the configuration information.

[0112] refer to Fig.11d According to an embodiment, as a basic component from a specification to be updated later, information indicating the version number of the E2AP specification may be provided as an independent IE (eg, Fig.11d The "E2 node E2AP version" in the E2 establishment request message is added.

[0113] In the present disclosure, information for indicating an interface type may be used to identify the interface type from information in a node receiving information. For example, information for indicating an interface type may indicate a specific value among candidate values ​​of the interface type (e.g., ng, xn, e1, f1, w1, s1, x2, and e2). The node receiving the information may identify the interface type corresponding to the specific value. According to an embodiment, information for indicating an interface type may indicate an E2 interface. The node receiving the information may identify that the application protocol configured for the E2 node is E2AP. In the present disclosure, information for indicating a version of E2AP may be used to identify the version of E2AP from information in a node receiving the information. For example, information for indicating a version of E2AP may include a bit sequence. The node receiving the information may identify a version corresponding to a value indicated by a bit string. A version may indicate a capability range including functions supported by a corresponding protocol (e.g., E2AP).

[0114] According to an embodiment, the information for indicating the version of E2AP may include a bit sequence. For example, the information for indicating the version of E2AP may include one or more octet strings. Each octet string represents a sequence of bytes or octets used to represent binary data. The octet string may be composed of an 8-bit integer. An octet may be used to represent binary data in network protocols and network device management. A node receiving information for indicating the version of E2AP is able to identify the version of E2AP based on the decoding of the information. For example, the information for indicating the version of E2AP may obtain multiple octet strings (e.g., 3 octet strings) by decoding. The node may obtain a value corresponding to each octet string. The node may identify (or determine) the version of E2AP based on the obtained value.

[0115] Fig.12 An example of identifying compatibility according to a version number of the E2AP specification according to an embodiment is shown.

[0116] refer to Fig.12 , the library of E2AP Abstract Syntax Notation (ASN).1 of RIC 1100 (e.g., near-RT RIC) may support E2AP xyz+1. The E2AP ASN.1 library of E2 node 1000 may support E2AP xyz. ASN.1 is a standardized notation for describing the data structure of messages exchanged between communication entities. ASN.1 is a long-recorded notation with reliability and interoperability, and may support the exchange of information in all forms (e.g., audio, video, and data).

[0117] The RIC (e.g., near RT RIC) 1100 may identify a version of the E2AP. The RIC (e.g., near RT RIC) 1100 may determine whether to connect to the E2 node 1000 based on the identified version of the E2AP. For example, in a case where the E2 node 1000 corresponds to an E2AP version that is not supported by the RIC (e.g., near RT RIC) 1100, the establishment request for the E2 node 1000 may not be allowed regardless of the compatibility. In this case, according to an additional embodiment, the RIC (e.g., near RT RIC) 1100 may indicate to the E2 node 1000 the reason why the establishment request of the E2 node 1000 is not allowed. In addition, for example, when the E2 node 1000 corresponds to an E2AP version that is not supported by the RIC (e.g., near RT RIC) 1100, the RIC (e.g., near RT RIC) 1100 may filter at least some of the IEs received from the E2 node 1000. In other words, with the E2AP version in the E2 node 1000, a process for identifying an IE that is not transmitted may not be performed.

[0118] When the version information of the E2AP specification is different between two network entities (e.g., the E2 node 1000 and the RIC (e.g., near-RT RIC) 1100), compatibility issues may occur. For example, the RIC (e.g., near-RT RIC) 1100 may receive IEs from the E2 node 1000. In this case, the near-RT RIC may skip decoding for IEs that are supported only in higher versions (e.g., transaction ID, RAN function addition list, E2 node component configuration addition list). In the case where the RIC (e.g., near-RT RIC) 1100 does not receive specific information, it is not known whether the specific information is due to the low version not appearing or not being sent from the E2 node 1000. As described above, the level of recognition between the RIC (e.g., near-RT RIC) for a specific message may be different from the information of the E2 node 1000 for the specific message. This difference may cause errors in messages sent over the E2AP interface. Therefore, the E2 node 1000 and the RIC (eg, near-RT RIC) 1100 according to one or more embodiments of the present disclosure may reduce the above errors and may improve communication performance of the E2 interface by sharing interface types and version information of 3GPP specifications for the interface types.

[0119] Under the existing E2AP specification of O-RAN, non-backward compatibility issues may frequently occur. The present disclosure relates to an apparatus and method for controlling an E2 node by a RIC in a radio access network. The present disclosure provides an apparatus and method for controlling an E2 node through an E2 message that complies with the open radio access network (O-RAN) specification of a wireless communication system. In addition, the present invention provides an apparatus and method for sending the specification number of the O-RAN E2 application protocol (E2AP) of an E2 node to a radio access network (RAN) intelligent controller (RIC) in a wireless communication system.

[0120] According to one or more embodiments of the present disclosure, an E2 node provides a version of an E2AP specification related to an E2 node (e.g., a central unit (CU) or a control plane (CU-CP)) to a radio access network (RAN) intelligent controller (RIC) in a wireless communication system. The RIC may perform specific wireless communication control functions according to the E2AP version of the O-RAN specification. In addition, the RIC may enable effective control of the E2 node regardless of the compatibility of the E2AP specification of the base station, thereby providing a function of enhancing the mutual compatibility of the E2 interface.

[0121] Effects obtained from the present disclosure are not limited to the above-mentioned effects, and any other effects not mentioned herein will be clearly understood by a person of ordinary skill in the art to which the present disclosure pertains from the following description.

[0122] According to an embodiment, a method performed by an E2 node may include sending an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (RIC). The method may include receiving an E2 setup response message from the RIC. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near-RT RIC.

[0123] According to an embodiment, the E2 setup request message may include information about the type of communication protocol. The information about the type of communication protocol may indicate the E2 interface.

[0124] According to an embodiment, the information element (IE) of the E2 node component configuration addition list for the E2 establishment request message may include information and version information about the type of communication protocol. The information about the type of communication protocol may include one of an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, a W1 interface, or an E2 interface. In the case where the information about the type of communication protocol indicates an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, or a W1 interface, the version information may indicate a version of the third generation partnership project (3GPP) standard corresponding to the type of communication protocol. In the case where the information about the type of communication protocol indicates an E2 interface, the version information may indicate a version of the standard of the E2AP.

[0125] According to an embodiment, the version information may include a field designated to indicate a version number of a standard of an E2AP supported in the E2 node.

[0126] According to an embodiment, the version information may include a field indicating a version number of a standard of E2AP supported in the E2 node.

[0127] According to an embodiment, the version information may be used for backward compatibility of E2AP. For example, the version information may indicate backward compatibility of E2AP.

[0128] According to an embodiment, a method performed by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) may include receiving an E2 setup request message from an E2 node. The method may include sending an E2 setup response message to the E2 node. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near-RT RIC.

[0129] According to an embodiment, the E2 setup request message may include information about the type of communication protocol. The information about the type of communication protocol may indicate the E2 interface.

[0130] According to an embodiment, the information element (IE) of the E2 node component configuration addition list for the E2 establishment request message may include information and version information about the type of communication protocol. The information about the type of communication protocol may include one of an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, a W1 interface, or an E2 interface. In the case where the information about the type of communication protocol indicates an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, or a W1 interface, the version information may indicate a version of the third generation partnership project (3GPP) standard corresponding to the type of communication protocol. In the case where the information about the type of communication protocol indicates an E2 interface, the version information may indicate a version of the standard of the E2AP.

[0131] According to an embodiment, the version information may include a field designated to indicate a version number of a standard of an E2AP supported in the E2 node.

[0132] According to an embodiment, the version information may include a field indicating a version number of a standard of E2AP supported in the E2 node.

[0133] According to an embodiment, the version information may be used for backward compatibility of E2AP. For example, the version information may indicate backward compatibility of E2AP.

[0134] According to an embodiment, the device of the E2 node may include at least one transceiver; and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to send an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to receive an E2 setup response message from the near RT RIC. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near RT RIC.

[0135] According to an embodiment, the E2 setup request message may include information about the type of communication protocol. The information about the type of communication protocol may indicate the E2 interface.

[0136] According to an embodiment, the information element (IE) of the E2 node component configuration addition list for the E2 establishment request message may include information and version information about the type of communication protocol. The information about the type of communication protocol may include one of an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, a W1 interface, or an E2 interface. In the case where the information about the type of communication protocol indicates an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, or a W1 interface, the version information may indicate a version of the third generation partnership project (3GPP) standard corresponding to the type of communication protocol. In the case where the information about the type of communication protocol indicates an E2 interface, the version information may indicate a version of the standard of the E2AP.

[0137] According to an embodiment, the version information may include a field designated to indicate a version number of a standard of an E2AP supported in the E2 node.

[0138] According to an embodiment, the version information may include a field indicating a version number of a standard of E2AP supported in the E2 node.

[0139] According to an embodiment, the version information may be used for backward compatibility of E2AP. For example, the version information may indicate backward compatibility of E2AP.

[0140] According to an embodiment, a device of a near real-time (RT) radio access network (RAN) intelligent controller (RIC) may include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor may be configured to receive an E2 setup request message from an E2 node. The at least one processor may be configured to send an E2 setup response message to the E2 node. The E2 setup request message includes information for indicating an E2 interface between an E2 node and a near RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in an E2 interface between an E2 node and a near RT RIC.

[0141] According to an embodiment, the E2 setup request message may include information about the type of communication protocol. The information about the type of communication protocol may indicate the E2 interface.

[0142] According to an embodiment, the information element (IE) of the E2 node component configuration addition list for the E2 establishment request message may include information and version information about the type of communication protocol. The information about the type of communication protocol may include one of an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, a W1 interface, or an E2 interface. In the case where the information about the type of communication protocol indicates an X2 interface, an Xn interface, an F1 interface, an S1 interface, an E1 interface, an NG interface, or a W1 interface, the version information may indicate a version of the third generation partnership project (3GPP) standard corresponding to the type of communication protocol. In the case where the information about the type of communication protocol indicates an E2 interface, the version information may indicate a version of the standard of the E2AP.

[0143] According to an embodiment, the version information may include a field designated to indicate a version number of a standard of an E2AP supported in the E2 node.

[0144] According to an embodiment, the version information may be used for backward compatibility of E2AP.

[0145] According to an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes a memory storing a program including instructions. When the instructions are executed by a processor of an E2 node, the instructions cause the E2 node to send an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (near RT RIC) and receive an E2 setup response message from the near RTRIC. The E2 setup request message includes information for indicating an E2 interface between the E2 node and the near RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near RT RIC.

[0146] According to an embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes a memory storing a program including instructions. When the instructions are executed by a processor of a near real-time (RT) radio access network (RAN) intelligent controller (near RT RIC), the instructions cause the near RT RIC to receive an E2 setup request message from an E2 node and send an E2 setup response message to the E2 node. The E2 setup request message includes information for indicating an E2 interface between an E2 node and the near RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and information for indicating a version of an E2 application protocol (E2AP) of a radio network layer in the E2 interface between the E2 node and the near RT RIC.

[0147] According to an embodiment, information indicating the version of E2AP and information for indicating the E2 interface are included in the E2 node component configuration addition list information element (IE) of the E2 setup request message. The information indicating the version of E2AP is encoded after the information for indicating the E2 interface. The IE encoded subsequently may indicate that the information for indicating the version of E2AP is placed adjacent to the IE corresponding to the information for indicating the E2 interface.

[0148] According to an embodiment, information indicating the E2 interface is included in the E2 node component configuration addition list information element (IE) of the E2 setup request message. Information indicating the version of the E2AP is encoded at the end of the E2 setup request message. The meaning encoded at the end of the E2 setup request message may indicate that the IE corresponding to the information indicating the version of the E2AP among the IEs of the E2 setup request message is placed at the end.

[0149] According to an embodiment, the E2 setup request message includes a message type of the E2 setup request message, a transaction identifier (ID) of the E2 setup request message, and a global ID of the E2 node. Information indicating a version of the E2AP is encoded after the global ID of the E2 node.

[0150] According to an embodiment, information indicating the version of E2AP and information for indicating the E2 interface are included in the E2 node component configuration addition list information element (IE) of the E2 setup request message. The information indicating the version of E2AP is placed after the information for indicating the E2 interface. The meaning of being placed subsequently may indicate that the IE for information indicating the version of E2AP is placed immediately adjacent to the IE corresponding to the information for indicating the E2 interface.

[0151] According to an embodiment, information indicating the E2 interface is included in the E2 node component configuration addition list information element (IE) of the E2 setup request message. Information indicating the version of the E2AP is placed at the end of the E2 setup request message. The meaning of being placed at the end of the E2 setup request message may indicate that the IE corresponding to the information indicating the version of the E2AP among the IEs of the E2 setup request message is placed at the end.

[0152] According to an embodiment, the E2 setup request message includes a message type of the E2 setup request message, a transaction identifier (ID) of the E2 setup request message, and a global ID of the E2 node. Information indicating a version of the E2AP is placed after the global ID of the E2 node.

[0153] In the above-mentioned embodiment, an example of including information indicating the version of the E2AP specification in the E2 setup request message has been described, but the embodiments of the present disclosure are not limited thereto. According to an embodiment, the information indicating the version of the E2AP specification may be included in the E2 setup response message. By receiving the version of the E2AP specification of the E2 setup response message, the E2 node can check the version on the interface of the E2 node identified by the near RT RIC. According to another embodiment, the information indicating the version of the E2AP specification may be included in the E2 node configuration update message. In the case where the version of the E2AP specification is not sent in the E2 setup process, the E2 node may provide the version of the E2AP specification of the interface to the near RT RIC through the E2 node configuration update process. In addition, only the E2 setup process is described in the present disclosure, but the embodiments of the present disclosure are not limited thereto. The information indicating the version of the E2AP of the present disclosure may also be used in other processes such as the RIC service update process. For example, the information indicating the version of the E2AP may be included in the RIC service update message of the RIC service update process, rather than the E2 setup request message of the E2 setup process.

[0154] Various embodiments of the present disclosure may be implemented as software including one or more instructions stored in a storage medium readable by a machine (e.g., a device that performs the functions of the E2 node 1000, a device that performs the functions of the near-RT RIC 1100). It may be, for example, that a processor (e.g., controller 530) of a machine (e.g., E2 node 1000, near-end 1100) calls at least one command among one or more instructions stored in a storage medium, and enables the machine to be operated to perform at least one function according to the at least one instruction called. The one or more instructions include a code generated by a compiler or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" means that the storage medium is tangible and does not contain a signal (e.g., an electromagnetic wave), and the term does not distinguish between situations where data is semi-permanently stored and temporarily stored in a storage medium. O-RAN enables the configuration of a virtualized intelligent network with a standardized open interface. For network virtualization, the operation according to the embodiment may be implemented in the form of a recording medium (e.g., a memory).

[0155] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product is distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or distributed online (e.g., downloaded or uploaded) through an application store (e.g., PlayStore™) or distributed directly between two user devices (e.g., smart phones) (e.g., downloaded or uploaded). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a storage medium readable by a device such as a memory of a manufacturer's server, an application store server, or a relay server.

[0156] According to various embodiments, each of the above-mentioned components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be arranged separately in other components. According to various embodiments, one or more components or operations in the aforementioned corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as the functions performed by the corresponding components in the multiple components before integration. According to various embodiments, the operations performed by the modules, programs or other components are performed sequentially, in parallel, iteratively or heuristically, or one or more of the operations are performed in a different order or omitted. Or one or more other actions may be added.

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

[0158] When implemented as software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to perform the method according to one or more embodiments described in the claims or description of the present disclosure.

[0159] Such a program (software module, software) may be stored in a random access memory, a non-volatile memory including flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk-ROM (CD-ROM), a digital versatile disk (DVD) or other form of optical storage, a magnetic tape cartridge. Alternatively, it may be stored in a memory configured with some or all of the above combinations. In addition, each configuration memory may include multiple.

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

[0161] In the above-mentioned specific embodiments of the present disclosure, the components included in the present disclosure are expressed in the singular or plural, depending on the specific embodiments presented. However, for ease of explanation, singular or plural expression is appropriately selected for the presented situation, and the present disclosure is not limited to singular or plural components, and even if a component is expressed in plural, it can also be configured with a singular, or even if it is expressed in a singular, it can also be configured with a plural.

[0162] Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but it goes without saying that various modifications may be made within the limits not departing from the scope of the present disclosure.

Claims

1. A method performed by an E2 node, the method comprising: Sending an E2 setup request message to a near real-time (RT) radio access network (RAN) intelligent controller (RIC); as well as Receive E2 Setup Response message from near RT RIC, The E2 establishment request message includes: Information indicating an E2 interface between an E2 node and a near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and Information used to indicate the version of the E2 Application Protocol (E2AP) of the radio network layer in the E2 interface between the E2 node and the near-RT RIC.

2. The method according to claim 1, in, Information indicating the version of the E2AP and information for indicating the E2 interface are included in an E2 node component configuration addition list information element (IE) of the E2 setup request message, and The information indicating the version of E2AP is encoded after the information indicating the E2 interface.

3. The method according to claim 1, in, Information for indicating the E2 interface is included in the E2 node component configuration addition list information element (IE) of the E2 setup request message, and The information indicating the version of E2AP is encoded at the end of the E2 setup request message.

4. The method according to claim 1, in, The E2 setup request message also includes a message type of the E2 setup request message, a transaction identifier (ID) of the E2 setup request message and a global ID of the E2 node, and The information indicating the version of the E2AP is encoded after the global ID of the E2 node.

5. The method according to claim 1, wherein: The information indicating the version of E2AP is used for backward compatibility of E2AP.

6. A method performed by a near real-time (RT) radio access network (RAN) intelligent controller (RIC), the method comprising: Receive an E2 setup request message from the E2 node; as well as Send an E2 establishment response message to the E2 node, The E2 establishment request message includes: Information indicating an E2 interface between an E2 node and a near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and Information used to indicate the version of the E2 Application Protocol (E2AP) of the radio network layer in the E2 interface between the E2 node and the near-RT RIC.

7. The method according to claim 6, in, Information indicating the version of the E2AP and information for indicating the E2 interface are included in an E2 node component configuration addition list information element (IE) of the E2 setup request message, and The information indicating the version of E2AP is placed after the information indicating the E2 interface.

8. The method according to claim 6, in, Information for indicating the E2 interface is included in the E2 node component configuration addition list information element (IE) of the E2 setup request message, and The information indicating the version of E2AP is placed at the end of the E2 setup request message.

9. The method according to claim 6, in, The E2 setup request message also includes a message type of the E2 setup request message, a transaction identifier (ID) of the E2 setup request message and a global ID of the E2 node, and Here, information indicating the version of the E2AP is placed after the global ID of the E2 node.

10. The method according to claim 6, wherein: The information indicating the version of E2AP is used for backward compatibility of E2AP.

11. A device of an E2 node, the device comprising: at least one transceiver; and at least one processor electrically connected to the at least one transceiver, Wherein, the at least one processor is configured to: sending an E2 Setup Request message to a Near Real-Time (RT) Radio Access Network (RAN) Intelligent Controller (RIC), and Receive E2 Setup Response message from near RT RIC, The E2 establishment request message includes: Information indicating an E2 interface between an E2 node and a near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and Information used to indicate the version of the E2 Application Protocol (E2AP) of the radio network layer in the E2 interface between the E2 node and the near-RT RIC.

12. The device according to claim 11, in, The at least one processor is configured to perform one of the methods of claims 2 to 5.

13. A device of a near real-time (RT) radio access network (RAN) intelligent controller (RIC), the device comprising: at least one transceiver; and at least one processor electrically connected to the at least one transceiver, Wherein, the at least one processor is configured to: receiving an E2 Setup Request message from the E2 node, and Send an E2 establishment response message to the E2 node, The E2 establishment request message includes: Information indicating an E2 interface between an E2 node and a near-RT RIC among an NG interface, an XN interface, an E1 interface, an F1 interface, a W1 interface, an S1 interface, an X2 interface, and an E2 interface, and Information used to indicate the version of the E2 Application Protocol (E2AP) of the radio network layer in the E2 interface between the E2 node and the near-RT RIC.

14. The device according to claim 13, in, The at least one processor is configured to perform one of the methods of claims 7 to 10.

Images