WO2016101639A1 - Load balancer connecting method, and service instantiation deployment method and device - Google Patents

Load balancer connecting method, and service instantiation deployment method and device 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
French (fr)
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/en

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

This application provides a load balancer connecting method, and a service instantiation deployment method and device. The method comprises: acquiring an NSD of a service according to an instantiation request, the NSD comprising a first VNFD of a first VNF, a second VNFD of a second VNF, and information about a connection between the first VNF and the second VNF, the first VNFD and/or the second VNFD comprising description information of an LB type, and the second VNFD further comprising port capability information of the second VNF; determining a used LB type according to the description information of the LB type and information about an LB type supported by a service providing device; and when instantiation on the first VNF and instantiation on the second VNF are successful, sending description information of an LB, the information about the connection, and the port capability information to a VIM. The VIM connects the LB between an instance of the first VNF and an instance of the second VNF according to the description information of the LB, the information about the connection, and the port capability information.

Description

负载均衡器的连接方法、业务的实例化部署方法及装置Load balancer connection method, business instantiation deployment method and device 技术领域Technical field
本申请涉及通信技术领域,尤其涉及一种负载均衡器的连接方法、业务的实例化部署方法及装置。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.
背景技术Background technique
网络功能虚拟化(英文:Network Function Virtualization,简称:NFV)通过使用通用的硬件设备及虚拟化技术,来承载传统网络中专用设备的功能,从而降低因为部署专用设备带来的昂贵成本。通过软硬件解耦,使网络设备功能不再依赖于专用硬件。其中,能够接收虚拟化请求,并根据请求对相应业务进行虚拟化处理的一方,一般称为虚拟化业务提供方(简称业务提供方),发起虚拟化请求的一方一般称为业务请求方。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.
NFV中虚拟化的网络服务(英文:Network Service,简称:NS)可以是一个网络协议多媒体子***(英文:Internet Protocol Multimedia Subsystem,简称:IMS)的网络服务,也可以是一个下一代移动核心网络(英文:Evolved Packet Core,简称:EPC)的网络服务。一个NS中还可能包含若干个虚拟化网络功能模块(英文:Virtualized Network Function,简称:VNF)。在一个VNF中还可以包含多个模块,一个模块可以被称为一个VNFC(VNF component)。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).
当一个NS在实例化部署时,根据业务的需要,NS内的VNF有可能需要多个实例,同样在VNF内,VNFC也可能需要多个实例。所以在业务进行时,需要利用负载均衡技术对VNF的实例进行选择,从而尽量选择负载较轻的实例为当前的业务服务。When an NS is deployed in an instantiation, the VNF in the NS may need multiple instances according to the needs of the service. Similarly, in the VNF, 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.
目前NFV中定义了三种负载均衡模型,其中图1a中表示的是外设负载均衡模型。Three load balancing models are currently defined in NFV, and the peripheral load balancing model is shown in Figure 1a.
在图1a的模型中,VNF1与VNF2相互连接。负载均衡器(英文:Load Balancer,简称:LB)是一个单独的VNF,可以为VNF2的实例提供负载均衡 的功能。在图1a中,右边的VNF2实例1、VNF2实例2、VNF2实例3是VNF2的3个实例。对于左边的V NF1来说,右边只有一个逻辑的VNF2,当数据从对VNF1发往VNF2时,LB负责选择负载较轻的实例为其服务。在该模型中,LB可以由平台方提供。In the model of Figure 1a, 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. The function. In Figure 1a, VNF2 instance 1, VNF2 instance 2, VNF2 instance 3 on the right are 3 instances of VNF2. For the left V NF1, there is only one logical VNF2 on the right. When data is sent from VNF1 to VNF2, the LB is responsible for selecting the lighter instance to serve it. In this model, the LB can be provided by the platform side.
再请参考图1b所示,为端到端负载均衡模型。在该模型中,LB设置在对VNF1中。该LB可以为连接的VNF2的多个实例进行负载均衡选择。具体来说,当VNF1需要发送数据到VNF2时,VNF1根据其内置的LB判断VNF2的哪个实例上的负载相对较轻,从而直接将数据发向负载较轻的实例。Referring again to Figure 1b, it is an end-to-end load balancing model. In this model, 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.
再请参考图1c所示,为基于基础设施的负载均衡模型。基于基础设施的负载均衡模型在架构上同外设负载均衡相似,最大的区别是外设负载均衡模型(如图1a)中的LB是一个VNF,LB主要通过同被服务的VNF2的交互获取被服务的VNF2上的负载情况,从而实现负载均衡的功能。基于基础设施的负载均衡模型中LB是配置在基础设施层的,比如可以配置在物理服务器上的虚拟机管理器上的虚拟交换机上,或是配置在基础设施层的一个专有的物理设备上。图1c的模型中的LB可以直接同被服务的VNF2上的虚拟机通信,从而获知被服务的VNF2的负载情况。Referring again to Figure 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. The load condition on the service VNF2, thus implementing the load balancing function. In an infrastructure-based load balancing model, 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.
在现有NFV中虽然定义了以上三种负载均衡模型,却没有定义如何在关于业务的实例化部署过程中如何确定使用的LB类型以及如何将LB连接在业务的VNF的实例之间。Although the above three load balancing models are defined in the existing NFV, there is no definition of how to determine the type of LB used in the process of instantiation deployment of the service and how to connect the LB between instances of the VNF of the service.
发明内容Summary of the invention
本申请实施例提供一种负载均衡器的连接方法、业务的实例化部署方法及装置,用于解决现有技术中的如何确定使用的LB类型以及如何将LB连接在业务的VNF的实例之间的技术问题。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.
本申请第一方面提供了一种LB的连接方法,包括:The first aspect of the present application provides a connection method of an LB, including:
业务提供设备接收业务请求设备发送的关于业务的实例化请求; The service providing device receives an instantiation request for the service sent by the service requesting device;
所述业务提供设备根据所述实例化请求获取所述业务的网络服务描述信息NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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;
所述业务提供设备获取所述业务提供设备支持的LB类型的信息;The service providing device acquires information of an LB type supported by the service providing device;
所述业务提供设备根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型;Determining, by the service providing device, 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;
所述业务提供设备获取所述所使用的LB类型的LB的描述信息;The service providing device acquires description information of the used LB of the LB type;
所述业务提供设备在接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将所述LB的描述信息、所述连接信息和所述端口能力信息发送给虚拟基础设施管理器VIM,以使所述VIM能够根据所述LB的描述信息、所述连接信息和所述端口能力信息将所述所使用的LB类型的LB连接在所述第一VNF的实例和所述第二VNF的实例之间。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.
结合第一方面,在第一方面的第一种可能的实现方式中,当所述对LB类型的描述信息包含需求的LB的类型信息,以及每种类型的优先级信息时;所述业务提供设备根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型,包括:With reference to the first aspect, in a first possible implementation manner of the first aspect, 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:
所述业务提供设备根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定共同的LB类型;Determining, by the service providing device, a 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;
所述业务提供设备根据所述优先级信息确定所述共同的LB类型中的优先级最高的LB类型作为所述所使用的LB类型;Determining, by the service providing device, the LB type with the highest priority among the common LB types as the used LB type according to the priority information;
其中,所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息。 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.
结合第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,当所述对LB类型的描述信息还包含支持的LB的类型信息时,所述方法还包括:With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, when the description information of the LB type further includes type information of the supported LB, the method further include:
所述业务提供设备根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;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;
所述业务提供设备确定所述支持的LB的类型作为所述所使用的LB类型;Determining, by the service providing device, a type of the supported LB as the used LB type;
其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。The type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式,在第一方面的第三种可能的实现方式中,当所述所使用的LB类型为外设LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:In combination with the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect, in a third possible implementation of the first aspect, when the used LB When the type is the LB type, the service providing device obtains the description information of the LB of the used LB type, including:
所述业务提供设备向数据库发送查询可用的外设LB类型的LB实例的请求;所述业务提供设备将接收到的所述数据库返回的可用的LB实例的地址信息作为所述LB的描述信息;或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
所述业务提供设备向数据库发送查询可用的外设LB类型的LB实例的请求;所述业务提供设备接收所述数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;所述业务提供设备根据所述LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;所述业务提供设备将接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。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. .
结合第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,在所述业务提供设备向数据库发送查询可用的外设LB类型的LB实例 的请求之前,所述方法还包括:In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation manner of the first aspect, the service providing device sends an LB instance of the peripheral LB type that is available for querying the database to the database. Before the request, the method further includes:
所述业务提供设备确定所述对LB类型的描述信息中未包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息。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.
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式,在第一方面的第五种可能的实现方式中,当所述所使用的LB类型为外设LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:In combination with the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect, in a fifth possible implementation of the first aspect, when the used LB When the type is the LB type, the service providing device obtains the description information of the LB of the used LB type, including:
所述业务提供设备确定所述对LB类型的描述信息中包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息;Determining, by the service providing device, the identifier information of the virtual network function description information VNFD of the peripheral LB type in the description information of the LB type;
所述业务提供设备根据所述标识信息获取与所述标识信息对应的所述VNFD;The service providing device acquires the VNFD corresponding to the identifier information according to the identifier information;
所述业务提供设备根据所述VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;The service providing device initiates a request for instantiating a peripheral LB according to the VNFD to the virtual network function manager VNFM;
所述业务提供设备将接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。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.
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式,在第一方面的第六种可能的实现方式中,当所述所使用的LB类型为基于基础设施的LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:In conjunction with the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect, in a sixth possible implementation of the first aspect, when the used LB is used When the type is an LB type based on the infrastructure, the service providing device acquires the description information of the LB of the used LB type, including:
所述业务提供设备向所述VIM发起为所述业务分配所述基于基础设施的LB类型的LB的请求;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;
所述业务提供设备将接收到的所述VIM发送的可用的基于基础设施的LB 的地址信息作为所述LB的描述信息。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.
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第六种可能的实现方式中的任意一种,在第一方面的第七种可能的实现方式中,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。With reference to the first aspect, or the first possible implementation of the first aspect, to any one of the sixth possible implementations of the first aspect, in a seventh possible implementation of the first aspect, 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:
业务请求设备向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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.
结合第二方面,在第二方面的第一种可能的实现方式中,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。With reference to the second aspect, in a first possible implementation manner of the second aspect, 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.
结合第二方面或第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。 With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, 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:
虚拟基础设施管理器VIM接收业务提供设备发送的连接请求,所述连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类型的LB的描述信息、所述第一VNF和所述第二VNF之间的连接信息以及所述第二VNF的端口能力信息,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息;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 connection information between the first VNF and the second VNF and the port capability information of the second VNF, the port capability information including a port number of the port of the second VNF and a function of the port information;
所述VIM根据所述连接信息和所述LB的描述信息将第一VNF的实例与所述LB连接,并根据所述端口的功能信息将所述LB上与所述端口的功能信息相对应的接口与所述第二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.
结合第三方面,在第三方面的第一种可能的实现方式中,当所述LB类型为基于基础设施的LB类型时,在所述VIM接收所述连接请求之前,所述方法还包括:With reference to the third aspect, in a first possible implementation manner of the third aspect, when the LB type is an infrastructure-based LB type, before the VIM receives the connection request, the method further includes:
所述VIM接收所述业务提供设备发送的为所述业务分配所述基于基础设施的LB的请求;The VIM receives a request sent by the service providing device to allocate the infrastructure-based LB for the service;
所述VIM根据所述为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配所述基于基础设施的LB的请求;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;
所述VIM接收所述基础设施层返回的可用的基于基础设施的LB的地址信息;The VIM receives address information of an available infrastructure-based LB returned by the infrastructure layer;
所述VIM将所述可用的基于基础设施的LB的地址信息发送给所述业务提供设备;其中,所述LB的描述信息包括所述可用的基于基础设施的LB的地址信息。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;
处理单元,用于根据所述实例化请求获取所述业务的网络服务描述信息NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;获取所述装置支持的LB类型的信息;根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型;并获取所述所使用的LB类型的LB的描述信息;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. Description information of the LB of the used LB type;
发送单元,用于在所述接收单元接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将所述LB的描述信息、所述连接信息和所述端口能力信息发送给虚拟基础设施管理器VIM,以使所述VIM能够根据所述LB的描述信息、所述连接信息和所述端口能力信息将所述所使用的LB类型的LB连接在所述第一VNF的实例和所述第二VNF的实例之间。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.
结合第四方面,在第四方面的第一种可能的实现方式中,所述处理单元具体用于:当所述对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, 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,
根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,根据所述优先级信息确定所述共同的LB类型中的优先级最高的LB类型作为所述所使用的LB类型;其中,所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息。Determining whether there is a 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; if yes, determining that the common LB type has the highest priority according to the priority 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.
结合第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现 方式中,所述处理单元还用于:当所述对LB类型的描述信息还包含支持的LB的类型信息时,根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;确定所述第一VNF支持的LB的类型作为所述所使用的LB类型;其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。In conjunction with the first possible implementation of the fourth aspect, the second possible implementation in the fourth aspect In an aspect, 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.
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种可能的实现方式,在第四方面的第三种可能的实现方式中,所述处理单元具体用于:当所述所使用的LB类型为外设LB类型时,With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, or the second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the processing unit is specifically used to : When the type of LB used is a peripheral LB type,
通过所述发送单元向数据库发送查询可用的外设LB类型的LB实例的请求;Sending, by the sending unit, a request for querying an available LB instance of a peripheral LB type to the database;
将通过所述接收单元接收到的所述数据库返回的可用的LB实例的地址信息作为所述LB的描述信息;或Using the address information of the available LB instance returned by the database received by the receiving unit as the description information of the LB; or
通过所述接收单元接收所述数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;根据所述LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;将通过所述接收单元接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。Receiving, by the receiving unit, virtual network function description information VNFD of the available LB instance returned by the database; initiating a request for instantiating the peripheral LB according to the VNFD of the LB instance to the virtual network function manager VNFM; The address information of the peripheral LB instance sent by the VNFM received by the receiving unit is used as the description information of the LB.
结合第四方面的第三种可能的实现方式,在第四方面的第四种可能的实现方式中,所述处理单元还用于:在通过所述发送单元向数据库发送查询可用的外设LB类型的LB实例的请求之前,确定所述对LB类型的描述信息中未包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息。In conjunction with the third possible implementation of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, 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.
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种可能的实现方式,在第四方面的第五种可能的实现方式中,所述处理单元具体 用于:当所述所使用的LB类型为外设LB类型时,确定所述对LB类型的描述信息中包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息;根据所述标识信息获取与所述标识信息对应的所述VNFD;根据所述VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;并将通过所述接收单元接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, or the second possible implementation manner of the fourth aspect, in a fifth possible implementation manner of the fourth aspect, And determining, when the used LB type is a 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.
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种可能的实现方式,在第四方面的第六种可能的实现方式中,所述处理单元具体用于:当所述所使用的LB类型为基于基础设施的LB类型时,通过所述发送单元向所述VIM发起为所述业务分配所述基于基础设施的LB类型的LB的请求;并将通过所述接收单元接收到的所述VIM发送的可用的基于基础设施的LB的地址信息作为所述LB的描述信息。With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, or the second possible implementation manner of the fourth aspect, in a sixth possible implementation manner of the fourth aspect, 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.
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第六种可能的实现方式中的任意一种,在第四方面的第七种可能的实现方式中,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, to any one of the sixth possible implementation manner of the fourth aspect, 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:
发送单元,用于向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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.
结合第五方面,在第五方面的第一种可能的实现方式中,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, 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.
结合第五方面或第五方面的第一种可能的实现方式,在第五方面的第二种可能的实现方式中,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, 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:
接收单元,用于接收业务提供设备发送的连接请求,所述连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类型的LB的描述信息、所述第一VNF和所述第二VNF之间的连接信息以及所述第二VNF的端口能力信息,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息;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 ;
处理单元,用于根据所述连接信息和所述LB的描述信息将第一VNF的实例与所述LB连接,并根据所述端口的功能信息将所述LB上与所述端口的功能信息相对应的接口与所述第二VNF上对应的功能的端口连接。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.
结合第六方面,在第六方面的第一种可能的实现方式中,所述装置还包括发送单元,With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the device further includes a sending unit,
所述接收单元还用于:当所述LB类型为基于基础设施的LB类型时,在所 述接收单元接收所述连接请求之前,接收所述业务提供设备发送的为所述业务分配所述基于基础设施的LB的请求;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;
所述处理单元还用于:根据所述为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配所述基于基础设施的LB的请求;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;
所述接收单元还用于:接收所述基础设施层返回的可用的基于基础设施的LB的地址信息;The receiving unit is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
所述发送单元还用于:将所述可用的基于基础设施的LB的地址信息发送给所述业务提供设备;其中,所述LB的描述信息包括所述可用的基于基础设施的LB的地址信息。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;
处理器,用于根据所述实例化请求获取所述业务的网络服务描述信息NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;获取所述装置支持的LB类型的信息;根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型;并获取所述所使用的LB类型的LB的描述信息;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. Description information of the LB of the used LB type;
发送器,用于在所述接收器接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将所述LB的描述信息、所述连接信息和所述端口能力信息发送给虚拟基础设施管理器VIM,以使所述VIM能够根据所述LB的描述信息、所述连接信息和所述端口能力信息将所述所使用的LB类型的LB连接在所 述第一VNF的实例和所述第二VNF的实例之间。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.
结合第七方面,在第七方面的第一种可能的实现方式中,所述处理器具体用于:当所述对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, 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,
根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,根据所述优先级信息确定所述共同的LB类型中的优先级最高的LB类型作为所述所使用的LB类型;其中,所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息。Determining whether there is a 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; if yes, determining that the common LB type has the highest priority according to the priority 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.
结合第七方面的第一种可能的实现方式,在第七方面的第二种可能的实现方式中,所述处理器还用于:当所述对LB类型的描述信息还包含支持的LB的类型信息时,根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;确定所述第一VNF支持的LB的类型作为所述所使用的LB类型;其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。With reference to the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, 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.
结合第七方面或第七方面的第一种可能的实现方式或第七方面的第二种可能的实现方式,在第七方面的第三种可能的实现方式中,所述处理器具体用于:当所述所使用的LB类型为外设LB类型时,With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, or the second possible implementation manner of the seventh aspect, in a third possible implementation manner of the seventh aspect, : When the type of LB used is a peripheral LB type,
通过所述发送器向数据库发送查询可用的外设LB类型的LB实例的请求;Sending, by the sender, a request for querying an available LB instance of a peripheral LB type to the database;
将通过所述接收器接收到的所述数据库返回的可用的LB实例的地址信息作为所述LB的描述信息;或Using the address information of the available LB instance returned by the database received by the receiver as the description information of the LB; or
通过所述接收器接收所述数据库返回的可用的LB实例的虚拟网络功能描 述信息VNFD;根据所述LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;将通过所述接收器接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。Receiving, by the receiver, a virtual network function description of an available LB instance returned by the database Deriving the information VNFD; initiating a request for instantiating the peripheral LB according to the VNFD of the LB instance to the virtual network function manager VNFM; using the address information of the peripheral LB instance sent by the VNFM received by the receiver as a Describe the description information of LB.
结合第七方面的第三种可能的实现方式,在第七方面的第四种可能的实现方式中,所述处理器还用于:在通过所述发送器向数据库发送查询可用的外设LB类型的LB实例的请求之前,确定所述对LB类型的描述信息中未包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息。In conjunction with the third possible implementation of the seventh aspect, in a fourth possible implementation manner of the seventh aspect, 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.
结合第七方面或第七方面的第一种可能的实现方式或第七方面的第二种可能的实现方式,在第七方面的第五种可能的实现方式中,所述处理器具体用于:当所述所使用的LB类型为外设LB类型时,确定所述对LB类型的描述信息中包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息;根据所述标识信息获取与所述标识信息对应的所述VNFD;根据所述VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;并将通过所述接收器接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, or the second possible implementation manner of the seventh aspect, in 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.
结合第七方面或第七方面的第一种可能的实现方式或第七方面的第二种可能的实现方式,在第七方面的第六种可能的实现方式中,所述处理器具体用于:当所述所使用的LB类型为基于基础设施的LB类型时,通过所述发送器向所述VIM发起为所述业务分配所述基于基础设施的LB类型的LB的请求;并将通过所述接收器接收到的所述VIM发送的可用的基于基础设施的LB的地址信息作为所述LB的描述信息。With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, or the second possible implementation manner of the seventh aspect, in 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.
结合第七方面或第七方面的第一种可能的实现方式至第七方面的第六种可能的实现方式中的任意一种,在第七方面的第七种可能的实现方式中,所述 端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, to any one of the sixth possible implementation manner of the seventh aspect, in a seventh possible implementation manner of the seventh aspect, 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:
发送器,用于向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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;
接收器,用于接收所述业务提供设备发送的所述业务的实例部署成功的响应消息。And a receiver, configured to receive a response message that the instance of the service sent by the service providing device is successfully deployed.
结合第八方面,在第八方面的第一种可能的实现方式中,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, 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.
结合第八方面或第八方面的第一种可能的实现方式,在第八方面的第二种可能的实现方式中,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。With reference to the eighth aspect, or the first possible implementation manner of the eighth aspect, in a second possible implementation manner of the eighth aspect, 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:
接收器,用于接收业务提供设备发送的连接请求,所述连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器 LB类型的LB的描述信息、所述第一VNF和所述第二VNF之间的连接信息以及所述第二VNF的端口能力信息,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息;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;
处理器,用于根据所述连接信息和所述LB的描述信息将第一VNF的实例与所述LB连接,并根据所述端口的功能信息将所述LB上与所述端口的功能信息相对应的接口与所述第二VNF上对应的功能的端口连接。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.
结合第九方面,在第九方面的第一种可能的实现方式中,所述管理器还包括发送器,In conjunction with the ninth aspect, in a first possible implementation manner of the ninth aspect, the manager further includes a transmitter,
所述接收器还用于:当所述LB类型为基于基础设施的LB类型时,在所述接收器接收所述连接请求之前,接收所述业务提供设备发送的为所述业务分配所述基于基础设施的LB的请求;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;
所述处理器还用于:根据所述为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配所述基于基础设施的LB的请求;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;
所述接收器还用于:接收所述基础设施层返回的可用的基于基础设施的LB的地址信息;The receiver is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
所述发送器还用于:将所述可用的基于基础设施的LB的地址信息发送给所述业务提供设备;其中,所述LB的描述信息包括所述可用的基于基础设施的LB的地址信息。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 .
本申请实施例中提供的一个或多个技术方案,至少具有如下技术效果或优点:One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:
本申请实施例中,NSD包括第一VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD,第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,第二VNFD还包括第二VNF的端口能力信息;在实例化的 过程中,业务提供设备能够根据对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型。因此,通过本申请的方法能够确定所使用的LB类型。然后业务提供设备还将所使用的LB类型的LB的描述信息发送给VIM,以使VIM能够根据所述连接信息、第二VNF的端口能力信息和LB的描述信息将所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。因此,通过本申请的方法还能将确定的所使用的LB类型的LB连接在VNF的实例之间。In the embodiment of the present application, 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; In the process, 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. Then, 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. Thus, the determined LB of the used LB type can also be connected between instances of the VNF by the method of the present application.
附图说明DRAWINGS
图1a-图1c为现有技术中的负载均衡模型的示意图;1a-1c are schematic diagrams of a load balancing model in the prior art;
图2为本申请实施例中LB连接在VNF之间的示意图;2 is a schematic diagram of an LB connection between VNFs in an embodiment of the present application;
图3为本申请实施例提供的一种LB的连接方法的流程图;FIG. 3 is a flowchart of a method for connecting an LB according to an embodiment of the present disclosure;
图4为本申请实施例提供的第一例LB的连接方法的流程图;4 is a flowchart of a method for connecting a first example LB according to an embodiment of the present application;
图5为本申请实施例提供的第二例LB的连接方法的流程图;FIG. 5 is a flowchart of a method for connecting a second example LB according to an embodiment of the present disclosure;
图6为本申请实施例提供的第三例LB的连接方法的流程图;FIG. 6 is a flowchart of a method for connecting a third example LB according to an embodiment of the present disclosure;
图7为本申请实施例提供的第一例LB的连接装置的功能框图;FIG. 7 is a functional block diagram of a connection apparatus of a first example LB according to an embodiment of the present disclosure;
图8为本申请实施例提供的业务提供设备的***框图;FIG. 8 is a system block diagram of a service providing device according to an embodiment of the present application;
图9为本申请实施例提供的业务的实例化部署装置的功能框图;FIG. 9 is a functional block diagram of an instantiation deployment apparatus of a service according to an embodiment of the present application;
图10本申请实施例提供的业务请求设备的***框图;Figure 10 is a system block diagram of a service requesting device provided by an embodiment of the present application;
图11为本申请实施例提供的第二例LB的连接装置的功能框图;FIG. 11 is a functional block diagram of a connection apparatus of a second example LB according to an embodiment of the present disclosure;
图12为本申请实施例提供的VIM的***框图。FIG. 12 is a system block diagram of a VIM according to an embodiment of the present application.
具体实施方式detailed description
本申请实施例提供一种负载均衡器的连接方法、业务的实例化部署方法及装置,用以解决现有技术中如何确定使用的LB类型以及如何将LB连接在业务的VNF的实例之间的技术问题。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.
本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存 在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。The term "and/or" in this article is merely an association that describes the associated object, indicating that it can be saved. In three relationships, for example, A and/or B, it can be said that there are three cases in which A exists separately, and A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.
为使本申请实施例的目的、技术方案和优点更加清楚,下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。The technical solutions in the embodiments of the present application are clearly described in the following with reference to the accompanying drawings in the embodiments of the present application. It is obvious that the described embodiments are Some embodiments are applied, not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.
首先请参考图2所示,为本申请实施例中一个LB连接在两个VNF的实例之间的场景示意图。其中,VNF1在本申请实施例中称为第一VNF。VNF2在本申请实施例中称为第二VNF。图2中的LB例如可以是外设LB、基于基础设施的LB或者是端到端的LB。当图2中的LB为端到端的LB时,该LB属于VNF1的一部分。在实际运用中,图2中的LB还可以是其他类型的LB,本申请不作具体限定。First, please refer to FIG. 2, which 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. When the LB in FIG. 2 is an end-to-end LB, the LB belongs to a part of VNF1. In actual use, the LB in FIG. 2 may also be other types of LBs, which is not specifically limited in this application.
需要说明的是,在本申请实施例中以第一VNF和第二VNF两个VNF为例进行说明,但在实际运用中,一个NS可以包括两个以上的VNF,所以两个以上的VNF之间的任意两个有连接关系的VNF的处理方式均可以同处理第一VNF和第二VNF之间的连接关系的处理方式相同,所以以下将详细描述如何确定第一VNF和第二VNF之间所使用的LB类型和如何将确定的所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。It should be noted that, in the embodiment of the present 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.
请参考图3所示,为本申请一实施例提供的一种负载均衡器的连接方法的流程图,该方法包括以下内容:Referring to FIG. 3, a flowchart of a method for connecting a load balancer according to an embodiment of the present disclosure includes the following content:
步骤101:业务提供设备接收业务请求设备发送的关于业务的实例化请求。Step 101: The service providing device receives an instantiation request for the service sent by the service requesting device.
步骤102:根据所述实例化请求获取所述业务的网络服务描述信息(英文: Network Service Descriptor,简称:NSD)。所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和第一VNF和第二VNF之间的连接信息。第一VNFD和/或第二VNFD包括对LB类型的描述信息。第二VNFD还包括第二VNF的端口能力信息。所述端口能力信息包括第二VNF的端口的端口号和所述端口的功能信息。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.
步骤103:业务提供设备获取所述业务提供设备支持的LB类型的信息。Step 103: The service providing device acquires information of an LB type supported by the service providing device.
步骤104:业务提供设备根据所述对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型。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.
步骤105:业务提供设备获取所述所使用的LB类型的LB的描述信息。Step 105: The service providing device acquires description information of the used LB of the LB type.
步骤106:在业务提供设备接收到第一VNF和第二VNF都实例化成功的响应消息之后,将所述LB的描述信息、连接信息和端口能力信息发送给虚拟基础设施管理器(英文:Virtual Infrastructure Manager,简称:VIM),以使VIM能够根据所述连接信息、端口能力信息和所述LB的描述信息将所述所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。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 (VIM) 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.
在本实施例以及本申请其他实施例中,业务提供设备可以对应到网络功能虚拟化业务提供方(NFVO)。业务请求设备可以对应到网络功能虚拟化业务请求方。通常来讲,业务请求方例如为运营商网络,例如运营支撑和计费***。In this embodiment and other embodiments of the present application, the service providing device may correspond to a network function virtualization service provider (NFVO). The service requesting device can correspond to the network function virtualization service requester. Generally, a service requester is, for example, a carrier network, such as an operational support and billing system.
所述NSD可以采用多种规范进行描述,例如云应用的拓扑和运维规范(英文:Topology and Orchestration Specification for Cloud Applications,简称:TOSCA)。其中第一种描述方法如下: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:
tosca_definitions_version:tosca_simple_yaml_1_0_0#定义一个TOSCA的业务模板Tosca_definitions_version:tosca_simple_yaml_1_0_0#Define a TOSCA business template
description:Template with a generic connection between two nodes.#定义该模板的作用为两个节点之间的通用的连接Description:Template with a generic connection between two nodes.#Define the role of this template as a universal connection between two nodes
Figure PCTCN2015087807-appb-000001
Figure PCTCN2015087807-appb-000001
Figure PCTCN2015087807-appb-000002
Figure PCTCN2015087807-appb-000002
Figure PCTCN2015087807-appb-000003
Figure PCTCN2015087807-appb-000003
在本实施例中,描述信息为另一种标记语言(英文:Yet Another Markup Language,简称:YAML)语言版本的TOSCA规范。在本实施例中包含两个节点,分别对应两个VNF。节点1对应连接的第一VNF。节点2对应被连接的第二VNF。根据上述Scalable参数中包含节点2支持的最小实例化个数为3可知节点2在部署时有部署多个实例的需求。所以需要在节点1和节点2之间使用LB。In this embodiment, the description information is another TOSCA specification of a language version of the Yet Another Markup Language (YAML) language. In this embodiment, 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. According to the above Scalable parameter, 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.
具体的,在节点1的描述信息中,即第一VNFD中,包含:Capabilities:Loadbalance:E2E。其中,Capabilities是对节点1的能力信息的描述。Loadbalance是本发明新增的一种能力信息,用来表示节点1支持的负载均衡模型。在本实施例中,E2E表明节点1支持端到端的负载均衡模型(如图1b所示的负载均 衡模型)。该模型可以用来为被连接的节点2提供端到端的LB。requirements参数中包含了节点1的需求信息,其中connect:Node 2,表明节点1需要同节点2连接,即第一VNF和第二VNF之间的连接信息。Specifically, in the description information of the node 1, that is, the first VNFD, includes: Capabilities: Loadbalance: E2E. 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. In this embodiment, 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.
            “Loadbalance:external"Loadbalance:external
               class:3Class:3
             Loadbalance:infrastructureLoadbalance: infrastructure
               class:2Class:2
             Loadbalance:E2ELoadbalance: E2E
               class:1”代码段表示节点1同节点2之间的连接的进一步需求。在本实施例中,Loadbalance参数是本发明新增的参数,用来表示节点1和节点之间的连接对负载均衡模型的需求。每个loadbalance参数下还有class参数。class参数用来表示对应的负载均衡模型的需求优先级别,比如本实施例中“external”,即外设负载均衡模型(如图1a所示的负载均衡模型)的优先级最高,端到端的负载均衡模型的优先级最低。换言之,所述对LB类型的描述信息包括第一VNFD中包含的第一VNF需求的LB的类型信息或者第二VNFD中包含的第二VNF需求的LB的类型信息,以及每种类型的优先级信息。所述对LB类型的描述信息还包括第一VNFD中包含的第一VNF支持的LB的类型信息。The class: 1" code segment represents a further requirement for the connection between node 1 and node 2. In this embodiment, 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. There is also a class parameter under each loadbalance parameter. 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. In other words, 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.
