WO2024219718A1 - Electronic device and method for network element load balancing - Google Patents

Abstract

According to one embodiment, a method performed by means of a server may comprise an operation of receiving, through a first service processing entity included in a first cluster, a signal for requesting a connection of a first network element (NE) from an external device for managing the first cluster and a second cluster. The method may comprise an operation of identifying, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster. The method may comprise an operation of identifying, through the first service processing entity, one NE management service entity from among the first NE management service entities and the second NE management service entities. The method may comprise an operation of identifying, through the first service processing entity, a cluster for connecting the first NE.

Description

Electronic device and method for network element load balancing

The present disclosure relates to wireless communication systems, and more particularly to electronic devices and methods for network element load balancing.

In a wireless communication system, a plurality of network elements are configured. The plurality of network elements can be managed by one or more devices. A system for efficiently managing the plurality of network elements may be required.

The above information may be provided as related art for the purpose of assisting in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

According to one embodiment, a server may include at least one processor, and a memory storing instructions. The instructions, when executed by the at least one processor, may be configured to cause the server to receive, through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The instructions, when executed by the at least one processor, may be configured to cause the server to identify, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster, based on the signal for requesting connection of the first NE. The instructions, when executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify one of the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The instructions, when executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify a cluster to which the first NE is to be connected based on the identified NE management service entity.

According to one embodiment, a method performed in a server may include an operation of receiving, through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The method may include an operation of identifying, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster based on the signal for requesting connection of the first NE. The method may include an operation of identifying, through the first service processing entity, one NE management service entity among the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The method may include an operation of identifying a cluster to which the first NE is to be connected based on the identified NE management service entity, through the first service processing entity.

According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of a server, cause the server to receive, through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to identify, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster, based on the signal for requesting connection of the first NE. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to, through the first service processing entity, identify one of the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to, through the first service processing entity, identify a cluster to which the first NE is to be connected based on the identified NE management service entity.

FIG. 1 illustrates a wireless communication system according to one embodiment.

FIG. 2 illustrates an example of a cluster for managing NEs according to one embodiment.

FIG. 3 illustrates an example of the operation of a master node and a worker node according to one embodiment.

FIG. 4 illustrates an example of the operation of a first cluster and a second cluster according to one embodiment.

FIG. 5 illustrates an example of the operation of a first cluster and a second cluster according to one embodiment.

FIG. 6 illustrates an example of signal exchange operations between a first network cell distributor (NCD) service processing entity of a first cluster and a second NCD service processing entity of a second cluster, according to one embodiment.

FIG. 7 illustrates a flow diagram of the operation of a first NCD service processing entity for selecting a configuration and fault management (CFM) to manage an NE to be added, according to one embodiment.

Figure 8 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Figure 9 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Figure 10 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Figure 11 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Figure 12 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

FIG. 13 illustrates a flowchart regarding the operation of a server according to one embodiment.

FIG. 14 illustrates an example of a functional configuration of an electronic device according to one embodiment.

The terms used in this disclosure are only used to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include the plural expression unless the context clearly indicates otherwise. The terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by a person having ordinary skill in the art described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted as having the same or similar meaning as the meaning they have in the context of the related technology, and shall not be interpreted in an ideal or excessively formal meaning unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

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

In the following description, terms referring to signals (e.g., signal, information, symbol, message, signaling, RS (reference signal), data)), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, RE (resource element), RB (resource block), BWP (bandwidth part), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to entities (e.g., node, point, server, component), terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

Also, in the present disclosure, in order to determine whether a specific condition is satisfied or fulfilled, the expression "more than" or "less than" may be used, but this is only a description for expressing an example and does not exclude the description of more than or less than. A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." Also, hereinafter, "A" to "B" mean at least one of the elements from A to (inclusive of A) and from (inclusive of B). Hereinafter, "C" and/or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.

Although this disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), extensible radio access network (xRAN), open-radio access network (O-RAN), etc.), this is merely an example for explanation. Various embodiments of this disclosure can be easily modified and applied to other communication systems as well.

FIG. 1 illustrates a wireless communication system according to one embodiment.

Referring to FIG. 1, FIG. 1 illustrates a base station (110) and a terminal (120) as some of the nodes that utilize a wireless channel in a wireless communication system. FIG. 1 illustrates only one base station, but the wireless communication system may further include other base stations that are identical or similar to the base station (110).

The base station (110) is a network infrastructure that provides wireless access to the terminal (120). The base station (110) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (110) may be referred to as an 'access point (AP)', 'eNodeB (eNB)', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission/reception point (TRP)' or other terms having equivalent technical meanings.

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

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

According to one embodiment, the base station (120) of FIG. 1 may configure at least one cell. Conventionally, in a communication system with a relatively large cell radius of a base station, each base station was installed such that each base station included the functions of a digital processing unit (or a distributed unit (DU)) and a radio frequency (RF) processing unit (or a radio unit (RU)). However, as a high frequency band is used in 4G ( ^4th generation) and/or subsequent communication systems (e.g., 5G) and the cell coverage of the base station becomes smaller, the number of base stations for covering a specific area has increased. The installation cost burden of the operator for installing the base stations has also increased. In order to minimize the installation cost of the base station, a structure has been proposed in which the DU and RU of the base station are separated, one or more RUs are connected to one DU through a wired network, and one or more RUs are geographically distributed to cover a specific area. In this way, the base station (110) may be composed of one or more NEs (network elements). In addition to the DUs and RUs, depending on the protocol stack, the base station may be implemented in a distributed deployment according to a CU (centralized unit) configured to perform functions of upper layers (e.g., PDCP (packet data convergence protocol), RRC (radio resource control)) and a DU (distributed unit) configured to perform functions of lower layers. For example, an NE constituting the base station may include a CU (centralized unit), a DU (distributed unit), and/or a RU (radio unit). For example, a CU (centralized unit) may be connected to one or more DUs and may be responsible for functions of a higher layer than the DU. For example, the CU may be responsible for functions of RRC (radio resource control) and PDCP (packet data convergence protocol) layers, and the DU and RU may be responsible for functions of lower layers. DU can perform some functions (high PHY) of the RLC (radio link control), MAC (media access control), and PHY (physical) layers, and RU can be responsible for the remaining functions (low PHY) of the PHY layer.

In addition to the nodes constituting the access network, a functional entity for the core network may also be referred to as an NE. For example, for a 5th generation core network (5GC), one or more NEs may include a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), a user data management (UDM), a policy control function (PCF), an authentication server function (AUSF), and/or an authentication, authorization and accounting (AAA). For example, for an evolved packet core network (EPC), one or more NEs may include a mobility management entity (MME), a serving-gateway (S-GW), a packet-gateway (P-GW), a policy charging rules function (PCRF), and/or a home subscriber server (HSS).

In this disclosure, a system for managing NEs may be described. In the embodiments described below, NEs may include at least one of the entities described above. In order to manage the NEs, a data center (DC) may be used. The data center may be a collection of hardware and/or software required to operate and manage a cluster. Hereinafter, in FIG. 2, a system including one or more clusters will be described.

