Electronic device and method for a subscribing process

Abstract

The present disclosure relates to a 5th-Generation (5G) or pre-5G communication system for supporting a data transmission rate higher than a data transmission rate of a 4th-Generation (4G) communication system such as Long Term Evolution (LTE). In an embodiment of the present disclosure, a device executed by an E2 node may include at least one transceiver and at least one processor coupled to the at least one transceiver. At least one processor may be configured to receive a near real-time (near RT) RAN (Radio Access Network) Intelligent Controller (RIC) subscription request message from an RIC. The at least one processor may be configured to send an RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

Description

Technical Field

[0001] The following description relates to electronic devices and methods for a subscription process. Background Art

[0002] In order to meet the growing demand for wireless data services after the commercialization of the 4G (fourth generation) communication system, efforts have been made to develop an improved 5G (fifth generation) communication system or pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is called a super 4G network communication system or a post-long term evolution (LTE) system.

[0003] In order to achieve high data transmission rates, implementation of 5G communication systems in the millimeter wave (mmWave) band (e.g., 60 GHz band) is being considered. In order to mitigate the path loss of radio waves in the mmWave band and extend the propagation distance of radio waves, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are being discussed in 5G communication systems.

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

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

[0006] With the commercialization of 5G systems and new radio or next generation radio (NR) to meet the demand for wireless data services, high data rate services are being provided to users through the 5G system similar to 4G, and it is expected to provide various wireless communication services including the Internet of Things (IoT) and services that require high reliability for specific purposes. In the current system where the 4th generation communication system and the 5th generation communication system are mixed, the open radio access network (O-RAN) established by operators and equipment providers defines the E2 application protocol (E2AP) standard in the application protocol of the E2 interface between the E2 node and the near real-time (near RT) radio access network (RAN) intelligent controller (RIC).

[0007] The above information may be provided as related art for the purpose of assisting understanding of the present disclosure. No statement or determination is made as to whether any of the above information may be applicable as prior art related to the present disclosure. Summary of the invention

[0008] Technical Solution

[0009] In an embodiment of the present disclosure, a method performed by an E2 node is provided. The method may include receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The method may include sending a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0010] In an embodiment of the present disclosure, a method performed by an E2 node is provided. The method may include receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The method may include sending a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0011] In an embodiment of the present disclosure, a method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) is provided. The method may include sending a RIC subscription request message to an E2 node. The method may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0012] In an embodiment of the present disclosure, a method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) is provided. The method may include sending a RIC subscription request message to an E2 node. The method may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0013] In an embodiment of the present disclosure, a device performed by an E2 node is provided. The device 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 a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to send a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0014] In an embodiment of the present disclosure, a device performed by an E2 node is provided. The device 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 a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to send a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0015] In an embodiment of the present disclosure, a device performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) is provided. The device 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 a RIC subscription request message to an E2 node. The at least one processor may be configured to receive a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0016] In an embodiment of the present disclosure, a device performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) is provided. The device 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 a RIC subscription request message to an E2 node. The at least one processor may be configured to receive a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0017] In an embodiment of the present disclosure, a non-transitory storage medium is provided. The non-transitory storage medium may include a memory storing instructions. The instructions, when executed by at least one processor, may cause an E2 node to receive a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) and send a RIC subscription response message to the near RT RIC. According to an embodiment, the RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function. According to an embodiment, the RIC subscription request message may include an event trigger definition list containing one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0018] In an embodiment of the present disclosure, a non-transitory storage medium is provided. The non-transitory storage medium may include a memory storing instructions. The instructions, when executed by at least one processor, may cause a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) to send a RIC subscription request message to an E2 node and receive a RIC subscription response message from the E2 node. According to an embodiment, the RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions. According to an embodiment, the RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 2a An example of a 5th generation (5G) non-standard alone (NSA) system is shown.

[0021] Figure 2b An example of the architecture of O-RAN is shown.

[0022] Figure 3 A protocol stack of an E2 application protocol message in a wireless access network according to an embodiment is shown.

[0023] Figure 4 An example of a connection between a base station and a radio access network intelligent controller (RIC) in a wireless access network according to an embodiment is shown.

[0024] Figure 5 The configuration of devices in a radio access network according to various embodiments is shown.

[0025] Figure 6Schematic diagram showing logical functions related to E2 messages and RIC of an E2 node in a wireless access network according to an embodiment.

[0026] Figure 7 An example of a functional split between an E2 node and a RIC according to an embodiment is shown.

[0027] Figure 8 Implementation of an E2 node and a RIC according to an embodiment is shown.

[0028] Fig. 9 An example of a functional split between a centralized unit (CU) and a RIC according to an embodiment is shown.

[0029] Fig.10 An example of a subscription process of an E2 node and an RIC according to an embodiment is shown.

[0030] Fig.11a An example of mapping between applications and radio access network (RAN) functions according to an embodiment is shown.

[0031] Fig.11b An example of multiple subscription processes for an E2 node and an RIC for a service is shown.

[0032] Fig.12 An example of a subscription procedure for supporting multiple RAN functions according to an embodiment is shown.

[0033] Fig.13 An example of a subscription process for supporting multiple event trigger definitions according to an embodiment is shown.

[0034] Fig.14 An example of a subscription process for supporting multiple RAN functions and multiple event trigger definitions according to an embodiment is shown. DETAILED DESCRIPTION

[0035] The terms used in this disclosure are only used to describe specific embodiments and may not be intended to limit the scope of another embodiment. Unless the context clearly indicates otherwise, a singular expression may include a plural expression. The terms used herein (including technical or scientific terms) may have the same meaning as the meanings generally understood by those of ordinary skill in the art described in this disclosure. Among the terms used in this disclosure, the terms defined in a general dictionary may be interpreted as meanings identical or similar to the contextual meanings of the relevant technology, and unless clearly defined in this disclosure, are not interpreted as ideal or overly formal meanings. In some cases, even the terms defined in this disclosure may not be interpreted as excluding embodiments of the present disclosure.

