WO2017096920A1 - Cloud virtual network element control method and apparatus, and wireless network controller - Google Patents

Abstract

A cloud virtual network element control method comprises: establishing a flexible management group, the flexible management group comprising at least one service node used for managing a station resource; acquiring load information of each service node among the at least one service node in the flexible management group and a detection result of a station currently not managed by the service node; and flexibly allocating the station to the service node for management according to the load information of each service node and the detection result.

Description

Cloud virtual network element control method and device and wireless network controller Technical field

The present application relates to, but is not limited to, the field of network technologies, and in particular, to a cloud virtual network element control method and apparatus, and a wireless network controller.

Background technique

With the development of smart terminals and mobile Internet, "communication" has long since deviated from traditional voice and text messages, and people are connected with people, and even the connection between things and things has become a predictable future. In October 2012, the European Telecommunications Standards Institute (ETSI) established the NFV (Network Functions Virtualization) ISG (Industry Specification Group) organization. The organization is committed to promoting "Network Functions Virtualization."

NFV's simple understanding is to migrate telecom equipment from the current dedicated platform to the general-purpose X86COTS (Commercial-off-the-shelf, commercial off-the-shelf or technology) server. The various devices used in the current telecommunication network are deployed on a private platform. The hardware resources of the network elements cannot be used interchangeably. The hardware needs to be increased when the capacity is expanded, and the hardware is idle when the capacity is reduced. In the NFV method, various network elements are used. It has become a stand-alone application that can be flexibly deployed on a unified platform built by standard servers, storage, and switches. Such software and hardware decoupling, each application can quickly reduce and expand capacity by rapidly increasing virtual resources. The purpose is to greatly enhance the flexibility of the network.

Thus in a 3G ^(the 3 ^rd Generation, Third Generation) network, a cloud service, a conventional RNC (Radio Network Controller, the radio network controller), CN (core net, core network), the NodeB (base station) are NE In the form of VNF, the network elements such as the RNC (BSR (Base Transceiver Station)) must adapt to the requirements of the cloud environment and support the elastic scaling function.

There are many algorithms based on elastic scaling on the cloud platform, but most of the algorithms based on Internet services are based on the server's hardware resources (CPU, memory, disk I/O (input/output), network bandwidth) and network utilization. Elastic expansion, but for the telecommunications industry, traffic is more important, this information is not enough and can not directly reflect the business load.

The wireless controller network element (NodeB/BTS) and the base station, the adjacent controller, and the CN all have multiple wireless protocols and transmission protocol connections, and various protocol parameters (which may be referred to as connection protocol parameters) for connection are required. The service load of a service node (here, a virtual machine or a virtual container) is closely related to the protocol processing on the node. Once a CCP (Communication Control Port) signaling link is established on a service node. Then, many UE (terminal) measurement reports and the like using the NodeB need to be transmitted through the service node, and when different service nodes process the same number of users, compared with the service node that does not establish the CCP signaling link, the CPU (central The processor) load will be higher.

Therefore, the existing flexible scaling algorithm under the cloud platform is not suitable for the wireless network controller in the virtual environment.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

This paper provides a cloud virtual network element control method and device and a wireless network controller to overcome the defects of the elastic scaling algorithm existing in the related technology without considering the connection protocol parameters and traffic volume, and the related technology is not applicable to the cloud virtual The problem that the virtual network element implements the elastic expansion method on the wireless network controller in the environment.

The embodiment of the invention provides a cloud virtual network element control method, including:

Establishing an elastic management group, the flexible management group including at least one service node for managing site resources of the site;

Obtaining load information of each service node in the flexible management group and a detection result of a site currently not managed by the service node;

And assigning the site elasticity to the management of the service node according to the load information of each of the service nodes and the detection result.

Optionally, the dynamically assigning the site to the service node according to the load information and the detection result includes:

When the detection result is that there is no unmanaged site, according to each of the service nodes The load information determines whether there is a service node that needs to be retracted in the flexible management group;

When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether an existing service node needs to be used in the flexible management group or a new service node is popped up to Managed sites are managed.

Optionally, the load information of the service node includes at least the number of stations managed by the service node;

When the detection result is that there is no unmanaged site, determining whether there is a service node that needs to be retracted in the flexible management group according to the load information of each service node includes:

When there is a service node whose number of managed sites is smaller than the idle value of the first site, and the number of sites managed by the service node is not greater than the sum of the number of remaining manageable sites of other service nodes, The service node is retracted and the site managed by the service node is migrated to another service node for management.

Optionally, the load information of the service node further includes a resource occupancy rate of the service node;

The method further includes: before retracting the service node whose number of managed sites is smaller than the idle value of the first site, and migrating the site managed by the service node to another service node for management, the method further includes:

And determining that the resource occupancy rate of the service node that is smaller than the first station idle value is smaller than the first resource idle value, and the resource occupancy rate of the service node is not greater than other service nodes in the elastic management group. The sum of the remaining resource occupancy rates is performed by retrieving the service node and migrating the site managed by the service node to another service node for management.

Optionally, when the detection result is that there is an unmanaged site, determining, according to load information of each service node, whether an existing service node needs to be used in the elastic management group or popping up a new service node to Management of unmanaged sites includes:

When there is a service node whose number of managed sites is smaller than the first site alert value, the unmanaged site is allocated to the service node for management;

When the number of sites managed by all service nodes is not less than the first site alert value in the flexible management group, a new service node pops up in the elastic management group to manage the unmanaged site.

Optionally, the site resource includes a first type of site resource and a second type of site resource;

The elastic management group includes a first elastic management group and a second flexible management group.

In the step of dynamically assigning the site to the management of the service node according to the load information and the detection result, the service node in the first elastic management group and the service node in the second elastic management group respectively The first type of site resource and the second type of site resource of the site are managed, and the first type of site resource and the second type of site resource of the same site are configured with associated parameters.

Optionally, the load information includes at least the number of stations managed by the service nodes in the first elastic management group and the second elastic management group;

When the detection result is that there is no unmanaged site, determining whether there is a service node that needs to be retracted in the flexible management group according to the load information of each service node includes:

In the first elastic management group, there is a service node whose number of managed sites is smaller than the idle value of the second site, and the number of sites managed by the service node is not greater than the remaining of other service nodes in the first elastic management group. When the sum of the number of sites can be managed, the service node is retracted, and the site managed by the service node is migrated to other service nodes in the first elastic management group for management;

When the second elastic management group has a service node whose number of managed sites is smaller than the idle value of the third site, and the number of sites managed by the service node is not greater than the remaining of other service nodes in the second elastic management group. When the sum of the number of sites can be managed, the service node is retracted, and the site managed by the service node is migrated to other service nodes in the second elastic management group for management.

