Patent Description:
In order to satisfy wireless data traffic demands that tend to increase after <NUM> communication system commercialization, efforts to develop an enhanced <NUM> communication system or a pre-<NUM> communication system are being made. For this reason, the <NUM> communication system or pre-<NUM> communication system is called a beyond <NUM> network communication system or a post LTE system. In order to achieve a high data transfer rate, an implementation of the <NUM> communication system in an mmWave band (e.g., <NUM> or more band) in addition to the band (<NUM> or less band) used in LTE is also taken into consideration. In the <NUM> communication system, technologies, such as beamforming, massive MIMO, full dimensional MIMO (FD-MIMO), an array antenna, analog beamforming and large scale antenna technologies, are being discussed.

A base station providing mobile communication services is implemented in an integrated form in which a data processing unit (a digital unit or a distributed unit (DU)) and wireless transceiver (radio unit or remote unit (RU)) of a base station are together installed in a cell site. However, the base station implemented in the integrated form of the DU and the RU is not suitable for the needs of a mobile communication operator attempting to construct multiple cell sites according to an increase in users and traffic. Accordingly, a centralized radio access network (C-RAN) (or a cloud RAN) structure for improving such incompatibility has emerged.

The C-RAN has a structure in which the DUs are intensively disposed at one physical place and only the RU is left in a cell site that actually transmits and receives radio signals to and from a terminal. The DU and the RU may be connected through an optical cable or a coaxial cable. Furthermore, as the RU and the DU are separated from each other, an interface standard for communication between the RU and the DU becomes necessary. A standard, such as a common public radio interface (CPRI), is currently used between the RU and the DU.

Furthermore, even in the 3rd generation partnership project (3GPP), such a base station structure is being standardized. An open radio access network (O-RAN), that is, an open network standard which may be applied to a <NUM> system is researched.

An O-RAN system may refer to a network system implemented based on an O-RAN standard in which functions capable of being performed by a base station (eNB) of the existing <NUM> mobile communication system and a base station (gNB) of a <NUM> mobile communication system are logically separated and implemented. The O-RAN system may include a RAN intelligent controller (RIC) for performing various types of management including resource allocation between the base station and a core network. The RIC is an element for improving quality of service used by a user equipment (UE), and may provide optimal cellular communication to the UE through the optimization of elements and resources of the O-RAN system. The following documents describe O-RAN systems; <NPL>; "<NPL>; and <NPL>.

An RIC may include an application capable of performing various functions. The application may perform a subscription procedure of receiving data transmitted by a node of an O-RAN system in order to perform various functions. The RIC may receive data from the node through an E2 termination that refers to the termination of an E2 interface, and may provide the received data to the application.

However, as the number of nodes connected to the RIC is increased, a load of the E2 termination may be increased because the size of data traffic of the E2 termination is increased. An electronic device may implement a plurality of E2 terminations in order to reduce a load of an E2 termination.

However, as the number of E2 terminations implemented on the electronic device is increased, the number of data transmission paths between the E2 termination and the application may be increased. When the number of data transmission paths is increased, the size of data traffic of the electronic device may be increased, and a phenomenon in which the stability of data reception is reduced may occur.

The current invention is defined by the appended claims.

The electronic device and an operating method of the electronic device according to various example embodiments of the present disclosure can select an E2 termination to be connected to an application that has performed a subscription request based on the size of traffic to be generated by the application that has performed the subscription request and the size of traffic which occurs or is to occur in the E2 termination, and can connect the E2 termination and an E2 node. Accordingly, the electronic device can prevent and/or reduce overload of some E2 terminations and improve the stability of data reception by properly distributing loads of a plurality of E2 terminations.

The electronic device and an operating method of the electronic device according to various example embodiments of the present disclosure can control nodes transmitting the same data type to be connected to the same E2 termination. Accordingly, the electronic device can improve the stability of data reception by reducing the number of data transmission paths within the electronic device.

<FIG> is a diagram illustrating an example of a <NUM> NR core system according to various embodiments.

<FIG> is a diagram of the <NUM> NR core system. A core network <NUM> may have a network function including an access and mobility management function (AMF) <NUM>, a session management function (SMF) <NUM>, and a user plane function (UPF) <NUM>. The elements within the core network <NUM> may be elements implemented physically or as software, for example, including various circuitry and/or executable program instructions.

According to various embodiments of the present disclosure, the AMF <NUM> may provide a function for access and mobility management for each UE <NUM>. The AMF <NUM> may perform a registration procedure on a cellular communication network of the UE <NUM>, the mobility management (e.g., identify a location of the UE <NUM>) of the UE <NUM>, or connection management between the UE <NUM> and a cellular communication network.

According to various embodiments of the present disclosure, the SMF <NUM> may perform the establishment, modification or release of a session including a procedure for data transmission or reception between the UE <NUM> and the core network <NUM> or a session management operation including the assignment of an IP address to a UE.

According to various embodiments of the present disclosure, the UPF <NUM> may receive, through a base station <NUM>, user data transmitted by the UE <NUM>, and may transmit the received user data to an external server. The UPF <NUM> may transmit, to the UE <NUM>, user data transmitted by the external server through the base station <NUM>.