[0036] In various embodiments of the present disclosure described below, a hardware method will be described as an example. However, since various embodiments of the present disclosure include techniques using both hardware and software, various embodiments of the present disclosure do not exclude software-based methods.

[0037] 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. Specifically, the present disclosure relates to a process, message, and method for an E2 node and an RIC to perform a standard-compliant operation and ensure backward compatibility by providing a version number (e.g., E2AP 2.02) of the E2AP standard from the E2 node to the RIC over an E2 interface.

[0038] Terms used in the following description referring to configurations (e.g., settings, settings, arrangements, controls), terms referring to signals (e.g., packets, messages, signals, information, signaling), terms referring to resources (e.g., segments, symbols, time slots, subframes, radio frames, subcarriers, resource elements (REs), resource blocks (RBs), bandwidth parts (BWPs), opportunities), terms referring to operating 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 (e.g., distributed unit (DU), radio unit (RU), central unit (CU), control plane (CU-CP), user plane (CU-UP), open radio access network (O-RAN) DU (O-DU), O-RAN RU (O-RU), O-RAN CU (O-CU), O-RAN CU-CP (O-CU-UP), O-RAN CU-CP (O-CU-CP)), terms referring to device components, etc., are exemplified for convenience of explanation. Therefore, the present disclosure is not limited to the terms to be described below, and another term with an equivalent technical meaning may be used. In addition, the terms used below such as "... unit", "... device", "... object" and "... structure" may refer to at least one shape structure, or may refer to a unit of a processing function.

[0039] In addition, in the present disclosure, the term "greater than" or "less than" can be used to determine whether a specific condition is met or satisfied, but this is only a description of an expression example and does not exclude the description of "greater than or equal to" or "less than or equal to". The condition described as "greater than or equal to" can be replaced with "greater than", the condition described as "less than or equal to" can be replaced with "less than", and the condition described as "greater than or equal to and less than" can be replaced with "greater than and less than or equal to". In addition, hereinafter, "A" to "B" refers to at least one of the elements of A (including A) to B (including B). hereinafter, "C" and / or "D" refers to at least one of "C" or "D", i.e., {"C", "D", and "C" and "D"}.

[0040] In addition, the present disclosure uses terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), Scalable Radio Access Network (xRAN), Open Radio Access Network (O-RAN)) to describe various embodiments, but these are merely examples for illustration. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0041] With the commercialization of 4th generation (4G) / 5th generation (5G) communication systems (e.g., New Radio (NR)), differentiated service support for users in virtualized networks has become required. 3GPP is a joint research project between mobile communication related organizations that aims to develop globally applicable third generation mobile communication system standards within the scope of the IMT-2000 project of the International Telecommunication Union (ITU). 3GPP was established in December 1998. The 3GPP standards are based on advanced GSM standards and cover radio, core network and service architectures within the scope of standardization. Accordingly, the open radio access network (O-RAN) newly defines the radio unit (RU), digital unit (DU), central unit (CU)-control plane (CP) and CU-user plane (CU-UP) as O-RAN (O)-RU, O-DU, O-CU-CP and O-CU-UP, respectively, and further standardizes the near real-time (NRT) radio access network intelligent controller (RT). The present disclosure is used to support 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, the O-DU, the O-CU-CP, and the 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 E2 Application Protocol (E2AP) is used between the RIC and the E2 node, and the E2 Application Protocol (E2AP) is used as an interface for objects constituting a RAN capable of operating according to the O-RAN standard.

[0042] RIC is a logical node capable of collecting information about the cell site sent and received by the terminal and O-DU, O-CU-CP or O-CU-UP. RIC can be implemented in the format of a server centrally located in one physical location. The connection between O-DU and RIC, O-CU-CP and RIC, and O-CU-UP and RIC can be established through Ethernet. To this end, interface standards for communication between O-DU and RIC, O-CU-CP and RIC, and O-CU-UP and RIC have become necessary, and message standards for E2-DU, E2-CU-CP and E2-CU-UP and definitions of procedures between RIC and O-DU, O-CU-CP and O-CU-UP are required. In particular, differentiated service support for users is required in virtualized networks, and by centralizing call processing messages / functions generated in O-RAN to RIC, functional definitions of messages for E2-DU, E2-CU-CP and E2-CU-UP are required to support services for wide cell coverage.

[0043] RIC can communicate with O-DU, O-CU-CP and O-CU-UP using the E2 interface, and can set event occurrence conditions by generating and sending subscription messages. Specifically, RIC can set call processing events by generating an E2 subscription request message and sending it to an E2 node (e.g., O-CU-CP, O-CU-UP, O-DU). In addition, after setting the event, the E2 node transmits the transmitted subscription request response message to the RIC.

[0044] The E2 node may send the current status to the RIC via an E2 indication / report. The RIC may provide control of the O-DU, O-CU-CP, and O-CU-UP using an E2 control message. Various embodiments of the present disclosure propose an E2 indication message that sends measurement information for each UE at a time period set by a subscription event condition in the O-DU. In addition, various embodiments of the present disclosure propose a message for controlling resources sent from the RIC to the O-DU.

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

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

[0047] The base station 110 is a network infrastructure that provides wireless access to the terminal 120. For example, the base station 110 is a device that performs scheduling by collecting status information such as the buffer status, available transmission power, and channel status of the terminal 110. The base station 110 has a coverage area 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 to a base station, the base station 110 may also be referred to as an "access point (AP)", "eNodeB (eNB)", "radio point", "transmission / reception point (TRP)" or another term with equivalent technical meaning.

