WO2017096920A1 - Procédé et appareil de commande d'élément de réseau virtuel de nuage, et dispositif de commande de réseau sans fil - Google Patents

Procédé et appareil de commande d'élément de réseau virtuel de nuage, et dispositif de commande de réseau sans fil Download PDF

Info

Publication number
WO2017096920A1
WO2017096920A1 PCT/CN2016/091880 CN2016091880W WO2017096920A1 WO 2017096920 A1 WO2017096920 A1 WO 2017096920A1 CN 2016091880 W CN2016091880 W CN 2016091880W WO 2017096920 A1 WO2017096920 A1 WO 2017096920A1
Authority
WO
WIPO (PCT)
Prior art keywords
site
service node
resource
managed
management group
Prior art date
Application number
PCT/CN2016/091880
Other languages
English (en)
Chinese (zh)
Inventor
赵艳华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017096920A1 publication Critical patent/WO2017096920A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices

Definitions

  • 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.
  • 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.
  • 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.
  • a cloud service a conventional RNC (Radio Network Controller, the radio network controller), CN (core net, core network), the NodeB (base station) are NE
  • RNC Radio Network Controller, the radio network controller
  • CN core net, core network
  • NodeB base station
  • 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.
  • 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.
  • a CCP Common Control Port
  • 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.
  • 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:
  • the flexible management group including at least one service node for managing site resources of the site;
  • the dynamically assigning the site to the service node according to the load information and the detection result includes:
  • the load information determines whether there is a service node that needs to be retracted in the flexible management group
  • the load information of the service node includes at least the number of stations managed by the service node;
  • 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:
  • the service node 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 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:
  • 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.
  • 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:
  • the unmanaged site is allocated to the service node for management;
  • 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 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 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;
  • 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:
  • 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.
  • 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;
  • 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.
  • 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 load information of the service node further includes a resource occupancy rate of the service node
  • the method further includes:
  • 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:
  • the detection result is that there is an unmanaged site
  • the management of the unmanaged sites includes:
  • 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;
  • the first type of site resource of the unmanaged site is directly managed by the existing service node;
  • 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;
  • the second type of site resources of the unmanaged site are directly managed by the existing service node.
  • the directly managing, by the existing service node, the first type of site resource of the unmanaged site includes:
  • 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:
  • 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 method 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:
  • 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;
  • 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.
  • 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;
  • 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;
  • the management module further includes:
  • 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.
  • the management module further includes:
  • the configuration management sub-module is set to: manage resource configuration by site.
  • 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.
  • 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.
  • the management module further includes:
  • the first judgment sub-module is set to:
  • 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
  • the service node needs to be retracted;
  • 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.
  • the management module further includes:
  • the second judgment sub-module is set to:
  • 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
  • the service node needs to be retracted;
  • 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.
  • the first determining submodule is further configured to:
  • the service node 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:
  • the service node 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 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.
  • 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.
  • FIG. 1 is a flowchart of a method for controlling a cloud virtual network element according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of site resource management according to an alternative embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for controlling a cloud virtual network element according to an alternative embodiment of the present invention.
  • FIG. 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.
  • 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.).
  • processing nodes that are virtualized independently processable services are represented by service nodes.
  • the elastic scaling algorithm can be implemented by a centralized point.
  • the centralized point is referred to as a primary node.
  • the elastic scaling algorithm can be implemented on the master node.
  • 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.
  • 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).
  • wireless public resources such as wireless
  • UE wireless dedicated resource
  • transmission of common resources such as transmission signaling link
  • 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.
  • 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.
  • an embodiment of the present invention provides a cloud virtual network element control method, including the following steps:
  • 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.
  • the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.
  • the method may further include:
  • 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;
  • 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.
  • the service node 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.
  • 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:
  • 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.
  • 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.
  • the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.
  • 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.
  • first site idle value 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.
  • the first station idle value is used.
  • it is set to 10% of the maximum number of stations that the service node can manage.
  • 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.
  • 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.
  • 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. .
  • the new site is not found, that is, all the sites are managed by the service node.
  • 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.
  • 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:
  • 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.
  • 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.
  • the service node with the service association can be notified in time.
  • S303 to S3052 are repeatedly executed to implement elastic scalability control of the site traffic.
  • 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.
  • the process includes:
  • 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.
  • 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.
  • 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.
  • the resource occupancy rate is optionally the sum of the CPU usage of the service node or the CPU usage of the site.
  • the above information can be obtained by timing reporting or by actively requesting.
  • 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.
  • second site idle value 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.
  • 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.
  • 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%.
  • the second station alert value can also be set to other percentages, and can even be set to a fixed value.
  • 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.
  • 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.
  • third site idle value 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • This step can include:
  • 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.
  • 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.
  • 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.
  • 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.
  • This step can include:
  • 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.
  • 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.
  • 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.
  • S503 to S5072 are repeatedly executed to implement elastic scalability control of the site traffic.
  • the key lies in the judgment of the elastic expansion index, and the following formula is used to further describe the elastic expansion algorithm.
  • 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.
  • 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.
  • an embodiment of the present invention further provides a cloud virtual network element control apparatus.
  • 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.
  • 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.
  • 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.
  • the determining submodule 6031 is set to:
  • 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.
  • the retraction action of the service node is performed.
  • the determining submodule 6031 is set to:
  • 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;
  • 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.
  • 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.
  • the management module may further include:
  • the first judgment sub-module is set to:
  • 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
  • the service node needs to be retracted
  • the detection result is that there is an unmanaged site
  • the management module may further include:
  • the second judgment sub-module is set to:
  • 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
  • the service node needs to be retracted
  • 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.
  • the first determining submodule is further configured to:
  • the service node 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.
  • the second determining submodule is further configured to:
  • the service node 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;
  • the first type of site resource type of the unmanaged site is managed by the service node in the first elastic management group.
  • 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.
  • the determining submodule may also be split into the first determining submodule and the second determining submodule.
  • 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.
  • 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.
  • the device/function module/functional unit in the above embodiment 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.
  • 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.
  • the device/function module/functional unit in the above embodiment 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 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de commande d'élément de réseau virtuel de nuage qui consiste : à établir un groupe de gestion souple, le groupe de gestion souple comprenant au moins un nœud de service utilisé pour gérer une ressource de station ; à acquérir des informations de charge de chaque nœud de service parmi le ou les nœuds de service dans le groupe de gestion souple et un résultat de détection d'une station non gérée en cours par le nœud de service ; et à allouer de manière souple la station au nœud de service pour une gestion selon les informations de charge de chaque nœud de service et le résultat de détection.
