WO2018059191A1

WO2018059191A1 - Enterprise service bus connector, and connection method between functional entities

Info

Publication number: WO2018059191A1
Application number: PCT/CN2017/100320
Authority: WO
Inventors: 李江; 孟照星; 王淼; 何海龙
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-09-29
Filing date: 2017-09-04
Publication date: 2018-04-05
Also published as: CN107888545A

Abstract

Provided is an enterprise service bus (ESB) connector. The ESB connector is located in a network function virtualization (NFV) architecture, and the ESB connector consists of one or more protocol interface connectors. The protocol interface connector is used for connecting functional entities having different functions so as to achieve protocol conversion, of transmission information, between the functional entities with different functions. Also provided is a connection method between functional entities.

Description

Enterprise service bus connector and connection method between functional entities

Technical field

The present disclosure relates to the field of virtualization technologies in communication technologies, and in particular, to an enterprise service bus (ESB) connector and a connection method between functional entities.

Background technique

With the rapid development of Internet applications, the traffic demand of the entire Internet has increased greatly, and the traditional proprietary network devices have become more and more diverse. This has made it increasingly difficult for operators and data center operators to upgrade services, and network functions are virtualized. (Network Function Virtualization, NFV) technology provides a way to solve this problem.

NFV integrates network functions into industry-standard servers, switches, and storage hardware. It replaces traditional physical network devices with administrators through software running on servers, providing optimized virtualized data planes, reducing costs, power consumption, and Complexity.

With the gradual maturity and improvement of virtualization standards, the NFV inter-entity communication structure is shown in Figure 1, including the Network Function Virtualization Orchestrator (NFVO) 11 and several different heterogeneous vendors' virtual network functions. Management (Virtualized Network Function Manager, VNFM) 12, Virtual Infrastructure Management (VIM) 23 (not shown), because the interfaces between VNFM and VIM provided by different vendors are quite different, NFVO and each VNFM are respectively Communication through different interfaces, such as NFVO and VNFM1 communicate through ETSI standard interface, NFVO and VNFM2 communicate through VNFM2 private interface, NFVO and VNFM3 communicate through VNFM3 private interface; similarly, NFVO and VIM communication have similar problems, therefore, NFVO The interactive communication with VNFM and VIM of heterogeneous vendors has become a problem. Moreover, since VNFM2 and VNFM3 use their respective private interfaces to communicate with NFVO, each VNFM needs to perform code adaptation between NFVO and VNFM when docking with NFVO, and the adaptation and docking process is cumbersome.

Summary of the invention

In view of this, the embodiments of the present disclosure provide a method for connecting an ESB connector and a functional entity, which can facilitate the adaptation and docking between functional entities in the NFV architecture.

In order to achieve the above object, the technical solution of the embodiment of the present disclosure is implemented as follows:

An embodiment of the present disclosure provides an ESB connector, where the ESB connector is located in a network function virtualization NFV architecture, the ESB connector is more than one protocol interface connector; and the protocol interface connector is used to connect A functional entity with different functions to implement protocol conversion of information transmitted between different functional entities.

In the above solution, the protocol interface connector includes a first port and a second port, where the first port and the second port respectively connect a first functional entity and a second functional entity having different functions; a port for transmitting and receiving the first transmission information of the protocol interface connector and the first functional entity; the second port, configured to send and receive the a second transmission information of the protocol interface connector and the second functional entity.

In the above solution, the protocol interface connector includes a virtual network function management VNFM connector, and the first port and the second port of the VNFM connector are respectively connected to the network function virtualization coordinators NFVO and VNFM.

In the above solution, the protocol interface connector includes a virtual infrastructure management VIM connector, and the first port and the second port of the VIM connector are respectively connected to the NFVO and the VIM.

In the above solution, the protocol interface connector includes a virtual network function coordinator VNFO connector, and the first port and the second port of the VNFO connector are respectively connected to the VNFM and the virtual network function VNF.

In the above solution, the protocol interface connector includes a resource coordinator RO connector, and the first port and the second port of the RO connector are respectively connected to the cross-domain resource coordinators CDRO and VIM.

