WO2016101639A1 - Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services - Google Patents

Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services Download PDF

Info

Publication number
WO2016101639A1
WO2016101639A1 PCT/CN2015/087807 CN2015087807W WO2016101639A1 WO 2016101639 A1 WO2016101639 A1 WO 2016101639A1 CN 2015087807 W CN2015087807 W CN 2015087807W WO 2016101639 A1 WO2016101639 A1 WO 2016101639A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
type
vnf
vnfd
providing device
Prior art date
Application number
PCT/CN2015/087807
Other languages
English (en)
Chinese (zh)
Inventor
李世涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2016101639A1 publication Critical patent/WO2016101639A1/fr

Links

Images

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method for connecting a load balancer, an exemplary deployment method, and a device.
  • Network Function Virtualization (English: Network Function Virtualization, NFV for short) uses the common hardware devices and virtualization technologies to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive cost of deploying dedicated devices. By decoupling hardware and software, network device functions are no longer dependent on dedicated hardware.
  • the party that can receive the virtualization request and perform the virtualization process on the corresponding service according to the request is generally referred to as a virtualization service provider (referred to as a service provider), and the party that initiates the virtualization request is generally referred to as a service requester.
  • the virtualized network service (English: Network Service, NS for short) can be a network service of the Internet Protocol Multimedia Subsystem (IMS) or a next-generation mobile core network. (English: Evolved Packet Core, referred to as: EPC) network services.
  • An NS may also contain several virtualized network function modules (English: Virtualized Network Function, VNF for short).
  • a module can also be included in a VNF, and a module can be called a VNFC (VNF component).
  • the VNF in the NS may need multiple instances according to the needs of the service.
  • the VNFC may also need multiple instances. Therefore, when the service is running, it is necessary to use the load balancing technology to select an instance of the VNF, so as to select an instance with a light load as the current service service.
  • VNF1 and VNF2 are interconnected.
  • Load Balancer (English: Load Balancer, LB for short) is a separate VNF that provides load balancing for instances of VNF2.
  • VNF2 instance 1, VNF2 instance 2, VNF2 instance 3 on the right are 3 instances of VNF2.
  • the LB is responsible for selecting the lighter instance to serve it.
  • the LB can be provided by the platform side.
  • the LB is set in the pair VNF1.
  • the LB can perform load balancing selection for multiple instances of the connected VNF2. Specifically, when VNF1 needs to send data to VNF2, VNF1 determines which instance of VNF2 is relatively lightly loaded according to its built-in LB, thereby directly transmitting data to the lightly loaded instance.
  • FIG. 1c it is an infrastructure-based load balancing model.
  • the infrastructure-based load balancing model is similar in architecture to peripheral load balancing.
  • the biggest difference is that the LB in the peripheral load balancing model ( Figure 1a) is a VNF, and the LB is mainly obtained through the interaction with the served VNF2.
  • LB is configured at the infrastructure layer, such as on a virtual switch on a virtual machine manager on a physical server, or on a proprietary physical device at the infrastructure layer. .
  • the LB in the model of Figure 1c can communicate directly with the virtual machine on the served VNF2 to learn the load of the served VNF2.
  • the embodiment of the present application provides a method for connecting a load balancer, and a method and an apparatus for deploying a service, which are used to solve the problem of how to determine the type of LB used in the prior art and how to connect the LB between instances of the VNF of the service.
  • Technical problem is a problem.
  • connection method of an LB including:
  • the service providing device receives an instantiation request for the service sent by the service requesting device;
  • the service providing device acquires network service description information NSD of the service according to the instantiation request;
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and Connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD includes description information for a load balancer LB type, and the second VNFD further includes the second Port capability information of the VNF;
  • the service providing device acquires information of an LB type supported by the service providing device
  • the service providing device acquires description information of the used LB of the LB type
  • the service providing device After receiving the response message that the first VNF and the second VNF are successfully instantiated, the service providing device sends the description information of the LB, the connection information, and the port capability information to the virtual basis.
  • a facility manager VIM configured to enable the VIM to connect the used LB type LB to the instance and location of the first VNF according to the description information of the LB, the connection information, and the port capability information Between the instances of the second VNF.
  • the service when the description information of the pair of LB types includes type information of the required LB, and each type of priority information, the service provides The device determines, according to the description information of the LB type and the information of the LB type supported by the service providing device, the type of the LB used, including:
  • the type information of the required LB is the type information of the LB of the first VNF requirement included in the first VNFD, or the type of the LB of the second VNF requirement included in the second VNFD. information.
  • the method further include:
  • the service providing device determines that there is no common LB type according to the type information of the required LB and the information of the LB type supported by the service providing device;
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • the service providing device obtains the description information of the LB of the used LB type, including:
  • the service providing device sends a request for querying an available LB instance of the peripheral LB type to the database; the service providing device uses the received address information of the available LB instance returned by the database as the description information of the LB; or
  • the service providing device sends a request for querying an available LB instance of the peripheral LB type to the database; the service providing device receives the virtual network function description information VNFD of the available LB instance returned by the database; the service providing device is configured according to The VNFD of the LB instance initiates a request for instantiating the peripheral LB to the virtual network function manager VNFM; the service providing device uses the received address information of the peripheral LB instance sent by the VNFM as the description information of the LB. .
  • the service providing device sends an LB instance of the peripheral LB type that is available for querying the database to the database.
  • the method further includes:
  • the service providing device determines that the description information of the LB type does not include the identifier information of the virtual network function description information VNFD of the peripheral LB type.
  • the service providing device obtains the description information of the LB of the used LB type, including:
  • the service providing device acquires the VNFD corresponding to the identifier information according to the identifier information;
  • the service providing device initiates a request for instantiating a peripheral LB according to the VNFD to the virtual network function manager VNFM;
  • the service providing device uses the received address information of the peripheral LB instance sent by the VNFM as the description information of the LB.
  • the service providing device acquires the description information of the LB of the used LB type, including:
  • the service providing device initiates, to the VIM, a request for allocating the LB of the LB type based on the infrastructure for the service;
  • the service providing device will receive the available infrastructure-based LB sent by the VIM
  • the address information is used as the description information of the LB.
  • the port capability information includes a port number of a port of the second VNF and function information of the port.
  • the second aspect of the present application provides an instantiation deployment method of a service, including:
  • the service requesting device sends an instantiation request for the service to the service providing device, where the instantiation request carries the identifier information of the network service description information NSD of the service or the NSD;
  • the NSD includes the first virtual network function First description information VNFD of the module VNF, second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD including the load Descriptor information of the equalizer LB type, the second VNFD further includes port capability information of the second VNF;
  • the service requesting device receives a response message that the instance of the service sent by the service providing device is successfully deployed.
  • the description information of the LB type includes the type information of the supported LB, the type information of the required LB, and the priority information of each type.
  • the type information of the required LB is type information of the LB of the first VNF requirement included in the first VNFD, or type information of the LB of the second VNF requirement included in the second VNFD
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • the port capability information includes a port number of the port of the second VNF, and the The function information of the port.
  • a third aspect of the present application provides a connection method of a load balancer, including:
  • the virtual infrastructure manager VIM receives a connection request sent by the service providing device, where the connection request includes an instance of the first virtual network function module VNF of the service and a description of the LB of the load balancer LB type used by the instance of the second VNF.
  • the VIM connects an instance of the first VNF to the LB according to the connection information and the description information of the LB, and associates the function information of the port with the function information of the port according to the function information of the port.
  • the interface is connected to a port of a corresponding function on the second VNF.
  • the method further includes:
  • the VIM receives a request sent by the service providing device to allocate the infrastructure-based LB for the service;
  • the VIM sends a request to allocate an infrastructure-based LB to an infrastructure layer according to the request to allocate the infrastructure-based LB for the service;
  • the VIM receives address information of an available infrastructure-based LB returned by the infrastructure layer;
  • the VIM sends the address information of the available infrastructure-based LB to the service providing device; wherein the description information of the LB includes the address information of the available infrastructure-based LB.
  • a fourth aspect of the present application provides a connection device for a load balancer, including:
  • a receiving unit configured to receive an instantiation request for a service sent by the service requesting device
  • a processing unit configured to acquire network service description information NSD of the service according to the instantiation request;
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and Connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD includes description information for a load balancer LB type, and the second VNFD further includes the second The port capability information of the VNF is obtained;
  • the information of the LB type supported by the device is obtained;
  • the type of the LB used is determined according to the description information of the LB type and the information of the LB type supported by the service providing device; and the location is obtained.
  • a sending unit configured to: after the receiving unit receives the response message that the first VNF and the second VNF are successfully instantiated, the description information of the LB, the connection information, and the port capability information Sending to the virtual infrastructure manager VIM, so that the VIM can connect the used LB type LB to the first VNF according to the description information of the LB, the connection information, and the port capability information. Between the instance of the second VNF and the instance of the second VNF.
  • the processing unit is specifically configured to: when the description information of the LB type is the type information of the required LB, and the priority of each type Level information,
  • the LB type is used as the LB type used; wherein the type information of the required LB is type information of the LB of the first VNF requirement included in the first VNFD, or the second VNFD Type information of the LB of the second VNF requirement included.
  • the processing unit is further configured to: when the description information of the LB type further includes the type information of the supported LB, according to the type information of the required LB and the LB type supported by the service providing device Determining that there is no common LB type; determining the type of the LB supported by the first VNF as the used LB type; wherein the type information of the supported LB is the first part included in the first VNFD Type information of a LB supported by a VNF.
  • the processing unit is specifically used to :
  • the type of LB used is a peripheral LB type
  • the processing unit is further configured to: send, by using the sending unit, a peripheral LB available for query to the database Before the request of the LB instance of the type, it is determined that the description information of the LB type does not include the identification information of the virtual network function description information VNFD of the peripheral LB type.
  • the description information of the LB type includes the identifier information of the virtual network function description information VNFD of the peripheral LB type; according to the identifier Obtaining, by the VNFD, the VNFD corresponding to the identifier information, and initiating, by the VNFD, a request for instantiating a peripheral LB to the virtual network function manager VNFM; and transmitting, by the receiving unit, the peripheral device sent by the VNFM
  • the address information of the LB instance is used as the description information of the LB.
  • the processing unit is specifically used to : when the used LB type is an infrastructure-based LB type, the sending unit sends a request to the VIM to allocate the LB type LB based on the infrastructure to the service; and The address information of the available infrastructure-based LB transmitted by the VIM received by the receiving unit is used as the description information of the LB.
  • the port capability information includes a port number of a port of the second VNF and function information of the port.
  • the fifth aspect of the present application provides an instantiation deployment device of a service, including:
  • a sending unit configured to send, to the service providing device, an instantiation request for the service, where the instantiation request carries the identifier information of the network service description information NSD of the service or the NSD;
  • the NSD includes the first virtual First description information VNFD of the network function module VNF, second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD includes The description information of the load balancer LB type, the second VNFD further includes port capability information of the second VNF;
  • a receiving unit configured to receive an instance deployment of the service sent by the service providing device Response message.
  • the description information about the LB type includes the type information of the supported LB, the type information of the required LB, and the priority information of each type.
  • the type information of the required LB is type information of the LB of the first VNF requirement included in the first VNFD, or type information of the LB of the second VNF requirement included in the second VNFD
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • the port capability information includes a port number of the port of the second VNF, and the The function information of the port.
  • a sixth aspect of the present application provides a connection device for a load balancer, including:
  • a receiving unit configured to receive a connection request sent by the service providing device, where the connection request includes an instance of the first virtual network function module VNF of the service and a description information of the LB of the load balancer LB type used by the instance of the second VNF, Connection information between the first VNF and the second VNF and port capability information of the second VNF, the port capability information including a port number of a port of the second VNF and function information of the port ;
  • a processing unit configured to connect an instance of the first VNF to the LB according to the connection information and the description information of the LB, and compare the function information of the LB with the port according to the function information of the port
  • the corresponding interface is connected to a port of a corresponding function on the second VNF.
  • the device further includes a sending unit,
  • the receiving unit is further configured to: when the LB type is an infrastructure-based LB type, Before receiving the connection request, the receiving unit receives a request sent by the service providing device to allocate the infrastructure-based LB for the service;
  • the processing unit is further configured to: send, according to the request for the infrastructure-based LB to the service, a request to allocate the infrastructure-based LB to an infrastructure layer;
  • the receiving unit is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
  • the sending unit is further configured to: send the address information of the available infrastructure-based LB to the service providing device, where the description information of the LB includes the address information of the available infrastructure-based LB .
  • the seventh aspect of the present application provides a service providing device, including:
  • a receiver configured to receive an instantiation request for a service sent by the service requesting device
  • a processor configured to acquire network service description information NSD of the service according to the instantiation request;
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and Connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD includes description information for a load balancer LB type, and the second VNFD further includes the second The port capability information of the VNF is obtained;
  • the information of the LB type supported by the device is obtained;
  • the type of the LB used is determined according to the description information of the LB type and the information of the LB type supported by the service providing device; and the location is obtained.
  • a transmitter configured to: after the receiver receives the response message that the first VNF and the second VNF are successfully instantiated, the description information of the LB, the connection information, and the port capability information Sending to the virtual infrastructure manager VIM, so that the VIM can connect the used LB type LB according to the description information of the LB, the connection information, and the port capability information. Between an instance of the first VNF and an instance of the second VNF.
  • the processor is specifically configured to: when the description information of the LB type is the type information of the required LB, and the priority of each type Level information,
  • the LB type is used as the LB type used; wherein the type information of the required LB is type information of the LB of the first VNF requirement included in the first VNFD, or the second VNFD Type information of the LB of the second VNF requirement included.
  • the processor is further configured to: when the description information of the LB type further includes a supported LB And determining, according to the type information of the required LB and the information of the LB type supported by the service providing device, that there is no common LB type; determining the type of the LB supported by the first VNF as the used LB
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • a third possible implementation manner of the seventh aspect when the type of LB used is a peripheral LB type,
  • the processor is further configured to: send, by using the sender, a peripheral LB available for query to the database Before the request of the LB instance of the type, it is determined that the description information of the LB type does not include the identification information of the virtual network function description information VNFD of the peripheral LB type.
  • a fifth possible implementation manner of the seventh aspect Determining, in the description information of the LB type, the identifier information of the virtual network function description information VNFD of the peripheral LB type; and obtaining the identifier information according to the identifier information.
  • the VNFD corresponding to the identification information; initiating a request for instantiating a peripheral LB according to the VNFD to the virtual network function manager VNFM; and transmitting a peripheral LB instance sent by the VNFM received by the receiver
  • the address information is used as the description information of the LB.
  • a sixth possible implementation manner of the seventh aspect when the used LB type is an infrastructure-based LB type, initiating, by the sender, a request to the VIM to allocate the LB type LB based on the infrastructure for the service;
  • the address information of the available infrastructure-based LB transmitted by the VIM received by the receiver is used as the description information of the LB.
  • the port capability information includes a port number of a port of the second VNF and function information of the port.
  • the eighth aspect of the present application provides a service requesting device for a service, including:
  • a sender configured to send an instantiation request for the service to the service providing device, where the instantiation request carries the identifier information of the network service description information NSD of the service or the NSD;
  • the NSD includes the first virtual First description information VNFD of the network function module VNF, second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF;
  • the first VNFD and/or the second VNFD includes The description information of the load balancer LB type, the second VNFD further includes port capability information of the second VNF;
  • a receiver configured to receive a response message that the instance of the service sent by the service providing device is successfully deployed.
  • the description information of the LB type includes the type information of the supported LB, the type information of the required LB, and the priority information of each type.
  • the type information of the required LB is type information of the LB of the first VNF requirement included in the first VNFD, or type information of the LB of the second VNF requirement included in the second VNFD
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • the port capability information includes a port number of the port of the second VNF, and the The function information of the port.
  • the ninth aspect of the present application provides a virtual infrastructure manager, including:
  • a receiver configured to receive a connection request sent by the service providing device, where the connection request includes an instance of the first virtual network function module VNF of the service and a load balancer used by the instance of the second VNF Descriptive information of the LB type LB, connection information between the first VNF and the second VNF, and port capability information of the second VNF, the port capability information including a port of the port of the second VNF Number and function information of the port;
  • a processor configured to connect an instance of the first VNF to the LB according to the connection information and the description information of the LB, and compare the function information of the LB with the port according to the function information of the port
  • the corresponding interface is connected to a port of a corresponding function on the second VNF.
  • the manager further includes a transmitter
  • the receiver is further configured to: when the LB type is an infrastructure-based LB type, before the receiver receives the connection request, receive, by the service providing device, the Infrastructure LB request;
  • the processor is further configured to: send a request for allocating the infrastructure-based LB to an infrastructure layer according to the request for the infrastructure-based LB to allocate the service;
  • the receiver is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
  • the transmitter is further configured to: send the address information of the available infrastructure-based LB to the service providing device, where the description information of the LB includes the address information of the available infrastructure-based LB .
  • the NSD includes the first description information VNFD of the first VNF, the second description information VNFD of the second VNF, and the first VNFD and/or the second VNFD includes description information about the type of the load balancer LB, and second.
  • the VNFD also includes port capability information for the second VNF;
  • the service providing device can determine the LB type used according to the description information of the LB type and the LB type information supported by the service providing device. Therefore, the type of LB used can be determined by the method of the present application.
  • the service providing device sends the description information of the LB of the LB type to the VIM, so that the VIM can use the LB of the LB type according to the connection information, the port capability information of the second VNF, and the description information of the LB. Connected between the instance of the first VNF and the instance of the second VNF.
  • the determined LB of the used LB type can also be connected between instances of the VNF by the method of the present application.
  • 1a-1c are schematic diagrams of a load balancing model in the prior art
  • FIG. 2 is a schematic diagram of an LB connection between VNFs in an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for connecting an LB according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for connecting a first example LB according to an embodiment of the present application
  • FIG. 5 is a flowchart of a method for connecting a second example LB according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for connecting a third example LB according to an embodiment of the present disclosure
  • FIG. 7 is a functional block diagram of a connection apparatus of a first example LB according to an embodiment of the present disclosure.
  • FIG. 8 is a system block diagram of a service providing device according to an embodiment of the present application.
  • FIG. 9 is a functional block diagram of an instantiation deployment apparatus of a service according to an embodiment of the present application.
  • Figure 10 is a system block diagram of a service requesting device provided by an embodiment of the present application.
  • FIG. 11 is a functional block diagram of a connection apparatus of a second example LB according to an embodiment of the present disclosure.
  • FIG. 12 is a system block diagram of a VIM according to an embodiment of the present application.
  • An embodiment of the present application provides a method for connecting a load balancer, and a method and an apparatus for deploying a service, to solve the problem of how to determine the type of LB used in the prior art and how to connect the LB between the instances of the VNF of the service. technical problem.
  • FIG. 2 is a schematic diagram of a scenario in which an LB is connected between two instances of a VNF in the embodiment of the present application.
  • the VNF1 is referred to as the first VNF in the embodiment of the present application.
  • VNF2 is referred to as a second VNF in the embodiment of the present application.
  • the LB in FIG. 2 may be, for example, a peripheral LB, an infrastructure based LB, or an end-to-end LB.
  • the LB in FIG. 2 is an end-to-end LB, the LB belongs to a part of VNF1.
  • the LB in FIG. 2 may also be other types of LBs, which is not specifically limited in this application.
  • two VNFs of the first VNF and the second VNF are taken as an example, but in actual application, one NS may include more than two VNFs, so two or more VNFs are used.
  • the processing manner of any two VNFs having a connection relationship may be the same as the processing manner of processing the connection relationship between the first VNF and the second VNF, so how to determine between the first VNF and the second VNF will be described in detail below.
  • the type of LB used and how the determined LB of the used LB type is connected between the instance of the first VNF and the instance of the second VNF.
  • a flowchart of a method for connecting a load balancer includes the following content:
  • Step 101 The service providing device receives an instantiation request for the service sent by the service requesting device.
  • Step 102 Acquire network service description information of the service according to the instantiation request (English: Network Service Descriptor, referred to as NSD).
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF.
  • the first VNFD and/or the second VNFD include descriptive information for the LB type.
  • the second VNFD also includes port capability information for the second VNF.
  • the port capability information includes a port number of a port of the second VNF and function information of the port.
  • Step 103 The service providing device acquires information of an LB type supported by the service providing device.
  • Step 104 The service providing device determines the used LB type according to the description information of the LB type and the information of the LB type supported by the service providing device.
  • Step 105 The service providing device acquires description information of the used LB of the LB type.
  • Step 106 After the service providing device receives the response message that the first VNF and the second VNF are successfully instantiated, the description information, the connection information, and the port capability information of the LB are sent to the virtual infrastructure manager.
  • Infrastructure Manager for enabling the VIM to connect the used LB type LB to the first VNF instance and the second VNF according to the connection information, the port capability information, and the description information of the LB. Between instances.
  • the service providing device may correspond to a network function virtualization service provider (NFVO).
  • NFVO network function virtualization service provider
  • the service requesting device can correspond to the network function virtualization service requester.
  • a service requester is, for example, a carrier network, such as an operational support and billing system.
  • the NSD can be described by using various specifications, such as a topology and an operation specification (English: Topology and Orchestration Specification for Cloud Applications, TOSCA).
  • the first method described is as follows:
  • the description information is another TOSCA specification of a language version of the Yet Another Markup Language (YAML) language.
  • two nodes are included, which respectively correspond to two VNFs.
  • Node 1 corresponds to the first VNF of the connection.
  • Node 2 corresponds to the second VNF being connected.
  • the minimum number of instantiations supported by the node 2 is 3, and it is known that the node 2 has a requirement to deploy multiple instances at the time of deployment. So you need to use LB between node 1 and node 2.
  • Capabilities is a description of the capability information of node 1.
  • Loadbalance is a new capability information of the present invention, which is used to represent the load balancing model supported by node 1.
  • E2E indicates that node 1 supports an end-to-end load balancing model (as shown in Figure 1b). Balance model). This model can be used to provide an end-to-end LB for connected nodes 2.
  • the requirement parameter contains the requirement information of the node 1, where connect: Node 2, indicating that the node 1 needs to be connected with the node 2, that is, the connection information between the first VNF and the second VNF.
  • the class: 1" code segment represents a further requirement for the connection between node 1 and node 2.
  • the Loadbalance parameter is a new parameter of the present invention and is used to indicate that the connection between node 1 and the node is load balanced. The requirements of the model.
  • the class parameter is used to indicate the priority level of the corresponding load balancing model. For example, in this embodiment, “external” is the peripheral load balancing model (as shown in Figure 1a).
  • the load balancing model has the highest priority, and the end-to-end load balancing model has the lowest priority.
  • the description information of the LB type includes the type information of the LB of the first VNF requirement included in the first VNFD or the second The type information of the LB of the second VNF requirement included in the VNFD, and the priority information of each type.
  • the description information of the LB type further includes type information of the LB supported by the first VNF included in the first VNFD.
  • the capabilities parameter in the description information of the node 2 defines the capability information of the node 2.
  • the capability information of the port is defined.
  • the capability information defines information about the externally exposed connection point on node 2, that is, other nodes can be connected to the node through the port.
  • two connection points are defined, one is the port number 253, and the supported protocol is the Transmission Control Protocol (English: Transmission Control Protocol, TCP for short).
  • the parameter usage is a newly added parameter of the invention and is used to indicate the purpose of the port 253.
  • port 253 can be used to connect to a load balancer.
  • the protocol used by the other port is Hypertext Transfer Protocol (English: Hypertext transfer protocol, HTTP), and the port number is 254.
  • port 254 can be used to connect to the service. data.
  • the second VNFD includes port capability information of the second VNF, such as a port number of the port, function information of the port, a transmission protocol supported by the port, and the like.
  • the scalable parameter defines the number of instances needed to instantiate the deployment of node 2, where "Min_instance” defines the minimum number of instantiations, and "Max_instance” defines the maximum number of instantiations.
  • a second method of describing the NSD can be:
  • the second description method described above is also the TOSCA specification of the YAML language version.
  • the description of the node 1 is different from the previous description method in that the load balance parameter is added to the capability parameter, and the class parameter is added under the load balance parameter to indicate that the node 1 supports The priority level of the load balancing model.
  • the value of class is 1, indicating that the corresponding E2E model has the lowest priority.
  • the first VNFD includes type information of the LB supported by the first VNF and priority information of each type.
  • a new Loadbalance parameter is added under the requirements parameter to indicate the requirement of node 2 for the load balancing model. This need is a requirement put forward by the virtual service providing device, that is, what kind of load balancer is desired by the virtual service providing device.
  • the class of the infrastructure model indicated in node 2 is "2", and the class of the external model is "3".
  • the second VNFD includes type information of the LB of the second VNF demand, and priority information of each type.
  • NSD also includes other information, such as NSD identification information, manufacturer, version number, resiliency strategy, lifecycle management, deployment preferences, and so on. These information are well known to those skilled in the art and will not be described here.
  • the service providing device acquires the NSD of the service according to the instantiation request.
  • the instantiation request carries the NSD of the service, so the service providing device can obtain the NSD by analyzing the instantiation request.
  • the method further includes: receiving, by the service providing device An on-boarding request for the service sent by the service requesting device, in which the NSD of the service is carried.
  • the service providing device sends the NSD information to a database for storage. After the data is saved, the database returns a save success response to the service provider.
  • the service providing device sends a registration success response to the service requesting device.
  • the instantiation request carries the identification information of the NSD.
  • the step 102 includes: the service providing device acquires the NSD corresponding to the identifier information from the database according to the identifier information of the NSD carried in the instantiation request.
  • the service providing device receives the NSD returned by the database, by querying the saved NSD according to the identification information.
  • the deployment method corresponding to the instantiation of a service provided on the service requesting device side includes: the service requesting device sends an instantiation request for the service to the service providing device; wherein the instantiated request carries the NSD of the service Identification information or the NSD.
  • step 103 is performed, that is, the service providing device acquires information of the LB type supported by the service providing device.
  • the information of the LB type supported by the service providing device is, for example, stored in a storage unit, and the service providing device is obtained by querying.
  • step 104 is performed, that is, the service providing device determines the used LB type according to the description information of the LB type and the information of the LB type supported by the service providing device.
  • the step 103 includes: the service providing device provides the type information and service provision of the LB according to the requirement.
  • the information of the LB type supported by the device determines whether there is a common LB type; if yes, the service providing device determines, according to the priority information, the LB type with the highest priority among the common LB types as the used LB type.
  • the type information of the required LB is the type information of the LB of the first VNF requirement included in the first VNFD, or the type information of the LB of the second VNF requirement included in the second VNFD.
  • the virtual service provider supports both the peripheral type and the infrastructure-based type of load balancing module. type.
  • the common LB type determined by the service providing device is a peripheral type and an infrastructure based type.
  • the LB of the peripheral type has the highest priority, and the service providing device determines that the peripheral type is the LB type used.
  • the method further includes: the service providing device determines that there is no common LB type according to the type information of the required LB and the information of the LB type supported by the service providing device; the service providing device determines the type of the supported LB as The type of LB used.
  • the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  • the virtual service providing device supports neither the peripheral type nor the infrastructure-based type of load balancing model, it is determined that the E2E type is the used LB type.
  • the virtual service providing device does not provide any load balancer, and the E2E type load balancer is used between the node 1 and the node 2, that is, the LB carried by the node 1 is used.
  • step 105 is performed, that is, the service providing device acquires description information of the LB of the used LB type.
  • the specific implementation of step 104 is also different according to the determined type of LB used, which will be respectively exemplified below.
  • step 105 includes: the service providing device sends a request to the database to query the available LB instance of the peripheral LB type; if there is, the database returns the address of the available LB instance.
  • the information correspondingly, the service providing device uses the address information of the available LB instance returned by the received database as the description information of the LB.
  • the description information of the LB may further include other information, such as information about a maximum processing capacity of the LB (such as the number of connectable instances), processing time, and the like.
  • the available LB instance refers to an LB instance that can be used at the time of the query, for example, an LB instance in an idle state.
  • the database when the database does not have an available LB instance, the database returns the virtual network function description information VNFD of the available LB instance.
  • the method further includes: the service providing device receives the VNFD of the available LB instance returned by the database.
  • the service providing device initiates a request for instantiating the peripheral LB according to the VNFD of the LB instance to the virtual network function manager (English: Virtualized Network Function Manager, VNFM for short); the service providing device will receive the peripheral device sent by the VNFM.
  • the address information of the LB instance is used as the description information of the LB.
  • the VNFD of the LB instance needs to be included in the request for instantiating the peripheral LB.
  • the service providing device obtains the address information of the instance of the peripheral LB. As the description information of the LB.
  • the service requesting device may register the VNFD of the LB of the peripheral type to the service providing device before the initiation of the instantiation request of the service.
  • the description information of the LB type further includes the identifier information of the VNFD. Therefore, in consideration of the situation, before the service providing device queries the database for an available LB instance of the peripheral LB type, the method further includes: the service providing device determines that the description information of the LB type does not include the Identification information of the peripheral LB type VNFD. In other words, the request to query the available LB instance of the peripheral LB type is sent to the database without registering the VNFD in advance.
  • step 105 includes: the service providing device according to the The identifier information acquires a VNFD corresponding to the identifier information; the service providing device initiates a request for instantiating the peripheral LB according to the VNFD to the VNFM; the service providing device uses the received address information of the peripheral LB instance sent by the VNFM as the location Describe the description information of LB. Among them, instantiation The request of the peripheral LB includes the VNFD.
  • the step 105 specifically includes: the service providing device initiates, to the VIM, a request for allocating an infrastructure-based LB for the service; and the service providing device sends the received VIM.
  • the address information of the available infrastructure-based LB is used as the description information of the LB.
  • VIM virtual resource management
  • the service providing device can use the interface to send resource management requests to the VIM, such as resource allocation, resource query, resource update, resource migration, and resource release.
  • the interface is more to provide management of VNF resources in the service, such as allocating resources for a VNF and updating and releasing resources.
  • the VIM needs to allocate an infrastructure-based load balancer, and does not allocate load balancer resources for the VNF itself, so it needs to be provided in the service.
  • a new interface is used between the device and the VIM to pass the load balancer's allocation request.
  • a new interface name can be defined as an "infrastructure based load balancer management" interface.
  • the interface is used by the service providing device to apply for an infrastructure load balancer based operation to the VIM, such as applying for a new load balancer, updating the load balancer, balancing the load balancer, and deleting the load balancer.
  • the new interface is used to allocate a new load balancer to the VIM.
  • the VIM After the VIM receives the allocation request, it requests the infrastructure layer to allocate the infrastructure-based LB. The infrastructure layer then returns the address information of the available infrastructure-based LB to the VIM. The VIM then returns the address information to the service providing device. The service providing device then uses the address information as the description information of the LB.
  • step 104 step 105 is not required to be performed, and in step 106, after receiving the response message that both the first VNF and the second VNF are successfully instantiated, the service providing device will connect the information. And port capability information is sent to VIM.
  • the VIM first requests the infrastructure layer to allocate the infrastructure-based LB.
  • the infrastructure layer then returns the address information of the available infrastructure-based LB to the VIM.
  • the VIM then connects the LB between the instance of the first VNF and the instance of the second VNF based on the address information, connection information, and port capability information of the LB.
  • the step 105 includes: the service providing device acquiring, in the first VNFD, description information of the LB of the E2E type LB.
  • step 106 After obtaining the description information of the used LB of the LB type in step 105, and after receiving the response message that both the first VNF and the second VNF are successfully instantiated, step 106 is performed next, that is, the service providing device will
  • the description information of the LB is sent to the VIM, so that the VIM can connect the used LB type LB to the instance of the first VNF and the instance of the second VNF according to the connection information, the port capability information, and the description information of the LB. between.
  • the VIM receives a connection request sent by the service providing device, and includes, in the connection request, information sent by the service providing device in step 106. Based on the connection information, the VIM knows that the first VNF and the second VNF need to be connected, so the instance of the first VNF is connected to the LB.
  • the VIM further connects the interface corresponding to the function information of the port on the LB to the port corresponding to the function on the second VNF according to the port capability information of the second VNF. For example, the interface on the LB for transmitting load detection is connected to the port on the second VNF whose usage is loadbalance.
  • LB The data interface sent by the first VNF is connected to the port whose "usage" is "data" on the second VNF.
  • the VIM sends a response message to the service providing device to complete the connection.
  • the service providing device After receiving the response message that the connection is completed, the service providing device sends an instantiation completion response to the service requesting device. Correspondingly, the service requesting device receives the instantiation completion response.
  • the LB type used can be determined during the deployment process of the instantiation of the service, and the LB of the LB type used is connected between the instances of the two VNFs. .
  • FIG. 4 is a flowchart of a method for connecting a load balancer in this embodiment.
  • the method includes the following.
  • Step 201 The service requesting device sends an on boarding request for the service to the virtual service providing device.
  • the request contains the NSD for the service.
  • step 202 is performed: after the service providing device receives the registration request, the NSD in the request is sent to the database for saving.
  • Step 203 After the database is saved, return a save success response to the service providing device.
  • Step 204 After receiving the save success response sent by the database, the service providing device sends a registration success response to the service requesting device.
  • Step 205 The service requesting device initiates an instantiation request for the service to the service providing device.
  • the request carries the identification information corresponding to the NSD of the service.
  • Step 206 The service providing device acquires the NSD from the database according to the identifier information of the NSD.
  • Step 207 The database queries the NSD according to the NSD identification information, and returns the NSD to the service providing device.
  • Step 208 The service providing device analyzes the NSD, and initiates a process of instantiating the request according to the NSD to the node 1 and the node 2. Specifically, the service providing device sends a request for instantiating the node 1 to the virtual network function manager (English: Virtualised Network Function Manager, VNFM for the node 1). The VNFD identity of node 1 is included in the request. The VNFM queries the database for the VNFD of the node 1 based on the identity of the VNFD. The database then returns the VNFD to the VNFM after querying the VNFD of Node 1. The VNFM applies for resources to the service provisioning device according to the VNFD.
  • VNFM Virtualised Network Function Manager
  • the resources include the central processing unit (English: Central Processing Unit, CPU for short) resources and storage resources required by the node 1.
  • the service providing device sends a resource request request to the VIM, and the VIM is required to allocate the corresponding resource to the node 1.
  • VIM applies for the required resources to the Network Functions Virtualization Infrastructure (NFVI) layer. After confirming the successful allocation of resources, NFVI returns information such as the address of the resource.
  • the VIM provides the device with the service confirmation that the resource allocation is successful, and returns information such as the address of the resource.
  • the service providing device confirms that the resource allocation is successful to the VNFM, and returns information such as the address of the resource.
  • the VNFM creates an instance of Node 1 at the assigned address based on the allocated resources.
  • the service providing device determines that node 1 is instantiated successfully. Then repeat the above steps to instantiate node 2.
  • the instantiation process for Node 1 and Node 2 is well known to those skilled in the art, and therefore will not
  • Step 209 The service providing device determines the description information related to the load balancing model included in the NSD.
  • the peripheral load balancing model has the highest priority (class 3 in the foregoing description, so the priority is the highest), and the cloud platform where the service providing device is also supports the peripheral load balancing model, then the peripheral is determined.
  • the type of LB acts as the LB between the instance of node 1 and the instance of node 2.
  • Step 210 The service providing device sends an instance of the peripheral load balancer that is available to the database to query whether the cloud platform is located.
  • Step 211 If there is an instance of the available peripheral load balancer queried, the database returns information such as the address of the instance to the service providing device. Returns available peripherals if no instances are available The description of the load balancer, which is the VNFD of the peripheral load balancer.
  • Step 212 If the database returns the VNFD of the peripheral load balancer, the service providing device uses the VNFD to initiate a request to the VNFM to instantiate a corresponding peripheral LB instance.
  • the VNFD is carried in the request.
  • Step 213 The service providing device receives the address information of the peripheral LB instance returned by the VNFM.
  • Step 214 After both node 1 and node 2 are instantiated, the service providing device requests the VIM to establish a connection between the VNFs, that is, the connection between node 1 and node 2. A connection between the instance of Node 2 and the Peripheral Load Balancer instance is also established. The address information, connection information, and port capability information of the peripheral LB instance are included in the request.
  • the instance of node 1 is first connected to an instance of the load balancer, and the load balancer is connected to multiple instances of node 2.
  • the interface for transmitting load detection on the load balancer is connected to the "Endpoint” where the "usage” is “Loadbalance” on the node 2, and the data interface sent by the forwarding node 1 on the load balancer is the same as the node 2
  • the usage is connected to the "Endpoint” of "data”.
  • Step 215 After the establishment is completed, the VIM sends a completion response to the service providing device.
  • Step 216 The service providing device sends an instantiation completion response to the service requesting device.
  • the service requesting device sets the peripheral load balancing model with the highest priority.
  • the peripheral load balancing is provided for the service during the deployment process. Device.
  • the peripheral type of load balancer is provided by the requesting party. Therefore, the requesting party registers the VNFD of the peripheral type load balancer to the virtual service providing device before initiating the registration request. And when the service is instantiated, carrying the identification information of the VNFD of the load balancer, indicating that the load balancer needs to be used.
  • the virtual service providing device finds the VNFD of the corresponding LB according to the identification information of the VNFD in the request, and instantiates the instance of the load balancer by using the VNFD of the corresponding LB, and uses the instance to provide a load balancing function for the requested service.
  • FIG. 5 is a flowchart of a method for connecting a load balancer in this embodiment. The method includes the following.
  • Step 301 The service requesting device initiates a request to register the LB.
  • the registration request carries the VNFD of the LB.
  • the composition and components of the LB are provided by the service requesting device.
  • the LB123 is the identifier of the node template, that is, the identifier information of the VNFD.
  • the node template is a node of the load balancer type.
  • Step 302 The service providing device sends the received VNFD to the database for storage.
  • Step 303 The database sends a save completion response to the service providing device after the saving is completed.
  • Step 304 The service providing device sends a registration completion response to the service requesting device.
  • Step 305 The service requesting device initiates a registration request of the network service.
  • the NSD included in the request information is basically the same as in the first example. The difference is that under the "external" load balancer requirements
  • the identification information of the VNFD of the load balancer is added. If the first description in step 201 is used, it can be:
  • This parameter carries the identification information of the VNFD of an "external" type load balancer, that is, LB123.
  • the identification information corresponds to the VNFD of the load balancer that needs to be saved in the database in step 301.
  • the next step is basically the same as the first example.
  • the difference is that the service providing device needs to determine the load balancer corresponding to the identification information of the VNFD as the load balancer of the network service. Therefore, the service providing device needs to request the VNFD corresponding to the identifier information according to the identification information of the VNFD, that is, “LB123”.
  • the database is sent to the service providing device after querying the VNFD.
  • the service providing device uses the VNFD to initiate a process of instantiating the load balancer to the VNFM.
  • the next steps are the same as the first example and will not be described here.
  • the service requesting device sets the infrastructure-based load balancing model with the highest priority.
  • an infrastructure-based load balancer is provided for the service during deployment.
  • FIG. 6 is a flowchart of a load balancing connection method in this embodiment. The method includes the following.
  • Step 401 is basically the same as step 201, except that in the NSD, the class of the "infrastructure" type is set to "3", that is, the load balancing model based on the infrastructure has the highest priority.
  • Steps 402 to 408 are substantially the same as steps 201 to 208, and details are not described herein again.
  • Step 409 Since it is assumed that the service providing device also supports the infrastructure-based LB, the LB type is determined to be an infrastructure-based LB according to the demand information in the NSD.
  • Step 410 The service providing device initiates a request to the VIM, and selects an infrastructure based on the current service. The type of LB applied.
  • Step 411 The VIM requests the infrastructure layer to allocate a load balancer.
  • Step 412 The infrastructure layer returns information such as the address of the infrastructure-based load balancer to the VIM.
  • Step 413 The VIM returns information such as an address of the infrastructure-based load balancer to the service providing device.
  • Step 414 The service providing device requests the VIM to connect between the VNF instances. This includes the connection of the relevant VNF in the business to the selected infrastructure-based load balancer.
  • the instance of node 1 is first connected to the load balancer.
  • the load balancer is then connected to multiple instances of node 2.
  • the interface on the load balancer for transmitting load detection is connected to the Endpoint where the usage is "Loadbalance" on node 2.
  • the data interface sent by the forwarding node 1 on the load balancer is connected to the "Endpoint" whose "usage" is "data” on the node 2.
  • Step 415 The VIM completes the establishment of the connection, and returns a completion response to the service providing device.
  • Step 416 The service providing device returns an instantiation completion response to the service requesting device.
  • FIG. 7 is a functional block diagram of a connection device of an LB according to an embodiment of the present application.
  • the apparatus is for implementing a connection method of the LB as described in FIG. 3 and its embodiments. As shown in FIG. 7
  • the connection apparatus includes: a receiving unit 501, configured to receive an instantiation request for a service sent by a service requesting device, and a processing unit 502, configured to acquire a network service description information NSD of the service according to the instantiation request;
  • the first description information VNFD of the first virtual network function module VNF, the second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF are included;
  • the first VNFD and/or the second VNFD include a load
  • the description information of the equalizer LB type, the second VNFD further includes the port capability information of the second VNF; the information of the LB type supported by the device is obtained; and the information is determined according to the description information of the LB type and the information of the LB type supported by the service providing device.
  • the sending unit 503 is used to receive the order
  • the 501 sends the description information, the connection information, and the port capability information of the LB to the virtual infrastructure manager VIM, so that the VIM can be based on the description information of the LB.
  • the connection information and the port capability information connect the LB of the LB type used between the instance of the first VNF and the instance of the second VNF.
  • the processing unit 502 is specifically configured to: when the description information of the LB type is the type information of the required LB, and the priority information of each type,
  • the type information of the LB of the required VNF is the type information of the LB of the first VNF requirement included in the first VNFD, or the type information of the LB of the second VNF requirement included in the second VNFD.
  • the processing unit 502 is further configured to: when the description information of the LB type further includes the type information of the supported LB, determine that the type information of the LB according to the requirement and the information of the LB type supported by the service providing device are not common.
  • LB type determining the type of the LB supported by the first VNF as the LB type used; wherein the type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD .
  • the processing unit 502 is specifically configured to: when the used LB type is a peripheral LB type,
  • the address information of the available LB instance returned by the database received by the receiving unit 501 is used as the description information of the LB; or
  • the receiving unit 501 Receiving, by the receiving unit 501, the virtual network function description information VNFD of the available LB instance returned by the database; initiating instantiation to the virtual network function manager VNFM according to the VNFD of the LB instance
  • the request of the LB is set; the address information of the peripheral LB instance sent by the VNFM received by the receiving unit 501 is used as the description information of the LB.
  • the processing unit 502 is further configured to: before sending, by the sending unit 503, a request for querying an available LB instance of the peripheral LB type to the database, determining that the description information of the LB type does not include the virtual network of the peripheral LB type.
  • Function description information VNFD identification information VNFD identification information.
  • the processing unit 502 is specifically configured to: when the used LB type is a peripheral LB type, determine, in the description information of the LB type, the identifier information of the virtual network function description information VNFD of the peripheral LB type; Obtaining a VNFD corresponding to the identifier information; initiating a request for instantiating the peripheral LB according to the VNFD to the virtual network function manager VNFM; and using the address information of the peripheral LB instance sent by the VNFM received by the receiving unit 501 as the description information of the LB .
  • the processing unit 502 is specifically configured to: when the LB type used is an infrastructure-based LB type, initiate, by the sending unit 503, a request for assigning an LB of the LB type based on the infrastructure to the VIM; and
  • the address information of the available infrastructure-based LB transmitted by the VIM received by the unit 501 is used as the description information of the LB.
  • the port capability information includes a port number of the port of the second VNF and function information of the port.
  • connection method of the LB in the foregoing embodiment of FIG. 3 are also applicable to the connection device of the LB of the present embodiment.
  • the foregoing detailed description of the connection method of the LB can be clearly understood by those skilled in the art.
  • the implementation method of the connection device of the LB in this embodiment is known, so that the details of the description will not be described in detail herein.
  • FIG. 8 is a system block diagram of a service providing device according to an embodiment of the present application.
  • the service providing device includes: a receiver 601, configured to receive, by the service requesting device, about An instantiation request of the service; the processor 602, configured to acquire the network service description information NSD of the service according to the instantiation request; the NSD includes the first description information VNFD of the first virtual network function module VNF, and the second description information VNFD of the second VNF
  • the connection information between the first VNF and the second VNF; the first VNFD and/or the second VNFD includes description information about the type of the load balancer LB, and the second VNFD further includes port capability information of the second VNF; LB type information; determining the type of LB used according to the description information of the LB type and the information of the LB type supported by the service providing device; and obtaining description information
  • the processor 602 is specifically configured to: when the description information of the LB type is the type information of the required LB, and the priority information of each type,
  • the type information of the LB of the required VNF is the type information of the LB of the first VNF requirement included in the first VNFD, or the type information of the LB of the second VNF requirement included in the second VNFD.
  • the processor 602 is further configured to: when the description information of the LB type further includes the type information of the supported LB, determine that the type information of the LB and the information of the LB type supported by the service providing device are not common.
  • LB type determining the type of the LB supported by the first VNF as the type of LB used; wherein the type information of the supported LB is the first VNF included in the first VNFD Type information of supported LBs.
  • the processor 602 is specifically configured to: when the used LB type is a peripheral LB type,
  • the address information of the available LB instance returned by the database received by the receiver 601 is used as the description information of the LB; or
  • the receiver 601 Receiving, by the receiver 601, the virtual network function description information VNFD of the available LB instance returned by the database; initiating a request to instantiate the peripheral LB according to the VNFD of the LB instance to the virtual network function manager VNFM; and receiving the VNFM through the receiver 601
  • the address information of the sent peripheral LB instance is used as the description information of the LB.
  • the processor 602 is further configured to: before sending, by the sender 603, a request for querying an available LB instance of the peripheral LB type to the database, determining that the description information of the LB type does not include the virtual network of the peripheral LB type.
  • Function description information VNFD identification information VNFD identification information.
  • the processor 602 is specifically configured to: when the type of the LB used is a peripheral LB type, determine, in the description information of the LB type, the identifier information of the virtual network function description information VNFD of the peripheral LB type; Obtaining a VNFD corresponding to the identifier information; initiating a request for instantiating the peripheral LB according to the VNFD to the virtual network function manager VNFM; and using the address information of the peripheral LB instance sent by the VNFM received by the receiver 601 as the description information of the LB .
  • the processor 602 is specifically configured to: when the LB type used is an infrastructure-based LB type, initiate, by the sender 603, a request for the LB of the infrastructure-based LB type to be sent to the VIM; and The address information of the available infrastructure-based LB transmitted by the VIM received by the VIM is used as the description information of the LB.
  • the port capability information includes a port number of the port of the second VNF and function information of the port.
  • bus 600 can include any number of interconnected buses and bridges, and bus 600 will include one or more processors and memory 604 represented by processor 602. The various circuits of the memory are linked together.
  • the bus 600 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 605 provides an interface between bus 600 and processor 602, receiver 601, and transmitter 603. The receiver 601 and the transmitter 603 are used for data communication between the service providing device and the external device.
  • Processor 602 is responsible for managing bus 600 and the usual processing.
  • Memory 604 can be used to store data used by processor 602 in performing operations.
  • FIG. 9 is a functional block diagram of an instantiation deployment apparatus for a service according to an embodiment of the present application.
  • the device is used in the instantiation deployment method of the service on the service request device side in the foregoing embodiment. As shown in FIG. 9
  • the instantiated deployment device of the service includes: a sending unit 701, configured to send an instantiation request for a service to a service providing device, where the instantiation request carries network service description information of the service Identification information of the NSD or the NSD;
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and the first VNF and the second VNF Connection information;
  • the first VNFD and/or the second VNFD includes description information about a load balancer LB type, the second VNFD further includes port capability information of the second VNF;
  • the receiving unit 702 is configured to receive The service provides a response message that the instance of the service is successfully deployed by the service.
  • the description information of the LB type includes the type information of the supported LB, the type information of the required LB, and the priority information of each type; and the type information of the required LB is the first VNFD.
  • the port capability information includes a port number of the port of the second VNF and function information of the port.
  • FIG. 10 is a system block diagram of a service requesting device according to an embodiment of the present application.
  • the service requesting device is used in the instantiation deployment method of the service on the service request device side in the foregoing embodiment.
  • the service requesting device includes: a sender 801, configured to send an instantiation request for a service to a service providing device, where the instantiation request carries an identifier of the network service description information NSD of the service.
  • the NSD includes first description information VNFD of the first virtual network function module VNF, second description information VNFD of the second VNF, and connection information between the first VNF and the second VNF
  • the first VNFD and/or the second VNFD include description information for a load balancer LB type
  • the second VNFD further includes port capability information of the second VNF
  • a receiver 802 configured to receive the service Providing a response message that the instance of the service sent by the device is successfully deployed.
  • the description information of the LB type includes the type information of the supported LB, the type information of the required LB, and the priority information of each type;
  • the type information of the required LB is the The type information of the LB of the first VNF requirement included in the first VNFD, or the type information of the LB of the second VNF requirement included in the second VNFD;
  • the type information of the supported LB is the Type information of the LB supported by the first VNF included in the first VNFD.
  • the port capability information includes a port number of the port of the second VNF and function information of the port.
  • bus 800 can include any number of interconnected buses and bridges, and bus 800 will include one or more processors and memory 804 represented by processor 803. The various circuits of the memory are linked together.
  • the bus 800 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 805 provides an interface between bus 800 and processor 803, receiver 802, and transmitter 801. The receiver 802 and the transmitter 801 are used for data communication between the service requesting device and the external device.
  • the processor 803 is responsible for managing the bus 800 and the usual processing.
  • Memory 804 can be used to store data used by processor 803 in performing operations.
  • FIG. 11 is a functional block diagram of a connection device of an LB according to an embodiment of the present application.
  • the connection device of the LB is used to implement a connection method of the LB on the VIM side.
  • the connection device of the LB includes: a receiving unit 901, configured to receive a connection request sent by the service providing device, where the connection request includes an instance of the first virtual network function module VNF of the service and an instance of the second VNF.
  • Load balancer LB type LB description information first VNF and second
  • An instance of the VNF is connected to the LB, and the interface corresponding to the function information of the port on the LB is connected to the port of the corresponding function on the second VNF according to the function information of the port.
  • the device further includes a sending unit 903, configured to send, to the service providing device, a response message that the connection is completed.
  • the receiving unit 901 is further configured to: when the LB type is an infrastructure-based LB type, receive, by the service providing device, a request for allocating an infrastructure-based LB for the service, before the receiving unit 901 receives the connection request;
  • the processing unit 902 is further configured to: send a request for allocating an infrastructure-based LB to the infrastructure layer according to the request for allocating the infrastructure-based LB for the service;
  • the receiving unit 901 is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
  • the sending unit 903 is further configured to: send the address information of the available infrastructure-based LB to the service providing device; wherein the description information of the LB includes address information of the available infrastructure-based LB.
  • connection method of the LB has been described in detail in the foregoing embodiments.
  • the implementation method of the connection device of the LB in this embodiment can be clearly understood by the person skilled in the art, so The simplicity is not detailed here.
  • FIG. 12 is a system block diagram of a VIM provided by an embodiment of the present application.
  • This VIM is used to implement a connection method of the LB on the VIM side.
  • the VIM includes: a receiver 1001, configured to receive a connection request sent by a service providing device, where the connection request includes an instance of a first virtual network function module VNF of a service and a load balancing used by an instance of the second VNF.
  • the VIM further includes a sender 1003, configured to send a connection completion response message to the service providing device.
  • the receiver 1001 is further configured to: when the LB type is an infrastructure-based LB type, receive, by the service providing device, a request for allocating an infrastructure-based LB for the service, before the receiver 1001 receives the connection request;
  • the processor 1002 is further configured to: send a request for allocating an infrastructure-based LB to an infrastructure layer according to a request for allocating an infrastructure-based LB for the service;
  • the receiver 1001 is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
  • the sender 1003 is further configured to: send the address information of the available infrastructure-based LB to the service providing device; wherein the description information of the LB includes address information of the available infrastructure-based LB.
  • bus 1000 can include any number of interconnected buses and bridges, and bus 1000 will include one or more processors and memory 1004 represented by processor 1002.
  • the various circuits of the memory are linked together.
  • the bus 1000 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • the bus interface 1005 is provided between the bus 1000 and the processor 1002, the receiver 1001, and the transmitter 1003. mouth.
  • the receiver 1001 and the transmitter 1003 are used for data communication between the VIM and an external device.
  • the processor 1002 is responsible for managing the bus 1000 and the usual processing.
  • the memory 1004 can be used to store data used by the processor 1002 in performing operations.
  • connection method of the LB has been described in detail in the foregoing embodiments.
  • the implementation method of the connection device of the LB in this embodiment can be clearly understood by the person skilled in the art, so The simplicity is not detailed here.
  • the NSD includes the first description information VNFD of the first VNF, the second description information VNFD of the second VNF, the first VNFD and/or the second VNFD includes description information about the LB type, and the second VNFD further includes The port capability information of the second VNF; in the process of instantiation, the service providing device can determine the LB type used according to the description information of the LB type and the LB type information supported by the service providing device. Therefore, the type of LB used can be determined by the method of the present application.
  • the service providing device sends the description information of the LB of the LB type to the VIM, so that the VIM can use the LB of the LB type according to the connection information, the port capability information of the second VNF, and the description information of the LB. Connected between the instance of the first VNF and the instance of the second VNF.
  • the determined LB of the used LB type can also be connected between instances of the VNF by the method of the present application.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