[0048] The terminal 120 is a device used by a user, and performs communication with the base station 110 through a wireless channel. In some cases, the terminal 120 can be operated without user participation. That is, at least one of the terminal 120 and the terminal 130, which are devices for performing machine type communication (MTC), may not be carried by the user. In addition to the terminal, the terminal 120 may also be referred to as "user equipment (UE)", "mobile station", "subscriber station", "customer-premises equipment (CPE)", "remote terminal", "wireless terminal" or "user equipment" or another term with equivalent technical meaning.

[0049] The S-GW 130 provides a data bearer and creates or controls the data bearer according to the control of the MME 150. For example, the S-GW 130 processes 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 when switching between base stations of the terminal 120. The P-GW 140 may be used as a connection point with an external network (e.g., the Internet). In addition, the P-GW 140 allocates an Internet Protocol (IP) address to the terminal 120 and serves 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.

[0050] 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 linked with a Serving GPRS Support Node (SGSN).

[0051] 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 is connected to the network.

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

[0053] Carrier aggregation (hereinafter, CA) technology is a technology that combines multiple component carriers and increases frequency usage efficiency in terms of terminals or base stations because the terminal uses multiple component carriers to send and receive signals at the same time. Specifically, according to the CA technology, the terminal and the base station can use broadband to send and receive signals by using multiple component carriers in the uplink (UL) and downlink (DL), respectively, and at this time, each component carrier is in a different frequency band. Hereinafter, uplink refers to a communication link through which the terminal sends a signal to the base station, and downlink refers to a communication link through which the base station sends a signal to the terminal. At this time, the number of uplink component carriers and downlink component carriers may be different from each other.

[0054] Dual connectivity or multi-connectivity is a technology in which a terminal is connected to multiple different base stations to simultaneously send and receive signals using carriers in multiple base stations located in different frequency bands, thereby increasing the frequency usage efficiency on the terminal or base station side. The terminal can be simultaneously connected to a first base station (for example, a base station providing services using LTE technology or 4th generation mobile communication technology) and a second base station (for example, a base station providing services using new radio (NR) technology or 5th generation (5G) mobile communication technology) to send and receive services. In this case, the frequency resources used by each base station can be located in different frequency bands. As described above, the method of operating based on the dual connectivity method of LTE and NR can be referred to as 5G non-standalone networking (NSA).

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

[0056] 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 can be connected to EPC 150, 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. In this document, the NR base station may be referred to as a "5th generation node (5G node)", "next generation nodeB (gNB)" or another term with equivalent technical meaning. In addition, the NR base station may have a structure separated into a central unit (CU) and a digital unit (DU), and in addition, the CU may have a structure separated into a CU-control plane (CP) unit and a CU-user plane (UP) unit.

[0057] In a structure such as FIG. 2 , the terminal 220 may perform a radio resource control (RRC) connection through a first base station (e.g., a base station belonging to the LTE RAN 210b) and may be served by functions provided in the control plane (e.g., connection management, mobility management, etc.). In addition, the terminal 220 may 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 RAN 210a). This dual connection technology using LTE and NR may be referred to as Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connection (EN-DC). Similarly, a dual connection technology in which the first base station uses NR technology and the second base station uses LTE technology is referred to as NR-E-UTRA Dual Connection (NE-DC). In addition, various embodiments may be applied to various forms of multi-connection and carrier aggregation technologies. In addition, various embodiments may be applied even if a first system using a first communication technology and a second system using a second communication technology are implemented in one device, or the first base station and the second base station are located in the same geographical location.

[0058] Figure 2b An example of the architecture of O-RAN is shown. For the purpose of E2-SM-Key Performance Indicator (KPI) Monitoring (KPIMON) of the E2 service model, O-RAN non-standalone mode in multi-connectivity operation using E-UTRA and NR radio access technologies is considered and the E2 node is assumed to be in O-RAN stand alone mode.

[0059] refer to Figure 2bIn O-RAN non-standalone mode deployment, the eNB is connected to the EPC through the S1-C / S1-U interface and to the O-CU-CP through the X2 interface. For O-RAN standalone mode deployment, the O-CU-CP can be connected to the 5G core (5GC) through the N2 / N3 interface.

[0060] Figure 3 FIG. 4 shows a protocol stack of an E2 application protocol message in a wireless access network according to an embodiment. 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 .

[0061] The wireless network layer includes an E2AP 350. The E2AP 350 is used to transmit a subscription message, an indication message, a control message, a service update message, and a service query message, and they are transmitted in a higher layer of the SCTP 340 and the IP 330.

[0062] Figure 4 An example of a connection between a base station and a radio access network intelligent controller (RIC) in a wireless access network according to an embodiment is shown.

[0063] refer to Figure 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 functions for new services or regional resource optimization. RIC 440 can provide functions such as network intelligence (e.g., policy implementation, switching optimization), resource guarantee (e.g., radio link management, advanced self-organizing network (SON)), and resource control (e.g., load balancing, slicing strategy). RIC 440 can perform communication with O-CU-CP 420, O-CU-UP410, O-DU 430. RIC 440 can be connected to each node through E2-CP, E2-UP, E2-DU interfaces. In addition, the interface between O-CU-CP and DU and 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, CU-UP and O-CU-UP can be used interchangeably.

[0064] Figure 4 One RIC 440 is shown, but multiple RICs may exist in various embodiments. Multiple RICs may be implemented using multiple hardware located in the same physical location, or may be implemented using one hardware through virtualization.

[0065] Figure 5The configuration of devices in a radio access network according to various embodiments is shown. Figure 5 The structure illustrated in can be understood as having Figure 5 The term "... unit", "... device" and the like used below means a unit that processes at least one function or operation, and it can be implemented by hardware or software, or a combination of hardware and software.

[0066] refer to Figure 5 , the core network device is configured to include a communication unit 510, a storage unit 520 and a control unit 530.

[0067] The communication unit 510 provides an interface for performing communication with other devices in the network. That is, the communication unit 510 converts a bit stream 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 stream. 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.

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

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

[0070] Figure 6 Schematic diagram showing logical functions related to E2 messages and RIC of an E2 node in a wireless access network according to an embodiment.