In one embodiment, a data center may include a plurality of servers. The data center may be composed of one or more clusters. A cluster is a set of nodes required to deploy and manage containers. A node represents a physical server or virtual server that constitutes a cluster. A pod represents a set of containers running in a cluster. A service represents a logical unit that exposes a pod in a cluster and is accessible from the outside (e.g., NE). A cluster may be composed of one or more master nodes and one or more worker nodes. In the cluster, a master node may manage the cluster, deploy containers, and monitor the status of the containers. A worker node in the cluster may be configured to run the containers. In FIG. 2, an example of one cluster may be described.

FIG. 2 illustrates an example of a cluster for managing NEs according to an embodiment. In the present disclosure, the description of NEs may refer to examples of access network entities (e.g., CU, DU, RU), core network entities (e.g., UPF, AMF, SMF, MME) described above.

Referring to FIG. 2, a system (200) for managing NEs may include an operations support systems (OSS) (230), a cluster (210), and a plurality of NEs (220).

According to one embodiment, the OSS (230) may be a device (or operator) for managing a cluster (210) and a plurality of NEs (220). The OSS (230) may query (or inquire) a service related to an NE. The OSS (230) may control (or manage) a service related to an NE based on querying the service related to the NE. For example, the OSS (230) may request information related to an NE from the cluster (210). Based on the request, the OSS (230) may receive (or obtain) information related to the NE from the cluster (210).

According to one embodiment, the plurality of NEs (220) may include a central unit (CU), a distributed unit (DU), and/or a radio unit (RU). The plurality of NEs (220) may be used to perform a communication service.

According to one embodiment, the cluster (210) may include a master node (250), at least one worker node (260), and a storage entity (280). For example, at least one of the components included in the cluster (210) (e.g., the master node (250), at least one worker node (260), and the storage entity (280)) may each be configured as one electronic device (or server) or may be configured based on a virtualized electronic device (or virtual machine (VM)). As an example, a pod may mean the smallest deployable computing unit. As an example, a container may share an operating system between applications. A container may include its own file system, CPU usage, memory, and process space. According to an embodiment, a container may be configured as one electronic device (or server).

For example, a master node (250) may be used to control a cluster (210). As an example, the master node (250) may include a storage entity, a scheduler, a controller manager, and an API (application programming interface) server. For example, the master node (250) may manage at least one worker node (260) and pods included in the cluster (210).

For example, at least one worker node (260) may include worker node (260-1), worker node (260-2), and worker node (260-3). As an example, each of the at least one worker node (260) may include at least one service processing entity. Worker node (260-1) may include service processing entity (271), service processing entity (272), and service processing entity (273).

For example, each of the at least one worker node (260) may host a pod, which is a component of an application. For example, a service processing entity (e.g., service processing entity (271), service processing entity (272), and service processing entity (273)) may be composed of one or more pods (or one or more containers). As an example, a service processing entity may be composed of one or more electronic devices (or servers). As an example, a service processing entity may be composed of a virtualized electronic device.

For example, a service processing entity can be used to process a service regarding NE. The service processing entity can be used to process a service regarding FCAPS (fault, configuration, account, performance, security). FCAPS represents a communication management framework for network management. For example, fault management represents detecting, diagnosing, and recovering network failures. For example, configuration management represents managing and changing the configuration of network equipment. For example, account management represents recording and analyzing the usage of network resources. For example, performance management represents monitoring and analyzing the performance of the network to prevent performance degradation. For example, security management represents protecting the network and preventing acts that violate network security. FCAPS can provide basic functions for network management. At least one function of FCAPS can be provided as a service.

For example, a storage entity (280) may be used to store at least one of information about a plurality of NEs (220), configuration information, and/or security information.

According to one embodiment, nodes constituting a managed base station may be defined as a radio unit (RU), a digital unit (DU), a central unit (CU)-control plane (CU-CP), a user plane (CU-UP), and a Near-RT (real time) radio access network intelligent controller (RIC).

FIG. 3 illustrates an example of the operation of a master node and a worker node according to an embodiment. In the present disclosure, the description of NEs may refer to examples of the above-described access network entities (e.g., CU, DU, RU), core network entities (e.g., UPF, AMF, SMF, MME). The master node (250) and the worker node (260-1) illustrated in FIG. 3 may correspond to the master node (250) and the worker node (260-1) of FIG. 2.

Referring to FIG. 3, the master node (250) may include a controller manager (251), a scheduler (252), a storage entity (253), and/or an API server (254).

For example, the controller manager (251) can be used to manage the cluster (210). The controller manager (251) can operate to maintain the declared state of the cluster (210). For example, in the OSS (230), the state of the cluster (210) can be declared. For example, the controller manager (251) can request the creation and change of resources and/or objects to the API server (254) based on the state of the cluster (250).

For example, the scheduler (252) may be used to select a worker node (e.g., worker node (260-1)) on which to execute a pod on at least one worker node (260). The scheduler (252) may be used to identify a worker node on which to deploy a pod. For example, the scheduler (252) may be used to identify a worker node on which a newly created pod and/or an unreserved pod will execute. The resources required for the pods may be different from each other. Accordingly, the scheduler (252) may identify a worker node based on information about the resources required by the pod. If there is no suitable worker node for the pod, the scheduler (252) may keep the pod in an unscheduled state until the pod can be placed on a worker node.

For example, the storage entity (253) may be used to store state values of components of the cluster (210). As an example, the storage entity (253) may store information for recovering a failure when a failure occurs in some of the components of the cluster (210). According to an embodiment, the storage entity (253) may store data based on distributed storage. The storage entity (253) may be designed to store data in different locations.

For example, the API server (254) can be used to receive or transmit information via the cluster (210). The API server (254) can receive a request to use an API for the cluster (210) and identify the validity of the received request.

According to one embodiment, a worker node (260-1) may include an agent (311), a proxy (312), and one or more pods (313).

For example, the agent (311) can be used to communicate with the API server (254) of the master node (250). The agent (311) can perform creation and/or deletion of pods instructed by the master node (250) (or scheduler (252)).

For example, a proxy (312) can be used to manage network operations. The proxy (312) can configure iptables rules.

For example, each of one or more pods (313) may be configured to include one or more containers. As an example, a container included in a pod may be configured to package a service that includes an application.

In the following specification, an example of a system for managing multiple NEs using multiple clusters will be described. For example, the multiple clusters may include a first cluster and a second cluster. As an example, both the first cluster and the second cluster may operate in an active mode. When the first cluster and the second cluster operate in the active mode, the system may operate in an active-active mode.

In one embodiment, containers can provide the flexibility to run cloud-native applications on physical infrastructure and/or virtual infrastructure. For example, containers can package services that include applications. Containers can be used to provide services that can be used in a variety of computing environments, for development/testing and/or production. For example, when containers are used, application instances can be rapidly scaled based on sudden spikes in demand. For example, containers can utilize the resources of the host operating system (OS). Since containers utilize the resources of the host OS, they can be less complex than when virtual machines are used. When containers are used, the underlying server infrastructure can be utilized efficiently.

In one embodiment, an application and/or service may be deployed. The application and/or service may be provided based on a cluster for one configuration (e.g., cluster (210) of FIG. 2). The cluster may operate based on various configurations. Each cluster according to various configurations may operate as an active site.

In one embodiment, it may be efficient for each cluster to operate as an independent, stateless cluster with independent data.

On the other hand, in a container-based cluster, data can be state-dependent. For example, a container-based cluster can be stateful. For example, in the absence of shared storage, each cluster can operate as an independent system with an active site. Therefore, whenever a problem occurs in the first cluster, a second cluster located at a different site may have to take over the operation and services of the first cluster that has experienced a problem.

