CN107888545A - A kind of connection method between ESB connector and functional entity - Google Patents
A kind of connection method between ESB connector and functional entity Download PDFInfo
- Publication number
- CN107888545A CN107888545A CN201610868129.3A CN201610868129A CN107888545A CN 107888545 A CN107888545 A CN 107888545A CN 201610868129 A CN201610868129 A CN 201610868129A CN 107888545 A CN107888545 A CN 107888545A
- Authority
- CN
- China
- Prior art keywords
- message
- esb
- connectors
- port
- functional entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of ESB (ESB) connector, the ESB connectors are located in network function virtualization (NFV) framework, and the ESB connectors are specially more than one protocol interface connectors；The protocol interface connector is used to connect the functional entity with difference in functionality, realizes the protocol conversion of transmission information between the functional entity of the difference in functionality.The invention also discloses the connection method between a kind of functional entity.
Description
Technical field
The present invention relates to the technical field of virtualization in the communication technology, more particularly to a kind of ESB
Connection method between (Enterprise Service Bus, ESB) connector and functional entity.
Background technology
With the fast development of the Internet, applications, the traffic demand of whole internet increases, traditional proprietary network equipment
More and more diversified, this make it that the upgrade service of operator and data center operators is more and more difficult, and network function is virtual
Change (Network Function Virtualization, NFV) technology and provide a kind of approach for solving the problem.
Network function is incorporated on the server, interchanger and storage hardware of professional standard by NFV, by being transported on server
Capable software, the conventional physical network equipment instead of by keeper, there is provided the virtualization data plane of optimization, and reduce into
Originally, energy consumption and complexity.
With virtualization standard it is progressively ripe and perfect, NFV inter-entity communication structure is as shown in figure 1, including network work(
Can virtualize telegon (Network Function Virtualization Orchestrator, NFVO) 11 and several not
The virtual network function management (Virtualised Network Function Manager, VNFM) 12 of same isomery manufacturer,
Virtual base facilities management 23 (Virtualised Infrastructure Manager, VIM) (not shown), due to difference
The VNFM and VIM interface that manufacturer provides have larger difference, and NFVO and each VNFM are led to by different interfaces respectively
Letter, if NFVO and VNFM1 are by etsi standard interface communication, NFVO and VNFM2 by the privately owned interface communications of VNFM2, NFVO with
VNFM3 passes through the privately owned interface communications of VNFM3；Equally, there is also Similar Problems, therefore, NFVO and isomery for NFVO and VIM communication
Interactive communication between the VNFM and VIM of manufacturer is into a problem.Also, because VNFM2 and VNFM3 is using respective privately owned
Interface communicates with NFVO, so, each VNFM enters line code when being docked with NFVO, it is necessary between NFVO and VNFM and is adapted to, and fits
With comparatively laborious with docking operation.
The content of the invention
In view of this, the embodiment of the present invention provides the connection method between a kind of ESB connectors and functional entity, may be such that
Conveniently it is adapted to and docks between each functional entity in NFV framework.
To reach above-mentioned purpose, what the technical scheme of the embodiment of the present invention was realized in：
The embodiments of the invention provide a kind of ESB connectors, the ESB connectors are located at network function virtualization NFV framves
In structure, the ESB connectors are specially more than one protocol interface connectors；The protocol interface connector, have for connecting
There is the functional entity of difference in functionality, realize the protocol conversion of difference in functionality inter-entity transmission information.
In such scheme, the protocol interface connector includes first port and second port, the first port and institute
State second port and connect the first functional entity and the second functional entity with difference in functionality respectively；The first port, is used for
Receive and dispatch the first transmission information of the protocol interface connector and first functional entity；The second port, for receiving and dispatching
Second transmission information of the protocol interface connector and second functional entity.
In such scheme, the protocol interface connector includes virtual network function management VNFM connectors, the VNFM
The first port and second port of connector are connected with network function virtualization telegon NFVO and VNFM respectively.
In such scheme, the protocol interface connector includes Virtual base facilities management VIM connectors, and the VIM connects
The first port and second port for connecing device are connected with NFVO and the VIM respectively.
In such scheme, the protocol interface connector includes virtual network function telegon VNFO connectors, described
The first port and second port of VNFO connectors are connected with VNFM and virtual network function VNF respectively.
In such scheme, the protocol interface connector includes resource coordinator RO connectors, and the of the RO connectors
Single port and second port are connected with cross-domain resource telegon CDRO and VIM respectively.
The embodiments of the invention provide the connection method between a kind of functional entity, and the functional entity with difference in functionality is led to
Cross the ESB ESB connectors connection of specially more than one protocol interface connectors；Difference in functionality inter-entity is transmitted
Information carries out protocol conversion by each protocol interface connector.
In such scheme, the protocol interface connector includes first port and second port, the protocol interface connection
Device receives and dispatches the first transmission information of the first functional entity by the first port of itself, and second is received and dispatched by the second port of itself
Second transmission information of functional entity；Wherein, first functional entity has difference in functionality with second functional entity.
In such scheme, first functional entity is that network function virtualizes telegon NFVO, and second function is real
Body is that virtual network function manages VNFM；The protocol interface connector is VNFM connectors；First transport packet includes
The first message that the NFVO received is distributed by ESB routers, second transport packet includes to be disappeared by described first
Second message that meets corresponding VNFM agreement of the breath through protocol conversion, second message are sent to by the ESB routers
The VNFM；Second transport packet includes the 3rd message that the VNFM received is returned, the first transmission information
Including being passed through by fourth message that meets ESB standard interface protocol of the 3rd message through protocol conversion, the 4th message
The ESB routers are sent to the NFVO.
In such scheme, first functional entity is NFVO, and second functional entity is Virtual base facilities management
VIM；The protocol interface connector is VIM connectors；Second transport packet include that the VIM that receives sends the
Five message, first transport packet are included by meet ESB standard interface protocols of the 5th message through protocol conversion
Six message, the 6th message are sent to the NFVO by ESB routers.
In such scheme, first functional entity is VNFM, and second functional entity is virtual network function VNF；
The protocol interface connector is VNFO connectors；First transport packet includes the 7th that the VNFM received is sent
Message；Second transport packet is included by the meet ESB standard interface protocols the 8th of the 7th message through protocol conversion
Message, the 8th message are sent to the VNF by ESB routers.
In such scheme, first functional entity is cross-domain resource telegon CDRO, and second functional entity is
VIM；The protocol interface connector is resource coordinator RO connectors；Second transport packet include receive it is described
The 9th message that VIM is sent, first transport packet includes to be connect by the ESB standards that meet of the 9th message through protocol conversion
Tenth message of mouth agreement, the tenth message are sent to the CDRO by ESB routers.
Connection method between ESB connectors and functional entity that the embodiment of the present invention is provided, there will be difference in functionality
Functional entity pass through specially more than one protocol interface connectors ESB ESB connectors connect；Different work(
Energy inter-entity transmission information carries out protocol conversion by each protocol interface connector.In this way, each function in NFV frameworks is real
Connected between body by ESB connectors so that can be in communication with each other, enter between the functional entity with distinct interface in NFV frameworks
And realize in NFV frameworks and be easily adapted to and dock between each functional entity.
Brief description of the drawings
Fig. 1 is NFVO in the prior art and VNFM connection diagrams；
Fig. 2 is ESB connector construction schematic diagrames in NFV frameworks of the embodiment of the present invention；
VNFM connector relevant portions in connection methods of the Fig. 3 between functional entity in NFV frameworks of the embodiment of the present invention
Flow chart；
The stream of VIM connector relevant portions in connection methods of the Fig. 4 between functional entity in NFV frameworks of the embodiment of the present invention
Cheng Tu；
NVFO connector relevant portions in connection methods of the Fig. 5 between functional entity in NFV frameworks of the embodiment of the present invention
Flow chart；
The stream of RO connector relevant portions in connection methods of the Fig. 6 between functional entity in NFV frameworks of the embodiment of the present invention
Cheng Tu.
Embodiment
ESB is the product that traditional middleware technology is combined with technologies such as XML, Web services, is that can connect multiple application ends
Measured, the service-oriented key network bus of point, is a kind of collection of the standard between the service and application of loose couplings
Into mode, the service interaction between virtualization communication participant in Enterprise SOA is supported, and to virtualization communication ginseng
It is managed with side.
The embodiment of the present invention is exactly the characteristics of utilizing ESB, to propose a kind of ESB connectors, be connected to multiple work(in NFV frameworks
Can between entity, by more than one protocol interface connectors included in ESB connectors, between different functional entitys in
Turn transmission information, and complete to transmit protocol conversion of the information between difference in functionality entity.
In order to more fully hereinafter understand the features of the present invention and technology contents, below in conjunction with the accompanying drawings to the reality of the present invention
Now it is described in detail, appended accompanying drawing purposes of discussion only for reference, is not used for limiting the present invention.
In NFV frameworks, NFVO is divided into (the Network Service of network service telegon 111 from business
Orchestrator, NSO) and cross-domain resource monitor 112 (Cross-Domain Resource Orchestrator, CDRO)
Two parts.
NSO is mainly responsible for Web Services directory management, network service life cycle management, virtual network function 211
(Virtual Network Feature, VNF) directory management and VNF life cycle managements.Wherein Element management system 212
(Element Management System, EMS) is configured and managed to VNF.CDRO is mainly responsible for cross-domain resource prison
Control.
Fig. 2 is the ESB connector construction schematic diagrames in NFV frameworks in the embodiment of the present invention, as shown in Fig. 2 the present invention is real
Apply example and provide a kind of ESB connectors 22, the ESB connectors 22 are located in NFV frameworks, are specially that more than one protocol interfaces connect
Connect device；Protocol interface connector is used for the functional entity for connecting difference in functionality, and realization passes between the functional entity with difference in functionality
The protocol conversion of defeated information.
Connected, can had not what is developed using different manufacturers using ESB connectors between functional entity in NFV frameworks
With interface functional entity when, facilitate the adaptation between functional entity and docking.
Wherein, the protocol interface connector includes first port and second port, the first port and described second
Port connects the first functional entity and the second functional entity with difference in functionality respectively；The first port, for receiving and dispatching
State the first transmission information of protocol interface connector and first functional entity；The second port, for receiving and dispatching the association
Discuss the second transmission information of interface connector and second functional entity.
The protocol interface connector can conveniently realize the communication connection between the first functional entity and the second functional entity.
Specifically, as shown in Fig. 2 above-mentioned protocol interface connector include VNFM connectors 222, VIM connectors 223,
VNFO connectors 221 and RO connectors 224.
Wherein, the first port of VNFM connectors 222 and second port are connected with NFVO and VNFM respectively；Accordingly,
One functional entity is NFVO, and the second functional entity is VNFM；
It should be noted that first, second clearer explanation technic relization scheme is only used in the embodiment of the present invention, it is actual
In or the first functional entity is VNFM, and the second functional entity is NFVO；Accordingly, VNFM connectors and VNFM
The port of connection is first port, and the port that VNFM connectors are connected with NFVO is second port.
The first port and second port of VIM connectors 223 are connected with NFVO and VIM respectively；Accordingly, the first function is real
Body is NFVO, and the second functional entity is VIM；
It should be noted that first, second clearer explanation technic relization scheme is only used in the embodiment of the present invention, it is actual
In or the first functional entity is VIM, and the second functional entity is NFVO；Accordingly, VIM connectors are connected with VIM
Port be first port, the port that VIM connectors are connected with NFVO is second port.
The first port and second port of VNFO connectors 221 are connected with VNFM and VNF respectively；Accordingly, the first function
Entity is VNFM, and the second functional entity is VNF；
It should be noted that first, second clearer explanation technic relization scheme is only used in the embodiment of the present invention, it is actual
In or the first functional entity is VNF, and the second functional entity is VNFM；Accordingly, VNFO connectors connect with VNF
The port connect is first port, and the port that VNFO connectors are connected with VNFM is second port.
The first port and second port of RO connectors 224 are connected with CDRO and VIM respectively；Accordingly, the first function is real
Body is CDRO, and the second functional entity is VIM；
It should be noted that first, second clearer explanation technic relization scheme is only used in the embodiment of the present invention, it is actual
In or the first functional entity is VIM, and the second functional entity is CDRO；Accordingly, RO connectors are connected with VIM
Port be first port, the port that RO connectors are connected with CDRO is second port.
The characteristics of based on ESB, ESB connectors 22 can fit with the interface of VNFM, VNF product of the different structure of different vendor
Match somebody with somebody, and message or message that VNFM, the VNF are received and sent are converted to and meet the standard agreements such as HTTP, FTP, JMS, RMI
Message or message, to solve to be adapted to existing for direct communication between the product of the different vendors such as NFVO, VNFM, VNF and NFVO
The cumbersome problem of journey.
ESB connectors 22 in the embodiment of the present invention are designed and developed using ESB designers to be formed, and typically, ESB connectors are set
It is as follows to count development process：
The first step, the RAML API Editor insert designs REST API integrated using ESB designers, this API are used for
NFVO orders are issued and received；Wherein, NFVO orders issue including issue instantiation, it is scalable hold etc. order and give VNFM connectors,
NFVO orders receive the alarm performance reported result for including receiving VIM connectors.
Second step, using the newly-built Mule engineerings of ESB designers, the raml files generated is imported in the first step, and pass through ESB
The integrated APIKit plug-in unit product process templates of designer；Wherein, the flow template automatically generated includes NFVO and REST message
A connector corresponding to the sub-process and each sub-process distributed by APIKit Router routers.
3rd step, the customized connector of DevKit insert designs integrated using ESB designers, this connector can be used for
The parsing NFVO REST message that issues and receives, and the content progress data conversion in message, and by designed connection
Device is put into flow template, product process deployment file.
4th step, the flow deployment file of zip forms is deployed in corresponding project process.
ESB connectors in the NFV frameworks provided in the embodiment of the present invention are connected between NFV functional entitys, for based on
ESB realizes the communication between each functional entity in NFV frameworks, realizes in NFV frameworks between the functional entity with distinct interface
Communication connection, facilitates the adaptation in NFV frameworks between each functional entity and docking.
As shown in Figures 3 to 6, the embodiment of the present invention provides the connection method between a kind of functional entity, will have different work(
ESB (ESB) connector that the functional entity of energy passes through specially more than one protocol interface connectors connects；No
Congenerous inter-entity transmits information and carries out protocol conversion by each protocol interface connector.
Connected, can had not what is developed using different manufacturers using ESB connectors between functional entity in NFV frameworks
With interface functional entity when, facilitate the adaptation between functional entity and docking.
Specifically, the protocol interface connector includes first port and second port, and the protocol interface connector leads to
The first transmission information that the first port of itself receives and dispatches the first functional entity is crossed, the second function is received and dispatched by the second port of itself
Second transmission information of entity；Wherein, the first functional entity and the second functional entity have difference in functionality.
The protocol interface connector can conveniently realize the communication connection between the first functional entity and the second functional entity.
Wherein, in method as shown in Figure 3, the first functional entity is NFVO, and the second functional entity is VNFM；Protocol interface
Connector is VNFM connectors, and accordingly, the connection method in NFV frameworks between functional entity includes：First transport packet includes
The first message that the NFVO received is distributed by ESB routers, the second transport packet are included by first message through protocol conversion
The second message for meeting corresponding VNFM agreements, the second message is sent to VNFM by ESB routers；Second transport packet includes
The 3rd message that the VNFM received is returned, the first transport packet includes meets ESB standards by the 3rd message through protocol conversion
4th message of interface protocol, the 4th message are sent to NFVO by ESB routers.Comprise the following steps that：
Step 301：The first message distributed by the first port reception NFVO of VNFM connectors by ESB routers.
Here, the first message distributed by ESB routers includes：When first message issues, user passes through first
NFVO transmitting order to lower levels is disposed in flow to ESB, and ESB disposes flow by APIKit Route routers by message distribution to VNFM
Connector.
Step 302：First message is converted to the second message of VNFM agreements corresponding to meeting.
Here, VNFM connectors are adapted to according to VNFM interface type, and the first message received is converted to can
The data mode to be communicated with the VNFM.
Step 303：Second message is sent to by VNFM by the second port of VNFM connectors.
Here, after VNFM receives NFVO message, VNF is operated, and message result is returned with the 3rd message.
Step 304：3rd message of VNFM returns is received by the second port of VNFM connectors.
Step 305：3rd message is converted to the 4th message for meeting ESB standard interface protocols.
Here, the above-mentioned ESB standard interface protocols that meet can be the HTTP message based on REST interfaces.
Step 306：4th message is sent to by NFVO by ESB routers by the first port of VNFM connectors.
When including the VNFM products with distinct interface that different vendor provides in NFV frameworks, implemented using the present invention
Connection method in example, NFVO interfaces can be made in the case of not direct-coupling, to enter with VNFM interfaces by VNFM connectors
Line interface matches, time saving and energy saving.
In method as shown in Figure 4, the first functional entity is NFVO, and the second functional entity is VIM；Protocol interface connector
For VIM connectors；Accordingly, the connection method in NFV frameworks between functional entity includes：Second transport packet includes what is received
The 5th message that VIM is sent, the first transport packet includes meets ESB standard interface protocols by the 5th message through protocol conversion
6th message, the 6th message are sent to NFVO by ESB routers.Comprise the following steps that：
Step 401：5th message of VIM transmissions is received by the first port of VIM connectors.
Step 402：5th message is converted to the 6th message for meeting ESB standard interface protocols.
Step 403：6th message is sent to by NFVO by ESB routers by the second port of VIM connectors.
Here, ESB routers are ESB APIKit Router routers.
The reporting message that VIM is sent is sent to NFVO after carrying out protocol conversion by VIM connectors, and NFVO is received on this
It is handled after report message and is presented to user.Wherein, the reporting message that VIM is sent is included in the data of alarm performance
Report.
When including the VIM products with distinct interface that different vendor provides in NFV frameworks, using the embodiment of the present invention
In connection method, NFVO and VIM can be made in the case of not direct-coupling, pass through VIM connectors and carry out Interface Matching, save
Shi Shengli.
In method as shown in Figure 5, the first functional entity is VNFM, and the second functional entity is VNF；Protocol interface connector
For VNFO connectors；Accordingly, the connection method in NFV frameworks between functional entity includes：First transport packet, which includes, to be received
VNFM send the 7th message；Second transport packet includes meets ESB standard interfaces association by the 7th message through protocol conversion
8th message of view, the 8th message are sent to VNF by ESB routers.Comprise the following steps that：Step 501：Connected by VNFO
The first port of device receives the 7th message that VNFM is sent.
Step 502：7th message is converted to the 8th message for meeting ESB standard interface protocols.
Step 503：8th message is sent to by VNF by ESB routers by the second port of VNFO connectors.
Here, ESB routers are ESB APIKit Router routers.
VNFO connectors can realize the communication between the VNFM of different vendor and VNF.
The VNFM of different vendor is linked into by VNFM when the VNF to different vendor is managed, by VNFO connectors
NFVO, and the VNF of different vendor is managed, wherein, VNFM registrations, VNF instantiations, expansion are included to VNF management work
Capacity reducing, startup, stopping etc..
Using the connection method in the embodiment of the present invention, NFVM interfaces can be made with VNF interfaces in not direct-coupled feelings
Under condition, Interface Matching is carried out by NFVO connectors, it is time saving and energy saving.
In method as shown in Figure 6, the first functional entity is CDRO, and the second functional entity is VIM；Protocol interface connector
For RO connectors；Accordingly, the connection method in NFV frameworks between functional entity includes：Second transport packet includes what is received
The 9th message that VIM is sent, the first transport packet includes meets ESB standard interface protocols by the 9th message through protocol conversion
Tenth message, the tenth message are sent to CDRO by ESB routers.Comprise the following steps that：
Step 601：9th message of VIM transmissions is received by the first port of RO connectors.
Step 602：9th message is converted to the tenth message for meeting standard interface protocol.
Step 603：Tenth message is sent to by CDRO by ESB routers by the second port of RO connectors.
Here, ESB routers are ESB APIKit Router routers.
The reporting message that VIM is sent is sent to CDRO after carrying out protocol conversion by RO connectors, and CDRO is received on this
It is handled after report message, finally realizes the unified storage of resource.
When including the VIM products with distinct interface that different vendor provides in NFV frameworks, using the embodiment of the present invention
In RO connectors, CDRO and VIM can be made in the case of not direct-coupling, lead to RO connectors and carry out Interface Matching, it is time saving
It is laborsaving.
The connection method between functional entity in the NFV frameworks provided in the embodiment of the present invention is by being connected to NFV frameworks
In functional entity between ESB connectors realize communication between NFV functional entitys, realize being connect with difference in NFV frameworks
Communication connection between the functional entity of mouth, make the functional entity in NFV frameworks is convenient to dock.
It should be understood by those skilled in the art that, embodiments of the invention can be provided as method, system or computer program
Product.Therefore, the shape of the embodiment in terms of the present invention can use hardware embodiment, software implementation or combination software and hardware
Formula.Moreover, the present invention can use the computer for wherein including computer usable program code in one or more to use storage
The form for the computer program product that medium is implemented on (including but is not limited to magnetic disk storage and optical memory etc.).
The present invention is the flow with reference to method according to embodiments of the present invention, equipment (system) and computer program product
Figure and/or block diagram describe.It should be understood that can be by every first-class in computer program instructions implementation process figure and/or block diagram
Journey and/or the flow in square frame and flow chart and/or block diagram and/or the combination of square frame.These computer programs can be provided
The processors of computer, special-purpose computer, Embedded Processor or other programmable data processing devices is instructed to produce one
Individual machine so that produced by the instruction of computer or the computing device of other programmable data processing devices for realizing
The device for the function of being specified in one flow of flow chart or multiple flows and/or one square frame of block diagram or multiple square frames.
These computer program instructions, which may be alternatively stored in, can guide computer or other programmable data processing devices with spy
Determine in the computer-readable memory that mode works so that the instruction being stored in the computer-readable memory, which produces, to be included referring to
Make the manufacture of device, the command device realize in one flow of flow chart or multiple flows and/or one square frame of block diagram or
The function of being specified in multiple square frames.
These computer program instructions can be also loaded into computer or other programmable data processing devices so that counted
Series of operation steps is performed on calculation machine or other programmable devices to produce computer implemented processing, so as in computer or
The instruction performed on other programmable devices is provided for realizing in one flow of flow chart or multiple flows and/or block diagram one
The step of function of being specified in individual square frame or multiple square frames.
More than, only presently preferred embodiments of the present invention is not intended to limit the scope of the present invention.
Claims (12)
1. a kind of ESB ESB connectors, it is characterised in that the ESB connectors are located at network function virtualization NFV
In framework, the ESB connectors are specially more than one protocol interface connectors；
The protocol interface connector, for connecting the functional entity with difference in functionality, realize that difference in functionality inter-entity is transmitted
The protocol conversion of information.
2. connector according to claim 1, it is characterised in that the protocol interface connector includes first port and the
Two-port netwerk, the first port and the second port connect the first functional entity and the second function with difference in functionality respectively
Entity；
The first port, for receiving and dispatching the first transmission information of the protocol interface connector and first functional entity；
The second port, for receiving and dispatching the second transmission information of the protocol interface connector and second functional entity.
3. connector according to claim 2, it is characterised in that the protocol interface connector includes virtual network function
VNFM connectors are managed, the first port and second port of the VNFM connectors virtualize telegon with network function respectively
NFVO connects with VNFM.
4. connector according to claim 2, it is characterised in that the protocol interface connector includes Virtual base facility
VIM connectors are managed, the first port and second port of the VIM connectors are connected with NFVO and the VIM respectively.
5. connector according to claim 2, it is characterised in that the protocol interface connector includes virtual network function
Telegon VNFO connectors, the first port and second port of the VNFO connectors respectively with VNFM and virtual network function
VNF connections.
6. connector according to claim 2, it is characterised in that the protocol interface connector includes resource coordinator RO
Connector, the first port and second port of the RO connectors are connected with cross-domain resource telegon CDRO and VIM respectively.
7. the connection method between a kind of functional entity, it is characterised in that by the functional entity with difference in functionality by being specially
The ESB ESB connectors connection of more than one protocol interface connectors；Methods described also includes：
Difference in functionality inter-entity transmits information and carries out protocol conversion by each protocol interface connector.
8. according to the method for claim 7, it is characterised in that the protocol interface connector includes first port and second
Port, the protocol interface connector are received and dispatched the first transmission information of the first functional entity by the first port of itself, passed through
The second port of itself receives and dispatches the second transmission information of the second functional entity；Wherein, first functional entity and described second
Functional entity has difference in functionality.
9. according to the method for claim 8, it is characterised in that first functional entity is that network function virtualization is coordinated
Device NFVO, second functional entity are that virtual network function manages VNFM；
The protocol interface connector is VNFM connectors；
First transport packet includes the first message that the NFVO received is distributed by ESB routers, and described second
Transport packet includes the second message for meeting corresponding VNFM agreements through protocol conversion, second message by the first message
The VNFM is sent to by the ESB routers；
Second transport packet includes the 3rd message that the VNFM that receives is returned, first transport packet include by
Fourth message that meets ESB standard interface protocol of 3rd message through protocol conversion, the 4th message pass through the ESB
Router is sent to the NFVO.
10. according to the method for claim 8, it is characterised in that first functional entity is NFVO, second function
Entity is Virtual base facilities management VIM；
The protocol interface connector is VIM connectors；
Second transport packet includes the 5th message that the VIM that receives is sent, first transport packet include by
Sixth message that meets ESB standard interface protocol of 5th message through protocol conversion, the 6th message are route by ESB
Device is sent to the NFVO.
11. according to the method for claim 8, it is characterised in that first functional entity is VNFM, second function
Entity is virtual network function VNF；
The protocol interface connector is VNFO connectors；
First transport packet includes the 7th message that the VNFM received is sent；Second transport packet include by
Eightth message that meets ESB standard interface protocol of 7th message through protocol conversion, the 8th message are route by ESB
Device is sent to the VNF.
12. according to the method for claim 8, it is characterised in that first functional entity is cross-domain resource telegon
CDRO, second functional entity are VIM；
The protocol interface connector is resource coordinator RO connectors；
Second transport packet includes the 9th message that the VIM that receives is sent, first transport packet include by
Tenth message that meets ESB standard interface protocol of 9th message through protocol conversion, the tenth message are route by ESB
Device is sent to the CDRO.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610868129.3A CN107888545A (en) | 2016-09-29 | 2016-09-29 | A kind of connection method between ESB connector and functional entity |
| PCT/CN2017/100320 WO2018059191A1 (en) | 2016-09-29 | 2017-09-04 | Enterprise service bus connector, and connection method between functional entities |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610868129.3A CN107888545A (en) | 2016-09-29 | 2016-09-29 | A kind of connection method between ESB connector and functional entity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107888545A true CN107888545A (en) | 2018-04-06 |
Family
ID=61763716
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610868129.3A Withdrawn CN107888545A (en) | 2016-09-29 | 2016-09-29 | A kind of connection method between ESB connector and functional entity |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107888545A (en) |
| WO (1) | WO2018059191A1 (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938770A (en) * | 2012-11-22 | 2013-02-20 | 亚信联创科技（中国）有限公司 | Method for realizing uniform interface for multi-protocol messages and related device and system |
| US20150256580A1 (en) * | 2014-03-10 | 2015-09-10 | Gazoo, Inc. | Video streaming system and method |
| CN105245553A (en) * | 2015-11-18 | 2016-01-13 | 拉扎斯网络科技（上海）有限公司 | SOA system and service processing method |
| WO2016095121A1 (en) * | 2014-12-17 | 2016-06-23 | 华为技术有限公司 | Method and system for automatically adjusting network service capability |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102347983B (en) * | 2011-08-26 | 2014-01-29 | 四川长虹电器股份有限公司 | ESB (Enterprise Service Bus) system in SOA (Service-Oriented Architecture) |
| US9760428B1 (en) * | 2013-12-19 | 2017-09-12 | Amdocs Software Systems Limited | System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network |
| ES2726699T3 (en) * | 2014-08-07 | 2019-10-08 | Intel Ip Corp | Virtualized network function management |
| US9912737B2 (en) * | 2014-08-27 | 2018-03-06 | Exxonmobil Research And Engineering Company | Method and system for modular interoperable distributed control |
| CN104601723B (en) * | 2015-02-03 | 2018-04-27 | 中国南方电网有限责任公司 | Power Marketing Management System SOA framework based on internal services bus |
| CN105429780B (en) * | 2015-10-30 | 2019-04-23 | 南京优速网络科技有限公司 | A method of virtualization network service business automatically generates and dynamic monitors |
| CN105635345B (en) * | 2016-02-23 | 2019-02-05 | 华为技术有限公司 | Domain name resources record management method and apparatus |
-
2016
- 2016-09-29 CN CN201610868129.3A patent/CN107888545A/en not_active Withdrawn
-
2017
- 2017-09-04 WO PCT/CN2017/100320 patent/WO2018059191A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938770A (en) * | 2012-11-22 | 2013-02-20 | 亚信联创科技（中国）有限公司 | Method for realizing uniform interface for multi-protocol messages and related device and system |
| US20150256580A1 (en) * | 2014-03-10 | 2015-09-10 | Gazoo, Inc. | Video streaming system and method |
| WO2016095121A1 (en) * | 2014-12-17 | 2016-06-23 | 华为技术有限公司 | Method and system for automatically adjusting network service capability |
| CN105245553A (en) * | 2015-11-18 | 2016-01-13 | 拉扎斯网络科技（上海）有限公司 | SOA system and service processing method |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018059191A1 (en) | 2018-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10025613B2 (en) | Universal VNFM and method for managing VNF | |
| CN107563947B (en) | Traffic and transportation integrated comprehensive service method and system | |
| CN107005480A (en) | The system and method cooperated for SDT and NFV and SDN | |
| CN104737519A (en) | System and apparatus of generalized network controller for a software defined network (SDN) | |
| CN109995801A (en) | A kind of method for message transmission and device | |
| CN106686023A (en) | Flow designing method, client machine, server side apparatus and system | |
| CN105827428A (en) | Management method and device of asset information | |
| CN105786611A (en) | Method and device for task scheduling of distributed cluster | |
| CN102866925B (en) | Communication method and system for middleware and user interface | |
| CN105302564B (en) | Network OA service control and implementation method | |
| CN109391516A (en) | Realize the cloud third party NMS system of more producer UTN equipment centralized maintenance management | |
| CN108063694A (en) | The system and method for pressure test are carried out on PORT COM by kernel program | |
| CN110070394A (en) | Data processing method, system, medium and calculating equipment | |
| CN104702636B (en) | Information interacting method, device and analogue system based on assembly function agent skill group | |
| CN109840725A (en) | Cargo picking method, device, electronic device and computer readable storage medium | |
| TWI651667B (en) | Interface system of virtual and physical integrated network with resources topology | |
| CN109873872A (en) | A kind of cloud electrical connector and method for supporting mixing cloud mode | |
| CN113515267A (en) | PaaS platform based on industrial Internet of things | |
| TWI608442B (en) | Software definition driven cloud computing network component service assembly system | |
| CN107888545A (en) | A kind of connection method between ESB connector and functional entity | |
| CN107172139A (en) | A kind of radio protocol stack and its implementation | |
| CN109857965A (en) | Products of Meteorological Services publisher server control system and method based on SOA | |
| CN110324194A (en) | Method, apparatus, system and medium for load balancing | |
| CN108234608A (en) | A kind of method of data synchronization between power grid ERP system and third party system | |
| CN102541539A (en) | Method for designing intelligent panel of supply chain based on M2M (Machine to Machine) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20180406 |