Embodiments of the present disclosure provide a connection method between functional entities, where functional entities having different functions are connected through an enterprise service bus ESB connector that is more than one protocol interface connector; information transmitted between different functional entities is described by each The protocol interface connector performs protocol conversion.

In the above solution, the protocol interface connector includes a first port and a second port, and the protocol interface connector transmits and receives the first transmission information of the first functional entity through the first port of the protocol, and sends and receives the first transmission information through the second port of the first interface. Second transmission information of the second functional entity; wherein the first functional entity and the second functional entity have different functions.

In the above solution, the first function entity is a network function virtualization coordinator NFVO, the second function entity is a virtual network function management VNFM; the protocol interface connector is a VNFM connector; the first transmission information includes Receiving, by the NFVO, a first message distributed by an ESB router, where the second transmission information includes a second message conforming to a corresponding VNFM protocol converted by the first message, and the second message passes the ESB Sending, by the router, the VNFM; the second transmission information includes a received third message returned by the VNFM, where the first transmission information includes a protocol conforming to the ESB standard interface protocol converted by the third message by a protocol And a fourth message sent by the ESB router to the NFVO.

In the above solution, the first functional entity is NFVO, the second functional entity is a virtual infrastructure management VIM; the protocol interface connector is a VIM connector; and the second transmission information includes the received VIM The fifth message sent, the first transmission information includes a sixth message conforming to the ESB standard interface protocol converted by the fifth message by the protocol, and the sixth message is sent to the NFVO through an ESB router.

In the above solution, the first functional entity is a VNFM, the second functional entity is a virtual network function VNF; the protocol interface connector is a VNFO connector; and the first transmission information includes the received VNFM transmission. The seventh message; the second transmission information includes an eighth message conforming to the ESB standard interface protocol converted by the seventh message by the protocol, and the eighth message is sent to the VNF through an ESB router.

In the above solution, the first functional entity is a cross-domain resource coordinator CDRO, the second functional entity is a VIM, the protocol interface connector is a resource coordinator RO connector, and the second transmission information includes receiving The ninth message sent by the VIM, the first transmission information includes a tenth message conforming to the ESB standard interface protocol converted by the ninth message, and the tenth message is sent to the CDRO through an ESB router. .

The embodiment of the present disclosure further provides a storage medium for storing program code, where the program code is used for execution. A method of connecting between functional entities as described in any of the embodiments.

The ESB connector and the connection method between the functional entities provided by the embodiments of the present disclosure connect functional entities with different functions through an enterprise service bus ESB connector that is more than one protocol interface connector; Each of the protocol interface connectors performs protocol conversion. In this way, each functional entity in the NFV architecture is connected through an ESB connector, so that functional entities having different interfaces in the NFV architecture can communicate with each other, thereby facilitating convenient adaptation and docking between functional entities in the NFV architecture. .

DRAWINGS

1 is a schematic diagram of a connection between NFVO and VNFM in the related art;

2 is a schematic structural diagram of an ESB connector in an NFV architecture according to an embodiment of the present disclosure;

3 is a flowchart of a relevant part of a VNFM connector in a connection method between functional entities in an NFV architecture according to an embodiment of the present disclosure;

4 is a flowchart of a relevant part of a VIM connector in a connection method between functional entities in an NFV architecture according to an embodiment of the present disclosure;

5 is a flowchart of a relevant part of an NVFO connector in a connection method between functional entities in an NFV architecture according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of a relevant part of an RO connector in a connection method between functional entities in an NFV architecture according to an embodiment of the present disclosure.

detailed description

ESB is a combination of traditional middleware technology and XML, Web services and other technologies. It is a standards-based, service-oriented backbone bus that can connect multiple application endpoints. It is a standard between loosely coupled services and applications. An integrated approach that supports virtualized communication interactions between communication participants in a service-oriented architecture and manages virtualized communication participants.