[0071] refer to Figure 6, the RIC 640 and the E2 node 610 can send or receive E2 messages between 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. In addition, for example, the E2 node 610 can communicate with the E2 node 616 through an X2 interface or an XN interface. In addition, 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).

[0072] The E2 node 610 may include an E2 node function 612. The E2 node function 612 is a function corresponding to a specific application S / W (xApp) 646 installed in the RIC 640. For example, in the case of a KPI monitor, a KPI monitor set S / W is installed in the RIC 640, and the E2 node 610 may include an E2 node function 612, which generates a KPI parameter and then sends an E2 message including the KPI parameter to an E2 termination 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 wireless network provided to a terminal.

[0073] The E2 termination 642 located in the RIC 640 is a termination of the RIC 640 for E2 messages, and performs a function of interpreting the E2 message sent by the E2 node 610 and then sending it to the xApp 646. The database DB 644 located in the RIC 640 can be used for the E2 termination 624 or the xApp 616. Figure 6 The E2 node 610 shown in FIG. 6 is a termination of at least one interface and can be understood as a termination of a message sent to a terminal, a peripheral base station, and a core network.

[0074] Figure 7 An example of a functional split between an E2 node and a RIC according to an embodiment is shown. The O-RAN standard provides a functional split between an E2 node and a RIC. For example, the E2 node may be a CU. 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 send commands. Functional split options may include a functional split 700 of managing the entire radio resource management (RRM) in a near-RT RIC and a functional split 750 of selectively managing RRM in a near-RT RIC.

[0075] According to the WG3 decision of the 2019 / 01 / 16 meeting, the near-RT RIC is expected to support E2 as an open logical interface for a multi-vendor environment, regardless of the implementation of the specific RRC-RRM algorithm located in the near-RT RIC. In the present disclosure, an E2 Service Model Radio Interface Control (E2SM-RIC) may be proposed, which is paired with an E2SM-NI capable of performing injection / modification / configuration of per-UE RRC messages for each I / F and network entity (NE). In other words, in the functional split 750, the near-RT RIC may be gradually improved in the direction of the functional split 700. E2 may evolve into an open logical interface that is independent of the implementation of the specific RRC-RRM algorithm in the near-RT RIC while targeting a multi-vendor environment.

[0076] Figure 8 An implementation of an E2 node and RIC according to an embodiment is shown. In the scenario of implementation example 800, the E2 node (e.g., O-DU, O-CU) and RIC can be virtualized on a cloud platform (e.g., an open chassis and blade specification edge cloud) and configured on a device (e.g., a server). Such a scenario can support deployment in dense urban areas with abundant fronthaul capacity, which allows BBU functions to be pooled at a central location with low latency sufficient to meet O-DU latency requirements. Therefore, there may be no need to attempt to centralize near-RT RICs beyond the limitations of centralized O-DU functions. According to an embodiment, the E2SM-RIC can be optimized for an O-RAN deployment scenario, where the near-RT RIC, O-CU, and O-DU are implemented on an O-Cloud platform.

[0077] Fig. 9 An example of a functional split between a centralized unit (CU) and a RIC according to an embodiment is shown. Fig. 9 , functional splitting can be performed based on deployment scenario #1 900 or functional deployment scenario #2 950.

[0078] Deployment scenario #1 900: RIC is located at a separate site or exists only as another NE, replacing or recommending some intelligent key functions.

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

[0080] exist Fig. 9In the embodiment, two scenarios are shown, but other scenarios may apply. As an example, in deployment scenario #1 900, mobility functions may be performed by the RIC instead of the CU. Also, as an example, in deployment scenario #1 900, UE context functions may be performed by the RIC instead of the CU. Also, as an example, in deployment scenario #1 900, session establishment functions may be performed by the RIC instead of the CU.

[0081] The present disclosure relates to an electronic device and method for controlling an E2 node through an RIC in a radio access network. The present disclosure provides an electronic device and method for controlling an E2 node through an E2 message complying with an open radio access network (O-RAN) standard of a wireless communication system.

[0082] In addition, the present disclosure provides an electronic device and method for sending a message format and / or information element (IE) to a radio access network (RAN) intelligent controller (RIC) in a wireless communication system to enable subscription to multiple services in a service subscription process of an O-RAN E2 application protocol (E2AP) of an E2 node.

[0083] The apparatus and method according to an embodiment of the present disclosure enable subscription to multiple services in one subscription process, because in a wireless communication system a radio access network (RAN) intelligent controller (RIC) sends a subscription request message to an E2 node in a message format including one or more radio access network (RAN) functions and / or one or more event trigger definitions.

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

[0085] Fig.10 An example of a subscription process of an E2 node and a RIC according to an embodiment is shown. The RIC subscription process can be used to establish an E2 subscription consisting of an event trigger and an action sequence. The O-RAN Working Group (WG) 3 Near-Real-Time RAN Intelligent Controller Architecture & E2 General Aspects and Principles (E2GAP) standard defines a near-RT RIC as a service consumer and an E2 node as a service producer. The near-RT RIC can perform a RIC subscription process to receive services. The standard specifies that the near-RT RIC sends a RIC subscription request message for the RIC subscription process. The near-RT RIC 1010 illustrates the process of receiving a service through Figures 1 to 9The E2 node 1020 illustrates an RIC (eg, RIC 640) described above. Figures 1 to 9 An E2 node (eg, E2 node 610 ) is described.

[0086] refer to Fig.10 In operation S1001, the near RT RIC 1010 may send a RIC subscription request message (eg, RIC subscription request message) to the E2 node 1020. The RIC subscription request message may include information about RAN functions.

[0087] In operation S1003, the E2 node 1020 may send a RIC subscription response message (eg, RIC subscription response message) to the near RT RIC 1010. If there is no error in the RIC subscription request message and the RAN function of the RIC subscription request message is supportable, the E2 node 1020 may send the RIC subscription response message to the near RT RIC 1010.