Below, we will outline some things to consider when dealing with issues that arise in a container-based cluster.

1) Since each cluster is an independent cluster, load balancing is not performed when NE is added to one cluster.

2) Since the first cluster is overloaded and the second cluster has a low load, the number of cells in the NE may increase or decrease as the existing NE placement plan is changed.

3) The NE being moved must manually change the distribution of NEs and/or cells in each cluster. This is an overhead for the user.

For example, the operations performed on the cluster may relate to at least one of fault, configuration, accounting, performance, and/or security of the NE. The operations performed on the cluster may relate to operations on the element management system and/or the network management system.

In the following specification, an embodiment for distributing the load of a first cluster and a second cluster can be described.

FIG. 4 illustrates an example of the operation of a first cluster and a second cluster according to one embodiment.

Referring to Fig. 4, an EMS (element management system)/NMS (network management system) application can provide a state dependent container based on a micro service application. Each of the independent clusters can manage a set of NEs, such as 4G, 5G RAN, and/or core NEs.

According to one embodiment, a first cluster (411) and a second cluster (412) may be configured. Hereinafter, the first cluster (411) may be referred to as an OP (operator) cluster. The second cluster (412) may be referred to as a DR (disaster recovery) cluster. Each of the first cluster (411) and the second cluster (412) may correspond to the cluster (210) illustrated in FIG. 2.

For example, the first cluster (411) and the second cluster (412) can operate independently. For example, the OSS (230) can query (or inquire) only the services related to the NEs of each cluster. For example, the first cluster (411) can be set to manage a plurality of NEs (421). The second cluster (412) can be set to manage a plurality of NEs (422).

According to one embodiment, the first cluster (411) may include a master node entity (451), at least one worker node entity (461), and a storage entity (481). For example, the at least one worker node entity (461) may include worker node entity (461-1), worker node entity (461-2), and worker node entity (461-3). Each of the at least one worker node entity (461) may include one or more service processing entities. As an example, the worker node entity (461-1) may include one or more service processing entities.

In one embodiment, the second cluster (412) may include a master node entity (452), at least one worker node entity (462), and a storage entity (482). For example, the at least one worker node entity (462) may include worker node entity (462-1), worker node entity (462-2), and worker node entity (462-3). Each of the at least one worker node entity (462) may include one or more service processing entities. As an example, the worker node entity (462-1) may include one or more service processing entities. The service processing entities may be configured based on at least one pod (or container).

According to one embodiment, the first cluster (411) may be configured to manage a plurality of NEs (421). The second cluster (412) may be configured to manage a plurality of NEs (422). Each of the plurality of NEs (421) and the plurality of NEs (422) may support at least one cell. For example, NE (421-1) of the plurality of NEs (421) may support two cells. NE (421-2) of the plurality of NEs (421) may support four cells.

According to one embodiment, when the first cluster (411) and the second cluster (412) perform load balancing based on the number of NEs connected to each cluster, since the number of cells supported per NE is different from each other, an imbalance in network resources may occur. For example, depending on the number of cells, data handling and/or resources (e.g., central processing unit (CPU), memory, network) may be used more. When new NEs (423) are added to the first cluster (411), the load with the second cluster (412) may not be balanced. For example, the load of the first cluster (411) and the load of the second cluster (412) may be balanced. For example, the number of the plurality of NEs (421) and the number of the plurality of NEs (422) may be the same or similar. In a state where the number of multiple NEs (421) and the number of multiple NEs (422) are the same or similar, new NEs (423) may be added to the first cluster (411). Depending on the addition of new NEs (423), the load of the first cluster (411) and the load of the second cluster (412) may become unbalanced.

According to one embodiment, examples of loads of the first cluster (411) and the second cluster (412) may be configured as shown in the table below.

Referring to Table 1, in Case 1, the number of NEs in the first cluster (411) is 1, and the number of cells is 1. The number of NEs in the second cluster (412) is 1, and the number of cells is 1. In this case, since the numbers of cells are the same, the loads of the first cluster (411) and the second cluster (412) can be balanced. In Case 2, the number of NEs in the first cluster (411) is 2, and the number of cells is 64. The number of NEs in the second cluster (412) is 2, and the number of cells is 2. In this case, since the numbers of cells differ by more than a specified range, the loads of the first cluster (411) and the second cluster (412) can be unbalanced. In Case 3, the number of NEs of the first cluster (411) is 1000, and the number of cells is 2,300. The number of NEs of the second cluster (412) is 100, and the number of cells is 100. In this case, since the number of cells differs by more than a specified range, the loads of the first cluster (411) and the second cluster (412) may become unbalanced. In Case 4, the number of NEs of the first cluster (411) is 100, and the number of cells is 40,000. The number of NEs of the second cluster (412) is 1000, and the number of cells is 1000. In this case, since the number of cells differs by more than a specified range, the loads of the first cluster (411) and the second cluster (412) may become unbalanced.

As described above, even when the NEs of the first cluster (411) and the second cluster (412) increase equally, the number of cells of the first cluster (411) and the number of cells of the second cluster (412) may be different. As in cases 2 to 4 of Table 1, the balance of the NE level is maintained, but the balance of the cell level may not be maintained. Depending on the imbalance, in the first cluster (511) and the second cluster (512), more or less resource usage, network, and other external components may be required for balance.

In the following specification, embodiments for maintaining cell level balance between clusters will be described.

FIG. 5 illustrates an example of the operation of a first cluster and a second cluster according to one embodiment.

Referring to Figure 5, an EMS (element management system)/NMS (network management system) application can provide a state dependent container based on a micro service application together with a NCD (network cell distributor) service running on independent clusters.

In one embodiment, each cluster (e.g., the first cluster (511) and the second cluster (512)) operates to perform its own services and can provide requests for tasks of its own managing NEs.

In one embodiment, an NE may be added to one of the first cluster (511) and the second cluster (512). For example, based on the number of cells of the NE being added, the NE may be added so that the first cluster (511) and the second cluster (512) balance the load. For example, the NE cell may have a high weight. For example, one NE may have from one to N cells. N may be set to 64 or more based on the support of the NE.

In one embodiment, the balance of NE can be determined by using the weights of the number of actual cells and the number of planned cells. Based on the balance of NE, whether to move NE to another cluster (or another server, another site) can be identified (or determined).

According to one embodiment, each of the first cluster (511) and the second cluster (512) may include a network cell distributor (NCD) service processing entity (e.g., the first NCD service processing entity (591) and the second NCD service processing entity (592)). The NCD service processing entities (e.g., the first NCD service processing entity (591) and the second NCD service processing entity (592)) may perform load balancing based on weights of NEs and cells added to the server or cluster. For example, the weights may be determined according to the network architecture.

In one embodiment, weights may be applied to NEs and Cells. The weights may be changed based on the number of NEs (NEC), the actual cell count (ACC), and the planned cell count (PCC).

For example, ACC can be the number of cells added while NE is being generated. PCC can be the maximum number of cells resulting from the addition of cells, including ACC. PCC can be greater than or equal to ACC.

