WO2019047835A1 - Instantiation method for virtual network function - Google Patents
Instantiation method for virtual network function Download PDFInfo
- Publication number
- WO2019047835A1 WO2019047835A1 PCT/CN2018/104055 CN2018104055W WO2019047835A1 WO 2019047835 A1 WO2019047835 A1 WO 2019047835A1 CN 2018104055 W CN2018104055 W CN 2018104055W WO 2019047835 A1 WO2019047835 A1 WO 2019047835A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- paas
- vnf
- vnfm
- instance
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Definitions
- the present application relates to the field of communications, and in particular, to an instantiation method, related device, and system for a virtual network function.
- the traditional telecommunication system is composed of various dedicated hardware devices, and different applications use different hardware devices.
- the system becomes more and more complex, which brings many challenges, including the development of new services, the operation and maintenance of the system, and resource utilization.
- the world's 13 major telecom operators jointly released the NFV white paper. It also announced the establishment of NFV ISG at ETSI to develop NFV requirements and technical framework to promote the development of NFV.
- NFV Network Function Virtualization
- COTS Commercial-off-the- Shelf
- each network element used in the telecommunication network can be transformed into a stand-alone application, which can be flexibly deployed on a unified infrastructure platform built by standards-based servers, storage, and switches, and through virtualization technology to the infrastructure.
- Hardware device resource pooling and virtualization providing virtual resources to upper-layer applications, enabling application and hardware decoupling, enabling each application to rapidly increase virtual resources to achieve rapid expansion of system capacity, or to rapidly reduce virtual resources to achieve shrinkage
- the purpose of system capacity greatly enhances the flexibility of the network.
- the common COTS server is used to form a shared resource pool. The newly developed services do not need to be separately deployed with hardware devices, which greatly shortens the time for new services to go online.
- PaaS Platform as a Service
- SaaS Software as a Service
- IaaS Infrastructure as a Service
- a typical PaaS platform should provide the following functions: 1) Application runtime environment: including distributed computing runtime environment, multiple types of data storage, dynamic resource scaling; application lifecycle support: including development of SDK, IDE, etc. Develop, test, and deploy. 2) Public service: Provide public services in the form of API, such as queue service, storage service and cache service, monitor, manage and measure: provide resource pool, application system management and monitoring functions, accurate measurement; 3) integration, composite application Building capabilities: including connectivity services, integration services, messaging services, and process services.
- each VNF component (VNFC) constituting the VNF instance is closely coupled with the lifecycle management of the VNF instance, and is inseparable.
- VNF virtualized network element
- functions included in the VNF such as mobility management, session management, and QoS management can be decomposed into different VNFCs.
- MME Mobility Management Function
- each VNFC instance monopolizes the virtual resources of one VM and releases the occupied VM resources along with the termination of the VNF instance.
- the advantage of this management method is to ensure the resource isolation between VNFCs and to provide high-reliability service guarantee for carrier-grade VNF.
- each VM since each VM is monopolized by one VNFC, the utilization of VM resources is not high, and it is difficult to ensure large-scale deployment of VNF functions.
- VNFC When the original design principles of the cloud are introduced into the VNF implementation, the functions of the VNF will be further deconstructed and even micro-served. If VNFC still adopts a lifecycle management method closely coupled with the VNF instance, a large number of VNFC instances consume a large amount of VM resources (or a finer granular container resource), resulting in low utilization of virtual resources of the NFVI layer, thereby Affect the operational efficiency of VNF instances.
- An embodiment of the present application provides an instantiation method, a related device, and a system for a virtual network function, and implements lifecycle management of PaaS services of certain types (for example, public services) through interaction between MANO and PaaS management entities of NFV. (instantiation, elastic scaling, termination) is separated (decoupled) from the VNF lifecycle management that invokes it.
- an embodiment of the present application provides a method for instantiating a virtual network function VNF, including: a virtual network function manager VNFM receiving a VNF instantiation request, where the VNF instantiation request carries an identifier of a VNF that needs to be instantiated Determining, by the VNFM, a PaaS service that the VNF instance needs to invoke according to a mapping relationship between the PaaS service and the VNF, and determining a capacity of the PaaS service that the VNF instance needs to invoke; the VNFM sending the to the PaaS management entity a configuration request of the PaaS service, the configuration request carrying the PaaS service identifier, the capacity and the identifier of the tenant to be called, the tenant corresponding to the VNF of the PaaS service; the VNFM is allocated according to the PaaS management entity The PaaS service instance of the specified capacity of the VNF completes instantiation of the VNF.
- the VNF instance needs to invoke the PaaS service as a public service.
- the solution of the embodiment of the present application improves the utilization of the NFVI virtual resource and the operating efficiency of the VNF instance, because the lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance.
- the PaaS service that the VNF instance needs to invoke further includes a proprietary service
- the method further includes: the VNFM sending, to the PaaS management entity, a request for instantiating the proprietary service, where the request carries the requirement
- the instantiated proprietary service identifies and instantiates operational parameters; the VNFM completes instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
- the embodiment of the present invention further includes the cooperative call of the public service and the proprietary service to the PaaS platform during the VNF instantiation process, thereby further improving the flexibility of the VNF instance deployment and the overall efficiency of the virtual resource management.
- the method further includes: the VNFM receives the VNF instance elastic scaling request, where the elastic scaling request carries the VNF instance identifier and the elastic scaling operation parameter; and the VNFM determines according to the mapping relationship between the PaaS service and the VNF.
- the VNFM sends an elastic scaling request to the PaaS management entity, where the elastic scaling request carries the called private service identifier and the elastic scaling operation parameter; the VNFM Receiving an execution result of the elastic scaling returned by the PaaS management entity.
- the VNFM receives a VNF instance termination request, where the VNF instance termination request carries a VNF instance identifier that needs to be terminated; and the VNFM determines, according to a mapping relationship between the PaaS service and the VNF, the VNF instance that needs to be terminated.
- a public service the VNFM sends a public service configuration request to the PaaS management entity, where the configuration request carries a public service identifier that needs to be terminated and a tenant identifier corresponding to a VNF that invokes the public service; and the VNFM receives the PaaS management The response message of the public service configuration returned by the entity; the VNFM completes the termination process of the VNF instance according to the public service configuration response message.
- the VNFM determines, according to the mapping relationship between the PaaS service and the VNF, that the PaaS service invoked by the VNF instance that needs to be terminated further includes a proprietary service, where the method further includes: the VNFM managing the entity to the PaaS Initiating a proprietary service termination request, the termination request carrying an identifier of a proprietary service instance that needs to be terminated. Receiving, by the VNFM, the response message of the proprietary service instance termination returned by the PaaS management entity; the VNFM completing the finalization process of the VNF instance according to the response message terminated by the proprietary service instance and the public service configuration response message .
- mapping relationship between the PaaS service and the VNF is stored in a descriptor file VNFD of the VNF, and the VNFM obtains the mapping relationship from the VNFD.
- the VNFM obtains, from the VNFD file of the VNF, a capacity of a PaaS service that the VNF needs to use when instantiating, where the capacity includes an instance number of the PaaS service.
- an embodiment of the present invention provides an instantiation method for a virtual network function VNF, including: a PaaS management entity receives a PaaS service configuration request sent by a VNFM, where the configuration request carries a PaaS service name that needs to be invoked, and a PaaS service And a tenant identifier corresponding to the VNF that invokes the PaaS service; the PaaS management entity assigns the PaaS service of the specified capacity to the tenant according to the configuration request; the PaaS management entity returns to the VNFM The execution result of the PaaS service configuration.
- the configuration request carries a PaaS service that needs to be invoked as a public service.
- the method further includes: the PaaS management entity receives a request for instantiating a proprietary service sent by the VNFM, where the request carries a proprietary service name and an instantiated operation parameter that need to be instantiated; The PaaS management entity receives the instantiation request, instantiating the proprietary service according to an instantiated operational parameter in the request; the PaaS management entity returns an execution result of the proprietary service instantiation to the VNFM.
- the method further includes: the PaaS management entity receiving the elastic scalability request sent by the VNFM, where the elastic scalability request carries the PaaS-specific service identifier and the elastic scaling operation parameter of the call;
- the PaaS management entity performs elastic scaling of the PaaS proprietary service according to the elastic scaling request and returns an execution result of the elastic scaling to the VNFM.
- the capacity of the PaaS service includes the number of instances of the PaaS service.
- the embodiment of the present invention further provides a virtual network function manager VNFM, including: a processing module, a sending module, and an instantiation module; the processing module is configured to perform an instance according to a VNF instantiation request The identifier of the VNF, and the mapping relationship between the PaaS service and the VNF, determining the PaaS service that the VNF instance needs to invoke, and further determining the capacity of the PaaS service that the VNF instance needs to invoke; the sending module, a configuration request for sending the PaaS service to the PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity and the identifier of the tenant, and the tenant corresponds to the VNF that invokes the PaaS service; And an instantiation module, configured to complete instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
- VNFM virtual network function manager
- the VNF instance needs to invoke the PaaS service as a public service.
- the PaaS service that the VNF instance needs to invoke further includes a proprietary service, where the sending module is further configured to send, to the PaaS management entity, a request to instantiate the proprietary service, where the request carries an instantiation that needs to be instantiated.
- the proprietary service identifies and instantiates the operational parameters; the instantiation module is further for completing the instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
- the implementation of the present invention further provides a PaaS management entity, including a service module and a response module, where the service module is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service that needs to be invoked. a name, a capacity of the PaaS service, and a tenant identifier corresponding to the VNF that invokes the PaaS service; and assigning the PaaS service of the specified capacity to the tenant according to the configuration request; the response module is configured to The VNFM returns the execution result of the PaaS service configuration.
- a PaaS management entity including a service module and a response module, where the service module is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service that needs to be invoked. a name, a capacity of the PaaS service, and a tenant identifier corresponding to the VNF that invokes the PaaS service; and assigning the PaaS service
- the configuration request carries a PaaS service that needs to be invoked as a public service.
- the service module is further configured to receive a request for instantiating a proprietary service sent by the VNFM, where the request carries a specific service name and an instantiated operation parameter that need to be instantiated; the service module Receiving the instantiation request, instantiating the proprietary service according to the instantiated operation parameter in the request; the response module is further configured to return an execution result of the proprietary service instantiation to the VNFM.
- the present invention provides an NFV network system, comprising the VNFM of any of the preceding aspects and the PaaS management entity of any of the foregoing.
- the implementation of the present invention further provides an instantiation method of a virtual network function VNF, including: the virtual network function manager VNFM receives a VNF instantiation request, and the VNF instantiation request carries an identifier of the VNF that needs to be instantiated.
- VNFM Determining, by the VNFM, a PaaS-specific service that the VNF instance needs to invoke according to a mapping relationship between the PaaS service and the VNF; the VNFM sending a request to the PaaS management entity to instantiate the proprietary service, where the request carries Instantiating a proprietary service name and instantiating operational parameters, the parameters including capacity of the proprietary service; the VNFM completing instantiation of the VNF based on the proprietary service instance instantiated on a PaaS platform .
- the present invention provides a computer readable storage medium comprising program instructions, when executed on a computer, causing the computer to perform the NFV instantiation method as described in any of the preceding aspects.
- the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the preceding aspects.
- FIG. 1 is a schematic diagram of a network architecture based on NFV MANO provided by an embodiment of the present application
- FIG. 2 is a schematic diagram of an alternative architecture for interfacing a PaaS and a MANO according to an embodiment of the present application
- FIG. 3 is a schematic flowchart of a method for instantiating a VNF according to an embodiment of the present application
- FIG. 4 is a schematic diagram of a VNF instance termination process provided by an embodiment of the present application.
- FIG. 5 is a schematic diagram of an elastic scaling process of a proprietary service instance according to an embodiment of the present application.
- FIG. 6 is a schematic diagram of an elastic scaling process of a public service instance according to an embodiment of the present application.
- FIG. 7 is a schematic diagram of a general PaaS service elastic scaling process provided by an embodiment of the present application.
- FIG. 8 is a schematic structural diagram of a device of a VNFM according to an embodiment of the present disclosure.
- FIG. 9 is a schematic structural diagram of a PaaS management entity device according to an embodiment of the present application.
- FIG. 10 is a schematic diagram of an NFV network system according to an embodiment of the present application.
- FIG. 11 is a schematic structural diagram of a VNFM or PaaS management entity according to an embodiment of the present application.
- FIG. 1 is a schematic diagram of an NFV-based network architecture, which mainly includes: an operation support system (OSS), a business support system (BSS), and an element management (EM) unit. , Virtual Network Function (VNF) unit, Network Function Virtualization Infrastructure (NFVI) unit, Common Service (CS) unit, and Network Function Virtualization Management and Orchestration (NFV MANO) system.
- VNF Virtual Network Function
- NFVI Network Function Virtualization Infrastructure
- CS Common Service
- NFV MANO Network Function Virtualization Management and Orchestration
- the NFV Management and Orchestration (NFV MANO) system includes the NFV Orchestrator (NFVO) unit, the Virtualized Network Function Management (VNF Manager, VNFM) unit, and the virtualization infrastructure. Management (Virtualised Infrastructure Manager, VIM) unit.
- the corresponding unit may be described by the abbreviation of each unit, for example, the network element management unit may be described as an EM or EM unit.
- the network element management unit may be described as an EM or EM unit.
- OSS/BSS is a support system for the integration and information resource sharing of telecom operators. It is mainly composed of network management, system management, billing, business, accounting and customer services, while the system passes through a unified information bus. Organically integrated. OSS/BSS can help operators determine the development direction of the system while helping them to develop their own operational support systems. It can also help users to formulate system integration standards and improve and improve users' business levels. The OSS/BSS is used in the NFV-based network architecture to make necessary modifications and adjustments to the lifecycle management (eg, instantiation, etc.) of each network element.
- NFV orchestrator (NFVO, NFV Orchestrator): NFVO implements network service descriptor (NSD, NS Descriptor), virtual network function forwarding map (VNFFG, VNF Forwarding Graph) management and processing, network service life cycle management, and VNFM cooperation Realize VNF lifecycle management and global view of virtual resources.
- NSD network service descriptor
- VNFFG virtual network function forwarding map
- VNFM cooperation Realize VNF lifecycle management and global view of virtual resources.
- VNFM implements lifecycle management of virtualized network functions VNF, including management of virtualized network function descriptors (VNFD, VNF Descriptor), instantiation of VNFs, and elastic scaling of VNF instances (including Scaling out/up and Scaling in/down), healing of VNF instances, and termination of VNF instances.
- VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.
- Virtual Infrastructure Manager responsible for infrastructure layer hardware resources, virtualized resource management (including reservation and allocation), virtual resource status monitoring and fault reporting, and virtualized resources for upper-layer applications Pool.
- OSS/BSS Operations and Business Support Systems: refers to the operator's existing operation and maintenance system OSS/BSS.
- Element Management System Performs traditional fault, configuration, user, performance, and security management (FCAPS, Fault Management, Configuration Management, Account Management, Performance Management, Security Management) functions for the VNF.
- FCAPS Fault Management, Configuration Management, Account Management, Performance Management, Security Management
- VNF Virtualized Network Function
- PNFs physical network functions
- MME virtualized EPC nodes
- SGW SGW
- PGW PGW
- VNF can be composed of multiple lower-level VNF components (VNFC, VNF Component). Therefore, a VNF can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component function; VNF It can also be deployed on a VM.
- VNFC lower-level VNF components
- VNF Component VNF Component
- NFV Infrastructure NFV Infrastructure: NFVI consists of hardware resources and virtual resources and a virtualization layer. From a VNF perspective, the virtualization layer and hardware resources appear to be a complete entity that provides the required virtual resources.
- this application proposes a lifecycle management method for NFV PaaS services, which differentiates lifecycle management for public services and proprietary services that make up VNF, thereby improving the utilization of NFVI layer virtual resources and VNF.
- lifecycle management refers to a set of functions used to manage the instantiation, maintenance, and termination of a VNF or NS.
- PaaS management functions (referred to as PaaS management entities) that constitute VNF's public services, proprietary services, and operation and maintenance management of these services are deployed on the PaaS platform, as shown in Figure 2.
- the PaaS platform provides an application programming interface (API) for the VNF or application that calls the PaaS platform service on the northbound interface, and the PaaS management entity interfaces the operation and maintenance management of the PaaS platform service with the MANO system to implement the cloud-oriented Unified operation and maintenance management of VNF instances with native features.
- API application programming interface
- the PaaS management entity interfaces the operation and maintenance management of the PaaS platform service with the MANO system to implement the cloud-oriented Unified operation and maintenance management of VNF instances with native features.
- the ETSI standard has not yet determined the interoperability framework of standardized PaaS and MANO.
- the architecture shown in Figure 2 is a viable alternative architecture.
- the anchor entity of the PaaS management entity function accessing the MANO system is VNFM.
- VNF instances with Cloud-Native features consist of public services (also known as VNF public services) and proprietary services (also known as VNF proprietary services).
- Public service A modular service or function that can be invoked by one or more applications or services in a functional definition.
- the created public service instance is called by one or more applications or service instances.
- Proprietary services Identify, in a functional definition, a modular service or function that can only be invoked by a particular collection of applications or services. A created proprietary service instance can only be called by an application or service instance.
- VNF virtual network element
- a modular service or application can be atomic (for example, microservices) or a combination of multiple atomization functions.
- the public service and the proprietary service deployed on the PaaS platform (referred to as PaaS public service and PaaS proprietary service, or further referred to as public service and proprietary service, respectively, in the embodiments of the present invention) ), using the following differentiation method to implement lifecycle management of PaaS service instances that make up VNF:
- the public service instance on the PaaS platform its life cycle is managed autonomously by the PaaS platform.
- the management surface of the PaaS platform (or PaaS management entity) performs instantiation of public services, scale, and cure. (Heal) and final operations.
- the lifecycle management of a public service instance is completely decoupled from the lifecycle management of the VNF instance that invokes it (ie, independent of each other, independent of each other), and the public service instance deployed on the PaaS platform uses the public service in the application or service that invokes it.
- the virtual resource allocation required for instantiation has been completed before.
- a proprietary service instance on the PaaS platform For a proprietary service instance on the PaaS platform, its lifecycle is bound to the lifecycle of the VNF instance that invoked it, and the proprietary service instance is created with the instantiation of the VNF instance that invoked it, along with the VNF that called it. The end of the instance ends. In this way, the lifecycle management of a proprietary service instance is fully coupled with the lifecycle management of the VNF instance that invokes it. The lifecycle management of the proprietary service instance is performed by the PaaS platform, but relies on VNF instance lifecycle management events from MANO. trigger.
- the following first takes a VNF instantiation process to call the service provided by the PaaS platform as an example to illustrate how to realize the separation (decoupling) between the PaaS service lifecycle management and the VNF lifecycle management that calls it.
- the embodiment of the present application provides a schematic diagram of a VNF instantiation method.
- the NFVM interacts with the PaaS management entity to complete the instantiation of the VNF, which is the life of the NFV PaaS service.
- a typical scenario of the cycle management method including but not limited to the following steps:
- VNFM The MANO (VNFM) receives a VNF instantiation request from the sender Sender (which may be NFVO or EM), and the instantiation request message carries the VNF identifier to be instantiated.
- the VNFM determines, according to the mapping relationship between the PaaS service and the VNF, the proprietary service and/or the public service that the instantiated VNF needs to invoke; the instantiated VNF may only invoke the proprietary service or only the public service;
- the service when the service is registered on the PaaS platform, it is necessary to notify MANO (for example: VNFM) of the registration event of the service, so that MANO obtains the service and the supported applications/services that call it.
- MANO for example: VNFM
- VNFM the MANO entity
- the MANO can subscribe to the service registration event on the corresponding PaaS platform to all PaaS management entities connected thereto.
- the PaaS management entity registers the PaaS service (public service or proprietary service) according to its own service registration requirement or plan, and finally The PaaS management entity sends a PaaS service registration notice to the MANO, and the notification message carries at least one of the following: a registered service name, a tenant type (corresponding to the VNF) supported by the service (ie, a serviceable), and service information.
- the tenant corresponding to the application or service that invokes the registration service may also be represented as a VNF.
- Service information refers to some descriptive information related to the service, such as: constraint or dependency information of the service call, and so on.
- the VNFM also determines the capacity of the PaaS service that the VNF instance needs to invoke when instantiating, or the size of the PaaS service capability that needs to be invoked; the capacity of the PaaS service, which may be the number of service instances required, It can also be the product of the number of service instances and the capacity of each service instance; the PaaS service capacity information supporting a certain VNF can be obtained by the VNFM from the VNFD of the VNF.
- the VNFM initiates a proprietary service instantiation request operation to the PaaS management entity, where the instantiation request message carries the identifier of the proprietary service that needs to be instantiated, and instantiates operational parameters, such as an initial capacity requirement after the instantiation of the proprietary service. .
- the PaaS management entity receives the instantiation request message, and performs instantiation of the PaaS proprietary service according to the indication of the parameter in the message.
- S305 The PaaS management entity returns a response message instantiated by the PaaS proprietary service to the VNFM.
- the VNFM initiates a public service configuration request to the PaaS management entity, where the configuration request message carries the configured public service name, the configured public service capacity (such as the number of instances), and the identifier information of the tenant that invokes the public service, and the tenant's The identifier corresponds to the VNF that invokes the PaaS service.
- the PaaS management entity receives the configuration request message, completes the binding of the public service and the tenant identity according to the parameter in the message, and allocates the public service of the specified capacity (such as the number of instances) in the message to the VNF instance corresponding to the tenant identifier. .
- S308 The PaaS management entity returns a response message of the PaaS public service configuration to the VNFM.
- VNFM completes the instantiation process of the VNF according to the PaaS proprietary service and/or the configuration-bound PaaS public service instance created by the instantiation.
- the instantiation operation of the PaaS proprietary service in steps S303-S305 and the configuration operation of the PaaS public service in steps S306-S308 may be interchanged, or concurrently executed. Not limited.
- the PaaS management entity autonomously triggers the execution of public service lifecycle management operations based on monitoring public services deployed on the PaaS platform, such as instantiation, resiliency, healing, or termination.
- the condition for triggering the execution of the operation may be based on a public service lifecycle management policy pre-configured by the operator in the PaaS management entity, for example, when the number of instances of a certain type of public service on the platform is less than one threshold, the public of the type
- the service performs auto-scale operations (automatic scaling, for example, to complete the specified scale out), and can also initiate the lifecycle management of the public service on demand through the human-machine interface mode.
- the PaaS management entity receives human-machine commands gracefully terminating all instances of this type of public service.
- the MANO entity for example, VNFM
- VNFM is not aware of the public service lifecycle management operations triggered by the PaaS management entity, but can obtain the real-time performance related to the public service instance lifecycle management by subscribing to the public service lifecycle management operation notification.
- the VNF instance information is used to invoke the cooperative operation of its VNF instance lifecycle management.
- the VNFM can obtain the public service instance through the subscription information of the public service instance lifecycle management operation information.
- the status for example, whether there is enough public service instance of the specified name available on the PaaS platform, so that a decision basis can be provided for initiating a public service configuration request to the PaaS management entity in step S306. It can be understood that if the VNFM knows There is no sufficient public service instance available on the PaaS platform, and the decision can not or temporarily fail to initiate a public service configuration request to the PaaS management entity.
- the method of the embodiment of the present invention implements the call of the VNF in the instantiation process to the PaaS service, especially the public service instance, through the interaction between the MANO and the PaaS management entity.
- the lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance, which improves the utilization of the NFVI virtual resource and the operating efficiency of the VNF instance.
- the embodiment of the present invention further includes the VNF instantiation process. Co-calling of public and proprietary services for the PaaS platform further enhances the flexibility of VNF instance deployment and the overall efficiency of virtual resource management.
- VNF instance termination process supporting the cloud native feature is further described below, as shown in FIG. 4:
- the VNFM receives a VNF instance termination request from the sender Sender (which may be NFVO or EM), where the instance termination request message carries the VNF instance identifier to be terminated.
- Sender which may be NFVO or EM
- the VNFM determines the proprietary service and the public service invoked by the terminated VNF instance according to the mapping relationship between the type of the tenant (corresponding to the VNF instance to be terminated) supported by the PaaS service and the service.
- the VNFM initiates a proprietary service termination request operation to the PaaS management entity, where the finalization request message carries the identifier of the proprietary service instance that needs to be terminated.
- the PaaS management entity receives the instance termination request message, and performs termination of the PaaS proprietary service instance according to the indication of the parameter in the message.
- S405 The PaaS management entity returns a response message of the PaaS proprietary service instance termination to the VNFM.
- the VNFM initiates a public service configuration request to the PaaS management entity, where the configuration request message carries the configured public service name and the identifier information of the tenant that invokes the public service.
- the PaaS management entity receives the configuration request message, completes the unbinding of the public service and the tenant identifier according to the parameter in the message, and releases the public service instance corresponding to the tenant identifier to the PaaS platform.
- S408 The PaaS management entity returns a response message of the PaaS public service configuration to the VNFM.
- VNFM completes the finalization process of the VNF instance according to the PaaS proprietary service instance terminated by the instantiation and the PaaS public service instance that is configured to be bound.
- the instantiation operation of the PaaS proprietary service in steps S403-S405 and the configuration operation of the PaaS public service in steps S406-S408 may be interchanged, or concurrently performed. Not limited.
- the interaction between the MANO of the NFV and the PaaS management entity realizes the termination of the VNF instance in the case of calling the PaaS platform service, and improves the lifecycle management of the NFV PaaS service capability call.
- the VNF instance elastic scaling that supports the native features of the cloud can be divided into two processes, which can be connected together or separately, as shown in Figure 5 and Figure 6.
- the VNF instance elastic scaling triggers the private service instance elastic scaling.
- Figure 6 shows the elastic scaling process of the PaaS public service instance.
- Step 501 The MANO (VNFM) receives a VNF instance resilience (VNF scale) request from the sender Sender (which may be NFVO or EM), and the elastic scalability request message carries the VNF instance identifier to be instantiated and is related to the elastic scaling operation.
- the information related to the elastic stretching operation includes the type of the elastic stretching operation ⁇ scale in, scale out ⁇ , the step size of the elastic stretching, and the like.
- Step 502 The VNFM determines the proprietary service invoked by the VNF instance according to the mapping relationship between the PaaS service and the tenant (which can correspond to the VNF) type supported by the service.
- Step 503 The VNFM initiates a proprietary service elastic scaling request operation to the PaaS management entity, where the elastic scalability request message carries the identifier of the proprietary service instance that needs to be elastically scaled and the information related to the elastic scaling operation.
- the information related to the elastic stretching operation includes the type of the elastic stretching operation ⁇ scale in, scale out ⁇ , the step size of the elastic stretching, and the like.
- Step 504 The PaaS management entity receives the elastic scalability request message, and performs elastic scaling of the PaaS proprietary service according to the indication of the parameter in the message.
- Step 505 The PaaS management entity returns a response message of the PaaS proprietary service elastic extension to the VNFM.
- Step 506 The VNFM completes the elastic scaling process of the VNF instance according to the elastic scaling result of the PaaS proprietary service instance.
- Figure 6 shows the process by which PaaS management subscribes to the VNFM for PaaS public service tenant elastic scaling.
- the PaaS management entity internally autonomously triggers the lifecycle management of the public service
- the subscription notification process shown in FIG. 6 in this embodiment can be used as a condition for triggering the PaaS management entity to perform an auto-scale operation, but PaaS
- the management entity can also further combine other monitoring information to determine whether to perform the auto-scale process of the public service.
- the subscription notification process shown in Figure 6 is decoupled from the auto-scale process that the PaaS management entity triggers to perform the public service.
- the PaaS management entity subscribes to the public service tenant elastic extension notification to the VNFM, and indicates the condition of the subscription event in the subscription request message, including the name of the public service.
- VNFM receives a VNF instance resiliency (VNF scale) request from the sender Sender (which may be NFVO or EM), and the elastic retraction request message carries information about the VNF instance identifier to be instantiated and the elastic scaling operation. .
- the VNFM determines the public service invoked by the VNF instance according to the mapping relationship between the tenant (which can correspond to the VNF) type supported by the PaaS service and the service.
- the VNFM sends a public service elastic extension notification to the PaaS management entity, where the notification message carries at least one of the following: the name of the public service
- the information about the tenant of the public service and the information related to the elastic extension operation includes the type of the elastic stretching operation ⁇ scale in, scale out ⁇ , the step size of the elastic stretching, and the like.
- FIG. 7 The process of FIG. 7 is similar to the process of FIG. 5.
- the private service instance and the public service instance to be elastically stretched are not differentiated, and the VNFM can be unified.
- the elastic operation request operation of the service operation command to the PaaS management entity (whether it is a proprietary service or a public service) is not described herein.
- each network element such as VNFM, the PaaS management entity, in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing various functions.
- VNFM the Cloud-to-Semiconductor
- the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
- the embodiment of the present invention may divide the functional units of the VNFM and the PaaS management entity according to the foregoing method.
- each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
- FIG. 8 shows a possible structural diagram of the VNFM 800 involved in the foregoing embodiment, including a processing module 801, a sending module 802, and an instantiation module 803.
- the processing module 801 is configured to determine, according to the identifier of the VNF that needs to be instantiated in the VNF instantiation request, and the mapping relationship between the PaaS service and the VNF, to determine the PaaS service that needs to be invoked by the VNF instance, and further determine Describe the capacity of the PaaS service that the VNF instance needs to invoke, such as the number of instances;
- the sending module 802 is configured to send a configuration request of the PaaS service to a PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity, and the identifier of the tenant, and the tenant correspondingly invokes the PaaS Service VNF;
- the instantiation module 803 is configured to complete instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
- the sending module 802 is further configured to send the instantiated to the PaaS management entity. a request for a proprietary service carrying a proprietary service identifier and instantiated operational parameters that need to be instantiated;
- the instantiation module 803 is further configured to complete instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
- FIG. 9 is a schematic structural diagram of a possible PaaS management entity involved in the foregoing embodiment, including: a service module 901 and a response module 902, where an integrated module or unit is used.
- the service module 901 is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service name that needs to be called, a capacity of the PaaS service (for example, an instance number), and a tenant corresponding to the VNF that invokes the PaaS service. Identifying, and assigning, according to the configuration request, the PaaS service of the specified capacity to the tenant;
- the response module 902 is configured to return an execution result of the PaaS service configuration to the VNFM.
- the PaaS service that needs to be invoked in the configuration request may be a public service
- the service module 901 is further configured to receive a request for instantiating a proprietary service sent by the VNFM, where the request carries a specialization that needs to be instantiated. Having a service name and instantiating an operational parameter; the service module receiving the instantiation request, instantiating the proprietary service based on an instantiated operational parameter in the request; the response module 902 is further for The VNFM returns the execution result of the proprietary service instantiation.
- VNFM and PaaS management entities may refer to the embodiments described in the foregoing FIGS. 3-7.
- the corresponding process of the VNFM and PaaS management entities will not be described here.
- the foregoing embodiment is only an example, and the embodiment of the present invention is not limited thereto. Therefore, the VNFM and the PaaS management entity provided by the embodiment of the present invention implement the VNF in the process of instantiation to the PaaS service, especially the public service instance. Call.
- the lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance, which improves the resource utilization and the operating efficiency of the VNF instance.
- the embodiment of the present invention further includes the VNF instantiation process for the PaaS.
- the platform's public service and proprietary service are called together, which further solves the PaaS platform service call problem in complex scenarios.
- the embodiment of the present invention further provides an NFV network system.
- the NFV network system 1000 includes a VNFM and a PaaS management entity.
- each module may be referred to each functional module in the system, and details are not described herein again.
- VNFM and PaaS management entities in all of the foregoing embodiments of the present invention may be implemented in the form of a computer device.
- FIG. 11 is a schematic structural diagram of a virtual network function manager VNFM or a PaaS management entity according to an embodiment of the present application.
- the network element includes a processor 1101, a memory 1102, and a transceiver 1103.
- the processor 1101 is coupled to the memory 1102 and the transceiver 1103, for example, the processor 1101 can be coupled to the memory 1102 and the transceiver 1103 via a bus.
- the processor 1101 may be configured to support the VNFM to perform the corresponding functions in the method embodiments described in Figures 2-7, and may also be configured to support the PaaS management entity to perform the corresponding functions in the methods described in Figures 2-7.
- the processor 1101 can be a central processing unit (CPU), a network processor (in English), a hardware chip, or any combination thereof.
- the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
- ASIC application-specific integrated circuit
- PLD programmable logic device
- the above PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or Any combination thereof.
- the memory 1102 is used to store program codes and the like.
- the memory 1102 may include a volatile memory (English: volatile memory), such as a random access memory (English: random access memory, abbreviation: RAM); the memory 1102 may also include a non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 1102 may also include a combination of memories of the above kind.
- ROM read-only memory
- flash memory English: flash memory
- HDD hard disk drive
- SSD solid state drive
- the transceiver 1103 can be a communication module and a transceiver circuit for implementing transmission of data, signaling, and the like between the VNFM or the PaaS management entity and other network elements.
- the processor 1101 can invoke the program code to perform the operations in the method embodiments described in Figures 2-7.
- the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
- software it may be implemented in whole or in part in the form of a computer program product.
- the computer program product includes one or more computer instructions.
- the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in or transmitted by a computer readable storage medium.
- the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
- the computer readable storage medium can be any available media that can be accessed by a computer.
- the computer instructions can be stored or transmitted using a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)).
- SSD Solid State Disk
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
An instantiation method for a virtual network function (VNF): by means of the collaborative management of management and orchestration (MANO) and a platform as a service (PaaS) management entity, organically bindingly linking or decoupling and separating the lifecycle management of a VNF public service and proprietary service that are deployed on a PaaS platform to or from the VNF life cycle management that calls the services so as to effectively satisfy the requirements for the differentiated life cycle management and resource management of each component part (public service and proprietary service) of a VNF having cloud native characteristics, increasing the usage of virtual resources of a Network Function Virtualization Infrastructure (NFVI) layer and the flexibility of VNF entity deployment.
Description
本申请要求于2017年9月5日提交中国专利局、申请号为201710792188.1、发明名称为“虚拟网络功能的实例化方法”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。This application claims the priority of the Chinese Patent Application, filed on Sep. 5, 2017, the application Serial No. .
本申请涉及通信领域,尤其涉及一种虚拟网络功能的实例化方法、相关设备及系统。The present application relates to the field of communications, and in particular, to an instantiation method, related device, and system for a virtual network function.
传统的电信系统通过各种专用的硬件设备组成,不同的应用采用不同的硬件设备。随着网络规模的增长,系统越来越复杂,带来了诸多的挑战,包括新增业务的开发上线、系统的运维、资源利用率等。为了应对这些挑战及利用IT业界的虚拟化技术及云计算技术,在2012年10月22日召开的“SDN and OpenFlow World Congress”会议上,全球主要的13个电信运营商联合发布了NFV白皮书,并宣布在ETSI成立NFV ISG,制定NFV的需求及技术框架,推动NFV的发展。The traditional telecommunication system is composed of various dedicated hardware devices, and different applications use different hardware devices. As the scale of the network grows, the system becomes more and more complex, which brings many challenges, including the development of new services, the operation and maintenance of the system, and resource utilization. In response to these challenges and the use of virtualization technology and cloud computing technology in the IT industry, at the "SDN and OpenFlow World Congress" conference held on October 22, 2012, the world's 13 major telecom operators jointly released the NFV white paper. It also announced the establishment of NFV ISG at ETSI to develop NFV requirements and technical framework to promote the development of NFV.
网络功能虚拟化(Network Function Virtualization,NFV)技术可以简单地理解为将电信网络中使用的各个网元的功能从目前的专用硬件平台迁移至通用的商用货架产品(COTS,Commercial-off-the-shelf)服务器上。通过NFV技术将电信网络中使用的各个网元转变成为独立的应用,可以灵活部署在基于标准的服务器、存储以及交换机等其他设备构建的统一基础设施平台上,并通过虚拟化技术,对基础设施硬件设备资源池化及虚拟化,对上层应用提供虚拟资源,实现应用、硬件解耦,使得每一个应用能够快速增加虚拟资源以实现快速扩展系统容量的目的,或者能够快速减少虚拟资源以实现收缩系统容量的目的,大大提升网络的弹性。采用通用的COTS服务器组成共享的资源池,新开发的业务,不需要单独部署硬件设备,大大缩短新业务上线时间。Network Function Virtualization (NFV) technology can be simply understood as the migration of the functions of the various network elements used in the telecommunications network from the current dedicated hardware platform to the common commercial shelf products (COTS, Commercial-off-the- Shelf) on the server. Through NFV technology, each network element used in the telecommunication network can be transformed into a stand-alone application, which can be flexibly deployed on a unified infrastructure platform built by standards-based servers, storage, and switches, and through virtualization technology to the infrastructure. Hardware device resource pooling and virtualization, providing virtual resources to upper-layer applications, enabling application and hardware decoupling, enabling each application to rapidly increase virtual resources to achieve rapid expansion of system capacity, or to rapidly reduce virtual resources to achieve shrinkage The purpose of system capacity greatly enhances the flexibility of the network. The common COTS server is used to form a shared resource pool. The newly developed services do not need to be separately deployed with hardware devices, which greatly shortens the time for new services to go online.
平台即服务(PaaS,Platform as a Service)是将服务器平台作为一种服务的商业模式。通过网络进行软件程序提供的服务称为软件即服务(SaaS,Software as a Service),而云计算时代相应的云计算平台或者开发环境作为服务提供就成为PaaS。在云计算的典型层级中,PaaS层介于SaaS与基础设施即服务(IaaS,Infrastructure as a Service)之间。Platform as a Service (PaaS, Platform as a Service) is a business model that uses the server platform as a service. The service provided by the software program through the network is called Software as a Service (SaaS), and the corresponding cloud computing platform or development environment in the cloud computing era becomes PaaS as a service provider. In a typical level of cloud computing, the PaaS layer is between SaaS and Infrastructure as a Service (IaaS).
典型的PaaS平台应提供如下功能:1)应用运行环境:包括分布式计算运行环境、多种类型的数据存储、动态资源伸缩功能;应用全生命周期支持:包括提供开发SDK、IDE等加快应用的开发、测试和部署。2)公共服务:以API形式提供公共服务,如队列服务、存储服务和缓存服务等,监控、管理和计量:提供资源池、应用系统的管理和监控功能,精确计量;3)集成、复合应用构建能力:包括连通性服务、整合服务、消息服务和流程服务等。A typical PaaS platform should provide the following functions: 1) Application runtime environment: including distributed computing runtime environment, multiple types of data storage, dynamic resource scaling; application lifecycle support: including development of SDK, IDE, etc. Develop, test, and deploy. 2) Public service: Provide public services in the form of API, such as queue service, storage service and cache service, monitor, manage and measure: provide resource pool, application system management and monitoring functions, accurate measurement; 3) integration, composite application Building capabilities: including connectivity services, integration services, messaging services, and process services.
随着NFV技术的不断发展,原有的构建在NFVI层虚拟机(VM)基础上的VNF的呈现形态融入了新的特性,支持云原生(Cloud-native)的VNF和融合PaaS平台服务的云化架构将成为电信云发展的新趋势。在IT领域,云原生是一种方法,用于构建和运行充分利用云计算模型优势的应用。企业需要一个用于构建和运行云原生应用和服务的平台,来自动执行并集成DevOps、持续交付、微服务和容器等概念。由于云原生和PaaS等云化架构概念来自IT应用领域,这 些概念如何通过在电信NFV领域适配后进行应用,目前仍然没有解决方案。With the continuous development of NFV technology, the original VNF representation based on the NFVI layer virtual machine (VM) incorporates new features, supporting cloud-native VNF and cloud converged PaaS platform services. The architecture will become a new trend in the development of telecommunications clouds. In the IT world, Cloud Native is a way to build and run applications that take full advantage of the cloud computing model. Enterprises need a platform for building and running cloud-native applications and services to automate and integrate concepts such as DevOps, continuous delivery, microservices, and containers. Since cloud-based architecture concepts such as cloud native and PaaS come from IT applications, there are still no solutions to how these concepts can be applied after adaptation in the telecom NFV domain.
在现有的NFV技术中,组成VNF实例的各VNF组件(VNFC)的生命周期管理与VNF实例的生命周期管理紧密耦合,不可分割。例如:如果将虚拟化的网元MME(Mobility Management Function)定义为一个VNF,那么包含在该VNF内的功能如:移动性管理、会话管理和QoS管理可以分解为不同的VNFC。在VNF实例的生命周期内,每个VNFC实例独占一个VM的虚拟资源,并伴随着VNF实例的终结而释放所占用的VM资源。这种管理方式带来的好处是确保了VNFC之间的资源隔离性,有利于面向电信级VNF提供高可靠性的服务保障。但另一方面,由于每个VM被一个VNFC所独占,VM资源的利用率不高,很难保证大规模的VNF功能部署。In the existing NFV technology, the lifecycle management of each VNF component (VNFC) constituting the VNF instance is closely coupled with the lifecycle management of the VNF instance, and is inseparable. For example, if a virtualized network element MME (Mobility Management Function) is defined as a VNF, functions included in the VNF such as mobility management, session management, and QoS management can be decomposed into different VNFCs. During the life cycle of the VNF instance, each VNFC instance monopolizes the virtual resources of one VM and releases the occupied VM resources along with the termination of the VNF instance. The advantage of this management method is to ensure the resource isolation between VNFCs and to provide high-reliability service guarantee for carrier-grade VNF. On the other hand, since each VM is monopolized by one VNFC, the utilization of VM resources is not high, and it is difficult to ensure large-scale deployment of VNF functions.
当云原生的设计原则引入到VNF实现时,VNF的功能将被进一步进行服务化解构甚至微服务化。如果对于VNFC仍然采用与VNF实例紧密耦合的生命周期管理方式,数量众多的VNFC实例会消耗大量的VM资源(或者是更细颗粒度的容器资源),导致NFVI层的虚拟资源利用率低下,从而影响VNF实例的运行效率。When the original design principles of the cloud are introduced into the VNF implementation, the functions of the VNF will be further deconstructed and even micro-served. If VNFC still adopts a lifecycle management method closely coupled with the VNF instance, a large number of VNFC instances consume a large amount of VM resources (or a finer granular container resource), resulting in low utilization of virtual resources of the NFVI layer, thereby Affect the operational efficiency of VNF instances.
发明内容Summary of the invention
本申请实施例提供一种虚拟网络功能的实例化(instantiation)方法、相关设备及系统,通过NFV的MANO和PaaS管理实体的交互,实现某些类型(例如公共服务)的PaaS服务的生命周期管理(实例化、弹性伸缩、终结)与调用它的VNF生命周期管理相互分离(解耦)。An embodiment of the present application provides an instantiation method, a related device, and a system for a virtual network function, and implements lifecycle management of PaaS services of certain types (for example, public services) through interaction between MANO and PaaS management entities of NFV. (instantiation, elastic scaling, termination) is separated (decoupled) from the VNF lifecycle management that invokes it.
第一方面,本申请实施例提供了一种虚拟网络功能VNF的实例化方法,包括:虚拟网络功能管理器VNFM接收VNF实例化请求,所述VNF实例化请求中携带需要实例化的VNF的标识;所述VNFM根据PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS服务,并确定所述VNF实例需要调用的所述PaaS服务的容量;所述VNFM向PaaS管理实体发送所述PaaS服务的配置请求,所述配置请求中携带所述需要调用的PaaS服务标识,容量以及租户的标识,所述租户对应调用所述PaaS服务的VNF;所述VNFM根据所述PaaS管理实体分配给所述VNF的所述指定容量的PaaS服务实例,完成所述VNF的实例化。In a first aspect, an embodiment of the present application provides a method for instantiating a virtual network function VNF, including: a virtual network function manager VNFM receiving a VNF instantiation request, where the VNF instantiation request carries an identifier of a VNF that needs to be instantiated Determining, by the VNFM, a PaaS service that the VNF instance needs to invoke according to a mapping relationship between the PaaS service and the VNF, and determining a capacity of the PaaS service that the VNF instance needs to invoke; the VNFM sending the to the PaaS management entity a configuration request of the PaaS service, the configuration request carrying the PaaS service identifier, the capacity and the identifier of the tenant to be called, the tenant corresponding to the VNF of the PaaS service; the VNFM is allocated according to the PaaS management entity The PaaS service instance of the specified capacity of the VNF completes instantiation of the VNF.
可选的,所述VNF实例需要调用的PaaS服务为公共服务。Optionally, the VNF instance needs to invoke the PaaS service as a public service.
由于PaaS上的公共服务的生命周期管理与NFV实例的生命周期管理是解耦的,本申请实施例的方案提高了NFVI虚拟资源的利用率和VNF实例的运行效率。The solution of the embodiment of the present application improves the utilization of the NFVI virtual resource and the operating efficiency of the VNF instance, because the lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance.
可选的,所述VNF实例需要调用的PaaS服务还包括专有服务,则所述方法进一步包括,所述VNFM向PaaS管理实体发送实例化所述专有服务的请求,所述请求中携带需要实例化的专有服务标识和实例化操作参数;所述VNFM根据在PaaS平台上实例化的所述专有服务实例和配置的所述公共服务实例,完成所述VNF的实例化。本发明实施例通过进一步包含了VNF实例化过程中对PaaS平台的公共服务和专有服务协同调用,从而更进一步的提高了VNF实例部署的灵活性和虚拟资源管理的整体效率。Optionally, the PaaS service that the VNF instance needs to invoke further includes a proprietary service, and the method further includes: the VNFM sending, to the PaaS management entity, a request for instantiating the proprietary service, where the request carries the requirement The instantiated proprietary service identifies and instantiates operational parameters; the VNFM completes instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance. The embodiment of the present invention further includes the cooperative call of the public service and the proprietary service to the PaaS platform during the VNF instantiation process, thereby further improving the flexibility of the VNF instance deployment and the overall efficiency of the virtual resource management.
可选的,所述方法还进一步包括:所述VNFM接收VNF实例弹性伸缩请求,所述弹性伸缩请求中携带VNF实例标识和弹性伸缩操作参数;所述VNFM根据PaaS服务和VNF的映射关系,确定所述VNF实例调用的专有服务;所述VNFM向所述PaaS管理实体发送弹性伸缩请求,所述弹性伸缩请求中携带所述调用的专有服务标识和所述弹性伸缩操作参数;所述VNFM接收所述PaaS管理实体返回的所述弹性伸缩的执行结果。Optionally, the method further includes: the VNFM receives the VNF instance elastic scaling request, where the elastic scaling request carries the VNF instance identifier and the elastic scaling operation parameter; and the VNFM determines according to the mapping relationship between the PaaS service and the VNF. The VNFM sends an elastic scaling request to the PaaS management entity, where the elastic scaling request carries the called private service identifier and the elastic scaling operation parameter; the VNFM Receiving an execution result of the elastic scaling returned by the PaaS management entity.
可选的,所述VNFM接收VNF实例终结请求,所述VNF实例终结请求中携带需要终结的 VNF实例标识;所述VNFM根据PaaS服务和VNF的映射关系,确定所述需要终结的VNF实例调用的公共服务;所述VNFM向所述PaaS管理实体发起公共服务配置请求,所述配置请求中携带需要终结的公共服务标识和调用该公共服务的VNF对应的租户标识;所述VNFM接收所述PaaS管理实体返回的公共服务配置的应答消息;所述VNFM根据所述公共服务配置应答消息完成VNF实例的终结过程。Optionally, the VNFM receives a VNF instance termination request, where the VNF instance termination request carries a VNF instance identifier that needs to be terminated; and the VNFM determines, according to a mapping relationship between the PaaS service and the VNF, the VNF instance that needs to be terminated. a public service; the VNFM sends a public service configuration request to the PaaS management entity, where the configuration request carries a public service identifier that needs to be terminated and a tenant identifier corresponding to a VNF that invokes the public service; and the VNFM receives the PaaS management The response message of the public service configuration returned by the entity; the VNFM completes the termination process of the VNF instance according to the public service configuration response message.
可选的,所述VNFM根据PaaS服务和VNF的映射关系,确定所述需要终结的VNF实例调用的PaaS服务还包括专有服务,则所述方法进一步包括:所述VNFM向所述PaaS管理实体发起专有服务终结请求,所述终结请求中携带需要终结的专有服务实例的标识。所述VNFM接收所述PaaS管理实体返回的所述专有服务实例终结的应答消息;所述VNFM根据所述专有服务实例终结的应答消息和所述公共服务配置应答消息完成VNF实例的终结过程。Optionally, the VNFM determines, according to the mapping relationship between the PaaS service and the VNF, that the PaaS service invoked by the VNF instance that needs to be terminated further includes a proprietary service, where the method further includes: the VNFM managing the entity to the PaaS Initiating a proprietary service termination request, the termination request carrying an identifier of a proprietary service instance that needs to be terminated. Receiving, by the VNFM, the response message of the proprietary service instance termination returned by the PaaS management entity; the VNFM completing the finalization process of the VNF instance according to the response message terminated by the proprietary service instance and the public service configuration response message .
可选的,所述PaaS服务和VNF的映射关系存储在所述VNF的描述符文件VNFD中,所述VNFM从所述VNFD中获取所述映射关系。Optionally, the mapping relationship between the PaaS service and the VNF is stored in a descriptor file VNFD of the VNF, and the VNFM obtains the mapping relationship from the VNFD.
可选的,所述VNFM从所述VNF的VNFD文件中获得所述VNF在实例化时需要使用的PaaS服务的容量,所述容量包括所述PaaS服务的实例数。Optionally, the VNFM obtains, from the VNFD file of the VNF, a capacity of a PaaS service that the VNF needs to use when instantiating, where the capacity includes an instance number of the PaaS service.
另一方面,本发明实施例提供了一种虚拟网络功能VNF的实例化方法,包括:PaaS管理实体接收VNFM发送的PaaS服务配置请求,所述配置请求中携带需要调用的PaaS服务名称,PaaS服务的容量以及调用所述PaaS服务的VNF对应的租户标识;所述PaaS管理实体根据所述配置请求,将指定容量的所述PaaS服务分配给所述租户;所述PaaS管理实体向所述VNFM返回所述PaaS服务配置的执行结果。On the other hand, an embodiment of the present invention provides an instantiation method for a virtual network function VNF, including: a PaaS management entity receives a PaaS service configuration request sent by a VNFM, where the configuration request carries a PaaS service name that needs to be invoked, and a PaaS service And a tenant identifier corresponding to the VNF that invokes the PaaS service; the PaaS management entity assigns the PaaS service of the specified capacity to the tenant according to the configuration request; the PaaS management entity returns to the VNFM The execution result of the PaaS service configuration.
可选的,所述配置请求中携带需要调用的PaaS服务为公共服务。Optionally, the configuration request carries a PaaS service that needs to be invoked as a public service.
可选的,所述方法进一步包括,所述PaaS管理实体接收所述VNFM发送的实例化专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数;所述PaaS管理实体接收所述实例化请求,根据所述请求中的实例化操作参数实例化所述专有服务;所述PaaS管理实体向所述VNFM返回所述专有服务实例化的执行结果。Optionally, the method further includes: the PaaS management entity receives a request for instantiating a proprietary service sent by the VNFM, where the request carries a proprietary service name and an instantiated operation parameter that need to be instantiated; The PaaS management entity receives the instantiation request, instantiating the proprietary service according to an instantiated operational parameter in the request; the PaaS management entity returns an execution result of the proprietary service instantiation to the VNFM.
可选的,所述方法还进一步包括:所述PaaS管理实体接收所述VNFM发送的弹性伸缩请求,所述弹性伸缩请求中携带所述调用的PaaS专有服务标识和弹性伸缩操作参数;所述PaaS管理实体根据所述弹性伸缩请求,执行所述PaaS专有服务的弹性伸缩并向所述VNFM返回所述弹性伸缩的执行结果。Optionally, the method further includes: the PaaS management entity receiving the elastic scalability request sent by the VNFM, where the elastic scalability request carries the PaaS-specific service identifier and the elastic scaling operation parameter of the call; The PaaS management entity performs elastic scaling of the PaaS proprietary service according to the elastic scaling request and returns an execution result of the elastic scaling to the VNFM.
可选的,所述PaaS服务的容量包括所述PaaS服务的实例数。Optionally, the capacity of the PaaS service includes the number of instances of the PaaS service.
再一方面,本发明实施例还提供了一种虚拟网络功能管理器VNFM,包括:处理模块,发送模块,和实例化模块;所述处理模块,用于根据VNF实例化请求中携带的需要实例化的VNF的标识,以及PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS服务,还进一步用于确定所述VNF实例需要调用的所述PaaS服务的容量;所述发送模块,用于向PaaS管理实体发送所述PaaS服务的配置请求,所述配置请求中携带所述需要调用的PaaS服务标识,容量以及租户的标识,所述租户对应调用所述PaaS服务的VNF;所述实例化模块,用于根据所述PaaS管理实体分配给所述VNF的所述指定容量的PaaS服务实例,完成所述VNF的实例化。In a further aspect, the embodiment of the present invention further provides a virtual network function manager VNFM, including: a processing module, a sending module, and an instantiation module; the processing module is configured to perform an instance according to a VNF instantiation request The identifier of the VNF, and the mapping relationship between the PaaS service and the VNF, determining the PaaS service that the VNF instance needs to invoke, and further determining the capacity of the PaaS service that the VNF instance needs to invoke; the sending module, a configuration request for sending the PaaS service to the PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity and the identifier of the tenant, and the tenant corresponds to the VNF that invokes the PaaS service; And an instantiation module, configured to complete instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
可选的,所述VNF实例需要调用的PaaS服务为公共服务。Optionally, the VNF instance needs to invoke the PaaS service as a public service.
可选的,所述VNF实例需要调用的PaaS服务还包括专有服务,所述发送模块进一步用于 向PaaS管理实体发送实例化所述专有服务的请求,所述请求中携带需要实例化的专有服务标识和实例化操作参数;所述实例化模块进一步用于根据在PaaS平台上实例化的所述专有服务实例和配置的所述公共服务实例,完成所述VNF的实例化。Optionally, the PaaS service that the VNF instance needs to invoke further includes a proprietary service, where the sending module is further configured to send, to the PaaS management entity, a request to instantiate the proprietary service, where the request carries an instantiation that needs to be instantiated. The proprietary service identifies and instantiates the operational parameters; the instantiation module is further for completing the instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
再一方面,本发明实施还提供了一种PaaS管理实体,包括服务模块和响应模块,所述服务模块,用于接收VNFM发送的PaaS服务配置请求,所述配置请求中携带需要调用的PaaS服务名称,PaaS服务的容量以及调用所述PaaS服务的VNF对应的租户标识;并根据所述配置请求,将指定容量的所述PaaS服务分配给所述租户;所述响应模块,用于向所述VNFM返回所述PaaS服务配置的执行结果。In another aspect, the implementation of the present invention further provides a PaaS management entity, including a service module and a response module, where the service module is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service that needs to be invoked. a name, a capacity of the PaaS service, and a tenant identifier corresponding to the VNF that invokes the PaaS service; and assigning the PaaS service of the specified capacity to the tenant according to the configuration request; the response module is configured to The VNFM returns the execution result of the PaaS service configuration.
可选的,所述配置请求中携带需要调用的PaaS服务为公共服务。Optionally, the configuration request carries a PaaS service that needs to be invoked as a public service.
可选的,则所述服务模块还进一步用于接收所述VNFM发送的实例化专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数;所述服务模块接收所述实例化请求,根据所述请求中的实例化操作参数实例化所述专有服务;所述响应模块还进一步用于向所述VNFM返回所述专有服务实例化的执行结果。Optionally, the service module is further configured to receive a request for instantiating a proprietary service sent by the VNFM, where the request carries a specific service name and an instantiated operation parameter that need to be instantiated; the service module Receiving the instantiation request, instantiating the proprietary service according to the instantiated operation parameter in the request; the response module is further configured to return an execution result of the proprietary service instantiation to the VNFM.
再一方面,本发明实施还提供了一种NFV网络系统,包含前述中任一方面中的VNFM和前述中任一方面中PaaS管理实体。In a further aspect, the present invention provides an NFV network system, comprising the VNFM of any of the preceding aspects and the PaaS management entity of any of the foregoing.
再一方面,本发明实施还提供了一种虚拟网络功能VNF的实例化方法,包括:虚拟网络功能管理器VNFM接收VNF实例化请求,所述VNF实例化请求中携带需要实例化的VNF的标识;所述VNFM根据PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS专有服务;所述VNFM向PaaS管理实体发送实例化所述专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数,所述参数包括所述专有服务的容量;所述VNFM根据在PaaS平台上实例化的所述专有服务实例,完成所述VNF的实例化。In another aspect, the implementation of the present invention further provides an instantiation method of a virtual network function VNF, including: the virtual network function manager VNFM receives a VNF instantiation request, and the VNF instantiation request carries an identifier of the VNF that needs to be instantiated. Determining, by the VNFM, a PaaS-specific service that the VNF instance needs to invoke according to a mapping relationship between the PaaS service and the VNF; the VNFM sending a request to the PaaS management entity to instantiate the proprietary service, where the request carries Instantiating a proprietary service name and instantiating operational parameters, the parameters including capacity of the proprietary service; the VNFM completing instantiation of the VNF based on the proprietary service instance instantiated on a PaaS platform .
再一方面,本发明实施还提供了一种计算机可读存储介质,包括程序指令,当其在计算机上运行时,使得计算机执行如前述任一方面所述的NFV实例化方法。In a further aspect, the present invention provides a computer readable storage medium comprising program instructions, when executed on a computer, causing the computer to perform the NFV instantiation method as described in any of the preceding aspects.
本申请还提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行前述各方面所述的方法。The present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the preceding aspects.
为了更清楚地说明本申请实施例或背景技术中的技术方案,下面将对本申请实施例或背景技术中所需要使用的附图进行说明。In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings to be used in the embodiments of the present application or the background art will be described below.
图1是本申请实施例提供的一种基于NFV MANO的网络架构示意图;1 is a schematic diagram of a network architecture based on NFV MANO provided by an embodiment of the present application;
图2是本申请实施例提供的一种PaaS与MANO对接的备选架构示意图;2 is a schematic diagram of an alternative architecture for interfacing a PaaS and a MANO according to an embodiment of the present application;
图3是本申请实施例提供的一种VNF的实例化方法流程示意图;3 is a schematic flowchart of a method for instantiating a VNF according to an embodiment of the present application;
图4是本申请实施例提供的一种VNF实例终结过程示意图;4 is a schematic diagram of a VNF instance termination process provided by an embodiment of the present application;
图5是本申请实施例提供的一种专有服务实例弹性伸缩过程示意图;FIG. 5 is a schematic diagram of an elastic scaling process of a proprietary service instance according to an embodiment of the present application; FIG.
图6是本申请实施例提供的一种公共服务实例弹性伸缩过程示意图;FIG. 6 is a schematic diagram of an elastic scaling process of a public service instance according to an embodiment of the present application; FIG.
图7是本申请实施例提供的一种通用的PaaS服务弹性伸缩过程示意图;7 is a schematic diagram of a general PaaS service elastic scaling process provided by an embodiment of the present application;
图8是本申请实施例提供的一种VNFM的装置结构示意图;FIG. 8 is a schematic structural diagram of a device of a VNFM according to an embodiment of the present disclosure;
图9是本申请实施例提供的一种PaaS管理实体装置结构示意图;9 is a schematic structural diagram of a PaaS management entity device according to an embodiment of the present application;
图10是本申请实施例提供的一种NFV网络系统示意图;FIG. 10 is a schematic diagram of an NFV network system according to an embodiment of the present application;
图11是本申请实施例提供的一种VNFM或者PaaS管理实体的结构示意图。FIG. 11 is a schematic structural diagram of a VNFM or PaaS management entity according to an embodiment of the present application.
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。其中,在本申请的描述中,除非另有说明,“/”表示或的意思,例如,A/B可以表示A或B;本文中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,在本申请的描述中,“多个”是指两个或多于两个。The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, unless otherwise stated, "/" means the meaning of or, for example, A/B may represent A or B; "and/or" herein is merely an association describing the associated object. The relationship indicates that there may be three kinds of relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. In addition, in the description of the present application, "a plurality" means two or more than two.
请参阅图1,图1为基于NFV的网络架构示意图,主要包括:运营支撑系统(Operation Support System,OSS)/业务支撑系统(Business Support System,BSS)、网元管理(Element Manager,EM)单元、虚拟化网络功能(VNF)单元、网络功能虚拟化基础设施(NFV Infrastructure,NFVI)单元、公共服务(Common Service,CS)单元以及网络功能虚拟化管理和编排(NFV MANO)系统。其中,网络功能虚拟化管理和编排(NFV Management and Orchestration,NFV MANO)系统包括网络功能虚拟化编排(NFV Orchestrator,NFVO)单元、虚拟化网络功能管理(VNF Manager,VNFM)单元和虚拟化基础设施管理(Virtualised Infrastructure Manager,VIM)单元。Please refer to FIG. 1. FIG. 1 is a schematic diagram of an NFV-based network architecture, which mainly includes: an operation support system (OSS), a business support system (BSS), and an element management (EM) unit. , Virtual Network Function (VNF) unit, Network Function Virtualization Infrastructure (NFVI) unit, Common Service (CS) unit, and Network Function Virtualization Management and Orchestration (NFV MANO) system. Among them, the NFV Management and Orchestration (NFV MANO) system includes the NFV Orchestrator (NFVO) unit, the Virtualized Network Function Management (VNF Manager, VNFM) unit, and the virtualization infrastructure. Management (Virtualised Infrastructure Manager, VIM) unit.
需要说明的是,在下文中,可以各用单元的英文缩写来描述对应单元,例如网元管理单元可以描述为EM或EM单元。下面对上述单元做简单介绍:It should be noted that, in the following, the corresponding unit may be described by the abbreviation of each unit, for example, the network element management unit may be described as an EM or EM unit. The following is a brief introduction to the above units:
OSS/BSS是电信运营商的一体化、信息资源共享的支持系统,其主要由网络管理、系统管理、计费、营业、账务和客户业务等部分组成,而系统间则通过统一的信息总线有机整合在一起。OSS/BSS能在帮助运营商制订符合自身特点的运营支撑系统的同时帮助确定系统的发展方向,还能帮助用户制订系统的整合标准,改善和提高用户的业务水平。OSS/BSS在基于NFV的网络架构中用于对各个网元的生命周期管理(例如实例化等)进行必要的修改和调整。OSS/BSS is a support system for the integration and information resource sharing of telecom operators. It is mainly composed of network management, system management, billing, business, accounting and customer services, while the system passes through a unified information bus. Organically integrated. OSS/BSS can help operators determine the development direction of the system while helping them to develop their own operational support systems. It can also help users to formulate system integration standards and improve and improve users' business levels. The OSS/BSS is used in the NFV-based network architecture to make necessary modifications and adjustments to the lifecycle management (eg, instantiation, etc.) of each network element.
NFV编排器(NFVO,NFV Orchestrator):NFVO实现网络服务描述符(NSD,NS Descriptor),虚拟网络功能转发图(VNFFG,VNF Forwarding Graph)的管理及处理,网络服务生命周期的管理,和VNFM配合实现VNF的生命周期管理和虚拟资源的全局视图功能。NFV orchestrator (NFVO, NFV Orchestrator): NFVO implements network service descriptor (NSD, NS Descriptor), virtual network function forwarding map (VNFFG, VNF Forwarding Graph) management and processing, network service life cycle management, and VNFM cooperation Realize VNF lifecycle management and global view of virtual resources.
VNF管理器(VNFM,VNF Manager):VNFM实现虚拟化网络功能VNF的生命周期管理,包括虚拟化网络功能描述符(VNFD,VNF Descriptor)的管理、VNF的实例化、VNF实例的弹性伸缩(包括扩容Scaling out/up和缩容Scaling in/down)、VNF实例的治愈(healing)以及VNF实例的终止。VNFM还支持接收NFVO下发的弹性伸缩(scaling)策略,实现自动化的VNF弹性伸缩。VNFM (VNFM): VNFM implements lifecycle management of virtualized network functions VNF, including management of virtualized network function descriptors (VNFD, VNF Descriptor), instantiation of VNFs, and elastic scaling of VNF instances (including Scaling out/up and Scaling in/down), healing of VNF instances, and termination of VNF instances. VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.
虚拟基础设施管理器(VIM,Virtualised Infrastructure Manager):主要负责基础设施层硬件资源,虚拟化资源的管理(包括预留和分配),虚拟资源状态的监控和故障上报,面向上层应用提供虚拟化资源池。Virtual Infrastructure Manager (VIM): Responsible for infrastructure layer hardware resources, virtualized resource management (including reservation and allocation), virtual resource status monitoring and fault reporting, and virtualized resources for upper-layer applications Pool.
运营和商务支撑系统(OSS/BSS,Operations and Business Support Systems):指运营商现有的运行维护系统OSS/BSS。OSS/BSS (Operations and Business Support Systems): refers to the operator's existing operation and maintenance system OSS/BSS.
网元管理系统(EM,Element Manager):针对VNF执行传统的故障、配置、用户、性能和安全管理(简称FCAPS,Fault Management,Configuration Management,Account Management,Performance Management,Security Management)功能。Element Management System (EM): Performs traditional fault, configuration, user, performance, and security management (FCAPS, Fault Management, Configuration Management, Account Management, Performance Management, Security Management) functions for the VNF.
虚拟化网络功能(VNF,Virtualized Network Function):对应于传统非虚拟化网络中的物理网络功能(PNF),如虚拟化的EPC节点(MME,SGW,PGW等)。网络功能的功能性行为和状态与虚拟化与否无关,NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。Virtualized Network Function (VNF): Corresponds to physical network functions (PNFs) in traditional non-virtualized networks, such as virtualized EPC nodes (MME, SGW, PGW, etc.). The functional behavior and state of network functions are independent of virtualization. NFV technology requires that VNF and PNF have the same functional behavior and external interfaces.
VNF可以由多个更低级别的VNF组件(VNFC,VNF Component)来组成,因此,一个VNF可以部署在多个虚拟机(VM,Virtual Machine)上,每个VM承载一个VNF组件的功能;VNF也可以部署在一个VM上。VNF can be composed of multiple lower-level VNF components (VNFC, VNF Component). Therefore, a VNF can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component function; VNF It can also be deployed on a VM.
NFV基础架构(NFVI,NFV Infrastructure):NFVI由硬件资源和虚拟资源以及虚拟化层组成。从VNF的角度来说,虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的完整实体。NFV Infrastructure (NFVI Infrastructure): NFVI consists of hardware resources and virtual resources and a virtualization layer. From a VNF perspective, the virtualization layer and hardware resources appear to be a complete entity that provides the required virtual resources.
基于当前的NFV系统架构,本申请提出一种NFV PaaS服务的生命周期管理方法,面向组成VNF的公共服务和专有服务进行差异化的生命周期管理,从而提高NFVI层虚拟资源的利用率和VNF实例部署的灵活性。(注:在ETSI NFV003GS中,生命周期管理指用于管理一个VNF或NS的实例化、维护和终结的一组功能。)Based on the current NFV system architecture, this application proposes a lifecycle management method for NFV PaaS services, which differentiates lifecycle management for public services and proprietary services that make up VNF, thereby improving the utilization of NFVI layer virtual resources and VNF. The flexibility of instance deployment. (Note: In ETSI NFV003GS, lifecycle management refers to a set of functions used to manage the instantiation, maintenance, and termination of a VNF or NS.)
PaaS平台上部署了组成VNF的公共服务、专有服务以及对这些服务进行运维管理的PaaS管理功能(简称PaaS管理实体),如图2所示。PaaS平台在北向接口上为调用PaaS平台服务的VNF或应用提供了应用编程接口(API,Application Programming Interface),而PaaS管理实体将PaaS平台服务的运维管理和MANO系统进行对接,以实现面向云原生特性的VNF实例的统一运维管理。目前,ETSI标准尚未确定标准化的PaaS与MANO的互操作框架,图2所示的架构是一种可行的备选架构,PaaS管理实体功能接入MANO系统的锚点实体是VNFM。PaaS management functions (referred to as PaaS management entities) that constitute VNF's public services, proprietary services, and operation and maintenance management of these services are deployed on the PaaS platform, as shown in Figure 2. The PaaS platform provides an application programming interface (API) for the VNF or application that calls the PaaS platform service on the northbound interface, and the PaaS management entity interfaces the operation and maintenance management of the PaaS platform service with the MANO system to implement the cloud-oriented Unified operation and maintenance management of VNF instances with native features. At present, the ETSI standard has not yet determined the interoperability framework of standardized PaaS and MANO. The architecture shown in Figure 2 is a viable alternative architecture. The anchor entity of the PaaS management entity function accessing the MANO system is VNFM.
具有云原生(Cloud-Native)特性的VNF实例由公共服务(也称为VNF公共服务)和专有服务(也称为VNF专有服务)组成。VNF instances with Cloud-Native features consist of public services (also known as VNF public services) and proprietary services (also known as VNF proprietary services).
公共服务:在功能定义中确定可以被一个或多个应用或服务调用(consume)的模块化服务或功能。创建后的公共服务实例被一个或多个应用或服务实例所调用。Public service: A modular service or function that can be invoked by one or more applications or services in a functional definition. The created public service instance is called by one or more applications or service instances.
专有服务:在功能定义中确定仅能被一个特定集合的应用或服务调用的模块化服务或功能。创建后的专有服务实例仅能被一个应用或服务实例所调用。Proprietary services: Identify, in a functional definition, a modular service or function that can only be invoked by a particular collection of applications or services. A created proprietary service instance can only be called by an application or service instance.
需要说明的是,不论是公共服务还是专有服务,既可以部署在PaaS平台上,也可以部署在PaaS平台之外的应用层,应用层对应VNF应用层的概念可以是VNF平台层,例如:部署在PaaS平台的服务组件。公共服务和专有服务可以看作是服务化的VNF,或者是服务化的VNFC。调用公共服务的应用或服务可以是VNF(电信级的虚拟化网元),也可以是来自其他行业客户的第三方应用。模块化服务或应用可以是原子的(例如:微服务),也可以是由多个原子化功能组合成的功能。It should be noted that whether it is a public service or a proprietary service, it can be deployed on the PaaS platform or on the application layer outside the PaaS platform. The concept of the application layer corresponding to the VNF application layer can be the VNF platform layer, for example: Service components deployed on the PaaS platform. Public and proprietary services can be thought of as serviced VNFs or serviced VNFCs. The application or service that invokes the public service may be a VNF (telecom scale virtualized network element) or a third party application from other industry customers. A modular service or application can be atomic (for example, microservices) or a combination of multiple atomization functions.
在本发明实施例方案中,对于部署在PaaS平台上公共服务和专有服务(在本发明实施例方案中分别简称为PaaS公共服务和PaaS专有服务,或者进一步简称为公共服务和专有服务),采用如下的差异化方法实现组成VNF的PaaS服务实例的生命周期管理:In the solution of the embodiment of the present invention, the public service and the proprietary service deployed on the PaaS platform (referred to as PaaS public service and PaaS proprietary service, or further referred to as public service and proprietary service, respectively, in the embodiments of the present invention) ), using the following differentiation method to implement lifecycle management of PaaS service instances that make up VNF:
对于PaaS平台上的公共服务实例,其生命周期由PaaS平台自主进行管理,特别地,由PaaS平台的管理面(或者称为PaaS管理实体)进行公共服务的实例化、弹性伸缩(Scale)、治愈(Heal)和终结等操作。公共服务实例的生命周期管理与调用它的VNF实例的生命周期管理完全解耦(即:彼此无关,互不依赖),部署在PaaS平台的公共服务实例在调用它的应 用或服务使用该公共服务之前已经完成实例化所需的虚拟资源分配。For the public service instance on the PaaS platform, its life cycle is managed autonomously by the PaaS platform. In particular, the management surface of the PaaS platform (or PaaS management entity) performs instantiation of public services, scale, and cure. (Heal) and final operations. The lifecycle management of a public service instance is completely decoupled from the lifecycle management of the VNF instance that invokes it (ie, independent of each other, independent of each other), and the public service instance deployed on the PaaS platform uses the public service in the application or service that invokes it. The virtual resource allocation required for instantiation has been completed before.
对于PaaS平台上的专有服务实例,其生命周期与调用它的VNF实例的生命周期进行绑定,专有服务实例伴随着调用它的VNF实例的实例化过程而创建,伴随着调用它的VNF实例的终结而终结。这样,专有服务实例的生命周期管理与调用它的VNF实例的生命周期管理完全耦合,专有服务实例的生命周期管理由PaaS平台来执行,但依赖于来自MANO的VNF实例生命周期管理事件的触发。For a proprietary service instance on the PaaS platform, its lifecycle is bound to the lifecycle of the VNF instance that invoked it, and the proprietary service instance is created with the instantiation of the VNF instance that invoked it, along with the VNF that called it. The end of the instance ends. In this way, the lifecycle management of a proprietary service instance is fully coupled with the lifecycle management of the VNF instance that invokes it. The lifecycle management of the proprietary service instance is performed by the PaaS platform, but relies on VNF instance lifecycle management events from MANO. trigger.
下面首先以一个VNF实例化的过程需要调用到PaaS平台提供的服务为例,来说明如何实现PaaS服务生命周期管理与调用它的VNF生命周期管理相互分离(解耦)的。The following first takes a VNF instantiation process to call the service provided by the PaaS platform as an example to illustrate how to realize the separation (decoupling) between the PaaS service lifecycle management and the VNF lifecycle management that calls it.
基于附图1和2的网络架构,本申请实施例提供一种VNF的实例化方法流程示意图,如附图3所示,NFVM与PaaS管理实体交互完成VNF的实例化,是NFV PaaS服务的生命周期管理方法的一个典型场景,该方法包括但不限于如下步骤:Based on the network architecture of FIG. 1 and FIG. 2, the embodiment of the present application provides a schematic diagram of a VNF instantiation method. As shown in FIG. 3, the NFVM interacts with the PaaS management entity to complete the instantiation of the VNF, which is the life of the NFV PaaS service. A typical scenario of the cycle management method, including but not limited to the following steps:
S301:MANO(VNFM)接收来自发送者Sender(可以是NFVO或EM)的VNF实例化请求,该实例化请求消息中携带要实例化的VNF标识。S301: The MANO (VNFM) receives a VNF instantiation request from the sender Sender (which may be NFVO or EM), and the instantiation request message carries the VNF identifier to be instantiated.
S302:VNFM根据PaaS服务和VNF的映射关系,确定该实例化的VNF需要调用的专有服务和/或公共服务;实例化VNF可以仅调用专有服务或仅调用公共服务;S302: The VNFM determines, according to the mapping relationship between the PaaS service and the VNF, the proprietary service and/or the public service that the instantiated VNF needs to invoke; the instantiated VNF may only invoke the proprietary service or only the public service;
不论是公共服务还是专有服务,当该服务在PaaS平台上注册后,需要通知MANO(例如:VNFM)该服务的注册事件,以使得MANO获取该服务和所支持的调用它的应用/服务的类型的映射关系。具体的:MANO实体(例如:VNFM)向PaaS管理实体订阅PaaS服务注册事件。可选的,MANO可以向与其连接的所有PaaS管理实体订阅对应的PaaS平台上的服务注册事件。在订阅请求消息中指出订阅事件的条件,包括所注册服务的名称和该服务支持的租户类型,然后PaaS管理实体根据自身的服务注册需求或计划注册PaaS服务(公共服务或专有服务),最后,PaaS管理实体向MANO发送PaaS服务注册通知,通知消息中携带以下至少一项:注册的服务名称、该服务支持的(即:可服务的)租户类型(对应VNF)、服务信息。其中,租户对应调用该注册服务的应用或服务,也可以表示为VNF。服务信息是指该服务相关的一些说明信息,例如:服务调用的约束或依赖信息,等等。Whether it is a public service or a proprietary service, when the service is registered on the PaaS platform, it is necessary to notify MANO (for example: VNFM) of the registration event of the service, so that MANO obtains the service and the supported applications/services that call it. The mapping relationship of types. Specifically: the MANO entity (for example: VNFM) subscribes to the PaaS service registration event to the PaaS management entity. Optionally, the MANO can subscribe to the service registration event on the corresponding PaaS platform to all PaaS management entities connected thereto. Indicate the conditions of the subscription event in the subscription request message, including the name of the registered service and the type of tenant supported by the service, and then the PaaS management entity registers the PaaS service (public service or proprietary service) according to its own service registration requirement or plan, and finally The PaaS management entity sends a PaaS service registration notice to the MANO, and the notification message carries at least one of the following: a registered service name, a tenant type (corresponding to the VNF) supported by the service (ie, a serviceable), and service information. The tenant corresponding to the application or service that invokes the registration service may also be represented as a VNF. Service information refers to some descriptive information related to the service, such as: constraint or dependency information of the service call, and so on.
一般来说,VNFM还要确定所述VNF实例在实例化时需要调用的所述PaaS服务的容量,或者说需要调用的PaaS服务能力的大小;PaaS服务的容量,可以是需要的服务实例数量,也可以是服务实例数量和每个服务实例容量的乘积;支持某一VNF的PaaS服务容量信息可以是由VNFM从该VNF的VNFD中获取。In general, the VNFM also determines the capacity of the PaaS service that the VNF instance needs to invoke when instantiating, or the size of the PaaS service capability that needs to be invoked; the capacity of the PaaS service, which may be the number of service instances required, It can also be the product of the number of service instances and the capacity of each service instance; the PaaS service capacity information supporting a certain VNF can be obtained by the VNFM from the VNFD of the VNF.
对于PaaS专有服务(S303-S305):For PaaS proprietary services (S303-S305):
S303:VNFM向PaaS管理实体发起专有服务实例化请求操作,该实例化请求消息中携带需要实例化的专有服务的标识、实例化操作参数,如:专有服务实例化后的初始容量要求。S303: The VNFM initiates a proprietary service instantiation request operation to the PaaS management entity, where the instantiation request message carries the identifier of the proprietary service that needs to be instantiated, and instantiates operational parameters, such as an initial capacity requirement after the instantiation of the proprietary service. .
S304:PaaS管理实体接收该实例化请求消息,按照消息中参数的指示执行PaaS专有服务的实例化。S304: The PaaS management entity receives the instantiation request message, and performs instantiation of the PaaS proprietary service according to the indication of the parameter in the message.
S305:PaaS管理实体向VNFM返回PaaS专有服务实例化的应答消息。S305: The PaaS management entity returns a response message instantiated by the PaaS proprietary service to the VNFM.
对于PaaS公共服务(S306-S308):For PaaS Public Service (S306-S308):
S306:VNFM向PaaS管理实体发起公共服务配置请求,该配置请求消息中携带所配置的公共服务名称、配置的公共服务的容量(如实例数)以及调用该公共服务的租户的标识信息, 租户的标识即对应调用所述PaaS服务的VNF。S306: The VNFM initiates a public service configuration request to the PaaS management entity, where the configuration request message carries the configured public service name, the configured public service capacity (such as the number of instances), and the identifier information of the tenant that invokes the public service, and the tenant's The identifier corresponds to the VNF that invokes the PaaS service.
S307:PaaS管理实体接收该配置请求消息,按照消息中参数的指示完成公共服务和租户标识的绑定,并将消息中指定容量(如实例数)的公共服务分配给该租户标识对应的VNF实例。S307: The PaaS management entity receives the configuration request message, completes the binding of the public service and the tenant identity according to the parameter in the message, and allocates the public service of the specified capacity (such as the number of instances) in the message to the VNF instance corresponding to the tenant identifier. .
S308:PaaS管理实体向VNFM返回PaaS公共服务配置的应答消息。S308: The PaaS management entity returns a response message of the PaaS public service configuration to the VNFM.
S309:VNFM根据实例化所创建的PaaS专有服务和/或配置绑定的PaaS公共服务实例完成VNF的实例化过程。S309: The VNFM completes the instantiation process of the VNF according to the PaaS proprietary service and/or the configuration-bound PaaS public service instance created by the instantiation.
需要说明的是,在本实施例过程的示例中,步骤S303-S305对PaaS专有服务的实例化操作和步骤S306-S308对PaaS公共服务的配置操作可以互换顺序,或者并发执行,在此不作限定。It should be noted that, in the example of the process of this embodiment, the instantiation operation of the PaaS proprietary service in steps S303-S305 and the configuration operation of the PaaS public service in steps S306-S308 may be interchanged, or concurrently executed. Not limited.
另外,PaaS管理实体根据对部署在PaaS平台上的公共服务的监控,自主触发执行公共服务的生命周期管理操作,例如:实例化、弹性伸缩、治愈或终结。触发操作执行的条件可以基于运营商预配置于PaaS管理实体的公共服务生命周期管理策略,例如:当平台上某一类型的公共服务的实例数少于一个门限值时,对该类型的公共服务进行auto-scale操作(自动伸缩,例如:完成指定的scale out),也可以通过人机界面方式按需发起公共服务的生命周期管理,例如:确定某类型公共服务下线不再使用,则PaaS管理实体接收人机命令优雅终结该类公共服务的所有实例。MANO实体(例如:VNFM)对PaaS管理实体内部自主触发的公共服务生命周期管理操作无法感知,但可以通过订阅公共服务生命周期管理操作发生通知,来获取与公共服务实例生命周期管理相关的实时性的VNF实例信息,用于调用它的VNF实例生命周期管理的协作运行,在本实施例中,VNFM通过对公共服务实例生命周期管理操作信息的的订阅信息,可以获取到所述公共服务实例的状态,例如PaaS平台上是否有足够的指定名称的公共服务实例可用(available),从而可以为步骤S306中是否向PaaS管理实体发起公共服务配置请求提供决策依据,可以理解的是,如果VNFM了解到PaaS平台上没有所需要的足够可用的公共服务实例,则可以决策不能够或者暂时不能够向PaaS管理实体发起公共服务配置请求。In addition, the PaaS management entity autonomously triggers the execution of public service lifecycle management operations based on monitoring public services deployed on the PaaS platform, such as instantiation, resiliency, healing, or termination. The condition for triggering the execution of the operation may be based on a public service lifecycle management policy pre-configured by the operator in the PaaS management entity, for example, when the number of instances of a certain type of public service on the platform is less than one threshold, the public of the type The service performs auto-scale operations (automatic scaling, for example, to complete the specified scale out), and can also initiate the lifecycle management of the public service on demand through the human-machine interface mode. For example, if it is determined that a certain type of public service is no longer used, The PaaS management entity receives human-machine commands gracefully terminating all instances of this type of public service. The MANO entity (for example, VNFM) is not aware of the public service lifecycle management operations triggered by the PaaS management entity, but can obtain the real-time performance related to the public service instance lifecycle management by subscribing to the public service lifecycle management operation notification. The VNF instance information is used to invoke the cooperative operation of its VNF instance lifecycle management. In this embodiment, the VNFM can obtain the public service instance through the subscription information of the public service instance lifecycle management operation information. The status, for example, whether there is enough public service instance of the specified name available on the PaaS platform, so that a decision basis can be provided for initiating a public service configuration request to the PaaS management entity in step S306. It can be understood that if the VNFM knows There is no sufficient public service instance available on the PaaS platform, and the decision can not or temporarily fail to initiate a public service configuration request to the PaaS management entity.
本发明实施例的方法,通过MANO和PaaS管理实体的交互,实现VNF在实例化过程中对PaaS服务,特别是公共服务实例的调用。由于PaaS上的公共服务的生命周期管理与NFV实例的生命周期管理是解耦的,提高了NFVI虚拟资源的利用率和VNF实例的运行效率;本发明实施例还进一步包含了VNF实例化过程中对PaaS平台的公共服务和专有服务协同调用,从而更进一步的提高了VNF实例部署的灵活性和虚拟资源管理的整体效率。The method of the embodiment of the present invention implements the call of the VNF in the instantiation process to the PaaS service, especially the public service instance, through the interaction between the MANO and the PaaS management entity. The lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance, which improves the utilization of the NFVI virtual resource and the operating efficiency of the VNF instance. The embodiment of the present invention further includes the VNF instantiation process. Co-calling of public and proprietary services for the PaaS platform further enhances the flexibility of VNF instance deployment and the overall efficiency of virtual resource management.
与前述VNF实例化过程的实施例相对应,下面进一步介绍支持云原生特性的VNF实例终结过程,如图4所示:Corresponding to the foregoing embodiment of the VNF instantiation process, the VNF instance termination process supporting the cloud native feature is further described below, as shown in FIG. 4:
S401:VNFM接收来自发送者Sender(可以是NFVO或EM)的VNF实例终结请求,该实例终结请求消息中携带要终结的VNF实例标识。S401: The VNFM receives a VNF instance termination request from the sender Sender (which may be NFVO or EM), where the instance termination request message carries the VNF instance identifier to be terminated.
S402:VNFM根据PaaS服务和服务所支持的租户(对应所述要终结的VNF实例)类型的映射关系,确定该终结的VNF实例调用的专有服务和公共服务。S402: The VNFM determines the proprietary service and the public service invoked by the terminated VNF instance according to the mapping relationship between the type of the tenant (corresponding to the VNF instance to be terminated) supported by the PaaS service and the service.
S403:VNFM向PaaS管理实体发起专有服务终结请求操作,该终结请求消息中携带需要终结的专有服务实例的标识。S403: The VNFM initiates a proprietary service termination request operation to the PaaS management entity, where the finalization request message carries the identifier of the proprietary service instance that needs to be terminated.
S404:PaaS管理实体接收该实例终结请求消息,按照消息中参数的指示执行PaaS专有服务实例的终结。S404: The PaaS management entity receives the instance termination request message, and performs termination of the PaaS proprietary service instance according to the indication of the parameter in the message.
S405:PaaS管理实体向VNFM返回PaaS专有服务实例终结的应答消息。S405: The PaaS management entity returns a response message of the PaaS proprietary service instance termination to the VNFM.
S406:VNFM向PaaS管理实体发起公共服务配置请求,该配置请求消息中携带所配置的公共服务名称和调用该公共服务的租户的标识信息。S406: The VNFM initiates a public service configuration request to the PaaS management entity, where the configuration request message carries the configured public service name and the identifier information of the tenant that invokes the public service.
S407:PaaS管理实体接收该配置请求消息,按照消息中参数的指示完成公共服务和租户标识的去绑定,并将该租户标识所对应分配的公共服务实例释放回PaaS平台。S407: The PaaS management entity receives the configuration request message, completes the unbinding of the public service and the tenant identifier according to the parameter in the message, and releases the public service instance corresponding to the tenant identifier to the PaaS platform.
S408:PaaS管理实体向VNFM返回PaaS公共服务配置的应答消息。S408: The PaaS management entity returns a response message of the PaaS public service configuration to the VNFM.
S409:VNFM根据实例化所终结的PaaS专有服务实例和配置去绑定的PaaS公共服务实例完成VNF实例的终结过程。S409: The VNFM completes the finalization process of the VNF instance according to the PaaS proprietary service instance terminated by the instantiation and the PaaS public service instance that is configured to be bound.
需要说明的是,在本实施例过程的示例中,步骤S403-S405对PaaS专有服务的实例化操作和步骤S406-S408对PaaS公共服务的配置操作可以互换顺序,或者并发执行,在此不作限定。It should be noted that, in the example of the process of this embodiment, the instantiation operation of the PaaS proprietary service in steps S403-S405 and the configuration operation of the PaaS public service in steps S406-S408 may be interchanged, or concurrently performed. Not limited.
通过本发明实施例的方法,通过NFV的MANO和PaaS管理实体的交互,实现VNF实例在调用了PaaS平台服务情况下的终结,完善了NFV PaaS服务能力调用的生命周期管理。Through the method of the embodiment of the present invention, the interaction between the MANO of the NFV and the PaaS management entity realizes the termination of the VNF instance in the case of calling the PaaS platform service, and improves the lifecycle management of the NFV PaaS service capability call.
下面进一步介绍支持云原生特性的VNF实例弹性伸缩(scale)过程,支持云原生特性的VNF实例弹性伸缩可以分为两段过程,彼此可以连接在一起或分开独立执行,如图5和图6所示,图5为VNF实例弹性伸缩触发专有服务实例弹性伸缩,图6给出PaaS公共服务实例弹性伸缩的过程。The following describes the VNF instance elastic scaling process that supports the native features of the cloud. The VNF instance elastic scaling that supports the native features of the cloud can be divided into two processes, which can be connected together or separately, as shown in Figure 5 and Figure 6. As shown in Figure 5, the VNF instance elastic scaling triggers the private service instance elastic scaling. Figure 6 shows the elastic scaling process of the PaaS public service instance.
步骤501:MANO(VNFM)接收来自发送者Sender(可以是NFVO或EM)的VNF实例弹性伸缩(VNF scale)请求,该弹性伸缩请求消息中携带要实例化的VNF实例标识和弹性伸缩操作相关的信息。其中,弹性伸缩操作相关的信息包括弹性伸缩操作的类型{scale in,scale out},弹性伸缩执行的步长等。Step 501: The MANO (VNFM) receives a VNF instance resilience (VNF scale) request from the sender Sender (which may be NFVO or EM), and the elastic scalability request message carries the VNF instance identifier to be instantiated and is related to the elastic scaling operation. information. The information related to the elastic stretching operation includes the type of the elastic stretching operation {scale in, scale out}, the step size of the elastic stretching, and the like.
步骤502:VNFM根据PaaS服务和服务所支持的租户(可以对应VNF)类型的映射关系,确定该VNF实例调用的专有服务。Step 502: The VNFM determines the proprietary service invoked by the VNF instance according to the mapping relationship between the PaaS service and the tenant (which can correspond to the VNF) type supported by the service.
步骤503:VNFM向PaaS管理实体发起专有服务弹性伸缩(scale)请求操作,该弹性伸缩请求消息中携带需要进行弹性伸缩的专有服务实例的标识和弹性伸缩操作相关的信息。其中,弹性伸缩操作相关的信息包括弹性伸缩操作的类型{scale in,scale out},弹性伸缩执行的步长等。Step 503: The VNFM initiates a proprietary service elastic scaling request operation to the PaaS management entity, where the elastic scalability request message carries the identifier of the proprietary service instance that needs to be elastically scaled and the information related to the elastic scaling operation. The information related to the elastic stretching operation includes the type of the elastic stretching operation {scale in, scale out}, the step size of the elastic stretching, and the like.
步骤504:PaaS管理实体接收该弹性伸缩请求消息,按照消息中参数的指示执行PaaS专有服务的弹性伸缩。Step 504: The PaaS management entity receives the elastic scalability request message, and performs elastic scaling of the PaaS proprietary service according to the indication of the parameter in the message.
步骤505:PaaS管理实体向VNFM返回PaaS专有服务弹性伸缩的应答消息。Step 505: The PaaS management entity returns a response message of the PaaS proprietary service elastic extension to the VNFM.
步骤506:VNFM根据PaaS专有服务实例的弹性伸缩结果完成VNF实例的弹性伸缩过程。Step 506: The VNFM completes the elastic scaling process of the VNF instance according to the elastic scaling result of the PaaS proprietary service instance.
图6给出PaaS管理向VNFM订阅PaaS公共服务租户弹性伸缩的通知的过程。根据前述实施例过程描述,PaaS管理实体内部自主触发执行公共服务的生命周期管理,在本实施例图6中所示的订阅通知过程可以作为触发PaaS管理实体执行auto-scale操作的条件,但PaaS管理实体也可以进一步结合其他的监视信息来判断是否执行公共服务的auto-scale过程。因此,图6所示的订阅通知过程与PaaS管理实体触发执行公共服务的auto-scale过程相互解耦。Figure 6 shows the process by which PaaS management subscribes to the VNFM for PaaS public service tenant elastic scaling. According to the process description of the foregoing embodiment, the PaaS management entity internally autonomously triggers the lifecycle management of the public service, and the subscription notification process shown in FIG. 6 in this embodiment can be used as a condition for triggering the PaaS management entity to perform an auto-scale operation, but PaaS The management entity can also further combine other monitoring information to determine whether to perform the auto-scale process of the public service. Thus, the subscription notification process shown in Figure 6 is decoupled from the auto-scale process that the PaaS management entity triggers to perform the public service.
S601:PaaS管理实体向VNFM订阅公共服务租户弹性伸缩通知,在订阅请求消息中指出订阅事件的条件,包括公共服务的名称。S601: The PaaS management entity subscribes to the public service tenant elastic extension notification to the VNFM, and indicates the condition of the subscription event in the subscription request message, including the name of the public service.
S602:MANO(VNFM)接收来自发送者Sender(可以是NFVO或EM)的VNF实例弹性伸缩(VNF scale)请求,该弹性伸缩请求消息中携带要实例化的VNF实例标识和弹性伸缩操作相关的信息。S602: The MANO (VNFM) receives a VNF instance resiliency (VNF scale) request from the sender Sender (which may be NFVO or EM), and the elastic retraction request message carries information about the VNF instance identifier to be instantiated and the elastic scaling operation. .
S603:VNFM根据PaaS服务和服务所支持的租户(可以对应VNF)类型的映射关系,确定该VNF实例调用的公共服务。S603: The VNFM determines the public service invoked by the VNF instance according to the mapping relationship between the tenant (which can correspond to the VNF) type supported by the PaaS service and the service.
S604:如果该VNF实例调用的公共服务包括步骤1的订阅通知中携带的公共服务的名称,则VNFM向PaaS管理实体发送公共服务弹性伸缩通知,通知消息中携带以下至少一项:公共服务的名称、调用该公共服务的租户的标识信息、弹性伸缩操作相关的信息。其中,弹性伸缩操作相关的信息包括弹性伸缩操作的类型{scale in,scale out},弹性伸缩执行的步长等。S604: If the public service invoked by the VNF instance includes the name of the public service carried in the subscription notification of step 1, the VNFM sends a public service elastic extension notification to the PaaS management entity, where the notification message carries at least one of the following: the name of the public service The information about the tenant of the public service and the information related to the elastic extension operation. The information related to the elastic stretching operation includes the type of the elastic stretching operation {scale in, scale out}, the step size of the elastic stretching, and the like.
图7的过程和图5的过程相似,参考附图7中文字描述,在本实施例中,要进行弹性伸缩的专有服务实例和公共服务实例不再进行差异化处理,VNFM可以通过统一的服务操作命令向PaaS管理实体发起服务(不区分是专有服务还是公共服务)的弹性伸缩请求操作,本发明实施例在此不在赘述。The process of FIG. 7 is similar to the process of FIG. 5. Referring to the text in FIG. 7, in this embodiment, the private service instance and the public service instance to be elastically stretched are not differentiated, and the VNFM can be unified. The elastic operation request operation of the service operation command to the PaaS management entity (whether it is a proprietary service or a public service) is not described herein.
上述实施例主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是,各个网元,例如VNFM,PaaS管理实体为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本发明的范围。The foregoing embodiment mainly introduces the solution of the embodiment of the present invention from the perspective of interaction between the network elements. It can be understood that each network element, such as VNFM, the PaaS management entity, in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
本发明实施例可以根据上述方法示例对VNFM,PaaS管理实体进行功能单元的划分,例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。需要说明的是,本发明实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。The embodiment of the present invention may divide the functional units of the VNFM and the PaaS management entity according to the foregoing method. For example, each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
在采用集成的模块或者单元的情况下,图8示出了上述实施例中所涉及的VNFM800的一种可能的结构示意图,包括:处理模块801,发送模块802,和实例化模块803。FIG. 8 shows a possible structural diagram of the VNFM 800 involved in the foregoing embodiment, including a processing module 801, a sending module 802, and an instantiation module 803.
所述处理模块801,用于根据VNF实例化请求中携带的需要实例化的VNF的标识,以及PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS服务,还进一步用于确定所述VNF实例需要调用的所述PaaS服务的容量,例如实例数;The processing module 801 is configured to determine, according to the identifier of the VNF that needs to be instantiated in the VNF instantiation request, and the mapping relationship between the PaaS service and the VNF, to determine the PaaS service that needs to be invoked by the VNF instance, and further determine Describe the capacity of the PaaS service that the VNF instance needs to invoke, such as the number of instances;
所述发送模块802,用于向PaaS管理实体发送所述PaaS服务的配置请求,所述配置请求中携带所述需要调用的PaaS服务标识,容量以及租户的标识,所述租户对应调用所述PaaS服务的VNF;The sending module 802 is configured to send a configuration request of the PaaS service to a PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity, and the identifier of the tenant, and the tenant correspondingly invokes the PaaS Service VNF;
所述实例化模块803,用于根据所述PaaS管理实体分配给所述VNF的所述指定容量的PaaS服务实例,完成所述VNF的实例化。The instantiation module 803 is configured to complete instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
所述VNF实例需要调用的PaaS服务为公共服务的情况下,如果所述VNF实例需要调用的PaaS服务还包括专有服务,所述发送模块802还进一步用于向PaaS管理实体发送实例化所 述专有服务的请求,所述请求中携带需要实例化的专有服务标识和实例化操作参数;In the case that the VNF instance needs to invoke the PaaS service as a public service, if the PafS service that the VNF instance needs to invoke further includes a proprietary service, the sending module 802 is further configured to send the instantiated to the PaaS management entity. a request for a proprietary service carrying a proprietary service identifier and instantiated operational parameters that need to be instantiated;
所述实例化模块803进一步用于根据在PaaS平台上实例化的所述专有服务实例和配置的所述公共服务实例,完成所述VNF的实例化。The instantiation module 803 is further configured to complete instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
在采用集成的模块或者单元的情况下,图9示出了上述实施例中所涉及的的一种可能的PaaS管理实体结构示意图,包括:服务模块901和响应模块902,FIG. 9 is a schematic structural diagram of a possible PaaS management entity involved in the foregoing embodiment, including: a service module 901 and a response module 902, where an integrated module or unit is used.
所述服务模块901,用于接收VNFM发送的PaaS服务配置请求,所述配置请求中携带需要调用的PaaS服务名称,PaaS服务的容量(例如实例数)以及调用所述PaaS服务的VNF对应的租户标识;并根据所述配置请求,将指定容量的所述PaaS服务分配给所述租户;The service module 901 is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service name that needs to be called, a capacity of the PaaS service (for example, an instance number), and a tenant corresponding to the VNF that invokes the PaaS service. Identifying, and assigning, according to the configuration request, the PaaS service of the specified capacity to the tenant;
所述响应模块902,用于向所述VNFM返回所述PaaS服务配置的执行结果。The response module 902 is configured to return an execution result of the PaaS service configuration to the VNFM.
在所述配置请求中携带需要调用的PaaS服务可以为公共服务,所述服务模块901还进一步用于接收所述VNFM发送的实例化专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数;所述服务模块接收所述实例化请求,根据所述请求中的实例化操作参数实例化所述专有服务;所述响应模块902还进一步用于向所述VNFM返回所述专有服务实例化的执行结果。The PaaS service that needs to be invoked in the configuration request may be a public service, and the service module 901 is further configured to receive a request for instantiating a proprietary service sent by the VNFM, where the request carries a specialization that needs to be instantiated. Having a service name and instantiating an operational parameter; the service module receiving the instantiation request, instantiating the proprietary service based on an instantiated operational parameter in the request; the response module 902 is further for The VNFM returns the execution result of the proprietary service instantiation.
所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,上述描述的VNFM和PaaS管理实体,以及它们包含的模块的具体工作过程,可以参考前述图3-图7所描述的实施例中VNFM和PaaS管理实体的对应过程,在此不再赘述。上述实施例仅是举例说明,本发明实施例不限于此,因此,本发明实施例提供的VNFM和PaaS管理实体,通过交互,实现了VNF在实例化过程中对PaaS服务,特别是公共服务实例的调用。由于PaaS上的公共服务的生命周期管理与NFV实例的生命周期管理是解耦的,提高了资源的利用率和VNF实例的运行效率;本发明实施例还进一步包含了VNF实例化过程中对PaaS平台的公共服务和专有服务共同调用,从而更进一步的解决了复杂场景下的PaaS平台服务调用问题。It will be apparent to those skilled in the art that for the convenience and brevity of the description, the specific working processes of the VNFM and PaaS management entities described above, and the modules they contain, may refer to the embodiments described in the foregoing FIGS. 3-7. The corresponding process of the VNFM and PaaS management entities will not be described here. The foregoing embodiment is only an example, and the embodiment of the present invention is not limited thereto. Therefore, the VNFM and the PaaS management entity provided by the embodiment of the present invention implement the VNF in the process of instantiation to the PaaS service, especially the public service instance. Call. The lifecycle management of the public service on the PaaS is decoupled from the lifecycle management of the NFV instance, which improves the resource utilization and the operating efficiency of the VNF instance. The embodiment of the present invention further includes the VNF instantiation process for the PaaS. The platform's public service and proprietary service are called together, which further solves the PaaS platform service call problem in complex scenarios.
本发明实施例还提供了一种NFV网络系统,如图10所示,所述NFV网络系统1000包括VNFM和PaaS管理实体。The embodiment of the present invention further provides an NFV network system. As shown in FIG. 10, the NFV network system 1000 includes a VNFM and a PaaS management entity.
前述方法实施例和装置实例中涉及的各步骤和各模块的所有相关内容均可以援引到该系统中各功能模块,在此不再赘述。The various steps involved in the foregoing method embodiments and device examples and all related contents of each module may be referred to each functional module in the system, and details are not described herein again.
本发明前述所有实施例中的VNFM和PaaS管理实体可以通过计算机设备的形式实现。The VNFM and PaaS management entities in all of the foregoing embodiments of the present invention may be implemented in the form of a computer device.
请参阅图11,是本申请实施例提供的一种虚拟网络功能管理器VNFM或者PaaS管理实体的结构示意图。如图11所示,该网元包括处理器1101、存储器1102以及收发器1103。处理器1101连接到存储器1102和收发器1103,例如处理器1101可以通过总线连接到存储器1102和收发器1103。FIG. 11 is a schematic structural diagram of a virtual network function manager VNFM or a PaaS management entity according to an embodiment of the present application. As shown in FIG. 11, the network element includes a processor 1101, a memory 1102, and a transceiver 1103. The processor 1101 is coupled to the memory 1102 and the transceiver 1103, for example, the processor 1101 can be coupled to the memory 1102 and the transceiver 1103 via a bus.
处理器1101可以被配置为支持VNFM执行图2-图7所述方法实施例中相应的功能,也可以被配置为支持PaaS管理实体执行图2-图7所述方法中相应的功能。该处理器1101可以是中央处理器(英文:central processing unit,CPU),网络处理器(英文:network processor,NP),硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文:application-specific integrated circuit,ASIC),可编程逻辑器件(英文:programmable logic device,PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文:complex programmable logicdevice,CPLD),现场可编程逻辑门阵列(英文:field-programmable gate array,FPGA),通用阵列逻辑(英文:generic array logic,GAL)或其任意组合。The processor 1101 may be configured to support the VNFM to perform the corresponding functions in the method embodiments described in Figures 2-7, and may also be configured to support the PaaS management entity to perform the corresponding functions in the methods described in Figures 2-7. The processor 1101 can be a central processing unit (CPU), a network processor (in English), a hardware chip, or any combination thereof. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or Any combination thereof.
存储器1102存储器用于存储程序代码等。存储器1102可以包括易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random access memory,缩写:RAM);存储器1102也可以包括非易失性存储器(英文:non-volatile memory),例如只读存储器(英文:read-only memory,缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD);存储器1102还可以包括上述种类的存储器的组合。The memory 1102 is used to store program codes and the like. The memory 1102 may include a volatile memory (English: volatile memory), such as a random access memory (English: random access memory, abbreviation: RAM); the memory 1102 may also include a non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 1102 may also include a combination of memories of the above kind.
收发器1103可以是通信模块、收发电路,用于实现VNFM或者PaaS管理实体与其他网络单元之间的数据、信令等信息的传输。The transceiver 1103 can be a communication module and a transceiver circuit for implementing transmission of data, signaling, and the like between the VNFM or the PaaS management entity and other network elements.
处理器1101可以调用所述程序代码以执行图2-图7所述方法实施例中的操作。The processor 1101 can invoke the program code to perform the operations in the method embodiments described in Figures 2-7.
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质。例如,可以利用磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))来存储或传输所述计算机指令。In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center. The computer readable storage medium can be any available media that can be accessed by a computer. For example, the computer instructions can be stored or transmitted using a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)).
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到各种等效的修改或替换,这些修改或替换都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应以权利要求的保护范围为准。The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any equivalent person can be easily conceived within the technical scope of the present invention by any person skilled in the art. Modifications or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
Claims (21)
- 一种虚拟网络功能VNF的实例化方法,其特征在于,所述方法包括:An instantiation method for a virtual network function VNF, the method comprising:虚拟网络功能管理器VNFM接收VNF实例化请求,所述VNF实例化请求中携带需要实例化的VNF的标识;The virtual network function manager VNFM receives the VNF instantiation request, where the VNF instantiation request carries the identifier of the VNF that needs to be instantiated;所述VNFM根据PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS服务,并确定所述VNF实例需要调用的所述PaaS服务的容量;Determining, by the VNFM, a PaaS service that the VNF instance needs to invoke according to a mapping relationship between the PaaS service and the VNF, and determining a capacity of the PaaS service that the VNF instance needs to invoke;所述VNFM向PaaS管理实体发送所述PaaS服务的配置请求,所述配置请求中携带所述需要调用的PaaS服务标识,容量以及租户的标识,所述租户对应调用所述PaaS服务的VNF;The VNFM sends a configuration request of the PaaS service to the PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity and the identifier of the tenant, and the tenant corresponds to the VNF of the PaaS service.所述VNFM根据所述PaaS管理实体分配给所述VNF的所述指定容量的PaaS服务实例,完成所述VNF的实例化。The VNFM completes instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
- 如权利要求1中所述的方法,其特征在于,所述VNF实例需要调用的PaaS服务为公共服务。The method of claim 1 wherein the VNF instance needs to invoke a PaaS service as a public service.
- 如权利要求2中所述的方法,其特征在于,所述VNF实例需要调用的PaaS服务还包括专有服务,则所述方法进一步包括,The method of claim 2, wherein the PaaS service that the VNF instance needs to invoke further includes a proprietary service, and the method further includes,所述VNFM向PaaS管理实体发送实例化所述专有服务的请求,所述请求中携带需要实例化的专有服务标识和实例化操作参数;The VNFM sends a request to the PaaS management entity to instantiate the proprietary service, where the request carries a proprietary service identifier and an instantiated operational parameter that need to be instantiated;所述VNFM根据在PaaS平台上实例化的所述专有服务实例和配置的所述公共服务实例,完成所述VNF的实例化。The VNFM completes instantiation of the VNF based on the proprietary service instance instantiated on the PaaS platform and the configured public service instance.
- 如权利要求3所述的方法,其特征在于,所述方法还进一步包括:The method of claim 3, wherein the method further comprises:所述VNFM接收VNF实例弹性伸缩请求,所述弹性伸缩请求中携带VNF实例标识和弹性伸缩操作参数;The VNFM receives the VNF instance elastic scaling request, where the elastic scaling request carries the VNF instance identifier and the elastic scaling operation parameter;所述VNFM根据PaaS服务和VNF的映射关系,确定所述VNF实例调用的专有服务;Determining, by the VNFM, a proprietary service invoked by the VNF instance according to a mapping relationship between the PaaS service and the VNF;所述VNFM向所述PaaS管理实体发送弹性伸缩请求,所述弹性伸缩请求中携带所述调用的专有服务标识和所述弹性伸缩操作参数;The VNFM sends an elastic scaling request to the PaaS management entity, where the elastic scaling request carries the called private service identifier and the elastic scaling operation parameter;所述VNFM接收所述PaaS管理实体返回的所述弹性伸缩的执行结果。The VNFM receives an execution result of the elastic scaling returned by the PaaS management entity.
- 如权利要求2所述的方法,其特征在于,所述方法还进一步包括:The method of claim 2, wherein the method further comprises:所述VNFM接收VNF实例终结请求,所述VNF实例终结请求中携带需要终结的VNF实例标识;The VNFM receives the VNF instance termination request, and the VNF instance termination request carries the VNF instance identifier that needs to be terminated;所述VNFM根据PaaS服务和VNF的映射关系,确定所述需要终结的VNF实例调用的公共服务;Determining, by the VNFM, a public service invoked by the VNF instance that needs to be terminated according to a mapping relationship between the PaaS service and the VNF;所述VNFM向所述PaaS管理实体发起公共服务配置请求,所述配置请求中携带需要终结的公共服务标识和调用该公共服务的VNF对应的租户标识;The VNFM initiates a public service configuration request to the PaaS management entity, where the configuration request carries a public service identifier that needs to be terminated and a tenant identifier corresponding to the VNF that invokes the public service;所述VNFM接收所述PaaS管理实体返回的公共服务配置的应答消息;Receiving, by the VNFM, a response message of a public service configuration returned by the PaaS management entity;所述VNFM根据所述公共服务配置应答消息完成VNF实例的终结过程。The VNFM completes the termination process of the VNF instance according to the public service configuration response message.
- 如权利要求5所述的方法,其特征在于,所述方法进一步包括:所述VNFM根据PaaS服务和VNF的映射关系,确定所述需要终结的VNF实例调用的PaaS服务还包括专有服务,则所述方法进一步包括:The method according to claim 5, wherein the method further comprises: determining, by the VNFM, that the PaaS service invoked by the VNF instance that needs to be terminated further includes a proprietary service according to a mapping relationship between the PaaS service and the VNF, The method further includes:所述VNFM向所述PaaS管理实体发起专有服务终结请求,所述终结请求中携带需要终结的专有服务实例的标识。The VNFM initiates a proprietary service termination request to the PaaS management entity, where the termination request carries an identifier of a proprietary service instance that needs to be terminated.所述VNFM接收所述PaaS管理实体返回的所述专有服务实例终结的应答消息;Receiving, by the VNFM, a response message of the termination of the proprietary service instance returned by the PaaS management entity;所述VNFM根据所述专有服务实例终结的应答消息和所述公共服务配置应答消息完成VNF实例的终结过程。The VNFM completes the termination process of the VNF instance according to the response message terminated by the proprietary service instance and the public service configuration response message.
- 如权利要求1-6中任一项所述的方法,其特征在于,所述PaaS服务和VNF的映射关系存储在所述VNF的描述符文件VNFD中,所述VNFM从所述VNFD中获取所述映射关系。The method according to any one of claims 1 to 6, wherein the mapping relationship between the PaaS service and the VNF is stored in a descriptor file VNFD of the VNF, and the VNFM obtains the VNFD from the VNFD. The mapping relationship.
- 如权利要求1-7中任一项所述的方法,其特征在于,所述VNFM从所述VNF的VNFD文件中获得所述VNF在实例化时需要使用的PaaS服务的容量,所述容量包括所述PaaS服务的实例数。The method according to any one of claims 1 to 7, wherein the VNFM obtains a capacity of a PaaS service that the VNF needs to use when instantiating from a VNFD file of the VNF, the capacity including The number of instances of the PaaS service.
- 一种虚拟网络功能VNF的实例化方法,其特征在于,所述方法包括:An instantiation method for a virtual network function VNF, the method comprising:PaaS管理实体接收VNFM发送的PaaS服务配置请求,所述配置请求中携带需要调用的PaaS服务名称,PaaS服务的容量以及调用所述PaaS服务的VNF对应的租户标识;The PaaS management entity receives the PaaS service configuration request sent by the VNFM, where the configuration request carries the name of the PaaS service to be called, the capacity of the PaaS service, and the tenant identifier corresponding to the VNF that invokes the PaaS service;所述PaaS管理实体根据所述配置请求,将指定容量的所述PaaS服务分配给所述租户;And the PaaS management entity allocates the PaaS service of a specified capacity to the tenant according to the configuration request;所述PaaS管理实体向所述VNFM返回所述PaaS服务配置的执行结果。The PaaS management entity returns an execution result of the PaaS service configuration to the VNFM.
- 如权利要求9中所述的方法,其特征在于,所述配置请求中携带需要调用的PaaS服务为公共服务。The method according to claim 9, wherein the configuration request carries a PaaS service that needs to be called as a public service.
- 如权利要求10中所述的方法,其特征在于,所述方法进一步包括,The method of claim 10 wherein said method further comprises所述PaaS管理实体接收所述VNFM发送的实例化专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数;Receiving, by the PaaS management entity, a request for instantiating a proprietary service sent by the VNFM, where the request carries a proprietary service name and an instantiated operation parameter that need to be instantiated;所述PaaS管理实体接收所述实例化请求,根据所述请求中的实例化操作参数实例化所述专有服务;Receiving, by the PaaS management entity, the instantiation request, instantiating the proprietary service according to an instantiated operation parameter in the request;所述PaaS管理实体向所述VNFM返回所述专有服务实例化的执行结果。The PaaS management entity returns an execution result of the proprietary service instantiation to the VNFM.
- 如权利要求11所述的方法,其特征在于,所述方法还进一步包括:The method of claim 11 wherein the method further comprises:所述PaaS管理实体接收所述VNFM发送的弹性伸缩请求,所述弹性伸缩请求中携带所述调用的PaaS专有服务标识和弹性伸缩操作参数;Receiving, by the PaaS management entity, the elastic scalability request sent by the VNFM, where the elastic scalability request carries the PaaS-specific service identifier and the elastic scaling operation parameter of the call;所述PaaS管理实体根据所述弹性伸缩请求,执行所述PaaS专有服务的弹性伸缩并向所述VNFM返回所述弹性伸缩的执行结果。The PaaS management entity performs elastic scaling of the PaaS proprietary service according to the elastic scaling request and returns an execution result of the elastic scaling to the VNFM.
- 如权利要求9-12任一项所述的方法,其特征在于,所述PaaS服务的容量包括所述PaaS服务的实例数。A method according to any of claims 9-12, wherein the capacity of the PaaS service comprises the number of instances of the PaaS service.
- 一种虚拟网络功能管理器VNFM,其特征在于,包括:处理模块,发送模块,和实例化模块A virtual network function manager VNFM, comprising: a processing module, a sending module, and an instantiation module所述处理模块,用于根据VNF实例化请求中携带的需要实例化的VNF的标识,以及PaaS服务和VNF的映射关系,确定所述VNF实例需要调用的PaaS服务,还进一步用于确定所述VNF实例需要调用的所述PaaS服务的容量;The processing module is configured to determine, according to the identifier of the VNF that needs to be instantiated in the VNF instantiation request, and the mapping relationship between the PaaS service and the VNF, the PaaS service that needs to be invoked by the VNF instance, and further used to determine the The capacity of the PaaS service that the VNF instance needs to invoke;所述发送模块,用于向PaaS管理实体发送所述PaaS服务的配置请求,所述配置请求中携带所述需要调用的PaaS服务标识,容量以及租户的标识,所述租户对应调用所述PaaS服务的VNF;The sending module is configured to send a configuration request of the PaaS service to a PaaS management entity, where the configuration request carries the PaaS service identifier, the capacity, and the identifier of the tenant, and the tenant correspondingly invokes the PaaS service VNF;所述实例化模块,用于根据所述PaaS管理实体分配给所述VNF的所述指定容量的PaaS服务实例,完成所述VNF的实例化。The instantiation module is configured to complete instantiation of the VNF according to the PaaS service instance of the specified capacity allocated by the PaaS management entity to the VNF.
- 如权利要求14中所述的VNFM,其特征在于,所述VNF实例需要调用的PaaS服务为公共服务。A VNFM as claimed in claim 14, wherein the VNF instance needs to invoke a PaaS service as a public service.
- 如权利要求15中所述的VNFM,其特征在于,所述VNF实例需要调用的PaaS服务还包括专有服务,所述发送模块进一步用于向PaaS管理实体发送实例化所述专有服务的请求, 所述请求中携带需要实例化的专有服务标识和实例化操作参数;A VNFM as claimed in claim 15 wherein the PaaS service to be invoked by the VNF instance further comprises a proprietary service, the transmitting module further for transmitting a request to the PaaS management entity to instantiate the proprietary service The request carries a proprietary service identifier and an instantiated operation parameter that need to be instantiated;所述实例化模块进一步用于根据在PaaS平台上实例化的所述专有服务实例和配置的所述公共服务实例,完成所述VNF的实例化。The instantiation module is further for performing instantiation of the VNF based on the proprietary service instance and the configured public service instance instantiated on a PaaS platform.
- 一种PaaS管理实体,其特征在于,包括服务模块和响应模块,A PaaS management entity, comprising: a service module and a response module,所述服务模块,用于接收VNFM发送的PaaS服务配置请求,所述配置请求中携带需要调用的PaaS服务名称,PaaS服务的容量以及调用所述PaaS服务的VNF对应的租户标识;并根据所述配置请求,将指定容量的所述PaaS服务分配给所述租户;The service module is configured to receive a PaaS service configuration request sent by the VNFM, where the configuration request carries a PaaS service name that needs to be invoked, a capacity of the PaaS service, and a tenant identifier corresponding to the VNF that invokes the PaaS service; Configuring a request to allocate the PaaS service of a specified capacity to the tenant;所述响应模块,用于向所述VNFM返回所述PaaS服务配置的执行结果。The response module is configured to return an execution result of the PaaS service configuration to the VNFM.
- 如权利要求17所述的PaaS管理实体,其特征在于,所述配置请求中携带需要调用的PaaS服务为公共服务。The PaaS management entity according to claim 17, wherein the configuration request carries a PaaS service that needs to be called as a public service.
- 如权利要求18所述的PaaS管理实体,其特征在于,则所述服务模块还进一步用于接收所述VNFM发送的实例化专有服务的请求,所述请求中携带需要实例化的专有服务名称和实例化操作参数;所述服务模块接收所述实例化请求,根据所述请求中的实例化操作参数实例化所述专有服务;The PaaS management entity according to claim 18, wherein the service module is further configured to receive a request for instantiating a proprietary service sent by the VNFM, the request carrying a proprietary service that needs to be instantiated Name and instantiating an operational parameter; the service module receives the instantiation request, instantiating the proprietary service according to an instantiated operational parameter in the request;所述响应模块还进一步用于向所述VNFM返回所述专有服务实例化的执行结果。The response module is further configured to return an execution result of the proprietary service instantiation to the VNFM.
- 一种NFV网络系统,其特征在于,包含权利要求14-16中任一项中的VNFM和所述权利要求权利要求17-19中任一项中的PaaS管理实体。An NFV network system, comprising the VNFM of any one of claims 14-16 and the PaaS management entity of any of claims 17-19.
- 一种计算机可读存储介质,包括程序指令,当其在计算机上运行时,使得计算机执行如权利要求1-13任意一项所述的NFV实例化方法。A computer readable storage medium comprising program instructions which, when executed on a computer, cause the computer to perform the NFV instantiation method of any of claims 1-13.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710792188.1A CN109428764B (en) | 2017-09-05 | 2017-09-05 | Virtual network function instantiation method |
CN201710792188.1 | 2017-09-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019047835A1 true WO2019047835A1 (en) | 2019-03-14 |
Family
ID=65514108
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/104055 WO2019047835A1 (en) | 2017-09-05 | 2018-09-05 | Instantiation method for virtual network function |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN109428764B (en) |
WO (1) | WO2019047835A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112015515A (en) * | 2019-05-28 | 2020-12-01 | 华为技术有限公司 | Virtual network function instantiation method and device |
CN113395178A (en) * | 2021-06-11 | 2021-09-14 | 聚好看科技股份有限公司 | Method and device for elastic expansion and contraction of container cloud |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111988263B (en) * | 2019-05-22 | 2021-07-16 | 华为技术有限公司 | Container service management method, container manager, virtual network function instance and virtual network function manager |
CN110535964B (en) * | 2019-09-03 | 2021-12-14 | 北京首都在线科技股份有限公司 | Data processing method and device based on Paas connector |
CN112559113B (en) * | 2019-09-10 | 2023-11-10 | 中国移动通信集团浙江有限公司 | CMDB-based NFV configuration management method, system, server and storage medium |
CN114124740A (en) * | 2020-08-03 | 2022-03-01 | 华为技术有限公司 | VNF instantiation method and device |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016154917A1 (en) * | 2015-03-31 | 2016-10-06 | 华为技术有限公司 | Method and apparatus for managing virtualized network function |
CN106161173A (en) * | 2015-04-15 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of virtual network function that realizes disposes the method and device of specification configuration |
CN106161171A (en) * | 2015-03-23 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of method and apparatus setting up Network example |
CN106375101A (en) * | 2015-07-20 | 2017-02-01 | 华为技术有限公司 | Life cycle management method and apparatus |
US20170208147A1 (en) * | 2014-04-30 | 2017-07-20 | Hewlett Packard Enterprise Development Lp | Network infrastructure management |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9973375B2 (en) * | 2013-04-22 | 2018-05-15 | Cisco Technology, Inc. | App store portal providing point-and-click deployment of third-party virtualized network functions |
BR112016004183A8 (en) * | 2013-08-27 | 2020-02-11 | Huawei Tech Co Ltd | method for virtualization of mobile network and computer function |
US9998320B2 (en) * | 2014-04-03 | 2018-06-12 | Centurylink Intellectual Property Llc | Customer environment network functions virtualization (NFV) |
CN104219127B (en) * | 2014-08-30 | 2018-06-26 | 华为技术有限公司 | A kind of creation method and equipment of virtual network example |
-
2017
- 2017-09-05 CN CN201710792188.1A patent/CN109428764B/en active Active
-
2018
- 2018-09-05 WO PCT/CN2018/104055 patent/WO2019047835A1/en active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170208147A1 (en) * | 2014-04-30 | 2017-07-20 | Hewlett Packard Enterprise Development Lp | Network infrastructure management |
CN106161171A (en) * | 2015-03-23 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of method and apparatus setting up Network example |
WO2016154917A1 (en) * | 2015-03-31 | 2016-10-06 | 华为技术有限公司 | Method and apparatus for managing virtualized network function |
CN106161173A (en) * | 2015-04-15 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of virtual network function that realizes disposes the method and device of specification configuration |
CN106375101A (en) * | 2015-07-20 | 2017-02-01 | 华为技术有限公司 | Life cycle management method and apparatus |
Non-Patent Citations (1)
Title |
---|
ETSI: "Network Functions Virtualisation (NFV); Software Architecture; Re- port on the Enhancements of the NFV architecture towards ''Cloud-native'' and ''PaaS'' Release 3", ETSI GR NFV-IFA 029 V0.0.2, 30 June 2017 (2017-06-30) * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112015515A (en) * | 2019-05-28 | 2020-12-01 | 华为技术有限公司 | Virtual network function instantiation method and device |
CN112015515B (en) * | 2019-05-28 | 2024-06-04 | 华为技术有限公司 | Instantiation method and device of virtual network function |
CN113395178A (en) * | 2021-06-11 | 2021-09-14 | 聚好看科技股份有限公司 | Method and device for elastic expansion and contraction of container cloud |
Also Published As
Publication number | Publication date |
---|---|
CN109428764A (en) | 2019-03-05 |
CN109428764B (en) | 2021-10-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200313969A1 (en) | Network Slice Deployment Method and Apparatus | |
CN109428764B (en) | Virtual network function instantiation method | |
KR102439559B1 (en) | Alarm method and device | |
US11108653B2 (en) | Network service management method, related apparatus, and system | |
WO2020186911A1 (en) | Resource management method and device for containerized virtualised network function vnf | |
CN111949364A (en) | Deployment method of containerized VNF and related equipment | |
CN108347343B (en) | Policy management method, device and system | |
CN111221618B (en) | Deployment method and device for containerized virtual network function | |
WO2017185303A1 (en) | Method and device for managing nfv mano policy descriptor | |
WO2017185251A1 (en) | Vnfm determining method and network function virtualization orchestrator | |
KR102674017B1 (en) | Network resource management method, system, network device and readable storage medium | |
WO2018032884A1 (en) | Charging method, device, and system | |
CN109995552B (en) | VNF service instantiation method and device | |
EP4177742A1 (en) | Multitenancy management method and apparatus | |
EP4024767A1 (en) | Vnf instantiation method, nfvo, vim, vnfm and system | |
WO2018153355A1 (en) | Control information transmission method, server, and system | |
WO2022140945A1 (en) | Container cluster management method and apparatus | |
WO2019034084A1 (en) | Method for applying for common service resource, related device, and system | |
WO2021004320A1 (en) | Service resource license management method and related device | |
WO2022198524A1 (en) | Service instance deployment method, and method and system for load balancing between nodes | |
CN112015515B (en) | Instantiation method and device of virtual network function | |
CN112889247B (en) | VNF service instantiation method and device | |
CN113098705B (en) | Authorization method and device for life cycle management of network service | |
WO2023155838A1 (en) | Virtual network function (vnf) instantiation method and apparatus | |
WO2023066224A1 (en) | Method and apparatus for deploying container service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18853215 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18853215 Country of ref document: EP Kind code of ref document: A1 |