[0088] Although not in Fig.10 As shown in the figure, however, if the E2 node 1020 does not allow at least one requested action, or detects inconsistencies in the action sequence and / or action definition, or a failure occurs during the RIC subscription process, the E2 node 1020 may send a RIC subscription failure message (e.g., a RIC subscription failure message) to the near-RT RIC 1010.

[0089] Fig.11a An example of mapping between applications and radio access network (RAN) functions according to an embodiment is shown.

[0090] refer to Fig.11a , a near-RT RIC (e.g., near-RT RIC 1010) may include a RIC subscription manager. An E2 node (e.g., E2 node 1020) may include a DU. A service refers to a service provided by the E2 node 1020 to provide access to messages and measurements and to control the E2 node 1020 from the near-RT RIC 1010. A RAN function refers to a specific function in an E2 node. For example, a RAN function may include X2AP, F1AP, E1AP, S1AP, NGAP interfaces for processing UE and / or cell and RAN internal functions. An xApp is an application designed to be executed in the near-RT RIC 1010. Such an application is likely to consist of one or more microservices and may identify what data it consumes and provides when onboarding. The application is independent of the near-RT RIC 1010 and may be provided by a third party. The E2 interface enables a direct connection between the xApp and RAN functions.

[0091] Multiple RAN functions may be used to perform a service. For example, one RAN function among multiple RAN functions may include cell-level KPI reporting. As an example, the event trigger definition ID may be "4". For example, one RAN function among multiple RAN functions may include node configuration. As an example, the event trigger definition ID may be "1". For example, one RAN function among multiple RAN functions may include UE KPI reporting. As an example, the event trigger definition ID may be "2". For example, one RAN function among multiple RAN functions may include UE ID reporting. As an example, the event trigger definition ID may be "5".

[0092] Fig.11b An example of multiple subscription processes for E2 nodes and RIC for services is shown. Fig.11b middle, Fig.11a UE ID reporting, UE KPI reporting and cell-level KPI reporting among the RAN functions mentioned in can be used for the service.

[0093] refer to Fig.11b In process S1150, a near-RT RIC (e.g., near-RT RIC 1010) may perform an E2 establishment process with an E2 node (e.g., E2 node 1020). The purpose of the E2 establishment process is to establish a signaling connection between the E2 node 1020 and the near-RT RIC 1010. The E2 establishment process may delete existing application-level configuration data between the two nodes and replace the data with the received data. The E2 node 1020 may send an E2 establishment request message (e.g., an establishment request message) to the near-RT RIC 1010. The near-RT RIC 1010 may send an E2 establishment response message (e.g., an establishment response message) to the E2 node 1020.

[0094] The E2 setup request message of the E2 setup procedure may include a RAN function ID. The E2 setup request message may include a RAN function definition corresponding to the RAN function ID, the RAN function ID corresponding to each RAN function ID. The RAN function definition may include a description of the RAN function. The RAN function may be specific to the E2 service model. Subsequently, in the process, the RAN function may be indicated via the RAN function ID.

[0095] After the E2 establishment process, a subscription process S1160 may be performed for service provision. The service may request UEID reporting, UE KPI reporting, and cell-level KPI reporting. The near-RT RIC 1010 may request subscription to three services ("UE ID reporting" service, "UE KPI reporting" service, and "cell-level KPI reporting" service) from the E2 node 1020. That is, for the above functions, the near-RT RIC 1010 may require three subscription processes (S1161, S1163, S1165) with the E2 node 1020. Each message for service subscription may include a RAN function and an event trigger definition related to the RAN function, as shown in the following table.

[0096] [Table 1]

[0097]

[0098] In the first subscription process S1161, the near RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near RT RIC 1010. After the first subscription process S1161, in operation S1171, the first RIC indication of the reporting process S1170 may be performed. The E2 node 1020 may send a RIC indication message including a UE ID report to the near RT RIC 1010.

[0099] In the second subscription process S1163, the near RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near RT RIC 1010. After the second subscription process S1163, in operation S1173, the second RIC indication of the reporting process S1170 may be performed. The E2 node 1020 may send a RIC indication message including a UE KPI report to the near RT RIC 1010.

[0100] In the third subscription process S1165, the near RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near RT RIC 1010. After the third subscription process S1165, in operation S1175, the third RIC indication of the reporting process S1170 may be performed. The E2 node 1020 may send a RIC indication message including a cell-level KPI report to the near RT RIC 1010.

[0101] As shown in Table 1, the format of the RIC subscription request message (e.g., RIC Subscription Request message) includes one RAN Function ID Information Element (IE) and one RIC Event Trigger Definition IE. Therefore, in the case of performing multiple functions related to a specific service, the near-RT RIC 1010 has a problem of having to perform a separate subscription process for each function. As the number of multiple functions increases, the number of subscription processes increases. Since one subscription process includes a request and a response, an overflow occurs. The overflow causes a delay in service provision between the near-RT RIC 1010 and the E2 node 1020.

[0102] In order to solve the above problems, the embodiments of the present disclosure propose a format of a RIC subscription request message that can support multiple RAN functions and / or multiple event trigger definitions. Here, supporting multiple RAN functions and / or multiple event trigger definitions means that the format of the IE in the RIC subscription request message is configured to include multiple items. Therefore, the RIC subscription request message according to the embodiments of the present disclosure should not be interpreted as necessarily including multiple RAN function IDs and / or multiple event trigger definitions.

[0103] Fig.12 An example of a subscription process for supporting multiple RAN functions according to an embodiment is shown. Fig.12 In the RIC subscription request process according to an embodiment of the present disclosure, a subscription process using a single RIC subscription request message in a list format with a RAN function ID IE is described.