One NE can support many cells, but depending on the embodiment, only a small number of cells may be used (or configured). Therefore, the system (e.g., the first NCD service processing entity (591), the second NCD service processing entity (592)) can support the number of cells actually operated through the ACC. The PCC can indicate the number to be added in the future or on demand. Based on the ACC, the PCC, and the NEC, a balancing scheme at the cluster (or site) level and a balancing scheme at the intra-cluster level can be supported.

Referring to FIG. 5, the first NCD service processing entity (591) can maintain a balance between the number of NEs (or cells) in the first cluster (511) and the number of NEs (or cells) in the second cluster (512).

For example, based on the first NCD service processing entity (591) receiving an additional request for NE (523) from OSS (230), the first NCD service processing entity (591) can identify the number of NEs (or cells) in the first cluster (511) and the number of NEs (or cells) in the second cluster (512).

The first NCD service processing entity (591) can identify the cluster to which the NE (523) is to be added as the first cluster (511) based on the number of NEs (or cells) in the first cluster (511) and the number of NEs (or cells) in the second cluster (512). The first NCD service processing entity (591) can add the NE (523) to the first cluster (511).

According to an embodiment, the first NCD service processing entity (591) may identify that an imbalance occurs between the number of NEs (or cells) in the first cluster (511) and the number of NEs (or cells) in the second cluster (512). Based on the imbalance between the number of NEs (or cells) in the first cluster (511) and the number of NEs (or cells) in the second cluster (512), the first NCD service processing entity (591) may transmit a request signal to the second NCD service processing entity (592) of the second cluster (512) to connect the NE (523) to the second cluster (512). The second NCD service processing entity (592) may connect the NE (523) to the second cluster (512) based on a request signal received from the first NCD service processing entity (591). Based on the NE (523) being connected to the second cluster (512), the connection between the NE (523) and the first cluster (511) may be released.

The signal exchange operation between the first NCD service processing entity (591) and the second NCD service processing entity (592) will be described in FIG. 6.

FIG. 6 illustrates an example of signal exchange operations between a first network cell distributor (NCD) service processing entity of a first cluster and a second NCD service processing entity of a second cluster, according to one embodiment.

Referring to FIG. 6, in operation 601, the OSS (230) may transmit a signal for an NE addition request to the first NCD service processing entity (591). The first NCD service processing entity (591) may receive the signal for the NE addition request from the OSS (230). The signal for the NE addition request may include information about the number of one or more NEs to be added and information about the number of one or more cells of the one or more NEs to be added.

In operation 602, the first NCD service processing entity (591) can transmit a signal to the second NCD service processing entity (592) to request the number of NEs and the number of cells for the second cluster (512). The second NCD service processing entity (592) can receive the signal to request the number of NEs and the number of cells for the second cluster (512) from the first NCD service processing entity (591). For example, the second NCD service processing entity (592) can identify the number of NEs connected to the second cluster (512). The second NCD service processing entity (592) can identify the number of all cells for the NEs connected to the second cluster (512).

In operation 603, the second NCD service processing entity (592) can transmit a signal to the first NCD service processing entity (591) for responding with the number of NEs and the number of cells regarding the second cluster (512). The first NCD service processing entity (591) can receive a signal from the second NCD service processing entity (592) for requesting the number of NEs and the number of cells regarding the second cluster (512).

In operation 604, the first NCD service processing entity (591) can identify the number of NEs and the number of cells for the first cluster (511). For example, the first NCD service processing entity (591) can identify the number of NEs connected to the first cluster (511). The first NCD service processing entity (591) can identify the number of all cells for the NEs connected to the first cluster (511).

In operation 605, the first NCD service processing entity (591) can perform a load balancing process. The first NCD service processing entity (591) can perform the load balancing process based on information about the number of one or more NEs to be added and information about the number of one or more cells of the one or more NEs to be added. The first NCD service processing entity (591) can identify a cluster to which one or more NEs are to be added as one of the first cluster (511) and the second cluster (512) based on the load balancing process.

For example, if the cluster to which one or more NEs are to be added is identified as the first cluster (511), operation 606 may be performed. For example, if the cluster to which one or more NEs are to be added is identified as the first cluster (511), operation 607 may be performed.

In operation 606, based on the cluster to which one or more NEs are to be added being identified as the first cluster (511), the first NCD service processing entity (591) may add one or more NEs to the first cluster (511). For example, the first NCD service processing entity (591) may perform a process for adding one or more NEs to the first cluster (511).

In operation 607, based on the cluster to which one or more NEs are to be added being identified as the second cluster (512), the second NCD service processing entity (5921) can add one or more NEs to the second cluster (512). Based on the first NCD service processing entity (591) and the second NCD service processing entity (592) performing operations 607-1 and 607-2, the second NCD service processing entity (5921) can add one or more NEs to the second cluster (512).

In operation 607-1, the first NCD service processing entity (591) can transmit a signal for an NE addition request to the second NCD service processing entity (592). The second NCD service processing entity (592) can receive the signal for the NE addition request from the first NCD service processing entity (591).

In operation 607-2, the second NCD service processing entity (592) can transmit a signal for a response to the NE addition to the first NCD service processing entity (591). The first NCD service processing entity (591) can receive a signal for a response to the NE addition from the second NCD service processing entity (591). The second NCD service processing entity (592) can perform a process for adding one or more NEs to the second cluster (512) based on the signal for the NE addition response.

FIG. 7 illustrates a flow diagram of the operation of a first NCD service processing entity for selecting a configuration and fault management (CFM) to manage an NE to be added, according to one embodiment.

Referring to FIG. 7, operations 701 to 706 may be described as examples of operations for adding an NE to one of one or more configuration and fault management (CFM) service processing entities (or CFM servers) for managing the NE by the first NCD service processing entity (591). For example, one of the one or more CFM service processing entities included in the first cluster (511) may be used to manage some of the plurality of NEs for the first cluster (511) (or the plurality of NEs for the first cluster (511)). One of the one or more CFM service processing entities included in the second cluster (512) may be used to manage some of the plurality of NEs for the second cluster (512) (or the plurality of NEs for the second cluster (512)).

For example, operations 701 to 706 may be related to operation 605 of FIG. 6. The first NCD service processing entity (591) may identify the number of NEs and the number of cells for the first cluster (511), and may identify the number of NEs and the number of cells for the second cluster (512). The first NCD service processing entity (591) may identify one of the one or more CFM service processing entities included in the first cluster (511) and the second cluster (512) to which to add the NE, based on the identified information. Hereinafter, for convenience of explanation, an example in which the weight of the PCC and the weight of the NEC are set to be the same may be described. The weight of the PCC and the weight of the NEC may be changed by a system user. For convenience of explanation, the CFM service processing entity may be referred to as CFM hereinafter.

In operation 701, the first NCD service processing entity (591) may identify a list of CFMs to which the NE can be added. For example, the first NCD service processing entity (591) may manage a list of CFMs to which the NE can be added. The first NCD service processing entity (591) may identify one or more CFMs to which the NE can be added based on the list. For example, the first NCD service processing entity (591) may output an error message based on identifying that the list of CFMs to which the NE can be added is empty. The first NCD service processing entity (591) may wait without adding the NE based on identifying that the list of CFMs to which the NE can be added is empty.