According to various embodiments of the present disclosure, the base station <NUM> (e.g., a base station (a generation Node B (gNB)) of a <NUM> mobile communication or a base station (an e-node B (eNB) of a <NUM> mobile communication) may include at least one element of a radio unit (RU) <NUM> performing a physical layer function as a logical function, a digital unit (DU) <NUM> responsible for medium access control (MAC) and radio link control (RLC) functions, a central unit-control plane (CU-CP) <NUM> and a central unit-user plane (CU-UP) <NUM> responsible for higher functions, such as radio resource control (RRC) and a packet data convergence protocol (PDCP). The elements within the base station <NUM> may be elements implemented physically or as software.

According to various embodiments of the present disclosure, the CU-CP <NUM> may be an element performing a function related to a control plane. The CU-CP <NUM> may be an element performing functions related to connection setup between the UE <NUM> and the base station <NUM> and mobility and security of the UE <NUM>.

According to various embodiments of the present disclosure, the CU-UP <NUM> may perform functions related to the data transmission and reception of a user as a function related to a user plane. The base station <NUM> may be connected to the AMF <NUM>. At least one AMF <NUM> may be implemented on the core network <NUM>.

<FIG> is a diagram illustrating an example of an open radio access network (O-RAN) system according to various embodiments.

Referring to <FIG>, O-RAN system may be a network system implemented based on an O-RAN standard in which functions capable of being performed by a base station (eNB) of the existing <NUM> mobile communication system and a base station (gNB) of a <NUM> mobile communication system are logically separated and implemented.

In the O-RAN standard, a non-real time RAN intelligent controller (NRT-RIC) <NUM>, a (near-real-time) RAN intelligent controller (RIC) <NUM>, an O-CU-CP <NUM>, an O-CU-UP <NUM>, an O-DU <NUM>, etc. are newly defined.

The O-CU-CP <NUM> may be a logical element providing a function of a control plane part of RRC and a PDCP. The O-CU-UP <NUM> may be a logical element providing a function of a user plane part of an SDAP and a PDCP. The O-CU-CP <NUM> and/or the O-CU-UP <NUM> may be implemented as an O-CU, that is, an integrated element.

According to various embodiments of the present disclosure, the O-DU <NUM> may be a logical element providing a function of RLC, MAC, a higher physical layer (high-PHY) (this is based on a <NUM>-2x fronthaul split). Although not illustrated in <FIG>, an O-RU connected to the O-DU <NUM> may be a logical element providing a lower physical layer (low-PHY) (this is based on a <NUM>-2x fronthaul split) function and RF processing (e.g., the amplification of a signal and/or the modulation of a signal).

According to various embodiments of the present disclosure, the NRT-RIC <NUM> may be a logical element that enables non-real-time control, the optimization of a RAN element and a resource, modeling training, an update, etc. The RIC <NUM> may be a logical element that enables near-real-time control and the optimization of a RAN element and a resource based on data collected from the O-DU <NUM>, the O-CU-CP <NUM>, or the O-CU-UP <NUM> through an E2 interface.

The present disclosure is not limited by the name of each described element. The present disclosure may be applied to a logical element performing the described function. Furthermore, the logical elements may be disposed physically at the same location or different locations, and functions thereof may be provided by the same physical device (e.g., a processor or a controller) or functions thereof may be provided by different physical devices. For example, one physical device may provide the function of the described at least one logical element through virtualization.

<FIG> is a diagram illustrating an example of a connection between a RIC and multiple O-CU-CPs, O-CU-UPs, and O-DUs within the O-RAN system according to various embodiments.

Referring to <FIG>, an RIC <NUM> may be connected to multiple O-CU-CPs <NUM>, O-CU-UPs <NUM>, and O-DUs <NUM>.

An interface between the RIC <NUM> and the O-DU <NUM> may be defined as an E2-DU <NUM>. An interface between the RIC <NUM> and the O-CU-CP <NUM> may be defined as an E2-CP <NUM>. An interface between the RIC <NUM> and the O-CU-UP <NUM> may be defined as an E2-UP <NUM>.

An interface between the O-CU-CP <NUM> and the O-DU <NUM> may be defined as F1. An interface between the O-CU-UP <NUM> and the O-DU <NUM> may be defined as an F1 <NUM>.

One RIC <NUM> has been illustrated in <FIG>, but an O-RAN system may be implemented to include a plurality of RICs. The plurality of RICs may be implemented as a plurality of pieces of hardware disposed at the same physical location or may be implemented through virtualization using one piece of hardware.

<FIG> is a block diagram illustrating an example configuration of an electronic device according to various embodiments.

Referring to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include a plurality of applications including a first application <NUM>, a second application <NUM> and/or a third application <NUM>, and an E2 termination <NUM> connected between the applications and nodes (e.g., a first node <NUM>, a second node <NUM> and/or a third node <NUM>).

According to various embodiments of the present disclosure, the application <NUM> may be an element which is implemented within the electronic device <NUM> and performs various functions. The application <NUM> may perform various functions based on information (e.g., information related to a UE (e.g., the UE <NUM> in <FIG>) connected to a first node <NUM>, a second node <NUM> and/or a third node <NUM>) transmitted by the first node <NUM>, the second node <NUM>, or the third node <NUM>.

The first application <NUM> may transmit, to a subscription manager (not illustrated), a subscription request for receiving data for performing a function which may be provided by the first application <NUM>. The subscription manager may receive destination node (e.g., the first node <NUM>) information included in the subscription request transmitted by the first application <NUM>, and may transmit data to the first node <NUM> through the E2 termination <NUM>. The subscription manager may transmit, to the first application <NUM>, data transmitted by the first node <NUM> through the E2 termination <NUM>. The first application <NUM> may perform various functions using data transmitted by the first node <NUM> through the E2 termination <NUM>.

The second application <NUM> may transmit, to the subscription manager (not illustrated), a subscription request for receiving data for performing a function which may be provided by the second application <NUM>. The subscription request may include information indicative of a destination node and/or information indicative of the type of data (or a service type), that is, a target of subscription. The subscription manager may receive destination node (e.g., the second node <NUM>) information included in the subscription request transmitted by the second application <NUM>, and may transmit data to the second node <NUM> through the E2 termination <NUM>. The subscription manager may transmit, to the second application <NUM>, data transmitted by the second node <NUM> through the E2 termination <NUM>. The second application <NUM> may perform various functions using data transmitted by the second node <NUM> through the E2 termination <NUM>.

The third application <NUM> may transmit, to the subscription manager (not illustrated), a subscription request for receiving data for performing a function which may be provided by the third application <NUM>. The subscription manager may receive destination node (e.g., the third node <NUM>) information included in the subscription request transmitted by the third application <NUM>, and may transmit data to the third node <NUM> through the E2 termination <NUM>. The subscription manager may transmit, to the third application <NUM>, data transmitted by the third node <NUM> through the E2 termination <NUM>. The second application <NUM> may perform various functions using data transmitted by the third node <NUM> through the E2 termination <NUM>.

According to various embodiments of the present disclosure, the E2 termination <NUM> may be an entity that performs the transmission, reception and/or processing of data through an E2 interface implemented in an open RAN system. The data may be data implemented according to a method defined in the E2 interface. The E2 termination <NUM> may process data transmitted by nodes, and may transmit the processed data to an application. The E2 termination <NUM> may transmit data to the first node <NUM>, the second node <NUM> and/or the third node <NUM>, and may transmit data, transmitted by the first node <NUM>, the second node <NUM> and/or the third node <NUM>, to respective applications (e.g., the first application <NUM>, the second application <NUM> and/or the third application <NUM>).

The first node <NUM>, the second node <NUM> and/or the third node <NUM> may, for example, be any one of the O-CU-CP <NUM>, the O-CU-UP <NUM> or the O-DU <NUM> illustrated in <FIG>.

In the electronic device <NUM>, as the number of nodes, for example, targets subscribed by an application, is increased, the amount (or traffic) of data transmitted through the E2 termination <NUM> may be increased. As traffic increases, a load of the E2 termination <NUM> may be increased. A delay time of a function performed by the first application <NUM>, the second application <NUM> and/or the third application <NUM> may be increased due to the processing time of data received through the E2 termination <NUM>.

<FIG> is a block diagram illustrating an example configuration of the electronic device according to various embodiments.

Referring to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include a plurality of applications including a first application <NUM>, a second application <NUM> and/or a third application <NUM>, and a first E2 termination <NUM>, a second E2 termination <NUM> and/or a third E2 termination <NUM> connected between the applications and nodes (e.g., a first node <NUM>, a second node <NUM>, a third node <NUM>, a fourth node <NUM>, a fifth node <NUM>, a sixth node <NUM>, a seventh node <NUM>, an eighth node <NUM> and/or a ninth node <NUM>).

In the description with reference to <FIG>, some of a description of an element redundant with that of <FIG> may not be repeated here.

The electronic device <NUM> may implement a plurality of E2 terminations for a connection with more nodes. Referring to <FIG>, the electronic device <NUM> may include the first E2 termination <NUM>, the second E2 termination <NUM> and/or the third E2 termination <NUM>.

For convenience of description, it is assumed that the first E2 termination <NUM> is connected to the first node <NUM>, the second node <NUM> and/or the third node <NUM>, the second E2 termination <NUM> is connected to the fourth node <NUM> and/or the fifth node <NUM>, and the third E2 termination <NUM> is connected to the sixth node <NUM>, the seventh node <NUM> and/or the eighth node <NUM>. Furthermore, it is assumed that the first node <NUM>, the fourth node <NUM> and/or the eighth node <NUM> transmit, to the electronic device <NUM>, data for a first function provided by the first application <NUM>, the second node <NUM>, the fifth node <NUM> and/or the sixth node <NUM> transmit, to the electronic device <NUM>, data for a second function provided by the second application <NUM>, and the third node <NUM> and/or the seventh node <NUM> transmit, to the electronic device <NUM>, data for a third function provided by the third application <NUM>.

The electronic device <NUM> may receive a subscription request for performing the first function from the first application <NUM> capable of performing the first function. The subscription request may include information indicative of a destination node (e.g., the first node <NUM>, the fourth node <NUM> and/or the eighth node <NUM>) and/or information indicative of the type of data (or a service type). The electronic device <NUM> may transmit, to the first application <NUM>, data transmitted by the first node <NUM> through the first E2 termination <NUM>, may transmit, to the first application <NUM>, data transmitted by the fourth node <NUM> through the second E2 termination <NUM>, and may transmit, to the first application <NUM>, data transmitted by the eighth node <NUM> through the third E2 termination <NUM>. The first application <NUM> may perform the first function based on the data transmitted by the first node <NUM>, the fourth node <NUM> and/or the eighth node <NUM>.

The electronic device <NUM> may receive a subscription request for performing the second function from the second application <NUM> capable of performing the second function. The subscription request may include information indicative of a destination node (e.g., the second node <NUM>, the fifth node <NUM> and/or the sixth node <NUM>) and/or information indicative of the type of data (or a service type). The electronic device <NUM> may transmit, to the second application <NUM>, data transmitted by the second node <NUM> through the first E2 termination <NUM>, may transmit, to the second application <NUM>, data transmitted by the fifth node <NUM> through the second E2 termination <NUM>, and may transmit, to the second application <NUM>, data transmitted by the sixth node <NUM> through the third E2 termination <NUM>. The second application <NUM> may perform the second function based on the data transmitted by the second node <NUM>, the fifth node <NUM> and/or the sixth node <NUM>.

The electronic device <NUM> may receive a subscription request for performing the third function from third application <NUM> capable of performing the third function. The subscription request may include information indicative of a destination node (e.g., the third node <NUM> and/or the seventh node <NUM>) and/or information indicative of the type of data (or a service type). The electronic device <NUM> may transmit, to the third application <NUM>, data transmitted by the third node <NUM> through the first E2 termination <NUM>, and may transmit, to the third application <NUM>, data transmitted by the seventh node <NUM> through the third E2 termination <NUM>. The third application <NUM> may perform the third function based on the data transmitted by the third node <NUM> and/or the seventh node <NUM>.

Referring to <FIG>, it may be seen that the number of data reception paths within the electronic device <NUM> is increased compared to the number of data reception paths in <FIG>. As the number of E2 terminations implemented on the electronic device <NUM> and the number of nodes connected to the electronic device <NUM> are increased, the number of data reception paths may be increased. When the number of data reception paths is increased, resources required to control the paths between the applications <NUM>, <NUM>, and <NUM> and the E2 terminations <NUM>, <NUM>, and <NUM> may be increased. As the resources required to control the paths are increased, the resources of the electronic device <NUM> may not be efficiently used, a data processing speed may be reduced, and the stability of data reception may be decreased.

Hereinafter, an example in which connections between an E2 termination (e.g., the first E2 termination <NUM>, the second E2 termination <NUM> and/or the third E2 termination <NUM>) and a plurality of nodes (e.g., the first node <NUM>, the second node <NUM>, the third node <NUM>, the fourth node <NUM>, the fifth node <NUM>, the sixth node <NUM>, the seventh node <NUM>, the eighth node <NUM> and/or the ninth node <NUM>) are controlled in order to improve the stability of data reception is described.

Referring to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include at least one an application (e.g., the first application <NUM> in <FIG>), a plurality of E2 terminations (e.g., the first E2 termination <NUM>, the second E2 termination <NUM>) connected between the application <NUM> and at least one node (e.g., the first node <NUM> or the second node <NUM> in <FIG>), and a traffic controller (e.g., including various processing circuitry and/or executable program instructions) <NUM>.

According to various embodiments of the present disclosure, the application <NUM> may be an element which is implemented within the electronic device <NUM> and performs various functions. The application <NUM> may perform various functions based on information transmitted by the first node <NUM> or the second node <NUM> (e.g., information related to a UE (e.g., the UE <NUM> in <FIG>) connected to the first node <NUM> and the second node <NUM>).

The first E2 termination <NUM> may identify the size of data received by the first E2 termination <NUM>, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the first E2 termination <NUM> for a designated time. The first E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>.

The second E2 termination <NUM> may identify the size of data received by the second E2 termination <NUM>, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the second E2 termination <NUM> for a designated time. The second E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>.

The traffic controller <NUM> may be an entity which receives data traffic information monitored by the plurality of E2 terminations <NUM> and <NUM> and controls the plurality of E2 terminations <NUM> and <NUM> based on the data traffic information. The traffic controller <NUM> may be an entity implemented on a processor (not illustrated) of the electronic device <NUM>, and may be an entity implemented physically or as software.

The traffic controller <NUM> may include a node connection control module (e.g., including various processing circuitry and/or executable program instructions) <NUM> controlling a connection between a plurality of nodes and an E2 termination (e.g., the first E2 termination <NUM> or the second E2 termination <NUM>), a termination control module (e.g., including various processing circuitry and/or executable program instructions) <NUM> controlling the activation or deactivation of a plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>) and/or a traffic manager (e.g., including various processing circuitry and/or executable program instructions) <NUM> controlling the node connection control module <NUM> and/or the termination control module <NUM> based on data traffic information.