Optionally, the load information of the service node further includes a resource occupancy rate of the service node;

Before the retracting the service node whose number of sites is smaller than the idle value of the second site, and the site managed by the service node is migrated to another service node for management, the method further includes:

If the resource occupancy rate of the service node is less than the idle value of the second resource, and the resource occupancy rate of the service node is not greater than the sum of the remaining resource usage rates of other service nodes in the first elastic management group, The step of retrieving the service node and migrating the site managed by the service node to another service node in the first elastic management group for management;

The method further includes: before retracting the service node whose number of sites is smaller than the idle value of the third site, and migrating the site managed by the service node to another service node for management, the method further includes:

Determining whether the resource occupancy rate of the service node is smaller than the idle value of the third resource, and if the value is less than the idle value of the third resource, and the resource occupancy rate of the service node is not greater than other industries in the second elastic management group. And the step of relocating the service node to the other node of the second elastic management group for management.

Optionally, when the detection result is that there is an unmanaged site, determining, according to load information of each service node, whether an existing service node needs to be used in the elastic management group or a new service node is popped up. The management of the unmanaged sites includes:

Obtain the type of site resource on the unmanaged site;

When the site type of the unmanaged site has the first type:

If in the first elastic management group, the number of sites managed by all service nodes is not less than the second site alert value, a new service node is popped up in the first elastic management group, and the unmanaged site is popped up. The first type of site resource is managed;

If in the first elastic management group, there is a service node whose number of managed sites is smaller than the second site alert value, the first type of site resource of the unmanaged site is directly managed by the existing service node;

When the second resource type exists for the site resource type of the unmanaged site:

If in the second elastic management group, the number of sites managed by all service nodes is not less than the third site alert value, a new service node is popped in the second elastic management group, and the unmanaged site is popped up. The second type of site resource is managed;

If in the second flexible management group, there is a service node whose number of managed sites is smaller than the third site alert value, the second type of site resources of the unmanaged site are directly managed by the existing service node.

Optionally, the directly managing, by the existing service node, the first type of site resource of the unmanaged site includes:

If there is a service node whose number of managed sites is smaller than the second site alert value, the number of managed sites is greater than the idle value of the second site, that is, the number of managed sites is greater than the idle value of the second site and is less than The service node of the two-site alert value directly allocates the first type of site resource of the unmanaged site to the service node for management;

The managing the second type of site resources of the unmanaged site directly by the existing service node includes:

If there is a service node whose number of managed sites is less than the third site idle value, the number of managed sites is greater than the third site idle value, and the number of managed sites is greater than the third site idle value. The service node that is smaller than the third site alert value directly allocates the second type of site resource of the unmanaged site to the service node for management.

Optionally, before the acquiring the load information of each service node in the flexible management group and the detection result of the current site that is not managed by the service node, the method further includes:

Determining whether the acquisition condition is met; the obtaining condition includes at least one of the following conditions: when the site of the site resource is newly added; when the preset time is reached; when the site in the elastic management group is deleted; When the system is powered on; actively querying each of the service nodes in the flexible management group and the information of the sites managed by each service node;

When the acquisition condition is met, the step of acquiring the load information of each of the service nodes in the flexible management group and the detection result of the site not currently managed by the service node is performed.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, and the computer virtual executable element control method is implemented when the computer executable instructions are executed.

An embodiment of the present invention further provides a cloud virtual network element control apparatus, including a setup module, an acquisition module, and a management module.

The establishing module is configured to: establish an elastic management group, where the elastic management group includes at least one service node for managing site resources of the site;

The obtaining module is configured to: acquire load information of each service node in the flexible management group and a detection result of a site that is not currently managed by the service node;

The management module is configured to: elastically allocate the site to the service node according to the load information of each of the service nodes and the detection result.

Optionally, the management module includes a determining submodule;

The determining sub-module is configured to determine, according to load information of each service node, whether there is a service node that needs to be retracted in the flexible management group, when the detection result is that there is no unmanaged site; In the flexible management group, when there is a service node whose number of sites is smaller than the idle value of the first site, and the number of sites managed by the service node is not greater than the sum of the number of remaining manageable sites of other service nodes, and When the number of sites managed is less than the idle value of the first site If the resource usage of the node is smaller than the idle value of the first resource, and the resource usage of the service node is not greater than the sum of the remaining resource usages of other service nodes in the elastic management group, the service node needs to be retracted;

When the detection result is that there is an unmanaged site, it is determined according to the load information of each service node whether a new service node needs to be popped up in the elastic management group; when the elastic management group, all the service nodes When the number of sites managed is not less than the first site alert value, a new service node needs to be popped up.

Optionally, the management module further includes:

Retract the submodule and set it to: Perform the business node retraction action.

Optionally, the management module further includes:

The pop-up sub-module is configured to: perform a pop-up new service node action in the flexible management group.

Optionally, the management module further includes:

The configuration management sub-module is set to: manage resource configuration by site.

Optionally, the management module further includes:

The notification sub-module is configured to: notify the configuration management sub-module, which service node management the site resource belongs to, and if the site managed by the service node needs to be migrated to another service node for management, notify the service node to perform the relevant service instance. migrate.

Optionally, the site resource includes a first type of site resource and a second type of site resource;

The management module is configured to separately manage the first type of site resources and the second type of site resources of the site, and the first type of site resources and the second type of site resource configurations of the same site have associated parameters.

Optionally, the management module further includes:

The first judgment sub-module is set to:

When the detection result is that there is no unmanaged site, and the first elastic management group has a service node whose number of managed sites is smaller than the idle value of the second site, and the number of sites managed by the service node is not When the sum of the number of remaining manageable stations of the other service nodes in the first elastic management group is greater than, the service node needs to be retracted;

When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether a new service node needs to be popped up in the first elastic management group; when the site resource of the unmanaged site If the type of the first type exists, if the number of sites managed by all service nodes is not less than the second site alert value in the first elastic management group, a new pop-up service node is required; otherwise, in the first elastic management group. Select an existing service node whose number of sites is less than the second site alert value.

Optionally, the management module further includes:

The second judgment sub-module is set to:

When the detection result is that there is no unmanaged site, and the second elastic management group has a service node whose number of managed sites is smaller than the idle value of the third site, and the number of sites managed by the service node is not When the sum of the number of remaining manageable stations of the other service nodes in the second elastic management group is greater than, the service node needs to be retracted;

When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether a new service node needs to be popped up in the second elastic management group; when the site of the unmanaged site is If there is a second type of the resource type, if the number of sites managed by all the service nodes is not less than the third site alert value in the second elastic management group, the new service needs to be popped up in the second elastic management group. Node; otherwise, in the second elastic management group, the existing service node whose number of managed sites is smaller than the third site alert value is selected.

