CN112565390A - Service distribution method, device, electronic equipment and storage medium - Google Patents
Service distribution method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112565390A CN112565390A CN202011385200.5A CN202011385200A CN112565390A CN 112565390 A CN112565390 A CN 112565390A CN 202011385200 A CN202011385200 A CN 202011385200A CN 112565390 A CN112565390 A CN 112565390A
- Authority
- CN
- China
- Prior art keywords
- network element
- service
- network
- identifier
- target
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides a service allocation method, a device, electronic equipment and a storage medium, wherein the service allocation method determines candidate services in preset network services according to network element type identifiers by receiving a registration request which is sent by an idle network element and carries network element cluster identifiers and network element type identifiers; determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service, and then determining the target service in the candidate service according to the target network element and a preset load balancing algorithm; finally, the service resources of the target service are sent to the target network element; the service allocation method provided by the embodiment of the application can determine the target network element according to the bearing condition of the network service and the working state of the network element cluster, and can allocate the appropriate network service to the target network element, so that the service processing efficiency and the accuracy are improved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a service distribution method and apparatus, an electronic device, and a storage medium.
Background
In the context of the construction of the fifth Generation mobile communication (5G, 5th-Generation) network, in order to fully utilize its advantages to obtain better user experience, various edge cloud systems that meet the user's needs nearby are in the endlessly. A cloud gateway is an important device in an edge cloud system, and includes a controller and a virtual Network element (VNF), where the virtual Network element is a Network element Virtualized by a virtualization technology to implement some specific functions, and the controller is configured to manage the virtual Network element, for example, to allocate a Network service to the virtual Network element.
Because the types and the number of the network services and the virtual network elements are numerous, and the number, the types or the number of the types of the virtual network elements which can be carried by different network services are different, at present, the situation of wrong distribution often occurs when the controller distributes the network services for the virtual network elements, so that the processing efficiency of the edge cloud service is low, the accuracy is low, and particularly, when the number of the virtual network elements carried by the network services reaches the upper limit, the distribution abnormality occurs when the controller distributes the network services for the virtual network elements.
Disclosure of Invention
The embodiment of the application provides a service allocation method, a service allocation device, electronic equipment and a storage medium, which are used for solving the technical problem that wrong allocation often occurs when network services are allocated to virtual network elements.
In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:
an embodiment of the present application provides a service allocation method, including:
receiving a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier;
determining candidate services in preset network services according to the network element type identifier;
determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service;
determining a target service in the candidate services according to the target network element and a preset load balancing algorithm;
and sending the service resource of the target service to the target network element.
In some embodiments, the step of determining a candidate service among preset network services according to the network element type identifier includes:
calling a preset service bearing capacity table, wherein a service identifier corresponding to each network service, and a bearing type identifier and the number of network elements capable of bearing are stored in the service bearing capacity table in an associated manner;
sequentially judging whether the bearing type identification capable of being borne by each network service is consistent with the network element type identification;
and if so, determining the network service as the candidate service.
In some embodiments, the step of determining, according to the network element cluster identifier, the network element type identifier, and the candidate service, a target network element in a network element cluster corresponding to the network element cluster identifier includes:
calling the service bearing capacity table and a preset distributed service table, wherein the distributed service table is stored with service identification corresponding to each network service and network element identification of a loaded network element in a correlated manner;
judging whether the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements or not;
and if the number of the network elements which can be carried by the candidate service is equal to the number of the carried network elements, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
In some embodiments, the step of determining, according to the network element cluster identifier, the network element type identifier, and the candidate service, a target network element in a network element cluster corresponding to the network element cluster identifier further includes:
if the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements, acquiring the number of idle network elements in the network element cluster corresponding to the network element cluster identifier;
judging whether the number of the idle network elements is larger than a preset idle network element threshold value or not;
if the number of the idle network elements is larger than the idle network element threshold value, determining the idle network elements as target network elements;
and if the number of the idle network elements is less than or equal to an idle network element threshold value, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
In some embodiments, before the step of determining whether the number of network elements that can be carried by the candidate service is greater than the number of already-carried network elements, the method further includes:
and acquiring the number of the network elements carried by the candidate services according to the network element identifiers carried by the candidate services.
In some embodiments, if there is a case that the number of network elements that can be carried by the candidate service is equal to the number of network elements already carried, the step of determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element includes:
determining candidate network elements in the network element cluster corresponding to the network element cluster identifier according to the network element type identifier, wherein the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
acquiring network element information reported by each candidate network element;
and determining a target network element in each candidate network element according to the network element information.
In some embodiments, after the step of determining a target service among the candidate services according to the target network element and a preset load balancing algorithm, the method further includes:
and storing the target network element identification of the target network element in the allocated service table, and associating the target network element identification with the service identification of each target service.
The present application further provides a service distribution apparatus, including:
a registration request receiving module, configured to receive a registration request sent by an idle network element, where the registration request carries an idle network element identifier, and the idle network element identifier includes a network element cluster identifier and a network element type identifier;
a candidate service determining module, configured to determine a candidate service among preset network services according to the network element type identifier;
a target network element determining module, configured to determine a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier, and the candidate service;
a target service determining module, configured to determine a target service among the candidate services according to the target network element and a preset load balancing algorithm;
and the service resource sending module is used for sending the service resource of the target service to the target network element.
The present application also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the service allocation method as described above when executing the program.
The present application also provides a computer-readable storage medium having stored thereon a plurality of instructions that can be loaded by a processor to perform the service distribution method as described above.
The beneficial effect of this application: the application provides a service allocation method, a device, an electronic device and a storage medium, wherein the service allocation method receives a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier; determining candidate services in preset network services according to the network element type identifier; determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service, for example, taking an idle network element or a non-idle network element as the target network element; then, determining a target service in the candidate services according to the target network element and a preset load balancing algorithm; and finally, sending the service resource of the target service to the target network element. The target network element is determined according to the bearing condition of the network service and the working state of the network element cluster, the appropriate network service can be distributed to the target network element, and the service processing efficiency and the accuracy are improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a cloud gateway provided in an embodiment of the present invention;
fig. 2 is a schematic flow chart of a service allocation method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of determining a target network element according to the present invention;
fig. 4 is a schematic structural diagram of a service distribution apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the application provides a service allocation method, a service allocation device, electronic equipment and a storage medium, wherein the service allocation method receives a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier; determining candidate services in preset network services according to the network element type identifier; determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service, for example, taking an idle network element or a non-idle network element as the target network element; then, determining a target service in the candidate services according to the target network element and a preset load balancing algorithm; and finally, sending the service resource of the target service to the target network element. The target network element is determined according to the bearing condition of the network service and the working state of the network element cluster, the appropriate network service can be distributed to the target network element, and the service processing efficiency and the accuracy are improved.
The service distribution method provided in the embodiment of the present application is applied to an edge cloud system, where the edge cloud system includes a cloud gateway, fig. 1 is a schematic structural diagram of the cloud gateway provided in the embodiment of the present application, and as shown in fig. 1, the cloud gateway includes a controller 12 and a network element 11. The network element 11 is installed in a hardware entity device (not shown in fig. 1) such as a filtering server or a deep packet inspection server, and is configured to implement functions such as network traffic analysis or forwarding. It should be noted that, in this embodiment, unless otherwise specified, the Network element 11 is a Virtual Network element (VNF), specifically, the Network element 11 may be a Data center Network element, an access Network element, a service Network element, and the like, where the Data center Network element may be a Data Center Switch (DCSW), the access Network element and the service Network element may be a Virtual Switch (vSwitch, Virtual Switch), and the like, and each of the Network elements belongs to a fixed Network element cluster.
To facilitate iteration and expansion, the controller 12 employs a micro-service architecture and provides mainly the following three types of network services:
Connection service: the configuration is issued to the network element 11 in a Google Remote Procedure Call (GRPC) manner, and a connection request of the network element 11 is received.
Collecting service: the receiving network element 11 receives a message sent by a User Datagram Protocol (UDP) and forwards the message to the card message queue.
It should be noted that the structural schematic diagram of the cloud gateway shown in fig. 1 is an example, the controller and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the occurrence of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
Fig. 2 is a flowchart of a service distribution method provided in an embodiment of the present application, where the service distribution method is applied to a cloud gateway, and an execution subject of the service distribution method is a controller 12 in the cloud gateway. As shown in fig. 2, the service allocation method includes:
210: receiving a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier;
specifically, when a certain traffic channel needs to be established, the idle network element needs to register with the controller 12, where one implementation manner is that the idle network element sends a registration request to the controller 12. The registration request carries an idle network element identifier, and the idle network element identifier includes a network element cluster identifier and a network element type identifier.
The idle network element identifier may be generated as a network element identifier when creating a network element, and is used to uniquely represent the network element, and network element identifiers of different network elements are different from each other. The network element identification comprises a first sub-identification and a second sub-identification.
Table 1 is a definition table of the first sub-identifier, and as shown in table 1, the first sub-identifier includes 8 bytes, which are sequentially referred to as byte 1, byte 2, byte 3, byte 4, byte 5, byte 6, byte 7, and byte 8 from top to bottom.
Table 1 definition table of first sub-id
In this embodiment, the number of the machine room may also be used as the network element cluster identifier, for example, a hexadecimal number FA00 is used to represent the number of a certain machine room, and then byte 1 and byte 2 of the first sub-identifier of the network element in all the hardware entity devices in the machine room are both set to be FA 00.
Byte 3, byte 4, byte 5, and byte 6 may be customized according to actual requirements, which is not specifically limited in this embodiment of the application.
Byte 7 is used to indicate the type of the network element, and it should be noted that the type of the network element may be divided according to its function, for example, the type of the network element includes a virtual switch, a virtual client device, and the like, where the virtual switch also includes a virtual access switch, a virtual service switch, and the like. As a specific example, the access virtual access switch is represented by a hexadecimal number 0x01, and byte 7 of the first sub-identifier of all network elements of which the type is the virtual access switch is set to 0x 01; using hexadecimal number 0x02 to represent the virtual service switch, byte 7 of the first sub-identifier of all network elements of which the type is the virtual service switch is set to be 0x 02; using the hexadecimal number 0x11 to represent the virtual client device, byte 7 of the first sub-identity of all network elements of type virtual client device is set to 0x 11.
Byte 8 is used to represent the number of the network element, and when the network element in any hardware entity device is numbered, the value of byte 8 is sequentially incremented, for example, if only 16 network elements exist in a certain hardware entity device and the types of the network elements are all virtual client devices, 16 integers from 0x01 to 0x10 are used to represent the number of 16 network elements respectively.
The second sub-identifier is a hexadecimal number corresponding to the management internet protocol address of the hardware entity device for installing the network element, the management internet protocol addresses of all the network elements in the same hardware entity device are the same, and the management internet protocol addresses of the network elements in different hardware entity devices are different from each other.
The network element identifier may be obtained by splicing the first sub-identifier and the second sub-identifier, for example, the first sub-identifier is spliced at the front and the second sub-identifier is spliced at the back. As a specific example, if the first sub-identifier of a certain network element is 11667788FFFF6601 hexadecimal number and the second sub-identifier is C0a80114 hexadecimal number, the network element is identified as 11667788FFFF6601C0a80114 hexadecimal number.
It should be noted that, the registration request may also carry a management internet protocol address and a port of the hardware entity device for installing the network element, in addition to the idle network element identifier of the idle network element.
If the controller 12 receives the registration request sent by the idle network element, the registration request may be analyzed to obtain the idle network element identifier of the idle network element carried in the registration request, and further obtain the network element type identifier carried in the idle network element identifier.
220: determining candidate services in preset network services according to the network element type identifier;
specifically, several network services, such as a connection service and an acquisition service, are built into the controller 12. When the controller 12 receives a registration request sent by an idle network element, it needs to prepare to allocate network services to the network element.
The types and the number of the network elements that can be carried by different network services may be the same or different, and in general, some network services can carry multiple types of network elements, some network services can only carry one type of network element, some network services can carry multiple network elements, and some network services can only carry one network element.
In this embodiment of the application, the cloud gateway presets a corresponding relationship between a network service and a type of a network element, and if the controller 12 receives a registration request sent by an idle network element, the registration request may be analyzed to obtain a network element identifier carried in the registration request, and further obtain a network element type identifier carried in the network element identifier and used for determining a target network element type, and then determine a candidate service among a plurality of preset network services based on the corresponding relationship between the network service and the type of the network element.
In an embodiment, the step of determining a candidate service among preset network services according to the network element type identifier includes:
calling a preset service bearing capacity table, wherein a service identifier corresponding to each network service, and a bearing type identifier and the number of network elements capable of bearing are stored in the service bearing capacity table in an associated manner;
sequentially judging whether the bearing type identification capable of being borne by each network service is consistent with the network element type identification;
and if so, determining the network service as the candidate service.
It should be noted that each network service is built in the controller 12, and after the network service is built, the network service needs to be registered, for example, the carrying capacity of the network service is stored in the service carrying capacity table, and after the network service is registered, the subsequent distribution can be performed. Specifically, a service carrying capacity table is stored in the database, and a service identifier corresponding to each network service, a carrying type identifier of a network element that can be carried, and a number are stored in the service carrying capacity table in an associated manner.
It should be noted that the service carrying capacity table specifically includes a connection service carrying capacity sub-table and a collection service carrying capacity sub-table, where the connection service carrying capacity sub-table corresponds to the connection service, and a service identifier corresponding to each connection service, and a type and a number of network elements that can be carried are stored in association with each other; the collection service bearing capacity sub-table corresponds to collection services, wherein service identification corresponding to each collection service, and types and number of network elements capable of bearing are stored in association.
If a certain network service is a connection service, after the network service is registered, the bearing capacity of the network service is stored in a connection service bearing capacity sub-table, and if a certain network service is an acquisition service, after the network service is registered, the bearing capacity of the network service is stored in an acquisition service bearing capacity sub-table.
230: determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service;
in an embodiment, as shown in fig. 3, the step of determining, according to the network element cluster identifier, the network element type identifier, and the candidate service, a target network element in a network element cluster corresponding to the network element cluster identifier includes:
310: calling the service bearing capacity table and a preset distributed service table, wherein the distributed service table is stored with service identification corresponding to each network service and network element identification of a loaded network element in a correlated manner;
320: judging whether the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements or not;
if the number of the network elements which can be loaded by the candidate service is equal to the number of the loaded network elements;
330: and determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
It should be noted that, before the step of determining whether the number of network elements that can be carried by the candidate service is greater than the number of network elements that have already been carried, the method further includes: and acquiring the number of the network elements carried by the candidate services according to the network element identifiers carried by the candidate services. Determining the network element identification carried by the candidate service by calling an allocated service table, so as to determine the number of the network elements carried by the candidate service according to the network element identification carried by the candidate service; it is convenient to determine whether the number of network elements that can be carried by the candidate service is greater than the number of network elements that have already been carried.
It can be understood that, when the number of network elements that can be carried by the candidate service is equal to the number of network elements that have already been carried, that is, the candidate service has reached the upper limit of the number of carrying network elements, at this time, the controller 12 has no resource or space to manage the idle network elements, and therefore, a non-idle network element in the network element cluster corresponding to the network element cluster identifier is determined as a target network element, where a target network element type identifier of the target network element is the same as the network element type identifier.
Specifically, if there is a step in which the number of network elements that can be carried by the candidate service is equal to the number of network elements already carried, the step of determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element includes:
determining candidate network elements in the network element cluster corresponding to the network element cluster identifier according to the network element type identifier, wherein the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
acquiring network element information reported by each candidate network element;
and determining a target network element in each candidate network element according to the network element information.
Specifically, a plurality of working network elements, that is, the non-idle network elements, exist in the network element cluster corresponding to the network element cluster identifier, and a candidate network element is determined from the non-idle network elements having the same type identifier as the network element type identifier according to the network element type identifier, obviously, the candidate network element is already loaded in the candidate service as the non-idle network element, that is, the network element identifier of the candidate network element is stored in the allocated service table, so that the number of network elements that can be loaded by the candidate service does not need to be considered.
Further, network element information reported by each candidate network element is obtained, where the network element information may include candidate network element identifiers, operation state information, and the like of the candidate network elements, and specifically, the operation state information may include data traffic information, resource occupation information, and the like of the candidate network elements, and a target network element is determined in each candidate network element according to the network element information, that is, a candidate network element with smaller processing data traffic or less resource occupation may be determined as the target network element according to the data traffic information and the resource occupation information in the operation state information; so that the target network element has enough space to carry new traffic.
As shown in fig. 3, the step of determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier, and the candidate service further includes:
340: if the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements, acquiring the number of idle network elements in the network element cluster corresponding to the network element cluster identifier;
350: judging whether the number of the idle network elements is larger than a preset idle network element threshold value or not;
if the number of the idle network elements is larger than the threshold value of the idle network elements;
360: and determining the idle network element as a target network element.
If the number of idle network elements is less than or equal to the idle network element threshold, referring to step 330:
and determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
It is understood that a standby network element, which may be the idle network element, is preset during the initial configuration of the network by the controller 12, and is used for the function expansion. The new traffic needs to be accessed or a part of the network elements need to be replaced when a fault occurs, and the like, so that idle network elements need to be reserved in each network element cluster, wherein the number of the reserved idle network elements is also a preset idle network element threshold, and the specific idle network element threshold can be set according to actual needs, which is not limited herein.
Specifically, if the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried, that is, the controller 12 has a carrying capability for the network element type corresponding to the network element type identifier, at this time, the number of idle network elements in the network element cluster corresponding to the network element cluster identifier is obtained, so as to determine whether the number of idle network elements is greater than a preset idle network element threshold value; when the number of the idle network elements is greater than the idle network element threshold value, that is, enough idle network elements are available, determining the idle network elements as target network elements; when the number of the idle network elements is less than or equal to the idle network element threshold, that is, the number of the idle network elements is less, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, and specifically, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element is described in the embodiment related to step 330, which is not described herein again, where a target network element type identifier of the target network element is the same as the network element type identifier.
240: determining a target service in the candidate services according to the target network element and a preset load balancing algorithm;
in particular, load balancing refers to the spreading of requests or data across several operating units for execution to collectively complete a work task with the goal of optimizing resource usage, maximizing throughput, and minimizing response time by scheduling clusters. Through a load balancing algorithm, a plurality of better target services can be determined from the candidate services corresponding to the target network element to be allocated to the target network element. The load balancing algorithm may be a polling method, a random method, a source address hashing method, a weighted polling method, a weighted random method, a minimum concatenation method, or the like.
It should be noted that the target service at least includes a connection service, or at least one collection service, or at least one connection service and at least one collection service.
250: and sending the service resource of the target service to the target network element.
Specifically, the service resource of the target service refers to a management internet protocol address and a port of the target service, and the controller 12 sends the management internet protocol address and the port of the target service to the target virtual network element, thereby completing the allocation of the network service.
In an embodiment, after the step of determining a target service among the candidate services according to the target network element and a preset load balancing algorithm, the method further includes storing a target network element identifier of the target network element in the allocated service table, and associating the target network element identifier with a service identifier of each target service.
Specifically, after determining the target service allocated to the target network element, the controller 12 stores the target network element identifier of the target network element in the allocated service table, and associates the target network element identifier with the service identifier of each target service in the allocated service table, so as to update the allocated service table, and ensure the accuracy of subsequent service allocation.
In an embodiment, before the step of receiving the registration request sent by the idle network element, different network services need to be set up in the controller 12, and the following data table is defined in the database, it should be noted that the services described in the following data table are all network services.
Service table: for storing service information such as service identification of the service, type of service, management internet protocol address of the service, port of the service and description information.
Virtual network element table: for storing virtual network element information, such as network element identification of the virtual network element, management internet protocol address of the virtual network element, port of the virtual network element, type and description information of the virtual network element.
Virtual network element type table: for storing virtual network element type information, such as the type of the virtual network element, the name and description information of the virtual network element.
Service carrying capacity table: the bearer capability information used for storing the service, such as the service identification of the service, the type of virtual network elements that can be carried by the service, the number of virtual network elements that can be carried by the service, and description information.
It should be noted that the service includes a connection service and/or an acquisition service, and correspondingly, the service carrying capacity table includes a connection service carrying capacity sub-table and/or an acquisition service carrying capacity sub-table, where the connection service carrying capacity sub-table is used to store carrying capacity information of the connection service, such as a service identifier of the connection service, a type of a network element that can be carried by the connection service, and a number and description information of the network elements that can be carried by the connection service; the collection service bearing capacity sub-table is used for storing bearing capacity information of the collection service, such as a service identifier of the collection service, a type of a network element that can be carried by the collection service, and a number and description information of the network elements that can be carried by the collection service.
Allocated services table: for storing allocated service information, such as a service identification of the service and a network element identification of a network element that the service has carried. It should be noted that, since the service includes a connection service and/or an acquisition service, the service identifier in the allocated service table specifically includes a service identifier of the connection service and/or a service identifier of the acquisition service.
When a new connection service or an acquisition service is added to the controller 12, the newly added service needs to be registered, that is, the bearer capability information of the service is stored in the service bearer capability table, specifically, if the newly added service is a connection service, the bearer capability information of the connection service is stored in the connection service bearer capability sub-table, and if the newly added service is an acquisition service, the bearer capability information of the acquisition service is stored in the acquisition service bearer capability sub-table. Optionally, the service information may also be stored in a service table.
The service allocation method provided by the embodiment of the application receives a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier; determining candidate services in preset network services according to the network element type identifier; determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service, for example, taking an idle network element or a non-idle network element as the target network element; then, determining a target service in the candidate services according to the target network element and a preset load balancing algorithm; and finally, sending the service resource of the target service to the target network element. The target network element is determined according to the bearing condition of the network service and the working state of the network element cluster, the appropriate network service can be distributed to the target network element, and the service processing efficiency and the accuracy are improved.
Correspondingly, the present application further provides a service distribution device, and fig. 4 is a schematic structural diagram of the service distribution device provided in the embodiment of the present application; referring to fig. 4, the service distribution apparatus includes the following modules:
a registration request receiving module 401, configured to receive a registration request sent by an idle network element, where the registration request carries an idle network element identifier, and the idle network element identifier includes a network element cluster identifier and a network element type identifier;
a candidate service determining module 402, configured to determine a candidate service among preset network services according to the network element type identifier;
a target network element determining module 403, configured to determine a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier, and the candidate service;
a target service determining module 404, configured to determine a target service among the candidate services according to the target network element and a preset load balancing algorithm;
a service resource sending module 405, configured to send the service resource of the target service to the target network element.
In an embodiment, the candidate service determining module 402 is further configured to invoke a preset service carrying capability table, where the service carrying capability table stores, in association with the service identifier corresponding to each network service, the carrying type identifier and the number of the network elements that can be carried;
sequentially judging whether the bearing type identification capable of being borne by each network service is consistent with the network element type identification;
and if so, determining the network service as the candidate service.
In an embodiment, the target network element determining module 403 is further configured to invoke the service carrying capability table and a preset allocated service table, where a service identifier corresponding to each network service and a network element identifier of a carried network element are stored in the allocated service table in an associated manner;
judging whether the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements or not;
and if the number of the network elements which can be carried by the candidate service is equal to the number of the carried network elements, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
In an embodiment, the target network element determining module 403 is further configured to, if the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried, obtain the number of idle network elements in the network element cluster corresponding to the network element cluster identifier;
judging whether the number of the idle network elements is larger than a preset idle network element threshold value or not;
if the number of the idle network elements is larger than the idle network element threshold value, determining the idle network elements as target network elements;
and if the number of the idle network elements is less than or equal to an idle network element threshold value, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
In an embodiment, the target network element determining module 403 is further configured to obtain, according to the network element identifier carried by each candidate service, the number of network elements carried by the candidate service.
In an embodiment, the target network element determining module 403 is further configured to determine, according to the network element type identifier, a candidate network element in a network element cluster corresponding to the network element cluster identifier, where the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
acquiring network element information reported by each candidate network element;
and determining a target network element in each candidate network element according to the network element information.
In an embodiment, the service resource sending module 405 is further configured to store a target network element identifier of the target network element in the allocated service table, and associate the target network element identifier with the service identifier of each of the target services.
Accordingly, an electronic device may include, as shown in fig. 5, a Radio Frequency (RF) circuit 501, a memory 502 including one or more computer-readable storage media, an input unit 503, a display unit 504, a sensor 505, an audio circuit 506, a Wireless Fidelity (WiFi) module 507, a central processor 508 including one or more processing cores, and a power supply 509. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 5 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some portions may be combined, or a different arrangement of components. Wherein:
the RF circuit 501 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information from a base station and then sends the received downlink information to one or more central processing units 508 for processing; in addition, data relating to uplink is transmitted to the base station. The memory 502 may be used to store software programs and modules, and the central processor 508 executes various functional applications and data processing by operating the software programs and modules stored in the memory 502. The input unit 503 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
The display unit 504 may be used to display information input by or provided to a user and various graphical user interfaces of the electronic device, which may be made up of graphics, text, icons, video, and any combination thereof.
The electronic device may also include at least one sensor 505, such as light sensors, motion sensors, and other sensors. The audio circuitry 506 includes speakers that can provide an audio interface between the user and the electronic device.
WiFi belongs to short-distance wireless transmission technology, and the electronic equipment can help a user to receive and send emails, browse webpages, access streaming media and the like through the WiFi module 507, and provides wireless broadband internet access for the user. Although fig. 5 shows the WiFi module 507, it is understood that it does not belong to the essential constitution of the electronic device, and may be omitted entirely as needed within the scope not changing the essence of the application.
The cpu 508 is a control center of the electronic device, connects various parts of the entire mobile phone by using various interfaces and lines, and executes various functions of the electronic device and processes data by operating or executing software programs and/or modules stored in the memory 502 and calling data stored in the memory 502, thereby integrally monitoring the mobile phone.
The electronic device also includes a power supply 509 (e.g., a battery) for powering the various components, which may preferably be logically connected to the central processor 508 via a power management system, such that the power management system may be used to manage charging, discharging, and power consumption.
Although not shown, the electronic device may further include a camera, a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, the central processing unit 508 in the electronic device loads the executable file corresponding to the process of one or more application programs into the memory 502 according to the following instructions, and the central processing unit 508 runs the application program stored in the memory 502, so as to implement the following functions:
receiving a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier;
determining candidate services in preset network services according to the network element type identifier;
determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service;
determining a target service in the candidate services according to the target network element and a preset load balancing algorithm;
and sending the service resource of the target service to the target network element.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description, and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, and the storage medium stores a plurality of instructions that can be loaded by a processor to implement the following functions:
receiving a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier;
determining candidate services in preset network services according to the network element type identifier;
determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service;
determining a target service in the candidate services according to the target network element and a preset load balancing algorithm;
and sending the service resource of the target service to the target network element.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the instructions stored in the storage medium can execute the steps in any method provided in the embodiments of the present application, the beneficial effects that can be achieved by any method provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The foregoing describes in detail a service allocation method, device, electronic device, and computer-readable storage medium provided in the embodiments of the present application, and specific examples are applied herein to explain the principles and implementations of the present application, and the descriptions of the foregoing embodiments are only used to help understand the method and core ideas of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method for service allocation, comprising:
receiving a registration request sent by an idle network element, wherein the registration request carries an idle network element identifier, and the idle network element identifier comprises a network element cluster identifier and a network element type identifier;
determining candidate services in preset network services according to the network element type identifier;
determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service;
determining a target service in the candidate services according to the target network element and a preset load balancing algorithm;
and sending the service resource of the target service to the target network element.
2. The method for allocating services according to claim 1, wherein the step of determining candidate services among the preset network services according to the network element type identifier comprises:
calling a preset service bearing capacity table, wherein a service identifier corresponding to each network service, and a bearing type identifier and the number of network elements capable of bearing are stored in the service bearing capacity table in an associated manner;
sequentially judging whether the bearing type identification capable of being borne by each network service is consistent with the network element type identification;
and if so, determining the network service as the candidate service.
3. The service allocation method according to claim 2, wherein the step of determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier and the candidate service includes:
calling the service bearing capacity table and a preset distributed service table, wherein the distributed service table is stored with service identification corresponding to each network service and network element identification of a loaded network element in a correlated manner;
judging whether the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements or not;
and if the number of the network elements which can be carried by the candidate service is equal to the number of the carried network elements, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
4. The service allocation method according to claim 3, wherein the step of determining a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier, and the candidate service further comprises:
if the number of the network elements which can be borne by the candidate service is larger than the number of the borne network elements, acquiring the number of idle network elements in the network element cluster corresponding to the network element cluster identifier;
judging whether the number of the idle network elements is larger than a preset idle network element threshold value or not;
if the number of the idle network elements is larger than the idle network element threshold value, determining the idle network elements as target network elements;
and if the number of the idle network elements is less than or equal to an idle network element threshold value, determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element, wherein the target network element type identifier of the target network element is the same as the network element type identifier.
5. The service allocation method according to claim 3, wherein before the step of determining whether the number of network elements that can be carried by the candidate service is greater than the number of already-carried network elements, the method further comprises:
and acquiring the number of the network elements carried by the candidate services according to the network element identifiers carried by the candidate services.
6. The service allocation method according to claim 3, wherein if there is a situation where the number of network elements that can be carried by the candidate service is equal to the number of network elements already carried, the step of determining a non-idle network element in the network element cluster corresponding to the network element cluster identifier as a target network element comprises:
determining candidate network elements in the network element cluster corresponding to the network element cluster identifier according to the network element type identifier, wherein the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
acquiring network element information reported by each candidate network element;
and determining a target network element in each candidate network element according to the network element information.
7. The method for allocating services according to claim 3, wherein after the step of determining the target service among the candidate services according to the target network element and a preset load balancing algorithm, the method further comprises:
and storing the target network element identification of the target network element in the allocated service table, and associating the target network element identification with the service identification of each target service.
8. A service distribution apparatus, comprising:
a registration request receiving module, configured to receive a registration request sent by an idle network element, where the registration request carries an idle network element identifier, and the idle network element identifier includes a network element cluster identifier and a network element type identifier;
a candidate service determining module, configured to determine a candidate service among preset network services according to the network element type identifier;
a target network element determining module, configured to determine a target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, the network element type identifier, and the candidate service;
a target service determining module, configured to determine a target service among the candidate services according to the target network element and a preset load balancing algorithm;
and the service resource sending module is used for sending the service resource of the target service to the target network element.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the service distribution method according to any one of claims 1 to 7 when executing the program.
10. A computer-readable storage medium storing instructions that can be loaded by a processor to perform the service distribution method of any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011385200.5A CN112565390B (en) | 2020-12-01 | 2020-12-01 | Service distribution method, device, electronic equipment and storage medium |
| PCT/CN2021/131448 WO2022116849A1 (en) | 2020-12-01 | 2021-11-18 | Service allocation method, apparatus, electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011385200.5A CN112565390B (en) | 2020-12-01 | 2020-12-01 | Service distribution method, device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112565390A true CN112565390A (en) | 2021-03-26 |
| CN112565390B CN112565390B (en) | 2022-05-31 |
Family
ID=75045947
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011385200.5A Active CN112565390B (en) | 2020-12-01 | 2020-12-01 | Service distribution method, device, electronic equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112565390B (en) |
| WO (1) | WO2022116849A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022116849A1 (en) * | 2020-12-01 | 2022-06-09 | 武汉绿色网络信息服务有限责任公司 | Service allocation method, apparatus, electronic device, and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116980420B (en) * | 2023-09-22 | 2023-12-15 | 新华三技术有限公司 | Cluster communication method, system, device, equipment and medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101431439A (en) * | 2008-12-02 | 2009-05-13 | 中兴通讯股份有限公司 | Resource data acquisition and leading-out system and method for network management system |
| US20140297805A1 (en) * | 2013-03-29 | 2014-10-02 | Alcatel-Lucent India Limited | Method and apparatus for assigning priority levels to streams by a network element in a communications network |
| CN105049240A (en) * | 2015-06-26 | 2015-11-11 | 大唐移动通信设备有限公司 | Message processing method and server |
| CN109040243A (en) * | 2018-08-02 | 2018-12-18 | 新华三信息安全技术有限公司 | A kind of message processing method and device |
| CN109842906A (en) * | 2017-11-28 | 2019-06-04 | 华为技术有限公司 | A kind of method, apparatus and system of communication |
| CN110620822A (en) * | 2019-09-27 | 2019-12-27 | 腾讯科技（深圳）有限公司 | Network element determination method and device |
| CN110661828A (en) * | 2018-06-28 | 2020-01-07 | 中移(苏州)软件技术有限公司 | Resource allocation method, device, server and readable storage medium |
| CN111356182A (en) * | 2018-12-21 | 2020-06-30 | 中兴通讯股份有限公司 | Resource scheduling and processing method and device |
| CN111555915A (en) * | 2020-04-24 | 2020-08-18 | 科大国创云网科技有限公司 | Dynamic network element control system based on plug-in configuration |
| CN111818158A (en) * | 2020-07-08 | 2020-10-23 | 京东方科技集团股份有限公司 | Gateway control method, device, electronic equipment and storage medium |
| CN111901135A (en) * | 2019-05-05 | 2020-11-06 | 华为技术有限公司 | Data analysis method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105551138A (en) * | 2015-12-08 | 2016-05-04 | 腾讯科技（深圳）有限公司 | Method and system for processing service voucher |
| WO2017125161A1 (en) * | 2016-01-21 | 2017-07-27 | Hewlett Packard Enterprise Development Lp | Resource allocation |
| US20200328977A1 (en) * | 2019-04-10 | 2020-10-15 | Cisco Technology, Inc. | Reactive approach to resource allocation for micro-services based infrastructure |
| CN112565390B (en) * | 2020-12-01 | 2022-05-31 | 武汉绿色网络信息服务有限责任公司 | Service distribution method, device, electronic equipment and storage medium |
-
2020
- 2020-12-01 CN CN202011385200.5A patent/CN112565390B/en active Active
-
2021
- 2021-11-18 WO PCT/CN2021/131448 patent/WO2022116849A1/en active Application Filing
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101431439A (en) * | 2008-12-02 | 2009-05-13 | 中兴通讯股份有限公司 | Resource data acquisition and leading-out system and method for network management system |
| US20140297805A1 (en) * | 2013-03-29 | 2014-10-02 | Alcatel-Lucent India Limited | Method and apparatus for assigning priority levels to streams by a network element in a communications network |
| CN105049240A (en) * | 2015-06-26 | 2015-11-11 | 大唐移动通信设备有限公司 | Message processing method and server |
| CN109842906A (en) * | 2017-11-28 | 2019-06-04 | 华为技术有限公司 | A kind of method, apparatus and system of communication |
| CN110661828A (en) * | 2018-06-28 | 2020-01-07 | 中移(苏州)软件技术有限公司 | Resource allocation method, device, server and readable storage medium |
| CN109040243A (en) * | 2018-08-02 | 2018-12-18 | 新华三信息安全技术有限公司 | A kind of message processing method and device |
| CN111356182A (en) * | 2018-12-21 | 2020-06-30 | 中兴通讯股份有限公司 | Resource scheduling and processing method and device |
| CN111901135A (en) * | 2019-05-05 | 2020-11-06 | 华为技术有限公司 | Data analysis method and device |
| CN110620822A (en) * | 2019-09-27 | 2019-12-27 | 腾讯科技（深圳）有限公司 | Network element determination method and device |
| CN111478981A (en) * | 2019-09-27 | 2020-07-31 | 腾讯科技（深圳）有限公司 | Network element determination method and device |
| CN111555915A (en) * | 2020-04-24 | 2020-08-18 | 科大国创云网科技有限公司 | Dynamic network element control system based on plug-in configuration |
| CN111818158A (en) * | 2020-07-08 | 2020-10-23 | 京东方科技集团股份有限公司 | Gateway control method, device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022116849A1 (en) * | 2020-12-01 | 2022-06-09 | 武汉绿色网络信息服务有限责任公司 | Service allocation method, apparatus, electronic device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022116849A1 (en) | 2022-06-09 |
| CN112565390B (en) | 2022-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11558346B2 (en) | Address management method and system, and device | |
| CN107135279B (en) | Method and device for processing long connection establishment request | |
| US20210092643A1 (en) | User plane resource management method, user plane network element, and control plane network element | |
| US11432137B2 (en) | Service notification method for mobile edge host and apparatus | |
| CN105049502B (en) | The method and apparatus that device software updates in a kind of cloud network management system | |
| CN112565390B (en) | Service distribution method, device, electronic equipment and storage medium | |
| WO2019012735A1 (en) | Ran slice resource management device and ran slice resource management method | |
| CN112653577A (en) | Network element management method, device and storage medium | |
| JP2021518955A (en) | Processor core scheduling method, equipment, terminals and storage media | |
| WO2014194704A1 (en) | A grouping processing method and system | |
| WO2023020432A1 (en) | Computing power request method, computing power allocation method, computing power execution method, and terminal and network-side device | |
| EP3972196B1 (en) | Virtual network function (vnf) deployment method and apparatus | |
| CN114616899A (en) | Terminal control apparatus and method | |
| CN116596202A (en) | Work order processing method, related device and storage medium | |
| CN113271228B (en) | Bandwidth resource scheduling method, device, equipment and computer readable storage medium | |
| CN110839296B (en) | Network resource scheduling method, device, storage medium and mobile terminal | |
| CN109426572B (en) | Task processing method and device and electronic equipment | |
| CN113596119A (en) | Edge capability distribution method, system, device and computer readable storage medium | |
| US20220272737A1 (en) | Method and apparatus for determining frequency domain resource | |
| CN106330785B (en) | Method and device for selecting service node | |
| CN108259391B (en) | Port configuration method and device | |
| CN112291340B (en) | Service distribution method, controller and virtual network element | |
| CN112995704B (en) | Cache management method and device, electronic equipment and storage medium | |
| CN109731345B (en) | Voice processing method and device, electronic equipment and storage medium | |
| CN114189436B (en) | Multi-cluster configuration deployment method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |