CN110519730B

CN110519730B - Method and device for managing, arranging and docking service system and NFV

Info

Publication number: CN110519730B
Application number: CN201910858581.5A
Authority: CN
Inventors: 夏小银; 田斌
Original assignee: Hangzhou Xinyun Zhichuang Technology Co ltd
Current assignee: Hangzhou Xinyun Zhichuang Technology Co ltd
Priority date: 2019-09-11
Filing date: 2019-09-11
Publication date: 2021-11-26
Anticipated expiration: 2039-09-11
Also published as: CN110519730A

Abstract

The invention discloses a method and a device for managing, arranging and docking a service system and an NFV (network file system), and particularly relates to the field of NFVs (network file systems) of telecommunication operators, wherein the service system is docked with an MANO (management and management object) through an MANO middleware, and the MANO middleware is a service system for realizing a C10 interface between VNF service system software and VNFM, a C8 interface between EMS/OMC and VNFM and a northbound enhanced interface between EMS/OMC and NFVO. The invention only needs the service system software to develop according to the universal interface between the middleware and the service system software, the development difficulty, the development workload and the direct butt joint of the service system software and the MANO are greatly reduced, except for adding a device applying the method, the invention does not need to modify the network, does not need to add any further operation, and can realize the rapid and reliable butt joint of the service system and the MANO of different manufacturers and different versions.

Description

Method and device for managing, arranging and docking service system and NFV

Technical Field

The invention relates to the technical field of telecommunication operator NFV, in particular to a method and a device for managing, arranging and docking a service system and NFV.

Background

Telecom operators promote NFV construction work from 2015, and China Mobile requires to support NFV from 2018 for newly-built systems, but operators of Ve-Vnfm-VNF (C10) interfaces between VNF and VNFM and Ve-Vnfm-em (C8) interface specifications between EMS/OMC and VNFM still do not release formal versions so far, so that the release of the formal versions is a pilot specification at present, the pilot specification is frequently updated, and in the pilot process, some provinces of the specifications have two branch versions of group and province. While many manufacturers offer MANO products, the understanding of each MANO manufacturer is biased due to the unpublished official version, resulting in different C8/C10 interfaces for each MANO manufacturer.

Therefore, for manufacturers who only have VNFs and do not have MANOs, NFV deployment on a telecommunication cloud resource pool becomes more difficult if their own service systems are to be implemented, and service online time cannot be guaranteed.

Disclosure of Invention

In order to overcome the above-mentioned defects in the prior art, embodiments of the present invention provide a method and an apparatus for managing, arranging, and docking a service system and NFV, which shield version differences of MANO specifications at different times, different branches, and different MANO manufacturers for a service system manufacturer by using a MANO middleware, so that a VNF of the service system manufacturer can rapidly implement NFV deployment, and thus the service system manufacturer can better focus on service innovation and service optimization.

In order to achieve the purpose, the invention provides the following technical scheme: a method for managing, arranging and docking a service system and an NFV is characterized in that the service system is docked with an MANO through an MANO middleware, the MANO middleware realizes a C10 interface between VNF service system software and a VNFM, a C8 interface between EMS/OMC and the VNFM and a northbound enhanced interface between EMS/OMC and NFVO for the service system, and realizes a VNF instantiation process, a VNF elastic capacity expansion and contraction process, a VNF self-healing process and a VNF termination process for the service system.

In a preferred embodiment, the VNF flexible capacity expansion and reduction process includes a manual capacity expansion process, a manual capacity reduction process, an automatic capacity expansion process, and an automatic capacity reduction process.

A business system and NFV management and arrangement butt joint method comprises the following specific butt joint steps:

s1, starting the virtual machine by VNFM, injecting host names, internet access information, NFVO/VNFM information and custom information into VNFM after starting by file injection, pulling up an initialization script of the MANO middleware, completing corresponding configuration by the initialization script according to the injected information, and starting the MANO middleware program;

s2, initiating an instantiation process to the MANO middleware by the VNFM, establishing connection between the EMS of the MANO middleware and the service system software management interface module, and informing the service system software management interface module to start service system software;

s3, the MANO middleware service system software management interface module downloads service system software and configuration files generated by the EMS for the service system software from the EMS, and starts the service system software;

s4, the VNFM acquires instantiation progress from the MANO middleware regularly, and the MANO middleware feeds back progress to the VNFM; if all the service system software is successfully started, the instantiation progress is fed back to be 100%, and the VNFM does not obtain the instantiation progress from the MANO middleware any more;

s5, VNFM informs MANO middleware of the completion of instantiation, if the service system software needs to be configured with relevant service, the MANO middleware configures the service system software;

s6, if the automatic capacity expansion condition or the manual capacity expansion is satisfied, the VNFM informs the MANO middleware to perform capacity expansion, and if the MANO middleware judges that the capacity expansion is allowed, the MANO middleware processes and configures the related resources;

s7, the VNFM acquires the capacity expansion progress from the MANO middleware regularly, the MANO middleware feeds back the progress to the VNFM, if the capacity expansion service system software is started successfully, the capacity expansion progress is fed back to 100%, and the VNFM does not acquire the capacity expansion progress from the MANO middleware any more;

s8, VNFM informs MANO middleware to complete expansion, if relevant service system software needs service configuration, the MANO middleware configures the relevant service system software;

s9, if meeting the automatic capacity reduction condition or manual capacity reduction, VNFM informs MANO middleware to carry out capacity reduction, if MANO middleware judges that capacity reduction is allowed, the MANO middleware processes and configures relevant resources to realize service migration;

s10, the VNFM acquires a capacity reduction preparation progress from the MANO middleware regularly, the MANO middleware feeds back a progress to the VNFM, if the service migration is completed, the feedback progress is 100%, and the VNFM does not acquire the progress from the MANO middleware any more;

s11, VNFM informs MANO middleware of the completion of capacity reduction, if the relevant service system software needs to be configured, the MANO middleware configures the relevant service system software;

s12, the MANO middleware judges whether a self-healing process needs to be initiated, and then requests the VNFM to initiate self-healing operation;

and S13, if the VNF is required to be terminated, the VNFM initiates a VNF termination flow to the MANO middleware, and if the MANO middleware judges that termination is allowed, all business system software is closed.

By adopting the technical scheme of the invention, the service system software is only required to be developed according to the universal interface between the middleware and the service system software, so that the development difficulty, the development workload and the direct connection of the service system software and the MANO are greatly reduced. The invention has the obvious advantages that the device applying the method is added, the network is not required to be modified, any further operation is not required to be added, and the service system can be quickly and reliably butted with MANOs of different manufacturers and different versions.

A device for managing, arranging and docking a service system and an NFV comprises a service system software management interface module and an EMS module, wherein the EMS module comprises a northbound enhanced interface module, an OMC module, a database module, a C10 interface module and a C8 interface module, and the service system software management interface module interacts with service system software through SOCKET, HTTP and SNMP.

In a preferred embodiment, the northbound enhanced interface module interacts with the NFVO through a northbound enhanced interface; the C10 interface module interacts with a VNFM through a C10 interface, and the C10 interface is specifically a Ve-Vnfm-vnf interface; the C8 interface module interacts with VNFM through a C8 interface, the C8 interface is a Ve-Vnfm-em interface, the device can be butted with MANOs of different manufacturers and different versions through the cooperation of the modules to complete the NFV deployment of the service system, and in addition, the device is added between the service system and the MANO without modifying the MANO equipment.

The invention has the technical effects and advantages that:

1. the service system is butted with the MANO through the MANO middleware, the MANO middleware realizes a C10 interface between VNF service system software and VNFM, a C8 interface between EMS/OMC and VNFM and a northbound enhancement interface between EMS/OMC and NFVO for the service system, and realizes VNF instantiation process, VNF elastic expansion and contraction capacity process, VNF self-healing process and VNF termination process for the service system, only the service system software needs to be developed according to a general interface between the middleware and the service system software, and the development difficulty, the development workload and the direct MANO butting of the service system software are greatly reduced;