Optionally, the first determining submodule is further configured to:

Before performing the retracting operation on the service node that is smaller than the first station idle value, determining whether the resource occupancy rate of the service node is smaller than the second resource idle value, if the second resource idle value is less than If the resource occupancy rate of the service node is not greater than the sum of the remaining resource usage rates of the other service nodes in the first elastic management group, the service node needs to be retracted;

The second determining submodule is further configured to:

Before the performing, by the service node, that the number of the managed sites is smaller than the third site idle value, determining whether the resource occupancy of the service node is smaller than the third resource idle value, and if the value is less than the third resource idle value, If the resource occupancy of the service node is not greater than the sum of the remaining resource usages of other service nodes in the second elastic management group, the service node needs to be retracted.

Optionally, the management module further includes:

a type obtaining submodule, configured to: obtain a site resource type on the unmanaged site; when the site resource type of the unmanaged site exists in the first type, the first type of site resource of the unmanaged site is first The service node management in the flexible management group; when the site resource type of the unmanaged site exists in the second type, the second type of site resource of the unmanaged site is managed by the service node in the second elastic management group.

An embodiment of the present invention further provides a radio network controller, including the foregoing cloud virtual network element control apparatus.

A cloud virtual network element control method and device and a wireless network controller using the same are provided in an embodiment of the present invention. The wireless network controller is provided with a cloud virtual network element control device, and the cloud virtual network element control device is established. The flexible management group manages the site resources of the site by using the service nodes in the elastic management group, and then obtains the load information of the service node and the unmanaged site information, and the elastic management group according to the load information and the unmanaged site information. The management of the service node in the middle implements the elastic extension control of the virtual network element such as the service node on the radio network controller. Increased the elastic capacity of the system. As the configuration site increases/decreases and the traffic volume increases/decreases, the system does not need to increase/decrease the hardware to expand/retract as in the related art, but automatically expands/decreases according to the number of sites. Capacity increases efficiency.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a flowchart of a method for controlling a cloud virtual network element according to an embodiment of the present invention;

2 is a schematic diagram of site resource management according to an alternative embodiment of the present invention;

3 is a flowchart of a method for controlling a cloud virtual network element according to an alternative embodiment of the present invention;

4 is a schematic diagram of site resource management according to an alternative embodiment 2 of the present invention;

FIG. 5 is a flowchart of a method for controlling a cloud virtual network element according to an alternative embodiment 2 of the present invention;

FIG. 6 is a schematic diagram of a cloud virtual network element control apparatus according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a radio network controller according to an embodiment of the present invention.

Preferred embodiment of the invention

Embodiments of the present invention will be described below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the various manners in the embodiments may be combined with each other without conflict.

In the computer world, virtualization technology typically simulates multiple independent virtual machines or virtual containers on a single hardware platform. After the virtualization technology is adopted, the running of the program or software does not necessarily have the exclusive physical computing resources. It can be implemented by a dedicated cloud platform to generate virtual machines or virtual containers according to resource requirements (such as CPU working capacity, memory size, hard disk size, etc.).

For convenience of description, the processing nodes that are virtualized independently processable services are represented by service nodes.

Since the status of the different service nodes is equal, the elastic scaling algorithm can be implemented by a centralized point. In the system to which the embodiment of the present invention is applicable, the centralized point is referred to as a primary node. In the embodiment of the present invention, the elastic scaling algorithm can be implemented on the master node.

In addition, different service nodes may be loaded on different service nodes according to different protocols, and service nodes with the same service protocol module may join the same elastic management group. If the service protocol modules loaded on different service nodes are identical, all service nodes can be in the same elastic management group. If the service protocol modules loaded on different service nodes are different, there may be multiple flexible management groups.

According to the process of the service interaction between the radio network controller and the station, as shown in FIG. 5, in the embodiment of the present invention, for a station, the resources that the wireless controller needs to manage may include at least wireless public resources (such as wireless). Signaling link, cell, common transmission channel), wireless dedicated resource (such as UE), transmission of common resources (such as transmission signaling link), transmission of dedicated resources (such as transmission user plane bearer corresponding to the common transmission channel, UE corresponding Transfer user plane bearer).

The above splitting is performed in the embodiment of the present invention, mainly because the wireless public resource, the wireless dedicated resource, the transmission common resource, and the transmission dedicated resource can all be processed by different service protocol modules. These site resources can also be split into several different types of site resources, for example, the transmission signaling link, the transmission user plane bearer corresponding to the common transport channel are classified as transmitting common resources or the cells are separately split into one. Resource types, etc., but in general, can include two situations:

1) These resources of the site are centrally managed by one service node.

2) After the resources of the site are split, they are managed by multiple service nodes.

The embodiments of the present invention are described in the foregoing two situations. The site resources are described by taking only two resources, which are split into radio resources (sum of wireless public resources and dedicated resources) and transmission resources (sum of transmission common resources and dedicated resources). Other split situations can be analogized.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

As shown in FIG. 1 , an embodiment of the present invention provides a cloud virtual network element control method, including the following steps:

S101. Establish an elastic management group, where the elastic management group includes at least one service node for managing site resources of the site;

S102. Acquire load information of each service node in the elastic management group and a detection result of a site that is not currently managed by the service node.

S103. The station is elastically allocated to the service node according to the load information and the detection result of each service node.

The service node in the flexible management group manages the site to which the site resource is allocated, and the corresponding service load information value is represented. The load information may be the number of managed sites and the current resource occupancy rate of the service node; The current resource occupancy rate can be obtained by querying the resource occupancy rate of the current service node, or by querying the resource occupancy rate of each of the multiple sites under the service node. In this embodiment, the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.

When a site is added to the site, you can first configure the site resource for the site, and then assign the configured site to the service node in the corresponding elastic management group for management. In this case, you need to obtain the unmanaged site information. , including the number of sites, site resource types and other site characteristics information.

Before acquiring the load information of each service node and the detection result of the site currently not managed by the service node, the method may further include:

Determining whether the condition is met; the obtaining condition includes at least one of the following conditions: when the site with the site resource is newly added; when the preset time is reached; when the site in the flexible management group is deleted; when the whole system is powered on; Actively query each service node in the flexible management group and each one When the information of the site managed by the business node;

When the acquisition condition is met, the step of acquiring the load information of each service node and the detection result of the station not currently managed by the service node is performed.

The foregoing obtaining conditions may be the timing of acquiring the load information of the service node and the unmanaged site information.

After obtaining the load information of each current service node and the detection result, the service node can be adjusted. The adjustment mode here may include popping up the service node, retracting the service node, and directly adding the site to the existing service node. in. Popping up a service node means that the non-working service node enters the working state, and the process can generally be to power on the service node; retracting the service node means that the working node is in a non-working state, and This process can generally be to power down the service node.