In operation 702, the first NCD service processing entity (591) may identify a first CFM having a lowest PCC set among one or more CFMs. For example, an ACC, a PCC, and an NEC may be set in each of the one or more CFMs. The first NCD service processing entity (591) may identify the first CFM having the lowest PCC set to identify a CFM to which to add an NE. For example, in each of the CFMs, a maximum value of the PCC (e.g., 20000) and a maximum value of the NEC (e.g., 1000) may be set. Each of the CFMs may manage the NEs within the maximum value of the PCC (e.g., 20000) and the maximum value of the NEC (e.g., 1000).

In operation 703, the first NCD service processing entity (591) may identify whether the PCC of the first CFM due to the addition of the NE exceeds the maximum value of the PCC.

At operation 704, if the PCC of the first CFM exceeds the maximum value of PCC, the first NCD service processing entity (591) may remove the first CFM from the list of CFMs to which the NE can be added. The first NCD service processing entity (591) may remove the first CFM from the list of CFMs to which the NE can be added based on identifying that the PCC of the first CFM exceeds the maximum value of PCC. Although not illustrated, the first NCD service processing entity (591) may re-perform operation 701 to add the NE to the CFM based on removing the first CFM from the list of CFMs to which the NE can be added.

In operation 705, if the PCC of the first CFM does not exceed the maximum value of the PCC, the first NCD service processing entity (591) may identify whether the NEC of the first CFM resulting from the addition of the NE exceeds the maximum value of the NEC. The first NCD service processing entity (591) may identify whether the NEC of the first CFM resulting from the addition of the NE exceeds the maximum value of the NEC based on identifying that the PCC of the first CFM does not exceed the maximum value of the PCC.

In one embodiment, if the NEC of the first CFM exceeds the maximum value of the NEC, the first cluster (511) may perform operation 704. For example, the first NCD service processing entity (591) may remove the first CFM from the list of CFMs to which the NE can be added, based on the NEC of the first CFM exceeding the maximum value of the NEC. Although not illustrated, the first NCD service processing entity (591) may re-perform operation 701 to add the NE to the CFM, based on the removal of the first CFM from the list of CFMs to which the NE can be added.

In operation 706, if the NEC of the first CFM does not exceed the maximum value of the NEC, the first NCD service processing entity (591) may add an NE to the first CFM. The first NCD service processing entity (591) may add an NE to the first CFM based on identifying that the NEC of the first CFM does not exceed the maximum value of the NEC.

Specific examples for adding NE to CFM based on the above-described operations 701 to 706 will be described in FIGS. 8 to 12 below.

Figure 8 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Referring to FIG. 8, an NCD service processing entity (e.g., the first NCD service processing entity (591)) may determine (or allocate) a PCC per CFM. For example, if the PCC is set identically in one or more CFMs, the CFM to which a new NE is added may be randomly selected. If the PCC is not set identically in one or more CFMs, the CFM to which a new NE is added may be selected based on the PCC. As an example, the ACC may always be less than or equal to the PCC.

Information (810) represents information about the NE being added. Two NEs may be added to the system. For example, a first NE and a second NE may be added. The name of the first NE may be DU_1. The number of cells planned (or supported) in the first NE may be 15. The name of the second NE may be DU_2. The number of cells planned (or supported) in the second NE may be 10.

Information (821), information (822), and information (823) represent NEC, PCC, and ACC of multiple CFMs that are changed according to the addition of the first NE and the second NE. According to information (821), the NEC, PCC, and ACC of CFM#0, CFM#1, and CFM#2 may all be 0. Since the PCCs of CFM#0, CFM#1, and CFM#2 are all equal to 0, the CFM to which the NE is added may be randomly selected. The CFM to which the new NE is added may be CFM#0.

Information (822) indicates the NEC, PCC, and ACC of multiple CFMs after the first NE is added to CFM#0. As the first NE, of which 15 cells are planned (or supported), is added, the NEC of CFM#0 may be changed to 1 and the PCC may be changed to 15. The actual number of cells of the first NE may be 2. For example, the ACC of CFM#0 may be changed to 2.

According to information (822), the NEC, PCC, and ACC of CFM#1 and CFM#2 may all be 0. Since the PCCs of CFM#1 and CFM#2 are all equal to 0, the CFM to which the NE is added may be randomly selected. The CFM to which the new NE is added may be CFM#2.

Information (823) indicates the NEC, PCC, and ACC of multiple CFMs after the second NE is added to CFM#2. As the second NE with 10 planned (or supported) cells is added, the NEC of CFM#3 may be changed to 1 and the PCC may be changed to 10. The actual number of cells of the second NE may be 3. For example, the ACC of CFM#0 may be changed to 3.

Information (830) represents information about the CFM and PCC managed by the NE after the first NE and the second NE are added. For example, information indicating that the first NE (ID:1) is managed by CFM#0 and that the PCC of the first NE is 15 may be included in the information (830). For example, information indicating that the second NE (ID:N) is managed by CFM#2 and that the PCC of the second NE is 10 may be included in the information (830).

Figure 9 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Referring to FIG. 9, an NCD service processing entity (e.g., the first NCD service processing entity (591)) may determine (or allocate) a PCC per CFM. If the PCC is not set identically in one or more CFMs, a CFM to which a new NE is added may be selected based on the lowest PCC. However, a CFM to which a new NE is added may be selected based on the lowest PCC only when the conditions of the maximum number of cells (e.g., 20000) and the maximum number of NEs (e.g., 1000) are satisfied. For example, an ACC may always be less than or equal to a PCC.

Information (910) represents information about the NE being added. One NE may be added to the system. For example, a first NE may be added. The name of the first NE may be DU_X. The number of cells planned (or supported) in the first NE may be 10.

Information (921) and information (922) represent the NEC, PCC, and ACC of multiple CFMs that are changed according to the addition of the first NE. The NEC, PCC, and ACC of CFM#0, CFM#1, and CFM#2 may be set as in information (921). For example, the PCC of CFM#2 may be the lowest. Accordingly, the CFM to which a new NE is added may be CFM#2.

Information (922) indicates the NEC, PCC, and ACC of multiple CFMs after the first NE is added to CFM#2. As the first NE, of which 10 cells are planned (or supported), is added, the NEC of CFM#2 may be changed to 2, and the PCC may be changed to 20. The actual number of cells of the first NE may be 5. For example, the ACC of CFM#2 may be changed to 8.

Information (930) indicates information about the CFM and PCC managed by the NE after the first NE is added. For example, information indicating that the first NE (ID: X) is managed by CFM#2 and that the PCC of the first NE is 10 may be included in the information (930).

Figure 10 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Referring to FIG. 10, an NCD service processing entity (e.g., the first NCD service processing entity (591)) can determine (or allocate) a PCC per CFM. If the PCC is the same in one or more CFMs, a CFM to which a new NE is added can be selected based on the number of NEs. However, if the conditions of the maximum number of cells (e.g., 20,000) and the maximum number of NEs (e.g., 1,000) are satisfied, if the PCC is the same in one or more CFMs, a CFM to which a new NE is added can be selected based on the number of NEs. For example, an ACC can always be less than or equal to a PCC.

Information (1010) represents information about the NE being added. One NE may be added to the system. For example, a first NE may be added. The name of the first NE may be DU_X. The number of cells planned (or supported) in the first NE may be 10.