节点2的描述信息中的capabilities参数定义的是节点2的能力信息。在本实施例中,定义了端口的能力信息。该能力信息定义了节点2上对外暴露的连接点的信息,即其他的节点可以通过该端口同该节点相连。在该例中定义了2个连接点,一个是端口号为253的端口,支持的协议为传输控制协议(英文:Transmission Control Protocol,简称:TCP)。参数usage为本发明新增加的参数,用来表示端口253的用途。在本实施例中,端口253可以用来连接负载均衡器。另一个端口采用的协议为超文本传送协议(英文:Hypertext transfer protocol,简称:HTTP),端口号为254。进一步,端口254可以用来连接业务 数据。换言之,第二VNFD中包括第二VNF的端口能力信息,例如端口的端口号、端口的功能信息、端口支持的传输协议等。The capabilities parameter in the description information of the node 2 defines the capability information of the node 2. In this embodiment, 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. In this example, 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. In this embodiment, 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. Further, port 254 can be used to connect to the service. data. In other words, 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.
Capabilities参数中还有“scalable”参数。scalable参数定义了实例化部署节点2时所需要的实例的个数,其中“Min_instance”定义的是最小实例化个数,“Max_instance”定义的是最大实例化个数。There is also a "scalable" parameter in the Capabilities parameter. 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.
对所述NSD的第二种描述方法可以是:A second method of describing the NSD can be:
Figure PCTCN2015087807-appb-000004
Figure PCTCN2015087807-appb-000004
Figure PCTCN2015087807-appb-000005
Figure PCTCN2015087807-appb-000005
Figure PCTCN2015087807-appb-000006
Figure PCTCN2015087807-appb-000006
上述第二种描述方法同样为YAML语言版本的TOSCA规范。其中,在对节点1的描述中,与前面的第一种描述方法不同的是,在capabilities参数下不仅增加了Loadbalance参数,在Loadbalance参数下还新增了class参数,用于表示节点1所支持的负载均衡模型的优先级别。例如:在本实施例中,class的值为1,说明对应的E2E模型的优先级最低。换言之,第一VNFD包括第一VNF支持的LB的类型信息以及每种类型的优先级信息。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. For example, in this embodiment, the value of class is 1, indicating that the corresponding E2E model has the lowest priority. In other words, the first VNFD includes type information of the LB supported by the first VNF and priority information of each type.
在对节点2的描述中,与前面的第一种描述方法不同的是,在requirements参数下新增Loadbalance参数,用来表示节点2对负载均衡模型的需求。该需要是对虚拟业务提供设备提出的需求,即希望虚拟业务提供设备提供怎样的负载均衡器。In the description of node 2, unlike the first method described above, 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.
节点2中标示的infrastructure模型的class为“2”,external模型的class为“3”。换言之,第二VNFD包括第二VNF需求的LB的类型信息,以及每种类型的优先级信息。The class of the infrastructure model indicated in node 2 is "2", and the class of the external model is "3". In other words, the second VNFD includes type information of the LB of the second VNF demand, and priority information of each type.
在实际运用中,NSD还包括其他信息,例如NSD的标识信息、生产厂商、版本号、弹性策略、生命周期管理、部署喜好等。这些信息为本领域技术人员所熟知的内容,所以在此不再赘述。In practice, 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.
在一实施例中,在步骤102中,业务提供设备根据实例化请求获取所述业务的NSD。具体来说,实例化请求中携带有该业务的NSD,所以业务提供设备通过分析所述实例化请求即可获得所述NSD。In an embodiment, in step 102, the service providing device acquires the NSD of the service according to the instantiation request. Specifically, the instantiation request carries the NSD of the service, so the service providing device can obtain the NSD by analyzing the instantiation request.
在另一实施例中,在步骤101之前,所述方法还包括:业务提供设备接收 业务请求设备发送的关于所述业务的注册(on-boarding)请求,在该请求中携带所述业务的NSD。业务提供设备将所述NSD信息发送至数据库进行保存。在数据保存完成后,数据库向业务提供设备返回保存成功响应。业务提供设备向业务请求设备发送注册成功响应。在该情况下,在步骤101中,实例化请求中会携带NSD的标识信息。步骤102具体包括:业务提供设备根据实例化请求中携带的NSD的标识信息向数据库获取与该标识信息对应的NSD。在数据库根据该标识信息查询到保存的NSD,业务提供设备接收数据库返回的所述NSD。In another embodiment, before step 101, 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. In this case, in step 101, 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.
因此,对应在业务请求设备侧提供的一种业务的实例化的部署方法包括:业务请求设备向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的NSD的标识信息或者所述NSD。Therefore, 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.
接下来执行步骤103,即业务提供设备获取所述业务提供设备支持的LB类型的信息。其中,所述业务提供设备支持的LB类型的信息例如是存储在存储单元中,业务提供设备通过查询即可获得。Next, 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.
接下来执行步骤104,即业务提供设备根据对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型。Next, 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.
可选的,当所述对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,步骤103包括:业务提供设备根据所述需求的LB的类型信息和业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,业务提供设备根据优先级信息确定共同的LB类型中的优先级最高的LB类型作为所述所使用的LB类型。其中,所述需求的LB的类型信息为第一VNFD中包含的第一VNF需求的LB的类型信息,或第二VNFD中包含的第二VNF需求的LB的类型信息。Optionally, when the description information of the LB type is the type information of the required LB, and the priority information of each type, 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.
继续以前述第一种和第二种描述方式描述的NSD为例进行说明。假设虚拟业务提供设备既支持外设类型,也支持基于基础设施的类型的负载均衡模 型。那么业务提供设备确定出的共同的LB类型为外设类型和基于基础设施的类型。在对LB类型的描述信息中,外设类型的LB的优先级最高,那么业务提供设备就确定外设类型为所述所使用的LB类型。The NSD described in the foregoing first and second descriptions will be described as an example. Assume that the virtual service provider supports both the peripheral type and the infrastructure-based type of load balancing module. type. Then the common LB type determined by the service providing device is a peripheral type and an infrastructure based type. In the description information of the LB 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.
如前所述,当对LB类型的描述信息还包括支持的LB的类型信息时,可选的,还包括支持的LB的每种类型的优先级。在该情况下,方法还包括:业务提供设备根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;业务提供设备确定支持的LB的类型作为所述所使用的LB类型。其中,所述支持的LB的类型信息为第一VNFD中包括的第一VNF支持的LB的类型信息。As described above, when the description information of the LB type further includes the type information of the supported LB, optionally, each type of priority of the supported LB is also included. In this case, 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.
举例来说,假设虚拟业务提供设备既不支持外设类型,也不支持基于基础设施的类型的负载均衡模型,则确定E2E类型为所述所使用的LB类型。换言之,在该业务实例化部署时,虚拟业务提供设备不提供任何负载均衡器,节点1和节点2之间使用E2E类型的负载均衡器,即使用节点1所携带的LB。For example, assuming that 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. In other words, when the service is instantiated, 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.
当确定了所使用的LB类型,接下来执行步骤105,即业务提供设备获取所述所使用的LB类型的LB的描述信息。根据确定的所使用的LB的类型的不同,步骤104的具体实施方式也不相同,下面将分别举例进行说明。When the LB type used is determined, 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.
当所述所使用的LB类型为外设LB类型时,步骤105包括:业务提供设备向数据库发送查询可用的外设LB类型的LB实例的请求;如果有,数据库会返回可用的LB实例的地址信息,对应的,业务提供设备将接收到的数据库返回的可用的LB实例的地址信息作为所述LB的描述信息。可选的,除了地址信息,LB的描述信息还可以包括其他信息,例如LB的最大处理容量(比如可连接的实例个数),处理时间等信息。其中,在本申请所有实施例中,可用的LB实例是指在查询的时刻能够使用的LB实例,例如处于空闲状态的LB实例。When the used LB type is a peripheral LB type, 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. Optionally, in addition to the address information, 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. In all the embodiments of the present application, 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.
因为可能在实例化所述业务之前,在其他业务实例化的过程中,生成了外 设LB类型的LB实例,所以可以先向数据库查询是否有可用的外设LB类型的LB实例。Because it may be generated during the process of instantiating other services before the business is instantiated. Set the LB instance of the LB type, so you can first query the database for the available LB instance of the peripheral LB type.
可选的,当数据库没有可用的LB实例时,数据库就会返回可用的LB实例的虚拟网络功能描述信息VNFD,对应的,该方法还包括:业务提供设备接收数据库返回的可用的LB实例的VNFD;业务提供设备根据所述LB实例的VNFD向虚拟网络功能管理器(英文:Virtualized Network Function Manager,简称:VNFM)发起实例化外设LB的请求;业务提供设备将接收到的VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。其中,实例化外设LB的请求中需要包含所述LB实例的VNFD。Optionally, 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. Correspondingly, 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.
具体来说,如果数据库中没有可用的外设LB的实例,那么就需要重新实例化一个外设LB的实例,然后在实例化完成之后,业务提供设备获取到该外设LB的实例的地址信息作为所述LB的描述信息。Specifically, if there is no instance of the peripheral LB available in the database, then an instance of a peripheral LB needs to be instantiated, and then after the instantiation is completed, the service providing device obtains the address information of the instance of the peripheral LB. As the description information of the LB.
可选的,在一实施例中,业务请求设备可以事先在业务的实例化请求发起之前,将外设类型的LB的VNFD注册到业务提供设备。在业务的实例化过程中,对LB类型的描述信息中还包括所述VNFD的标识信息。因此,考虑到这种情况,在业务提供设备向数据库查询是否有可用的外设LB类型的LB实例之前,该方法还包括:业务提供设备确定所述对LB类型的描述信息中未包含所述外设LB类型的VNFD的标识信息。换言之,就是在没有事先注册VNFD的情况下,才向数据库发送查询可用的外设LB类型的LB实例的请求。Optionally, in an embodiment, 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. In the instantiation process 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.
可选的,当所述对LB类型的描述信息中包含所述外设LB类型的VNFD的标识信息时,就说明事先已注册过外设LB的VNFD,所以步骤105包括:业务提供设备根据所述标识信息获取与所述标识信息对应的VNFD;业务提供设备根据所述VNFD向VNFM发起实例化外设LB的请求;业务提供设备将接收到的VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。其中,实例化 外设LB的请求包括所述VNFD。Optionally, when the description information of the LB type includes the identifier information of the VNFD of the peripheral LB type, it indicates that the VNFD of the peripheral LB has been registered in advance, so 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.
当所述所使用的LB类型为基于基础设施的LB类型时,步骤105具体包括:业务提供设备向VIM发起为所述业务分配基于基础设施的LB的请求;业务提供设备将接收到的VIM发送的可用的基于基础设施的LB的地址信息作为所述LB的描述信息。When the LB type used is an infrastructure-based LB type, 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之间具有“虚拟资源管理”接口。该接口由VIM提供。业务提供设备可以使用该接口向VIM发送资源管理的请求,比如资源的分配,资源的查询,资源的更新,资源的迁移,资源的释放等。但是该接口更多的是提供对业务中VNF资源的管理,比如为某个VNF分配资源以及资源的更新和释放等。在业务提供设备向VIM发起为所述业务分配基于基础设施的LB的请求的步骤中,需要VIM分配基于基础设施的负载均衡器,并不是为VNF本身分配负载均衡器资源,所以需要在业务提供设备和VIM之间使用新的接口来传递负载均衡器的分配请求。在本实施例中,可以定义新的接口名称为“基于基础设施负载均衡器管理”接口。该接口用于业务提供设备向VIM申请基于基础设施负载均衡器的操作,比如申请新的负载均衡器,更新负载均衡器,负载均衡器预留,删除负载均衡器等。步骤105中,使用新的接口向VIM申请分配新的负载均衡器。Generally speaking, there is a "virtual resource management" interface between the service providing device and the VIM. This interface is provided by VIM. 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. However, 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. In the step of the service providing device initiating a request for the VIM to allocate an infrastructure-based LB for the service, 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. In this embodiment, 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. In step 105, the new interface is used to allocate a new load balancer to the VIM.
在VIM接收到分配请求之后,就向基础设施层请求分配基于基础设施的LB。基础设施层然后向VIM返回可用的基于基础设施的LB的地址信息。然后VIM向业务提供设备返回所述地址信息。然后业务提供设备将所述地址信息作为所述LB的描述信息。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.
需要说明的是,当确定的所使用的LB类型为基于基础设施的LB类型时, 另一种可能的实施方式为将连接请求和分配请求合一。具体来说,在步骤104之后,不需要执行步骤105,并且在步骤106中,业务提供设备在接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将连接信息和端口能力信息发送给VIM。那么VIM在接收到连接信息和端口能力信息之后,先向基础设施层请求分配基于基础设施的LB。基础设施层然后向VIM返回可用的基于基础设施的LB的地址信息。然后VIM根据LB的地址信息、连接信息和端口能力信息将所述LB连接在第一VNF的实例和第二VNF的实例之间。It should be noted that when the determined LB type used is an infrastructure-based LB type, Another possible implementation is to unify the connection request and the allocation request. Specifically, after 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. Then, after receiving the connection information and port capability information, 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.
当确定的所使用的LB类型为E2E类型时,因为E2E类型的LB为第一VNF的一部分,在第一VNFD中会携带该LB的LB的描述信息,例如为该LB的地址信息。因此步骤105包括:业务提供设备在第一VNFD中获取E2E类型的LB的LB的描述信息。When the determined LB type is the E2E type, because the LB of the E2E type is part of the first VNF, the description information of the LB of the LB, for example, the address information of the LB, is carried in the first VNFD. Therefore, the step 105 includes: the service providing device acquiring, in the first VNFD, description information of the LB of the E2E type LB.
在步骤105中获取到所使用的LB类型的LB的描述信息之后,并且在接收到第一VNF和第二VNF都实例化成功的响应消息后,接下来执行步骤106,即业务提供设备将所述LB的描述信息发送给VIM,以使VIM能够根据所述连接信息、端口能力信息和所述LB的描述信息将所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。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.
具体来说,VIM接收业务提供设备发送的连接请求,在该连接请求中包括业务提供设备在步骤106中所发送的信息。VIM根据所述连接信息,可知第一VNF和第二VNF需要连接,所以将第一VNF的实例同LB相连。VIM再根据第二VNF的端口能力信息,根据端口的功能信息将LB上与所述端口的功能信息相对应的接口与第二VNF上对应的功能的端口连接。例如:LB上用于传输负载检测相关的接口同第二VNF上“usage”为“loadbalance”的端口相连。LB 上用于转发第一VNF发送过来的数据接口同第二VNF上“usage”为“data”的端口相连。可选的,在连接完成后,VIM向业务提供设备发送连接完成的响应消息。Specifically, 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. Optionally, after the connection is completed, the VIM sends a response message to the service providing device to complete the connection.
进一步,业务提供设备在接收到连接完成的响应消息之后,向业务请求设备发送实例化完成响应。对应的,业务请求设备接收所述实例化完成响应。Further, 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.
由以上描述可以,通过本申请实施例中的方法,能够在业务的实例化的部署过程中,确定所使用的LB类型,并将所使用的LB类型的LB连接在两个VNF的实例之间。According to the foregoing description, by using the method in the embodiment of the present application, 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. .
以下举几个具体的例子说明本申请实施例中的负载均衡器的连接方法的具体实施过程。Several specific examples are given below to illustrate the specific implementation process of the connection method of the load balancer in the embodiment of the present application.
第一例,请参考图4所示,为本实施例中负载均衡器的连接方法的流程图。该方法包括如下内容。For the first example, please refer to FIG. 4, which is a flowchart of a method for connecting a load balancer in this embodiment. The method includes the following.
步骤201:业务请求设备向虚拟业务提供设备发送业务的注册(on boarding)请求。该请求中包含该业务的NSD。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.
接下来执行步骤202:当业务提供设备接收到注册请求之后,将请求中的NSD发送给数据库进行保存。Next, 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.
步骤203:数据库保存完成之后,向业务提供设备返回保存成功响应。Step 203: After the database is saved, return a save success response to the service providing device.
步骤204:业务提供设备在接收到数据库发送的保存成功响应之后,向业务请求设备发送注册成功响应。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.
步骤205:业务请求设备向业务提供设备发起关于该业务的实例化请求。在该请求中携带该业务的NSD对应的标识信息。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.
步骤206:业务提供设备根据NSD的标识信息向数据库获取NSD。Step 206: The service providing device acquires the NSD from the database according to the identifier information of the NSD.
步骤207:数据库根据NSD的标识信息查询到NSD,并将NSD返回给业务提供设备。 Step 207: The database queries the NSD according to the NSD identification information, and returns the NSD to the service providing device.
步骤208:业务提供设备对NSD进行分析,根据该NSD对节点1和节点2发起实例化请求的流程。具体来说,业务提供设备针对节点1向虚拟网络功能管理器(英文:Virtualised Network Function Manager,简称:VNFM)发送实例化该节点1的请求。在该请求中包含节点1的VNFD标识。VNFM根据VNFD的标识向数据库查询节点1的VNFD。然后数据库在查询到节点1的VNFD之后,将VNFD返回给VNFM。VNFM根据VNFD向业务提供设备申请资源。资源包括节点1需要的中央处理器(英文:Central Processing Unit,简称:CPU)资源、存储资源等。业务提供设备将资源申请请求发送给VIM,要求VIM为节点1分配相应的资源。VIM向网络功能虚拟化基础设施(英文:Network Functions Virtualization Infrastructure,简称:NFVI)层申请需要的资源。NFVI在确认资源分配成功后,返回资源的地址等信息。VIM向业务提供设备确认资源分配成功,并返回资源的地址等信息。业务提供设备向VNFM确认资源分配成功,并返回资源的地址等信息。VNFM根据分配的资源在分配的地址上创建节点1的实例。业务提供设备确定节点1实例化成功。然后重复上述步骤,对节点2进行实例化。对节点1和节点2的实例化过程为本领域技术人员所熟知的内容,所以在此不再赘述。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. 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 be described herein.
步骤209:业务提供设备对NSD中包含的负载均衡模型相关的描述信息做判断。在本实施例中,外设负载均衡模型的优先级最高(前述描述实例中class为3,所以优先级最高),业务提供设备所在的云平台也支持外设负载均衡模型,那么就确定外设类型的LB作为节点1的实例和节点2的实例之间的LB。Step 209: The service providing device determines the description information related to the load balancing model included in the NSD. In this embodiment, 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.
步骤210:业务提供设备向数据库发送查询其所在的云平台是否有可用的外设负载均衡器的实例。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.
步骤211:如果有查询到可用的外设负载均衡器的实例,数据库则向业务提供设备返回该实例的地址等信息。如果没有可用的实例,则返回可用的外设 负载均衡器的描述信息,即外设负载均衡器的VNFD。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.
步骤212:如果数据库返回的是外设负载均衡器的VNFD,业务提供设备则使用该VNFD向VNFM发起实例化一个对应的外设LB实例的请求。在该请求中携带该VNFD。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.
步骤213:业务提供设备接收VNFM返回的外设LB实例的地址信息。Step 213: The service providing device receives the address information of the peripheral LB instance returned by the VNFM.
步骤214:当节点1和节点2都实例化之后,业务提供设备向VIM请求建立VNF之间的连接,即节点1和节点2的连接。还建立节点2的实例和外设负载均衡器实例之间的连接。在该请求中包括外设LB实例的地址信息、连接信息和端口能力信息。在本实施例中,节点1的实例先和负载均衡器的实例相连,负载均衡器在与节点2的多个实例相连。其中,负载均衡器上用于传输负载检测相关的接口同节点2上“usage”为“Loadbalance”的“Endpoint”相连,负载均衡器上用于转发节点1发送过来的数据接口同节点2上“usage”为“data”的“Endpoint”相连。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. In this embodiment, 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".
步骤215:当建立完成之后,VIM向业务提供设备发送完成响应。Step 215: After the establishment is completed, the VIM sends a completion response to the service providing device.
步骤216:业务提供设备向业务请求设备发送实例化完成响应。Step 216: The service providing device sends an instantiation completion response to the service requesting device.
第二例,在本实施例中,业务请求设备设置外设负载均衡模型的优先级最高,当虚拟业务提供设备支持外设负载均衡模型时,在部署过程中会为该业务提供外设负载均衡器。在本实施例中还假设该外设类型的负载均衡器是由请求方提供。因此,请求方在发起注册请求之前将外设类型的负载均衡器的VNFD注册到虚拟业务提供设备。并在业务实例化时,携带该负载均衡器的VNFD的标识信息,指明需要使用该负载均衡器。虚拟业务提供设备会根据请求中的VNFD的标识信息,找到对应的LB的VNFD,并使用该对应的LB的VNFD实例化负载均衡器的实例,并使用该实例为请求的业务提供负载均衡功能。具体请参考图5所示,为本实施例中负载均衡器的连接方法的流程图。该方法包括以下内容。 In the second example, in this embodiment, the service requesting device sets the peripheral load balancing model with the highest priority. When the virtual service providing device supports the peripheral load balancing model, the peripheral load balancing is provided for the service during the deployment process. Device. It is also assumed in this embodiment that 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. For details, please refer to FIG. 5, which is a flowchart of a method for connecting a load balancer in this embodiment. The method includes the following.
步骤301:业务请求设备发起注册LB的请求。该注册请求中携带该LB的VNFD。该LB的构成及组件都由业务请求设备提供。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.
该VNFD的一种可能的描述方式为:One possible way to describe this VNFD is:
Figure PCTCN2015087807-appb-000007
Figure PCTCN2015087807-appb-000007
其中,“LB123”为该节点模板的标识,即VNFD的标识信息。该节点模板是一个负载均衡器类型的节点。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.
步骤302:业务提供设备将收到的VNFD发送至数据库进行保存。Step 302: The service providing device sends the received VNFD to the database for storage.
步骤303:数据库在保存完成之后向业务提供设备发送保存完成响应。Step 303: The database sends a save completion response to the service providing device after the saving is completed.
步骤304:业务提供设备向业务请求设备发送注册完成响应。Step 304: The service providing device sends a registration completion response to the service requesting device.
步骤305:业务请求设备发起网络服务的注册请求。该请求信息中包含的NSD与第一例中基本相同。不同的是在“external”负载均衡器的需求下面又 增加了该负载均衡器的VNFD的标识信息。如果采用步骤201中第一种描述方式的话,可以是: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:
Figure PCTCN2015087807-appb-000008
Figure PCTCN2015087807-appb-000008
如上所述,新增了“ref_Node_ID”参数。该参数携带一个“external”类型的负载均衡器的VNFD的标识信息,即LB123。该标识信息即对应步骤301中需要保存在数据库上的负载均衡器的VNFD。As mentioned above, the "ref_Node_ID" parameter has been added. 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.
接下来的步骤与第一例基本相同,不同的是,业务提供设备需要确定VNFD的标识信息对应的负载均衡器作为该网络服务的负载均衡器。因此,业务提供设备需要根据VNFD的标识信息,即“LB123”向数据库请求该标识信息对应的VNFD。数据库在查询到该VNFD后发送给业务提供设备。然后业务提供设备使用该VNFD向VNFM发起实例化该负载均衡器的流程。接下来的步骤与第一例相同,在此不再赘述。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 then 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.
第三例,在本实施例中,业务请求设备设置基于基础设施的负载均衡模型的优先级最高。当虚拟业务提供设备支持基于基础设施负载均衡模型时,在部署过程中会为该业务提供基于基础设施的负载均衡器。请参考图6所示,为本实施例中负载均衡连接方法的流程图。该方法包括以下内容。In the third example, in the present embodiment, the service requesting device sets the infrastructure-based load balancing model with the highest priority. When a virtual service provisioning device supports an infrastructure-based load balancing model, an infrastructure-based load balancer is provided for the service during deployment. Please refer to FIG. 6 , which is a flowchart of a load balancing connection method in this embodiment. The method includes the following.
步骤401与步骤201基本相同,不同的是在NSD中,“infrastructure”类型的class设置为“3”,即基于基础设施的负载均衡模型的优先级最高。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.
步骤402-步骤408与步骤201-步骤208基本相同,在此不再赘述。Steps 402 to 408 are substantially the same as steps 201 to 208, and details are not described herein again.
步骤409:因为假设业务提供设备也支持基于基础设施的LB,所以根据NSD中的需求信息确定LB类型为基于基础设施的LB。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.
步骤410:业务提供设备向VIM发起请求,为当前业务选择基于基础设 施的LB类型。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.
步骤411:VIM向基础设施层请求分配负载均衡器。Step 411: The VIM requests the infrastructure layer to allocate a load balancer.
步骤412:基础设施层向VIM返回基于基础设施的负载均衡器的地址等信息。Step 412: The infrastructure layer returns information such as the address of the infrastructure-based load balancer to the VIM.
步骤413:VIM向业务提供设备返回基于基础设施的负载均衡器的地址等信息。Step 413: The VIM returns information such as an address of the infrastructure-based load balancer to the service providing device.
步骤414:业务提供设备向VIM请求VNF实例之间的连接。其中包括业务中相关的VNF同选择的基于基础设施的负载均衡器的连接。在本实施例中,节点1的实例先同负载均衡器相连。负载均衡器再同节点2的多个实例相连。其中负载均衡器上用于传输负载检测相关的接口同节点2上“usage”为“Loadbalance”的“Endpoint”相连。负载均衡器上用于转发节点1发送过来的数据接口同节点2上“usage”为“data”的“Endpoint”相连。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. In this embodiment, 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.
步骤415:VIM完成连接的建立,向业务提供设备返回完成响应。Step 415: The VIM completes the establishment of the connection, and returns a completion response to the service providing device.
步骤416:业务提供设备向业务请求设备返回实例化完成响应。Step 416: The service providing device returns an instantiation completion response to the service requesting device.
基于同一发明构思,请参考图7所示,为本申请实施例提供的一种LB的连接装置的功能框图。该装置用于实现如图3及其实施例所述的LB的连接方法。如图7所示,该连接装置包括:接收单元501,用于接收业务请求设备发送的关于业务的实例化请求;处理单元502,用于根据实例化请求获取业务的网络服务描述信息NSD;NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和第一VNF和第二VNF之间的连接信息;第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,第二VNFD还包括第二VNF的端口能力信息;获取装置支持的LB类型的信息;根据对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型;并获取所使用的LB类型的LB的描述信息;发送单元503,用于在接收单 元501接收到第一VNF和第二VNF都实例化成功的响应消息后,将LB的描述信息、连接信息和端口能力信息发送给虚拟基础设施管理器VIM,以使VIM能够根据LB的描述信息、连接信息和端口能力信息将所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。Based on the same inventive concept, please refer to FIG. 7 , which 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. LB type; and obtain description information of the LB of the used LB type; the sending unit 503 is used to receive the order After receiving the response message that the first VNF and the second VNF are successfully instantiated, 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.
可选的,处理单元502具体用于:当对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,Optionally, 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,
根据需求的LB的类型信息和业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,根据优先级信息确定共同的LB类型中的优先级最高的LB类型作为所使用的LB类型;其中,需求的LB的类型信息为第一VNFD中包含的第一VNF需求的LB的类型信息,或第二VNFD中包含的第二VNF需求的LB的类型信息。Determining whether there is a 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; if yes, determining the LB type with the highest priority among the common LB types as the used LB according to the priority information 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.
可选的,处理单元502还用于:当当所述对LB类型的描述信息还包含支持的LB的类型信息时,根据需求的LB的类型信息和业务提供设备支持的LB类型的信息确定没有共同的LB类型;确定第一VNF支持的LB的类型作为所使用的LB类型;其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。Optionally, 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 .
可选的,处理单元502具体用于:当所使用的LB类型为外设LB类型时,Optionally, the processing unit 502 is specifically configured to: when the used LB type is a peripheral LB type,
通过发送单元503向数据库发送查询可用的外设LB类型的LB实例的请求;Sending, by the sending unit 503, a request for querying an available LB instance of the peripheral LB type to the database;
将通过接收单元501接收到的数据库返回的可用的LB实例的地址信息作为LB的描述信息;或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
通过接收单元501接收数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;根据LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外 设LB的请求;将通过接收单元501接收到的VNFM发送的外设LB实例的地址信息作为LB的描述信息。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.
可选的,处理单元502还用于:在通过发送单元503向数据库发送查询可用的外设LB类型的LB实例的请求之前,确定对LB类型的描述信息中未包含外设LB类型的虚拟网络功能描述信息VNFD的标识信息。Optionally, 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.
可选的,处理单元502具体用于:当所使用的LB类型为外设LB类型时,确定对LB类型的描述信息中包含外设LB类型的虚拟网络功能描述信息VNFD的标识信息;根据标识信息获取与标识信息对应的VNFD;根据VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;并将通过接收单元501接收到的VNFM发送的外设LB实例的地址信息作为LB的描述信息。Optionally, 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 .
可选的,处理单元502具体用于:当所使用的LB类型为基于基础设施的LB类型时,通过发送单元503向VIM发起为业务分配基于基础设施的LB类型的LB的请求;并将通过接收单元501接收到的VIM发送的可用的基于基础设施的LB的地址信息作为LB的描述信息。Optionally, 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.
可选的,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。Optionally, the port capability information includes a port number of the port of the second VNF and function information of the port.
前述图3实施例中的LB的连接方法中的各种变化方式和具体实例同样适用于本实施例的LB的连接装置,通过前述对LB的连接方法的详细描述,本领域技术人员可以清楚的知道本实施例中LB的连接装置的实施方法,所以为了说明书的简洁,在此不再详述。The various changes and specific examples in the 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.
基于同一发明构思,请参考图8所示,为本申请实施例提供的一种业务提供设备的***框图。用于实现如图3及其实施例所述的LB的连接方法。如图8所示,该业务提供设备包括:接收器601,用于接收业务请求设备发送的关于 业务的实例化请求;处理器602,用于根据实例化请求获取业务的网络服务描述信息NSD;NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和第一VNF和第二VNF之间的连接信息;第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,第二VNFD还包括第二VNF的端口能力信息;获取装置支持的LB类型的信息;根据对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型;并获取所使用的LB类型的LB的描述信息;发送器603,用于在接收器601接收到第一VNF和第二VNF都实例化成功的响应消息时,将LB的描述信息、连接信息和端口能力信息发送给虚拟基础设施管理器VIM,以使VIM能够根据LB的描述信息、连接信息和端口能力信息将所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。Based on the same inventive concept, please refer to FIG. 8 , which is a system block diagram of a service providing device according to an embodiment of the present application. A connection method for realizing the LB as described in FIG. 3 and its embodiments. As shown in FIG. 8, 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 of the LB of the used LB type; the transmitter 603 is configured to When receiving the response message that the first VNF and the second VNF are successfully instantiated, the receiver 601 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 described according to the LB. The information, connection information, and 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.
可选的,处理器602具体用于:当对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,Optionally, 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,
根据需求的LB的类型信息和业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,根据优先级信息确定共同的LB类型中的优先级最高的LB类型作为所使用的LB类型;其中,需求的LB的类型信息为第一VNFD中包含的第一VNF需求的LB的类型信息,或第二VNFD中包含的第二VNF需求的LB的类型信息。Determining whether there is a 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; if yes, determining the LB type with the highest priority among the common LB types as the used LB according to the priority information 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.
可选的,处理器602还用于:当所述对LB类型的描述信息还包含支持的LB的类型信息时,根据需求的LB的类型信息和业务提供设备支持的LB类型的信息确定没有共同的LB类型;确定第一VNF支持的LB的类型作为所使用的LB类型;其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF 支持的LB的类型信息。Optionally, 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.
可选的,处理器602具体用于:当所使用的LB类型为外设LB类型时,Optionally, the processor 602 is specifically configured to: when the used LB type is a peripheral LB type,
通过发送器603向数据库发送查询可用的外设LB类型的LB实例的请求;Sending, by the sender 603, a request for querying an available LB instance of the peripheral LB type to the database;
将通过接收器601接收到的数据库返回的可用的LB实例的地址信息作为LB的描述信息;或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
通过接收器601接收数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;根据LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;将通过接收器601接收到的VNFM发送的外设LB实例的地址信息作为LB的描述信息。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.
可选的,处理器602还用于:在通过发送器603向数据库发送查询可用的外设LB类型的LB实例的请求之前,确定对LB类型的描述信息中未包含外设LB类型的虚拟网络功能描述信息VNFD的标识信息。Optionally, 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.
可选的,处理器602具体用于:当所使用的LB类型为外设LB类型时,确定对LB类型的描述信息中包含外设LB类型的虚拟网络功能描述信息VNFD的标识信息;根据标识信息获取与标识信息对应的VNFD;根据VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;并将通过接收器601接收到的VNFM发送的外设LB实例的地址信息作为LB的描述信息。Optionally, 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 .
可选的,处理器602具体用于:当所使用的LB类型为基于基础设施的LB类型时,通过发送器603向VIM发起为业务分配基于基础设施的LB类型的LB的请求;并将通过接收器601接收到的VIM发送的可用的基于基础设施的LB的地址信息作为LB的描述信息。Optionally, 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.
可选的,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。 Optionally, the port capability information includes a port number of the port of the second VNF and function information of the port.
进一步,在图8中,总线架构(用总线600来代表),总线600可以包括任意数量的互联的总线和桥,总线600将包括由处理器602代表的一个或多个处理器和存储器604代表的存储器的各种电路链接在一起。总线600还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口605在总线600和处理器602、接收器601、发送器603之间提供接口。接收器601和发送器603用于业务提供设备与外部设备进行数据通信。Further, in FIG. 8, a bus architecture (represented by bus 600), 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.
处理器602负责管理总线600和通常的处理。存储器604可以被用于存储处理器602在执行操作时所使用的数据。 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.
前述图3实施例中的LB的连接方法中的各种变化方式和具体实例同样适用于本实施例的业务提供设备,通过前述对LB的连接方法的详细描述,本领域技术人员可以清楚的知道本实施例中业务提供设备的实施方法,所以为了说明书的简洁,在此不再详述。The various changes and specific examples in the foregoing method for connecting the LB in the embodiment of FIG. 3 are also applicable to the service providing device in this embodiment. The foregoing detailed description of the connection method of the LB can be clearly known by those skilled in the art. The method for implementing the service providing device in this embodiment is not detailed here for the sake of brevity of the description.
基于同一发明构思,请参考图9所示,为本申请实施例提供的一种业务的实例化部署装置的功能框图。该装置用于实施例前述业务请求设备侧的业务的实例化部署方法。如图9所示,该业务的实例化部署装置包括:发送单元701,用于向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;接收单元702,用于接收所述业务提供设备发送的所述业务的实例部署成功的响应消息。 Based on the same inventive concept, please refer to FIG. 9 , which 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; and 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.
可选的,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。Optionally, 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 type information of the LB of the first VNF requirement, 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 first VNFD Type information of the LB supported by the first VNF included in the first VNF.
可选的,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。Optionally, the port capability information includes a port number of the port of the second VNF and function information of the port.
前述实施例中已详细描述业务的实例化部署方法的实施例过程,通过前述对业务的实例化部署方法的详细描述,本领域技术人员可以清楚的知道本实施例中业务实例化部署装置的实施方法,所以为了说明书的简洁,在此不再详述。The embodiment process of the instantiated deployment method of the service has been described in detail in the foregoing embodiment. Through the foregoing detailed description of the instantiation deployment method of the service, those skilled in the art can clearly understand the implementation of the service instantiation deployment device in this embodiment. Method, so for the sake of brevity of the description, it will not be described in detail here.
基于同一发明构思,请参考图10所示,为本申请实施例提供的一种业务请求设备的***框图。该业务请求设备用于实施例前述业务请求设备侧的业务的实例化部署方法。如图10所示,该业务请求设备包括:发送器801,用于向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;接收器802,用于接收所述业务提供设备发送的所述业务的实例部署成功的响应消息。Based on the same inventive concept, please refer to FIG. 10, which 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. As shown in FIG. 10, 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. Information 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 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, and 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.
可选的,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述 第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。Optionally, 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.
可选的,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。Optionally, the port capability information includes a port number of the port of the second VNF and function information of the port.
进一步,在图10中,总线架构(用总线800来代表),总线800可以包括任意数量的互联的总线和桥,总线800将包括由处理器803代表的一个或多个处理器和存储器804代表的存储器的各种电路链接在一起。总线800还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口805在总线800和处理器803、接收器802、发送器801之间提供接口。接收器802和发送器801用于业务请求设备与外部设备进行数据通信。Further, in FIG. 10, a bus architecture (represented by bus 800), 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.
处理器803负责管理总线800和通常的处理。存储器804可以被用于存储处理器803在执行操作时所使用的数据。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.
前述实施例中已详细描述业务的实例化部署方法的实施例过程,通过前述对业务的实例化部署方法的详细描述,本领域技术人员可以清楚的知道本实施例中业务实例化部署装置的实施方法,所以为了说明书的简洁,在此不再详述。The embodiment process of the instantiated deployment method of the service has been described in detail in the foregoing embodiment. Through the foregoing detailed description of the instantiation deployment method of the service, those skilled in the art can clearly understand the implementation of the service instantiation deployment device in this embodiment. Method, so for the sake of brevity of the description, it will not be described in detail here.
基于同一发明构思,请参考图11所示,为本申请实施例提供的一种LB的连接装置的功能框图。该LB的连接装置用于实施VIM侧的LB的连接方法。如图11所示,该LB的连接装置包括:接收单元901,用于接收业务提供设备发送的连接请求,连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类型的LB的描述信息、第一VNF和第二 VNF之间的连接信息以及第二VNF的端口能力信息,端口能力信息包括第二VNF的端口的端口号和端口的功能信息;处理单元902,用于根据连接信息和LB的描述信息将第一VNF的实例与LB连接,并根据端口的功能信息将LB上与端口的功能信息相对应的接口与第二VNF上对应的功能的端口连接。Based on the same inventive concept, please refer to FIG. 11 , which 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. As shown in FIG. 11, 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 The connection information between the VNF and the port capability information of the second VNF, the port capability information includes the port number of the port of the second VNF and the function information of the port, and the processing unit 902 is configured to perform the first according to the connection information and the description information of the LB. 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.
可选的,该装置还包括发送单元903,用于向业务提供设备发送连接完成的响应消息。Optionally, the device further includes a sending unit 903, configured to send, to the service providing device, a response message that the connection is completed.
可选的,接收单元901还用于:当LB类型为基于基础设施的LB类型时,在接收单元901接收连接请求之前,接收业务提供设备发送的为业务分配基于基础设施的LB的请求;Optionally, 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;
处理单元902还用于:根据为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配基于基础设施的LB的请求;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;
接收单元901还用于:接收基础设施层返回的可用的基于基础设施的LB的地址信息;The receiving unit 901 is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
发送单元903还用于:将可用的基于基础设施的LB的地址信息发送给业务提供设备;其中,LB的描述信息包括可用的基于基础设施的LB的地址信息。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.
前述实施例中已详细描述LB的连接方法的实施例过程,通过前述对LB的连接方法的详细描述,本领域技术人员可以清楚的知道本实施例中LB的连接装置的实施方法,所以为了说明书的简洁,在此不再详述。The embodiment process of the connection method of the LB has been described in detail in the foregoing embodiments. Through the foregoing detailed description of the connection method of the LB, 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.
基于同一发明构思,请参考图12所示,为本申请实施例提供的一种VIM的***框图。该VIM用于实施VIM侧的LB的连接方法。如图12所示,该VIM包括:接收器1001,用于接收业务提供设备发送的连接请求,连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类 型的LB的描述信息、第一VNF和第二VNF之间的连接信息以及第二VNF的端口能力信息,端口能力信息包括第二VNF的端口的端口号和端口的功能信息;处理器1002,用于根据连接信息和LB的描述信息将第一VNF的实例与LB连接,并根据端口的功能信息将LB上与端口的功能信息相对应的接口与第二VNF上对应的功能的端口连接。Based on the same inventive concept, please refer to FIG. 12 , which 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. As shown in FIG. 12, 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. LB class The description information of the type LB, the connection information between the first VNF and the second VNF, and the port capability information of the second VNF, the port capability information includes the port number of the port of the second VNF and the function information of the port; the processor 1002, And configured to connect the instance of the first VNF to the LB according to the connection information and the description information of the LB, and connect the interface corresponding to the function information of the port on the LB to the port of the corresponding function on the second VNF according to the function information of the port.
可选的,VIM还包括发送器1003,用于向业务提供设备发送连接完成的响应消息。Optionally, the VIM further includes a sender 1003, configured to send a connection completion response message to the service providing device.
可选的,接收器1001还用于:当LB类型为基于基础设施的LB类型时,在接收器1001接收连接请求之前,接收业务提供设备发送的为业务分配基于基础设施的LB的请求;Optionally, 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;
处理器1002还用于:根据为业务分配基于基础设施的LB的请求向基础设施层发送分配基于基础设施的LB的请求;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;
接收器1001还用于:接收基础设施层返回的可用的基于基础设施的LB的地址信息;The receiver 1001 is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
发送器1003还用于:将可用的基于基础设施的LB的地址信息发送给业务提供设备;其中,LB的描述信息包括可用的基于基础设施的LB的地址信息。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.
进一步,在图12中,总线架构(用总线1000来代表),总线1000可以包括任意数量的互联的总线和桥,总线1000将包括由处理器1002代表的一个或多个处理器和存储器1004代表的存储器的各种电路链接在一起。总线1000还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口1005在总线1000和处理器1002、接收器1001、发送器1003之间提供接 口。接收器1001和发送器1003用于VIM与外部设备进行数据通信。Further, in FIG. 12, a bus architecture (represented by bus 1000), 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.
处理器1002负责管理总线1000和通常的处理。存储器1004可以被用于存储处理器1002在执行操作时所使用的数据。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.
前述实施例中已详细描述LB的连接方法的实施例过程,通过前述对LB的连接方法的详细描述,本领域技术人员可以清楚的知道本实施例中LB的连接装置的实施方法,所以为了说明书的简洁,在此不再详述。The embodiment process of the connection method of the LB has been described in detail in the foregoing embodiments. Through the foregoing detailed description of the connection method of the LB, 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.
申请实施例中提供的一个或多个技术方案,至少具有如下技术效果或优点:One or more technical solutions provided in the application embodiments have at least the following technical effects or advantages:
本申请实施例中,NSD包括第一VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD,第一VNFD和/或第二VNFD包括对LB类型的描述信息,第二VNFD还包括第二VNF的端口能力信息;在实例化的过程中,业务提供设备能够根据对LB类型的描述信息和业务提供设备支持的LB类型的信息确定所使用的LB类型。因此,通过本申请的方法能够确定所使用的LB类型。然后业务提供设备还将所使用的LB类型的LB的描述信息发送给VIM,以使VIM能够根据所述连接信息、第二VNF的端口能力信息和LB的描述信息将所使用的LB类型的LB连接在第一VNF的实例和第二VNF的实例之间。因此,通过本申请的方法还能将确定的所使用的LB类型的LB连接在VNF的实例之间。In the embodiment of the present application, 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. Then, 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. Thus, the determined LB of the used LB type can also be connected between instances of the VNF by the method of the present application.
本领域内的技术人员应明白,本申请的实施例可提供为方法、***、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, 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. Moreover, 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 present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the present application. It should be understood that the flowcharts and / or each of the processes and / or blocks in the block diagram, and the combination of the flow and / or the blocks in the flowchart and / or block diagram. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。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.
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。 It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims (26)

  1. 一种负载均衡器的连接方法,其特征在于,包括:A method for connecting a load balancer, comprising:
    业务提供设备接收业务请求设备发送的关于业务的实例化请求;The service providing device receives an instantiation request for the service sent by the service requesting device;
    所述业务提供设备根据所述实例化请求获取所述业务的网络服务描述信息NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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;
    所述业务提供设备获取所述业务提供设备支持的LB类型的信息;The service providing device acquires information of an LB type supported by the service providing device;
    所述业务提供设备根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型;Determining, by the service providing device, 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;
    所述业务提供设备获取所述所使用的LB类型的LB的描述信息;The service providing device acquires description information of the used LB of the LB type;
    所述业务提供设备在接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将所述LB的描述信息、所述连接信息和所述端口能力信息发送给虚拟基础设施管理器VIM,以使所述VIM能够根据所述LB的描述信息、所述连接信息和所述端口能力信息将所述所使用的LB类型的LB连接在所述第一VNF的实例和所述第二VNF的实例之间。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.
  2. 如权利要求1所述的方法,其特征在于,当所述对LB类型的描述信息包含需求的LB的类型信息,以及每种类型的优先级信息时;所述业务提供设备根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型,包括:The method according to claim 1, wherein when the description information of the pair of LB types includes type information of a required LB, and priority information of each type; the service providing device according to the pair of LBs The type description information and the LB type information supported by the service providing device determine the type of LB used, including:
    所述业务提供设备根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定共同的LB类型;Determining, by the service providing device, a 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;
    所述业务提供设备根据所述优先级信息确定所述共同的LB类型中的优先 级最高的LB类型作为所述所使用的LB类型;Determining, by the service providing device, a priority among the common LB types according to the priority information The highest LB type is used as the LB type used;
    其中,所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息。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.
  3. 如权利要求2所述的方法,其特征在于,当所述对LB类型的描述信息还包含支持的LB的类型信息时,所述方法还包括:The method according to claim 2, wherein when the description information of the LB type further includes type information of the supported LB, the method further includes:
    所述业务提供设备根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;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;
    所述业务提供设备确定所述支持的LB的类型作为所述所使用的LB类型;Determining, by the service providing device, a type of the supported LB as the used LB type;
    其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。The type information of the supported LB is type information of the LB supported by the first VNF included in the first VNFD.
  4. 如权利要求1-3任一项所述的方法,其特征在于,当所述所使用的LB类型为外设LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:The method according to any one of claims 1-3, wherein when the used LB type is a peripheral LB type, the service providing device acquires a description of the used LB type LB. Information, including:
    所述业务提供设备向数据库发送查询可用的外设LB类型的LB实例的请求;所述业务提供设备将接收到的所述数据库返回的可用的LB实例的地址信息作为所述LB的描述信息;或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
    所述业务提供设备向数据库发送查询可用的外设LB类型的LB实例的请求;所述业务提供设备接收所述数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;所述业务提供设备根据所述LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;所述业务提供设备将接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。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. .
  5. 如权利要求4所述的方法,其特征在于,在所述业务提供设备向数据库 发送查询可用的外设LB类型的LB实例的请求之前,所述方法还包括:The method of claim 4, wherein said service providing device is directed to a database Before sending a request to query an available LB instance of a peripheral LB type, the method further includes:
    所述业务提供设备确定所述对LB类型的描述信息中未包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息。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.
  6. 如权利要求1-3任一项所述的方法,其特征在于,当所述所使用的LB类型为外设LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:The method according to any one of claims 1-3, wherein when the used LB type is a peripheral LB type, the service providing device acquires a description of the used LB type LB. Information, including:
    所述业务提供设备确定所述对LB类型的描述信息中包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息;Determining, by the service providing device, the identifier information of the virtual network function description information VNFD of the peripheral LB type in the description information of the LB type;
    所述业务提供设备根据所述标识信息获取与所述标识信息对应的所述VNFD;The service providing device acquires the VNFD corresponding to the identifier information according to the identifier information;
    所述业务提供设备根据所述VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;The service providing device initiates a request for instantiating a peripheral LB according to the VNFD to the virtual network function manager VNFM;
    所述业务提供设备将接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。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.
  7. 如权利要求1-3任一项所述的方法,其特征在于,当所述所使用的LB类型为基于基础设施的LB类型时,所述业务提供设备获取所述所使用的LB类型的LB的描述信息,包括:The method according to any one of claims 1 to 3, wherein, when the used LB type is an infrastructure-based LB type, the service providing device acquires the used LB type LB Descriptive information, including:
    所述业务提供设备向所述VIM发起为所述业务分配所述基于基础设施的LB类型的LB的请求;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;
    所述业务提供设备将接收到的所述VIM发送的可用的基于基础设施的LB的地址信息作为所述LB的描述信息。The service providing device uses the received address information of the available infrastructure-based LB sent by the VIM as the description information of the LB.
  8. 如权利要求1-7任一项所述的方法,其特征在于,所述端口能力信息包 括所述第二VNF的端口的端口号和所述端口的功能信息。Method according to any of claims 1-7, wherein said port capability information packet The port number of the port of the second VNF and the function information of the port.
  9. 一种业务的实例化部署方法,其特征在于,包括:An instantiation deployment method for a service, comprising:
    业务请求设备向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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.
  10. 如权利要求9所述的方法,其特征在于,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。The method according to claim 9, wherein the description information of the LB type includes type information of the supported LB, type information of the required LB, and priority information of each type; The type information 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 supported LB The type information is type information of the LB supported by the first VNF included in the first VNFD.
  11. 如权利要求9或10所述的方法,其特征在于,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。The method according to claim 9 or 10, wherein the port capability information comprises a port number of a port of the second VNF and function information of the port.
  12. 一种负载均衡器的连接方法,其特征在于,包括:A method for connecting a load balancer, comprising:
    虚拟基础设施管理器VIM接收业务提供设备发送的连接请求,所述连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类型的LB的描述信息、所述第一VNF和所述第二VNF之间的连 接信息以及所述第二VNF的端口能力信息,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息;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. a connection between the first VNF and the second VNF And the port capability information of the port of the second VNF, and the port information of the port of the second VNF and the function information of the port;
    所述VIM根据所述连接信息和所述LB的描述信息将第一VNF的实例与所述LB连接,并根据所述端口的功能信息将所述LB上与所述端口的功能信息相对应的接口与所述第二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.
  13. 如权利要求12所述的方法,其特征在于,当所述LB类型为基于基础设施的LB类型时,在所述VIM接收所述连接请求之前,所述方法还包括:The method according to claim 12, wherein when the LB type is an infrastructure-based LB type, before the VIM receives the connection request, the method further includes:
    所述VIM接收所述业务提供设备发送的为所述业务分配所述基于基础设施的LB的请求;The VIM receives a request sent by the service providing device to allocate the infrastructure-based LB for the service;
    所述VIM根据所述为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配所述基于基础设施的LB的请求;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;
    所述VIM接收所述基础设施层返回的可用的基于基础设施的LB的地址信息;The VIM receives address information of an available infrastructure-based LB returned by the infrastructure layer;
    所述VIM将所述可用的基于基础设施的LB的地址信息发送给所述业务提供设备;其中,所述LB的描述信息包括所述可用的基于基础设施的LB的地址信息。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.
  14. 一种负载均衡器的连接装置,其特征在于,包括:A connection device for a load balancer, comprising:
    接收单元,用于接收业务请求设备发送的关于业务的实例化请求;a receiving unit, configured to receive an instantiation request for a service sent by the service requesting device;
    处理单元,用于根据所述实例化请求获取所述业务的网络服务描述信息NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第 二VNFD还包括所述第二VNF的端口能力信息;获取所述装置支持的LB类型的信息;根据所述对LB类型的描述信息和所述业务提供设备支持的LB类型的信息确定所使用的LB类型;并获取所述所使用的LB类型的LB的描述信息;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 including description information about a load balancer LB type, the The second VNFD further includes port capability information of the second VNF; acquiring information of the LB type supported by the device; determining, according to the description information of the LB type and the information of the LB type supported by the service providing device, LB type; and obtaining description information of the LB of the used LB type;
    发送单元,用于在所述接收单元接收到所述第一VNF和所述第二VNF都实例化成功的响应消息后,将所述LB的描述信息、所述连接信息和所述端口能力信息发送给虚拟基础设施管理器VIM,以使所述VIM能够根据所述LB的描述信息、所述连接信息和所述端口能力信息将所述所使用的LB类型的LB连接在所述第一VNF的实例和所述第二VNF的实例之间。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.
  15. 如权利要求14所述的装置,其特征在于,所述处理单元具体用于:当所述对LB类型的描述信息为需求的LB的类型信息,以及每种类型的优先级信息时,The apparatus according to claim 14, wherein the processing unit is specifically configured to: when the description information of the pair of LB types is type information of a required LB, and each type of priority information,
    根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定是否有共同的LB类型;若有,根据所述优先级信息确定所述共同的LB类型中的优先级最高的LB类型作为所述所使用的LB类型;其中,所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息。Determining whether there is a 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; if yes, determining that the common LB type has the highest priority according to the priority 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.
  16. 如权利要求15所述的装置,其特征在于,所述处理单元还用于:当所述对LB类型的描述信息还包含支持的LB的类型信息时,根据所述需求的LB的类型信息和所述业务提供设备支持的LB类型的信息确定没有共同的LB类型;确定所述第一VNF支持的LB的类型作为所述所使用的LB类型;其中,所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。 The apparatus according to claim 15, wherein the processing unit is further configured to: when the description information of the pair of LBs further includes type information of the supported LB, according to the type information of the required LB and The LB type information supported by the service providing device determines that there is no common LB type; and determines 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 type information of the LB supported by the first VNF included in the first VNFD.
  17. 如权利要求14-16任一项所述的装置,其特征在于,所述处理单元具体用于:当所述所使用的LB类型为外设LB类型时,The device according to any one of claims 14-16, wherein the processing unit is specifically configured to: when the used LB type is a peripheral LB type,
    通过所述发送单元向数据库发送查询可用的外设LB类型的LB实例的请求;Sending, by the sending unit, a request for querying an available LB instance of a peripheral LB type to the database;
    将通过所述接收单元接收到的所述数据库返回的可用的LB实例的地址信息作为所述LB的描述信息;或Using the address information of the available LB instance returned by the database received by the receiving unit as the description information of the LB; or
    通过所述接收单元接收所述数据库返回的可用的LB实例的虚拟网络功能描述信息VNFD;根据所述LB实例的VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;将通过所述接收单元接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。Receiving, by the receiving unit, virtual network function description information VNFD of the available LB instance returned by the database; initiating a request for instantiating the peripheral LB according to the VNFD of the LB instance to the virtual network function manager VNFM; The address information of the peripheral LB instance sent by the VNFM received by the receiving unit is used as the description information of the LB.
  18. 如权利要求17所述的装置,其特征在于,所述处理单元还用于:在通过所述发送单元向数据库发送查询可用的外设LB类型的LB实例的请求之前,确定所述对LB类型的描述信息中未包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息。The apparatus according to claim 17, wherein said processing unit is further configured to: determine, by said transmitting unit, a request for querying an available LB instance of a peripheral LB type available to the database The description information of the virtual network function description information VNFD of the peripheral LB type is not included in the description information.
  19. 如权利要求14-16任一项所述的装置,其特征在于,所述处理单元具体用于:当所述所使用的LB类型为外设LB类型时,确定所述对LB类型的描述信息中包含所述外设LB类型的虚拟网络功能描述信息VNFD的标识信息;根据所述标识信息获取与所述标识信息对应的所述VNFD;根据所述VNFD向虚拟网络功能管理器VNFM发起实例化外设LB的请求;并将通过所述接收单元接收到的所述VNFM发送的外设LB实例的地址信息作为所述LB的描述信息。The device according to any one of claims 14 to 16, wherein the processing unit is specifically configured to: when the used LB type is a peripheral LB type, determine the description information of the LB type. The identifier information of the virtual network function description information VNFD of the peripheral LB type is included, the VNFD corresponding to the identifier information is obtained according to the identifier information, and the virtual network function manager VNFM is instantiated according to the VNFD. a request of the peripheral LB; and the address information of the peripheral LB instance sent by the VNFM received by the receiving unit is used as the description information of the LB.
  20. 如权利要求14-16任一项所述的装置,其特征在于,所述处理单元具体用于:当所述所使用的LB类型为基于基础设施的LB类型时,通过所述发送 单元向所述VIM发起为所述业务分配所述基于基础设施的LB类型的LB的请求;并将通过所述接收单元接收到的所述VIM发送的可用的基于基础设施的LB的地址信息作为所述LB的描述信息。The device according to any one of claims 14-16, wherein the processing unit is specifically configured to: when the used LB type is an infrastructure-based LB type, by using the sending The unit initiates, to the VIM, a request for allocating the LB of the infrastructure-based LB type for the service; and using the address information of the available infrastructure-based LB sent by the VIM received by the receiving unit as Description information of the LB.
  21. 如权利要求14-20任一项所述的装置,其特征在于,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。The apparatus according to any one of claims 14 to 20, wherein the port capability information comprises a port number of a port of the second VNF and function information of the port.
  22. 一种业务的实例化部署装置,其特征在于,包括:An instantiation deployment device for a service, comprising:
    发送单元,用于向业务提供设备发送关于业务的实例化请求;其中,所述实例化请求中携带所述业务的网络服务描述信息NSD的标识信息或者所述NSD;所述NSD包括第一虚拟网络功能模块VNF的第一描述信息VNFD、第二VNF的第二描述信息VNFD和所述第一VNF和所述第二VNF之间的连接信息;所述第一VNFD和/或第二VNFD包括对负载均衡器LB类型的描述信息,所述第二VNFD还包括所述第二VNF的端口能力信息;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;
    接收单元,用于接收所述业务提供设备发送的所述业务的实例部署成功的响应消息。And a receiving unit, configured to receive a response message that the instance of the service sent by the service providing device is successfully deployed.
  23. 如权利要求22所述的装置,其特征在于,所述对LB类型的描述信息包括支持的LB的类型信息、需求的LB的类型信息,以及每种类型的优先级信息;所述需求的LB的类型信息为所述第一VNFD中包含的所述第一VNF需求的LB的类型信息,或所述第二VNFD中包含的所述第二VNF需求的LB的类型信息;所述支持的LB的类型信息为所述第一VNFD中包含的所述第一VNF支持的LB的类型信息。The apparatus according to claim 22, wherein the description information of the LB type includes type information of the supported LB, type information of the required LB, and priority information of each type; The type information 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 supported LB The type information is type information of the LB supported by the first VNF included in the first VNFD.
  24. 如权利要求22或23所述的装置,其特征在于,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息。 The apparatus according to claim 22 or 23, wherein said port capability information comprises a port number of a port of said second VNF and function information of said port.
  25. 一种负载均衡器的连接装置,其特征在于,包括:A connection device for a load balancer, comprising:
    接收单元,用于接收业务提供设备发送的连接请求,所述连接请求包括业务的第一虚拟网络功能模块VNF的实例和第二VNF的实例所使用的负载均衡器LB类型的LB的描述信息、所述第一VNF和所述第二VNF之间的连接信息以及所述第二VNF的端口能力信息,所述端口能力信息包括所述第二VNF的端口的端口号和所述端口的功能信息;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 ;
    处理单元,用于根据所述连接信息和所述LB的描述信息将第一VNF的实例与所述LB连接,并根据所述端口的功能信息将所述LB上与所述端口的功能信息相对应的接口与所述第二VNF上对应的功能的端口连接。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.
  26. 如权利要求25所述的装置,其特征在于,所述装置还包括发送单元,The device according to claim 25, wherein said device further comprises a transmitting unit,
    所述接收单元还用于:当所述LB类型为基于基础设施的LB类型时,在所述接收单元接收所述连接请求之前,接收所述业务提供设备发送的为所述业务分配所述基于基础设施的LB的请求;The receiving unit is further configured to: when the LB type is an LB type based on an infrastructure, before the receiving unit receives the connection request, receive, by the service providing device, the Infrastructure LB request;
    所述处理单元还用于:根据所述为所述业务分配所述基于基础设施的LB的请求向基础设施层发送分配所述基于基础设施的LB的请求;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;
    所述接收单元还用于:接收所述基础设施层返回的可用的基于基础设施的LB的地址信息;The receiving unit is further configured to: receive address information of an available infrastructure-based LB returned by the infrastructure layer;
    所述发送单元还用于:将所述可用的基于基础设施的LB的地址信息发送给所述业务提供设备;其中,所述LB的描述信息包括所述可用的基于基础设施的LB的地址信息。 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 .