[0104] refer to Fig.12 In process S1150, the near-RT RIC (e.g., the near-RT RIC 1010) may perform an E2 establishment process with an E2 node (e.g., the E2 node 1020). The E2 node 1020 may send an E2 establishment request message (e.g., an establishment request message) to the near-RT RIC 1010. The near-RT RIC 1010 may send an E2 establishment response message (e.g., an establishment response message) to the E2 node 1020. The description of the E2 establishment process may refer to Fig.11b .

[0105] After the E2 establishment process, a subscription process S1210 may be performed for service provision. The service may request a UEID report, a UE KPI report, and a cell-level KPI report. The near-RT RIC 1010 may perform subscription to three services through one subscription process S1210. The near-RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near-RT RIC 1010. After the subscription process S1210, a reporting process S1170 may be performed. In operation S1171, the E2 node 1020 may send a RIC indication message including a UE ID report to the near-RT RIC 1010. In operation S1173, the E2 node 1020 may send a RIC indication message including a UE KPI report to the near-RT RIC 1010. In operation S1175 , the E2 node 1020 may send a RIC indication message including a cell-level KPI report to the near RT RIC 1010 .

[0106] The RIC subscription request message according to the embodiment may have a message structure for providing multiple RAN functions. For example, the message structure is shown in the following table.

[0107] [Table 2]

[0108]

[0109] According to an embodiment, one or more RAN function IDs may be configured in a list format. The message structure of the RIC subscription request message using the "RAN function list" IE may be configured such that multiple RAN function ID IEs are included in one RIC subscription request message. In addition, one event trigger definition IE may be associated with one RAN function ID IE. That is, one event trigger definition may be mapped to one RAN function ID. The RIC subscription request message including the "RAN function list" IE may be configured such that multiple event trigger definition IEs are included in one RIC subscription request message.

[0110] The RIC subscription response message according to the embodiment may include a permitted list. The permitted list may include at least one RAN function ID permitted by the E2 node among the one or more RAN function IDs of the RIC subscription request message. On the other hand, in another embodiment, the RIC subscription response message may include an unpermitted list. The unpermitted list may include at least one RAN function ID not permitted by the E2 node among the one or more RAN function IDs of the RIC subscription request message. For example, the message structure of the RIC subscription response message is shown in the following table.

[0111] [Table 3]

[0112]

[0113] According to an embodiment, the E2 node 1020 may obtain the RAN function ID of the RIC subscription request message from the near RT RIC 1010. The E2 node 1020 may identify whether the RAN function corresponding to each RAN function ID is permitted. The E2 node 1020 may send a RIC subscription response message including a list (e.g., RAN function permitted list IE) including at least one permitted RAN function ID to the near RT RIC 1010. In some embodiments, the RIC subscription response message may also include a list (e.g., RAN function unpermitted list IE) including at least one unpermitted RAN function ID.

[0114] For example, Fig.11a As shown, each event trigger definition may include an event trigger condition ID and a report ID. The event trigger condition ID may be mapped to each RAN function. In order to consume services corresponding to multiple event trigger conditions (e.g., event trigger condition IDs with "1", "2", "4", "5") through one subscription process, the E2 node may include the RAN function corresponding to each event trigger condition in a RAN function list (e.g., RAN function list).

[0115] Fig.13 An example of a subscription process for supporting multiple event trigger definitions according to an embodiment is shown. Fig.13 In the present invention, a subscription process using a single RIC subscription request message having a list format is described, so that multiple event trigger definition IEs of the RAN function for the RIC subscription request message according to an embodiment of the present disclosure are included in the RIC subscription request message.

[0116] refer to Fig.13 In process S1150, the near-RT RIC (e.g., the near-RT RIC 1010) may perform an E2 establishment process with an E2 node (e.g., the E2 node 1020). The E2 node 1020 may send an E2 establishment request message (e.g., an establishment request message) to the near-RT RIC 1010. The near-RT RIC 1010 may send an E2 establishment response message (e.g., an establishment response message) to the E2 node 1020. The description of the E2 establishment process may refer to Fig.11b .

[0117] After the E2 establishment process, a subscription process S1310 may be performed for service provision. For example, a RAN function may be defined as "SLA guarantee". Multiple event trigger definitions may be mapped to one RAN function. Multiple event trigger definitions may include "UE ID report", "per UE KPI report" and "cell KPI report". The near-RT RIC 1010 may perform subscription to three services through one subscription process S1310. The near-RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near-RT RIC 1010. After the subscription process S1400, a reporting process S1170 may be performed. In operation S1171, the E2 node 1020 may send a RIC indication message including a UEID report to the near-RT RIC 1010. In operation S1173, the E2 node 1020 may send a RIC indication message including a UE KPI report to the near-RT RIC 1010. In operation S1175 , the E2 node 1020 may send a RIC indication message including a cell-level KPI report to the near RT RIC 1010 .

[0118] According to the embodiment, the RIC subscription request message may have a message structure for providing multiple event trigger definitions. For example, the message structure is shown in the following table.

[0119] [Table 4]

[0120]

[0121] According to an embodiment, one or more event trigger definitions may be configured in a list format. One or more event trigger definition IEs (e.g., at least two event trigger definition IEs) may be associated with one RAN function ID IE. That is, one or more event trigger definitions may be mapped to one RAN function ID. For the above mapping, the RIC subscription request message may include a "RIC event trigger definition list" IE.

[0122] According to an embodiment, the RIC subscription response message may include a permission list. The permission list may include at least one event trigger definition permitted by the E2 node in one or more event trigger definitions of the RIC subscription request message. On the other hand, in another embodiment, the RIC subscription response message may include an unpermitted list. The unpermitted list may include at least one event trigger definition not permitted by the E2 node in one or more event trigger definitions of the RIC subscription request message. For example, the message structure of the RIC subscription response message is shown in the following table.

[0123] [Table 5]

[0124]