La présente invention concerne un procédé de connexion de dispositif d'équilibrage de charge, et un procédé et un dispositif de déploiement d'instanciations de services. Le procédé comprend les étapes consistant à : acquérir un NSD d'un service conformément à une demande d'instanciation, le NSD comprenant un premier VNFD d'un première VNF, un deuxième VNFD d'une deuxième VNF et des informations relatives à une connexion entre la première VNF et la deuxième VNF, le premier VNFD et/ou le deuxième VNFD comprenant des informations de description d'un type de LB, et le deuxième VNFD comprenant également des informations de capacité de port de la deuxième VNF ; déterminer un type de LB utilisé d'après les informations de description du type de LB et les informations relatives à un type de LB supporté par un dispositif de fourniture de service ; et lorsque l'instanciation sur la première VNF et l'instanciation sur la deuxième VNF ont réussi, envoyer les informations de description d'un LB, les informations relatives à la connexion et les informations de capacité de port à un VIM. Le VIM connecte le LB entre une instance de la première VNF et une instance de la deuxième VNF d'après les informations de description du LB, les informations relatives à la connexion et les informations de capacité de port.
PCT/CN2015/087807 2014-12-26 2015-08-21 Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services WO2016101639A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410833791.6 2014-12-26
CN201410833791.6A CN105791147B (zh) 2014-12-26 2014-12-26 负载均衡器的连接方法、业务的实例化部署方法及装置