PCT/CN2015/087807 2014-12-26 2015-08-21 Load balancer connecting method, and service instantiation deployment method and device WO2016101639A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410833791.6A CN105791147B (en) 2014-12-26 2014-12-26 The connection method of load balancer, the instantiation dispositions method of business and device
CN201410833791.6 2014-12-26

Publications (1)

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

Family

ID=56149171

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/087807 WO2016101639A1 (en) 2014-12-26 2015-08-21 Load balancer connecting method, and service instantiation deployment method and device

Country Status (2)

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

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107689882B (en) 2016-08-05 2020-04-21 华为技术有限公司 Method and device for service deployment in virtual network
CN108200018B (en) * 2017-12-20 2019-11-05 北京百度网讯科技有限公司 Flow forwarding method and equipment, computer equipment and readable medium in cloud computing
CN110891239B (en) * 2018-09-06 2021-01-15 ***通信有限公司研究院 PNF configuration and PNFD TOSCA implementation method and device
CN109753514A (en) * 2018-12-13 2019-05-14 平安普惠企业管理有限公司 Load balancer selection method, device, computer equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104170323A (en) * 2014-04-09 2014-11-26 华为技术有限公司 Fault handling method, device and system based on network function virtualization
CN104202264A (en) * 2014-07-31 2014-12-10 华为技术有限公司 Carrying resource allocation method for clouded data center network, device and system
CN104243301A (en) * 2013-06-08 2014-12-24 华为技术有限公司 Method, device and system for generating service path

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 (en) * 2013-10-29 2014-01-22 北京京东尚科信息技术有限公司 Method and device for updating Web application cluster
CN104219127B (en) * 2014-08-30 2018-06-26 华为技术有限公司 A kind of creation method and equipment of virtual network example
CN105634782B (en) * 2014-11-06 2019-03-01 华为技术有限公司 A kind of method and network element management device instantiating VNF

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243301A (en) * 2013-06-08 2014-12-24 华为技术有限公司 Method, device and system for generating service path
CN104170323A (en) * 2014-04-09 2014-11-26 华为技术有限公司 Fault handling method, device and system based on network function virtualization
CN104202264A (en) * 2014-07-31 2014-12-10 华为技术有限公司 Carrying resource allocation method for clouded data center network, device and system