The embodiment of the present disclosure utilizes the characteristics of the ESB, and proposes an ESB connector that is connected between multiple functional entities in the NFV architecture, through more than one protocol interface connector included in the ESB connector, in different functional entities. Transfer information between the transfer and complete the transfer of information between the different functional entities.

The present invention is described in detail with reference to the accompanying drawings.

In the NFV architecture, NFVO is divided into two parts: Network Service Orchestrator (NSO) and Cross-Domain Resource Orchestrator (CDRO).

The NSO is responsible for network service directory management, network service lifecycle management, virtual network feature (VNF) directory management, and VNF lifecycle management. The Element Management System (EMS) configures and manages the VNF. CDRO is primarily responsible for cross-domain resource monitoring.

2 is a schematic structural diagram of an ESB connector in an NFV architecture according to an embodiment of the present disclosure. As shown in FIG. 2, an embodiment of the present disclosure provides an ESB connector 22, which is located in an NFV architecture, for example, The above protocol interface connector; the protocol interface connector is used to connect functional entities of different functions, and realize protocol conversion of information transmission between functional entities having different functions.

The ESB connector is used between the functional entities in the NFV architecture to facilitate the adaptation and docking between functional entities when using functional entities with different interfaces developed by different vendors.

The protocol interface connector includes a first port and a second port, where the first port and the second port respectively connect a first functional entity and a second functional entity having different functions; the first port, Transmitting, by the second interface, the first transmission information of the protocol interface connector and the first functional entity; and the second port, configured to send and receive the second transmission information of the protocol interface connector and the second functional entity.

The protocol interface connector facilitates communication connection between the first functional entity and the second functional entity.

Illustratively, as shown in FIG. 2, the above protocol interface connector includes a VNFM connector 222, a VIM connector 223, a VNFO connector 221, and an RO connector 224.

The first port and the second port of the VNFM connector 222 are respectively connected to the NFVO and the VNFM; correspondingly, the first functional entity is NFVO, and the second functional entity is VNFM;

It should be noted that, in the embodiment of the present disclosure, the first and second are only used to explain the technical implementation scheme more clearly. In practical applications, the first functional entity may be VNFM, and the second functional entity is NFVO; The port to which the VNFM connector is connected to the VNFM is the first port, and the port to which the VNFM connector is connected to the NFVO is the second port.

The first port and the second port of the VIM connector 223 are respectively connected to the NFVO and the VIM; correspondingly, the first functional entity is NFVO, and the second functional entity is VIM;

It should be noted that, in the embodiment of the present disclosure, the first and second are only used to explain the technical implementation scheme more clearly. In an actual application, the first functional entity may be VIM, and the second functional entity is NFVO; The port to which the VIM connector is connected to the VIM is the first port, and the port to which the VIM connector is connected to the NFVO is the second port.

The first port and the second port of the VNFO connector 221 are respectively connected to the VNFM and the VNF; correspondingly, the first functional entity is a VNFM, and the second functional entity is a VNF;

It should be noted that, in the embodiment of the present disclosure, the first and the second are only used to explain the technical implementation scheme more clearly. In actual application, the first functional entity may be a VNF, and the second functional entity is a VNFM; The port to which the VNFO connector is connected to the VNF is the first port, and the port to which the VNFO connector is connected to the VNFM is the second port.

The first port and the second port of the RO connector 224 are respectively connected to the CDRO and the VIM; correspondingly, the first functional entity is a CDRO, and the second functional entity is a VIM;

It should be noted that, in the embodiment of the present disclosure, the first and second are only used to explain the technical implementation scheme more clearly. In an actual application, the first functional entity may be a VIM, and the second functional entity may be a CDRO; The port to which the RO connector is connected to the VIM is the first port, and the port to which the RO connector is connected to the CDRO is the second port.

Based on the characteristics of the ESB, the ESB connector 22 can be adapted to interfaces of VNFM and VNF products of different structures of different manufacturers, and convert messages and messages received and sent by the VNFM and the VNF into HTTP, FTP, JMS, and the like. Messages or messages of standard protocols such as RMI solve the cumbersome problem of the adaptation process between direct communication between NFVO, VNFM, VNF and other manufacturers and NFVO.