Publications (1)

Publication Number Publication Date
WO2016101639A1 true WO2016101639A1 (fr) 2016-06-30

Family

ID=56149171

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/087807 WO2016101639A1 (fr) 2014-12-26 2015-08-21 Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services

Country Status (2)

Country Link
CN (1) CN105791147B (fr)
WO (1) WO2016101639A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107689882B (zh) * 2016-08-05 2020-04-21 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
CN108200018B (zh) * 2017-12-20 2019-11-05 北京百度网讯科技有限公司 云计算中的流量转发方法及设备、计算机设备及可读介质
CN110891239B (zh) * 2018-09-06 2021-01-15 ***通信有限公司研究院 Pnf配置及pnfd tosca实现方法和装置
CN109753514A (zh) * 2018-12-13 2019-05-14 平安普惠企业管理有限公司 负载均衡器选型方法、装置、计算机设备以及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、***
CN104202264A (zh) * 2014-07-31 2014-12-10 华为技术有限公司 云化数据中心网络的承载资源分配方法、装置及***
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及***

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9614929B2 (en) * 2006-12-19 2017-04-04 International Business Machines Corporation Application server with automatic and autonomic application configuration validation
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
CN103532870A (zh) * 2013-10-29 2014-01-22 北京京东尚科信息技术有限公司 一种更新Web应用集群的方法和装置
CN104219127B (zh) * 2014-08-30 2018-06-26 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN105634782B (zh) * 2014-11-06 2019-03-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及***
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、***
CN104202264A (zh) * 2014-07-31 2014-12-10 华为技术有限公司 云化数据中心网络的承载资源分配方法、装置及***