2. the invention can realize the rapid and reliable butt joint of the service system and MANOs of different manufacturers and different versions without modifying the network and adding any further operation except adding the device applying the method;

3. by using the MANO middleware to shield version differences of MANO specifications in different periods, different branches and different MANO manufacturers for a service system manufacturer, the VNF of the service system manufacturer can quickly realize NFV deployment, so that the service system manufacturer can better focus on service innovation and service optimization.

Drawings

Fig. 1 is a logic diagram of embodiment 1 of the present invention.

Fig. 2 is a flowchart illustrating an instantiation process of a VNF in embodiment 2 of the present invention.

Fig. 3 is a schematic view of a VNF capacity expansion flow according to embodiment 3 of the present invention.

Fig. 4 is a schematic view of a VNF capacity reduction process in embodiment 4 of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example 1:

the external interface of MANO middleware device for implementing the method of the invention is shown in figure 1 when networking and implementing: the service system software management interface module in the device and the service system software are deployed on the same VM, and the service system software management interface module can be connected with the service system software by adopting SOCKET, HTTP, SNMP and the like; the system comprises a northbound enhanced interface module, an OMC module, a database module, a C10 interface module and a C8 interface module of EMS (enhanced message service) which are deployed on a single VM (virtual machine), wherein the northbound enhanced interface module is connected with NFVO (network function object) through a northbound enhanced interface, a C10 interface module is connected with VNFM through a C10 interface, a C8 interface module is connected with VNFM through a C8 interface, an internal interface is arranged between the EMS and a service system software management interface module, and SOCKET (SOCKET set), HTTP (hyper text transport protocol) and SNMP (simple network management protocol) are adopted for connection;

the MANO middleware device has the following specific external interfaces:

c10 interface:

the VNFM performs message interaction with the VNF through a C10 interface, which mainly includes:

1) VNFM to VNF message: establishing a connection with the VNF; configuration management of deployment correlation (VNF non-application layer) in processes of initialization, capacity expansion, self-healing and the like of the VNF instance is completed; notification of capacity reduction preparation; initializing and detecting the progress of expansion and contraction; acquiring performance index data related to the expansion and contraction capacity; and self-healing completion notification, etc.;

2) VNF to VNFM information: and initiating a VNF self-healing process.

C8 interface:

the VNFM carries out message interaction with the EMS/OMC through a C8 interface, and mainly comprises the following steps:

VNFM to EMS/OMC messages: establishing connection with EMS/OMC; notification of completion of preparation of the scaled-down volume of the VNF instance, and notification of VNF lifecycle changes (including instantiation completion, scaled-down volume completion, termination).

Northbound enhanced interface:

the northbound enhanced interface is an interface between the OMC and the NFVO and is divided into an uplink interface and a downlink interface, wherein the uplink interface refers to an interface from the OMC to the NFVO, and the downlink interface refers to an interface from the NFVO to the OMC; the method mainly comprises the following steps:

1) resource data interface: the data volume is relatively small, the periodic unidirectional transmission (uplink) is realized, and the data delay requirement is low;

2) performance data interface: the data volume is relatively large, the periodic unidirectional transmission (uplink) is realized, and the data delay requirement is general;

3) an alarm data interface: the data volume of single information is small, the total data volume is large, and the data is required to be transmitted in real time;

4) an operation instruction interface: the operation instruction channel interface of the network equipment provides a downlink instruction channel for the upper network management and feeds back an operation instruction to return a result, so that the data volume is relatively small, and the real-time requirement is high.

The english abbreviations therein are defined as follows:

NFV: network function virtualization;

VNF: VirtualisedNetworkFunction, virtualizing network functions;

VDU: a virtualisation deployment unit;

EMS: an element management system, a network element management system;

OMC: OperationdMaintenence center, operating maintenance center;

NFVO: a network function virtualisation orchestrator;