Also Published As

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

Similar Documents

Publication Publication Date Title
CN107689882B (en) Method and device for service deployment in virtual network
US20210011834A1 (en) Service Upgrade Management Method, Apparatus, And Storage Medium
US10701139B2 (en) Life cycle management method and apparatus
WO2016029821A1 (en) Method and device for creating virtual network instance
EP3455728B1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
WO2019184967A1 (en) Method and apparatus for deploying network slice
WO2016155394A1 (en) Method and device for establishing link between virtual network functions
CN106301829B (en) A kind of method and apparatus of network service dilatation
AU2015419073B2 (en) Life cycle management method and device for network service
JP6549787B2 (en) Method and apparatus for deploying network services
WO2018001049A1 (en) Virtual network function deployment method, device and system adopting network edge computing
WO2018149272A1 (en) Sla-based resource allocation method and nfvo
JP6190949B2 (en) Automatic configuration of access to virtual infrastructure manager by virtual network function manager
WO2015149600A1 (en) Virtual network service deployment method and device
WO2018072503A1 (en) Method for initiating software modification, method and device for publishing metadata
WO2015172362A1 (en) Network function virtualization network system, data processing method and device
WO2018090299A1 (en) Network service lifecycle management permission granting method and device
CN111245634B (en) Virtualization management method and device
WO2016101639A1 (en) Load balancer connecting method, and service instantiation deployment method and device
WO2017054129A1 (en) Network function virtualization resource processing method and virtualized network function manager
CN105556929A (en) Network element and method of running applications in a cloud computing system
KR20180006971A (en) Hardware acceleration methods and related devices
CN107534577A (en) A kind of method and apparatus of Network instantiation
WO2020135517A1 (en) Method and device for deploying virtual network function
WO2013097237A1 (en) Method, device and system for deploying application process

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