PCT/CN2016/091880 2015-12-09 2016-07-27 Procédé et appareil de commande d'élément de réseau virtuel de nuage, et dispositif de commande de réseau sans fil WO2017096920A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510900240.1 2015-12-09
CN201510900240.1A CN106856435A (zh) 2015-12-09 2015-12-09 一种云虚拟网元控制方法和装置以及无线网络控制器

Publications (1)

Publication Number Publication Date
WO2017096920A1 true WO2017096920A1 (fr) 2017-06-15

Family

ID=59013691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/091880 WO2017096920A1 (fr) 2015-12-09 2016-07-27 Procédé et appareil de commande d'élément de réseau virtuel de nuage, et dispositif de commande de réseau sans fil

Country Status (2)

Country Link
CN (1) CN106856435A (fr)
WO (1) WO2017096920A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240089320A1 (en) * 2019-05-29 2024-03-14 Cloudflare, Inc. State management and object storage in a distributed cloud computing network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030014524A1 (en) * 2001-07-11 2003-01-16 Alexander Tormasov Balancing shared servers in virtual environments
CN102550004A (zh) * 2009-09-30 2012-07-04 阿尔卡特朗讯公司 企业网络中分配的云资源的动态负载平衡和调配
CN103617086A (zh) * 2013-11-20 2014-03-05 东软集团股份有限公司 一种并行计算方法及系统
CN104468407A (zh) * 2013-09-16 2015-03-25 中国电信股份有限公司 实现业务平台资源弹性分配的方法与装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030014524A1 (en) * 2001-07-11 2003-01-16 Alexander Tormasov Balancing shared servers in virtual environments
CN102550004A (zh) * 2009-09-30 2012-07-04 阿尔卡特朗讯公司 企业网络中分配的云资源的动态负载平衡和调配
CN104468407A (zh) * 2013-09-16 2015-03-25 中国电信股份有限公司 实现业务平台资源弹性分配的方法与装置
CN103617086A (zh) * 2013-11-20 2014-03-05 东软集团股份有限公司 一种并行计算方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240089320A1 (en) * 2019-05-29 2024-03-14 Cloudflare, Inc. State management and object storage in a distributed cloud computing network

Also Published As

Publication number Publication date
CN106856435A (zh) 2017-06-16

Similar Documents

Publication Publication Date Title
WO2020001171A1 (fr) Procédé et dispositif d'attribution de ressources de tranche de réseau
US20200015131A1 (en) Communication method and communications device
US10924966B2 (en) Management method, management unit, and system
WO2019033817A1 (fr) Procédé, appareil, et système de communication
US11831509B2 (en) Network service management method, device, and system
US10979285B2 (en) Service transmission method, device, and system
JP6636142B2 (ja) スケールアウト関連付けの方法および装置、ならびにシステム
US11646939B2 (en) Network function NF management method and NF management device
CN110896355A (zh) 一种网络切片的选择方法及装置
US11088924B2 (en) Network management method, device, and system
US20230041039A1 (en) Method, device, and system for deploying network slice
EP3661291A1 (fr) Procédé de gestion d'un composant de réseau, et dispositif réseau
TWI697239B (zh) 資源塊組的劃分方法和使用者終端
WO2017107666A1 (fr) Procédé d'agrégation de porteuses, équipement côté réseau et support de stockage informatique
TWI692989B (zh) 上行資料包資源配置方法和使用者終端
WO2018121178A1 (fr) Procédé, dispositif, et système d'ajustement de ressources
WO2019029704A1 (fr) Procédé de gestion d'objet de réseau et appareil s'y rapportant
US11700189B2 (en) Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing
US10129739B2 (en) Data transmission method and device
WO2017096920A1 (fr) Procédé et appareil de commande d'élément de réseau virtuel de nuage, et dispositif de commande de réseau sans fil
CN107534678B (zh) 建立vnfm与vim之间的连接的方法、装置及系统
JP2020022053A (ja) 通信制御装置
WO2019100924A1 (fr) Procédé et dispositif de garantie de performance de réseau
CN107408058A (zh) 一种虚拟资源的部署方法、装置及系统
CN107615872B (zh) 一种释放连接的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16872119

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16872119

Country of ref document: EP

Kind code of ref document: A1