The ESB connector 22 in the embodiment of the present disclosure is developed using an ESB designer design. Generally, the ESB connector design development process is as follows:

The first step is to use the RAMB API Editor plug-in integrated with the ESB Designer to design the REST API. This API is used for the NFVO command to send and receive. The NFVO command is delivered to the VNFM connector, including the instantiation, expansion, and other commands. The NFVO command receives an alarm performance report result including receiving the VIM connector.

The second step is to use the ESB Designer to create a new Mule project, import the Raml file generated in the first step, and generate a process template through the APIKit plugin integrated by the ESB Designer; wherein the automatically generated process template includes NFVO and REST messages through the APIKit Router. A sub-process distributed by the router and a connector corresponding to each sub-process.

The third step is to design a custom connector using the DevKit plugin integrated by the ESB Designer. This connector can be used to parse REST messages sent and received by NFVO, and convert data according to the contents of the message, and design the connection. The process is placed in the process template to generate a process deployment file.

The fourth step is to deploy the zip format process deployment file to the corresponding project process.

The ESB connector in the NFV architecture provided in the embodiment of the present disclosure is connected between the NFV functional entities for implementing communication between the functional entities in the NFV architecture based on the ESB, and implementing the communication connection between the functional entities having different interfaces in the NFV architecture. It facilitates the adaptation and docking between various functional entities in the NFV architecture.

As shown in FIG. 3 to FIG. 6 , an embodiment of the present disclosure provides a connection method between functional entities, where functional entities having different functions are connected through an Enterprise Service Bus (ESB) connector that is more than one protocol interface connector; The information transmitted between different functional entities is protocol-converted by each protocol interface connector.

Illustratively, the protocol interface connector includes a first port and a second port, and the protocol interface connector transmits and receives the first transmission information of the first functional entity through the first port of the first interface, and transmits and receives the first transmission information through the second port of the first interface. The second transmission information of the two functional entities; wherein the first functional entity and the second functional entity have different functions.

In the method shown in FIG. 3, the first functional entity is NFVO, the second functional entity is VNFM, and the protocol interface connector is a VNFM connector. Correspondingly, the connection method between functional entities in the NFV architecture includes: The transmission information includes a first message that is sent by the received NFVO through the ESB router, the second transmission information includes a second message that is translated by the first message and conforms to the corresponding VNFM protocol, and the second message is sent to the VNFM through the ESB router; The transmission information includes a third message returned by the received VNFM, the first transmission information includes a fourth message conforming to the ESB standard interface protocol converted by the third message, and the fourth message is sent to the NFVO through the ESB router. The exemplary steps are as follows:

Step 301: Receive, by the first port of the VNFM connector, the first message that the NFVO distributes through the ESB router.

Here, the first message distributed by the ESB router includes: when the first message is delivered, the user first sends a command to the ESB deployment process through the NFVO, and the ESB deployment process distributes the message to the VNFM connector through the APIKit Route router.

Step 302: Convert the first message into a second message that conforms to the corresponding VNFM protocol.

Here, the VNFM connector adapts according to the interface type of the VNFM, and converts the received first message into a data form that can communicate with the VNFM.

Step 303: Send a second message to the VNFM through the second port of the VNFM connector.

Here, after receiving the NFVO message, the VNFM operates on the VNF and returns the message result as a third message.

Step 304: Receive a third message returned by the VNFM through the second port of the VNFM connector.

Step 305: Convert the third message into a fourth message conforming to the ESB standard interface protocol.

Here, the above-mentioned conforming ESB standard interface protocol may be an HTTP message based on a REST interface.

Step 306: Send the fourth message to the NFVO through the ESB router through the first port of the VNFM connector.

When the NFV architecture includes a VNFM product with different interfaces provided by different vendors, the connection method in the embodiment of the present disclosure can be used to perform interface matching between the NFVO interface and the VNFM interface through the VNFM connector without directly coupling. save time and energy.