The traffic manager <NUM> may receive a subscription request from the application <NUM>, and may identify information indicative of a node (e.g., the first node <NUM>) included in the subscription request transmitted by the application <NUM>. The subscription request may be an operation of requesting the electronic device <NUM> to perform a series of operations for receiving, by the application <NUM>, data requested to perform a specific function from a specific node.

The traffic manager <NUM> may select an E2 termination to be connected to the first node <NUM> among the plurality of E2 terminations based on data traffic information. The traffic manager <NUM> may identify the type of data, that is, a target of subscription, included in a subscription request from the application <NUM>, and may determine the size of traffic to be generated by the subscription of the application <NUM> based on the type of data. For example, the type of data may include a service type in which data is used and the transmission cycle of the data. For example, a service type may include information of the UE <NUM> when a connection of a UE (e.g., the UE <NUM> in <FIG>) with the first node <NUM> is detected and/or information indicative of a service that provides information related to a cell configured by the first node <NUM>. Alternatively, a service type may include information indicative of a service providing information that most uses resources provided by the first node <NUM> among a plurality of UEs connected to the first node <NUM>. The traffic manager <NUM> may determine the size of traffic to be generated by the subscription of the application <NUM> based on a transmission cycle and the size of data to be transmitted in the type of data.

The traffic manager <NUM> may select one of the plurality of E2 terminations based on data traffic information and the determined size of traffic.