Alternative embodiment 1

This embodiment provides a cloud virtual network element control method. The site resources in this embodiment include radio resources and transmission resources, and the site resources are not classified and managed. The distribution of the site resources on the site is as shown in FIG. 2 Show. The process of managing the site shown in Figure 2 is shown in Figure 3. The process includes:

S301. Organize and configure related radio resources and transmission resource parameters in units of stations. Here, the station-based unit may refer to the correspondence between the radio resources and the transmission resources of the same site.

S302: Create an elastic management group and power on the service node. The flexible management group has a service node for managing site resources of the site.

S303. Obtain site load information of each service node in the elastic management group.

The service node in the flexible management group manages the resources of the site, and can represent the corresponding service load. The traffic load can be the number of managed sites and the current resource occupancy rate of the service node. The current resource occupancy rate of the service node. It can be obtained by querying the resource occupancy rate of the current service node, or by querying the resource occupancy rate of each of the multiple sites under the service node. In this embodiment, the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.

Here, the above information can be obtained by timing reporting or by the active request of the master node.

S304: It is found that a site has no service node management, and the site is allocated according to the number of sites managed by each service node in the elastic management group.

Here, it is found that there is no service node management at a certain site, and there are various methods, which may be found at power-on, or when the system adds a new site, or may be discovered by periodically querying the site information.

When managing, mention can be made of related terms: first site idle value, first site alert value, first resource idle value.

The first station idle value and the first resource idle value are preset thresholds, which are represented as the lower limit value of the service node in the elastic management group that does not waste resources under normal conditions. In this embodiment, the first station idle value is used. Optionally, it is set to 10% of the maximum number of stations that the service node can manage. Similarly, the first resource idle value is optionally set to 10% of the maximum resource occupancy that the service node can accommodate, and may be empty according to the service node. The CPU usage at the time of the load is given. The percentage can be adjusted according to the actual situation, and even a fixed value can be directly set regardless of the management capability of the service node.

The first site alert value is a preset threshold, which is a security value of the number of sites in which the service node in the flexible management group works normally. In this embodiment, the maximum value of the number of sites manageable by the service node is optionally set. 70%, of course, the first site alert value can also be set to other percentages, or even set to a fixed value.

S3041: If the number of sites managed by all the service nodes exceeds the first site alert value, the service node is expanded, and a service node is popped up, and the service node is completely the same as the service protocol loaded by the service node in the elastic management group, and Join the flexible management group. The site is assigned to the service node management, and the management process ends.

S3042: If at least one service node currently manages the number of sites is lower than the first site alert value but greater than the first site idle value, then one of the service nodes is selected, and the site is allocated to the service node management, and the management process ends. .

S305, the new site is not found, that is, all the sites are managed by the service node. In this case, if the number of sites managed on a service node is lower than the idle value of the first site, and the CPU usage of the service node is lower than the first A resource idle value is performed according to the number of service nodes in the elastic management group and the number of sites managed by each service node, and the retracting action of the service node is performed.

Here, there are many ways to find that the number of sites managed by the service node is lower than the idle value. It may be checked when a site is deleted in the system, or may be reported periodically by the service node, or may be checked when the service node is actively queried.

The CPU usage of the service node can be directly reported by the service node or accumulated by the CPU usage of all sites managed on the service node.

S3051: If the sum of the capabilities of other service nodes in the elastic management group can fully accept the service of the service node, that is, the sum of the remaining manageable sites and the remaining CPU usage of other service nodes in the elastic management group is greater than or equal to the service node management respectively. The number of sites and the CPU usage are notified to be retracted to the service node, and all the sites managed by the site are moved to the target service node in the elastic management group. This step can include:

1) Identify the target service node.

When determining the target service node, you can select the service node with the least number of management sites in the elastic management group, or assign it to one or more service nodes with low CPU usage or each service node according to a certain allocation policy. You can all have the same number of new sites assigned.

2) Manage business instances of these sites for migration.

The service nodes to be retracted migrate the established service instances on these sites to the target service nodes, and the resources of these sites can be managed by the target service nodes.

3) Notify the business node that has business contacts.

When the service instance of the migrated site is migrated and the migration is successful, the service node with the service association can be notified in time.

S3052, retracting the idle service node, and the management process ends.

During the running of the system, S303 to S3052 are repeatedly executed to implement elastic scalability control of the site traffic.

Alternative embodiment 2

The embodiment provides a cloud virtual network element control method. The site resource in this embodiment includes a radio resource and a transmission resource, which are respectively used by the service node in the first elastic management group and the service node in the second elastic management group. Management, please see Figure 4. For the management process of the site shown in Figure 4, please refer to Figure 5. The process includes:

S501. The transmission resources are organized and configured on a site-by-site basis, and the wireless resources are organized and configured on a site-by-site basis. Although the transmission resources and radio resources of the same site are managed separately, they still belong to the same site.

S502. The first flexible management group and the second flexible management group are set up, and the service node that manages the radio resource joins the corresponding first elastic management group, and the service node that manages the transmission resource joins the corresponding second flexible management group.

S503. Obtain site load information managed by each service node in each established elastic management group.

The service node in the flexible management group manages the resources of the site, and can represent the corresponding service load. The traffic load can be the number of managed sites and the current resource occupancy rate of the service node. The current resource occupancy rate of the service node. It can be obtained by querying the resource occupancy rate of the current service node, or by querying the resource occupancy rate of each site under the service node. In this embodiment, the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.

Here, the above information can be obtained by timing reporting or by actively requesting.

S504. The wireless resource of a site is found to have no service node management, and the site is allocated according to the number of sites managed by each service node in the first elastic management group.

When managing, mention can be made of related terms: second site idle value, second site alert value, and second resource idle value.

The second site idle value and the second resource idle value are all preset thresholds, which are represented as the lower limit value of the service node in the first elastic management group that does not waste resources under normal conditions. In this embodiment, the second site is used. The idle value is optionally set to 10% of the maximum number of stations that the service node can manage. Similarly, the second resource idle value is optionally set to the maximum resource occupancy rate that the service node in the first elastic management group can accommodate. 10%, which can be given according to the CPU usage when the service node is empty. The percentage can be adjusted according to the actual situation, and even a fixed value can be directly set regardless of the management capability of the service node.

The second site alert value is a preset threshold, and is represented as a security value of the number of sites in which the service node in the first elastic management group works normally, and is optionally set as a site manageable by the service node in this embodiment. The maximum value of the number is 70%. Of course, the second station alert value can also be set to other percentages, and can even be set to a fixed value.