In the method shown in FIG. 4, the first functional entity is NFVO, the second functional entity is VIM, and the protocol interface connector is a VIM connector; correspondingly, the connection method between functional entities in the NFV architecture includes: second transmission information The fifth message sent by the received VIM is included. The first transmission information includes a sixth message conforming to the ESB standard interface protocol converted by the fifth message, and the sixth message is sent to the NFVO through the ESB router. The exemplary steps are as follows:

Step 401: Receive a fifth message sent by the VIM through the first port of the VIM connector.

Step 402: Convert the fifth message into a sixth message conforming to the ESB standard interface protocol.

Step 403: Send the sixth message to the NFVO through the ESB router through the second port of the VIM connector.

Here, the ESB router is the ESB APIKit Router router.

The reported message sent by the VIM is sent to the NFVO after being converted by the VIM connector. After receiving the report message, the NFVO processes the message and presents it to the user. The reported message sent by the VIM includes data reporting of the alarm performance.

When the NFV architecture includes VIM products with different interfaces provided by different vendors, the connection method in the embodiment of the present disclosure can make the interface matching between the NFVO and the VIM through the VIM connector without being directly coupled, saving time. Labor saving.

In the method shown in FIG. 5, the first functional entity is VNFM, the second functional entity is VNF, and the protocol interface connector is a VNFO connector; correspondingly, the connection method between functional entities in the NFV architecture includes: first transmission information The seventh message sent by the received VNFM is included; the second transmission information includes an eighth message conforming to the ESB standard interface protocol converted by the seventh message, and the eighth message is sent to the VNF through the ESB router. An exemplary step is as follows: Step 501: Receive a seventh message sent by the VNFM through the first port of the VNFO connector.

Step 502: Convert the seventh message into an eighth message conforming to the ESB standard interface protocol.

Step 503: Send the eighth message to the VNF through the ESB router through the second port of the VNFO connector.

Here, the ESB router is the ESB APIKit Router router.

The VNFO connector enables communication between VNFM and VNF from different vendors.

When VNFM manages VNFs of different vendors, VNFMs of different vendors are connected to NFVO through VNFO connectors, and VNFs of different vendors are managed. Among them, VNF management includes VNFM registration, VNF instantiation, and expansion. Shrink, start, stop, etc.

By using the connection method in the embodiment of the present disclosure, the NFVM interface and the VNF interface can be interface-matched through the NFVO connector without direct coupling, saving time and effort.

In the method shown in FIG. 6, the first functional entity is a CDRO, the second functional entity is a VIM, and the protocol interface connector is a RO connector. Correspondingly, the connection method between the functional entities in the NFV architecture includes: The ninth message sent by the received VIM is included. The first transmission information includes a tenth message conforming to the ESB standard interface protocol converted by the ninth message, and the tenth message is sent to the CDRO through the ESB router. The exemplary steps are as follows:

Step 601: Receive a ninth message sent by the VIM through the first port of the RO connector.

Step 602: Convert the ninth message into a tenth message conforming to the standard interface protocol.

Step 603: Send the tenth message to the CDRO through the ESB router through the second port of the RO connector.

Here, the ESB router is the ESB APIKit Router router.

The report message sent by the VIM is sent to the CDRO through the protocol conversion of the RO connector. After receiving the report message, the CDRO processes the report message, and finally realizes unified storage of resources.

When the NFV architecture includes VIM products with different interfaces provided by different vendors, the RO connector in the embodiment of the present disclosure can be used to perform interface matching between the CDRO and the VIM without directly coupling. Time and effort.

The connection method between functional entities in the NFV architecture provided in the embodiment of the present disclosure implements communication between NFV functional entities through an ESB connector connected between functional entities in the NFV architecture, and implements functions with different interfaces in the NFV architecture. The communication connection between entities makes the functional entities in the NFV architecture easy to interface.

Those skilled in the art will appreciate that embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may 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 disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. The computer program instructions can be provided to a processor of a computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine such that instructions executed by a processor of a computer or other programmable data processing device are utilized for Means for implementing the functions specified in one or more flows of the flowchart or in a block or blocks of the flowchart.

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.

