WO2017113201A1 - 一种网络服务的生命周期管理方法及设备 - Google Patents

一种网络服务的生命周期管理方法及设备 Download PDF

Info

Publication number
WO2017113201A1
WO2017113201A1 PCT/CN2015/099911 CN2015099911W WO2017113201A1 WO 2017113201 A1 WO2017113201 A1 WO 2017113201A1 CN 2015099911 W CN2015099911 W CN 2015099911W WO 2017113201 A1 WO2017113201 A1 WO 2017113201A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
vnf instance
lifecycle management
requirement information
nsd
Prior art date
Application number
PCT/CN2015/099911
Other languages
English (en)
French (fr)
Inventor
许瑞岳
季莉
邹兰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580078723.6A priority Critical patent/CN107431651B/zh
Priority to BR112017028214-3A priority patent/BR112017028214B1/pt
Priority to ES15911830T priority patent/ES2764442T3/es
Priority to AU2015419073A priority patent/AU2015419073B2/en
Priority to JP2018518767A priority patent/JP6609696B2/ja
Priority to PCT/CN2015/099911 priority patent/WO2017113201A1/zh
Priority to EP19204458.4A priority patent/EP3668009B1/en
Priority to KR1020177034801A priority patent/KR20180002771A/ko
Priority to EP15911830.6A priority patent/EP3285439B1/en
Publication of WO2017113201A1 publication Critical patent/WO2017113201A1/zh
Priority to US15/859,821 priority patent/US10700947B2/en

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
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • 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/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • 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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
    • 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
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present invention relates to the field of network function virtualization technologies, and in particular, to a network service lifecycle management method and device.
  • Network Function Virtualization technology virtualizes one computer into multiple virtual logical computers, namely virtual machines (VMs).
  • VMs virtual machines
  • IT Information Technology
  • NFV technology enables many types of network devices to be incorporated into industry standards. For example, services, switching, storage, etc. can be deployed in data centers or network nodes.
  • NFV technology implements various network functions in software and runs on industry-standard servers. It can be migrated, instantiated, redeployed, etc. as needed, and virtual machines can be created without installing new devices.
  • Virtualized Network Function VNF
  • Network Service Network Service
  • the Network Service Descriptor is a template used by vendors to deploy network services.
  • An NSD includes multiple Virtualized Network Function Descriptors (VNFDs) and multiple deployment specifications.
  • VNFD Virtualized Network Function Descriptors
  • a template for deploying virtual network functions A VNFD can instantiate multiple VNFs according to different deployment specifications.
  • a VNFD can also instantiate multiple VNFs according to the same deployment specification.
  • the process of instantiating an NS is: the Operations Support System (OSS) requests the network function virtualization management entity (NFVO) to instantiate an NS according to the specified NSD; when the NFVO receives the request, it looks for the specified NSD, and by analyzing the correspondence between multiple VNFDs under the NSD and multiple deployment specifications, instantiate multiple VNFs and establish connections between multiple VNFs.
  • OSS Operations Support System
  • NFVO network function virtualization management entity
  • the embodiment of the invention provides a lifecycle management method and device for a network service, which can improve the processing efficiency of the lifecycle management and improve the utilization of resources.
  • a first aspect of the embodiments of the present invention provides a lifecycle management method for a network service, including:
  • the lifecycle management request includes a mapping relationship between the identifier of the existing virtual network function VNF instance and a feature parameter corresponding thereto, the feature
  • the parameter is an identifier parameter of each VNF instance requirement information tag in the plurality of VNF instance requirement information required for the target NSD in the target network service descriptor NSD;
  • the first device performs lifecycle management on the target NS according to the existing VNF instance and the mapping relationship.
  • the lifecycle management request further includes an identification of the target NSD.
  • the identifier of the existing VNF instance and the feature parameter corresponding thereto are determined by the second device according to the instance information of the existing VNF instance and the multiple VNF instance requirements required by the target NSD. Information is determined.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor and a deployment specification in the target NSD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor, a deployment specification, and an instance parameter in the target NSD, where the instance parameter is used to identify the same virtual network function descriptor. Different VNF instance requirement information under the same deployment specification.
  • the first device matches a feature parameter of each VNF instance requirement information in the plurality of VNF instance requirement information required by the target NSD with a mapping relationship included in the life management request, respectively Obtaining a feature parameter that matches the success and a feature parameter that fails to match;
  • the first device directly obtains an existing VNF instance corresponding to the feature parameter that is successfully matched;
  • the first device instantiates the VNF instance requirement information corresponding to the matching failed feature parameter, thereby fully utilizing the instantiated VNF instance in the network architecture, reducing the process of repeatedly instantiating the request information of some VNF instances, and improving the instance. Processing efficiency.
  • a second aspect of the embodiments of the present invention provides another lifecycle management method for a network service, including:
  • the second device determines, according to the lifecycle management requirement information, an existing VNF instance required for the lifecycle management of the target NS;
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS.
  • the lifecycle management request includes a mapping relationship between the identifier of the existing VNF instance and a feature parameter corresponding thereto, where the feature parameter is a plurality of VNF instance requirement information required for the target NSD in the target NSD.
  • the identification parameter of each VNF instance requirement information tag is a mapping relationship between the identifier of the existing VNF instance and a feature parameter corresponding thereto, where the feature parameter is a plurality of VNF instance requirement information required for the target NSD in the target NSD.
  • the lifecycle management requirement information determines an existing VNF instance and a target NSD required for the lifecycle management of the target NS, and the target NSD is a descriptor of the target NS;
  • the lifecycle management request further includes an identification of the target NSD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor and a deployment specification in the target NSD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor, a deployment specification, and an instance parameter in the target NSD, where the instance parameter is used to identify the same virtual network function descriptor. Different VNF instance requirement information under the same deployment specification.
  • a third aspect of the embodiments of the present invention provides a method for managing a life cycle of a network service, including:
  • the first device receives a lifecycle management request of the target NS sent by the second device, where the lifecycle management request includes an identifier of the target NSD, where the target NSD includes a target virtual network function forwarding map descriptor VNFFGD, where the target VNFFGD includes Characteristic parameters of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD;
  • the first device acquires the target VNFFGD according to the identifier of the target NSD;
  • the first device performs lifecycle management on the target NS according to a characteristic parameter of each VNF requirement information in the target VNFFGD.
  • the first device performs lifecycle management on the target NS according to a feature parameter of each VNF requirement information in the target VNFFGD, that is, the first device is configured according to the target VNFFGD.
  • the feature parameters of each VNF instance requirement information are network-connected to multiple VNF instances obtained by the target NS instantiation:
  • the first device is instantiated according to multiple VNF instance requirement information required by the target NSD. And connecting to the plurality of VNF instances, and performing network connection on the plurality of VNF instances according to characteristic parameters of each VNF requirement information in the target VNFFGD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor and a deployment specification in the target NSD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor, a deployment specification, and an instance parameter in the target NSD, where the instance parameter is used to identify the same virtual network function descriptor. Different VNF instance requirement information under the same deployment specification.
  • a fourth aspect of the embodiments of the present invention provides a method for managing a life cycle of a network service, including:
  • the second device determines, according to the lifecycle management requirement information, an identifier of the target NSD for the lifecycle management of the target NS;
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management request includes An identifier of the target NSD, where the target NSD includes a target VNFFGD, and the target VNFFGD includes a feature parameter of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD.
  • a fifth aspect of the embodiments of the present invention provides a first device, including:
  • a receiving unit configured to receive a lifecycle management request of the target network service NS sent by the second device, where the lifecycle management request includes a mapping relationship between the identifier of the virtual network function VNF instance and the corresponding feature parameter.
  • the feature parameter is an identifier parameter of each VNF instance requirement information tag in the plurality of VNF instance requirement information required for the target NSD in the target network service descriptor NSD;
  • a management unit configured to perform lifecycle management on the target NS according to the existing VNF instance and the mapping relationship.
  • the first device provided by the fifth aspect of the embodiments of the present invention is used to implement the first device according to the first aspect of the present disclosure.
  • a sixth aspect of the embodiments of the present invention provides a second device, including:
  • a determining unit configured to determine, according to the lifecycle management requirement information, an existing VNF instance required for the lifecycle management of the target NS;
  • a sending unit configured to send, to the first device, a lifecycle management request of the target NS, where The lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management request includes a mapping relationship between the identifier of the existing VNF instance and its corresponding feature parameter.
  • the feature parameter is an identification parameter of each VNF instance requirement information tag in the plurality of VNF instance requirement information required for the target NSD in the target NSD.
  • the second device provided by the sixth aspect of the embodiments of the present invention is used to implement the second device according to the second aspect of the present disclosure.
  • the specific implementation process reference may be made to the description of the second aspect, and details are not described herein again.
  • the seventh aspect of the embodiment of the present invention provides another first device, including:
  • a receiving unit configured to receive a lifecycle management request of a target NS sent by the second device, where the lifecycle management request includes an identifier of the target NSD, where the target NSD includes a virtual network function forwarding map descriptor VNFFGD, where the target VNFFGD includes Characteristic parameters of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD;
  • An obtaining unit configured to acquire the target VNFFGD according to the identifier of the target NSD;
  • a management unit configured to perform lifecycle management on the NS according to a feature parameter of each VNF requirement information in the target VNFFGD.
  • the first device provided in the seventh aspect of the present invention is used to implement the first device in the third aspect of the embodiment of the present invention.
  • An eighth aspect of the embodiment of the present invention provides another first device, including:
  • a determining unit configured to determine, according to the lifecycle management requirement information, an identifier of the target NSD for the lifecycle management of the target NS;
  • a sending unit configured to send a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management request includes An identifier of the target NSD, where the target NSD includes a target VNFFGD, and the target VNFFGD includes a feature parameter of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD.
  • the second device provided in the eighth aspect of the present invention is used to implement the second device according to the fourth aspect of the present disclosure.
  • the second device is used to implement the second device according to the fourth aspect of the present disclosure.
  • details refer to the description of the fourth aspect, and details are not described herein again.
  • a ninth aspect of the embodiments of the present invention provides a network service lifecycle management system, including the first device of the fifth aspect and the second device of the sixth aspect, and/or the seventh aspect An apparatus and the second apparatus of the eighth aspect.
  • the target device is determined by the second device according to the target NS for the life cycle.
  • the VNF instance is required to be managed, and the lifecycle management request of the target NS is sent to the first device, where the lifecycle management request is used to indicate that the first device performs lifecycle management on the target NS, and the lifecycle management request includes the existing VNF instance.
  • the mapping relationship between the identifier and the corresponding characteristic parameter, the characteristic parameter is an identification parameter of each VNF instance requirement information tag in the plurality of VNF instance requirement information required for the target NSD in the target NSD, and the first device receives the second parameter
  • the mapping relationship manages the lifecycle of the NS, improves the processing efficiency of lifecycle management, and improves the utilization of resources.
  • FIG. 1 is a schematic diagram of a network architecture of a network function virtualization NFV
  • FIG. 2 is a schematic flowchart of a lifecycle management method for a network service according to Embodiment 1 of the present invention
  • FIG. 3 is a basic constituent element of a VNF according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a lifecycle management method for a network service according to Embodiment 2 of the present invention.
  • FIG. 6 is a basic element of a VNFFGD according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a first device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a second device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another first device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another second device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of still another first device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of still another second device according to an embodiment of the present invention.
  • the method, device and system for managing a life cycle of a network service provided by the embodiment of the present invention can be applied to a scenario in which a network function virtualized NFV network performs lifecycle management on a network service NS.
  • FIG. 1 is a schematic diagram of a network architecture of network function virtualization NFV.
  • the NFV network is divided into three layers: the NFV Infrastructure (NFVI), the Virtual Network Function (VNF), and the management layer.
  • the infrastructure layer from the perspective of cloud computing, is a resource pool.
  • NFVI mapping to physical infrastructure is a number of geographically dispersed data centers that are connected by high-speed communication networks.
  • NFVI needs to convert physical computing/storage/switching resources into virtual compute/storage/swap resource pools through virtualization.
  • the virtual network layer includes a plurality of VNF network elements, and is not indicated in FIG.
  • the virtual network layer corresponds to each telecommunication network service.
  • Each physical network element is mapped to a virtual network function network element VNF.
  • the resources required by the VNF need to be decomposed into virtual computing/storage/exchange resources, which are carried by NFVI.
  • the interface between the two still uses the signaling interface defined by the traditional network.
  • Multiple VNFs can implement a network service NS.
  • Management includes Operations/Business Support System (OSS/BSS) and Element Manager (EM).
  • OSS/BSS Operations/Business Support System
  • EM Element Manager
  • the EM is used to manage some VNF network elements.
  • the operational support layer is the current OSS/BSS system. It 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 service. They are organically integrated through a unified information bus.
  • OSS is the business support system
  • BSS is the operation support system
  • the OSS/BSS system makes necessary modifications and adjustments for virtualization in the NFV network architecture.
  • NFV networks are divided into network service domains and resource management orchestration domains.
  • the network service domain is the current telecommunication network services, including OSS/BSS, EM, VNF and NFVI.
  • the Management and Orchestration (MANO) is responsible for the management and orchestration of the entire NFVI resource, the mapping and association of network services and NFVI resources, and the implementation of the OSS business resource process.
  • MANO includes Virtual Infrastructure Management (VIM), Virtual Network Function Management Entity (VNFM), and NFV Orchestrator (NFVO), which are not marked in Figure 1, and the three are The structure of MANO is from top to bottom for NFVO, VNFM, and VIM.
  • VIM is responsible for the management of virtualized infrastructure.
  • the functions include: collecting the status information of the hardware resources and the virtual resources and reporting them to the VNFM for resource monitoring, fault monitoring, and reporting; accepting the upper layer application request from the VNFM and performing authentication. After the authentication is passed, the virtual machine manager is controlled. The upper layer applies the request to implement resource migration and elastic scaling.
  • VNFM is responsible for the life cycle management of VNF and the monitoring of its resource usage.
  • VNF is instantiated, added, deleted, changed, queried, expanded/reduced, reserved, and dynamically monitored by the resources occupied by the VNF.
  • NFVO is responsible for the management and orchestration of the infrastructure and virtualized network functions VNF to achieve complete network services.
  • the OSS/BSS in FIG. 1 may send a lifecycle management request to the MANO, and the lifecycle management request may be used to request the MANO to instantiate a network service NS, or may request the MANO to network the plurality of VNFs obtained by the instantiation. Connections can also be used to request MANO to update a network service NS, and so on.
  • the lifecycle management request is used to request the MANO to instantiate an NS.
  • the lifecycle management request includes an identifier of the specified NSD. When receiving the lifecycle management request, the MANO searches for the specified NSD according to the identifier of the specified NSD.
  • the specified NSD is analyzed, and the VNF instance requirement information under the specified NSD is analyzed, and multiple VNF instances are instantiated according to the VNF instance requirement information, thereby realizing the instantiation of the NS.
  • the network architecture composed of OSS/BSS and MANO
  • VNF instances that have been instantiated in these instantiated VNF instances and some VNF instance requirements required by the specified NSD Information matching
  • MANO can directly use these instantiated VNF instances to instantiate the NS, but MANO still performs instantiation of the NS according to the above process, which not only reduces the efficiency of instantiation processing, but also wastes the network architecture.
  • Instantiated VNF instance resources are some instantiated VNF instances in the network architecture composed of OSS/BSS and MANO, and some VNF instances that have been instantiated in these instantiated VNF instances and some VNF instance requirements required by the specified NSD Information matching.
  • the lifecycle management method of the network service provided by the embodiment of the present invention can improve the processing efficiency of the lifecycle management and fully utilize the VNF instance resources in the network architecture. Provide resource utilization.
  • the lifecycle management method of the network service provided by the embodiment of the present invention can be applied to the network architecture shown in FIG. 1.
  • the method provided in Embodiment 1 of the present invention is a lifecycle management method for instantiating an NS.
  • the method provided in Embodiment 2 of the present invention is a lifecycle management method for performing network connection on an instantiated VNF instance.
  • the first device in the embodiment of the present invention is a device that receives a life management request, that is, a device that runs MANO in FIG. 1 , and the first device includes a virtual network function management entity and a network function virtualization scheduling entity.
  • the second device in the embodiment of the present invention is a life tube
  • the requested device is the device running OSS/BSS in Figure 1.
  • FIG. 2 is a schematic flowchart diagram of a lifecycle management method for a network service according to Embodiment 1 of the present invention. As shown in FIG. 2, the method provided in Embodiment 1 of the present invention may include the following contents of 101-104.
  • the second device determines, according to the lifecycle management requirement information, an existing virtual network function VNF instance required for the target NS to perform lifecycle management.
  • VNF instances there are some instantiated VNF instances. These instantiated VNF instances may be obtained by pre-requesting MANO instantiation, or may be other VNF instances retained when the NS is released. It may also be a reusable VNF instance in other instantiated NSs in the network architecture.
  • An instantiated VNF instance can be instantiated by MANO according to the instance requirement information of the VNF, and then the instantiation information of an instantiated VNF instance is instantiated according to which demand information, including the virtual network function descriptor VNFD, VNFD is a template used by vendors to deploy virtual network functions.
  • VNFD includes multiple deployment flavors.
  • a VNFD can instantiate multiple VNF instances according to different deployment specifications.
  • a VNFD can also be instantiated according to the same deployment specification. Multiple VNF instances. Both the first device and the second device can obtain their corresponding instantiation information according to the instantiated VNF instances.
  • the second device is a device that initiates a lifecycle management request.
  • the life management request is used to instantiate the NS.
  • Instantiation is to turn a class into an actual example.
  • the instantiation of NS instantiates the actual existence of a network service instance with certain functions, and the instantiation of the VNF is instantiated.
  • An existing virtual network function instance with a certain function, multiple virtual network function instances can be combined to implement a network service instance, and the NS instantiation is actually instantiating multiple VNFs required for implementing NS and multiple VNF instances. Connection.
  • the second device determines the target according to the lifecycle management requirement information.
  • NS performs an existing VNF instance required for lifecycle management.
  • the target NS is the NS to be instantiated, and the existing VNF instance required for the lifecycle management of the target NS is the instantiated VNF instance already existing in the network architecture shown in FIG.
  • One or more of them for implementing instantiation of the target NS, the existing VNF instance The exact amount depends on the specific situation.
  • the lifecycle requirement information is used to determine an NS to be instantiated, that is, the target NS, and the lifecycle management request is further used to determine a target NSD of the target NS, that is, a network service description of the target NS, a network.
  • a service descriptor is a template used by a vendor to deploy a network service.
  • An NSD includes multiple VNFDs.
  • a VNFD includes multiple deployment specifications. The VNFD and deployment specifications are used as instance requirement information. Then an NSD includes multiple VNF instance requirement information.
  • the second device determines a plurality of VNF instance requirement information required by the target NSD according to the target NSD.
  • the second device determines, according to the multiple VNF instance requirement information required by the target NSD, the existing VNF instance required for the lifecycle management of the target NS.
  • the second device matches the instantiation information corresponding to the VNF instance that is instantiated in the network architecture with the multiple VNF instance requirement information required by the target NSD, and if there is a matching VNF instantiation information, the matching is performed.
  • the instantiated VNF instance corresponding to the successful VNF instantiation information determines an existing VNF instance required for lifecycle management of the target NS.
  • the embodiment of the present invention adds a feature parameter for identifying VNF instance requirement information in the Constituent VNF IE architecture under the service deployment flaver structure in the target NSD, that is, adding a Constituent VNF ID to the nsd:service_deployment_flavour:constituent VNF.
  • a feature parameter for identifying VNF instance requirement information in the Constituent VNF IE architecture under the service deployment flaver structure in the target NSD that is, adding a Constituent VNF ID to the nsd:service_deployment_flavour:constituent VNF.
  • FIG. 3 it is a basic component of the VNF provided by the embodiment of the present invention.
  • the basic constituent elements of the VNF in the prior art do not include the constraint_vnf_id in the table shown in FIG. 3.
  • the Constituent VNF ID is unique in its own NSD, that is, a Constituent VNF ID is used to identify a unique VNF instance requirement information. Referring to FIG.
  • the Constituent VNF ID is the feature parameter
  • the VNFD ID is the identifier of the virtual network function descriptor
  • the VNF deployment flavor ID is the deployment specification.
  • the VNFD ID and the VNF deployment flavor ID may represent a VNF instance requirement information, and thus, each instance requirement information in the plurality of VNF instance requirement information required by the target NSD corresponds to one feature parameter.
  • FIG. 4 does not exist in practical applications. The data in FIG. 4 is merely a simple example, and FIG. 4 is used to facilitate the reader to understand the relationship between the characteristic parameters and other parameters.
  • the characteristic parameter is an identifier parameter in the NSD that is marked by the NSD provider for the plurality of VNF instance requirement information required by the NSD; or the plurality of VNF instance requirements required by the second device for the NSD
  • the tag parameter for which the information is tagged is an identifier parameter in the NSD that is marked by the NSD provider for the plurality of VNF instance requirement information required by the NSD; or the plurality of VNF instance requirements required by the second device for the NSD.
  • the feature parameter is used to identify VNF instance requirement information including the virtual network function descriptor VNFD and the deployment specification in the target NSD, that is, as shown in FIG. 4, different VNFs are implemented.
  • the case requirement information corresponds to a unique feature parameter.
  • the feature parameter is used to identify VNF instance requirement information including the virtual network function descriptor, the deployment specification, and the instance parameter in the target NSD, that is, adding a column of the Instance ID, that is, the instance parameter, on the basis of FIG. 4,
  • the instance parameters are used to identify different virtual network function descriptors and different VNF instance requirement information under the same deployment specification.
  • the second row and the third row in FIG. 4 have the same VNFD ID and VNF deployment flavor ID, but the two are different VNF instance requirement information, so the instance parameters are used to distinguish the two, and the Instance ID of the second row is 1.
  • the Instance ID of the second line is 2.
  • the second device determines that the target NS performs an existing VNF instance required for lifecycle management
  • the second device according to the instantiation information of the existing VNF instance and the The plurality of VNF instance requirement information required by the target NSD determines an identifier of the existing VNF instance and a feature parameter corresponding thereto, that is, the second device uses the instantiation information of the existing VNF instance and the target NSD
  • the required VNF instance requirement information is matched, and then the identifier of the existing VNF instance and the corresponding feature parameter are determined.
  • the identifier of the existing VNF instance is obtained by marking, by the second device, the existing VNF instance, or the identifier of the existing VNF instance is that the first device marks the existing VNF instance.
  • the identifier of the existing VNF instance and its corresponding feature parameter are determined. If the number of the existing VNF instances is greater than one, determine the identifier of each existing VNF instance, and determine the feature parameters corresponding to the identifier of each existing VNF.
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request includes a mapping relationship between the identifier of the existing VNF instance and a feature parameter corresponding thereto.
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS.
  • the lifecycle management request includes a mapping relationship between the identifier of the existing VNF instance and the corresponding feature parameter. It can be understood that the identifier of the existing VNF instance and its corresponding feature parameter appear in pairs. That is, an identifier of an existing VNF instance corresponds to a feature parameter, and an identifier of an existing VNF instance corresponds to a Constituent VNF ID, and a mapping relationship is a correspondence between an identifier of an existing VNF instance and a corresponding Constituent VNF ID.
  • VNF instance ID the mapping relationship at this time can be expressed as VNF instance ID.
  • VNF ID 1 the lifecycle management request includes multiple mapping relationships.
  • the lifecycle management request further includes an identifier of the target NSD, where the identifier of the target NSD is used by the first device to search for the target NSD according to the identifier of the target NSD, thereby performing lifecycle management.
  • the lifecycle management request includes only the identifier of the target NSD. Therefore, the first device can only instantiate the target NS according to the identifier of the target NSD, reducing the processing efficiency of the instantiation, and wasting the instantiated in the network architecture. VNF instance resource.
  • the first device receives a lifecycle management request of the target NS sent by the second device.
  • the first device is a device that runs the MANO in FIG. 1, and the first device includes a virtual infrastructure management entity VIM, a virtual network function management entity VNFM, and a network function virtualization scheduling entity NFVO.
  • the NFVO receives the lifecycle management request of the target NS sent by the second device, and searches for the target NSD according to the identifier of the target NSD.
  • the NFVO stores instantiation information for multiple NSDs and multiple instantiated VNF instances.
  • the first device performs lifecycle management on the target NS according to the existing VNF instance and the mapping relationship.
  • the first device performs lifecycle management on the target NS according to the existing VNF instance and the mapping relationship, that is, instantiates the target NS.
  • the first device may obtain the plurality of VNF instance requirement information required to obtain the target NSD according to the target NSD, and the first device may obtain the information from the first device or the second device. There is no limit here.
  • the NFVO in the first device analyzes the obtained VNF instance requirement information in the target NSD, for example, if the first VNF instance requirement information is VNFD ID 1+VNF deployment flavor ID 1, corresponding If the characteristic parameter Constituent VNF ID is 1, the NFVO detects whether the mapping relationship of the Constituent VNF ID is 1 in the lifecycle management request.
  • the NFVO sends an instantiation request to the VNFM, the instantiation request includes a VNFD ID 1+VNF deployment flavor ID 1, and the instantiation request is used to request the VNFM to generate a VNF according to the VNFD ID 1+VNF deployment flavor ID 1.
  • Example 1 the VNFM receives the instantiation and generates VNF instance 1 according to VNFD ID 1+VNF deployment flavor ID 1 and VNF instance 1 is fed back to NFVO. If yes, NFVO directly obtains an existing VNF instance that has a mapping relationship with the Constituent VNF ID of 1. There is no need to send an instantiation request to the VNFM.
  • the prerequisite for performing this step is that the existing VNF instance exists on the NFVO side, otherwise the NFVO is still An instantiation request needs to be sent to the VNFM. And so on, until the first device completes instantiation of multiple VNF instance requirement information required for the target NSD, thereby completing instantiation of the target NS by the first device.
  • the first device feeds back multiple instantiated VNF instances to the second device, so that the second device is Determine the existing VNF instances required for this lifecycle management before initiating a lifecycle management request.
  • the second device determines the existing VNF instance required for the lifecycle management of the target NS according to the target NS, and sends a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to indicate
  • the first device performs lifecycle management on the target NS
  • the lifecycle management request includes a mapping relationship between the identifier of the existing VNF instance and the corresponding feature parameter, and the feature parameter is a plurality of VNF instances required for the target NSD in the target NSD.
  • the identifier of each VNF instance requirement information tag in the requirement information the first device receives the lifecycle management request of the target NS sent by the second device, and performs lifecycle management on the target NS according to the existing VNF instance and the mapping relationship, thereby implementing The first device performs lifecycle management on the NS according to the existing VNF instance and the mapping relationship in the lifecycle management request sent by the second device, improves the processing efficiency of the lifecycle management, and improves the resource utilization.
  • FIG. 5 is a schematic flowchart of a lifecycle management method for a network service according to Embodiment 2 of the present invention. As shown in FIG. 5, the method provided in Embodiment 2 of the present invention may include the following contents of 201-204.
  • the second device determines, according to the lifecycle management requirement information, an identifier of the target NSD for the lifecycle management of the target NS.
  • the second device is a device that initiates a lifecycle management request.
  • the life management request is used to perform network connection on multiple VNF instances obtained by instantiation. Determining, by the second device, the identifier of the target NSD for the lifecycle management of the target NS according to the lifecycle management requirement information, where the lifecycle requirement information is used to determine the NS to which the multiple VNF instances to be connected belong, that is, the The target NS is used, and the lifecycle management request is further used to determine a target NSD of the target NS, that is, a network service description of the target NS.
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request includes an identifier of the target NSD.
  • the second device sends a lifecycle management request of the target NS to the first device, where the lifecycle management request is used to indicate the A device performs lifecycle management on the target NS, the lifecycle management request includes an identifier of the target NSD, and the target NSD includes a target VNF Forward Graph Descriptor (VNFFGD), the target VNFFGD And including characteristic parameters of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD.
  • VNFFGD target VNF Forward Graph Descriptor
  • the VNF forwarding map descriptor corresponding to the plurality of NSDs exists on both ends of the second device and the first device, because a plurality of NSDs are stored in the second device and the first device.
  • the first device receives a lifecycle management request of a target NS sent by the second device.
  • the first device is a device that runs the MANO in FIG. 1, and the first device includes a virtual infrastructure management entity VIM, a virtual network function management entity VNFM, and a network function virtualization scheduling entity NFVO.
  • the NFVO receives the lifecycle management request of the target NS sent by the second device, and searches for the target NSD according to the identifier of the target NSD.
  • the NFVO stores instantiation information for multiple NSDs and multiple instantiated VNF instances.
  • the first device acquires the target VNFFGD according to the identifier of the target NSD.
  • the NFVO in the first device searches for the target NSD according to the identifier of the target NSD, and acquires the target VNFFGD of the target NSD that is found, where the target VNFFGD includes the target NSD.
  • the NFVO acquires, from the second device, a feature parameter of each VNF instance requirement information in the plurality of VNF instance requirement information required by the target NSD, where the second device sends the lifecycle management request And characterizing each VNF instance requirement information in the plurality of VNF instance requirement information required by the target NSD according to the identifier of the target NSD.
  • each of the plurality of VNF instance requirement information required by the NFVO for the target NSD is respectively marked with a feature parameter.
  • the feature parameter is used to identify VNF instance requirement information including the virtual network function descriptor VNFD and the deployment specification in the target NSD.
  • the feature parameter is used to identify VNF instance requirement information including a virtual network function descriptor, a deployment specification, and an instance parameter in the target NSD, where the instance parameter is used to identify the same virtual network function descriptor and the same deployment.
  • VNF instance requirements information under specifications.
  • the first device performs lifecycle management on the target NS according to a feature parameter of each VNF requirement information in the target VNFFGD.
  • the NFVO in the first device performs lifecycle management on the target NS according to a characteristic parameter of each VNF requirement information in the target VNFFGD, that is, according to each VNF requirement information in the target VNFFGD.
  • the feature parameter performs network connection on the plurality of VNF instances obtained by instantiating the target NS.
  • the first device instantiates a plurality of VNF instances according to the plurality of VNF instance requirement information required by the target NSD, and then the NFVO pairs the plurality of VNFs according to a characteristic parameter of each VNF requirement information in the target VNFFGD.
  • the instance makes a network connection.
  • a bold portion in the fifth row of FIG. 6 includes a feature parameter Constituent VNF ID, which is used to indicate that the NFVO performs a network connection between VNF instances according to the feature parameter. Or a network connection between a VNF instance and a Physical Network Function (PNF) instance.
  • the bold portion of FIG. 6 is nsd/vnfd/pnfd:connection_point: id.
  • the identifier of the target NSD for the lifecycle management of the target NS is determined by the second device according to the lifecycle management requirement information, and the lifecycle management request of the target NS is sent to the first device, where the lifecycle management request includes the target.
  • the identifier of the NSD, the target NSD includes the target VNFFGD, and the target VNFFGD includes the feature parameters of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD, and the first device receives the target NS sent by the second device.
  • the lifecycle management request acquires the target VNFFGD according to the identifier of the target NSD, and performs lifecycle management on the target NS according to the characteristic parameter of each VNF requirement information in the target VNFFGD, so that the network connection between the VNF instances can be explicitly indicated.
  • FIG. 7 is a schematic structural diagram of a first device according to an embodiment of the present invention.
  • the first device provided by the embodiment corresponding to FIG. 7 is the device for initiating a lifecycle management request provided by the first embodiment.
  • the first device 70 includes a receiving unit 701 and a management unit 702.
  • the receiving unit 701 is configured to receive a lifecycle tube of the target network service NS sent by the second device.
  • the request, the lifecycle management request includes a mapping relationship between an identifier of the existing virtual network function VNF instance and a feature parameter corresponding thereto, where the feature parameter is required for the target NSD in the target network service descriptor NSD
  • the identification parameter of each VNF instance requirement information tag in the multiple VNF instance requirement information.
  • the management unit 702 is configured to perform lifecycle management on the target NS according to the existing VNF instance and the mapping relationship.
  • the management unit 702 includes a matching unit, an obtaining unit, and an instantiation unit, which are not indicated in FIG.
  • a matching unit configured to match the mapping relationship with a feature parameter of each VNF instance requirement information in the plurality of VNF instance requirement information required by the target NSD.
  • the obtaining unit is configured to obtain an existing VNF instance corresponding to the matching feature parameter.
  • An instantiation unit is configured to instantiate VNF instance requirement information corresponding to the feature parameter that fails to match.
  • FIG. 8 is a schematic structural diagram of a second device according to an embodiment of the present invention.
  • the second device provided by the embodiment corresponding to FIG. 8 is the device for receiving the lifecycle management request provided by the first embodiment.
  • the second device 80 includes a determining unit 801 and a transmitting unit 802.
  • the determining unit 801 is configured to determine, according to the lifecycle management requirement information, an existing VNF instance required for the target NS to perform lifecycle management.
  • the sending unit 802 is configured to send, to the first device, a lifecycle management request of the target NS, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management
  • the request includes a mapping relationship between the identifier of the existing VNF instance and a feature parameter corresponding thereto, where the feature parameter is each VNF of the plurality of VNF instance requirement information required for the target NSD in the target NSD.
  • the identification parameter of the instance requirement information tag is configured to send, to the first device, a lifecycle management request of the target NS, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management
  • the request includes a mapping relationship between the identifier of the existing VNF instance and a feature parameter corresponding thereto, where the feature parameter is each VNF of the plurality of VNF instance requirement information required for the target NSD in the target NSD.
  • the identification parameter of the instance requirement information tag is configured to send,
  • the determining unit 801 is specifically configured to determine, according to the lifecycle management requirement information, an existing VNF instance and a target NSD required for the lifecycle management of the target NS, where the target NSD is a descriptor of the target NS, and according to the existing The instantiation information of the VNF instance and the plurality of VNF instance requirement information required by the target NSD determine an identifier of the existing VNF instance and a feature parameter corresponding thereto.
  • the first device shown in FIG. 7 and the second device shown in FIG. 8 are used to implement the lifecycle management method for the network service according to the first embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of another first device according to an embodiment of the present invention.
  • the first device provided by the embodiment corresponding to FIG. 9 is the device for initiating a lifecycle management request provided by the second embodiment.
  • the second device 90 includes a receiving unit 901, an obtaining unit 902, and a management unit 903.
  • the receiving unit 901 is configured to receive a lifecycle management request of the target NS sent by the second device, where the lifecycle management request includes an identifier of the target NSD, where the target NSD includes a target virtual network function forwarding map descriptor VNFFGD, the target VNFFGD And including characteristic parameters of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD.
  • the obtaining unit 902 is configured to acquire the target VNFFGD according to the identifier of the target NSD.
  • the management unit 903 is configured to perform lifecycle management on the NS according to a feature parameter of each VNF requirement information in the target VNFFGD.
  • the management unit 903 includes an instantiation unit and a connection unit, which are not indicated in FIG.
  • An instantiation unit configured to instantiate a plurality of VNF instances according to the plurality of VNF instance requirement information required by the target NSD.
  • a connecting unit configured to perform network connection on the plurality of VNF instances according to a characteristic parameter of each VNF requirement information in the target VNFFGD.
  • FIG. 10 is a schematic structural diagram of another second device according to an embodiment of the present invention.
  • the second device provided in the corresponding embodiment of FIG. 10 is the device for receiving the lifecycle management request provided by the second embodiment.
  • the second device 100 includes a determining unit 1001 and a transmitting unit 1002.
  • the determining unit 1001 is configured to determine, according to the lifecycle management requirement information, an identifier of the target NSD for the lifecycle management of the target NS.
  • the sending unit 1002 is configured to send, to the first device, a lifecycle management request of the target NS, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management request includes An identifier of the target NSD, the target NSD includes a target VNFFGD, and the target VNFFGD includes a feature parameter of each VNF instance requirement information in the plurality of virtual network function VNF instance requirement information required by the target NSD.
  • the first device shown in FIG. 9 and the second device shown in FIG. 10 are used to implement the lifecycle management method for the network service according to the second embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of still another first device according to an embodiment of the present invention.
  • the first device includes a memory 1101, a communication bus 1102, a network function virtualization scheduling entity NFVO 1103, and a virtual network function management entity VNFM 1104.
  • the communication bus 1102 is used to implement connection communication between these components.
  • the memory 1101 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.
  • a set of program codes is stored in the memory 1101, and the NFVO 1103 or VNFM 1104 calls the program code stored in the memory 1101 to execute computer instructions, thereby implementing the embodiment shown in FIG. 2 or 3.
  • the NFVO 1103 is configured to receive a lifecycle management request sent by the second device, and find a target NSD according to the lifecycle management request, and analyze multiple VNF instance requirement information required by the target NSD, and then according to the lifecycle management request.
  • the existing VNF instance and mapping relationship in the middle sends an instantiation request to the VNFM 1104.
  • the VNFM 1104 is configured to receive an instantiation request sent by the NFVO 1103 and generate a required VNF instance according to the instantiation request. After the VNFM 1104 completes the generation of all VNF instances required for the target NS, the VNFM 1104 stores the generated instantiation information of the VNF instance in the memory 1101, or places the generated VNF instance in the first device and the second device. In the network architecture formed by the device.
  • the NFVO 1103 is also used to make a network connection to the VNFM 1104 generating VNF instance, and the network connection includes a connection between the VNF instances and a connection between the VNF instance and the PNF.
  • the first device can improve the processing efficiency of the lifecycle management and improve the utilization of the VNF instance.
  • FIG. 12 is a schematic structural diagram of still another second device according to an embodiment of the present invention.
  • the second device includes at least one processor 1201, such as a CPU, at least one communication bus 1202, a communication interface 1203, an input device 1204, an output device 1205, and a memory 1206.
  • the communication bus 1202 is used to implement connection communication between these components.
  • Communication interface 1203 is used to communicate with other devices.
  • the memory 1206 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.
  • a set of program codes is stored in the memory 1206, and the processor 1201 calls the program stored in the memory 1101. The code can execute computer instructions to implement the embodiment shown in Figure 2 or Figure 3.
  • the processor 1201 controls when the output device 1205 outputs a lifecycle management request, and controls which NS lifecycle management request is output by the output device 1205.
  • the processor 1201 determines an existing VNF instance required for the lifecycle management of the target NS; an identification parameter of each VNF instance requirement information tag in the plurality of VNF instance requirement information required for the target NSD; according to the existing VNF instance Determining the information and the plurality of VNF instance requirement information required by the target NSD, determining an identifier of the existing VNF instance and a feature parameter corresponding thereto, and determining, according to the lifecycle management requirement information, the target NNS for the target NSD of the lifecycle management Logo.
  • the output device 1205 sends a lifecycle management request to the first device, where the lifecycle management request is used to instruct the first device to perform lifecycle management on the target NS, where the lifecycle management request includes the existing VNF instance
  • the lifecycle management request also includes an identification of the target NSD.
  • the second device needs to mark the feature parameters of the plurality of VNF instance requirements information required by the NSD to facilitate the second device and the first device to identify.
  • the embodiment of the present invention further provides a network service lifecycle management system, including the first device shown in FIG. 11 and the second device shown in FIG. 12, that is, the lifecycle management system includes the first device shown in FIG. The device and the second device shown in FIG. 8, and/or the first device shown in FIG. 9 and the second device shown in FIG.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • the computer readable medium may include a random access memory (RAM), a read-only memory (ROM), and an electrically erasable programmable read-only memory (Electrically Erasable Programmable).
  • EEPROM Electrically Error Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • Any connection may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, Then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the associated medium.
  • DSL Digital Subscriber Line
  • a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