Here, it is found that the wireless resources of a certain site have no service node management, and there are various methods, which may be found at the time of power-on, or may be discovered when the wireless resource configuration of the new site is newly added, or may be periodically queried for the wireless resources of the entire system site. Information to discover.

S5041: If the number of sites managed by all the service nodes exceeds the second site alert value, the service node is expanded, and a service node is popped up, and the service node is identical to the service protocol loaded by the service node in the first elastic management group. And join the first flexible management group. The site is assigned to the service node management, and the management process ends.

S5042: If the number of sites managed by at least one service node is lower than the second site alert value and greater than the second site idle value, select one of the service nodes, and assign the site to the service node management, and the current elastic allocation process ends. .

S505: The transmission resource of a certain site is found to have no service node management, and the primary node performs site allocation according to the number of sites managed by each service node in the second elastic management group.

When managing, related terms can be mentioned: third site idle value, third site alert value, third resource idle value.

The third station idle value and the third resource idle value are all preset thresholds, which are represented as the lower limit value of the service node in the second elastic management group that does not waste resources under normal conditions. In this embodiment, the third site is used. The idle value is optionally set to 10% of the maximum number of stations that the service node can manage. Similarly, the third resource idle value is optionally set to the maximum resource occupancy rate that the service node can accommodate in the second elastic management group. 10%, which can be given according to the CPU usage when the service node is empty. The percentage can be adjusted according to the actual situation, and even a fixed value can be directly set regardless of the management capability of the service node.

The third site alert value is a preset threshold, and is represented as a security value of the number of sites in which the service node in the second elastic management group works normally. In this embodiment, the maximum number of sites manageable by the service node is optionally set. 70% of the value, of course, the third site alert value can also be set to other percentages, and can even be set to a fixed value.

The third station idle value and the second station idle value may be the same or different. For the first The value of the three-site alert value and the second-site alert value may be similar. The value of the value of the third resource idle value and the second resource idle value may also be similar.

Here, it is found that the transmission resource of a certain site has no service node management, and there may be multiple methods, which may be found at the time of power-on, or may be discovered when the transmission resource configuration of the new site is added, or may be transmitted by periodically querying the entire system site. Information to discover.

S5051: If the number of sites managed by all the service nodes exceeds the third site alert value, the service node is expanded, and a service node is popped up, and the service node is completely the same as the service protocol loaded by the service node in the second elastic management group. And join the second flexible management group. The site is assigned to the service node management, and the management process ends.

S5052: If the number of sites managed by at least one service node is lower than the third site alert value and greater than the third site idle value, one of the service nodes is selected, and the site is allocated to the service node management, and the management process ends.

S506: The radio resources of all the sites are managed by the service node, and the number of the radio resources managed by the service node in the first elastic management group is lower than the idle value of the second site, and the CPU usage of the service node is lower than The second resource idle value, the primary node performs the retraction of the service node according to the number of sites managed by each service node in the first elastic management group.

Here, there are many ways to find that the number of sites managed by the service node is lower than the idle value. It may be checked when there is a site being retracted, or may be reported periodically by each service node, or may be checked when actively inquiring each service node.

S5061, if the sum of the capabilities of the other service nodes in the first elastic management group can all accept the service of the service node, that is, the sum of the remaining manageable sites and the remaining CPU usage of the other service nodes in the elastic management group is greater than or equal to the service respectively. The number of sites managed by the node and the CPU usage rate, the master node notifies that it needs to be retracted to the service node, and all the sites it manages need to be moved to the target service node. This step can include:

1) Identify the target service node.

When determining the target service node, you can select the service node with the lowest number of management sites in the first elastic management group, or assign it to one or more service nodes with low CPU usage or each service according to a certain allocation policy. Nodes can all be assigned the same number of new sites.

2) Manage the business instances of the wireless resources of these sites for migration.

The service node to be retracted migrates the established wireless resource service instances on the sites to the target service nodes, and the wireless resources of these sites can be managed by the target service nodes.

3) Notify the business node that has business contacts.

When the radio resource service instance of the migrated site is migrated and the migration is successful, the transport service instance on the service node that manages the transmission resource of the site and other service nodes with service associations can be notified in time.

S5062, retracting the idle service node, and the management process ends.

S507, the transmission resources of all the stations are managed by the service node, and the number of the stations of the transmission resources managed by the service node is lower than the idle value of the third station, and the CPU usage of the service node is lower than the idle value of the third resource. The retracting action of the site is performed according to the number of sites managed by each service node in the second elastic management group.

S5071, if the sum of the capabilities of the other service nodes in the second elastic management group can all accept the service of the service node, that is, the sum of the remaining manageable sites and the remaining CPU usage of the other service nodes in the elastic management group is greater than or equal to the service respectively. The number of sites managed by the node and the CPU usage rate, the master node notifies that it needs to be retracted to the service node, and all the sites it manages need to be moved to the target service node. This step can include:

1) Identify the target service node.

When determining the target service node, you can select the service node with the lowest number of management sites in the second elastic management group, or assign it to one or more service nodes with low CPU usage or each service according to a certain allocation policy. Nodes can all be assigned the same number of new sites.

2) Manage the business instances of the transmission resources of these sites for migration.

The service node to be retracted migrates the established transport resource service instances on the sites to the target service nodes, and the transmission resources of these sites can be subsequently managed by the target service node.

3) Notify the business node that has business contacts.

When the transport resource service instance of the migrated site is migrated and the migration is successful, the wireless service instance on the service node that manages the wireless resource of the site and other service nodes with service associations need to be notified in time.

S5072, retracting the service node with low load, the elastic contraction process ends.

During the running of the system, S503 to S5072 are repeatedly executed to implement elastic scalability control of the site traffic.

In the implementation process of the above two embodiments, the key lies in the judgment of the elastic expansion index, and the following formula is used to further describe the elastic expansion algorithm.

Let the sites managed on the service node A be 1, 2, ..., n, then

CPU load of the business node

1) Flexible expansion index

When the number of sites managed by all service nodes in the elastic management group exceeds the warning value, a pop-up action is performed.

2) elastic shrinkage index

If a service node X has a site number lower than the idle value and the CPU load on the X service node is lower than the CPU idle value,

(X.SiteNum<SiteLv)∩(CPU(X)<CPU.Idle)

In the same elastic management group, the number of remaining sites manageable on other service nodes is sufficient, and other service nodes have the ability to take over the sites on the service node.

Note, because each of the previous business nodes is using SiteHv as a warning line when assigning sites, the absolute limit of SiteMax is not reached. And if a service node A(i) takes over the k stations of the service node X, the CPU load does not exceed the CPU warning line.