The traffic manager <NUM> may identify whether traffic of the first E2 termination <NUM> increased due to the subscription of the application <NUM> exceeds maximum permission traffic of the first E2 termination <NUM> based on traffic information, and may select the first E2 termination <NUM> as an E2 termination to be used in the subscription of the application <NUM> when the increased traffic does not exceed the maximum permission traffic. When the increased traffic exceeds the maximum permission traffic, the traffic manager <NUM> may select, as an E2 termination to be used in the subscription of the application <NUM>, another E2 termination (e.g., the second E2 termination <NUM>) not the first E2 termination <NUM>. The traffic manager <NUM> may activate an additional E2 termination (e.g., the second E2 termination <NUM>) based on the identification of the absence of the E2 termination which may be used in the subscription of the application <NUM> among activated E2 terminations. The traffic manager <NUM> may control the termination control module <NUM> to activate the second E2 termination <NUM> as a part of an operation of activating the E2 termination. The termination control module <NUM> may activate the second E2 termination <NUM> based on control of the traffic manager <NUM>.

Although a subscription request from the application <NUM> is not present, the traffic manager <NUM> may receive traffic information from an activated E2 termination (e.g., the first E2 termination <NUM>) every designated cycle, and may activate another E2 termination (e.g., the second E2 termination <NUM>) based on the size of traffic of the first E2 termination <NUM> satisfying a designated condition (e.g., the size of traffic is greater than (or exceeds) maximum permission traffic).