[0125] exist Fig.12 In, a RIC subscription request message including a RAN function list IE for receiving multiple RAN function IDs is described. Fig.13 In the present invention, a RIC subscription request message including an event trigger definition list IE for receiving a plurality of event trigger definitions is described. The event trigger definition may be associated with one or more services provided according to a RIC service style type within a RAN function. Thus, it is possible to combine Fig.12 The message formats (e.g., Table 2 and Table 3) and Fig.13 message formats (e.g., Table 4 and Table 5).

[0126] Fig.14 An example of a subscription process for supporting multiple RAN functions and multiple event trigger definitions according to an embodiment is shown. Fig.14 In the present disclosure, a subscription process for providing multiple RAN function IDs and multiple event trigger definitions to an E2 node via a single RIC subscription request message according to an embodiment of the present disclosure is described.

[0127] refer to Fig.14 In process S1150, the near-RT RIC (e.g., the near-RT RIC 1010) may perform an E2 establishment process with an E2 node (e.g., the E2 node 1020). The E2 node 1020 may send an E2 establishment request message (e.g., an establishment request message) to the near-RT RIC 1010. The near-RT RIC 1010 may send an E2 establishment response message (e.g., an establishment response message) to the E2 node 1020. The description of the E2 establishment process may refer to Fig.11b .

[0128] After the E2 establishment process, a subscription process S1410 may be performed for service provision. A specific service may require multiple RAN functions. In addition, in each RAN function, the definition of one or more event trigger definitions according to the RIC service style type may be required. The near-RT RIC 1010 can perform subscriptions to multiple services through one subscription process S1410. The near-RT RIC 1010 may send a RIC subscription request message to the E2 node 1020. Thereafter, the E2 node 1020 may send a RIC subscription response message to the near-RT RIC 1010. After the subscription process S1410, a reporting process S1470 may be performed. The E2 node 1020 may perform a RIC service corresponding to each event trigger definition of the RAN function corresponding to each RAN function ID. For example, in the reporting process S1470, the E2 node 1020 may send a RIC indication message corresponding to each event trigger definition to the near-RT RIC 1010.

[0129] For example, the message structure of the RIC subscription request message is shown in the following table.

[0130] [Table 6]

[0131]

[0132] For example, the message structure of the RIC subscription response message is shown in the following table.

[0133] [Table 7]

[0134]

[0135] The section numbers in Tables 1 to 7 above may refer to the O-RAN Near Real-Time RAN Intelligent Controller, E2 Application Protocol (E2AP) standard (eg, version 2.02).

[0136] In the above embodiment, an example of a method for optimizing the transmission of the E2 subscription request message so that multiple RAN functions and multiple event trigger definitions can be sent to the E2 subscription request message is described, but the embodiments of the present disclosure are not limited thereto. In order to support multiple RAN function IDs and / or multiple RIC event trigger definitions, other messages (e.g., RIC control request messages) may be used.

[0137] In an embodiment of the present disclosure, a method performed by an E2 node may include receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The method may include sending a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0138] According to an embodiment, the RAN function list IE may include a RAN identifier (ID) corresponding to each RAN function, and information on one or more event trigger definition IEs corresponding to each RAN function.

[0139] According to an embodiment, information about one or more event trigger definition IEs corresponding to each RAN function may be configured in a list format. Information about one or more event trigger definition IEs may be associated with one RAN function identifier (ID).

[0140] According to an embodiment, the RIC subscription response message may include a permission list including at least one RAN function permitted by the E2 node among the one or more RAN functions.

[0141] In an embodiment of the present disclosure, it may include receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The method may include sending a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0142] In an embodiment of the present disclosure, a method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) may include sending a RIC subscription request message to an E2 node. The method may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0143] According to an embodiment, the RAN function list IE may include a RAN identifier (ID) corresponding to each RAN function, and information on one or more event trigger definition IEs corresponding to each RAN function.

[0144] According to an embodiment, information about one or more event trigger definition IEs corresponding to each RAN function may be configured in a list format. Information about one or more event trigger definition IEs may be associated with one RAN function identifier (ID).

[0145] According to an embodiment, the RIC subscription response message may include a permission list including at least one RAN function permitted by the E2 node among the one or more RAN functions.

[0146] In an embodiment of the present disclosure, a method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) may include sending a RIC subscription request message to an E2 node. It may include receiving a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0147] In an embodiment of the present disclosure, an apparatus executed by an 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 receive a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to send a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0148] According to an embodiment, the RAN function list IE may include a RAN identifier (ID) corresponding to each RAN function, and information on one or more event trigger definition IEs corresponding to each RAN function.

[0149] According to an embodiment, information about one or more event trigger definition IEs corresponding to each RAN function may be configured in a list format. Information about one or more event trigger definition IEs may be associated with one RAN function identifier (ID).

[0150] According to an embodiment, the RIC subscription response message may include a permission list including at least one RAN function permitted by the E2 node among the one or more RAN functions.

[0151] In an embodiment of the present disclosure, an apparatus executed by an 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 receive a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC). The at least one processor may be configured to send a RIC subscription response message to the near RT RIC. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0152] In an embodiment of the present disclosure, an apparatus executed by a near real-time (near 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 send a RIC subscription request message to an E2 node. The at least one processor may be configured to receive a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions.

[0153] According to an embodiment, the RAN function list IE may include a RAN identifier (ID) corresponding to each RAN function, and information on one or more event trigger definition IEs corresponding to each RAN function.

[0154] According to an embodiment, information about one or more event trigger definition IEs corresponding to each RAN function may be configured in a list format. Information about one or more event trigger definition IEs may be associated with one RAN function identifier (ID).

[0155] According to an embodiment, the RIC subscription response message may include a permission list including at least one RAN function permitted by the E2 node among the one or more RAN functions.

[0156] In an embodiment of the present disclosure, an apparatus executed by a near real-time (near 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 send a RIC subscription request message to an E2 node. The at least one processor may be configured to receive a RIC subscription response message from the E2 node. The RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0157] In an embodiment of the present disclosure, a non-transitory storage medium is provided. The non-transitory storage medium may include a memory storing instructions. The instructions, when executed by at least one processor, may cause the E2 node to receive a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC), and send a RIC subscription response message to the near RT RIC. According to an embodiment, the RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions. According to an embodiment, the RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function, and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