VIM: virtualisedlnfrastructure manager, virtualizing an infrastructure manager;

VNFM: virtualised network function manager, a virtualized network function manager;

VM: VirtualMachine, virtual machine.

Example 2:

the VNF instantiation process of the present invention is described in detail with reference to fig. 2 as follows:

1. after the resources are distributed, the VNFM calls an authentication interface of the MANO middleware, the authentication interface carries a user and a password, the interface is called once every several seconds (such as 10 seconds), the overtime time is several seconds (such as 600 seconds), and the instantiation fails after the overtime;

2. after the VNFM is connected with the MANO middleware, the MANO middleware feeds back token to the VNFM;

3. the VNFM calls an interface 'SetInitialconfiguration' to configure deployment (instantiation) related parameters;

4. the MANO middleware returns a "SetInitialConfiguration" response to the VNFM;

5. and initiating VNF instantiation progress detection to the MANO middleware by the VNFM calling interface 'GetProress', wherein the eventtype parameter is instantiate, and detecting whether the instantiation is finished. The interface is called once every several seconds (such as 10 seconds), the overtime time is several seconds (such as 600 seconds), and the instantiation fails after the overtime;

6. the MANO middleware feeds back the instantiation progress to the VNFM, and when the instantiation progress fed back by the MANO middleware is 100%, the VNF is successfully instantiated, and the VNFM does not send a 'GetProress' message to the MANO middleware any more;

7. after the VNF instantiation is completed, calling an interface VNFLifycyclechensNotification (VNFM-EM) to inform the MANO middleware of the completion of the instantiation;

8. if the service system software of the VNF needs to be configured, the MANO middleware needs to send a configuration request message to the service system software of the VNF for configuration;

9. the VNF's business system software returns a configuration response to the MANO middleware.

Example 3:

the VNF capacity expansion flow of the present invention is described in detail with reference to fig. 3 as follows:

1. the VNFM calls a VNFLCMGrant request interface to notify the MANO middleware that the capacity of the VNF is to be expanded;

2. and the MANO middleware determines whether to allow the VNFM to expand the VNF or not according to the condition that the MANO middleware operates the VNF and the requirement of avoiding operation conflict. If the MANO middleware allows, the VNFM carries out the subsequent process, if the MANO middleware does not allow, the VNFM sets the JobStatus as Error, and the task is ended;

3. a VNFM calling interface VNFLifycycleChangsNotification (VNFM-VNF) informs the MANO middleware of VNF resource processing completion and carries out configuration of related capacity expansion parameters;

4. the MANO middleware returns a response of 'VNFLiffycycleChangeNotification (VNFM-VNF)' to the VNFM;

5. and initiating VNF capacity expansion progress check to the MANO middleware by the VNFM calling interface 'GetProress', detecting whether the capacity expansion is finished or not, wherein the carried eventtype is scaleout. The interface is called once every a plurality of seconds (such as 10 seconds), the overtime time is a plurality of seconds (such as 1800 seconds), and the capacity expansion fails after the overtime;

6. the MANO middleware feeds back the capacity expansion progress to the VNFM, when the capacity expansion progress fed back by the MANO middleware is 100%, the VNF is indicated to be successfully expanded, and the VNFM does not send a 'GetProress' message to the MANO middleware any more;

7. a VNFM calling interface VNFLifeccechensNotification (VNFM-EM) informs the MANO middleware of finishing the capacity expansion;

Example 4:

the VNF capacity reduction process of the present invention is described in detail with reference to fig. 4 as follows:

1. the VNFM calls a VNFLCMGrant request interface to inform the MANO middleware of carrying out capacity reduction on the VNF;

2. and the MANO middleware determines whether to allow the VNFM to reduce the capacity of the VNF or not according to the situation that the MANO middleware operates the VNF and the requirement of avoiding operation conflict. If the task is allowed, the VNFM carries out the subsequent process, and if the task is not allowed, the VNFM sets the JobStatus as Error, and the task is ended;