Information (1021) and information (1022) represent NECs, PCCs, and ACCs of multiple CFMs that change according to the addition of the first NE. The NECs, PCCs, and ACCs of CFM#0, CFM#1, and CFM#2 may be set as in information (1021). For example, the PCCs of CFM#0, CFM#1, and CFM#2 may all be equal to 300. The NCD service processing entity (e.g., the first NCD service processing entity (591)) may secondarily select a CFM having the smallest number of NECs. For example, the NEC of CFM#0 may be the lowest. Even if the first NE is added to CFM#0, the conditions of the maximum number of cells (e.g., 20000) and the maximum number of NEs (e.g., 1000) may be satisfied. Therefore, the CFM to which a new NE is added may be CFM#0.

Information (1022) indicates the NEC, PCC, and ACC of multiple CFMs after the first NE is added to CFM#0. As the first NE, of which 10 cells are planned (or supported), is added, the NEC of CFM#0 may be changed to 21 and the PCC may be changed to 310. The actual number of cells of the first NE may be 5. For example, the ACC of CFM#0 may be changed to 65.

Information (1030) indicates information about the CFM and PCC managed by the NE after the first NE is added. For example, information indicating that the first NE (ID: X) is managed by CFM#0 and that the PCC of the first NE is 10 may be included in the information (1030).

Figure 11 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Referring to FIG. 11, an NCD service processing entity (e.g., the first NCD service processing entity (591)) may determine (or allocate) a PCC per CFM. If the conditions of the maximum number of cells (e.g., 20,000) and the maximum number of NEs (e.g., 1,000) are not satisfied, the NE may not be added to the CFM. For example, the sum of the existing PCCs and the newly added PCCs of the CFM should not exceed the maximum number of cells (e.g., 20,000). The sum of the existing NECs and the newly added NECs of the CFM should not exceed the maximum number of NEs (e.g., 1,000). For example, the ACC may always be less than or equal to the PCC.

Information (1110) represents information about the NE being added. One NE may be added to the system. For example, a first NE may be added. The name of the first NE may be DU_X. The number of cells planned (or supported) in the first NE may be 10.

Information (1121) and information (1122) represent the NEC, PCC, and ACC of multiple CFMs that are changed according to the addition of the first NE. The NEC, PCC, and ACC of CFM#0, CFM#1, and CFM#2 can be set as in information (1121).

For example, the PCC of CFM#1 may be the lowest. However, if a first NE is added to CFM#1, the NEC of CFM#1 may exceed the maximum number of NEs (e.g., 1000).

The NCD service processing entity (e.g., the first NCD service processing entity (591)) may secondarily select the CFM having the smallest number of NECs. For example, the NEC of CFM#0 may be the lowest. However, if the first NE is added to CFM#0, the PCC of CFM#0 may exceed the maximum number of cells (e.g., 20000).

The NCD service processing entity (e.g., the first NCD service processing entity (591)) may thirdly select the remaining CFM#2. For example, even if the first NE is added to CFM#2, the conditions of the maximum number of cells (e.g., 20,000) and the maximum number of NEs (e.g., 1,000) may be satisfied. Therefore, the CFM to which the new NE is added may be CFM#2.

Information (1122) indicates the NEC, PCC, and ACC of multiple CFMs after the first NE is added to CFM#2. As the first NE, of which 10 cells are planned (or supported), is added, the NEC of CFM#2 may be changed to 801 and the PCC may be changed to 19510. The actual number of cells of the first NE may be 5. For example, the ACC of CFM#2 may be changed to 19805.

Information (1130) indicates information about the CFM and PCC managed by the NE after the first NE is added. For example, information indicating that the first NE (ID: X) is managed by CFM#2 and that the PCC of the first NE is 10 may be included in the information (1130).

Figure 12 illustrates an example of the operation of an NCD service processing entity according to one embodiment.

Referring to FIG. 12, an NCD service processing entity (e.g., the first NCD service processing entity (591)) may determine (or allocate) a PCC per CFM. If the conditions of the maximum number of cells (e.g., 20,000) and the maximum number of NEs (e.g., 1,000) are not satisfied, the NE may not be added to the CFM. For example, the sum of the existing PCCs and the newly added PCCs of the CFM must not exceed the maximum number of cells (e.g., 20,000). The sum of the existing NECs and the newly added NECs of the CFM must not exceed the maximum number of NEs (e.g., 1,000). For example, the ACC may always be less than or equal to the PCC.

Information (1210) indicates information about the NE being added. One NE may be added to the system. For example, a first NE may be added. The name of the first NE may be DU_X. The number of cells planned (or supported) in the first NE may be 10.

Information (1221) represents the NEC, PCC, and ACC of multiple CFMs. The NEC, PCC, and ACC of CFM#0, CFM#1, and CFM#2 can be set as in information (1221).

Information (1230) indicates that the first NE was not added.

For example, if 10 PCCs are added, the PCCs of CFM#0 and CFM#1 may exceed the maximum number of cells (e.g., 20000). For example, if 1 NEC is added, the NEC of CFM#2 may exceed the maximum number of NEs (e.g., 1000). Therefore, the NCD service processing entity (e.g., the first NCD service processing entity (591)) may identify that the first NE cannot be added to all CFMs. The first NE may be ignored by all servers. The first NE may not be added to the system. The NCD service processing entity (e.g., the first NCD service processing entity (591)) may not add the first NE to the system.

FIG. 13 illustrates a flowchart regarding the operation of a server according to one embodiment.

Operations 1310 to 1340 illustrated in FIG. 13 may be performed in a server including a first service processing entity (e.g., a first NCD service processing entity (591)) illustrated in FIGS. 5 to 12. Hereinafter, for convenience of explanation, operations 1310 to 1340 will be described as being performed in the first service processing entity (e.g., a first NCD service processing entity (591)).

Referring to FIG. 13, in operation 1310, a first service processing entity (e.g., a first NCD service processing entity (591) of FIGS. 5 to 12) may receive a signal for requesting connection of a first NE from an external device (e.g., an OSS (230) of FIG. 5).

For example, an external device may be used to manage a first cluster (e.g., a first cluster (511) of FIG. 5) and a second cluster (e.g., a second cluster (512) of FIG. 5). For example, a first service processing entity may receive a signal to connect a first NE to one of the first cluster and the second cluster.

In operation 1320, the first service processing entity can identify first configuration information about first NE management service entities of the first cluster (e.g., one or more CFM service processing entities included in the first cluster of FIG. 7) and second configuration information about second NE management service entities of the second cluster (e.g., one or more CFM service processing entities included in the second cluster of FIG. 7). For example, the first service processing entity can identify the first configuration information about the first NE management service entities of the first cluster and the second configuration information about the second NE management service entities of the second cluster based on a signal for requesting connection of the first NE.

For example, the first configuration information may include information about the number of NEs connected to the first cluster and information about the number of cells for the NEs connected to the first cluster.

For example, the second configuration information may include information about the number of NEs connected to the second cluster and information about the number of cells for the NEs connected to the second cluster.

According to one embodiment, the first service processing entity may transmit a signal for requesting second configuration information to a second service processing entity (e.g., the second NCD service processing entity (592)) included in the second cluster based on a signal for requesting connection of the first NE. The first service processing entity may obtain the second configuration information from the second service processing entity based on the signal for requesting the second configuration information.

In operation 1330, the first service processing entity can identify one of the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information.

