WO2022116849A1 - 服务分配方法、装置、电子设备及存储介质 - Google Patents

服务分配方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2022116849A1
WO2022116849A1 PCT/CN2021/131448 CN2021131448W WO2022116849A1 WO 2022116849 A1 WO2022116849 A1 WO 2022116849A1 CN 2021131448 W CN2021131448 W CN 2021131448W WO 2022116849 A1 WO2022116849 A1 WO 2022116849A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
service
identifier
network
target
Prior art date
Application number
PCT/CN2021/131448
Other languages
English (en)
French (fr)
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 WO2022116849A1 publication Critical patent/WO2022116849A1/zh

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

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a service distribution method, apparatus, electronic device and storage medium.
  • the cloud gateway is an important device in the edge cloud system, which includes a controller and a virtual network element (VNF, Virtualized Network Function).
  • VNF Virtualized Network Function
  • the virtual network element is a network element virtualized by virtualization technology to realize some specific functions.
  • the controller is used to manage virtual network elements, such as allocating network services to virtual network elements.
  • Embodiments of the present application provide a service allocation method, apparatus, electronic device, and storage medium, which are used to solve the technical problem that erroneous allocation often occurs when allocating network services to virtual network elements.
  • the embodiment of the present application provides a service allocation method, including:
  • the registration request carries an idle network element identifier
  • the idle network element identifier includes a network element cluster identifier and a network element type identifier
  • a candidate service is determined from the preset network services
  • the network element type identifier and the candidate service determine a target network element in the network element cluster corresponding to the network element cluster identifier
  • the step of determining a candidate service among preset network services according to the network element type identifier includes:
  • the network service is determined as the candidate service.
  • 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, network element type identifier and the candidate service includes:
  • the allocated service table is associated and stored with a service identifier corresponding to each of the network services and the network element identifier of the bearing network element;
  • the candidate service determines the non-idle network elements in the network element cluster corresponding to the network element cluster identifier as the target network element, wherein the The target network element type identifier of the target network element is the same as the network element type identifier.
  • the step of determining the target network element in the network element cluster corresponding to the network element cluster identifier according to the network element cluster identifier, network element type identifier and candidate service further includes:
  • the candidate service If the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried, acquiring the number of idle network elements in the network element cluster corresponding to the network element cluster identifier;
  • the non-idle network elements in the network element cluster corresponding to the network element cluster identifier as the target network element, wherein the target network element of the target network element
  • the network element type identifier is the same as the network element type identifier.
  • the method before the step of judging whether the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried, the method further includes:
  • the non-idle network elements in the network element cluster corresponding to the network element cluster identifier are determined as The steps of the target network element, including:
  • a candidate network element is determined in the network element cluster corresponding to the network element cluster identifier, and the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
  • a target network element is determined among the candidate network elements.
  • the method further includes:
  • the target network element identifier of the target network element is stored in the allocated service table, and is associated with the service identifier of each target service.
  • the present application also provides a service distribution device, comprising:
  • a registration request receiving module configured to receive 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 includes a network element cluster identifier and a network element type identifier;
  • a candidate service determination module configured to determine a candidate service among preset network services according to the network element type identifier
  • a target network element determination 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 determination module configured to determine a target service in the candidate services according to the target network element and a preset load balancing algorithm
  • a service resource sending module configured to send the service resource of the target service to the target network element.
  • the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the steps of the aforementioned service distribution method when the processor executes the program.
  • the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores a plurality of instructions, and the instructions can be loaded by a processor to execute the aforementioned service distribution method.
  • the present application provides a service allocation method, device, electronic device and 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, the idle network element identifier includes network element cluster identifier and network element type identifier; to determine candidate services in preset network services according to the network element type identifier; and according to the network element cluster identifier, network element identifier Type identifier and the candidate service, determine the target network element in the network element cluster corresponding to the network element cluster identifier, for example, take an idle network element or a non-idle network element as the target network element; then according to the target network element and In the preset load balancing algorithm, a target service is determined in the candidate services; finally, the service resources of the target service are sent to the target network element.
  • the target network element can be determined according to the bearing condition of the network service and the working state of the network element cluster, and an appropriate network service can be allocated to the target network
  • FIG. 1 is a schematic structural diagram of a cloud gateway provided by an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a service allocation method provided by an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of determining a target network element according to the present invention.
  • FIG. 4 is a schematic structural diagram of a service distribution apparatus provided by an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of an electronic device provided by an embodiment of the present invention.
  • Embodiments of the present application provide a service allocation method, apparatus, electronic device, and storage medium.
  • 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 identifiers include network element cluster identifiers and network element type identifiers; to determine candidate services in preset network services according to the network element type identifiers; and according to the network element cluster identifiers, network element type identifiers and all
  • the target network element is determined in the network element cluster corresponding to the network element cluster identifier, for example, an idle network element or a non-idle network element is used as the target network element; then according to the target network element and the preset load
  • a balancing algorithm is used to determine a target service in the candidate services; finally, the service resources of the target service are sent to the target network element.
  • the target network element can be determined according to the bearing condition of the network service and the working state of the network element cluster, and
  • FIG. 1 is a schematic structural diagram of the cloud gateway provided by the embodiment of the present application.
  • the cloud gateway includes a controller 12 and a cloud gateway.
  • Network element 11 is installed in a hardware entity device such as a filtering server or a deep packet inspection server (not shown in FIG. 1 ) to implement functions such as network traffic analysis or forwarding.
  • a hardware entity device such as a filtering server or a deep packet inspection server (not shown in FIG. 1 ) to implement functions such as network traffic analysis or forwarding.
  • the network element 11 is a virtual network element (VNF, Virtualized Network Function).
  • VNF Virtualized Network Function
  • the network element 11 may be a data center network element, an access network element element, service network element and other network elements, wherein the data center network element may be a data center switch (DCSW, Data center switches), and the access network element and the service network element may be a virtual switch (vSwitch, Virtual Switch), etc., each of the network elements belongs to a fixed network element cluster.
  • DCSW data center switch
  • vSwitch virtual switch
  • Virtual Switch Virtual Switch
  • the controller 12 adopts a micro-service architecture and mainly provides the following three types of network services:
  • Network element 11 registration and distribution service namely, providing a Hyper Text Transfer Protocol (HTTP) interface for the network element 11 to call for registration, and assigning network services to the network element 11, specifically, sending network services to the network element 11
  • HTTP Hyper Text Transfer Protocol
  • the service resource wherein the service resource is the management Internet Protocol (Internet Protocol, IP) address and port of the network service, and the allocated network service includes the connection service and the collection service.
  • IP Internet Protocol
  • Connection service send the configuration to the network element 11 through Google Remote Procedure Call (GRPC), and receive the connection request of the network element 11.
  • GRPC Google Remote Procedure Call
  • Collection service Receive the message sent by the network element 11 through the User Datagram Protocol (UDP) and forward it to the Kafka message queue.
  • UDP User Datagram Protocol
  • FIG. 1 the schematic structural diagram of the cloud gateway shown in FIG. 1 is an example, and the controllers and scenarios described in the embodiments of the present application are for the purpose of more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute an implementation of the present application.
  • the technical solutions provided in the examples those of ordinary skill in the art know that with the evolution of the system and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems. Each of them will be described in detail below. It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.
  • FIG. 2 is a flowchart of a service allocation method provided by an embodiment of the present application.
  • the service allocation method is applied to a cloud gateway, and the execution body of the service allocation method is the controller 12 in the cloud gateway.
  • the service allocation method includes:
  • 210 Receive 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 includes a network element cluster identifier and a network element type identifier;
  • the idle network element sends a registration request to the controller 12 .
  • the registration request carries idle network element identifiers
  • the idle network element identifiers include network element cluster identifiers and network element type identifiers.
  • the idle network element identifier as a network element identifier, may be generated when the network element is created, and is used to uniquely represent the network element, and the network element identifiers of different network elements are different from each other.
  • the network element identification includes a first sub-identity and a second sub-identity.
  • Table 1 is the definition table of the first sub-identity. As shown in Table 1, the first sub-identity includes 8 bytes, which are called byte 1, byte 2, byte 3, byte 4, word from high to bottom. Section 5, Byte 6, Byte 7, and Byte 8.
  • byte 1 and byte 2 are used to indicate the number of the computer room where the hardware entity equipment of the network element is installed.
  • the number of the computer room can also be used as the identifier of the network element cluster.
  • the system number FA00 represents the serial number of a certain equipment room, then the byte 1 and byte 2 of the first sub-identification of the network element in all the hardware physical devices in the equipment room are set to FA00.
  • Byte 3, Byte 4, Byte 5, and Byte 6 can be customized according to actual requirements, which are not specifically limited in this embodiment of the present application.
  • Byte 7 is used to indicate the type of network element.
  • the types of network elements can be divided according to their functions.
  • the types of network elements include virtual switches and virtual client devices.
  • virtual switches also include virtual switches. Access switches and virtual service switches, etc.
  • the byte 7 of the first sub-identification of all network elements whose type is a virtual access switch is set to 0x01; If the system number 0x02 represents a virtual service switch, then the byte 7 of the first sub-ID of all network elements of the type is set to 0x02; if the hexadecimal number 0x11 is used to represent a virtual client device, the type is virtual client Byte 7 of the first sub-identification of all network elements of the end device is set to 0x11.
  • Byte 8 is used to indicate the number of the network element. When the network element in any hardware entity device is numbered, the value of byte 8 increases sequentially. For example, there are only 16 network elements in a hardware entity device and all If the types are virtual client devices, 16 integers ranging from hexadecimal 0x01 to hexadecimal 0x10 are used to represent the numbers of the 16 NEs.
  • the second sub-identity is the hexadecimal number corresponding to the management internet protocol address of the hardware entity device where the network element is installed. All network elements in the same hardware entity device have the same management internet protocol address and are in different hardware entity devices. The managed Internet Protocol addresses of the network elements are different from each other.
  • the network element identification can be obtained by splicing the first sub-identity and the second sub-identity, for example, the first sub-identity is first, and the second sub-identity is spliced end to end. For example, if the first sub-ID of a certain network element is hexadecimal number 11667788FFFF6601, and the second sub-ID is hexadecimal number C0A80114, then the network element ID is hexadecimal number 11667788FFFF6601C0A80114.
  • the registration request may additionally carry the management Internet protocol address and port of the hardware entity device on which the network element is installed.
  • the controller 12 If the controller 12 receives the registration request sent by the idle network element, it can parse the registration request to obtain the idle network element identifier of the idle network element carried in the registration request, and then obtain the network element type identifier carried in the idle network element identifier. .
  • connection services and collection services are built in the controller 12 .
  • the controller 12 After the controller 12 receives the registration request sent by the idle network element, it needs to prepare to allocate network services to the network element.
  • Different network services can carry the same or different types and quantities of network elements.
  • some network services can carry multiple types of network elements, some network services can only carry one type of network elements, and some network services can carry multiple types of network elements. Carrying multiple network elements, some network services can only carry one network element.
  • the cloud gateway presets the correspondence between the network service and the type of network element. If the controller 12 receives the registration request sent by the idle network element, it can parse the registration request, and obtain the information contained in the registration request. and then obtain the network element type identifier carried in the network element identifier and used to determine the type of the target network element, and then based on the corresponding relationship between network services and network element types, determine candidate services from several preset network services. .
  • the step of determining a candidate service among preset network services according to the network element type identifier includes:
  • the network service is determined as the candidate service.
  • each network service is built in the controller 12. After the network service is built, the network service needs to be registered. For example, the bearing capacity of the network service is stored in the service bearing capacity table. After registration, subsequent assignments can be made. Specifically, the service bearer capability table is stored in the database, and the service bearer capability table stores the service identifier corresponding to each network service, the bearer type identifier and the number of network elements that can be carried in association with each other.
  • the service bearing capacity table specifically includes a connection service bearing capacity sub-table and a collection service bearing capacity sub-table, wherein the connection service bearing capacity sub-table corresponds to the connection service, and the service identifier corresponding to each connection service is associated and stored. , the type and quantity of the network elements that can be carried; the collection service carrying capacity sub-table corresponds to the collection service, wherein the service identifier corresponding to each collection service, the type and quantity of the network elements that can be carried are stored in association.
  • a certain network service is a connection service, after the registration of the network service is completed, the bearing capacity of the network service is stored in the connection service bearing capacity sub-table; if a service is a collection service, after the registration of the network service is completed, Then, the bearing capacity of the network service is stored in the collection service bearing capacity sub-table.
  • the target network element is determined 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. steps, including:
  • the step of judging whether the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried further includes: obtaining, according to the network element identifiers already carried by each candidate service, obtaining The number of network elements already carried by the candidate service. Determine the ID of the network element carried by the candidate service by invoking the allocated service table, so as to determine the number of network elements carried by the candidate service according to the ID of the network element carried by the candidate service; it is convenient to judge whether the candidate service can Whether the number of bearer network elements is greater than the number of bearer network elements.
  • the controller 12 has no resources or The space manages the idle network elements, therefore, the non-idle network elements in the network element cluster corresponding to the network element cluster identifier are determined as the target network element, wherein the target network element type identifier of the target network element is the same as the target network element.
  • the NE type identifiers described above are the same.
  • the non-idle network element in the network element cluster corresponding to the network element cluster identifier as the target network element steps, including:
  • a candidate network element is determined in the network element cluster corresponding to the network element cluster identifier, and the candidate network element type identifier of the candidate network element is the same as the network element type identifier;
  • a target network element is determined among the candidate network elements.
  • the candidate network element is determined from the non-idle network elements with the same type identifier as the element type identifier.
  • the candidate network element has been carried in the candidate service as a non-idle network element, that is, the network element identifier of the candidate network element. It is stored in the allocated service table, so the number of network elements that can be carried by the candidate service does not need to be considered.
  • the network element information may include the candidate network element identifier of the candidate network element and the running status information, etc.
  • the running status information may include the candidate network element According to the network element information, the target network element is determined in each candidate network element, that is, the processing can be processed according to the data flow information and resource occupation information in the running status information. The candidate network element with less data traffic or less resource occupation is determined as the target network element; so that the target network element can have enough space to carry new services.
  • 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, network element type identifier and candidate service further includes: :
  • step 330 If the number of idle network elements is less than or equal to the idle network element threshold, refer to step 330:
  • a non-idle network element in the network element cluster corresponding to the network element cluster identifier is determined 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.
  • a backup network element will be preset, and the backup network element may be the idle network element, which is used for expansion when the function needs to be expanded. It is necessary to access new traffic or replace some network elements when they fail. Therefore, idle network elements need to be reserved in each network element cluster. The number of reserved idle network elements is also the preset idle network element. Element threshold, the specific idle network element threshold can be set according to actual needs, which is not limited here.
  • the controller 12 still has the bearing capacity for the network element type corresponding to the network element type identifier.
  • the number of idle network elements in the network element cluster corresponding to the network element cluster identifier is convenient for judging whether the number of idle network elements is greater than a preset idle network element threshold; wherein, when the number of idle network elements is greater than When the idle network element threshold, that is, there are enough idle network elements, the idle network element is determined as the target network element; when the number of idle network elements is less than or equal to the idle network element threshold, that is, the idle network element is idle If there are few network elements, the non-idle network element in the network element cluster corresponding to the network element cluster identifier is determined as the target network element, and specifically the non-idle network element in the network element cluster corresponding to the network element cluster identifier is determined.
  • the step of being the target network element has been described in the embodiments
  • load balancing refers to allocating requests or data to several operation units for execution to jointly complete work tasks. The purpose is to optimize resource usage, maximize throughput and minimize response time by scheduling clusters.
  • the load balancing algorithm may be a round-robin method, a random method, a source address hash method, a weighted round-robin method, a weighted random method, or a least connection method.
  • the target service includes at least one connection service, or at least one collection service, or at least one connection service and at least one collection service.
  • the service resource of the target service refers to the management IP address and port of the target service
  • the controller 12 sends the management IP address and port of the target service to the target virtual network element, thereby completing the allocation of the network service.
  • the step further includes storing the target network element identifier of the target network element in a The assigned service table is associated with the service identifier of each target service.
  • the controller 12 stores the target network element identifier of the target network element in the allocated service table, and compares it with the service of each target service in the allocated service table The identifiers are associated to update the assigned service table to ensure the accuracy of subsequent service assignments.
  • the controller 12 before the step of receiving the registration request sent by the idle network element, the controller 12 needs to build different network services, and define the following data tables in the database. It should be noted that in the following data tables The services described are all network services.
  • Service table used to store service information, such as the service identifier of the service, the type of the service, the management Internet protocol address of the service, the port of the service and the description information.
  • Virtual network element table used to store virtual network element information, such as the network element identifier of the virtual network element, the management Internet protocol address of the virtual network element, the port of the virtual network element, and the type and description information of the virtual network element.
  • Virtual network element type table used to store virtual network element type information, such as virtual network element type, virtual network element name and description information.
  • Service bearer capability table used to store the bearer capability information of the service, such as the service identifier of the service, the type of virtual network elements that the service can bear, the number and description information of the virtual network elements that the service can bear.
  • the services include connection services and/or collection services
  • the service bearing capability table includes a connection service bearing capability sub-table and/or a collection service bearing capability sub-table, wherein the connection service bearing capability sub-table is used to store Bearing capacity information of the connection service, such as the service identifier of the connection service, the type of network elements that the connection service can bear, the number and description information of the network elements that the connection service can bear; the collection service bearing capacity sub-table is used to store the collection service The carrying capacity information of the collection service, such as the service identifier of the collection service, the type of network elements that the collection service can carry, and the number and description information of the network elements that the collection service can carry.
  • Allocated service table used to store allocated service information, such as the service identifier of the service and the network element identifier of the network element that the service has carried. It should be noted that, since the service includes the connection service and/or the collection service, the service identifier in the allocated service table specifically includes the service identifier of the connection service and/or the service identifier of the collection service.
  • the newly added service needs to be registered, that is, the bearing capacity information of the service is stored in the service bearing capacity table.
  • the bearing capacity information of the connection service is stored in the connection service bearing capacity sub-table, and if the newly added service is the collection service, the bearing capacity information of the collection service is stored in the collection service bearing capacity sub-table.
  • the service information can also be stored in the service table.
  • a registration request sent by an idle network element is received, wherein 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 ;
  • To determine candidate services in preset network services according to the network element type identification; and according to the network element cluster identification, network element type identification and the candidate service, in the network element cluster identification corresponding to Determine the target network element in the network element cluster for example, take the idle network element or the non-idle network element as the target network element; then according to the target network element and the preset load balancing algorithm, determine the target service in the candidate services; finally Send the service resource of the target service to the target network element.
  • the target network element can be determined according to the bearing condition of the network service and the working state of the network element cluster, and an appropriate network service can be allocated to the target network element, thereby improving the business processing efficiency and accuracy.
  • FIG. 4 is a schematic structural diagram of the service distribution apparatus provided by an embodiment of the present application; please refer 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, wherein 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 determination 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 determination module 404 configured to determine a target service in the candidate services according to the target network element and a preset load balancing algorithm
  • the service resource sending module 405 is configured to send the service resource of the target service to the target network element.
  • the candidate service determination module 402 is further configured to call a preset service bearing capability table, wherein the service bearing capability table stores the service identifier corresponding to each network service, Bearer type identification and quantity of the network element;
  • the network service is determined as the candidate service.
  • the target network element determining module 403 is further configured to call the service bearing capability table and the preset allocated service table, wherein the allocated service table is associated with each network.
  • the candidate service determines the non-idle network elements in the network element cluster corresponding to the network element cluster identifier as the target network element, wherein the The target network element type identifier of the target network element is the same as the network element type identifier.
  • the target network element determining module 403 is further configured to obtain the network element corresponding to the network element cluster identifier if the number of network elements that can be carried by the candidate service is greater than the number of network elements already carried. The number of idle network elements in the cluster;
  • the non-idle network elements in the network element cluster corresponding to the network element cluster identifier as the target network element, wherein the target network element of the target network element
  • the network element type identifier is the same as the network element type identifier.
  • the target network element determining module 403 is further configured to acquire the number of network elements carried by the candidate service according to the identifiers of the network elements carried by each candidate service.
  • the target network element determining module 403 is further configured to determine a candidate network element in the network element cluster corresponding to the network element cluster identifier according to the network element type identifier, and the candidate network element's The candidate network element type identifier is the same as the network element type identifier;
  • a target network element is determined among the candidate network elements.
  • the service resource sending module 405 is further configured to store the target network element identifier of the target network element in the allocated service table, and associate it with the service identifier of each target service. .
  • an embodiment of the present application further provides an electronic device, as shown in FIG. 5
  • the electronic device may include a radio frequency (RF, Radio Frequency) circuit 501, a memory 502 including one or more computer-readable storage media, Input unit 503, display unit 504, sensor 505, audio circuit 506, Wireless Fidelity (WiFi, Wireless Fidelity) module 507, CPU 508 including one or more processing cores, and power supply 509 and other components.
  • RF Radio Frequency
  • a memory 502 including one or more computer-readable storage media
  • WiFi Wireless Fidelity
  • the RF circuit 501 can be used for receiving and sending signals during the process of sending and receiving information or talking. In particular, after receiving the downlink information of the base station, it is handed over to one or more central processors 508 for processing; base station.
  • the memory 502 can be used to store software programs and modules, and the central processing unit 508 executes various functional applications and data processing by running the software programs and modules stored in the memory 502 .
  • the input unit 503 may be used to receive input numerical or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
  • the display unit 504 can be used to display information input by the user or information provided to the user and various graphical user interfaces of the electronic device, which can be composed of graphics, text, icons, videos, and any combination thereof.
  • the electronic device may also include at least one sensor 505, such as light sensors, motion sensors, and other sensors.
  • Audio circuitry 506 includes speakers that provide an audio interface between the user and the electronic device.
  • WiFi is a short-distance wireless transmission technology
  • the electronic device can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 507, which provides users with wireless broadband Internet access.
  • FIG. 5 shows the WiFi module 507, it can be understood that it is not a necessary component of the electronic device, and can be completely omitted as required within the scope of not changing the essence of the application.
  • the central processing unit 508 is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire mobile phone, by running or executing the software programs and/or modules stored in the memory 502, and calling the data stored in the memory 502. , perform various functions of electronic equipment and process data, so as to monitor the mobile phone as a whole.
  • the electronic device also includes a power supply 509 (such as a battery) that supplies power to various components.
  • a power supply 509 (such as a battery) that supplies power to various components.
  • the power supply can be logically connected to the central processing unit 508 through a power management system, so that functions such as managing charging, discharging, and power consumption management are implemented through the power management system. .
  • the electronic device may further include a camera, a Bluetooth module, and the like, which will not be repeated here.
  • the central processing unit 508 in the electronic device loads the executable files corresponding to the processes of one or more application programs into the memory 502 according to the following instructions, and the central processing unit 508 executes them.
  • the registration request carries an idle network element identifier
  • the idle network element identifier includes a network element cluster identifier and a network element type identifier
  • a candidate service is determined from the preset network services
  • the network element type identifier and the candidate service determine a target network element in the network element cluster corresponding to the network element cluster identifier
  • 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, and the instructions can be loaded by a processor to realize the following functions:
  • the registration request carries an idle network element identifier
  • the idle network element identifier includes a network element cluster identifier and a network element type identifier
  • a candidate service is determined from the preset network services
  • the network element type identifier and the candidate service determine a target network element in the network element cluster corresponding to the network element cluster identifier
  • the storage medium may include: a read-only memory (ROM, Read Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and the like.
  • ROM Read Only Memory
  • RAM Random Access Memory
  • magnetic disk or an optical disk and the like.

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

本申请实施例提供一种服务分配方法、装置、电子设备及存储介质，该服务分配方法通过接收空闲网元发送的携带有网元集群标识和网元类型标识的注册请求，以根据网元类型标识，在预置的网络服务中确定候选服务；并且根据网元集群标识、网元类型标识和候选服务，在网元集群标识所对应的网元集群中确定目标网元，然后根据目标网元和预设的负载均衡算法，在候选服务中确定目标服务；最后将目标服务的服务资源发送给目标网元；本申请实施例提供的服务分配方法能够根据网络服务的承载情况和网元集群的工作状态确定目标网元，并能为目标网元分配合适的网络服务，提高了业务处理效率和准确率。

Description

服务分配方法、装置、电子设备及存储介质 技术领域
本发明涉及通信技术领域，尤其涉及一种服务分配方法、装置、电子设备及存储介质。
背景技术
在第五代移动通信(5G，5th-Generation)网络建设的背景下，为充分利用其优势来获得更好的用户体验，各种就近满足用户需求的边缘云系统层出不穷。云网关为边缘云系统中的重要设备，其包括控制器和虚拟网元(VNF，Virtualized Network Function)，其中，虚拟网元是通过虚拟化技术虚拟出来的网元，用以实现一些特定的功能，控制器用于管理虚拟网元，例如为虚拟网元分配网络服务。
由于网络服务和虚拟网元的类型和数量众多，不同网络服务能承载虚拟网元的数量、类型或者类型的数量存在差异，目前，控制器在为虚拟网元分配网络服务时经常出现错误分配的情况，从而导致边缘云业务处理效率低且准确率低，特别的，控制器在为虚拟网元分配网络服务时当遇到网络服务承载虚拟网元的数量达到上限时会出现分配异常。
发明内容
本申请实施例提供一种服务分配方法、装置、电子设备及存储介质，用于解决在为虚拟网元分配网络服务时经常出现错误分配的技术问题。
为解决上述技术问题，本申请实施例提供以下技术方案：
本申请实施例提供一种服务分配方法，包括：
接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
根据所述网元类型标识，在预置的网络服务中确定候选服务；
根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群 标识所对应的网元集群中确定目标网元；
根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
将所述目标服务的服务资源发送给所述目标网元。
在一些实施例中，所述根据所述网元类型标识，在预置的网络服务中确定候选服务的步骤，包括：
调用预置的服务承载能力表，其中，所述服务承载能力表中关联存储有每一网络服务对应的服务标识、所能承载的网元的承载类型标识和数量；
依次判断各所述网络服务所能承载的承载类型标识与所述网元类型标识是否一致；
若一致，则将所述网络服务确定为所述候选服务。
在一些实施例中，所述根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元的步骤，包括：
调用所述服务承载能力表和预置的已分配服务表，其中，所述已分配服务表中关联存储有每一所述网络服务对应的服务标识和已承载的网元的网元标识；
判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量；
若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
在一些实施例中，所述根据所述网元集群标识、网元类型标识和候选服务，在所述网元集群标识所对应的网元集群中确定目标网元的步骤，还包括：
若所述候选服务所能承载的网元数量大于已承载的网元数量，则获取所述网元集群标识所对应的网元集群中的空闲网元的数量；
判断所述空闲网元的数量是否大于预设的空闲网元阈值；
若所述空闲网元的数量大于空闲网元阈值，则将所述空闲网元确定为目标网元；
若所述空闲网元的数量小于或等于空闲网元阈值，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标 网元类型标识与所述网元类型标识相同。
在一些实施例中，所述判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量的步骤之前，还包括：
根据各所述候选服务已承载的网元标识，获取所述候选服务已承载的网元数量。
在一些实施例中，所述若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元的步骤，包括：
根据所述网元类型标识，在所述网元集群标识所对应的网元集群中确定候选网元，所述候选网元的候选网元类型标识与所述网元类型标识相同；
获取各所述候选网元上报的网元信息；
根据所述网元信息，在各所述候选网元中确定目标网元。
在一些实施例中，所述根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务的步骤之后，还包括：
将所述目标网元的目标网元标识存储于所述已分配服务表中，且与每一所述目标服务的服务标识进行关联。
本申请还提供一种服务分配装置，包括：
注册请求接收模块，用于接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
候选服务确定模块，用于根据所述网元类型标识，在预置的网络服务中确定候选服务；
目标网元确定模块，用于根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
目标服务确定模块，用于根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
服务资源发送模块，用于将所述目标服务的服务资源发送给所述目标网元。
本申请还提供一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如前所述服务 分配方法的步骤。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有多条指令，该指令能够被处理器加载，执行如前所述的服务分配方法。
本申请的有益效果：本申请提供一种服务分配方法、装置、电子设备及存储介质，所述服务分配方法通过接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；以根据所述网元类型标识，在预置的网络服务中确定候选服务；并且根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元，例如将空闲网元或非空闲网元作为目标网元；然后根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；最后将所述目标服务的服务资源发送给所述目标网元。实现了根据网络服务的承载情况和网元集群的工作状态确定目标网元，并能为目标网元分配合适的网络服务，提高了业务处理效率和准确率。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的云网关的结构示意图；
图2为本发明实施例提供的服务分配方法的流程示意图；
图3为本发明确定目标网元的流程示意图；
图4为本发明实施例提供的服务分配装置的结构示意图；
图5为本发明实施例提供的电子设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳 动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本申请实施例提供一种服务分配方法、装置、电子设备及存储介质，所述服务分配方法通过接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；以根据所述网元类型标识，在预置的网络服务中确定候选服务；并且根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元，例如将空闲网元或非空闲网元作为目标网元；然后根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；最后将所述目标服务的服务资源发送给所述目标网元。实现了根据网络服务的承载情况和网元集群的工作状态确定目标网元，并能为目标网元分配合适的网络服务，提高了业务处理效率和准确率。
本申请实施例提供的服务分配方法应用于边缘云系统，边缘云系统包括云网关，图1为本申请实施例提供的云网关的结构示意图，如图1所示，云网关包括控制器12和网元11。其中，网元11安装于过滤服务器或深度报文检测服务器等硬件实体设备(图1未示出)中，用以实现网络流量分析或转发等功能。需要说明的是，本实施例中，如无特别说明，所述网元11为虚拟网元(VNF，Virtualized Network Function)，具体的，所述网元11可以是数据中心网元、接入网元、业务网元等网元，其中，所述数据中心网元可以是数据中心交换机(DCSW，Data center switches)，所述接入网元和所述业务网元可以是虚拟交换机(vSwitch，Virtual Switch)等，每一所述网元属于一固定的网元集群。
为了便于迭代与扩展，控制器12采用微服务架构且主要提供以下三类网络服务：
网元11注册与分配服务：即提供超文本传输协议(Hyper Text Transfer Protocol，HTTP)接口供网元11调用以进行注册，并为网元11分配网络服务，具体为向网元11发送网络服务的服务资源，其中，服务资源是网络服务的管理互联网协议(Internet Protocol，IP)地址和端口，所分配的网络服务包括连接服务和采集服务。
连接服务：通过Google远程过程调用(Google Remote Procedure Call，GRPC)方式向网元11下发配置，并接收网元11的连接请求。
采集服务：接收网元11通过用户数据报协议(User Datagram Protocol，UDP)发送的报文并将其转发至卡夫卡消息队列。
需要说明的是，图1所示的云网关的结构示意图是一个示例，本申请实施例描述的控制器以及场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。以下分别进行详细说明。需要说明的是，以下实施例的描述顺序不作为对实施例优选顺序的限定。
图2为本申请实施例提供的服务分配方法流程图，该服务分配方法应用于云网关，且该服务分配方法的执行主体为云网关中的控制器12。如图2所示，该服务分配方法包括：
210：接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
具体地，在需要建立某一流量通道时，需要通过空闲网元向控制器12进行注册，其中一种实现方式为空闲网元向控制器12发送注册请求。其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识。
所述空闲网元标识作为一种网元标识可以在创建网元时生成，用于唯一表示网元，不同的网元的网元标识彼此不同。网元标识包括第一子标识和第二子标识。
表1为第一子标识的定义表，如表1所示，第一子标识包括8个字节，从高到底依次称为字节1、字节2、字节3、字节4、字节5、字节6、字节7和字节8。
表1第一子标识的定义表
Figure PCTCN2021131448-appb-000001
其中，字节1和字节2用于表示安装网元的硬件实体设备所在的机房的编号，本实施例中，机房的编号也即可以作为所述网元集群标识，例如，使用十 六进制数FA00表示某个机房的编号，则该机房内所有的硬件实体设备中的网元的第一子标识的字节1和字节2均设置为FA00。
字节3、字节4、字节5、字节6可以根据实际需求进行自定义，本申请实施例对此不作具体限定。
字节7用于表示网元的类型，需要说明的是，网元的类型可以按照其功能进行划分，例如，网元的类型包括虚拟交换机和虚拟客户端设备等，其中，虚拟交换机还包括虚拟接入交换机和虚拟业务交换机等。举个具体的例子，使用十六进制数0x01表示接入虚拟接入交换机，则类型为虚拟接入交换机的所有网元的第一子标识的字节7均设置为0x01；使用十六进制数0x02表示虚拟业务交换机，则类型为虚拟业务交换机的所有网元的第一子标识的字节7均设置为0x02；使用十六进制数0x11表示虚拟客户端设备，则类型为虚拟客户端设备的所有网元的第一子标识的字节7均设置为0x11。
字节8用于表示网元的编号，在对任一硬件实体设备中的网元进行编号时，字节8的值顺序递增，例如，某一硬件实体设备中仅存在16个网元且其类型均为虚拟客户端设备，则分别使用十六进制数0x01到十六进制数0x10的16个整数分别表示16个网元的编号。
第二子标识为安装网元的硬件实体设备的管理互联网协议地址对应的十六进制数，处于同一硬件实体设备中的所有网元的管理互联网协议地址均相同，处于不同的硬件实体设备中的网元的管理互联网协议地址彼此不同。
网元标识具体可由第一子标识与第二子标识拼接得到，例如第一子标识在前，第二子标识在后的首尾拼接。举个具体的例子，若某一网元的第一子标识为十六进制数11667788FFFF6601，第二子标识为十六进制数C0A80114，则网元标识为十六进制数11667788FFFF6601C0A80114。
需要说明的是，注册请求中除了携带有空闲网元的空闲网元标识外，还可另外携带有安装网元的硬件实体设备的管理互联网协议地址和端口。
若控制器12接收到空闲网元发送的注册请求，则可以对注册请求进行解析，获得注册请求中携带的空闲网元的空闲网元标识，进而获得空闲网元标识中携带的网元类型标识。
220：根据所述网元类型标识，在预置的网络服务中确定候选服务；
具体地，控制器12中搭建有若干网络服务，例如连接服务和采集服务。当控制器12接收到空闲网元发送的注册请求后，需要准备为网元分配网络服务。
不同的网络服务可承载的网元的类型和数量可以相同或不同，通常情况下有些网络服务能够承载多种类型的网元，有些网络服务仅能承载一种类型的网元，有些网络服务能够承载多个网元，有些网络服务仅能承载一个网元。
在本申请实施例中，云网关预置有网络服务与网元的类型的对应关系，若控制器12接收到空闲网元发送的注册请求，则可以对注册请求进行解析，获得注册请求中携带的网元标识，进而获得网元标识中携带的用于确定目标网元类型的网元类型标识，然后基于网络服务与网元的类型的对应关系，在预置的若干网络服务中确定候选服务。
在一实施例中，所述根据所述网元类型标识，在预置的网络服务中确定候选服务的步骤，包括：
调用预置的服务承载能力表，其中，所述服务承载能力表中关联存储有每一网络服务对应的服务标识、所能承载的网元的承载类型标识和数量；
依次判断各所述网络服务所能承载的承载类型标识与所述网元类型标识是否一致；
若一致，则将所述网络服务确定为所述候选服务。
需要说明的是，每一网络服务均搭建于控制器12中，在网络服务搭建完毕后，该网络服务需要进行注册，例如将该网络服务的承载能力存储于服务承载能力表中，当网络服务注册完毕后，即可进行后续的分配。具体的，服务承载能力表存储于数据库中，所述服务承载能力表中关联存储有每一网络服务对应的服务标识、所能承载的网元的承载类型标识和数量。
需要说明的是，服务承载能力表具体包括连接服务承载能力子表和采集服务承载能力子表，其中，连接服务承载能力子表对应于连接服务，其中关联存储有每一连接服务对应的服务标识、所能承载的网元的类型和数量；采集服务承载能力子表对应于采集服务，其中关联存储有每一采集服务对应的服务标识、所能承载的网元的类型和数量。
若某一网络服务为连接服务，则该网络服务注册完毕后，将该网络服务的承载能力存储于连接服务承载能力子表中，若某一服务为采集服务，则该网络 服务注册完毕后，则将该网络服务的承载能力存储于采集服务承载能力子表中。
230：根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
在一实施例中，如图3所示，所述根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元的步骤，包括：
310：调用所述服务承载能力表和预置的已分配服务表，其中，所述已分配服务表中关联存储有每一所述网络服务对应的服务标识和已承载的网元的网元标识；
320：判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量；
若存在所述候选服务所能承载的网元数量等于已承载的网元数量；
330：将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
需要说明的是，所述判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量的步骤之前，还包括：根据各所述候选服务已承载的网元标识，获取所述候选服务已承载的网元数量。通过调用已分配服务表确定所述候选服务已承载的网元标识，从而根据所述候选服务已承载的网元标识确定所述候选服务已承载的网元数量；便于判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量。
可以理解的是，当所述候选服务所能承载的网元数量等于已承载的网元数量，也即是所述候选服务已达到承载网元数量的上限，此时，控制器12没有资源或空间纳管所述空闲网元，因此，将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
具体的，所述若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元的步骤，包括：
根据所述网元类型标识，在所述网元集群标识所对应的网元集群中确定候 选网元，所述候选网元的候选网元类型标识与所述网元类型标识相同；
获取各所述候选网元上报的网元信息；
根据所述网元信息，在各所述候选网元中确定目标网元。
具体的，所述网元集群标识所对应的网元集群中，存在多个正在工作的网元，也即是所述非空闲网元，根据所述网元类型标识，将具有与所述网元类型标识相同类型标识的非空闲网元中确定候选网元，显然，所述候选网元作为非空闲网元已承载在所述候选服务中，也即是所述候选网元的网元标识存储于所述已分配服务表中，因此，无需考虑所述候选服务所能承载的网元数量。
进一步的，获取各所述候选网元上报的网元信息，所述网元信息可以包括候选网元的候选网元标识和运行状态信息等，具体的，所述运行状态信息可以包括候选网元的数据流量信息和资源占用信息等，根据所述网元信息，在各所述候选网元中确定目标网元，也即是可以根据运行状态信息中的数据流量信息和资源占用信息，将处理数据流量较小或资源占用较少的候选网元确定为目标网元；以便于所述目标网元能有足够的空间承载新的业务。
承上，如图3所示，所述根据所述网元集群标识、网元类型标识和候选服务，在所述网元集群标识所对应的网元集群中确定目标网元的步骤，还包括：
340：若所述候选服务所能承载的网元数量大于已承载的网元数量，则获取所述网元集群标识所对应的网元集群中的空闲网元的数量；
350：判断所述空闲网元的数量是否大于预设的空闲网元阈值；
若所述空闲网元的数量大于空闲网元阈值；
360：将所述空闲网元确定为目标网元。
若所述空闲网元的数量小于或等于空闲网元阈值，则参照所述步骤330：
将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
可以理解的是，在控制器12对网络的初始化配置的过程中会预置备用网元，该备用网元可以是所述空闲网元，用于在功能需要拓展。需要接入新的流量或部分网元出现故障时进行替换等，因此，每一网元集群中都需要预留空闲网元，其中，预留空闲网元的数量也即是预设的空闲网元阈值，具体空闲网元阈值可以根据实际需要进行设置，在此不做限制。
具体的，若所述候选服务所能承载的网元数量大于已承载的网元数量，也即是控制器12对于所述网元类型标识所对应网元类型还有承载能力，此时，获取所述网元集群标识所对应的网元集群中的空闲网元的数量，便于判断所述空闲网元的数量是否大于预设的空闲网元阈值；其中，当所述空闲网元的数量大于空闲网元阈值时，也即是拥有足够的空闲网元，则将所述空闲网元确定为目标网元；当所述空闲网元的数量小于或等于空闲网元阈值时，也即是空闲网元较少，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，具体将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元的步骤已在步骤330相关的实施例中说明，在此不再赘述，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
240：根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
具体地，负载均衡指的是将请求或数据分摊到若干操作单元上进行执行以共同完成工作任务，其目的在于通过调度集群达到最佳化资源使用、最大化吞吐率和最小化响应时间。通过负载均衡算法，可以在目标网元对应的候选服务中确定若干较优的目标服务以分配给目标网元。其中，负载均衡算法可以为轮询法、随机法、源地址哈希法、加权轮询法、加权随机法或最小连接法等。
需要说明的是，所述目标服务至少包括一个连接服务，或至少一个采集服务，或至少一个连接服务和至少一个采集服务。
250：将所述目标服务的服务资源发送给所述目标网元。
具体地，目标服务的服务资源指的是目标服务的管理互联网协议地址和端口，控制器12将目标服务的管理互联网协议地址和端口发送给目标虚拟网元，从而完成网络服务的分配。
在一实施例中，所述根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务的步骤之后，还包括将所述目标网元的目标网元标识存储于所述已分配服务表中，且与每一所述目标服务的服务标识进行关联。
具体地，控制器12确定为目标网元分配的目标服务后，将目标网元的目标网元标识存储于已分配服务表中，并将其与已分配服务表中的每一目标服务的服务标识进行关联，从而对已分配服务表进行更新，保证后续服务分配的准确 性。
在一实施例中，在所述接收空闲网元发送的注册请求的步骤之前，控制器12中需要搭建不同的网络服务，并且在数据库中定义以下数据表，需要说明的是，以下数据表中所述的服务均为网络服务。
服务表：用于存储服务信息，例如服务的服务标识、服务的类型、服务的管理互联网协议地址、服务的端口和描述信息。
虚拟网元表：用于存储虚拟网元信息，例如虚拟网元的网元标识、虚拟网元的管理互联网协议地址、虚拟网元的端口、虚拟网元的类型和描述信息。
虚拟网元类型表：用于存储虚拟网元类型信息，例如虚拟网元的类型、虚拟网元的名称和描述信息。
服务承载能力表：用于存储服务的承载能力信息，例如服务的服务标识、服务所能承载的虚拟网元的类型、服务所能承载的虚拟网元的数量和描述信息。
需要说明的是，服务包括连接服务和/或采集服务，相应地，服务承载能力表包括连接服务承载能力子表和/或采集服务承载能力子表，其中，连接服务承载能力子表用于存储连接服务的承载能力信息，例如连接服务的服务标识、连接服务所能承载的网元的类型、连接服务所能承载的网元的数量和描述信息；采集服务承载能力子表用于存储采集服务的承载能力信息，例如采集服务的服务标识、采集服务所能承载的网元的类型、采集服务所能承载的网元的数量和描述信息。
已分配服务表：用于存储已分配服务信息，例如服务的服务标识和服务已承载的网元的网元标识。需要说明的是，由于服务包括连接服务和/或采集服务，因此已分配服务表中的服务标识具体包括连接服务的服务标识和/或采集服务的服务标识。
当控制器12中增加新的连接服务或采集服务时，新增的服务需要进行注册，即将服务的承载能力信息存储于服务承载能力表中，具体地，若新增的服务为连接服务，则将连接服务的承载能力信息存储于连接服务承载能力子表中，若新增的服务为采集服务，则将采集服务的承载能力信息存储于采集服务承载能力子表中。可选地，还可将服务信息存储于服务表中。
本申请实施例提供的服务分配方法，通过接收空闲网元发送的注册请求， 其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；以根据所述网元类型标识，在预置的网络服务中确定候选服务；并且根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元，例如将空闲网元或非空闲网元作为目标网元；然后根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；最后将所述目标服务的服务资源发送给所述目标网元。实现了根据网络服务的承载情况和网元集群的工作状态确定目标网元，并能为目标网元分配合适的网络服务，提高了业务处理效率和准确率。
相应的，本申请还提供一种服务分配装置，图4为本申请实施例提供的服务分配装置的结构示意图；请参阅图4，该服务分配装置包括以下模块：
注册请求接收模块401，用于接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
候选服务确定模块402，用于根据所述网元类型标识，在预置的网络服务中确定候选服务；
目标网元确定模块403，用于根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
目标服务确定模块404，用于根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
服务资源发送模块405，用于将所述目标服务的服务资源发送给所述目标网元。
在一实施例中，所述候选服务确定模块402还用于调用预置的服务承载能力表，其中，所述服务承载能力表中关联存储有每一网络服务对应的服务标识、所能承载的网元的承载类型标识和数量；
依次判断各所述网络服务所能承载的承载类型标识与所述网元类型标识是否一致；
若一致，则将所述网络服务确定为所述候选服务。
在一实施例中，所述目标网元确定模块403还用于调用所述服务承载能力 表和预置的已分配服务表，其中，所述已分配服务表中关联存储有每一所述网络服务对应的服务标识和已承载的网元的网元标识；
判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量；
若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
在一实施例中，所述目标网元确定模块403还用于若所述候选服务所能承载的网元数量大于已承载的网元数量，则获取所述网元集群标识所对应的网元集群中的空闲网元的数量；
判断所述空闲网元的数量是否大于预设的空闲网元阈值；
若所述空闲网元的数量大于空闲网元阈值，则将所述空闲网元确定为目标网元；
若所述空闲网元的数量小于或等于空闲网元阈值，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
在一实施例中，所述目标网元确定模块403还用于根据各所述候选服务已承载的网元标识，获取所述候选服务已承载的网元数量。
在一实施例中，所述目标网元确定模块403还用于根据所述网元类型标识，在所述网元集群标识所对应的网元集群中确定候选网元，所述候选网元的候选网元类型标识与所述网元类型标识相同；
获取各所述候选网元上报的网元信息；
根据所述网元信息，在各所述候选网元中确定目标网元。
在一实施例中，所述服务资源发送模块405还用于将所述目标网元的目标网元标识存储于所述已分配服务表中，且与每一所述目标服务的服务标识进行关联。
相应的，本申请实施例还提供一种电子设备，如图5所示，该电子设备可以包括射频(RF，Radio Frequency)电路501、包括有一个或一个以上计算机可读存储介质的存储器502、输入单元503、显示单元504、传感器505、音频 电路506、无线保真(WiFi，Wireless Fidelity)模块507、包括有一个或者一个以上处理核心的中央处理器508、以及电源509等部件。本领域技术人员可以理解，图5中示出的电子设备结构并不构成对电子设备的限定，可以包括比图示更多或更少的部件，或者组合某些部分，或者不同的部件布置。其中：
RF电路501可用于收发信息或通话过程中，信号的接受和发送，特别地，将基站的下行信息接收后，交由一个或者一个以上中央处理器508处理；另外，将涉及上行的数据发送给基站。存储器502可用于存储软件程序以及模块，中央处理器508通过运行存储在存储器502的软件程序以及模块，从而执行各种功能应用以及数据处理。输入单元503可用于接收输入的数字或字符信息，以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。
显示单元504可用于显示由用户输入的信息或提供给用户的信息以及电子设备的各种图形用户接口，这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。
电子设备还可包括至少一种传感器505，比如光传感器、运动传感器以及其他传感器。音频电路506包括扬声器，扬声器可提供用户与电子设备之间的音频接口。
WiFi属于短距离无线传输技术，电子设备通过WiFi模块507可以帮助用户收发电子邮件、浏览网页和访问流式媒体等，它为用户提供了无线的宽带互联网访问。虽然图5示出了WiFi模块507，但是可以理解的是，其并不属于电子设备的必须构成，完全可以根据需要在不改变申请的本质的范围内而省略。
中央处理器508是电子设备的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器502内的软件程序和/或模块，以及调用存储在存储器502内的数据，执行电子设备的各种功能和处理数据，从而对手机进行整体监控。
电子设备还包括给各个部件供电的电源509(比如电池)，优选的，电源可以通过电源管理系统与中央处理器508逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
尽管未示出，电子设备还可以包括摄像头、蓝牙模块等，在此不再赘述。 具体在本实施例中，电子设备中的中央处理器508会按照如下的指令，将一个或一个以上的应用程序的进程对应的可执行文件加载到存储器502中，并由中央处理器508来运行存储在存储器502中的应用程序，从而实现以下功能：
接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
根据所述网元类型标识，在预置的网络服务中确定候选服务；
根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
将所述目标服务的服务资源发送给所述目标网元。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见上文的详细描述，此处不再赘述。
本领域普通技术人员可以理解，上述实施例的各种方法中的全部或部分步骤可以通过指令来完成，或通过指令控制相关的硬件来完成，该指令可以存储于一计算机可读存储介质中，并由处理器进行加载和执行。
为此，本申请实施例提供一种计算机可读存储介质，其中存储有计算机程序，所述存储介质存储有多条指令，该指令能够被处理器加载，以实现以下功能：
接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
根据所述网元类型标识，在预置的网络服务中确定候选服务；
根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
将所述目标服务的服务资源发送给所述目标网元。
以上各个操作的具体实施可参见前面的实施例，在此不再赘述。
其中，该存储介质可以包括：只读存储器(ROM，Read Only Memory)、随机存取记忆体(RAM，Random Access Memory)、磁盘或光盘等。
由于该存储介质中所存储的指令，可以执行本申请实施例所提供的任一种方法中的步骤，因此，可以实现本申请实施例所提供的任一种方法所能实现的有益效果，详见前面的实施例，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
以上对本申请实施例所提供的一种服务分配方法、装置、电子设备及计算机可读存储介质进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (10)

  1. 一种服务分配方法，其特征在于，包括：
    接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
    根据所述网元类型标识，在预置的网络服务中确定候选服务；
    根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
    根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
    将所述目标服务的服务资源发送给所述目标网元。
  2. 根据权利要求1所述的服务分配方法，其特征在于，所述根据所述网元类型标识，在预置的网络服务中确定候选服务的步骤，包括：
    调用预置的服务承载能力表，其中，所述服务承载能力表中关联存储有每一网络服务对应的服务标识、所能承载的网元的承载类型标识和数量；
    依次判断各所述网络服务所能承载的承载类型标识与所述网元类型标识是否一致；
    若一致，则将所述网络服务确定为所述候选服务。
  3. 根据权利要求2所述的服务分配方法，其特征在于，所述根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元的步骤，包括：
    调用所述服务承载能力表和预置的已分配服务表，其中，所述已分配服务表中关联存储有每一所述网络服务对应的服务标识和已承载的网元的网元标识；
    判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量；
    若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
  4. 根据权利要求3所述的服务分配方法，其特征在于，所述根据所述网元集群标识、网元类型标识和候选服务，在所述网元集群标识所对应的网元集群 中确定目标网元的步骤，还包括：
    若所述候选服务所能承载的网元数量大于已承载的网元数量，则获取所述网元集群标识所对应的网元集群中的空闲网元的数量；
    判断所述空闲网元的数量是否大于预设的空闲网元阈值；
    若所述空闲网元的数量大于空闲网元阈值，则将所述空闲网元确定为目标网元；
    若所述空闲网元的数量小于或等于空闲网元阈值，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元，其中，所述目标网元的目标网元类型标识与所述网元类型标识相同。
  5. 根据权利要求3所述的服务分配方法，其特征在于，所述判断所述候选服务所能承载的网元的数量是否大于已承载的网元的数量的步骤之前，还包括：
    根据各所述候选服务已承载的网元标识，获取所述候选服务已承载的网元数量。
  6. 根据权利要求3所述的服务分配方法，其特征在于，所述若存在所述候选服务所能承载的网元数量等于已承载的网元数量，则将所述网元集群标识所对应的网元集群中非空闲网元确定为目标网元的步骤，包括：
    根据所述网元类型标识，在所述网元集群标识所对应的网元集群中确定候选网元，所述候选网元的候选网元类型标识与所述网元类型标识相同；
    获取各所述候选网元上报的网元信息；
    根据所述网元信息，在各所述候选网元中确定目标网元。
  7. 根据权利要求3所述的服务分配方法，其特征在于，所述根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务的步骤之后，还包括：
    将所述目标网元的目标网元标识存储于所述已分配服务表中，且与每一所述目标服务的服务标识进行关联。
  8. 一种服务分配装置，其特征在于，包括：
    注册请求接收模块，用于接收空闲网元发送的注册请求，其中，所述注册请求中携带有空闲网元标识，所述空闲网元标识包括网元集群标识和网元类型标识；
    候选服务确定模块，用于根据所述网元类型标识，在预置的网络服务中确定候选服务；
    目标网元确定模块，用于根据所述网元集群标识、网元类型标识和所述候选服务，在所述网元集群标识所对应的网元集群中确定目标网元；
    目标服务确定模块，用于根据所述目标网元和预设的负载均衡算法，在所述候选服务中确定目标服务；
    服务资源发送模块，用于将所述目标服务的服务资源发送给所述目标网元。
  9. 一种电子设备，其特征在于，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如权利要求1至7中任一项所述服务分配方法的步骤。
  10. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有多条指令，该指令能够被处理器加载，执行如权利要求1至7任一项所述的服务分配方法。
PCT/CN2021/131448 2020-12-01 2021-11-18 服务分配方法、装置、电子设备及存储介质 WO2022116849A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011385200.5A CN112565390B (zh) 2020-12-01 2020-12-01 服务分配方法、装置、电子设备及存储介质
CN202011385200.5 2020-12-01

Publications (1)

Publication Number Publication Date
WO2022116849A1 true WO2022116849A1 (zh) 2022-06-09

Family

ID=75045947

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/131448 WO2022116849A1 (zh) 2020-12-01 2021-11-18 服务分配方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN112565390B (zh)
WO (1) WO2022116849A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116980420A (zh) * 2023-09-22 2023-10-31 新华三技术有限公司 一种集群通信方法、系统、装置、设备及介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112565390B (zh) * 2020-12-01 2022-05-31 武汉绿色网络信息服务有限责任公司 服务分配方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105551138A (zh) * 2015-12-08 2016-05-04 腾讯科技（深圳）有限公司 服务凭证处理方法及系统
WO2017125161A1 (en) * 2016-01-21 2017-07-27 Hewlett Packard Enterprise Development Lp Resource allocation
CN110661828A (zh) * 2018-06-28 2020-01-07 中移(苏州)软件技术有限公司 一种资源分配方法、装置、服务器及可读存储介质
US20200328977A1 (en) * 2019-04-10 2020-10-15 Cisco Technology, Inc. Reactive approach to resource allocation for micro-services based infrastructure
CN112565390A (zh) * 2020-12-01 2021-03-26 武汉绿色网络信息服务有限责任公司 服务分配方法、装置、电子设备及存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431439A (zh) * 2008-12-02 2009-05-13 中兴通讯股份有限公司 一种网管系统中的资源数据采集导出系统及方法
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
CN105049240B (zh) * 2015-06-26 2018-08-21 大唐移动通信设备有限公司 一种消息处理方法及服务器
CN113891430A (zh) * 2017-11-28 2022-01-04 华为技术有限公司 一种通信的方法、装置及系统
CN109040243B (zh) * 2018-08-02 2021-04-30 新华三信息安全技术有限公司 一种报文处理方法及装置
CN111356182A (zh) * 2018-12-21 2020-06-30 中兴通讯股份有限公司 一种资源的调度、处理方法及装置
CN111901135B (zh) * 2019-05-05 2021-10-15 华为技术有限公司 一种数据分析方法及装置
CN110620822A (zh) * 2019-09-27 2019-12-27 腾讯科技（深圳）有限公司 一种网元确定方法和装置
CN111555915A (zh) * 2020-04-24 2020-08-18 科大国创云网科技有限公司 一种基于插件配置的动态网元控制系统
CN111818158B (zh) * 2020-07-08 2023-06-30 京东方科技集团股份有限公司 网关控制方法、装置、电子设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105551138A (zh) * 2015-12-08 2016-05-04 腾讯科技（深圳）有限公司 服务凭证处理方法及系统
WO2017125161A1 (en) * 2016-01-21 2017-07-27 Hewlett Packard Enterprise Development Lp Resource allocation
CN110661828A (zh) * 2018-06-28 2020-01-07 中移(苏州)软件技术有限公司 一种资源分配方法、装置、服务器及可读存储介质
US20200328977A1 (en) * 2019-04-10 2020-10-15 Cisco Technology, Inc. Reactive approach to resource allocation for micro-services based infrastructure
CN112565390A (zh) * 2020-12-01 2021-03-26 武汉绿色网络信息服务有限责任公司 服务分配方法、装置、电子设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116980420A (zh) * 2023-09-22 2023-10-31 新华三技术有限公司 一种集群通信方法、系统、装置、设备及介质
CN116980420B (zh) * 2023-09-22 2023-12-15 新华三技术有限公司 一种集群通信方法、系统、装置、设备及介质

Also Published As

Publication number Publication date
CN112565390B (zh) 2022-05-31
CN112565390A (zh) 2021-03-26

Similar Documents

Publication Publication Date Title
EP3886404B1 (en) Domain name server allocation method and device
CN110113441B (zh) 实现负载均衡的计算机设备、系统和方法
WO2022116849A1 (zh) 服务分配方法、装置、电子设备及存储介质
WO2017107018A1 (zh) 应用拓扑关系发现的方法、装置和系统
CN107135279B (zh) 一种处理长连接建立请求的方法和装置
US9742636B2 (en) Reliable address discovery cache
US11432137B2 (en) Service notification method for mobile edge host and apparatus
WO2020164476A1 (zh) 数据下载的方法及相关装置
CN112261094A (zh) 一种报文处理方法及代理服务器
WO2022100198A1 (zh) 数据传输方法、装置、存储介质、终端及网络接入点设备
WO2021170033A1 (zh) 一种网络配置方法及装置
CN109005071B (zh) 一种决策部署方法和调度设备
WO2023020432A1 (zh) 算力请求、算力分配、算力执行方法、终端及网络侧设备
WO2023016460A1 (zh) 计算任务的策略确定或资源分配方法、装置、网元及介质
WO2022100202A1 (zh) 数据下载方法、装置、存储介质及电子设备
CN110636149A (zh) 远程访问方法、装置、路由器及存储介质
CN113596119B (zh) 边缘能力分发方法、系统、设备及计算机可读存储介质
CN113271228B (zh) 带宽资源调度方法、装置、设备及计算机可读存储介质
KR101997602B1 (ko) 디바이스 양방향 ｍ２ｍ 리소스 관리 방법
CN113366814B (zh) 对边缘计算系统中的资源分配进行管理的方法
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
CN114024968A (zh) 一种基于中间设备的报文发送方法、装置和电子设备
CN112181605A (zh) 负载均衡方法、装置、电子设备和计算机可读介质
US20240095104A1 (en) Asynchronous communication in cluster infrastructures
CN106330785B (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: 21899883

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: 21899883

Country of ref document: EP

Kind code of ref document: A1