The traffic manager <NUM> may perform a series of operations for connecting a selected E2 termination (e.g., the first E2 termination <NUM>) and a node (e.g., the first node <NUM>) included in a subscription request transmitted by the application <NUM>. The traffic manager <NUM> may control the node connection control module <NUM> to perform a connection between the first E2 termination <NUM> and the first node <NUM>. The node connection control module <NUM> may perform the connection between the first E2 termination <NUM> and the first node <NUM>.

The application <NUM> may receive data from the first node <NUM> and perform a specific function of the application <NUM> based on the data received from the first node <NUM>, as a part of a subscription procedure.

Through the aforementioned example, the electronic device <NUM> can reduce an increase in the delay time in a way that an E2 termination that will perform subscription is selected and the subscription is performed based on data traffic information, and a plurality of E2 terminations processes proper data traffic.

The traffic manager <NUM> may deactivate a specific E2 termination based on traffic information. According to an embodiment, the traffic manager <NUM> may determine to deactivate the first E2 termination <NUM> based on the size of traffic of the first E2 termination <NUM> satisfying a designated condition (e.g., the size of traffic is minimum traffic or less (less than minimum traffic)). The traffic manager <NUM> may control the termination control module <NUM> to deactivate the first E2 termination <NUM>. The traffic manager <NUM> may control the node connection control module <NUM> so that the first node <NUM> connected to the first E2 termination <NUM> is connected to another activated termination (e.g., the second E2 termination <NUM>).

The traffic controller <NUM> may improve the stability of data transmission (or reception) by reducing a data transmission (or reception) path within the electronic device <NUM>. The traffic controller <NUM> (or the traffic manager <NUM>) may identify the type of data (or a service type) transmitted through an activated E2 terminations. The type of data (or a service type) may be information indicative of an entity (e.g., the application <NUM>) that receives data or information indicative of a function which may be provided by the application <NUM>. The traffic controller <NUM> may control the node connection control module <NUM> to connect, to the same E2 termination, nodes that transmit the same data type. The traffic controller <NUM> may connect the same E2 termination and the application <NUM> that has requested data subscription. The aforementioned embodiment is described later with reference to <FIG>.

<FIG> is a diagram illustrating an example in which an electronic device activates a termination to be connected to an application that has requested subscription based on traffic of data transmitted and received through the termination according to various embodiments.

Referring to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include at least one an application (e.g., the first application <NUM> or the second application <NUM>), a plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>) connected between the application <NUM> and <NUM> and at least one node (e.g., the first node <NUM> or the second node <NUM> in <FIG>), and a traffic controller <NUM>.

According to various embodiments of the present disclosure, the application <NUM> may be an element which is implemented within the electronic device <NUM> and performs various functions. The application <NUM> may perform various functions based on information (e.g., information related to a UE (e.g., the UE <NUM> in <FIG>) connected to the first node <NUM> and the second node <NUM>) transmitted by the first node <NUM> or the second node <NUM>.

The first E2 termination <NUM> may identify the size of data received by the first E2 termination <NUM> for a designated time, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the first E2 termination <NUM> for a designated time. The first E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>. In <FIG>, it is assumed that the first application <NUM> receives data from the first node <NUM> through the first E2 termination <NUM>, for convenience of description.

The second E2 termination <NUM> may identify the size of data received by the second E2 termination <NUM> for a designated time, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the second E2 termination <NUM> for a designated time. The second E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>.

The traffic controller <NUM> may be an entity which receives data traffic information monitored by the plurality of E2 terminations <NUM> and <NUM> and controls the plurality of E2 terminations <NUM> and <NUM> based on the data traffic information. The traffic controller <NUM> is an entity implemented on a processor (not illustrated) of the electronic device <NUM>, and may be an entity implemented physically or as software. For example, the traffic controller <NUM> may include various processing circuitry and/or executable program instructions.

The traffic controller <NUM> may include a node connection control module <NUM> controlling a connection between a plurality of nodes and E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>), a termination control module <NUM> controlling the activation or deactivation of the plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>) and/or a traffic manager <NUM> controlling the node connection control module <NUM> and/or the termination control module <NUM> based on data traffic information.

The traffic manager <NUM> may receive a subscription request from the second application <NUM>, and may identify information indicative of a node (e.g., the second node <NUM>) included in the subscription request transmitted by the second application <NUM>.

The traffic manager <NUM> may select an E2 termination to be connected to the second node <NUM> among the plurality of E2 terminations based on data traffic information. The traffic manager <NUM> may identify the type of data, that is, a target of subscription included in a subscription request from the second application <NUM>, and may determine the size of traffic to be generated by the subscription of the second application <NUM> based on the type of data. The traffic manager <NUM> may select one of the plurality of E2 terminations based on the data traffic information and the determined size of traffic.