[0158] In an embodiment of the present disclosure, a non-transitory storage medium is provided. The non-transitory storage medium may include a memory storing instructions. The instructions, when executed by at least one processor, may cause a near real-time (near RT) radio access network (RAN) intelligent controller (RIC) to send a RIC subscription request message to an E2 node and receive a RIC subscription response message from the E2 node. According to an embodiment, the RIC subscription request message may include a RAN function list information element (IE) for indicating one or more RAN functions. According to an embodiment, the RIC subscription request message may include a RAN function identifier (ID) for indicating a RAN function and an event trigger definition list including one or more event trigger definition information elements (IEs) associated with the RAN function ID.

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

[0160] In the case of being implemented as software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. 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. One or more programs include instructions that cause the electronic device to perform the method according to the embodiments described in the claims or description of the present disclosure. One or more programs 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 product. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or distributed online (e.g., downloaded or uploaded) via an application store (e.g., App Store™), or distributed directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or a relay server.

[0161] 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), an optical storage device (digital versatile disk (DVD) or other format), or a magnetic tape cartridge. Alternatively, it may be stored in a memory configured with a combination of some or all of them. In addition, multiple configuration memories may be included.

[0162] In addition, the program may 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 may 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 may also be connected to the device that performs the embodiments of the present disclosure.

[0163] 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 embodiment presented. However, the singular or plural expression is appropriately selected according to the situation presented for the convenience of explanation, and the present disclosure is not limited to the singular or plural components, and even the components expressed in the plural may be configured in the singular, or the components expressed in the singular may be configured in the plural.

[0164] According to various embodiments, one or more components or operations of the above 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 such a case, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as performed by a corresponding one of the multiple components before integration. According to various embodiments, the operations performed by a module, a program, or another component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be performed in a different order or omitted, or one or more other operations may be added.

[0165] While specific embodiments have been described in the detailed description of the present disclosure, it is of course possible that various modifications are possible without departing from the scope of the present disclosure.

Claims

1. A method performed by an E2 node, the method include: receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC); as well as Send RIC subscription response message to the nearest RT RIC, The RIC subscription request message includes a RAN function list information element (IE) for indicating one or more RAN functions.

2. The method according to claim 1, in, The RAN function list IE includes: the RAN identifier (ID) corresponding to each RAN function, and Information about one or more event trigger definition IEs corresponding to each RAN function.

3. The method according to claim 2, in, The information on the one or more event trigger definition IEs corresponding to each RAN function is configured in a list format, and Therein, information about one or more event trigger definition IEs is associated with a RAN function identifier (ID).

4. The method according to claim 1, in, The RIC subscription response message includes a permission list, where the permission list includes at least one RAN function permitted by the E2 node among the one or more RAN functions.

5. A method performed by an E2 node, the method include: receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC); and Send RIC subscription response message to the nearest RT RIC, The RIC subscription request message includes: A RAN function identifier (ID) to indicate the RAN function, and An event trigger definition list comprising one or more event trigger definition information elements (IEs) associated with a RAN function ID.

6. A method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC), the method include: Send a RIC subscription request message to the E2 node; and Receive the RIC subscription response message from the E2 node, The RIC subscription request message includes a RAN function list information element (IE) for indicating one or more RAN functions.

7. The method according to claim 6, in, The RAN function list IE includes: the RAN identifier (ID) corresponding to each RAN function, and Information about one or more event trigger definition IEs corresponding to each RAN function.

8. The method according to claim 7, in, The information on the one or more event trigger definition IEs corresponding to each RAN function is configured in a list format, and Therein, information about one or more event trigger definition IEs is associated with a RAN function identifier (ID).

9. The method according to claim 6, in, The RIC subscription response message includes a permission list, where the permission list includes at least one RAN function permitted by the E2 node among the one or more RAN functions.

10. A method performed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC), the method comprising: Sending a RIC subscription request message to the E2 node; and Receive the RIC subscription response message from the E2 node, in, The RIC subscription request message includes: a RAN function identifier (ID) to indicate the RAN function, and An event trigger definition list comprising one or more event trigger definition information elements (IEs) associated with a RAN function ID.

11. A device executed by an E2 node, the device include: at least one transceiver; and at least one processor coupled to at least one transceiver, The at least one processor is configured to execute one of methods 1 to 5.

12. An apparatus executed by a near real-time (near RT) radio access network (RAN) intelligent controller (RIC), the apparatus include: at least one transceiver; and at least one processor coupled to at least one transceiver, The at least one processor is configured to execute one of methods 6 to 10.

13. A non-transitory storage medium, include: Memory for storing instructions, Wherein, when the instructions are executed by at least one processor, the E2 node: receiving a RIC subscription request message from a near real-time (near RT) radio access network (RAN) intelligent controller (RIC); and Send RIC subscription response message to the nearest RT RIC, The RIC subscription request message includes: A RAN function identifier (ID) to indicate the RAN function, and An event trigger definition list comprising one or more event trigger definition information elements (IEs) associated with a RAN function ID.

14. A non-transitory storage medium, include: Memory for storing instructions, Wherein the instructions, when executed by at least one processor, cause a near real-time (near RT) radio access network (RAN) intelligent controller (RIC): Sending a RIC subscription request message to the E2 node; and Receive the RIC subscription response message from the E2 node, The RIC subscription request message includes: A RAN Capability List Information Element (IE) for indicating one or more RAN capabilities, and An event trigger definition list is used to indicate a RAN function identifier (ID) of a RAN function and includes one or more event trigger definition information elements (IEs) associated with the RAN function ID.

Images