The above is only the preferred embodiment of the present disclosure, and is not intended to limit the scope of the disclosure.

Industrial applicability

Claims

An enterprise service bus ESB connector, wherein the ESB connector is located in a network function virtualization NFV architecture, and the ESB connector is more than one protocol interface connector;

The protocol interface connector is configured to connect functional entities having different functions to implement protocol conversion of information transmission between different functional entities.
The connector of claim 1, wherein the protocol interface connector comprises a first port and a second port, the first port and the second port respectively connecting a first functional entity having a different function and a Two functional entity;

The first port is configured to send and receive the first transmission information of the protocol interface connector and the first functional entity;

The second port is configured to send and receive the second transmission information of the protocol interface connector and the second functional entity.
The connector of claim 2, wherein the protocol interface connector comprises a virtual network function management VNFM connector, the first port and the second port of the VNFM connector being respectively associated with a network function virtualization coordinator NFVO and VNFM connection.
The connector of claim 2 wherein said protocol interface connector comprises a virtual infrastructure management VIM connector, said first port and said second port of said VIM connector being coupled to NFVO and said VIM, respectively.
The connector of claim 2, wherein the protocol interface connector comprises a virtual network function coordinator VNFO connector, the first port and the second port of the VNFO connector being respectively connected to the VNFM and the virtual network function VNF .
The connector of claim 2, wherein said protocol interface connector comprises a resource coordinator RO connector, said first port and said second port of said RO connector being connected to cross-domain resource coordinators CDRO and VIM, respectively .
A method of connecting between functional entities, wherein functional entities having different functions are connected by an enterprise service bus ESB connector that is more than one protocol interface connector; the method further includes:

The information transmitted between different functional entities is protocol-converted by each of the protocol interface connectors.
The method according to claim 7, wherein the protocol interface connector comprises a first port and a second port, and the protocol interface connector transmits and receives the first transmission information of the first functional entity through the first port of the first interface. The second port of the second function transmits and receives the second transmission information of the second functional entity; wherein the first functional entity and the second functional entity have different functions.
The method according to claim 8, wherein the first functional entity is a network function virtualization coordinator NFVO, and the second functional entity is a virtual network function management VNFM;

The protocol interface connector is a VNFM connector;

The first transmission information includes a first message that is received by the NFVO through an ESB router, The second transmission information includes a second message conforming to the corresponding VNFM protocol converted by the first message, and the second message is sent to the VNFM by the ESB router;

The second transmission information includes a received third message returned by the VNFM, where the first transmission information includes a fourth message conforming to an ESB standard interface protocol converted by the third message by a protocol, and the fourth message. A message is sent to the NFVO through the ESB router.
The method of claim 8, wherein the first functional entity is NFVO and the second functional entity is a virtual infrastructure management VIM;

The protocol interface connector is a VIM connector;

The second transmission information includes the received fifth message sent by the VIM, where the first transmission information includes a sixth message conforming to the ESB standard interface protocol converted by the fifth message by the protocol, and the sixth message. The message is sent to the NFVO through the ESB router.
The method according to claim 8, wherein the first functional entity is a VNFM, and the second functional entity is a virtual network function VNF;

The protocol interface connector is a VNFO connector;

The first transmission information includes a received seventh message sent by the VNFM, and the second transmission information includes an eighth message conforming to an ESB standard interface protocol converted by the seventh message by the protocol, the eighth The message is sent to the VNF through the ESB router.
The method according to claim 8, wherein the first functional entity is a cross-domain resource coordinator CDRO, and the second functional entity is a VIM;

The protocol interface connector is a resource coordinator RO connector;

The second transmission information includes the received ninth message sent by the VIM, where the first transmission information includes a tenth message conforming to the ESB standard interface protocol converted by the ninth message by the protocol, the tenth The message is sent to the CDRO through an ESB router.
A storage medium for storing program code for performing a connection method between functional entities according to any one of claims 7-12.