The traffic manager <NUM> may select, as an E2 termination to be used in the subscription of the second application <NUM>, another E2 termination (e.g., the second E2 termination <NUM>) not the first E2 termination <NUM> when increased traffic exceeds maximum permission traffic.

The traffic manager <NUM> may perform a series of operations for connecting a selected E2 termination (e.g., the second E2 termination <NUM>) and a node (e.g., the second node <NUM>) included in a subscription request transmitted by the second application <NUM>.

The traffic manager <NUM> may control the node connection control module <NUM> to perform the connection between the second E2 termination <NUM> and the second node <NUM>. The node connection control module <NUM> may perform the connection between the second E2 termination <NUM> and the second node <NUM>.

The second application <NUM> may receive data from the second node <NUM> and perform a specific function of the application <NUM> based on the data received from the second node <NUM>, as a part of a subscription procedure.

<FIG> is a diagram illustrating an example in which an electronic device deactivates a termination based on traffic of data transmitted and received through the termination according to various embodiments.

Referring to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include at least one application (e.g., the first application <NUM> or the second application <NUM>), a plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>) connected between the application <NUM> and <NUM> and at least one node (e.g., the first node <NUM> or the second node <NUM> in <FIG>), and a traffic controller (e.g., including various processing circuitry and/or executable program instructions) <NUM>.

According to various embodiments of the present disclosure, the application <NUM> may be an element implemented within the electronic device <NUM> and performing various functions. The application <NUM> may perform various functions based on information transmitted by the first node <NUM> or the second node <NUM> (e.g., information related to a UE (e.g., the UE <NUM> in <FIG>) connected to the first node <NUM> and the second node <NUM>).

The first E2 termination <NUM> may identify the size of data received by the first E2 termination <NUM> for a designated time, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the first E2 termination <NUM> for a designated time. The first E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>.

The second E2 termination <NUM> may identify the size of data received by the second E2 termination <NUM> for a designated time, and may generate data traffic information based on the identified size. The data traffic information may include the size of data received through the second E2 termination <NUM> for a designated time. The second E2 termination <NUM> may generate data traffic information every designated time, and may transmit the generated data traffic information to the traffic controller <NUM>. In <FIG>, it is assumed that the first application <NUM> receives data from the first node <NUM> through the first E2 termination <NUM> and the second application <NUM> receives data from the second node <NUM> through the second E2 termination <NUM>, for convenience of description.

The traffic controller <NUM> may be an entity which receives data traffic information monitored by the plurality of E2 terminations <NUM> and <NUM> and controls the plurality of E2 terminations <NUM> and <NUM> based on the data traffic information. The traffic controller <NUM> is an entity implemented on a processor (not illustrated) of the electronic device <NUM>, and may be an entity implemented physically or as software.

The traffic controller <NUM> may include a node connection control module <NUM> controlling a connection between a plurality of nodes and E2 terminations (e.g., the first E2 termination <NUM> an d the second E2 termination <NUM>), a termination control module <NUM> controlling the activation or deactivation of a plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM>) and/or a traffic manager <NUM> controlling the node connection control module <NUM> and/or the termination control module <NUM> based on data traffic information.

The traffic manager <NUM> may deactivate a specific E2 termination based on traffic information. According to an embodiment, the traffic manager <NUM> may determine to deactivate the second E2 termination <NUM> based on the size of traffic of the second E2 termination <NUM> satisfying a designated condition (e.g., the size of traffic is minimum traffic or less (less than minimum traffic)). The traffic manager <NUM> may control the termination control module <NUM> to deactivate the second E2 termination <NUM>. The traffic manager <NUM> may control the node connection control module <NUM> so that the second node <NUM> connected to the second E2 termination <NUM> is connected to another activated termination (e.g., the first E2 termination <NUM>).

<FIG> is a diagram illustrating an example in which an electronic device changes a termination to be connected to a node based on the type of data (or a service type) transmitted and received through the termination according to various embodiments.

With reference to <FIG>, an electronic device <NUM> (e.g., the RIC <NUM> in <FIG>) may include a plurality of applications including a first application <NUM>, a second application <NUM> and/or a third application <NUM>, a first E2 termination <NUM>, a second E2 termination <NUM> and/or a third E2 termination <NUM> connected between the applications and nodes (e.g., a first node <NUM>, a second node <NUM>, a third node <NUM>, a fourth node <NUM>, a fifth node <NUM>, a sixth node <NUM>, a seventh node <NUM>, an eighth node <NUM> and/or a ninth node <NUM>) and/or a traffic manager (e.g., including various processing circuitry and/or executable program instructions) <NUM>.

For convenience of description, it is assumed that the first node <NUM>, the fourth node <NUM> and/or the eighth node <NUM> transmit, to the electronic device <NUM>, data for a first function provided by the first application <NUM>, the second node <NUM>, the fifth node <NUM> and/or the sixth node <NUM> transmit, to the electronic device <NUM>, data for a second function provided by the second application <NUM>, and the third node <NUM> and/or the seventh node <NUM> transmit, to the electronic device <NUM>, data for a third function provided by the third application <NUM>.

The traffic controller <NUM> can improve the stability of data transmission (or reception) by reducing a data transmission (or reception) path within the electronic device <NUM>. The traffic controller <NUM> (or the traffic manager <NUM>) may identify the type of data (or a service type) transmitted through activated E2 terminations. The type of data (or a service type) may be information indicative of an entity (e.g., the application <NUM>) that receives data or information indicative of a function which may be provided by the application <NUM>. For example, information related to the first function performed by the first application <NUM> may refer, for example, to a first data type (or a first service type). Information related to the second function performed by the second application <NUM> may refer, for example, to a second data type (or a second service type). Information related to the third function performed by the third application <NUM> may refer, for example, to a third data type (or a third service type). In this case, the type of data transmitted by the first node <NUM>, the fourth node <NUM> and/or the eighth node <NUM> may be the first data type. The type of data transmitted by the second node <NUM>, the fifth node <NUM> and/or the sixth node <NUM> may be the second data type. The type of data transmitted by the third node <NUM> and the seventh node <NUM> may be the third data type.