According to one embodiment, the plurality of NE management service entities may include first NE management service entities included in a first cluster and second NE management service entities included in a second cluster. The first service processing entity may identify planned cell count (PCC) information regarding the plurality of NE management service entities and NE count (NEC) information regarding the plurality of NE management service entities. The first service processing entity may identify one of the plurality of NE management service entities based on the PCC information and the NEC information.

For example, the first service processing entity may identify, based on the PCC information, a third NE management service entity having a minimum PCC among the plurality of NE management service entities. For example, an operation of identifying a third NE management service entity having a minimum PCC among the plurality of NE management service entities may correspond to operation 702 of FIG. 7.

For example, the first service processing entity may identify whether the PCC of the third NE management service entity increased based on the connection of the first NE satisfies the first condition. As an example, the first condition may include a condition that the PCC of the third NE management service entity increased based on the connection of the first NE is less than or equal to a maximum value of PCC set in the system.

For example, the first service processing entity can identify whether the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the first condition based on identifying whether the PCC of the third NE management service entity, which is increased based on the connection of the first NE, exceeds the maximum value of PCC set in the system. For example, the first service processing entity can identify the third NE management service entity as one of the plurality of NE management service entities to which the first NE is added, based on identifying whether the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the first condition.

For example, the first service processing entity may identify whether the NEC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the third condition, based on identifying that the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the second condition. The first service processing entity may identify the third NE management service entity as one of the plurality of NE management service entities to which the first NE is added, based on identifying that the NEC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the second condition.

According to an embodiment, the first service processing entity may identify, based on the third NE management service entity, that the first condition and the second condition are not satisfied. The first service processing entity may identify another NE management service entity that satisfies the first condition and the second condition among the plurality of NE management service entities. For example, the first service processing entity may repeat operations 1320 and 1330 until it identifies an NE management service entity that satisfies the first condition and the second condition.

In operation 1340, the first service processing entity may identify a cluster to connect the first NE based on an identified NE management service entity among a plurality of NE management service entities to add the first NE. For example, the first service processing entity may identify a cluster including the identified NE management service entity. The first service processing entity may identify the cluster including the identified NE management service entity as the cluster to connect the first NE.

According to one embodiment, the first service processing entity may transmit a signal for a connection request to the first NE to the second service processing entity based on identifying the cluster to which the first NE is to be connected as the second cluster.

FIG. 14 illustrates an example of a functional configuration of an electronic device according to one embodiment.

Referring to FIG. 14, the electronic device (1400) may correspond to the components (e.g., the first cluster (511), the second cluster (512), the master node, the worker node, the first NCD service processing entity (591), the second NCD service processing entity (591), the CFM service processing entity) illustrated in FIGS. 2 to 12.

According to one embodiment, the electronic device (1400) may include a transceiver (1401), a processor (1403), and a memory (1405).

The transceiver (1401) may perform functions for transmitting and receiving signals in a wired communication environment. The transceiver (1401) may include a wired interface for controlling direct connection between devices through a transmission medium (e.g., copper wire, optical fiber). For example, the transceiver (1401) may transmit an electrical signal to another device through a copper wire, or perform conversion between an electrical signal and an optical signal.

The transceiver (1401) may perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver (1401) may perform a conversion function between a baseband signal and a bit stream according to a physical layer specification of the system. For example, when transmitting data, the transceiver (1401) encodes and modulates a transmission bit stream to generate complex-valued symbols. In addition, when receiving data, the transceiver (1401) restores a reception bit stream by demodulating and decoding a baseband signal. In addition, the transceiver (1401) may include a plurality of transmission and reception paths.

The transceiver (1401) transmits and receives signals as described above. Accordingly, all or part of the transceiver (1401) may be referred to as a 'communication unit', a 'transmitter', a 'receiver' or a 'transmitter-receiver'. In addition, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the transceiver (1401).

The processor (1403) controls the overall operations of the electronic device (1400). The processor (1403) may be referred to as a control unit. For example, the processor (1403) transmits and receives signals through the transceiver (1401). In addition, the processor (1403) records and reads data in the memory (1405). In addition, the processor (1403) may perform functions of a protocol stack required by a communication standard. Although only the processor (1403) is illustrated in FIG. 14, the electronic device (1400) may include two or more processors according to another implementation example.

In the present disclosure, the operations of the processor (1403) may be executed by software, or may mean controlling hardware components such as a Field Programmable Gate Array (FPGA) or an Application-specific Integrated Circuit (ASIC). In addition, the processor (1403) may include at least one of components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The processor (1403) may include at least one module, and the term "module" includes a unit composed of hardware, software, or firmware. For example, a module may be used interchangeably with terms such as logic, a logic block, a component, or a circuit. A module may be an integrally configured component or a minimum unit or a part thereof that performs one or more functions. For example, a module may be composed of an ASIC.

The memory (1405) stores data such as basic programs, application programs, and setting information for the operation of the electronic device (1400). The memory (1405) may be referred to as a storage unit. The memory (1405) may be composed of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory. In addition, the memory (1405) provides stored data according to a request from the processor (1403).

According to one embodiment, a server may include at least one processor including a processing circuit, and a memory including one or more storage media storing instructions. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server to receive, through a first service processing entity included in a first cluster, a signal for requesting a connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server to identify, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster, based on the signal for requesting a connection of the first NE. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify one of the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify a cluster to which the first NE is to be connected based on the identified NE management service entity.

According to one embodiment, the first configuration information may include information about the number of NEs connected to the first cluster and information about the number of cells for the NEs connected to the first cluster. The second configuration information may include information about the number of NEs connected to the second cluster and information about the number of cells for the NEs connected to the second cluster.

In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to transmit a signal to a second service processing entity included in the second cluster for requesting the second configuration information based on the signal for requesting the connection of the first NE. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to obtain the second configuration information from the second service processing entity based on the signal for requesting the second configuration information.

According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to transmit a signal to the second service processing entity for a connection request to the first NE based on identifying the cluster to which the first NE is to be connected as the second cluster.

In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify planned cell count (PCC) information regarding a plurality of NE management service entities including the first NE management service entities and the second NE management service entities and NE count (NEC) information regarding the plurality of NE management service entities. The instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify one of the plurality of NE management service entities based on the PCC information and the NEC information.

According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify, based on the PCC information, a third NE management service entity among the plurality of NE management service entities, the third NE management service entity having a minimum PCC.

According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify whether the PCC of the third NE management service entity increased based on the connection of the first NE satisfies a first condition.

According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify whether the NEC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the first condition, based on which the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the second condition.

In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify the third NE management service entity as one of the plurality of NE management service entities based on identifying that an NEC of the third NE management service entity, increased based on the connection of the first NE, satisfies the second condition.

According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may be configured to cause the server, through the first service processing entity, to identify another NE management service entity among the plurality of NE management service entities that satisfies the first condition and the second condition based on identifying that the first condition and the second condition are not satisfied.

According to one embodiment, a method performed in a server may include an operation of receiving, through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The method may include an operation of identifying, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster based on the signal for requesting connection of the first NE. The method may include an operation of identifying, through the first service processing entity, one NE management service entity among the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The method may include an operation of identifying a cluster to which the first NE is to be connected based on the identified NE management service entity, through the first service processing entity.