The retraction action is performed until all sites on X are successfully received.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, and the computer virtual executable element control method is implemented when the computer executable instructions are executed.

Corresponding to the foregoing control method, an embodiment of the present invention further provides a cloud virtual network element control apparatus.

As shown in Figure 6, the cloud virtual network element control device 600 includes an establishing module 601, an obtaining module 602, a management module 603;

The establishing module 601 is configured to: establish an elastic management group, where the elastic management group includes at least one service node for managing site resources of the site;

The obtaining module 602 is configured to: obtain load information of each service node in the elastic management group and a detection result of a site that is not currently managed by the service node;

The management module 603 is configured to: elastically allocate the site to the management of the service node according to the load information of each of the service nodes and the detection result.

In this embodiment, the obtaining module 602 can include:

The load acquisition sub-module 6021 and the site acquisition sub-module 6022 are respectively configured to: acquire load information of the service node and acquire a detection result of the site not managed by the service node.

In this embodiment, the management module 603 can include:

The judging sub-module 6031 is set to: according to the site load and unserviced of each service node The detection result of the site managed by the node determines whether the pop-up or retraction of the service node is required.

Optionally, the determining submodule 6031 is set to:

If there are sites that are not managed by the service node, if the number of sites managed by all the service nodes in the elastic management group exceeds the alert value, the pop-up action of the service node is performed;

If there is a service node in the flexible management group, and the number of sites managed by the elastic management group is between the idle value of the site and the alert value, no pop-up or retract action is performed;

If there is a service node in the flexible management group, the number of sites managed by it is lower than the idle value of the site, and the resource of the service node is lower than the resource idle value, and the total management capacity of other service nodes can be accepted by the service node. For the service, the retraction action of the service node is performed.

Alternatively, optionally, the determining submodule 6031 is set to:

When the detection result is that there is no unmanaged site, it is determined according to the load information of each service node whether there is a service node that needs to be retracted in the flexible management group; when the elastic management group exists, the number of sites managed is less than the number a service node with a site idle value, and the number of sites managed by the service node is not greater than the sum of the number of remaining manageable sites of other service nodes, and when the number of managed sites is smaller than the resources of the service node of the idle value of the first site When the occupancy rate is less than the idle value of the first resource, and the resource occupancy rate of the service node is not greater than the sum of the remaining resource usage rates of other service nodes in the elastic management group, the service node needs to be retracted;

When the result of the detection is that there is an unmanaged site, it is determined whether the new service node needs to be popped up in the flexible management group according to the load information of each service node; when the elastic management group, the number of sites managed by all service nodes is not less than When the first site is alert, a new service node needs to be popped up.

The management module 603 can also include:

The retracting sub-module 6032 is configured to perform a service node retracting action.

The management module 603 can also include:

The pop-up sub-module 6033 is configured to perform a new service node pop-up action in the flexible management group.

The management module 603 can also include:

The configuration management sub-module 6034 is configured to perform resource configuration management on a site-by-site basis.

The management module 603 can also include:

The notification sub-module 6035 is configured to: notify the configuration management sub-module, which service node management the site resource belongs to, and if the site managed by the service node needs to be migrated to another service node for management, notify the service node to notify the relevant service instance. Perform the migration.

Optionally, the site resource includes a first type of site resource and a second type of site resource;

The elastic management group includes a first elastic management group and a second flexible management group.

The management module is configured to: the service node in the first elastic management group and the service node in the second elastic management group respectively manage the first type of site resource and the second type of site resource of the site, and the same site The first type of site resource and the second type of site resource have associated parameters.

Optionally, the management module may further include:

The first judgment sub-module is set to:

When the detection result is that there is no unmanaged site, and the first elastic management group has a service node whose number of managed sites is smaller than the idle value of the second site, and the number of sites managed by the service node is not greater than the first elasticity When the sum of the number of remaining manageable stations of other service nodes in the management group is managed, the service node needs to be retracted;

When the detection result is that there is an unmanaged site, it is determined according to the load information of each service node whether a new service node needs to be popped up in the first elastic management group; when the site resource type of the unmanaged site has the first type If, in the first elastic management group, the number of sites managed by all the service nodes is not less than the second site alert value, the new service node needs to be popped up in the first elastic management group; otherwise, the first elastic management group is selected. The number of sites managed is less than the existing service node of the second site alert value.

Optionally, the management module may further include:

The second judgment sub-module is set to:

When the detection result is that there is no unmanaged site, and the second elastic management group has a service node whose number of managed sites is smaller than the idle value of the third site, and the number of sites managed by the service node is not greater than the second elasticity When the sum of the number of remaining manageable stations of other service nodes in the management group is managed, the service node needs to be retracted;

When the detection result is that there is an unmanaged site, according to the load information of each service node Determining whether a new service node needs to be popped up in the second elastic management group; if the site resource type of the unmanaged site exists in the second type, if the second elastic management group is in the second elastic management group, the number of sites managed by all the service nodes is not If the alarm value is less than the third site, the new service node needs to be popped up in the second elastic management group; otherwise, the existing service node whose number of managed sites is smaller than the third site alert value is selected in the second elastic management group.

Optionally, the first determining submodule is further configured to:

Before performing the retracting action on the service node whose number of the managed sites is smaller than the idle value of the first site, determining whether the resource occupancy rate of the service node is smaller than the second resource idle value, and if the second resource idle value is less than the second resource idle value, and the service node If the resource occupancy rate is not greater than the sum of the remaining resource usage rates of other service nodes in the first elastic management group, the service node needs to be retracted.

Optionally, the second determining submodule is further configured to:

Before performing the retracting action on the service node whose number of the managed sites is smaller than the idle value of the third site, determining whether the resource occupancy rate of the service node is smaller than the idle value of the third resource, and if the value is less than the idle value of the third resource, and the service node If the resource occupancy rate is not greater than the sum of the remaining resource usage rates of other service nodes in the second elastic management group, the service node needs to be retracted.

The management module 603 can also include:

The type obtaining submodule 6036 is configured to: acquire a site resource type on the unmanaged site;

When the first type of the site resource type of the unmanaged site exists, the first type of site resource of the unmanaged site is managed by the service node in the first elastic management group.

When the second resource type of the site resource type of the unmanaged site exists, the second type site resource of the unmanaged site is managed by the service node in the second elastic management group.

The modules of the above embodiments may be combined into one module, or may be split into multiple sub-modules. For example, if the site resource is divided into the first site resource and the second site resource, the determining submodule may also be split into the first determining submodule and the second determining submodule.

It will be understood by those skilled in the art that the modules in the devices in the embodiments may be distributed in the devices of the embodiments according to the embodiments, or may be correspondingly changed in one or more devices different from the embodiment.