Also Published As

Publication number Publication date
CN105791147B (zh) 2019-07-23
CN105791147A (zh) 2016-07-20

Similar Documents

Publication Publication Date Title
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US20210011834A1 (en) Service Upgrade Management Method, Apparatus, And Storage Medium
US10701139B2 (en) Life cycle management method and apparatus
WO2016029821A1 (fr) Procédé et dispositif servant à créer une instance de réseau virtuel
EP3455728B1 (fr) Orchestrateur pour une plate-forme de réseau virtuel en tant que service (vnpaas)
WO2019184967A1 (fr) Procédé et appareil de déploiement de tranche de réseau
WO2016155394A1 (fr) Procédé et dispositif pour établir une liaison entre des fonctions réseau virtualisées
CN106301829B (zh) 一种网络业务扩容的方法和装置
AU2015419073B2 (en) Life cycle management method and device for network service
JP6549787B2 (ja) ネットワークサービスをデプロイするための方法及び装置
WO2018001049A1 (fr) Procédé, dispositif et système de déploiement de fonction de réseau virtuelle utilisant le calcul en périphérie de réseau
WO2018149272A1 (fr) Procédé d'attribution de ressources fondé sur un sla et nfvo
JP6190949B2 (ja) 仮想ネットワーク機能マネージャによる仮想インフラストラクチャマネージャへのアクセスの自動化構成
WO2015149600A1 (fr) Procédé et dispositif de déploiement de service de réseau virtuel
WO2018072503A1 (fr) Procédé d'initiation de modification de logiciel, procédé et dispositif de publication de métadonnées
WO2015172362A1 (fr) Système réseau de virtualisation de fonction réseau, et procédé et dispositif de traitement de données
WO2018090299A1 (fr) Procédé et dispositif d'octroi d'autorisation de gestion de cycle de vie de service réseau
CN111245634B (zh) 一种虚拟化管理方法及装置
WO2016101639A1 (fr) Procédé de connexion de dispositif d'équilibrage de charge, et procédé et dispositif de déploiement d'instanciations de services
WO2017054129A1 (fr) Procédé de traitement de ressource de virtualisation de fonction de réseau et gestionnaire de fonction de réseau virtualisée
CN105556929A (zh) 在云计算***中运行应用的网络元件和方法
KR20180006971A (ko) 하드웨어 가속 방법 및 관련 장치
CN107534577A (zh) 一种网络业务实例化的方法及设备
WO2020135517A1 (fr) Procédé et dispositif de déploiement d'une fonction de réseau virtuel
WO2013097237A1 (fr) Méthode, dispositif et système de déploiement de processus d'application

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

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

Country of ref document: EP

Kind code of ref document: A1