The traffic controller <NUM> may control the node connection control module <NUM> to connect, to the same E2 termination, nodes that transmit the same data type.

The traffic controller <NUM> may control the node connection control module <NUM> so that nodes (e.g., the first node <NUM>, the fourth node <NUM>, and the eighth node <NUM>) that transmit the first data type are connected to the first E2 termination <NUM>, that is, the same E2 termination.

The traffic controller <NUM> may control the node connection control module <NUM> so that nodes (e.g., the second node <NUM>, the fifth node <NUM>, and the sixth node <NUM>) that transmit the second data type are connected to the second E2 termination <NUM>, that is, the same E2 termination.

The traffic controller <NUM> may control the node connection control module <NUM> so that nodes (e.g., the third node <NUM>, the seventh node <NUM>) that transmit the third data type are connected to the third E2 termination <NUM>, that is, the same E2 termination.

With reference to <FIG>, the first E2 termination <NUM> may transmit data to the first application <NUM>, and may not perform the transmission of data to other applications (e.g., the second application <NUM> and the third application <NUM>). Accordingly, a data transmission path between the first E2 termination <NUM> and the second application <NUM> and a data transmission path between the first E2 termination <NUM> and the third application <NUM> may be omitted.

With reference to <FIG>, the second E2 termination <NUM> may transmit data to the second application <NUM>, and may not perform the transmission of data to other applications (e.g., the first application <NUM> and the third application <NUM>). Accordingly, a data transmission path between the second E2 termination <NUM> and the first application <NUM> and a data transmission path between the second E2 termination <NUM> and the third application <NUM> may be omitted.

With reference to <FIG>, the third E2 termination <NUM> may transmit data to the third application <NUM>, and may not perform the transmission of data to other applications (e.g., the first application <NUM> and the second application <NUM>). Accordingly, a data transmission path between the third E2 termination <NUM> and the first application <NUM> and a data transmission path between the third E2 termination <NUM> and the second application <NUM> may be omitted.

As in the aforementioned example, the electronic device <NUM> connects, to the same E2 termination, nodes that transmit the same data type. A data transmission path within the electronic device <NUM> can be reduced compared to the embodiment of <FIG>, and the stability of data reception (or transmission) can be improved.

According to an embodiment, the electronic device <NUM> may determine an E2 node to be connected to a node based on a characteristic of data. The electronic device <NUM> may connect a node that transmits data having higher priority than other data to an E2 termination having a relatively low load. The electronic device <NUM> may connect a node that transmits data having a larger size than other data to an E2 termination having a relatively low load. The electronic device <NUM> may connect a node having a shorter transmission cycle of data than another node to an E2 termination having a relatively low load.

An electronic device according to various example embodiments of the present disclosure may include: a radio access network (RAN) intelligent controller (RIC) connected to at least one E2 node. The RIC may include: an application; a plurality of E2 terminations connected between at least one node and the application; and a traffic controller. The traffic controller may be configured to: receive a subscription request for the E2 node from the application, may select an E2 termination to be used for the application to perform subscription among the plurality of E2 terminations based on traffic information of data transmitted or received through the E2 termination, and control the application to receive data through the E2 node, through the selected E2 termination.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may be configured to: activate another E2 termination based on the identification of the amount of traffic of an E2 termination satisfying a designated condition; and connect the another E2 termination and a node.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may be configured to: deactivate an E2 termination based on the identification of the amount of traffic of the E2 termination satisfying a designated condition; and connect, to another E2 termination, a node connected to the deactivated E2 termination.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may be configured to: determine the amount of traffic to be generated by an application based on the type of data to be subscribed by the application included in a subscription request; and select an E2 termination to be connected to the application based on the determined amount of traffic.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may be configured to: identify a service type provided by at least one node; and connect, to the same E2 termination, nodes that provide the same service.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may be configured to: connect, to the same E2 termination, an application that has requested subscription corresponding to the service type.

In an electronic device according to various example embodiments of the present disclosure, the plurality of E2 terminations may be configured to periodically transmit the traffic information to the traffic controller.

In an electronic device according to various example embodiments of the present disclosure, the traffic controller may include the node connection control module configured to control a connection between the node and an E2 termination; the termination control module configured to control an operation related to the activation of the E2 termination; and the traffic manager configured to control the node connection control module and the termination control module.

In an electronic device according to various example embodiments of the present disclosure, the termination control module may be configured to: determine whether to activate or deactivate at least some of the plurality of E2 terminations based on traffic information received from the traffic manager.

In an electronic device according to various example embodiments of the present disclosure, the traffic manager may be configured to: select an E2 termination to which the application will be connected based on traffic information received from the E2 termination; and control the node connection control module to connect the selected E2 termination and a node.

<FIG> is a flowchart illustrating an example method of operating an electronic device according to various embodiments.

Referring to <FIG>, at operation <NUM>, an electronic device (e.g., the electronic device <NUM> in <FIG>) may receive a subscription request for a node (e.g., the first node <NUM> in <FIG>) from an application (e.g., the application <NUM> in <FIG>).