一种网络服务的生命周期管理方法及设备，其中方法包括：第二设备根据目标NS确定所述目标NS进行生命周期管理所需的已存在VNF实例；所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，所述第一设备接收所述第二设备发送的所述目标NS的生命周期管理请求，并根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。本发明实施例能够提高生命周期管理的处理效率，提高资源的利用率。

Description

一种网络服务的生命周期管理方法及设备 技术领域
本发明涉及网络功能虚拟化技术领域，尤其涉及一种网络服务的生命周期管理方法及设备。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)技术将一台计算机虚拟为多台虚拟逻辑计算机，即虚拟机(Virtual Machine，VM)。NFV技术通过借用信息技术(Information Technology，IT)的虚拟化技术，使得许多类型的网络设备可以合并到工业标准中，例如：服务、交换、存储等可以部署在数据中心或者网络节点中。NFV技术将各种网络功能以软件方式实现，并能在工业标准的服务器上运行，还能根据需要进行迁移、实例化、以及重新部署等等，并且不需要安装新的设备，便可产生虚拟网络功能(Virtualized Network Function，VNF)。多个VNF之间可以实现网络服务(Network Service，NS)。
网络业务描述符(Network Service Descriptor，NSD)是厂商用来部署网络业务的模板，一个NSD包括多个虚拟网络功能描述符(Virtualized Network Function Descriptor，VNFD)和多个部署规格，VNFD是厂商用来部署虚拟网络功能的模板，一个VNFD根据不同的部署规格可以实例化多个VNF，一个VNFD根据同一个部署规格也可以实例化多个VNF。
实例化一个NS的过程为：运营支撑系统(Operations Support System，OSS)请求网络功能虚拟化管理实体(NFV Orchestrator，NFVO)根据指定的NSD实例化一个NS；NFVO在接收到请求时，查找指定的NSD，并通过分析该NSD下的多个VNFD和多个部署规格之间的对应关系，实例化出多个VNF，并建立多个VNF之间的连接。然而,现有的实例化处理的效率和资源的利用率低。
发明内容
本发明实施例提供了一种网络服务的生命周期管理方法及设备，能够提高生命周期管理的处理效率，提高资源的利用率。
本发明实施例第一方面提供一种网络服务的生命周期管理方法，包括：
第一设备接收第二设备发送的目标网络服务NS的生命周期管理请求，所述生命周期管理请求包括已存在虚拟网络功能VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为目标网络服务描述符NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数；
所述第一设备根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
在可能实现的方式中，所述生命周期管理请求还包括所述目标NSD的标识。
在可能实现的方式中，所述已存在VNF实例的标识及与其对应的特征参数由所述第二设备根据所述已存在VNF实例的实例信息以及所述目标NSD所需的多个VNF实例需求信息确定。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
在可能实现的方式中，所述第一设备将所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息的特征参数与所述生命管理请求包括的映射关系进行匹配，分别获取匹配成功的特征参数和匹配失败的特征参数；
所述第一设备直接获取匹配成功的特征参数对应的已存在VNF实例；
所述第一设备对匹配失败的特征参数对应的VNF实例需求信息进行实例化，从而充分利用网络架构中已实例化的VNF实例，减少对某些VNF实例需求信息重复实例化的过程，提高实例化的处理效率。
本发明实施例第二方面提供另一种网络服务的生命周期管理方法，包括：
第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例；
所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所 述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为所述目标NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
在可能实现的方式中，生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例以及目标NSD，所述目标NSD为目标NS的描述符；
所述第二设备根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数。
在可能实现的方式中，所述生命周期管理请求还包括所述目标NSD的标识。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
本发明实施例第三方面提供又一种网络服务的生命周期管理方法，包括：
第一设备接收第二设备发送的目标NS的生命周期管理请求，所述生命周期管理请求包括目标NSD的标识，所述目标NSD包括目标虚拟网络功能转发图描述符VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数；
所述第一设备根据所述目标NSD的标识获取所述目标VNFFGD；
所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理。
在可能实现的方式中，所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理，即所述第一设备根据所述目标VNFFGD中的每个VNF实例需求信息的特征参数对所述目标NS实例化得到的多个VNF实例进行网络连接：
所述第一设备根据所述目标NSD所需的多个VNF实例需求信息实例化得 到多个VNF实例，并根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述多个VNF实例进行网络连接。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
在可能实现的方式中，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
本发明实施例第四方面提供又一种网络服务的生命周期管理方法，包括：
第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识；
所述第二设备向第一设备发送目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述目标NSD的标识，所述目标NSD包括目标VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。
本发明实施例第五方面提供一种第一设备，包括：
接收单元，用于接收第二设备发送的目标网络服务NS的生命周期管理请求，所述生命周期管理请求包括已存在虚拟网络功能VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为目标网络服务描述符NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数；
管理单元，用于根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
本发明实施例第五方面提供的第一设备用于实现本发明实施例第一方面所述的第一设备，具体实现过程可参见第一方面的描述，在此不再赘述。
本发明实施例第六方面提供一种第二设备，包括：
确定单元，用于根据生命周期管理需求信息确定所述目标NS进行生命周期管理所需的已存在VNF实例；
发送单元，用于向第一设备发送所述目标NS的生命周期管理请求，所述 生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述已存在VNF实例的标识及其对应的特征参数之间的映射关系，所述特征参数为所述目标NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
本发明实施例第六方面提供的第二设备用于实现本发明实施例第二方面所述的第二设备，具体实现过程可参见第二方面的描述，在此不再赘述。
本发明实施例第七方面提供另一种第一设备，包括：
接收单元，用接收第二设备发送的目标NS的生命周期管理请求，所述生命周期管理请求包括目标NSD的标识，所述目标NSD包括虚拟网络功能转发图描述符VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数；
获取单元，用于根据所述目标NSD的标识获取所述目标VNFFGD；
管理单元，用于根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述NS进行生命周期管理。
本发明实施例第七方面提供的第一设备用于实现本发明实施例第三方面所述的第一设备，具体实现过程可参见第三方面的描述，在此不再赘述。
本发明实施例第八方面提供另一种第一设备，包括：
确定单元，用于根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识；
发送单元，用于向第一设备发送目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述目标NSD的标识，所述目标NSD包括目标VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。
本发明实施例第八方面提供的第二设备用于实现本发明实施例第四方面所述的第二设备，具体实现过程可参见第四方面的描述，在此不再赘述。
本发明实施例第九方面提供一种网络服务的生命周期管理系统，包括第五方面所述的第一设备以及第六方面所述的第二设备，和/或包括第七方面所述的第一设备以及第八方面所述的第二设备。
在本发明实施中，通过第二设备根据目标NS确定目标NS进行生命周期 管理所需的已存在VNF实例，并向第一设备发送目标NS的生命周期管理请求，生命周期管理请求用于指示第一设备对目标NS进行生命周期管理，生命周期管理请求包括已存在VNF实例的标识及与其对应的特征参数之间的映射关系，特征参数为目标NSD中对目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数，第一设备接收第二设备发送的目标NS的生命周期管理请求，并根据已存在VNF实例以及映射关系对目标NS进行生命周期管理，从而实现第一设备根据第二设备发送的生命周期管理请求中的已存在VNF实例和映射关系对NS进行生命周期管理，提高生命周期管理的处理效率，提高资源的利用率。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为网络功能虚拟化NFV的网络架构示意图；
图2为本发明实施例一提供的网络服务的生命周期管理方法的流程示意图；
图3为本发明实施例提供的VNF的基本组成元素；
图4为本发明实施例提供的特征参数与其它参数的对应关系列表；
图5为本发明实施例二提供的网络服务的生命周期管理方法的流程示意图；
图6为本发明实施例提供的VNFFGD的基本元素；
图7为本发明实施例提供的一种第一设备的结构示意图；
图8为本发明实施例提供的一种第二设备的结构示意图；
图9为本发明实施例提供的另一种第一设备的结构示意图；
图10为本发明实施例提供的另一种第二设备的结构示意图；
图11为本发明实施例提供的又一种第一设备的结构示意图；
图12为本发明实施例提供的又一种第二设备的结构示意图。
具体实施方式
本发明实施例提供的一种网络服务的生命周期管理方法、设备及系统，可以应用于网络功能虚拟化NFV网络中对网络服务NS进行生命周期管理的场景中。
请参见图1，为网络功能虚拟化NFV的网络架构示意图。从纵向看，NFV网络分为三层：基础设施层(NFV Infrastructure，NFVI)、虚拟网络层(Virtual Network Function，VNF)和管理层。其中，基础设施层，从云计算的角度看，就是一个资源池。NFVI映射到物理基础设施就是多个地理上分散的数据中心，通过高速通信网连接起来。NFVI需要将物理计算/存储/交换资源通过虚拟化转换为虚拟的计算/存储/交换资源池。虚拟网络层包括多个VNF网元，未在图1中标明多个。虚拟网络层对应的就是目前各个电信网络服务，每个物理网元映射为一个虚拟网络功能网元VNF，VNF所需资源需要分解为虚拟的计算/存储/交换资源，由NFVI来承载，VNF之间的接口依然采用传统网络定义的信令接口。多个VNF可以实现一个网络服务NS。管理层包括运营支撑层(Operation/Business Support System，OSS/BSS)和网元管理(Element Manager，EM)。EM用于对部分VNF网元进行管理。运营支撑层为目前的OSS/BSS系统，是电信运营商的一体化、信息资源共享的支持系统，它主要由网络管理、系统管理、计费、营业、账务和客户服务等部分组成，系统间通过统一的信息总线有机整合在一起。它不仅能在帮助运营商制订符合自身特点的运营支撑系统的同时帮助确定系统的发展方向，还能帮助用户制订系统的整合标准，改善和提高用户的服务水平。OSS为业务支撑系统，BSS为运营支撑系统，OSS/BSS系统在NFV网络架构中为虚拟化进行必要的修改和调整。从横向看，NFV网络分为网络服务域和资源管理编排域。其中，网络服务域，就是目前的各电信网络服务，即为包括OSS/BSS、EM、VNF和NFVI。资源管理编排域(Management and Orchestration，MANO)负责对整个NFVI资源的管理和编排，负责网络服务和NFVI资源的映射和关联，负责OSS业务资源流程的实施等。MANO包括虚拟基础设施管理实体(Virtualised Infrastructure Manager，VIM)、虚拟网络功能管理实体(VNF Manager，VNFM)和网络功能虚拟化调度实体(NFV Orchestrator，NFVO)，未在图1中标明，三者在MANO的结构中从上自下为NFVO、VNFM、VIM。其中，VIM负责虚拟化基础设施的管理。主 要功能包括：采集硬件资源和虚拟资源的状态信息并上报给VNFM，实现资源监测、故障监测和上报；接受来自VNFM的上层应用请求并进行认证，认证通过后，通过控制虚拟机管理器来执行上层应用请求，实现资源的迁移和弹性伸缩。VNFM负责VNF的生命周期管理及其资源使用情况的监控。具体包括VNF的实例化、添加、删除、更改、查询、扩容/缩容、预留以及VNF所占用资源的动态监控等。NFVO负责基础设施和虚拟化网络功能VNF的管理和编排，进而实现完整的网络服务。
图1中的OSS/BSS可向MANO发送生命周期管理请求，该生命周期管理请求可用于请求MANO对某个网络服务NS进行实例化，也可用于请求MANO对实例化得到的多个VNF进行网络连接，还可用于请求MANO对某个网络服务NS进行更新，等等。以生命周期管理请求用于请求MANO对某个NS进行实例化为例，该生命周期管理请求包括指定NSD的标识，MANO接收到该生命周期管理请求时，根据指定NSD的标识查找指定的NSD，然后对指定的NSD进行分析，分析指定的NSD下有哪些VNF实例需求信息，并根据这些VNF实例需求信息实例化出多个VNF实例，从而实现对该NS的实例化。但是，在OSS/BSS和MANO构成的网络架构中存在一些已实例化的VNF实例，并且这些已实例化的VNF实例中有些已实例化的VNF实例与指定的NSD所需的某些VNF实例需求信息匹配，MANO可以直接使用这些已实例化的VNF实例进行该NS的实例化，但是MANO依然按照上述流程执行对该NS的实例化，不仅降低实例化处理的效率，而且浪费网络架构中的已实例化的VNF实例资源。
为了解决现有技术中实例化处理效率低下、浪费资源的问题，本发明实施例提供的网络服务的生命周期管理方法，能够提高生命周期管理的处理效率，并充分利用网络架构中的VNF实例资源，提供资源的利用率。
本发明实施例提供的网络服务的生命周期管理方法可应用于图1所示的网络架构中。本发明实施例一提供的方法是用于对NS进行实例化的生命周期管理方法。本发明实施例二提供的方法是用于对已实例化的VNF实例进行网络连接的生命周期管理方法。本发明实施例中的第一设备为接收生命管理请求的设备，即为图1中运行MANO的设备，所述第一设备包括虚拟网络功能管理实体和网络功能虚拟化调度实体。本发明实施例中的第二设备为发起生命管 理请求的设备，即为图1中运行OSS/BSS的设备。
下面将结合图2和图3，对本发明实施例提供的网络服务的生命周期管理方法进行详细的介绍。
图2为本发明实施例一提供的网络服务的生命周期管理方法的流程示意图。如图2所示，本发明实施例一提供的方法可以包括下述101-104的内容。
101，第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在虚拟网络功能VNF实例。
具体的，在图1所示的网络架构中存在一些已实例化的VNF实例，这些已实例化的VNF实例可能是预先请求MANO实例化得到的，也可能是其它释放NS时保留的VNF实例，还可能是网络架构中其它已实例化的NS中可以重复使用的VNF实例。一个已实例化的VNF实例可由MANO根据该VNF的实例需求信息实例化得到，那么一个已实例化的VNF实例的实例化信息即为根据哪些需求信息进行实例化，包括虚拟网络功能描述符VNFD，VNFD是厂商用来部署虚拟网络功能的模板，VNFD包括多个部署规格(deployment flavor),一个VNFD根据不同的部署规格可以实例化出多个VNF实例，一个VNFD根据同一个部署规格也可以实例化出多个VNF实例。第一设备和第二设备均可根据这些已实例化的VNF实例获取其对应的实例化信息。
第二设备为发起生命周期管理请求的设备，在本发明实施例中所述生命管理请求用于对NS进行实例化。实例化即把一个类变成实际存在的一个例子，在本发明实例中对NS的实例化即实例化出实际存在的具有某种功能的网络服务实例，对VNF的实例化即实例化出实际存在的具有某种功能的虚拟网络功能实例，多个虚拟网络功能实例可以组合实现一个网络服务实例，对NS实例化实际上为对实现NS所需的多个VNF实例化及对多个VNF实例的连接。
由于图1所示的网络架构中已经存在一些已实例化的VNF实例，因此在所述第二设备想要发起所述生命周期管理请求时，所述第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例。其中，所述目标NS即为此次待实例化的NS，所述目标NS进行生命周期管理所需的已存在VNF实例即为图1所示的网络架构中已经存在的已实例化的VNF实例中的一个或多个，用于实现所述目标NS的实例化，所述已存在VNF实例的 具体数量视具体情况而定。所述生命周期需求信息用于确定对待实例化的NS，即所述目标NS，所述生命周期管理请求还用于确定所述目标NS的目标NSD，即所述目标NS的网络服务描述，网络服务描述符是厂商用来部署网络服务的模板，一个NSD包括多个VNFD，一个VNFD又包括多个部署规格，将VNFD和部署规格作为实例需求信息，那么一个NSD包括多个VNF实例需求信息。
所述第二设备根据所述目标NSD确定所述目标NSD所需的多个VNF实例需求信息。所述第二设备根据所述目标NSD所需的多个VNF实例需求信息来确定所述目标NS进行生命周期管理所需的已存在VNF实例。所述第二设备将网络架构中已实例化的VNF实例对应的实例化信息与所述目标NSD所需的多个VNF实例需求信息进行匹配，若存在匹配成功的VNF实例化信息，则将匹配成功的VNF实例化信息对应的已实例化的VNF实例确定为所述目标NS进行生命周期管理所需的已存在VNF实例。
本发明实施例在所述目标NSD中service deployment flaver结构下的Constituent VNF IE架构中增加了用于识别VNF实例需求信息的特征参数，即nsd:service_deployment_flavour:constituent VNF中增加一个Constituent VNF ID。请参见图3，为本发明实施例提供的VNF的基本组成元素，现有技术中的VNF的基本组成元素不包括图3所示表格中的constituent_vnf_id。Constituent VNF ID在所属的NSD中具有唯一性，即一个Constituent VNF ID用于标识唯一一个VNF实例需求信息。请参见图4，为本发明实施例提供的特征参数与其它参数的对应关系列表，Constituent VNF ID即为特征参数，VNFD ID即为虚拟网络功能描述符的标识，VNF deployment flavor ID即为部署规格的标识，VNFD ID和VNF deployment flavor ID可表示一个VNF实例需求信息，由此可见，所述目标NSD所需的多个VNF实例需求信息中每个实例需求信息都对应一个特征参数。需要说明的是，图4在实际应用中并不存在，图4中的数据只是单纯的举例，图4用于方便读者理解特征参数与其它参数之间的关系。所述特征参数为某个NSD中，由NSD提供者对该NSD所需的多个VNF实例需求信息进行标记的标识参数；或者由所述第二设备对该NSD所需的多个VNF实例需求信息进行标记的标记参数。
可选的，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符VNFD和部署规格的VNF实例需求信息，即如图4所示，不同的VNF实 例需求信息对应一个唯一的特征参数。
可选的，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，即在图4的基础上增加一列Instance ID，即实例参数，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。例如，图4中的第二行和第三行VNFD ID相同并且VNF deployment flavor ID，但是两者是不同的VNF实例需求信息，因此用实例参数对两者进行区分，第二行的Instance ID为1，第二行的Instance ID为2。
基于图3和图4，在所述第二设备确定所述目标NS进行生命周期管理所需的已存在VNF实例之后，所述第二设备根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数，即所述第二设备将所述已存在VNF实例的实例化信息与所述目标NSD所需的多个VNF实例需求信息进行匹配，进而确定所述已存在VNF实例的标识及与其对应的特征参数。其中，所述已存在VNF实例的标识为所述第二设备对所述已存在VNF实例进行标记得到的，或者所述已存在VNF实例的标识为第一设备对所述已存在VNF实例进行标记，并将标记后的所述已存在VNF实例反馈至所述第二设备。若所述已存在VNF实例的数量为一个，则确定该已存在VNF实例的标识及其对应的特征参数。若所述已存在VNF实例的数量大于一个，则确定每个已存在VNF实例的标识，并分别确定每个已存在VNF的标识对应的特征参数。
102，所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系。
具体的，所述第二设备向所述第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理。所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，可以理解的是所述已存在VNF实例的标识与其对应的特征参数是成对出现的，即一个已存在VNF实例的标识对应一个特征参数，一个已存在VNF实例的标识对应一个Constituent VNF ID，一个映射关系即为一个已存在VNF实例的标识与其对应的Constituent VNF ID之间的 对应关系。例如，某个已存在VNF实例的标识为1，与其对应的特征参数Constituent VNF ID为1，那么此时的映射关系可表示为VNF instance ID
Figure PCTCN2015099911-appb-000001
VNF ID 1。若存在多个已存在VNF实例，则所述生命周期管理请求包括多个映射关系。
所述生命周期管理请求还包括所述目标NSD的标识，所述目标NSD的标识用于所述第一设备根据所述目标NSD的标识查找所述目标NSD，进而执行生命周期管理。现有技术中，生命周期管理请求只包括目标NSD的标识，因此第一设备只能根据目标NSD的标识对目标NS进行实例化，降低实例化的处理效率，浪费网络架构中的已实例化的VNF实例资源。
103，所述第一设备接收所述第二设备发送的所述目标NS的生命周期管理请求。
具体的，所述第一设备为运行图1中MANO的设备，所述第一设备包括虚拟基础设施管理实体VIM、虚拟网络功能管理实体VNFM和网络功能虚拟化调度实体NFVO。其中，NFVO接收所述第二设备发送的所述目标NS的生命周期管理请求，并根据所述目标NSD的标识查找所述目标NSD。NFVO存储着多个NSD以及多个已实例化的VNF实例的实例化信息。
104，所述第一设备根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
具体的，所述第一设备根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理，即对所述目标NS进行实例化。所述第一设备根据查找到所述目标NSD获取所述目标NSD所需的多个VNF实例需求信息，所述第一设备可从自身的存储器中获取，也可向所述第二设备获取，在此不做限定。所述第一设备中的NFVO依次对获取到的所述目标NSD下的多个VNF实例需求信息进行分析，例如，若第一个VNF实例需求信息为VNFD ID 1+VNF deployment flavor ID 1，对应的特征参数Constituent VNF ID为1，则NFVO检测所述生命周期管理请求中是否存在Constituent VNF ID为1的映射关系。若不存在，则NFVO向VNFM发送实例化请求，所述实例化请求包括VNFD ID 1+VNF deployment flavor ID 1，所述实例化请求用于请求VNFM根据VNFD ID 1+VNF deployment flavor ID 1生成VNF实例1，VNFM接收所述实例化并根据VNFD ID 1+VNF deployment flavor ID 1生成VNF实例1，并将 VNF实例1反馈给NFVO。若存在，则NFVO直接获取与Constituent VNF ID为1具有映射关系的已存在VNF实例，无需向VNFM发送实例化请求，执行此步骤的前提条件是NFVO侧存在所述已存在VNF实例，否则NFVO还需向VNFM发送实例化请求。以此类推，直至所述第一设备完成对所述目标NSD所需的多个VNF实例需求信息的实例化，进而完成所述第一设备对所述目标NS的实例化。
可选的，所述第一设备在完成对所述目标NS的实例化后，所述第一设备将实例化得到的多个VNF实例反馈至所述第二设备，便于所述第二设备在发起生命周期管理请求之前确定此次生命周期管理所需的已存在VNF实例。
在本发明实施例中，通过第二设备根据目标NS确定目标NS进行生命周期管理所需的已存在VNF实例，并向第一设备发送目标NS的生命周期管理请求，生命周期管理请求用于指示第一设备对目标NS进行生命周期管理，生命周期管理请求包括已存在VNF实例的标识及与其对应的特征参数之间的映射关系，特征参数为目标NSD中对目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数，第一设备接收第二设备发送的目标NS的生命周期管理请求，并根据已存在VNF实例以及映射关系对目标NS进行生命周期管理，从而实现第一设备根据第二设备发送的生命周期管理请求中的已存在VNF实例和映射关系对NS进行生命周期管理，提高生命周期管理的处理效率，提高资源的利用率。
图5为本发明实施例二提供的网络服务的生命周期管理方法的流程示意图。如图5所示，本发明实施例二提供的方法可以包括下述201-204的内容。
201，第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识。
具体的，第二设备为发起生命周期管理请求的设备，在本发明实施例中所述生命管理请求用于对实例化得到的多个VNF实例进行网络连接。所述第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识，其中，所述生命周期需求信息用于确定此次待连接的多个VNF实例所属的NS，即所述目标NS，同时所述生命周期管理请求还用于确定所述目标NS的目标NSD，即所述目标NS的网络服务描述。
202，所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求包括所述目标NSD的标识。
具体的，待所述第二设备确定所述目标NSD的标识之后，所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述目标NSD的标识，所述目标NSD包括目标VNF转发图描述符(VNF Forward Graph Descriptor，VNFFGD)，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。由于所述第二设备和所述第一设备两端均存储着多个NSD，因此所述第二设备和所述第一设备两端均存在多个NSD对应的VNF转发图描述符。
203，所述第一设备接收所述第二设备发送的目标NS的生命周期管理请求。
具体的，所述第一设备为运行图1中MANO的设备，所述第一设备包括虚拟基础设施管理实体VIM、虚拟网络功能管理实体VNFM和网络功能虚拟化调度实体NFVO。其中，NFVO接收所述第二设备发送的所述目标NS的生命周期管理请求，并根据所述目标NSD的标识查找所述目标NSD。NFVO存储着多个NSD以及多个已实例化的VNF实例的实例化信息。
204，所述第一设备根据所述目标NSD的标识获取所述目标VNFFGD。
具体的，所述第一设备中的NFVO根据所述目标NSD的标识查找所述目标NSD，并获取查找到的所述目标NSD的所述目标VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。可选的，NFVO向所述第二设备获取所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息的特征参数，所述第二设备在发送所述生命周期管理请求之前，便根据所述目标NSD的标识对所述目标NSD所需的多个VNF实例需求信息中的每个VNF实例需求信息标记了特征参数。可选的，NFVO对所述目标NSD所需的多个VNF实例需求信息中的每个VNF实例需求信息分别标记特征参数。
可选的，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符VNFD和部署规格的VNF实例需求信息。
可选的，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
205，所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理。
具体的，所述第一设备中的NFVO根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理，即根据所述目标VNFFGD中的每个VNF需求信息的特征参数对实例化所述目标NS得到的多个VNF实例进行网络连接。所述第一设备根据所述目标NSD所需的多个VNF实例需求信息实例化得到多个VNF实例，然后NFVO根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述多个VNF实例进行网络连接。
请参见图6，为本发明实施例提供的VNFFGD的基本元素，图6中第5行中加粗的部分包括特征参数Constituent VNF ID，用于指示NFVO根据特征参数进行VNF实例之间的网络连接或者VNF实例与物理网络功能(Physical Network Function，PNF)实例之间的网络连接。现有技术中，图6中弟行加粗的部分为nsd/vnfd/pnfd:connection_point:id，当基于一个VNFD生成多个VNF时，难以指定连接特定VNF实例的连接点。
在本发明实施例中，通过第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识，并向第一设备发送目标NS的生命周期管理请求，生命周期管理请求包括目标NSD的标识，目标NSD包括目标VNFFGD，目标VNFFGD包括目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数，第一设备接收第二设备发送的目标NS的生命周期管理请求，并根据目标NSD的标识获取目标VNFFGD，并根据目标VNFFGD中的每个VNF需求信息的特征参数对目标NS进行生命周期管理，从而能够明确指示VNF实例之间的网络连接。
请参见图7，为本发明实施例提供的一种第一设备的结构示意图。图7对应的实施例提供的第一设备为实施例一提供的用于发起生命周期管理请求的设备。所述第一设备70包括接收单元701和管理单元702。
接收单元701，用于接收第二设备发送的目标网络服务NS的生命周期管 理请求，所述生命周期管理请求包括已存在虚拟网络功能VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为目标网络服务描述符NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
管理单元702，用于根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
所述管理单元702包括匹配单元、获取单元和实例化单元，未在图7中标明。
匹配单元，用于将所述映射关系与所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息的特征参数进行匹配。
获取单元，用于获取匹配成功的特征参数对应的已存在VNF实例。
实例化单元，用于对匹配失败的特征参数对应的VNF实例需求信息进行实例化。
请参见图8，为本发明实施例提供的一种第二设备的结构示意图。图8对应的实施例提供的第二设备为实施例一提供的用于接收生命周期管理请求的设备。所述第二设备80包括确定单元801和发送单元802。
确定单元801，用于根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例。
发送单元802，用于向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为所述目标NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
所述确定单元801，具体用于根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例以及目标NSD，所述目标NSD为目标NS的描述符，并根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数。
图7所示的第一设备和图8所示的第二设备用于实现本发明实施例一所述的网络服务的生命周期管理方法，基于同一构思，其带来的技术效果也相同， 具体实现过程可参见实施例一的具体描述，此处不再赘述。
请参见图9，为本发明实施例提供的另一种第一设备的结构示意图。图9对应的实施例提供的第一设备为实施例二提供的用于发起生命周期管理请求的设备。所述第二设备90包括接收单元901、获取单元902和管理单元903。
接收单元901，用接收第二设备发送的目标NS的生命周期管理请求，所述生命周期管理请求包括目标NSD的标识，所述目标NSD包括目标虚拟网络功能转发图描述符VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。
获取单元902，用于根据所述目标NSD的标识获取所述目标VNFFGD。
管理单元903，用于根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述NS进行生命周期管理。
所述管理单元903包括实例化单元和连接单元，未在图9中标明。
实例化单元，用于根据所述目标NSD所需的多个VNF实例需求信息实例化得到多个VNF实例。
连接单元，用于根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述多个VNF实例进行网络连接。
请参见图10，为本发明实施例提供的另一种第二设备的结构示意图。图10对应的实施例提供的第二设备为实施例二提供的用于接收生命周期管理请求的设备。所述第二设备100包括确定单元1001和发送单元1002。
确定单元1001，用于根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识。
发送单元1002，用于向第一设备发送目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述目标NSD的标识，所述目标NSD包括目标VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数。
图9所示的第一设备和图10所示的第二设备用于实现本发明实施例二所述的网络服务的生命周期管理方法，基于同一构思，其带来的技术效果也相同，具体实现过程可参见实施例二的具体描述，此处不再赘述。
请参见图11，为本发明实施例提供的又一种第一设备的结构示意图。如图11所示，所述第一设备包括存储器1101、通信总线1102、网络功能虚拟化调度实体NFVO1103和虚拟网络功能管理实体VNFM1104。其中，通信总线1102用于实现这些组件之间的连接通信。其中，存储器1101可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器1101中存储一组程序代码，且NFVO1103或VNFM1104调用存储器1101中存储的程序代码可执行计算机指令，从而实现图2或图3所示的实施例。
NFVO1103用于接收第二设备发送的生命周期管理请求，并根据所述生命周期管理请求查找目标NSD，并分析所述目标NSD所需的多个VNF实例需求信息，然后根据所述生命周期管理请求中的已存在VNF实例和映射关系向VNFM1104发送实例化请求。
VNFM1104用于接收NFVO1103发送的实例化请求，并根据实例化请求生成所需的VNF实例。待VNFM1104完成对所述目标NS所需的所有VNF实例的生成后，VNFM1104将生成的VNF实例的实例化信息存储在存储器1101中，或将生成的VNF实例置于所述第一设备与第二设备所构成的网络架构中。
NFVO1103还用于对VNFM1104生成VNF实例进行网络连接，网络连接包括VNF实例之间的连接以及VNF实例与PNF之间的连接。
所述第一设备能够提高生命周期管理的处理效率，提高VNF实例利用率。
请参见图12，为本发明实施例提供的又一种第二设备的结构示意图。如图12所示，所述第二设备包括至少一个处理器1201，例如CPU，至少一个通信总线1202，通信接口1203，输入设备1204、输出设备1205，存储器1206。其中，通信总线1202用于实现这些组件之间的连接通信。通信接口1203用于与其他设备进行通信。其中，存储器1206可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器1206中存储一组程序代码，且处理器1201调用存储器1101中存储的程序 代码可执行计算机指令，从而实现图2或图3所示的实施例。
存储器1206中可能存储着一些已实例化的VNF实例化信息。处理器1201控制输出设备1205什么时候输出生命周期管理请求，控制输出设备1205输出哪个NS的生命周期管理请求。处理器1201确定目标NS进行生命周期管理所需的已存在VNF实例；对目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数；根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数；根据生命周期管理需求信息确定目标NS进行生命周期管理的目标NSD的标识。
输出设备1205向第一设备发送生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系。所述生命周期管理请求还包括所述目标NSD的标识。
所述第二设备对NSD所需的多个VNF实例需求信息标记特征参数，方便所述第二设备以及所述第一设备识别。
本发明实施例还提供一种网络服务的生命周期管理系统，包括图11所示的第一设备和图12所示的第二设备，即所述生命周期管理系统包括图7所示的第一设备和图8所示的第二设备，和/或图9所示的第一设备和图10所示的第二设备。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为根据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
本发明实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删 减。
本发明实施例装置中的单元可以根据实际需要进行合并、划分和删减。本领域的技术人员可以将本说明书中描述的不同实施例以及不同实施例的特征进行结合或组合。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(Digital Subscriber Line，DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本发明技术方案的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (30)

  1. 一种网络服务的生命周期管理方法，其特征在于，包括：
    第一设备接收第二设备发送的目标网络服务NS的生命周期管理请求，所述生命周期管理请求包括已存在虚拟网络功能VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为目标网络服务描述符NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数；
    所述第一设备根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
  2. 根据权利要求1所述的方法，其特征在于，所述生命周期管理请求还包括所述目标NSD的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述已存在VNF实例的标识及与其对应的特征参数由所述第二设备根据所述已存在VNF实例的实例信息以及所述目标NSD所需的多个VNF实例需求信息确定。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
  6. 根据权利要求4或5所述的方法，其特征在于，所述第一设备根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理，包括：
    所述第一设备将所述映射关系与所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息的特征参数进行匹配；
    所述第一设备获取匹配成功的特征参数对应的已存在VNF实例；
    所述第一设备对匹配失败的特征参数对应的VNF实例需求信息进行实例 化。
  7. 一种网络服务的生命周期管理方法，其特征在于，包括：
    第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例；
    所述第二设备向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为所述目标NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
  8. 根据权利要求7所述的方法，其特征在于，所述第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例，包括：
    所述第二设备根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例以及目标NSD，所述目标NSD为目标NS的描述符；
    所述第二设备根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数。
  9. 根据权利要求7或8所述的方法，其特征在于，所述生命周期管理请求还包括所述目标NSD的标识。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  11. 根据权利要求7-9任一项所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
  12. 一种网络服务的生命周期管理方法，其特征在于，包括：
    第一设备接收第二设备发送的目标NS的生命周期管理请求，所述生命周期管理请求包括目标NSD的标识，所述目标NSD包括目标虚拟网络功能转发图描述符VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟 网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数；
    所述第一设备根据所述目标NSD的标识获取所述目标VNFFGD；
    所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理。
  13. 根据权利要求12所述的方法，其特征在于，所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理，包括：
    所述第一设备根据所述目标NSD所需的多个VNF实例需求信息实例化得到多个VNF实例；
    所述第一设备根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述多个VNF实例进行网络连接。
  14. 根据权利要求12或13所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  15. 根据权利要求12或13所述的方法，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
  16. 一种第一设备，其特征在于，包括：
    接收单元，用于接收第二设备发送的目标网络服务NS的生命周期管理请求，所述生命周期管理请求包括已存在虚拟网络功能VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为目标网络服务描述符NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数；
    管理单元，用于根据所述已存在VNF实例以及所述映射关系对所述目标NS进行生命周期管理。
  17. 根据权利要求16所述的第一设备，其特征在于，所述生命周期管理请求还包括所述目标NSD的标识。
  18. 根据权利要求16或17所述的第一设备，其特征在于，所述已存在VNF实例的标识及与其对应的特征参数由所述第二设备根据所述已存在VNF 实例的实例信息以及所述目标NSD所需的多个VNF实例需求信息确定。
  19. 根据权利要求16-18任一项所述的第一设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  20. 根据权利要求16-18任一项所述的第一设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
  21. 根据权利要求19或20所述的第一设备，其特征在于，所述管理单元包括：
    匹配单元，用于将所述映射关系与所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息的特征参数进行匹配；
    获取单元，用于获取匹配成功的特征参数对应的已存在VNF实例；
    实例化单元，用于对匹配失败的特征参数对应的VNF实例需求信息进行实例化。
  22. 一种第二设备，其特征在于，包括：
    确定单元，用于根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例；
    发送单元，用于向第一设备发送所述目标NS的生命周期管理请求，所述生命周期管理请求用于指示所述第一设备对所述目标NS进行生命周期管理，所述生命周期管理请求包括所述已存在VNF实例的标识及与其对应的特征参数之间的映射关系，所述特征参数为所述目标NSD中对所述目标NSD所需的多个VNF实例需求信息中每个VNF实例需求信息标记的标识参数。
  23. 根据权利要求22所述的第二设备，其特征在于，所述确定单元具体用于根据生命周期管理需求信息确定目标NS进行生命周期管理所需的已存在VNF实例以及目标NSD，所述目标NSD为目标NS的描述符，并根据所述已存在VNF实例的实例化信息以及所述目标NSD所需的多个VNF实例需求信息确定所述已存在VNF实例的标识及与其对应的特征参数。
  24. 根据权利要求22或23所述的第二设备，其特征在于，所述生命周期管理请求还包括所述目标NSD的标识。
  25. 根据权利要求22-24任一项所述的第二设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  26. 根据权利要求22-24任一项所述的第二设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
  27. 一种第一设备，其特征在于，包括：
    接收单元，用接收第二设备发送的目标NS的生命周期管理请求，所述生命周期管理请求包括目标NSD的标识，所述目标NSD包括目标虚拟网络功能转发图描述符VNFFGD，所述目标VNFFGD包括所述目标NSD所需的多个虚拟网络功能VNF实例需求信息中每个VNF实例需求信息的特征参数；
    获取单元，用于根据所述目标NSD的标识获取所述目标VNFFGD；
    管理单元，用于根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述目标NS进行生命周期管理。
  28. 根据权利要求27所述的第一设备，其特征在于，所述管理单元包括：
    实例化单元，用于根据所述目标NSD所需的多个VNF实例需求信息实例化得到多个VNF实例；
    连接单元，用于根据所述目标VNFFGD中的每个VNF需求信息的特征参数对所述多个VNF实例进行网络连接。
  29. 根据权利要求27或28所述的第一设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符和部署规格的VNF实例需求信息。
  30. 根据权利要求27或28所述的第一设备，其特征在于，所述特征参数用于识别所述目标NSD中包括虚拟网络功能描述符、部署规格和实例参数的VNF实例需求信息，所述实例参数用于识别同一虚拟网络功能描述符和同一部署规格下的不同VNF实例需求信息。
PCT/CN2015/099911 2015-12-30 2015-12-30 一种网络服务的生命周期管理方法及设备 WO2017113201A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
CN201580078723.6A CN107431651B (zh) 2015-12-30 2015-12-30 一种网络服务的生命周期管理方法及设备
BR112017028214-3A BR112017028214B1 (pt) 2015-12-30 2015-12-30 Método de gerenciamento de ciclo de vida para um serviço de rede,primeiro dispositivo, segundo dispositivo, e sistema de virtualização de funções de rede
ES15911830T ES2764442T3 (es) 2015-12-30 2015-12-30 Método y dispositivo de gestión del ciclo de vida del servicio de red
AU2015419073A AU2015419073B2 (en) 2015-12-30 2015-12-30 Life cycle management method and device for network service
JP2018518767A JP6609696B2 (ja) 2015-12-30 2015-12-30 ネットワークサービスのライフサイクル管理の方法及びデバイス
PCT/CN2015/099911 WO2017113201A1 (zh) 2015-12-30 2015-12-30 一种网络服务的生命周期管理方法及设备
EP19204458.4A EP3668009B1 (en) 2015-12-30 2015-12-30 Network service lifecycle management method and device
KR1020177034801A KR20180002771A (ko) 2015-12-30 2015-12-30 네트워크 서비스 수명 주기 관리 방법 및 디바이스
EP15911830.6A EP3285439B1 (en) 2015-12-30 2015-12-30 Network service lifecycle management method and device
US15/859,821 US10700947B2 (en) 2015-12-30 2018-01-02 Life cycle management method and device for network service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/099911 WO2017113201A1 (zh) 2015-12-30 2015-12-30 一种网络服务的生命周期管理方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/859,821 Continuation US10700947B2 (en) 2015-12-30 2018-01-02 Life cycle management method and device for network service

Publications (1)

Publication Number Publication Date
WO2017113201A1 true WO2017113201A1 (zh) 2017-07-06

Family

ID=59223995

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099911 WO2017113201A1 (zh) 2015-12-30 2015-12-30 一种网络服务的生命周期管理方法及设备

Country Status (9)

Country Link
US (1) US10700947B2 (zh)
EP (2) EP3285439B1 (zh)
JP (1) JP6609696B2 (zh)
KR (1) KR20180002771A (zh)
CN (1) CN107431651B (zh)
AU (1) AU2015419073B2 (zh)
BR (1) BR112017028214B1 (zh)
ES (1) ES2764442T3 (zh)
WO (1) WO2017113201A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019096380A1 (en) * 2017-11-16 2019-05-23 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or identifier mapping of network services
US11409555B2 (en) * 2020-03-12 2022-08-09 At&T Intellectual Property I, L.P. Application deployment in multi-cloud environment

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016115844A1 (zh) 2015-01-19 2016-07-28 华为技术有限公司 一种ns与vnf的关联方法、装置及系统
CA2974629A1 (en) * 2015-01-23 2016-07-28 Nec Corporation Network functions virtualization management and orchestration method, network functions virtualization management and orchestration system, and program
CN107534571B (zh) * 2015-10-30 2020-12-01 慧与发展有限责任合伙企业 用于管理虚拟网络功能的方法、系统和计算机可读介质
CN109313568A (zh) * 2016-03-29 2019-02-05 诺基亚通信公司 用于在网络服务实例之间移动虚拟化网络功能实例的方法和装置
US10999155B2 (en) * 2017-10-26 2021-05-04 Cisco Technology, Inc. System and method for hybrid and elastic services
US10680898B2 (en) * 2018-03-06 2020-06-09 At&T Intellectual Property I, L.P. Mini-cloud deployment system
US11382150B2 (en) * 2018-03-26 2022-07-05 Apple Inc. System and method of managing PNF connectivity in a network slice instance
CN110401554B (zh) * 2018-04-25 2021-11-30 中移(苏州)软件技术有限公司 Vnf纳管的方法、装置、系统、电子设备及存储介质
GB2573283B (en) * 2018-04-26 2020-04-29 Metaswitch Networks Ltd Improvements relating to network functions virtualization
JP6947129B2 (ja) * 2018-07-05 2021-10-13 日本電信電話株式会社 管理装置およびネットワーク管理方法
CN112567687B (zh) * 2018-08-08 2023-05-12 瑞典爱立信有限公司 朝向网络切片的可用性
CN109753782B (zh) * 2018-11-23 2021-05-25 奇安信科技集团股份有限公司 一种云安全资源池的适配处理方法及装置
US20220217045A1 (en) * 2019-05-07 2022-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and node for using templates
US11546431B2 (en) * 2019-06-26 2023-01-03 Tencent America LLC Efficient and extensive function groups with multi-instance function support for cloud based processing
CN112148935B (zh) 2019-06-26 2024-05-17 腾讯美国有限责任公司 用于多实例的nbmp功能执行的方法和装置
CN112217654B (zh) * 2019-07-11 2022-06-07 华为技术有限公司 服务资源许可管理方法和相关设备
CN112448833B (zh) 2019-09-02 2022-05-17 华为技术有限公司 一种多管理域的通信方法和装置
US10929200B1 (en) * 2019-09-16 2021-02-23 International Business Machines Corporation Live runtime infrastructure orchestration
CN112887121B (zh) 2019-11-29 2022-08-19 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN104348873A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统
EP2849064A1 (en) * 2013-09-13 2015-03-18 NTT DOCOMO, Inc. Method and apparatus for network virtualization
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3094049B1 (en) * 2014-01-29 2018-01-10 Huawei Technologies Co., Ltd. Method for upgrading virtualized network function and network function virtualization orchestrator
WO2015172362A1 (zh) * 2014-05-15 2015-11-19 华为技术有限公司 一种网络功能虚拟化网络系统、数据处理方法及装置
CN104253866B (zh) * 2014-09-20 2018-03-27 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备
CN104734931B (zh) * 2015-03-31 2018-06-05 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348873A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统
EP2849064A1 (en) * 2013-09-13 2015-03-18 NTT DOCOMO, Inc. Method and apparatus for network virtualization
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3285439A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019096380A1 (en) * 2017-11-16 2019-05-23 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or identifier mapping of network services
CN110476444A (zh) * 2017-11-16 2019-11-19 华为技术有限公司 用于网络服务的标识符分配和/或标识符映射的网络实体和方法
CN110476444B (zh) * 2017-11-16 2020-11-17 华为技术有限公司 用于网络服务的标识符分配和/或标识符映射的网络实体和方法
AU2017440072B2 (en) * 2017-11-16 2021-02-25 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or identifier mapping of network services
US11218385B2 (en) 2017-11-16 2022-01-04 Huawei Technologies Co., Ltd. Network entity and method for identifier allocating and/or mapping of network services
US11409555B2 (en) * 2020-03-12 2022-08-09 At&T Intellectual Property I, L.P. Application deployment in multi-cloud environment

Also Published As

Publication number Publication date
CN107431651B (zh) 2020-07-21
AU2015419073B2 (en) 2019-02-07
EP3285439A1 (en) 2018-02-21
US20180145889A1 (en) 2018-05-24
EP3285439A4 (en) 2018-05-16
KR20180002771A (ko) 2018-01-08
JP2018523434A (ja) 2018-08-16
CN107431651A (zh) 2017-12-01
AU2015419073A1 (en) 2017-12-07
ES2764442T3 (es) 2020-06-03
EP3668009A1 (en) 2020-06-17
BR112017028214A2 (zh) 2018-08-28
EP3668009B1 (en) 2021-09-22
JP6609696B2 (ja) 2019-11-20
US10700947B2 (en) 2020-06-30
BR112017028214B1 (pt) 2024-02-06
EP3285439B1 (en) 2019-12-04

Similar Documents

Publication Publication Date Title
WO2017113201A1 (zh) 一种网络服务的生命周期管理方法及设备
US10768955B1 (en) Executing commands within virtual machine instances
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US20210240540A1 (en) Serverless platform request routing
US9760391B2 (en) Method and apparatus for network virtualization
US10917294B2 (en) Network function instance management method and related device
WO2016184045A1 (zh) 一种网络业务扩容的方法和装置
JP6568238B2 (ja) ハードウェアアクセラレーション方法及び関連デバイス
US9912759B2 (en) Dynamically generating solution stacks
WO2019057055A1 (zh) 一种任务处理方法、装置、电子设备及存储介质
JP2018523192A (ja) 分散型コンピューティング環境における仮想マシンインスタンス上のコマンドの実行
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
CN107534577B (zh) 一种网络业务实例化的方法及设备
WO2017206092A1 (zh) 一种生命周期管理方法及管理单元
US10911371B1 (en) Policy-based allocation of provider network resources
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
CN115665231A (zh) 服务创建方法、装置以及计算机可读存储介质
CN112889247B (zh) Vnf服务实例化方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
US11875202B2 (en) Visualizing API invocation flows in containerized environments

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: 15911830

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20177034801

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2015419073

Country of ref document: AU

Date of ref document: 20151230

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018518767

Country of ref document: JP

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017028214

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112017028214

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20171227