3. the VNFM call interface "vnfprescalemotification (VNFM-VNF)" sends a capacity reduction preparation notification to the MANO middleware;

4. the MANO middleware sends a service blocking request to service system software to inform the service system software of migrating services;

5. the MANO middleware returns a response of "VNFPReScaleNuotification (VNFM-VNF)" to the VNFM;

6. the VNFM calls interface 'GetProress' to initiate VNF capacity reduction preparation (service migration) check to the MANO middleware, and whether the capacity reduction preparation is completed is detected. The interface is called once every a plurality of seconds (such as 10 seconds), the overtime time is a plurality of seconds (such as 1800 seconds), and the capacity shrinkage fails after the overtime;

7. after the service system software finishes the service migration, the service blocking response is returned to the MANO middleware;

8. the MANO middleware feeds back a capacity reduction preparation (service migration) progress to the VNFM, when the capacity reduction preparation progress fed back by the VNF is 100%, the VNF capacity reduction preparation is indicated to be successful, and the VNFM does not send a 'GetProress' message to the MANO middleware any more;

9. a VNFM calling interface VNFLifeccechensNotification (VNFM-VNF) informs the MANO of the completion of the reduction of the middleware;

10. the MANO middleware returns a response of 'VNFLiffycycleChangeNotification (VNFM-VNF)' to the VNFM;

11. after the VNF is reduced, a VNFM calling interface VNFLifycyclechensNotification (VNFM-EM) informs the MANO middleware of the reduction completion;

12. if the service system software of the VNF needs to be configured, the MANO middleware needs to send a configuration request message to the service system software of the VNF for configuration;

13. the VNF's business system software returns a configuration response to the MANO middleware.

The points to be finally explained are: first, in the description of the present application, it should be noted that, unless otherwise specified and limited, the terms "mounted," "connected," and "connected" should be understood broadly, and may be a mechanical connection or an electrical connection, or a communication between two elements, and may be a direct connection, and "upper," "lower," "left," and "right" are only used to indicate a relative positional relationship, and when the absolute position of the object to be described is changed, the relative positional relationship may be changed;

secondly, the method comprises the following steps: in the drawings of the disclosed embodiments of the invention, only the structures related to the disclosed embodiments are referred to, other structures can refer to common designs, and the same embodiment and different embodiments of the invention can be combined with each other without conflict;

and finally: the above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that are within the spirit and principle of the present invention are intended to be included in the scope of the present invention.

Claims

1. A method for service system and NFV management and orchestration interfacing, comprising: the service system is in butt joint with the MANO through the MANO middleware, the MANO middleware realizes a C10 interface between VNF service system software and VNFM, a C8 interface between EMS/OMC and VNFM and a northbound enhancement interface between EMS/OMC and NFVO for the service system, and realizes a VNF instantiation process, a VNF elastic expansion and contraction capacity process, a VNF self-healing process and a VNF termination process for the service system;

the VNF elastic expansion and contraction flow comprises a manual expansion flow, a manual contraction flow, an automatic expansion flow and an automatic contraction flow;

the specific butt joint steps are as follows:

2. An apparatus for implementing the service system and NFV management and orchestration interfacing method of claim 1, wherein: the system comprises a service system software management interface module and an EMS module, wherein the EMS module comprises a northbound enhanced interface module, an OMC module, a database module, a C10 interface module and a C8 interface module, and the service system software management interface module interacts with service system software through SOCKET, HTTP and SNMP.

3. The apparatus according to claim 2, wherein the apparatus for implementing the service system and NFV management and orchestration interfacing method is further configured to: the northbound enhanced interface module interacts with the NFVO through a northbound enhanced interface; the C10 interface module interacts with a VNFM through a C10 interface, and the C10 interface is specifically a Ve-Vnfm-vnf interface; the C8 interface module interacts with VNFM through a C8 interface, the C8 interface is a Ve-Vnfm-em interface, and through cooperation of the modules, the device can be in butt joint with MANOs of different manufacturers and different versions to complete service system NFV deployment.