According to one embodiment, the first configuration information may include information about the number of NEs connected to the first cluster and information about the number of cells for the NEs connected to the first cluster. The second configuration information may include information about the number of NEs connected to the second cluster and information about the number of cells for the NEs connected to the second cluster.

According to one embodiment, the method may include an operation of transmitting, through the first service processing entity, a signal for requesting the second configuration information to a second service processing entity included in the second cluster based on a signal for requesting the connection of the first NE. The method may include an operation of obtaining, through the first service processing entity, the second configuration information from the second service processing entity based on the signal for requesting the second configuration information.

According to one embodiment, the method may include an operation of transmitting a signal for a connection request to the first NE to the second service processing entity based on identifying, through the first service processing entity, the cluster to which the first NE is to be connected as the second cluster.

According to one embodiment, the method may include an operation of identifying, through the first service processing entity, planned cell count (PCC) information regarding a plurality of NE management service entities including the first NE management service entities and the second NE management service entities and NE count (NEC) information regarding the plurality of NE management service entities. The method may include an operation of identifying, through the first service processing entity, one of the plurality of NE management service entities based on the PCC information and the NEC information.

According to one embodiment, the method may include an operation of identifying, through the first service processing entity, a first NE management service entity having a minimum PCC among the plurality of NE management service entities based on the PCC information.

According to one embodiment, the method may include an operation of identifying, through the first service processing entity, whether the PCC of the third NE management service entity increased based on the connection of the first NE satisfies a first condition.

According to one embodiment, the method may include an operation of identifying, through the first service processing entity, whether the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the first condition, and identifying whether the NEC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the second condition.

According to one embodiment, the method may include identifying the third NE management service entity as one of the plurality of NE management service entities based on identifying, through the first service processing entity, that an NEC of the third NE management service entity, increased based on the connection of the first NE, satisfies the second condition.

According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of a server, cause the server to receive, through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to identify, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster, based on the signal for requesting connection of the first NE. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to, through the first service processing entity, identify one of the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information. The one or more programs may include instructions that, when executed by a processor of the server, cause the server to, through the first service processing entity, identify a cluster to which the first NE is to be connected based on the identified NE management service entity.

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.

In the case of software implementation, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions for causing the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. The one or more programs may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store ^™ ) or 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 stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

These programs (software modules, 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 disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, a magnetic cassette. Or, they may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

Additionally, the program may be stored in an attachable storage device that is accessible via a communications 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. The storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communications network may be connected to the device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for the convenience of explanation, and the present disclosure is not limited to the singular or plural components, and even if a component is expressed in the plural form, it may be composed of the singular form, or even if a component is expressed in the singular form, it may be composed of the plural form.

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

Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is of course possible to make various modifications without departing from the scope of the present disclosure.

Claims (15)

On the server, At least one processor comprising a processing circuit; and A memory comprising one or more storage media storing instructions, The above instructions, when individually or collectively executed by the at least one processor, cause the server to: Through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) is received from an external device for managing the first cluster and the second cluster, Through the first service processing entity, based on a signal for requesting connection of the first NE, first configuration information about the first NE management service entities of the first cluster and second configuration information about the second NE management service entities of the second cluster are identified, Through the first service processing entity, based on the first configuration information and the second configuration information, one of the first NE management service entities and the second NE management service entities is identified, Through the first service processing entity, a cluster for connecting the first NE is identified based on the identified NE management service entity. Server. In the first paragraph, the first setting information is: Contains information about the number of NEs connected to the first cluster and information about the number of cells for the NEs connected to the first cluster, The above second setting information is, Information about the number of NEs connected to the second cluster and information about the number of cells for the NEs connected to the second cluster. Server. In the first aspect, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Through the first service processing entity, based on a signal for requesting connection of the first NE, a signal for requesting second setting information is transmitted to the second service processing entity included in the second cluster, Further configured to obtain the second setting information from the second service processing entity based on a signal for requesting the second setting information through the first service processing entity. Server. In the third aspect, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Further configured to transmit a signal for a connection request to the first NE to the second service processing entity based on identifying the cluster for connecting the first NE as the second cluster through the first service processing entity. Server. In the first aspect, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Through the first service processing entity, planed cell count (PCC) information regarding a plurality of NE management service entities including the first NE management service entities and the second NE management service entities and NE count (NEC) information regarding the plurality of NE management service entities are identified, Through the first service processing entity, one of the plurality of NE management service entities is set to be identified based on the PCC information and the NEC information. Server. In the fifth paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Further configured to identify a third NE management service entity having a minimum PCC among the plurality of NE management service entities based on the PCC information through the first service processing entity. Server. In the sixth paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Through the first service processing entity, it is set to identify whether the PCC of the third NE management service entity increased based on the connection of the first NE satisfies the first condition. Server. In the seventh paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Through the first service processing entity, based on identifying that the PCC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the first condition, is set to identify whether the NEC of the third NE management service entity, which is increased based on the connection of the first NE, satisfies the second condition. Server. In the eighth paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Based on identifying that the NEC of the third NE management service entity, which is increased based on the connection of the first NE through the first service processing entity, satisfies the second condition, the third NE management service entity is set to be identified as one of the plurality of NE management service entities. Server. In the 9th paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the server to: Further configured to identify another NE management service entity satisfying the first condition and the second condition among the plurality of NE management service entities based on identifying that the first condition and the second condition are not satisfied through the first service processing entity. Server. In the method performed on the server, An operation of receiving a signal for requesting connection of a first network element (NE) from an external device for managing the first cluster and the second cluster through a first service processing entity included in the first cluster; An operation of identifying, through the first service processing entity, first configuration information about first NE management service entities of the first cluster and second configuration information about second NE management service entities of the second cluster based on a signal for requesting connection of the first NE; An operation of identifying one NE management service entity among the first NE management service entities and the second NE management service entities based on the first configuration information and the second configuration information through the first service processing entity; and An operation for identifying a cluster to connect the first NE, based on the identified NE management service entity, through the first service processing entity. method. In the 11th paragraph, the first setting information is: Contains information about the number of NEs connected to the first cluster and information about the number of cells for the NEs connected to the first cluster, The above second setting information is, Information about the number of NEs connected to the second cluster and information about the number of cells for the NEs connected to the second cluster. method. In Article 11, An operation of transmitting a signal for requesting the second setting information to a second service processing entity included in the second cluster based on a signal for requesting connection of the first NE through the first service processing entity; and Further comprising an operation of obtaining the second configuration information from the second service processing entity based on a signal for requesting the second configuration information through the first service processing entity. method. In Article 13, Further comprising an action of transmitting a signal for a connection request to the first NE to the second service processing entity based on identifying the cluster for connecting the first NE as the second cluster through the first service processing entity. method. In a non-transitory computer-readable storage medium storing one or more programs, the one or more programs, when executed by a processor of a server, Through a first service processing entity included in a first cluster, a signal for requesting connection of a first network element (NE) is received from an external device for managing the first cluster and the second cluster, Through the first service processing entity, based on a signal for requesting connection of the first NE, first configuration information about the first NE management service entities of the first cluster and second configuration information about the second NE management service entities of the second cluster are identified, Through the first service processing entity, based on the first configuration information and the second configuration information, one of the first NE management service entities and the second NE management service entities is identified, Including instructions causing the server to identify a cluster to which the first NE is to be connected, based on the identified NE management service entity, through the first service processing entity. Computer readable storage medium.

Images