The embodiment of the invention further provides a radio network controller, as shown in FIG. 7, which includes the above Cloud virtual network element control device 600.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art may know that the embodiments of the present invention are not limited by the described action sequence. Because certain steps may be performed in other orders or concurrently in accordance with embodiments of the present invention.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, processor, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, processor, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

A person skilled in the art can understand that the technical solutions of the present application can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present application. The scope of protection of this application is defined by the scope defined by the claims.

Industrial applicability

A cloud virtual network element control method and device and a wireless network controller using the same are provided in an embodiment of the present invention. The wireless network controller is provided with a cloud virtual network element control device, and the cloud virtual network element control device is established. The flexible management group manages the site resources of the site by using the service nodes in the elastic management group, and then obtains the load information of the service node and the unmanaged site information, and the elastic management group according to the load information and the unmanaged site information. The management of the service node in the middle implements the elastic extension control of the virtual network element such as the service node on the radio network controller. Increased the elastic capacity of the system. As the configuration site increases/decreases and the traffic volume increases/decreases, the system does not need to increase/decrease the hardware to expand/retract as in the related art, but automatically expands/decreases according to the number of sites. Capacity increases efficiency.

Claims (22)

A cloud virtual network element control method includes: Establishing an elastic management group, where the elastic management group includes at least one service node for managing site resources; Obtaining load information of each service node in the flexible management group and a detection result of a site currently not managed by the service node; And assigning the site elasticity to the management of the service node according to the load information of each of the service nodes and the detection result. The cloud virtual network element control method according to claim 1, wherein the dynamically assigning the site to the service node according to the load information of each of the service nodes and the detection result comprises: When the detection result is that there is no unmanaged site, it is determined according to the load information of each service node whether there is a service node that needs to be retracted in the flexible management group; When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether an existing service node needs to be used in the flexible management group or a new service node is popped up to Managed sites are managed. The cloud virtual network element control method according to claim 2, wherein the load information of the service node includes the number of stations managed by the service node; When the detection result is that there is no unmanaged site, determining whether there is a service node that needs to be retracted in the flexible management group according to the load information of each service node includes: When there is a service node whose number of managed sites is smaller than the idle value of the first site, and the number of sites managed by the service node is not greater than the sum of the number of remaining manageable sites of other service nodes, The service node is retracted and the site managed by the service node is migrated to another service node for management. The cloud virtual network element control method according to claim 3, wherein the load information of the service node further includes a resource occupancy rate of the service node; The method further includes: before retracting the service node whose number of managed sites is smaller than the idle value of the first site, and migrating the site managed by the service node to another service node for management, the method further includes: Determining whether the resource occupancy rate of the service node whose number of sites is smaller than the idle value of the first site is smaller than the idle value of the first resource, and if the value of the resource is less than the idle value of the first resource, and the resource occupancy rate of the service node is not greater than the elasticity To manage the sum of the remaining resource usages of other service nodes in the group, perform the step of retracting the service node and migrating the site managed by the service node to another service node for management. The cloud virtual network element control method according to any one of claims 2 to 4, wherein, when the detection result is that there is an unmanaged site, determining whether the elasticity is required according to the load information Using an existing service node or popping up a new service node within the management group to manage the unmanaged site includes: When there is a service node whose number of managed sites is smaller than the first site alert value, the unmanaged site is allocated to the service node for management; When the number of sites managed by all service nodes is not less than the first site alert value in the flexible management group, a new service node pops up in the elastic management group to manage the unmanaged site. The cloud virtual network element control method according to claim 2, wherein The site resource includes a first type of site resource and a second type of site resource; The elastic management group includes a first elastic management group and a second flexible management group. In the step of dynamically assigning the site to the management of the service node according to the load information and the detection result, the service node in the first elastic management group and the service node in the second elastic management group respectively The first type of site resource and the second type of site resource of the site are managed, and the first type of site resource and the second type of site resource of the same site are configured with associated parameters. The cloud virtual network element control method according to claim 6, wherein the load information includes the number of stations managed by the service nodes in the first elastic management group and the second flexible management group; When the detection result is that there is no unmanaged site, determining whether there is a service node that needs to be retracted in the flexible management group according to the load information of each service node includes: In the first elastic management group, there is a service node whose number of managed sites is smaller than the idle value of the second site, and the number of sites managed by the service node is not greater than the remaining of other service nodes in the first elastic management group. When the sum of the number of sites can be managed, the service node is retracted, and the site managed by the service node is migrated to other service nodes in the first elastic management group for management; When the second elastic management group has a service node whose number of managed sites is smaller than the idle value of the third site, and the number of sites managed by the service node is not greater than the remaining of other service nodes in the second elastic management group. When the sum of the number of sites can be managed, the service node is retracted, and the site managed by the service node is migrated to other service nodes in the second elastic management group for management. The cloud virtual network element control method according to claim 7, wherein the load information of the service node further includes a resource occupancy rate of the service node; Before the retracting the service node whose number of sites is smaller than the idle value of the second site, and the site managed by the service node is migrated to another service node for management, the method further includes: Determining whether the resource occupancy rate of the service node is less than the idle value of the second resource, and if the value is less than the idle value of the second resource, and the resource occupancy rate of the service node is not greater than the remaining resource usage of the other service nodes in the first elastic management group. And the step of retrieving the service node and migrating the site managed by the service node to another service node in the first elastic management group for management; The method further includes: before retracting the service node whose number of sites is smaller than the idle value of the third site, and migrating the site managed by the service node to another service node for management, the method further includes: Determining whether the resource occupancy rate of the service node is smaller than the idle value of the third resource, and if the value is less than the idle value of the third resource, and the resource occupancy rate of the service node is not greater than the remaining resource usage of the other service nodes in the second elastic management group. And the step of retrieving the service node and migrating the site managed by the service node to another service node in the second elastic management group for management. The cloud virtual network element control method according to any one of claims 6 to 8, wherein when the detection result is that there is an unmanaged site, it is determined according to the load information of each of the service nodes whether The use of an existing service node or pop-up of a new service node in the flexible management group to manage the unmanaged site includes: Obtain the site resource type of the unmanaged site; When the site type of the unmanaged site has the first type: If in the first elastic management group, the number of sites managed by all service nodes is not less than the second site alert value, a new service node is popped up in the first elastic management group, and the unmanaged site is popped up. The first type of site resource is managed; If in the first elastic management group, there is a service node whose number of managed sites is smaller than the second site alert value, the first type of site is directly used by the existing service node for the unmanaged site. Source management; When the second resource type exists for the site resource type of the unmanaged site: If in the second elastic management group, the number of sites managed by all service nodes is not less than the third site alert value, a new service node is popped in the second elastic management group, and the unmanaged site is popped up. The second type of site resource is managed; If in the second flexible management group, there is a service node whose number of managed sites is smaller than the third site alert value, the second type of site resources of the unmanaged site are directly managed by the existing service node. The cloud virtual network element control method according to claim 9, wherein the directly managing the first type of site resources of the unmanaged site by the existing service node comprises: If there is a service node whose number of managed sites is smaller than the second site alert value, the number of managed sites is greater than the idle value of the second site, that is, the number of managed sites is greater than the idle value of the second site and is less than The service node of the two-site alert value directly allocates the first type of site resource of the unmanaged site to the service node for management; The managing the second type of site resources of the unmanaged site directly by the existing service node includes: If there is a service node whose number of managed sites is less than the third site idle value, the number of managed sites is greater than the third site idle value, and the number of managed sites is greater than the third site idle value. The service node that is smaller than the third site alert value directly allocates the second type of site resource of the unmanaged site to the service node for management. The cloud virtual network element control method according to any one of claims 1 to 4, wherein before the load information of each of the service nodes in the flexible management group and the detection result of the site currently not managed by the service node are acquired ,Also includes: Determining whether the acquisition condition is met; the obtaining condition includes at least one of the following conditions: when the site of the site resource is newly added; when the preset time is reached; when the site in the elastic management group is deleted; When the system is powered on; actively querying each of the service nodes in the flexible management group and the information of the sites managed by each service node; When the acquisition condition is met, the step of acquiring the load information of each of the service nodes in the flexible management group and the detection result of the current site that is not managed by the service node are performed. A cloud virtual network element control device includes a setup module, an acquisition module, and a management module; The establishing module is configured to: establish an elastic management group, where the elastic management group includes at least one service node for managing site resources of the site; The obtaining module is configured to: acquire load information of each service node in the flexible management group and a detection result of a site that is not currently managed by the service node; The management module is configured to: elastically allocate the site to the service node according to the load information of each of the service nodes and the detection result. The cloud virtual network element control device according to claim 12, wherein the management module comprises a determination sub-module; The determining sub-module is configured to determine, according to load information of each service node, whether there is a service node that needs to be retracted in the flexible management group, when the detection result is that there is no unmanaged site; In the flexible management group, when there is a service node whose number of sites is smaller than the idle value of the first site, and the number of sites managed by the service node is not greater than the sum of the number of remaining manageable sites of other service nodes, and The resource occupancy rate of the service node that is smaller than the idle value of the first site is smaller than the idle value of the first resource, and the resource occupancy rate of the service node is not greater than the remaining resource usage of other service nodes in the elastic management group. And time, the business node needs to be retracted; When the detection result is that there is an unmanaged site, it is determined according to the load information of each service node whether a new service node needs to be popped up in the elastic management group; when the elastic management group, all the service nodes When the number of sites managed is not less than the first site alert value, a new service node needs to be popped up. The cloud virtual network element control apparatus according to claim 12, wherein the management module further comprises: Retract the submodule and set it to: Perform the business node retraction action. The cloud virtual network element control apparatus according to claim 12, wherein the management module further comprises: The pop-up sub-module is configured to: perform a pop-up new service node action in the flexible management group. The cloud virtual network element control apparatus according to claim 12, wherein the management module further comprises: The configuration management sub-module is set to: manage resource configuration by site. The cloud virtual network element control apparatus according to claim 12, wherein the management module further comprises: The notification sub-module is set to: notify the configuration management sub-module, which service the site resource belongs to Node management, if the site managed by the service node needs to be migrated to another service node for management, the service node is notified to migrate the related service instance. The cloud virtual network element control device according to claim 12, wherein The site resource includes a first type of site resource and a second type of site resource; The elastic management group includes a first elastic management group and a second flexible management group. The management module is configured to: the service node in the first elastic management group and the service node in the second elastic management group respectively manage the first type of site resource and the second type of site resource of the site And the first type of site resource and the second type of site resource configuration of the same site have associated parameters. The cloud virtual network element control apparatus according to claim 18, wherein the management module further comprises: The first judgment sub-module is set to: When the detection result is that there is no unmanaged site, and the first elastic management group has a service node whose number of managed sites is smaller than the idle value of the second site, and the number of sites managed by the service node is not When the sum of the number of remaining manageable stations of the other service nodes in the first elastic management group is greater than, the service node needs to be retracted; When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether a new service node needs to be popped up in the first elastic management group; when the site resource of the unmanaged site When the type of the first type exists, if the number of sites managed by all the service nodes in the first elastic management group is not less than the second site alert value, the new service node needs to be popped up in the first elastic management group. Otherwise, in the first flexible management group, the existing service node whose number of sites managed is smaller than the second site alert value is selected; The management module further includes: The second judgment sub-module is set to: When the detection result is that there is no unmanaged site, and the second elastic management group has a service node whose number of managed sites is smaller than the idle value of the third site, and the number of sites managed by the service node is not When the sum of the number of remaining manageable stations of the other service nodes in the second elastic management group is greater than, the service node needs to be retracted; When the detection result is that there is an unmanaged site, determining, according to the load information of each service node, whether a new service node needs to be popped up in the second elastic management group; If the number of the site resource types of the management site is the second type, if the number of sites managed by all the service nodes in the second elastic management group is not less than the third site alert value, the second elastic management group is required. A new service node is popped up; otherwise, an existing service node whose number of managed sites is smaller than the third site alert value is selected in the second elastic management group. The cloud virtual network element control apparatus according to claim 19, wherein the first determining submodule is further configured to: Before performing the retracting operation on the service node that is smaller than the first station idle value, determining whether the resource occupancy rate of the service node is smaller than the second resource idle value, if the second resource idle value is less than If the resource occupancy rate of the service node is not greater than the sum of the remaining resource usage rates of the other service nodes in the first elastic management group, the service node needs to be retracted; The second determining submodule is further configured to: Before the performing, by the service node, that the number of the managed sites is smaller than the third site idle value, determining whether the resource occupancy of the service node is smaller than the third resource idle value, and if the value is less than the third resource idle value, If the resource occupancy of the service node is not greater than the sum of the remaining resource usages of other service nodes in the second elastic management group, the service node needs to be retracted. The cloud virtual network element control apparatus according to any one of claims 18 to 20, wherein the management module further comprises: a type obtaining submodule, configured to: obtain a site resource type on the unmanaged site; when the site resource type of the unmanaged site exists in the first type, the first type of site resource of the unmanaged site is first The service node management in the flexible management group; when the site resource type of the unmanaged site exists in the second type, the second type of site resource of the unmanaged site is managed by the service node in the second elastic management group. A radio network controller comprising the cloud virtual network element control apparatus according to any one of claims 12 to 21.

Images