The subscription request may be an operation of requesting the electronic device <NUM> to perform a series of operations for receiving, by the application <NUM>, data requested to perform a specific function from a specific node.

The electronic device <NUM> may receive a subscription request from the application <NUM>, and may identify information indicative of a node (e.g., the first node <NUM>) included in the subscription request transmitted by the application <NUM>.

At operation <NUM>, the electronic device <NUM> may select one of a plurality of E2 terminations (e.g., the first E2 termination <NUM> and the second E2 termination <NUM> in <FIG>) based on traffic information.

The electronic device <NUM> may identify the type of data, that is, a target of subscription included in the subscription request of the application <NUM>, and may determine the size of traffic to be generated by the subscription of the application <NUM> based on the type of data. The electronic device <NUM> may select one of the plurality of E2 terminations based on data traffic information and the determined size of traffic.

The electronic device <NUM> may identify whether traffic of the first E2 termination <NUM> increased due to the subscription of the application <NUM> exceeds maximum permission traffic of the first E2 termination <NUM> based on traffic information, and may select the first E2 termination <NUM> as an E2 termination to be used in the subscription of the application <NUM> when the increased traffic does not exceed the maximum permission traffic. The electronic device <NUM> may select another E2 termination (e.g., the second E2 termination <NUM>) not the first E2 termination <NUM> as an E2 termination to be used in the subscription of the application <NUM> when the increased traffic exceeds the maximum permission traffic. The electronic device <NUM> may activate an additional E2 termination (e.g., the second E2 termination <NUM>) based on the identification of the absence of an E2 termination which may be used in the subscription of the application <NUM> among activated E2 terminations. The electronic device <NUM> may control the termination control module <NUM> to activate the second E2 termination <NUM> as a part of an operation of activating the E2 termination. The termination control module <NUM> may activate the second E2 termination <NUM> based on control of the traffic manager <NUM>.

At operation <NUM>, the electronic device <NUM> may receive data from a node (e.g., the first node <NUM>) using the selected E2 termination.

The electronic device <NUM> may perform a series of operations for connecting a selected E2 termination (e.g., the first E2 termination <NUM>) and a node (e.g., the first node <NUM>) included in a subscription request transmitted by the application <NUM>. The electronic device <NUM> may control the node connection control module <NUM> to perform a connection between the first E2 termination <NUM> and the first node <NUM>. The node connection control module <NUM> may perform the connection between the first E2 termination <NUM> and the first node <NUM>.

Through the aforementioned embodiment, the electronic device <NUM> selects an E2 termination that will perform subscription and performs subscription based on data traffic information, and can reduce an increase in the delay time because a plurality of E2 terminations processes proper data traffic.

A method of operating the electronic device according to various example embodiments of the present disclosure may include: receiving, by a traffic controller of a radio access network (RAN) intelligent controller (RIC), a subscription request for an E2 node from an application included in the RIC; selecting, by the traffic controller, an E2 termination to be used for the application to perform subscription among a plurality of E2 terminations based on traffic information of data transmitted or received through the E2 termination; and controlling, by the traffic controller, the application to receive data through the node, through the selected E2 termination.

A method of operating the electronic device according to various example embodiments of the present disclosure may further include: =activating another E2 termination based on the identification of the amount of traffic of the E2 termination satisfying a designated condition; and connecting the another E2 termination and the node.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: deactivating the E2 termination based on the identification of the amount of traffic of the E2 termination satisfying a designated condition; and connecting, to another E2 termination, a node connected to the deactivated E2 termination.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: determining the amount of traffic to be generated by the application based on the type of data to be subscribed by the application included in the subscription request; and selecting an E2 termination to be connected to the application based on the determined amount of traffic.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: identifying a service type provided by the at least one node; and connecting, to the same E2 termination, nodes providing the same service.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: connecting, to the same E2 termination, an application that has requested subscription corresponding to the service type.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: periodically transmitting, by the plurality of E2 terminations, the traffic information to the traffic controller.

A method of operating the electronic device according to various embodiments of the present disclosure may further include: determining whether to activate or deactivate at least some of the plurality of E2 terminations based on the traffic information.

The electronic devices may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, a home appliance, or the like.

As used herein, such terms as "the first" and "the second" or "a first" and "a second" may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term "operatively" or "communicatively", as "coupled with," "coupled to," "connected with," or "connected to" another element (e.g., a second element), the element may be coupled with the other element directly (e.g., through wires), wirelessly, or via a third element.

As used in connection with various embodiments of the disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, or any combination thereof, and may interchangeably be used with other terms, for example, "logic," "logic block," "part," or "circuitry". For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments as set forth herein may be implemented as software including one or more instructions that are stored in a storage medium that is readable by a machine. For example, a processor of the machine may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. Wherein, the "non-transitory" storage medium is a tangible device, and may not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.

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 be distributed (e.g., downloaded or uploaded) online via an application store (e.g., PlayStore™), or between two user devices (e.g., smart phones) directly.

Claim 1:
An electronic device comprising:
a radio access network, RAN, intelligent controller, RIC, (<NUM>) connected to at least one E2 node (<NUM>-<NUM>),
wherein the RIC comprises:
a plurality of applications (<NUM>, <NUM>, <NUM>);
a plurality of E2 terminations (<NUM>, <NUM>, <NUM>) connected between the at least one E2 node and at least one application of the plurality of applications; and
a traffic controller (<NUM>),
wherein the traffic controller is configured to:
receive a subscription request for the E2 node from the at least one application select an E2 termination to be used for the at least one application to perform subscription among the plurality of E2 terminations based on traffic information of data transmitted or received through the E2 termination, and
control the at least one application to receive data through the E2 node, through the selected E2 termination.