WO2018120222A1 - 一种管理vnffg的方法、装置和*** - Google Patents

一种管理vnffg的方法、装置和*** Download PDF

Info

Publication number
WO2018120222A1
WO2018120222A1 PCT/CN2016/113955 CN2016113955W WO2018120222A1 WO 2018120222 A1 WO2018120222 A1 WO 2018120222A1 CN 2016113955 W CN2016113955 W CN 2016113955W WO 2018120222 A1 WO2018120222 A1 WO 2018120222A1
Authority
WO
WIPO (PCT)
Prior art keywords
composite
nested
nfvo
instance
vnffgd
Prior art date
Application number
PCT/CN2016/113955
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 PCT/CN2016/113955 priority Critical patent/WO2018120222A1/zh
Publication of WO2018120222A1 publication Critical patent/WO2018120222A1/zh

Links

Images

Classifications

    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for managing a Virtual Network Function Forward Graph (VNFFG).
  • VNFFG Virtual Network Function Forward Graph
  • Network Function Virtualization is a telecommunication network operator that implements the functions of some telecommunication networks in general-purpose cloud servers, switches, and memories by drawing on virtualization technologies in the field of information technology (IT). Decoupling software and hardware enables fast and efficient deployment of Network Services (NS).
  • the network integrator or the operator's Network Service Descriptor (NSD) presents the results of the network planning and installs the NSD on-board to the NFV Orchestrator (NFVO) and as needed.
  • the network plan described by the NSD is instantiated into an NS instance.
  • the shelf can be understood as registering the necessary NS or Virtual Network Functation (VNF) related software packages, descriptor files, etc. to NFVO.
  • the process of instantiation can be understood as the process of allocating virtual resources and physical resources by descriptor files, such as assigning virtual physical links, network port numbers, etc., and loading computer program software on the allocated resources.
  • the most basic components of an NS instance include Virtual Network Function (VNF), Virtual Link (VL), and one or more VNF forward Graphs (VNFFGs).
  • VNFFG is used to describe a telecommunication network resource and a network forwarding path (NFP) corresponding to different forwarding rules required for forwarding a certain service on the NS.
  • VNFFG can be understood as the service chain Service Chain on the NFV. How to forward the service data packet is determined according to the forwarding rule in VNFFG, that is, NFP.
  • the management domain refers to a system or network operated by an independent organization, and each management domain is responsible for the provision of network services within the management domain by the NFVO.
  • the management domain refers to a system or network operated by an independent organization, and each management domain is responsible for the provision of network services within the management domain by the NFVO.
  • NS management domain which together form a large carrier network
  • large Operators can also deploy independent NFVO management domains in various countries to form a complete carrier network through interconnection.
  • each nested NS is provided by an administrative domain different from the composite NS.
  • the NSD corresponding to the composite NS is called a composite NSD
  • the NSD corresponding to the nested NS referred to is called a nested NSD.
  • the embodiment of the present invention describes a method, an apparatus, and a system for managing a VNFFG, and constructing a reference and docking of a VNFFGD (Virtual Network Function Forward Graph Descriptor) of a composite NS and a VNFFGD of a nested NS referenced by the NS. Relationship, and NFPD (Network Forward Path Descriptor) in the VNFFGD of the composite NS and the reference and docking relationship of the NFPD of the nested NS referenced by the NS; to implement the VNFFG/NFP of the composite NS management domain and its Cooperative operation of VNFFG/NFP of the nested NS administrative domain, such as adding or deleting.
  • VNFFGD Virtual Network Function Forward Graph Descriptor
  • NFPD Network Forward Path Descriptor
  • VNFFG/NFP of the composite NS and the VNFFG/NFP of each nested NS that are referenced are associated with each other to provide a complete end-to-end service forwarding map, which satisfies the composite NS. Business needs.
  • an embodiment of the present invention provides a method for associating VNFFGD and NFPD of a composite NS with VNFFGD and NFPD of a nested NS referenced by the NS, including:
  • the composite NSD includes one or more VNFFGDs, and the VNFFGD may contain one or more referenced nested VNFFGD information.
  • the nested VNFFGD is a certain VNFFGD included in the nested NSD.
  • one or more VNFFGDs with nested VNFFGD will be referred to herein as composite VNFFGD.
  • the nested VNFFGD information includes at least a nested NSD ID (identity, Identity) to which the nested VNFFGD belongs, and a nested VNFFGD ID.
  • the nested VNFFGD ID is an identifier of a certain VNFFGD within the nested NSD.
  • Composite VNFFGD also contains information on VNF and PNF connection points in the composite NS management domain, and composite NS tubes.
  • the composite VNFFGD also includes one or more NFPDs, which may contain one or more referenced nested NFPD information.
  • one or more NFPDs with nested NFPD will be referred to herein as complex NFPD.
  • the composite NFPD describes the forwarding rules between the VNF and PNF connection points in the composite NS management domain, and between the composite NS and the nested NS, and between different nested NSs.
  • the nested NFPD is a certain NFPD included in the nested VNFFGD.
  • the nested NFPD information includes at least a nested NSD ID to which the nested NFPD belongs, and a nested NFPD ID.
  • the nested NFPD ID is an identifier of a unique NFPD within the nested NSD.
  • Nested NFPD describes the forwarding rules between VNF and PNF connection points within a nested NS.
  • the method adds one or more nested VNFFGD or nested NFPD referenced in VNFFGD and NFPD, and associates the originally isolated VNFFGD in different NS management domains to form a global composite VNFFGD and composite NFPD, so that The composite NS service can be forwarded end-to-end between nested NS management domains.
  • an embodiment of the present invention provides a method for managing a VNFFG, including:
  • OSS/BSS Operaational Support System/Business Support System
  • composite NFVO's own operation and maintenance client or other operation and maintenance entity to NFVO-1 (for convenience of reference, NFVO- in this application) 1 represents the NFVO of the composite NS management domain, sends a request to create a composite NS instance and instantiates the composite NS, and NFVO-1 instantiates the composite NS according to the NSD ID in the request message, and instantiates the present according to the description of VNFFGD in the composite NSD. Manage VNFFG and NFP within the domain.
  • VNFFGD in the composite NSD is a composite VNFFGD
  • NFVO-1 also initiates an instantiation process of nested VNFFG and nested NFP.
  • VNFFG and NFP in the composite NS management domain and the instantiation process of VNFFG and NFP in the nested NS management domain are in no particular order; a composite VNFFGD may reference multiple nested NSs.
  • VNFFGD each nested NS corresponds to a different NFVO
  • NFVO-1 needs to initiate an instantiated NS request to each nested NS corresponding NFVO.
  • NFVO-2 is taken as an example, representing all embedded Set of NF NFVO.
  • the composite NSD and the nested NSD are respectively uploaded to the composite NS administrative domain and the nested NS administrative domain, wherein the NFVO-1 of the composite NS administrative domain can also be Obtain the instantiation of the nested NS referenced by the composite NS (for example, whether it has been instantiated) or the nested NS management domain by means of subscription or query. Information on NFVO-2.
  • NFVO-1 initiates the instantiation process of nested VNFFG and nested NFP: NFVO-1 determines the nesting according to the nested NSD information recorded in the composite VNFFGD and according to the mapping relationship between the nested NSD and the nested NS management domain. The NS administrative domain to which the NSD belongs. NFVO-1 knows the instantiation of the nested NS of the NS administrative domain to which the nested NSD belongs by subscription or other means:
  • the NS administrative domain to which the nested NSD belongs does not complete the instantiation of the nested NS: NFVO-1 requests and obtains the instance ID of the nested NS from NFVO-2, and initiates instantiation to NFVO-2.
  • Nested NS request the request carries an instance ID containing at least a nested NS.
  • the request for instantiating the nested NS sent by the NFVO-1 to the NFVO-2 carries an indication of adding the VNFFG instance, referenced by the composite VNFFGD
  • One or more nested VNFFGD IDs, and one or more nested NFPD IDs referenced by the composite NFPD NFVO-2 receives the instantiated NS request message and instantiates the NS according to the NSD information in the request message.
  • the NFVO-2 may choose to instantiate only the VNFFG and the NFP corresponding to the nested VNFFGD ID and the nested NFPD ID. After the NFVO-2 is instantiated, the nested VNFFG instance ID and the nested NFP instance ID corresponding to the nested VNFFGD and the nested NFPD are returned to the NFVO-1.
  • NFVO-2 may also record which nested VNFFG instances and nested NFP instances are referenced by which composite NS to support a VNFFG instance or a nested NFP instance being referenced by multiple composite NSs.
  • the NFVO-1 records the nested VNFFG instance ID and the nested NFP instance ID referenced by the composite VNFFG and the composite NFP for subsequent association management.
  • the NS management domain to which the nested NSD belongs has completed the instantiation of the nested NS: NFVO-1 initiates a request to update the nested NS instance to NFVO-2, and the request message includes at least the composite NS.
  • the instance ID, the indication of the VNFFG instance is added, one or more nested VNFFGD IDs referenced by the composite VNFFGD, and one or more nested NFPD IDs referenced by the composite NFPD.
  • the NFVO-2 receives the request to update the nested NS instance, and according to the indication of adding the VNFFG instance in the request message, nesting the VNFFGD ID and the nested NFPD ID, instantiating the VNFFG and the NFP in the nested NS instance. After the NFVO-2 instantiation is completed, the nested VNFFG instance ID and the nested NFP instance ID corresponding to the nested VNFFGD and the nested NFPD are returned to the NFVO-1.
  • NFVO-2 can also record nested VNFFG instances and nested NFP instances referenced by which composite NS to support one A case where a VNFFG instance or a nested NFP instance is referenced by multiple composite NSs.
  • the NFVO-1 records the nested VNFFG instance ID and the nested NFP instance ID referenced by the composite VNFFG and the composite NFP for subsequent association management.
  • the method for creating a composite VNFFG and a composite NFP instance provided by the second aspect depends on the premise or assumption that when the NFVO-1 instantiates the composite NS, the method according to the first aspect already exists in the already-applied composite NSD.
  • the composite NSD needs to be re-stocked, and the composite VNFFG and composite NFP instances are created by updating the process of the composite NS instance.
  • the operation maintenance client or the other operation and maintenance entity of the composite NFVO itself sends a request for updating the composite NS instance to the NFVO-1, and the request message includes at least the instance ID of the composite NS, and the indication of the VNFFG instance is added. , composite VNFFGD ID and composite NFPD ID.
  • NFVO-1 instantiates VNFFG and NFP in the management domain according to the request message, and initiates an instantiation process of nested VNFFG and nested NFP.
  • the instantiation process of initiating the nested VNFFG and the nested NFP is consistent with the instantiation process of nesting the VNFFG and the nested NFP in the method of the second aspect.
  • NFVO-1 initiates nested VNFFG and nesting based on the composite VNFFGD/composite NFPD recorded in the composite NSD template according to the first aspect.
  • the instantiation process of NFP may not be recorded, but may be performed by the operation maintenance client or other operation and maintenance entity of the composite NFVO itself.
  • the request message for creating or updating the composite NS instance of NFVO-1 carries the nested VNFFGD information referenced by the composite VNFFGD and the nested NFPD information referenced by the composite NFPD, and the NFVO-1 learns the composite VNFFGD/composite through the information in the interface message. NFPD, and initiates the instantiation process of nested VNFFG and nested NFP.
  • the operation maintenance client or other operation and maintenance entity of the composite NFVO itself sends a request to the NFVO-1 to update the composite NS instance, and the request message carries at least the composite NS instance. ID, the indication of the VNFFG instance and the composite VNFFG instance ID are deleted.
  • NFVO-1 deletes the VNFFG in the composite NS management domain according to the request message, and sends a request to update the nested NS instance to the NFVO-2.
  • the request message carries the indication of deleting the VNFFG instance, and the nested VNFFG instance ID to be deleted and the deletion is to be deleted. Nested NFP instance ID.
  • NFVO-2 deletes the nested VNFFG instance and the nested NFP instance of the management domain.
  • NFVO-2 also needs to determine whether the nested VNFFG instance to be deleted or the nested NFP instance is referenced by other composite NS, if it is also compounded by other composites.
  • NFVO-2 only deletes the reference relationship between the nested VNFFG instance or the nested NFP instance and the composite NS that sends the request message. If not referenced by other composite NS, NFVO-2 deletes the nested VNFFG instance or embedded Set of NFP instances.
  • the composite VNFFGD or the composite NFPD is changed, for example, the referenced nested VNFFGD or the nested NFPD is added or deleted, the composite VNFFGD needs to be updated synchronously. Or a VNFFG instance or an NFP instance corresponding to the NFPD.
  • the operation and maintenance client or other operation and maintenance entity of the composite NFVO itself may delete the composite VNFFG instance corresponding to the old VNFFGD, and then create a new composite VNFFG instance according to the updated VNFFGD.
  • an embodiment of the present invention provides an NFVO of a composite NS management domain, where the NFVO of the composite NS management domain implements the function of NFVO-1 in the foregoing second aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the NFVO of the composite NS management domain includes: a communication interface, configured to receive a request message for instantiating a composite NS or updating a composite NS, and returning a corresponding response message, and is also used for sending Instantiating a nested NS or updating a request for a nested NS instance and receiving a corresponding response message; a memory for storing computer execution instructions and related information of the composite NS and its nested NS referenced, including references by the composite VNFFG instance a nested VNFFG instance identifier, and a nested NFPD instance identifier referenced by the composite NFP instance; the processor is connected to the memory and the communication interface through the bus, and when the communication interface receives the request message for instantiating the composite NS or updating the composite NS, the processor executes A computer stored in the memory executes instructions to perform the functions of NFVO-1 in the method of the second aspect.
  • an embodiment of the present invention provides an NFVO of a nested NS management domain, where the NFVO of the nested NS management domain implements the function of the NFVO-2 in the foregoing second aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the NFVO of the nested NS management domain includes: a communication interface, configured to receive a request message for instantiating a nested NS or updating a nested NS, and returning a corresponding response message; And storing a computer execution instruction; the processor is connected to the memory and the communication interface through a bus, and when the communication interface receives the request message for instantiating the nested NS or updating the nested NS, the processor executes the computer execution instruction stored in the memory to The function of NFVO-2 in the method of the second aspect is accomplished.
  • the embodiment of the present invention provides an operation and maintenance entity, which may be an operation and maintenance client or other operation and maintenance entity of the OSS/BSS or the composite NFVO itself, and the operation and maintenance entity implements the OSS/BSS in the foregoing second aspect or
  • the operation of the composite NFVO itself maintains the functionality of the client or other operational maintenance entity.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an operation and maintenance entity provided by an embodiment of the present invention includes a communication interface, configured to send a request message for instantiating a composite NS or updating a composite NS to a composite NFVO, and triggering to create or delete a composite VNFFG instance and its a nested VNFFG instance referenced, and a process of a composite NFP instance and a nested NFP instance referenced by the same; a memory for storing computer execution instructions; and a processor connected to the memory and the communication interface via the bus to generate a request message to be sent And processing the message received by the communication interface.
  • an embodiment of the present invention provides a system for managing a VNFFG, where the system includes the NFVO of the composite NS management domain according to the third aspect, and the NFVO of the nested NS management domain as described in the fourth aspect.
  • An operational maintenance entity as described in the fifth aspect.
  • an embodiment of the present invention provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present invention provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the VNFFG combination of multiple NS management domains can be associated in a composite NS scenario to form an end-to-end composite VNFFG service chain, providing new The combination of business services to enhance the value of the network.
  • the names of network functional entities or technical terms quoted in this application may change, but do not affect the use of the methods described herein.
  • the method described in the present application can be extended to the field of 5G slicing based on the NFV architecture.
  • a 5G slice is deployed in one management domain, and multiple 5G slices deployed in different management domains jointly provide a complete 5G network service; in another case, a 5G slice provides a complete 5G network service independently, and the 5G slice is divided into multiple components and deployed in multiple different management domains, in the above two cases,
  • the method described in this application can also be used to create and maintain an inter-domain end-to-end service chain.
  • FIG. 1 is a schematic structural diagram of an NFV system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a system architecture of a composite NS system according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of VNFFG and NFP of each management domain in a composite NS architecture according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of interconnection of VNFFG and NFP in each management domain in a composite NS architecture according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of creating a composite VNFFG in a Top-Down mode according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of creating a composite VNFFG in a Bottom-Up manner according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of a new composite VNFFG according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of deleting a composite VNFFG according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of creating a VNFFG by using an interface message according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • Embodiment 1 Overview of system architecture and technical solutions of the present application
  • the NFV system (100) includes an Operation Support System/Business Support System (OSS/BSS) (101) and an Element Management System (EMS). (102), Virtual Network Function (VNF) (103), Network Function Virtualization Infrastructure (NFVI) (104), and NFV Management and Orchestration (referred to as NFV Management and Orchestration) NFV MANO) (105).
  • OSS/BSS Operation Support System/Business Support System
  • EMS Element Management System
  • VNF Virtual Network Function
  • NFVI Network Function Virtualization Infrastructure
  • NFV Management and Orchestration referred to as NFV Management and Orchestration
  • NFV MANO NFV MANO
  • NFV MANO includes NFV Orchestrator (NFVO) (106), Virtualized Network Function Manager (VNFM) (107), Virtualized Infrastructure Manager (Virtualized Infrastructure Manager) , VIM) (108) and a Service, VNF and Infrastructure Description Unit (Service, VNF and Infrastructure Description) (109).
  • NFVO NFV Orchestrator
  • VNFM Virtualized Network Function Manager
  • VIM Virtualized Infrastructure Manager
  • Service, VNF and Infrastructure Description Service, VNF and Infrastructure Description
  • OSS/BSS (101): Mainly for telecom service operators, providing comprehensive network management and service operation functions, including triggering the addition, update, and instantiation of various descriptors such as NSD, VNFFGD, and NFPD.
  • NFVO 106): Implement NSD, management and processing of Virtualised Network Function Forwarding Graph (VNFFG) in the management domain, management of network service life cycle, and cooperate with VNFM to realize lifecycle management and resources of VNF Global view feature.
  • VNFFG Virtualised Network Function Forwarding Graph
  • VNFM (107) implements lifecycle management of the virtualized network element VNF, including management and processing of the VNFD, initialization of the VNF instance, expansion/reduction of the VNF, and termination of the VNF instance. Supports receiving the elastic scaling policy delivered by NFVO to realize the elastic scaling of VNF.
  • VIM (108) responsible for infrastructure layer hardware resources, virtualization resource management, monitoring and fault reporting, and providing virtualized resource pools for upper-layer applications.
  • Descriptor description unit (109) mainly records Network Service Descriptor (NSD), Virtual Gateway Function Descriptor (VNFD), Physical Network Function Descriptor (PNFD), virtual chain Virtual Link Descriptor (VLD), Virtual Network Function Descriptor (VNFFGD), Nested NSD (Nested NSD) and other NFV system related descriptor information.
  • NSD Network Service Descriptor
  • VNFD Virtual Gateway Function Descriptor
  • PNFD Physical Network Function Descriptor
  • VLD virtual chain Virtual Link Descriptor
  • VNFFGD Virtual Network Function Descriptor
  • Nested NSD Nested NSD
  • other NFV system related descriptor information mainly records Network Service Descriptor (NSD), Virtual Gateway Function Descriptor (VNFD), Physical Network Function Descriptor (PNFD), virtual chain Virtual Link Descriptor (VLD), Virtual Network Function Descriptor (VNFFGD), Nested NSD (Nested NSD) and other NFV system related descriptor information.
  • FIG. 2 is a schematic diagram of a composite NS system architecture across administrative domains, including NFVO management domain A (201), which provides NS A; NFVO management domain B (202), which provides NS B; NFVO management domain C (203) , which provides NS C.
  • the NFVO management domain A needs to provide NS A, and needs the NS provided by the NFVO management domain B and the NFVO management domain C.
  • the NS A is called a composite NS
  • the NS B and the NS C are called nested NSs.
  • the NFVO of the composite NS management domain and the nested NS management domain form an umbrella management structure
  • NFVO-1 (204) is responsible for the management of the composite NS
  • NFVO-2 (205) and NFVO-3 (206) are responsible for their respective nesting.
  • NS scheduling management, NFVO-1 (204) and NFVO-2 (205) / NFVO-3 (206) through the Or-Or interface to complete the life cycle management of the composite NS across the NFVO management domain.
  • the NFVO of the composite NS management domain is expressed by NFVO-1;
  • the NFVO in the nested NS management domain, such as NFVO-2 or NFVO-3 is uniformly expressed by NFVO-2.
  • OSS/BSS may also be an operation and maintenance client or other operation and maintenance entity of the NFVO-1 itself.
  • OSS/BSS is taken as an example for description.
  • the OSS/BSS related methods described in the same applies to the operation and maintenance client or other operational maintenance entity of NFVO-1 itself.
  • VNFFG How to manage the data packets of the internal network services of the management domain is determined according to VNFFG, that is, Said VNFFG will describe the CP information of each connection point and the order relationship between the connection points.
  • the path forwarding rules between connection points are defined by NFP, and the same VNFFG may contain multiple NFPs.
  • Figure 3 is based on the composite NS system architecture shown in Figure 2, and gives a possible cross-administration domain For the scenario of composite NS, examples of VNFFG and NFP in different management domains. The introduction of NFVO Management Domain A, NFVO Management Domain B and NFVO Management Domain C in Figure 3 and the relationship between them are shown in Figure 2 and its description.
  • VNFFG01 is a VNF forwarding diagram of the video service, which includes a service forwarding rule NFP011
  • VNFFG02 is a VNF forwarding diagram of the VoLTE service, which includes a service forwarding rule NFP021.
  • the VNF device in the NFVO management domain B may be a base station eNodeB device corresponding to the wireless network and a device such as a PDN gateway and an MME in the EPC network; and three types of VNFFGs in the NFVO management domain B are respectively used to describe different services.
  • the VNF device in the NFVO management domain C may correspond to devices such as SBC, P-CSCF, S-CSCF, and AS in the IMS core network.
  • VNFFGs in the NFVO management domain C which are used to describe the service forwarding path in different service scenarios.
  • the VNFFG21 is used to describe the VNF forwarding map of the video and the VoLTE service.
  • the NFP211 is used to describe the service forwarding rules of the video, and the NFP212 is used to describe The service forwarding rule of the VoLTE service;
  • the VNFFG22 is used to describe the VNF forwarding diagram of the conference service, which includes the service forwarding rule NFP221.
  • NFVO management domain A requires NFVO management domain B and NFVO management domain C to jointly provide end-to-end VoLTE services (ie, composite NS)
  • end-to-end VoLTE services ie, composite NS
  • VNFFG and NFP in each management domain are isolated, VNFFG and NFP between nested NSs Lack of association, unable to form a global composite VNFFG or composite NFP, the business can not be accurately forwarded between management domains.
  • a scheme is needed to describe how the end-to-end service in the composite NS management domain is forwarded. For example, the CP134 connection point in the NFP121 in the nested NS management domain 1 should forward the service packet to which connection point in the composite NS management domain (CP011). Still CP013).
  • the embodiment of the present invention proposes a composite NS system architecture as shown in FIG. A method, apparatus and system for managing a VNFFG.
  • OSS, NFVO-1 and NFVO-2 Have the following functions:
  • OSS/BSS After the composite NS is instantiated, if a composite VNFFGD is added to the composite NSD, the OSS supports sending an Update NS request message to the NFVO-1, and the request message carries the VNFFGD ID to be added and the new message. The instruction of the VNFFG instance is deleted. If the composite VNFFGD is deleted in the composite NSD, the OSS supports sending an update NS request message to the NFVO-1, and the request message carries the VNFFG instance ID corresponding to the deleted composite VNFFGD and deletes the VNFFG instance.
  • the OSS supports sending a request message for updating the NS to the NFVO-1, and the request message carries the VNFFG instance ID corresponding to the updated composite VNFFGD and an indication of updating the VNFFG instance. If the information of the composite VNFFGD and the referenced VNFFGD is not described in the composite NSD, the OSS needs to carry the composite VNFFGD and the referenced nested VNFFGD information in the request message for adding or updating the NS instance. See the description in Example 6 for information on the composite VNFFGD and its referenced nested VNFFGD. The OSS supports recording the composite VNFFG instance ID under the composite NS instance and its corresponding VNFFGD ID.
  • NFVO-1 In the process of creating an NS instance according to the NS instance request message, if the NSD corresponding to the NS instance contains a composite VNFFGD, NFVO-1 supports adding a VNFFG instance and an NFP instance in the management domain, and according to the composite VNFFGD.
  • the referenced nested VNFFGD information and the composite NFPD and the referenced nested NFPD information send a request to instantiate the nested NS or update the nested NS instance, request the nested NFVO to create a nested VNFFG instance and embed
  • the NFP instance the request message includes a nested NS instance identifier, and may further include an indication of adding a VNFFG, one or more nested VNFFGD identifiers, one or more nested NFPD identifiers, and updating the NS instance according to the update NS instance request message.
  • NFVO-1 supports adding or deleting a VNFFG instance and an NFP instance in the management domain, and according to the composite VNFFGD and its referenced nested VNFFGD Information and composite NFPD and its referenced nested NFPD information, send a request message updating the nested NS instance to the NFVO corresponding to the nested NS, requesting the nested NFVO to create a nested VNFFG instance and embedding A set of NFP instances, the request message includes a nested NS instance identifier, an indication of adding a VNFFG, one or more nested VNFFGD identifiers, and one or more nested NFPD identifiers.
  • NFVO-1 supports the recording of composite VNFFGD and its referenced nested VNFFGD information, supporting the recording of the composite VNFFG instance identifier and its nested VNFFG instance identifier.
  • NFVO-2 If you receive a request message from NFVO-1 to instantiate a nested NS or update a nested NS, Including the indication to add or delete VNFFG, NFVO-2 supports adding or deleting nested VNFFG instances and nested NFP instances according to the instructions in the message, and returns the nested VNFFG instance ID added according to the request message to NFVO-1. And nested NFP instance IDs.
  • Figure 4 shows an example of recording and managing a composite VNFFGD: one or more VNFFGDs are included in a composite NSD, which may contain one or more referenced nested VNFFGD information.
  • the nested VNFFGD information includes at least a nested NSD ID to which the nested VNFFGD belongs, and a nested VNFFGD ID.
  • the nested VNFFGD ID is an identifier of a certain VNFFGD within the nested NSD.
  • the cpdpool ID list in the composite VNFFGD contains the VNF and PNF connection point information in the composite NS management domain, and the connection point information of the composite NS management domain and other nested NS management domains, and the connection between different nested NS administrative domains. Point information, and the order relationship between the connection points described above.
  • the composite VNFFGD also includes one or more NFPDs, which may contain one or more referenced nested NFPD information.
  • the nfpRule of the composite NFPD describes the forwarding rules between the VNF and PNF junctions in the composite NS management domain, and between the composite NS and the nested NS, and between different nested NSs.
  • the nested NFPD information includes at least a nested NSD ID to which the nested NFPD belongs, and a nested NFPD ID.
  • the nested NFPD ID is an identifier of a unique NFPD within the nested NSD.
  • Nested NFPD describes the forwarding rules between VNF and PNF connection points within a nested NS administrative domain.
  • FIG. 5 is taken as an example to describe how to associate VNFFG and NFP in different management domains by the method described in FIG. 4 to provide an end-to-end composite VNFFG service chain across management domains.
  • NSD0 composite NSD corresponding to composite NS A refers to two nested NSDs, NSD1 and NSD2; NSD1 is identified as 1 in composite NSD, NSD2 is identified as 2 in composite NSD; nested NS B is based on NSD1 instance, embedded The set of NS C is based on an instance of NSD2;
  • VNFFG02 and NFP021 are VNFFGD02 and NFPD021, respectively, wherein the identifier of VNFFGD02 in NSD0 is 02, and the identifier of NFPD021 in NSD is 021;
  • VNFFG12 and NFP121 are VNFFGD12 and NFPD121, respectively, wherein the identifier of VNFFGD12 in NSD1 is 12, and the identifier of NFPD121 in NSD is 121;
  • VNFFG21 and NFP211 are VNFFGD21 and NFPD211, respectively, wherein the identifier of VNFFGD21 in NSD2 is 21, and the identifier of NFPD212 in NSD2 is 212;
  • the identifier of the CPD (connection point descriptor) corresponding to all the CP connection points in FIG. 5 is the number in the CP connection point label.
  • the identifier of the CPD corresponding to the CP111 in the NSD1 is 111, CP023.
  • the corresponding CPD is identified as 023 in NSD0.
  • the composite NS video service forwarding map descriptor VNFFGD02 needs to reference VNFFGD12/NFPD121, and VNFFGD21/NFPD212.
  • VNFFGD02 ie, composite VNFFGD
  • NSD corresponding to the composite NS shall contain at least the following information in Table 1, Table 2 and Table 3:
  • Table 1 describes the information of the nested VNFFGDs referenced in VNFFGD02:
  • Table 2 describes all the connection points of VNFFGD02 in the NFVO management domain A recorded in VNFFGD2, and the connection points of the NFVO management domain B and the NFVO management domain C to the external VNFFGD02 connection:
  • Table 3 describes the information of the nested NFPD referenced by NFPD021 recorded in VNFFGD2:
  • NFPD021 describes the forwarding rules of connection points in cpdPool Id, NFVO management domain B and NFVO management domain
  • the CPD information in C is described in VNFFGD12 and VNFFGD21, and the forwarding rules between CPDs are described in NFPD121 and NFPD212.
  • Embodiment 2 Creating a composite VNFFG in the Top-Down mode
  • the Top-Down mode means that in the process of instantiating a composite NS, NFVO-1 is responsible for initiating the instantiation of nested NSs to NFVO-2 of the management domain where the nested NS is located.
  • NFVO-1 controls the composite NS management domain and its nested NS management domain as a whole.
  • Figure 6 depicts a schematic diagram of a process for creating a composite VNFFG and composite NFP.
  • the network locations and relationships between OSS, NFVO-1 and NFVO-2 in the figure can be seen in Figure 2, where NFVO-2 represents all possible embeddings.
  • the composite NSD has been designed and put on NFVO-1; the referenced nested NSD has been uploaded to NFVO-2.
  • NFVO-1 obtains the information of NFVO-2 to which each nested NSD belongs.
  • the composite NSD contains information on the composite VNFFGD.
  • the OSS requests the NFVO-1 to create an ID of the composite NS instance, and carries the ID information of the composite NSD; the NFVO-1 allocates the instance ID of the composite NS for this request, and returns the ID to the OSS.
  • the OSS requests the NFVO-1 to instantiate the composite NS, and the request message includes at least the composite NS instance ID allocated in step S601.
  • NFVO-1 obtains the information of the composite NSD according to the ID of the instance; determines the VNFFGD ID and NFPD ID information referenced by each nested NSD, and the information of which composite VNFFGD/NFPD is referenced according to the description information in the composite NSD. .
  • NFVO-1 initiates a request for creating a nested NS instance ID to the NFVO-2 corresponding to each nested NSD according to the mapping relationship between the nested NSD ID and the NFVO-2, and the request carries the nested NSD ID information.
  • the mapping relationship between the nested NSD ID and NFVO-2, NFVO-1 can be obtained by subscribing to other NFVOs. By subscribing, NFVO-1 can obtain information such as NSDs of other NFVOs and their corresponding NS instance status. This is prior art and will not be described here.
  • NFVO-2 assigns the instance ID of the nested NS to this request and returns this ID to NFVO-1.
  • NFVO-1 requests the NFVO-2 to instantiate the nested NS, and the message includes at least the nested NS instance ID allocated in step S604, and adds an indication of the VNFFG instance (such as adding an optional parameter AddVnffg in the message, when If the value of this parameter is 1, it means that the VNFFG instance is added.
  • the VNFFGD ID+NFPD ID information in the nested NSD obtained in step S603 is obtained.
  • NFVO-2 instantiates the nested NS according to the request, and in the process of instantiating the VNFFG, according to the indication of the newly added VNFFG instance and the referenced VNFFGD ID+NFPD ID information in the nested NSD, corresponding to the instance
  • the information of the corresponding VNFFG and NFP is obtained in the NSD, and the VNFFG instance and the NFP instance in the local domain are created.
  • NFVO-2 also needs to record VNFFG instances and NFP instances that are referenced by the composite NS where NFVO-1 resides.
  • NFVO-2 sends the instantiation result of the nested NS to NFVO-1, and the newly notified nested VNFFG instance ID is notified in the result.
  • NFVO-1 receives the S607 message, and records the nested VNFFG instance ID carried in the message.
  • NFVO-1 instantiates the NS in this management domain, and the composite VNFFG and composite NFP in this management domain.
  • NFVO-1 records the reference relationship between the composite VNFFG instance ID of the administrative domain and the nested VNFFG instance ID referenced by it. It should be noted that the operation of the NFVO-1 instantiating the local NS and the composite VNFFG it contains has no order relationship with the operation of instantiating the nested NS and the nested VNFFG it contains, for example, the operation described in this step It can also be completed in step S603.
  • NFVO-1 sends an instantiation result of the composite NS to the OSS, where at least the composite VNFFG instance ID is included.
  • the S601 step may actually have multiple message interactions.
  • the NFVO-1 receives an NS instantiation request and returns an instant response message carrying the ID of the lifecycle operation, and then at NFVO-1.
  • NFVO-2 actually starts instantiating the NS, it sends a notification of the NS lifecycle state change to the OSS, carries the ID of the lifecycle operation and the start indication, and then starts the instantiation process of S603, at the end of the real instantiation.
  • the Top-Down method makes it easier for NFVO-1 to manage the overall NS service globally.
  • each management domain may not be fully managed.
  • the nested NS of each management domain is still performed by OSS.
  • Instantiation in this case, you need to use the Bottom-Up method to create a composite VNFFG.
  • the Bottom-Up mode refers to the instantiation of each nested NS by the OSS to the NFVO-2 of the nested NS management domain.
  • the OSS triggers the instance of the composite NS to the NFVO-1 of the composite NS administrative domain.
  • NFVO-1 is not responsible for triggering the instantiation of nested NS to NFVO-2.
  • Embodiment 3 Creating a composite VNFFG in the Bottom-Up mode
  • Figure 7 depicts a schematic diagram of the process of creating a composite VNFFG instance in the Bottom-Up mode. The difference from Figure 6 is:
  • the OSS first triggers the created instances of the nested NSs, as shown in steps S701-S704. After the nested NS instantiation is completed, the OSS triggers the instantiation of the composite NS to the NFVO-1, as shown in step S706. In step S703, NFVO-2 may choose not to perform instantiation of VNFFG according to the local policy configuration.
  • step S707 the NFVO-1 selection first instantiates the VNFFG and NFP of the management domain before triggering the nested VNFFG instantiation.
  • NFVO-1 determines the VNFFGD ID and NFPD ID information referenced by each nested NSD and the information of which composite VNFFGD/NFPD is referenced based on the description information in the composite NSD.
  • NFVO-1 can learn the nested NS instance ID of NFVO-2 by subscribing to the notification mechanism (for example, NFVO-1 subscribes to the nested NS instance of NFVO-2, and NFVO-2 sends a notification after the NS instance is created. The message is sent to NFVO-1). Therefore, it is no longer necessary to request NFVO-2 to allocate a nested NS instance identifier before step S708.
  • NFVO-1 directly sends an update NS instance request message in step S708, where the message includes at least a nested NS instance ID, and an indication of adding a VNFFG instance (such as adding a new one to the message)
  • the optional parameter AddVnffg when this parameter takes a value of 1, represents the VNFFG instance to be added, and the referenced VNFFGD ID and NFPD ID information in the nested NSD obtained in step S707.
  • the NFVO-2 receives the nested NS update request message, and instantiates the referenced VNFFG and NFP according to the indication in the request message in step S709.
  • NFVO-1 After receiving the S710 message sent by NFVO-2, NFVO-1 also records the reference relationship between the composite VNFFG instance ID of the domain and the nested VNFFG instance ID referenced by the domain. Returning to OSS in step S711 The composite NS result response is instantiated, including at least a composite VNFFG instance ID.
  • the originally developed NSD template may not be perfect, and some information may be missing, such as the lack of description information of the composite VNFFGD, so that the composite NS and the nested NS have completed the instance.
  • the operator needs to update the NSD template, re-upgrade the updated NSD template, and complete the instantiation of VNFFG through the NS update process.
  • Embodiment 4 Adding a composite VNFFG
  • Figure 8 depicts a flow diagram for creating a composite VNFFG instance in another scenario.
  • the composite NS and the nested NS have completed the instantiation process, but the composite NSD template on which the composite NS instantiation is based does not have a composite VNFFGD.
  • the network operator updates the composite NSD template after the composite NS and the nested NS are instantiated, adds the composite VNFFGD, and initiates the process of updating the composite NS instance through the OSS.
  • the OSS requests to update the NS instance, where at least the composite NS instance ID is carried, and the indication of the VNFFG instance and the composite VNFFGD ID are added.
  • the NFVO-1 After receiving the request message, the NFVO-1 instantiates the VNFFG and the NFP of the management domain according to the information in the request message, and further determines the composite VNFFGD ID in the request message according to the description information in the composite NSD. VNFFGD ID and NFPD ID information of each nested NSD referenced.
  • step S805 NFVO-1 initiates a request to update the nested NS to NFVO-2, requesting NFVO-2 to instantiate the VNFFG and NFP referenced by the nested NSD, the description of the request message and the processing of NFVO-2, see S708 and S709. .
  • Other process processing is referred to the fifth embodiment and will not be described again.
  • the OSS can also delete the established composite VNFFG as needed.
  • the composition relationship of the composite NS changes.
  • the nested NS needs to be added or deleted.
  • the service forwarding path between different management domains needs to be changed.
  • the original composite VNFFG is established.
  • the composite VNFFG can be changed by first deleting the failed composite VNFFG and then establishing a new composite VNFFG.
  • the associated composite VNFFG needs to be deleted.
  • Embodiment 5 Deleting a composite VNFFG
  • Figure 9 depicts a flow diagram for deleting a composite VNFFG instance.
  • the composite NS and the nested NS have completed the instantiation process, and the composite VNFFGD in the composite NS has also been instantiated.
  • the network operator deletes one of the VNFFG instances through the OSS.
  • step S902 the OSS sends an update NS instance request message to the NFVO-1, and the request carries at least the complex Combined with the NS instance ID, delete the VNFFG indication, the composite VNFFG instance ID to be deleted.
  • the NFVO-1 After receiving the request message, the NFVO-1 deletes the composite VNFFG instance corresponding to the composite VNFFG instance ID in the management domain and the composite NFP instance included in the management domain, and according to the previously recorded composite VNFFG instance/composite NFP.
  • the relationship between the instance and the nested VNFFG instance/nested NFP instance determines the nested VNFFG instance/nested NFP instance referenced by the composite VNFFG instance/composite NFP instance, and the embedded VNFFG instance/nested NFP instance belongs to the embedded Set of NS.
  • the NFVO-1 sends a request message for updating the nested NS instance to the NFVO-2 corresponding to the nested NS in step S904, where the nested NS instance ID is carried, and the VNFFG indication is deleted, and the nested VNFFG instance ID to be deleted is deleted.
  • NFVO-2 first determines in step S905 whether the nested VNFFG instance indicated in the S904 message is referenced by a other composite NS administrative domain other than NFVO-1, if there is no other reference relationship, the indication in the delete request message The VNFFG instance and the NFP instance it contains; if there are other reference relationships, the VNFFG instance indicated in the request message and the NFP instance it contains may not be deleted; and the updated nested NS instance result response message is returned in the S906 message.
  • an implementation manner of recording the composite VNFFGD and the nested VNFFGD information referenced in the NSD is given.
  • Composite VNFFGD and its referenced nested VNFFGD there may be some network integrators or operators who do not wish to use the extended NSD to record.
  • Composite VNFFGD and its referenced nested VNFFGD In this case, NFVO-1 can be indicated in the interface message by extending the interface message.
  • VNFFGD in the NSD is a composite VNFFGD, the nested VNFFGD information referenced in it, VNFFGD Which NFPD is a composite NFPD, the nested NFPD information referenced by it, and the connection point information of the composite NS administrative domain and other nested NS administrative domains, and the connection point information of the connection between different nested NS administrative domains, and above The order relationship between the connection points.
  • Embodiment 6 Creating a VNFFG through an interface message
  • the creation process of the composite VNFFG instance described in Embodiments 4 to 6 is also applicable to the case of not transmitting the composite NSD, but only transmitting the composite VNFFGD information in the interface message, taking the fourth embodiment as an example, if the composite NSD is added If the composite VNFFGD information is not included, as shown in FIG. 10, the OSS needs to carry the following information in the step S1002, based on the description of step S602:
  • Instructions for adding a VNFFG instance indicating that a composite VNFFG instance is to be added.
  • VNFFGD IDs the VNFFGD ID has been recorded in the composite NSD on the shelf;
  • Each composite VNFFGD ID corresponds to a composite VNFFGD information
  • each composite VNFFGD information includes the following information:
  • one or more nested VNFFGD information referenced by the composite VNFFGD corresponding to the VNFFGD ID, and each nested VNFFGD information includes: a nested NSN ID to which the nested VNFFGD belongs, and a nested VNFFGD ID.
  • the nested VNFFGD ID is an identifier of a certain VNFFGD within the nested NSD;
  • Each composite NFPD ID corresponds to a composite NFPD information
  • each composite NFPD information contains the following information:
  • the one or more nested NFPD information referenced by the composite NFPD corresponding to the NFPD ID, and each nested NFPD information includes: a nested NSD ID to which the nested NFPD belongs, and a nested NFPD ID.
  • the nested NFPD ID is an identifier of a certain NFPD within the nested NSD;
  • NFVO-1 parses out the composite VNFFGD information according to the above interface message, and combines the information of the nested NSD recorded in the composite NSD to determine the VNFFGD ID and NFPD ID information of each nested NSD, and Information about which composite VNFFGD/NFPD is referenced.
  • NFVO-1 initiates the creation of a nested VNFFG instance and a nested NFP instance in steps S1004 and thereafter, and the related process description is described with reference to Embodiment 4.
  • each network element such as a UE, a base station, a core network entity, etc.
  • each network element such as a UE, a base station, a core network entity, etc.
  • each network element such as a UE, a base station, a core network entity, etc.
  • each network element includes corresponding hardware structures and/or software modules for performing various functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • Example 7 Having a composite NFVO (such as NFVO-1) function or a nested NFVO (such as NFVO-2) function or Computer equipment that operates a maintenance entity (such as OSS)
  • NFVO-1 i.e., composite NFVO
  • NFVO-2 i.e., nested NFVO
  • OSS i.e., operational maintenance entity
  • FIG. 11 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 1100 includes at least one processor 1101, a communication bus 1102, a memory 1103, and at least one communication interface 1104.
  • the processor 1101 may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more of the programs for controlling the execution of the program of the present invention. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 1102 can include a path for communicating information between the components described above.
  • the communication interface 1104 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 1103 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 1103 is used to store application code for executing the solution of the present invention, and is controlled by the processor 1101 to execute.
  • the processor 1101 is configured to execute the application code stored in the memory 1103, thereby implementing the functions of NFVO-1 (ie, composite NFVO) or NFVO-2 (ie, nested NFVO) or OSS (ie, operation and maintenance entity) in the embodiment of the present invention. .
  • the processor 1101 may include one or more CPUs, for example. CPU0 and CPU1 in Figure 11.
  • computer device 1100 can include multiple processors, such as processor 1101 and processor 1108 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 1100 can also include an output device 1105 and an input device 1106.
  • the output device 1105 is in communication with the processor 1101 and can display information in a variety of ways.
  • the output device 1105 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 1106 is in communication with processor 1101 and can accept user input in a variety of ways.
  • input device 1106 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 1100 described above may be a general purpose computer device or a special purpose computer device.
  • the computer device 1100 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have the FIG. A device of similar structure.
  • PDA personal digital assistant
  • Embodiments of the invention do not limit the type of computer device 1100.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) , Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer.
  • the computer instructions can be stored or transmitted using a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)).
  • SSD Solid State Disk

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明涉及通信技术领域，尤其涉及网络功能虚拟化架构下管理VNFFG(Virtual Network Function Forward Graph，虚拟网络功能转发图)的技术。在一种管理VNFFG的方法中，构建复合NS(Network Service，网络服务)的VNFFGD(Virtual Network Function Forward Graph Descriptor，虚拟网络功能转发图描述符)与其所引用的嵌套NS的VNFFGD的引用和对接关系，及复合NS的VNFFGD中的NFPD(Network Forward Path Descriptor，网络转发路径描述符)与其所引用的嵌套NS的NFPD的引用和对接关系；在复合NS管理域的NFVO实例化复合NS管理域的VNFFG/NFP时，同步触发嵌套NS管理域的NFVO实例化其被引用的嵌套VNFFG/NFP。从而在跨管理域提供复合NS的场景下，将复合NS的VNFFG/NFP及其所引用的各嵌套NS的VNFFG/NFP关联起来，提供端到端完整的业务转发图。

Description

一种管理VNFFG的方法、装置和*** 技术领域
本发明涉及通信技术领域，尤其涉及一种管理VNFFG(Virtual Network Function Forward Graph，虚拟网络功能转发图)的方法、装置和***。
背景技术
网络功能虚拟化(NFV,Network Function Virtualization)是电信网络运营商通过借鉴信息技术(IT,Information Technology)领域的虚拟化技术，在通用的云服务器、交换机和存储器中将部分电信网络功能的实现进行软件和硬件解耦，从而实现网络服务(NS,Network Service)快速、高效部署。网络集成商或运营商用网络服务描述符(Network Service Descriptor，NSD)展现网络规划的结果，并将NSD上架(On-board)到网络功能虚拟化编排器(NFV Orchestrator，简称NFVO)，并根据需要将NSD所描述的网络规划实例化成NS实例。上架可以理解为，将必要的NS或虚拟网络功能(Virtual Network Funct ion，VNF)相关的软件包、描述符文件等，注册到NFVO。实例化的过程可以理解为按描述符文件分配虚拟资源和物理资源，比如分配虚拟物理链路，网络端口号等，并在所分配资源上加载计算机程序软件的过程。一个NS实例最基础的组成部分包含虚拟网络功能(Virtual Network Function，VNF)、虚拟链路(Virtual Link，VL)，还包含一个或多个VNF转发图(VNF forward Graph，VNFFG)。每个VNFFG用于描述NS上提供的某种业务进行在电信网络内部进行转发时所需要的电信网络资源和不同转发规则对应的网络转发路径(Network Forward Path，NFP)。VNFFG可以理解为是NFV上的业务链Service Chain，业务数据包怎么转发，是根据VNFFG中的转发规则，也就是NFP来确定的。
在实际的NFV应用中，可能存在多个管理域互联的场景，管理域指由一个独立的组织所运营的***或网络，每个管理域由NFVO负责该管理域内的网络服务的提供。例如，在中国、美国这样的国家，一个运营商的不同省公司可以各自运营一个独立的NS管理域，它们共同组成一个大的运营商网络；在欧洲，大的 运营商在各个国家也可以部署独立的NFVO管理域，通过互联形成完整的运营商网络。在某些场景中，可能存在跨越两个或多个NFVO域之间的网络服务形成一个复合网络服务(复合NS，Composite NS)，在复合NS的层级结构中包含多个嵌套NS(Nested NS)，每个嵌套NS由不同于复合NS的管理域提供。复合NS对应的NSD称为复合NSD，其所引用的嵌套NS对应的NSD称为嵌套NSD。
目前，业界NFV技术的研究对跨管理域的复合NS研究仍在起步阶段，缺乏端到端可行的业务方案，无法支撑复合NS业务的有效开展。
发明内容
本发明实施例描述了一种管理VNFFG方法、装置和***，构建复合NS的VNFFGD(Virtual Network Function Forward Graph Descriptor，虚拟网络功能转发图描述符)与其所引用的嵌套NS的VNFFGD的引用和对接关系，及复合NS的VNFFGD中的NFPD(Network Forward Path Descriptor，网络转发路径描述符)与其所引用的嵌套NS的NFPD的引用和对接关系；以实现复合NS管理域的VNFFG/NFP及其所引用的嵌套NS管理域的VNFFG/NFP的协同操作，如新增或删除。从而在跨管理域提供复合NS的场景下，将复合NS的VNFFG/NFP及其所引用的各嵌套NS的VNFFG/NFP关联起来，提供端到端完整的业务转发图，满足复合NS下的业务需求。
第一方面，本发明实施例提供一种关联复合NS的VNFFGD和NFPD与其所引用的嵌套NS的VNFFGD和NFPD的方法，包括：
复合NSD中包含一个或多个VNFFGD，所述VNFFGD中可以包含一个或多个引用的嵌套VNFFGD信息。所述嵌套VNFFGD为嵌套NSD中包含的某个VNFFGD。为引述方便，本申请中将包含了一个或多个与嵌套VNFFGD的VNFFGD称为复合VNFFGD。所述嵌套VNFFGD信息至少包含，嵌套VNFFGD所归属的嵌套NSD ID(标识，Identity)，嵌套VNFFGD ID。所述嵌套VNFFGD ID为嵌套NSD内唯一的某条VNFFGD的标识。
复合VNFFGD中还包含复合NS管理域内VNF和PNF连接点信息，以及复合NS管 理域与其它嵌套NS管理域连接的连接点信息，以及不同嵌套NS管理域之间连接的连接点信息，以及以上所述连接点之间的顺序关系。
复合VNFFGD中还包含一个或多个NFPD，所述NFPD中可以包含一个或多个引用的嵌套NFPD信息。为引述方便，本申请中将包含了一个或多个与嵌套NFPD的NFPD称为复合NFPD。复合NFPD描述了复合NS管理域内VNF和PNF连接点之间，以及复合NS与嵌套NS之间，以及不同的嵌套NS之间的转发规则。所述嵌套NFPD为嵌套VNFFGD中包含的某个NFPD。所述嵌套NFPD信息至少包含，嵌套NFPD所归属的嵌套NSD ID，嵌套NFPD ID。所述嵌套NFPD ID为嵌套NSD内唯一的某条NFPD的标识。嵌套NFPD描述了嵌套NS内VNF和PNF连接点之间的转发规则。
该方法在VNFFGD和NFPD中增加了其所引用的一个或多个嵌套VNFFGD或嵌套NFPD，将不同NS管理域中原本孤立的VNFFGD关联起来，形成一个全局性的复合VNFFGD和复合NFPD，使得复合NS业务能够在嵌套NS管理域间端到端进行转发。
第二方面，本发明实施例提供一种管理VNFFG的方法，包括：
OSS/BSS(Operational Support System/Business Support System，运营支撑***/业务支撑***)或复合NFVO本身的操作维护客户端或其它运营维护实体，向NFVO-1(为引述方便，本申请中以NFVO-1代表复合NS管理域的NFVO)，发送创建复合NS实例并实例化复合NS的请求，NFVO-1根据请求消息中的NSD ID实例化复合NS，并根据复合NSD中VNFFGD的描述，实例化本管理域内的VNFFG和NFP。当所述复合NSD中的VNFFGD为复合VNFFGD时，NFVO-1还要发起嵌套VNFFG和嵌套NFP的实例化流程。需要指出的是：复合NS管理域内的VNFFG和NFP的实例化流程，与发起嵌套NS管理域内VNFFG和NFP的实例化流程，顺序上不分先后；某个复合VNFFGD可能引用多个嵌套NS的VNFFGD，每个嵌套NS对应不同的NFVO，NFVO-1需要向每个嵌套NS对应的NFVO发起实例化NS请求，在本申请的描述中，仅以NFVO-2为例，代表所有嵌套NS的NFVO。另外需要指出的是，在实例化复合NS和嵌套NS之前，复合NSD和嵌套NSD会分别被上架到复合NS管理域和嵌套NS管理域，其中复合NS管理域的NFVO-1还可以通过订阅或查询等方式，获知复合NS所引用的嵌套NS的实例化情况(如，是否已经实例化)和嵌套NS所在管理域的 NFVO-2的信息。
NFVO-1发起嵌套VNFFG和嵌套NFP的实例化流程：NFVO-1根据复合VNFFGD中所记录的嵌套NSD信息，并根据嵌套NSD和嵌套NS管理域间的映射关系，确定嵌套NSD归属的NS管理域。NFVO-1通过订阅或其它手段获知所述嵌套NSD归属的NS管理域嵌套NS的实例化情况：
一种情况下，所述嵌套NSD归属的NS管理域没有完成嵌套NS的实例化：则NFVO-1向NFVO-2请求并获得嵌套NS的实例ID，并向NFVO-2发起实例化嵌套NS的请求，请求中携带至少包含嵌套NS的实例ID。可选的，根据复合VNFFGD和复合NFPD中记录的嵌套VNFFGD和嵌套NFPD信息，NFVO-1发给NFVO-2的实例化嵌套NS的请求中携带增加VNFFG实例的指示，复合VNFFGD所引用的一个或多个嵌套VNFFGD ID，和复合NFPD所引用的一个或多个嵌套NFPD ID。NFVO-2收到实例化NS请求消息，根据请求消息中的NSD信息实例化NS。如果请求消息中携带了增加VNFFG实例的指示，嵌套VNFFGD ID和嵌套NFPD ID，则NFVO-2可以选择只实例化嵌套VNFFGD ID和嵌套NFPD ID所对应的VNFFG和NFP。NFVO-2完成实例化后，向NFVO-1返回嵌套VNFFGD和嵌套NFPD对应的嵌套VNFFG实例ID和嵌套NFP实例ID。可选的，NFVO-2还可以记录嵌套VNFFG实例和嵌套NFP实例被哪个复合NS所引用，以支持一个VNFFG实例或一个嵌套NFP实例被多个复合NS所引用的情况。NFVO-1记录复合VNFFG和复合NFP所引用的嵌套VNFFG实例ID和嵌套NFP实例ID，以便于后续进行关联管理。
另一种情况下，所述嵌套NSD归属的NS管理域已经完成嵌套NS的实例化：则NFVO-1向NFVO-2发起更新嵌套NS实例的请求，请求消息中至少包含复合NS的实例ID，增加VNFFG实例的指示，复合VNFFGD所引用的一个或多个嵌套VNFFGD ID，和复合NFPD所引用的一个或多个嵌套NFPD ID。NFVO-2收到更新嵌套NS实例的请求，根据请求消息中增加VNFFG实例的指示，嵌套VNFFGD ID和嵌套NFPD ID，实例化嵌套NS实例中的VNFFG和NFP。NFVO-2实例化完成后，向NFVO-1返回嵌套VNFFGD和嵌套NFPD对应的嵌套VNFFG实例ID和嵌套NFP实例ID。可选的，NFVO-2还可以记录嵌套VNFFG实例和嵌套NFP实例被哪个复合NS所引用，以支持一个 VNFFG实例或一个嵌套NFP实例被多个复合NS所引用的情况。NFVO-1记录复合VNFFG和复合NFP所引用的嵌套VNFFG实例ID和嵌套NFP实例ID，以便于后续进行关联管理。
所述第二方面提供的创建复合VNFFG和复合NFP实例的方法，所依赖的前提或假设是在NFVO-1实例化复合NS时，在已上架的复合NSD中已经存在根据第一方面所述方法描述的复合VNFFGD/复合NFPD。如果在NFVO-1实例化复合NS时，在已上架的复合NSD中没有记录复合VNFFGD/复合NFPD，或者在NFVO-1完成复合NS的实例化之后，在复合NSD中新增了一条或多条复合VNFFGD/复合NFPD，则需要将复合NSD重新上架，并通过更新复合NS实例的流程来创建复合VNFFG和复合NFP实例。在一种可能的设计中，或复合NFVO本身的操作维护客户端或其它运营维护实体向NFVO-1发送更新复合NS实例的请求，请求消息中至少包含复合NS的实例ID，增加VNFFG实例的指示，复合VNFFGD ID和复合NFPD ID。NFVO-1根据请求消息，实例化本管理域内的VNFFG和NFP，并发起嵌套VNFFG和嵌套NFP的实例化流程。所述发起嵌套VNFFG和嵌套NFP的实例化流程与第二方面所述方法中嵌套VNFFG和嵌套NFP的实例化流程一致。
在第二方面所述的一种创建复合VNFFG和复合NFP实例的方法中，NFVO-1基于第一方面所述的在复合NSD模板中记录的复合VNFFGD/复合NFPD，发起嵌套VNFFG和嵌套NFP的实例化流程。在另一种可能的实现方式中，可以不在复合NSD的VNFFGD中记录其所引用的嵌套VNFFGD及嵌套NFPD的信息，而是在或复合NFVO本身的操作维护客户端或其它运营维护实体发给NFVO-1的创建或更新复合NS实例的请求消息中携带复合VNFFGD所引用的嵌套VNFFGD信息和复合NFPD所引用的嵌套NFPD信息，NFVO-1通过接口消息中的信息获知复合VNFFGD/复合NFPD，并发起嵌套VNFFG和嵌套NFP的实例化流程。
根据第二方面所述方法创建一个或多个复合VNFFG和复合NFP实例之后，如果需要删除某个复合VNFFG实例，则需要同步删除复合VNFFG所引用的嵌套VNFFG。在一种可能的设计中，或复合NFVO本身的操作维护客户端或其它运营维护实体向NFVO-1发送更新复合NS实例的请求，请求消息中至少携带复合NS实例 ID，删除VNFFG实例的指示和复合VNFFG实例ID。NFVO-1根据请求消息，删除复合NS管理域内的VNFFG，并向NFVO-2发送更新嵌套NS实例的请求，请求消息中携带删除VNFFG实例的指示，要删除的嵌套VNFFG实例ID和要删除的嵌套NFP实例ID。NFVO-2根据收到的请求消息，删除本管理域的嵌套VNFFG实例和嵌套NFP实例。当嵌套VNFFG实例或嵌套NFP实例被多个复合NS所引用时，NFVO-2还需要判断要删除的嵌套VNFFG实例或嵌套NFP实例是否被其它复合NS所引用，如果还被其它复合NS引用，则NFVO-2仅删除嵌套VNFFG实例或嵌套NFP实例与所述发送请求消息的复合NS的引用关系，如果不被其它复合NS引用，则NFVO-2删除嵌套VNFFG实例或嵌套NFP实例。
根据第二方面所述方法创建一个或多个复合VNFFG和复合NFP实例之后，如果复合VNFFGD或复合NFPD发生变更，例如新增或删除引用的嵌套VNFFGD或嵌套NFPD，则需要同步更新复合VNFFGD或复合NFPD所对应的VNFFG实例或NFP实例。一种可能的设计中，或复合NFVO本身的操作维护客户端或其它运营维护实体可以先删除旧的VNFFGD对应的复合VNFFG实例，再根据更新后的VNFFGD创建新的复合VNFFG实例。
第三方面，本发明实施例提供一种复合NS管理域的NFVO，该复合NS管理域的NFVO实现上述第二方面中NFVO-1的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
一种情况下，本发明实施例提供的一种复合NS管理域的NFVO，包括，通信接口，用于接收实例化复合NS或更新复合NS的请求消息并返回相应的响应消息，还用于发送实例化嵌套NS或更新嵌套NS实例的请求并接收相应的响应消息；存储器，用于存储计算机执行指令和复合NS及其所引用的嵌套NS的相关信息，包括复合VNFFG实例所引用的嵌套VNFFG实例标识，和复合NFP实例所引用的嵌套NFPD实例标识；处理器，通过总线与存储器和通信接口连接，当通信接口接收实例化复合NS或更新复合NS的请求消息，处理器执行存储器中存储的计算机执行指令，以完成第二方面所述方法中NFVO-1的功能。
第四方面，本发明实施例提供一种嵌套NS管理域的NFVO，该嵌套NS管理域的NFVO实现上述第二方面中NFVO-2的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
一种情况下，本发明实施例提供的一种嵌套NS管理域的NFVO，包括，通信接口，用于接收实例化嵌套NS或更新嵌套NS的请求消息并返回相应的响应消息；存储器，用于存储计算机执行指令；处理器，通过总线与存储器和通信接口连接，当通信接口接收实例化嵌套NS或更新嵌套NS的请求消息，处理器执行存储器中存储的计算机执行指令，以完成第二方面所述方法中NFVO-2的功能。
第五方面，本发明实施例提供一种运营维护实体，具体可以是OSS/BSS或复合NFVO本身的操作维护客户端或其它运营维护实体，该运营维护实体实现上述第二方面中OSS/BSS或复合NFVO本身的操作维护客户端或其它运营维护实体的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
一种情况下，本发明实施例提供的一种运营维护实体，包括，通信接口，用于向复合NFVO发送实例化复合NS或更新复合NS的请求消息，触发创建或删除复合VNFFG实例及其所引用的嵌套VNFFG实例，和复合NFP实例及其所引用的嵌套NFP实例的流程；存储器，用于存储计算机执行指令；处理器，通过总线与存储器和通信接口连接，生成要发送的请求消息并处理通信接口接收到的消息。
第六方面，本发明实施例提供了一种管理VNFFG的***，该***包括如第三方面所述的复合NS管理域的NFVO，和如第四方面所述的嵌套NS管理域的NFVO和如第五方面所述的运营维护实体。
第七方面，本发明实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本发明实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
通过如上创建或删除复合VNFFG实例和复合NFP实例的方法、装置和***，在复合NS的场景下，能够将多个NS管理域的VNFFG组合关联起来，组成端到端的复合VNFFG业务链，提供新的组合业务服务，提升网络价值。随着NFV技术的更新演进，本申请中所引述的网络功能实体或技术术语的名称可能会发生变更，但并不影响本申请所述方法的使用。同样，本申请所述方法可以扩展应用于基于NFV架构的5G切片领域，一种情况下，一个5G切片部署在一个管理域中，多个部署在不同管理域中的5G切片联合提供一个完整的5G网络服务；另一种情况下，一个5G切片独立提供一个完整的5G网络服务，该5G切片被分割成多个组成部分，分别部署于多个不同的管理域中，如上两种情况下，管理域间端到端业务链的创建和维护同样可以使用本申请中所述方法。
附图说明
下面将参照所示附图对本发明实施例进行更详细的描述：
图1为本发明实施例提供的一种NFV***架构示意图；
图2为本发明实施例提供的一种复合NS***架构***架构示意图；
图3为本发明实施例提供的一种复合NS架构下各管理域的VNFFG和NFP示意图；
图4为本发明实施例提供的一种记录和管理复合VNFFGD的示例
图5为本发明实施例提供的一种复合NS架构下各管理域的VNFFG和NFP互联示意图；
图6为本发明实施例提供的一种Top-Down方式创建复合VNFFG的流程示意图；
图7为本发明实施例提供的一种Bottom-Up方式创建复合VNFFG的流程示意图；
图8为本发明实施例提供的一种新增复合VNFFG的流程示意图；
图9为本发明实施例提供的一种删除复合VNFFG的流程示意图；
图10为本发明实施例提供的一种通过接口消息创建VNFFG的流程示意图；
图11为本发明实施例提供的一种计算机设备示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
实施例一：***架构与本申请技术方案概述
本实施例用于展示本发明可能被应用的一种可能的NFV***架构和一种可能的复合NS***架构。如图1所示，NFV***(100)包括，运营支撑***/业务支撑***(Operation Support System/Business Support System，简称OSS/BSS)(101)、网元管理***(Element Management System，简称EMS)(102)、虚拟网络功能(Virtualized Network Function，简称VNF)(103)、网络功能虚拟化基础设施(Network Function Virtualization Infrastructure，简称NFVI)(104)以及NFV管理和编排***(NFV Management and Orchestration，简称NFV MANO)(105)。其中，NFV MANO包括网络功能虚拟化编排器(NFV Orchestrator，简称NFVO)(106)、虚拟网络功能管理器(Virtualized Network Function Manager，简称VNFM)(107)、虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)(108)以及一个服务、VNF和基础设施说明单元(Service，VNF and Infrastructure Description)(109)。其中，与本发明比较相关的功能实体及其主要功能如下：
OSS/BSS(101)：主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括触发NSD，VNFFGD，NFPD等各类描述符的上架，更新，实例化等。
NFVO(106)：实现NSD、本管理域内虚拟网络功能转发图(Virtualised Network Function Forwarding Graph，VNFFG)的管理及处理，网络服务生命周期的管理，并与VNFM配合实现VNF的生命周期管理和资源的全局视图功能。
VNFM(107)：实现虚拟化网元VNF的生命周期管理，包括VNFD的管理及处理，VNF实例的初始化，VNF的扩容/缩容，VNF实例的终止。支持接收NFVO下发的弹性伸缩(scaling)策略，实现VNF的弹性伸缩。
VIM(108)：主要负责基础设施层硬件资源，虚拟化资源的管理，监控和故障上报，面向上层应用提供虚拟化资源池。
描述符说明单元(109)：主要记录网络服务描述符(Network Service Descriptor，NSD)，虚拟网关功能描述符(VNF Descriptor，VNFD)，物理网关功能描述符(Physical Network Function Descriptor，PNFD)，虚拟链路描述符(Virtual Link Descriptor，VLD)，虚拟网络功能转发图描述符(Virtual Network Function Descriptor,VNFFGD)，嵌套NSD(Nested NSD)等NFV***相关的描述符信息。
在实际的NFV应用中，可能存在多个跨管理域互联的场景，每个管理域包括一个NFVO，用于负责该管理域内的一组特定集合的网络服务的提供。图2为一个跨管理域的复合NS***架构示意图，该***包括NFVO管理域A(201)，其提供NS A；NFVO管理域B(202)，其提供NS B；NFVO管理域C(203)，其提供NS C。NFVO管理域A要提供NS A，需要NFVO管理域B和NFVO管理域C所提供的NS，NS A被称为复合NS，NS B和NS C被称为嵌套NS。复合NS管理域和嵌套NS管理域的NFVO形成一个伞状的管理架构，NFVO-1(204)负责复合NS的编排管理，NFVO-2(205)和NFVO-3(206)负责各自嵌套NS的编排管理，NFVO-1(204)和NFVO-2(205)/NFVO-3(206)间通过Or-Or接口完成跨NFVO管理域的复合NS的生命周期管理。本申请中将复合NS管理域的NFVO用NFVO-1来表述；嵌套NS管理域中的NFVO，如NFVO-2或NFVO-3，统一用NFVO-2来表述。需要说明的是，图2中的OSS/BSS，也可以是NFVO-1本身的操作维护客户端或其它运营维护实体，本申请实施例中仅以OSS/BSS为例进行描述，本发明实施例中所描述的与OSS/BSS相关的方法同样适用于NFVO-1本身的操作维护客户端或其它运营维护实体。
每个NFVO管理域所在的NFV***存在多个VNF，每个VNF上会分配对外连接的连接点(connection point)，管理域内部网络服务的数据包怎么走，是根据VNFFG来确定的，也就是说VNFFG会描述需要用到的各连接点CP信息和连接点间的顺序关系。连接点间的路径转发规则由NFP来定义，同一个VNFFG可能包含多个NFP。图3以图2所示的复合NS***架构为基础，给出了一种可能的跨管理域提 供复合NS的场景下，不同管理域内的VNFFG和NFP示例。图3中NFVO管理域A，NFVO管理域B和NFVO管理域C的介绍及它们之间的关系参见图2及其描述。
图3中，假设NFVO管理域A中的VNF设备对应于网络用户数据存储器HSS/HLR，鉴权服务器AAA等设备；复合NS管理域A中存在两种VNFFG分别用于描述不同业务场景下的业务转发路径：例如，VNFFG01是视频业务的VNF转发图，其中包含业务转发规则NFP011；VNFFG02是VoLTE业务的VNF转发图，其中包含业务转发规则NFP021。
图3中，假设NFVO管理域B中的VNF设备可以是对应于无线网络的基站eNodeB设备和EPC网络中的PDN gateway和MME等设备；NFVO管理域B中存在3种VNFFG分别用于描述不同业务场景下的业务转发路径：VNFFG11是视频业务的VNF转发图，其中包含业务转发规则NFP111；VNFFG12是VoLTE业务的VNF转发图，其中包含业务转发规则NFP121；VNFFG13是手机web业务的VNF转发图，其中包含业务转发规则NFP131。
图3中，假设NFVO管理域C中的VNF设备可能对应于IMS核心网中的SBC，P-CSCF，S-CSCF和AS等设备。NFVO管理域C中存在2种VNFFG分别用于描述不同业务场景下的业务转发路径：VNFFG21用于描述视频和VoLTE业务的VNF转发图，其中NFP211用于描述视频的业务转发规则，NFP212用于描述VoLTE业务的业务转发规则；VNFFG22用于描述会议业务的VNF转发图，其中包含业务转发规则NFP221。
当NFVO管理域A需要NFVO管理域B和NFVO管理域C联合提供端到端的VoLTE业务(即复合NS)时，由于各管理域内的VNFFG和NFP是孤立的，嵌套NS之间的VNFFG和NFP缺乏关联，无法形成一个全局性的复合VNFFG或复合NFP，业务无法在管理域间进行准确转发。需要提供一种方案能够描述复合NS管理域内端到端业务如何转发，比如嵌套NS管理域1中的NFP121中的CP134连接点应该将业务包转发至复合NS管理域中的哪个连接点(CP011还是CP013)。
为了在跨管理域的复合NS场景下，提供端到端的业务链或VNF转发图(具体在本发明中即复合VNFFG)，本发明实施例基于图2所示的复合NS***架构，提出了一种管理VNFFG的方法、装置和***。在本发明实施例中，OSS，NFVO-1和NFVO-2 分别具备如下功能：
OSS/BSS：在复合NS实例化后，如果在复合NSD中新增复合VNFFGD，则OSS支持发送更新(Update)NS的请求消息给NFVO-1，请求消息中携带要新增的VNFFGD ID和新增VNFFG实例的指示；如果在复合NSD中删除复合VNFFGD，则OSS支持发送更新(Update)NS的请求消息给NFVO-1，请求消息中携带删除的复合VNFFGD对应的VNFFG实例ID和删除VNFFG实例的指示；如果在复合NSD中更新复合VNFFGD，则OSS支持发送更新(Update)NS的请求消息给NFVO-1，请求消息中携带更新的复合VNFFGD对应的VNFFG实例ID和更新VNFFG实例的指示。如果复合VNFFGD及其引用的嵌套VNFFGD的信息不在复合NSD中进行描述，则需要OSS在新增或更新NS实例的请求消息中，携带复合VNFFGD及其引用的嵌套VNFFGD的信息，具体如何描述复合VNFFGD及其引用的嵌套VNFFGD的信息参见实施例六中的描述。OSS支持记录复合NS实例下的复合VNFFG实例ID，及其对应的VNFFGD ID。
NFVO-1：在根据创建NS实例请求消息创建NS实例的过程中，如果NS实例对应的NSD中包含复合VNFFGD，则NFVO-1支持在本管理域新增VNFFG实例和NFP实例，并且根据复合VNFFGD及其引用的嵌套VNFFGD的信息和复合NFPD及其引用的嵌套NFPD的信息，发送实例化嵌套NS或更新嵌套NS实例的请求，请求所述嵌套NFVO创建嵌套VNFFG实例和嵌套NFP实例，该请求消息包含嵌套NS实例标识，还可以包含增加VNFFG的指示，一个或多个嵌套VNFFGD标识，一个或多个嵌套NFPD标识；在根据更新NS实例请求消息更新NS实例的过程中，如果收到请求消息中包含新增或删除VNFFG的指示，则NFVO-1支持在本管理域新增或删除VNFFG实例和NFP实例，并且根据复合VNFFGD及其引用的嵌套VNFFGD的信息和复合NFPD及其引用的嵌套NFPD的信息，发送更新嵌套NS实例的请求消息到嵌套NS对应的NFVO，请求所述嵌套NFVO创建嵌套VNFFG实例和嵌套NFP实例，该请求消息包含嵌套NS实例标识，还包含增加VNFFG的指示，一个或多个嵌套VNFFGD标识，一个或多个嵌套NFPD标识。NFVO-1支持记录复合VNFFGD及其引用的嵌套VNFFGD信息，支持记录复合VNFFG实例标识及其引用的嵌套VNFFG实例标识。
NFVO-2：如果收到来自NFVO-1的实例化嵌套NS或更新嵌套NS的请求消息中， 包含新增或删除VNFFG的指示，则NFVO-2支持根据消息中的指示新增或删除嵌套VNFFG实例和嵌套NFP实例，并向NFVO-1返回根据请求消息新增的嵌套VNFFG实例ID和嵌套NFP实例ID。
图4给出了记录和管理复合VNFFGD的一个示例：复合NSD中包含一个或多个VNFFGD，所述VNFFGD中可以包含一个或多个引用的嵌套VNFFGD信息。所述嵌套VNFFGD信息至少包含，嵌套VNFFGD所归属的嵌套NSD ID，嵌套VNFFGD ID。所述嵌套VNFFGD ID为嵌套NSD内唯一的某条VNFFGD的标识。
复合VNFFGD中的cpdpool ID列表包含了复合NS管理域内VNF和PNF连接点信息，以及复合NS管理域与其它嵌套NS管理域连接的连接点信息，以及不同嵌套NS管理域之间连接的连接点信息，以及以上所述连接点之间的顺序关系。
复合VNFFGD中还包含一个或多个NFPD，所述NFPD中可以包含一个或多个引用的嵌套NFPD信息。复合NFPD的nfpRule描述了复合NS管理域内VNF和PNF连接点之间，以及复合NS与嵌套NS之间，以及不同的嵌套NS之间的转发规则。所述嵌套NFPD信息至少包含，嵌套NFPD所归属的嵌套NSD ID，嵌套NFPD ID。所述嵌套NFPD ID为嵌套NSD内唯一的某条NFPD的标识。嵌套NFPD描述了嵌套NS管理域内VNF和PNF连接点之间的转发规则。
以图3及其描述为假设前提，以图5为例，描述如何通过图4中所述方法来关联不同管理域中的VNFFG和NFP，以提供跨管理域的端到端的复合VNFFG业务链。
复合NS A对应的NSD0(复合NSD)引用两个嵌套NSD，NSD1和NSD2；NSD1在复合NSD中标识为1，NSD2在复合NSD中标识为2；嵌套NS B是基于NSD1的实例，嵌套NS C是基于NSD2的实例；
VNFFG02和NFP021对应的描述符分别是VNFFGD02和NFPD021，其中VNFFGD02在NSD0中的标识为02，NFPD021在NSD中的标识为021；
VNFFG12和NFP121对应的描述符分别是VNFFGD12和NFPD121，其中VNFFGD12在NSD1中的标识为12，NFPD121在NSD中的标识为121；
VNFFG21和NFP211对应的描述符分别是VNFFGD21和NFPD211，其中VNFFGD21在NSD2中的标识为21，NFPD212在NSD2中的标识为212；
假设图5中所有CP连接点所对应的CPD(连接点描述符)在其所在NSD中的标识即为CP连接点标号中的数字编号，如CP111对应的CPD在NSD1中的标识为111，CP023对应的CPD在NSD0中的标识为023。
复合NS的视频业务转发图描述符VNFFGD02需要引用VNFFGD12/NFPD121，和VNFFGD21/NFPD212。
基于如上假设，复合NS所对应的NSD中记录的VNFFGD02(即复合VNFFGD)至少应包含如下表一、表二和表三中的信息：
表一描述了VNFFGD02中记录的其所引用的嵌套VNFFGD的信息：
Figure PCTCN2016113955-appb-000001
表一
表二描述了VNFFGD2中记录的NFVO管理域A内VNFFGD02的所有连接点，NFVO管理域B和NFVO管理域C中对外与VNFFGD02连接的连接点：
Figure PCTCN2016113955-appb-000002
表二
表三描述了VNFFGD2中记录的NFPD021所引用的嵌套NFPD的信息：
Figure PCTCN2016113955-appb-000003
表三
其中，NFPD021描述cpdPool Id中连接点的转发规则，NFVO管理域B和NFVO管理域 C内的CPD信息在VNFFGD12和VNFFGD21中描述，各CPD间的转发规则在NFPD121和NFPD212中描述。
根据实施例一中描述的复合NS***架构和复合VNFFGD的功能介绍，在如下实施例中给出不同场景下创建或删除复合VNFFG的示意流程图。
实施例二：Top-Down方式创建复合VNFFG
Top-Down方式指在实例化复合NS的过程中，由NFVO-1负责向嵌套NS所在管理域的NFVO-2发起嵌套NS的实例化。NFVO-1作为复合NS网络的中心控制节点，整体掌控复合NS管理域及其所引用的嵌套NS管理域。
图6描述了一种创建复合VNFFG和复合NFP实例的流程示意图，图中OSS，NFVO-1和NFVO-2间的网络位置及相互关系可以参考图2所示，其中NFVO-2代表所有可能嵌套NS所在管理域的NFVO。
S600：复合NSD已经设计完毕并上架到NFVO-1；引用的嵌套NSD已经上架到NFVO-2。在复合NSD上架过程中，NFVO-1得到了各嵌套NSD所属的NFVO-2的信息。复合NSD中包含了复合VNFFGD的信息。
S601：OSS向NFVO-1请求创建复合NS实例的ID，携带复合NSD的ID信息；NFVO-1为此请求分配复合NS的实例ID，将此ID返回给OSS。
S602：OSS向NFVO-1请求实例化复合NS，请求消息中至少包含第S601步分配的复合NS实例ID。
S603：NFVO-1根据此实例ID，获得复合NSD的信息；根据复合NSD中的描述信息，确定各嵌套NSD被引用的VNFFGD ID和NFPD ID信息，以及其被哪个复合VNFFGD/NFPD引用的信息。
S604：NFVO-1根据嵌套NSD ID与NFVO-2的映射关系，向各嵌套NSD对应的NFVO-2发起创建嵌套NS实例ID的请求，请求中携带嵌套NSD ID信息。所述嵌套NSD ID与NFVO-2的映射关系，NFVO-1可以通过向其它NFVO订阅的方式获取，通过订阅，NFVO-1可以获取其它NFVO上架的NSD及其对应的NS实例状态等信息，此为现有技术，不在此赘述。NFVO-2为此请求分配嵌套NS的实例ID，将此ID返回给NFVO-1。
S605：NFVO-1向NFVO-2请求实例化嵌套NS，消息中至少包含S604步骤分配的嵌套NS实例ID，新增VNFFG实例的指示(如在消息中新增一个可选参数AddVnffg，当此参数取值为1时代表要新增VNFFG实例)，S603步骤中得到的该嵌套NSD中被引用的VNFFGD ID+NFPD ID信息。
S606：NFVO-2根据请求实例化嵌套NS，在实例化VNFFG的过程中，可以根据新增VNFFG实例的指示和该嵌套NSD中被引用的VNFFGD ID+NFPD ID信息，从该实例对应的NSD中获取到对应的VNFFG和NFP的信息，创建本域内的VNFFG实例和NFP实例。NFVO-2还需要记录VNFFG实例和NFP实例被NFVO-1所在复合NS所引用。
S607：NFVO-2向NFVO-1发送嵌套NS的实例化结果，结果中告知新增的嵌套VNFFG实例ID。
S608：NFVO-1收到S607消息，记录消息中携带的嵌套VNFFG实例ID。NFVO-1实例化本管理域内NS，以及本管理域内的复合VNFFG和复合NFP。NFVO-1记录本管理域的复合VNFFG实例ID及其所引用的嵌套VNFFG实例ID间的引用关系。需要说明的是，NFVO-1实例化本域NS及其所包含的复合VNFFG的操作，和实例化嵌套NS及其所包含的嵌套VNFFG的操作没有顺序关系，例如，此步骤描述的操作也可以放在S603步骤完成。
S609：NFVO-1向OSS发送复合NS的实例化结果，其中至少包含复合VNFFG实例ID。
需要说明的是，本申请中的示意图旨在清楚描述本申请的发明核心，因此在所有示意图中，一些现有技术中例行的步骤或不包含发明点的步骤可能合并显示或直接省略。以图6为例，S601步骤实际上可能存在多个消息交互；在S602步骤，NFVO-1收到NS实例化请求会返回一个即时响应消息，携带生命周期操作发生的ID，然后在NFVO-1或NFVO-2真正开始实例化NS之前，会向OSS发送一个NS生命周期状态改变的通知，携带生命周期操作发生的ID和开始的指示，然后才开始S603的实例化过程，在真正实例化结束后，会通过S609步骤发送消息给OSS指示实例化操作完成，其中携带生命周期操作发生的ID和结果的指示。图6中，S602和S605消息的即时响应消息和NS生命周期状态改变开始的消息均不再描 述。本申请中的其它流程图，同样采用类似的方式简化描述。
Top-Down方式更便于NFVO-1对复合NS业务做全局性整体的管理，但在实际应用中，各管理域可能还无法完全实现拉通管理，各管理域的嵌套NS还是由OSS分别进行实例化，这种情况下，要创建复合VNFFG就需要使用Bottom-Up方式。Bottom-Up方式指先由OSS向嵌套NS管理域的NFVO-2触发各嵌套NS的实例化，嵌套NS实例化完成后，OSS再向复合NS管理域的NFVO-1触发复合NS的实例化，也就是NFVO-1不负责向NFVO-2触发嵌套NS的实例化。
实施例三：Bottom-Up方式创建复合VNFFG
图7描述了Bottom-Up方式创建复合VNFFG实例的流程示意图，与图6的差别是：
1、OSS首先触发创建的各嵌套NS的实例，如图中S701-S704步骤，在嵌套NS实例化完成后，OSS再向NFVO-1触发复合NS的实例化，如图中S706步骤。其中在S703步骤，NFVO-2可以根据本地策略配置选择暂不执行VNFFG的实例化。
2、在S707步骤中，NFVO-1选择在触发嵌套VNFFG实例化之前，首先实例化本管理域的VNFFG和NFP。NFVO-1根据复合NSD中的描述信息，确定各嵌套NSD被引用的VNFFGD ID和NFPD ID信息，以及其被哪个复合VNFFGD/NFPD引用的信息。NFVO-1通过订阅通知的机制，可以获知NFVO-2的嵌套NS实例标识(比如，NFVO-1向NFVO-2订阅嵌套NS的实例情况，NFVO-2在创建NS实例之后，会发送通知消息给NFVO-1).因此在S708步骤之前，无需再请求NFVO-2分配嵌套NS实例标识。
3、由于嵌套NS已经实例化，因此NFVO-1在S708步骤中直接发送更新NS实例请求消息，消息中至少包含嵌套NS实例ID，新增VNFFG实例的指示(如在消息中新增一个可选参数AddVnffg，当此参数取值为1时代表要新增VNFFG实例)，S707步骤中得到的该嵌套NSD中被引用的VNFFGD ID和NFPD ID信息。NFVO-2收到嵌套NS更新请求消息，在S709步骤中根据请求消息中的指示，实例化被引用的VNFFG和NFP。
4、NFVO-1在收到NFVO-2发送的S710消息后，还要记录本域的复合VNFFG实例ID及其所引用的嵌套VNFFG实例ID间的引用关系。在S711步骤中向OSS返回实 例化复合NS结果响应，其中至少包含复合VNFFG实例ID。
在实际电信网络运营中，还存在一种场景，即最初制定的NSD模板可能并不完善，其中可能缺失部分信息，比如缺少复合VNFFGD的描述信息，这样在复合NS和嵌套NS均已完成实例化之后，运营商需要更新NSD模板，将更新后的NSD模板重新上架，并通过NS的更新流程完成VNFFG的实例化。
实施例四：新增复合VNFFG
图8描述了另一种场景下创建复合VNFFG实例的流程示意图。该场景下复合NS和嵌套NS均已完成实例化流程，但是复合NS实例化所依据的复合NSD模板并没有复合VNFFGD。网络运营商在复合NS和嵌套NS实例化之后更新了复合NSD模板，新增了复合VNFFGD，并通过OSS发起更新复合NS实例的流程。在S803步骤中，OSS请求更新NS实例，其中至少携带复合NS实例ID，新增VNFFG实例的指示和复合VNFFGD ID。NFVO-1在收到请求消息后，在S804步骤中，根据请求消息中的信息，实例化本管理域的VNFFG和NFP，并进一步根据复合NSD中的描述信息，确定请求消息中复合VNFFGD ID所引用的各嵌套NSD的VNFFGD ID和NFPD ID信息。在S805步骤中，NFVO-1向NFVO-2发起更新嵌套NS的请求，请求NFVO-2实例化嵌套NSD被引用的VNFFG和NFP，请求消息的描述及NFVO-2的处理参见S708和S709。其它流程处理参考实施例五，不再赘述。
OSS还可以根据需要删除已建立的复合VNFFG，如复合NS的组成关系发生变化，需要新增或删除嵌套NS，不同管理域间的业务转发路径需要随之发生改变，原来已建立的复合VNFFG失效，可以通过先删除失效的复合VNFFG，再建立新的复合VNFFG来实现复合VNFFG的变更；又或者某条业务转发路径及VNFFG不再需要维护，则需要删除之相关的复合VNFFG。
实施例五：删除复合VNFFG
图9描述了删除复合VNFFG实例的流程示意图。该场景下复合NS和嵌套NS均已完成实例化流程，复合NS中的复合VNFFGD也已经进行了实例化。网络运营商通过OSS删除其中一条VNFFG实例。
在S902步骤中，OSS向NFVO-1发送更新NS实例请求消息，请求中至少携带复 合NS实例ID，删除VNFFG指示，要删除的复合VNFFG实例ID。
NFVO-1在收到请求消息后，在步骤S903中，删除本管理域内所述复合VNFFG实例ID所对应的复合VNFFG实例和其包含的复合NFP实例，并根据之前记录的复合VNFFG实例/复合NFP实例和嵌套VNFFG实例/嵌套NFP实例间的关系，确定复合VNFFG实例/复合NFP实例所引用的嵌套VNFFG实例/嵌套NFP实例，及嵌套VNFFG实例/嵌套NFP实例所归属的嵌套NS。
NFVO-1在S904步骤中向嵌套NS所对应的NFVO-2发送更新嵌套NS实例的请求消息，其中携带嵌套NS实例ID，删除VNFFG指示，要删除的嵌套VNFFG实例ID。
NFVO-2在S905步骤中，首先确定S904消息中所指示的嵌套VNFFG实例是否被NFVO-1之外的其它复合NS管理域所引用，如果不存在其它引用关系，则删除请求消息中所指示的VNFFG实例及其包含的NFP实例；如果存在其它引用关系，则不能删除请求消息中指示的VNFFG实例及其包含的NFP实例；并在S906消息中返回更新嵌套NS实例结果响应消息。
实施例一中给出了一种在NSD中记录复合VNFFGD及其引用的嵌套VNFFGD信息的实现方式，在实际部署中，可能存在一些网络集成商或运营商不希望采用扩展NSD的方式来记录复合VNFFGD及其引用的嵌套VNFFGD，这种情况下可以通过扩展接口消息的方式，在接口消息中指示NFVO-1，NSD中哪些VNFFGD是复合VNFFGD，其所引用的嵌套VNFFGD信息，VNFFGD中哪些NFPD是复合NFPD，其所引用的嵌套NFPD信息，以及复合NS管理域与其它嵌套NS管理域连接的连接点信息，以及不同嵌套NS管理域之间连接的连接点信息，以及以上所述连接点之间的顺序关系。
实施例六：通过接口消息创建VNFFG
实施例四至六中所描述的复合VNFFG实例的创建流程，同样适用于不扩展复合NSD，而仅在接口消息中传递复合VNFFGD信息的情况，以实施例四为例，如果上架的复合NSD中并没有包含复合VNFFGD信息，则如图10所示，OSS在S1002步骤中，在S602步骤描述的基础上，还需要携带如下信息：
1、新增VNFFG实例的指示：表示要新增复合VNFFG实例；
2、一个或多个复合VNFFGD ID：所述VNFFGD ID已记录在上架的复合NSD中；
每个复合VNFFGD ID对应一条复合VNFFGD信息，每条复合VNFFGD信息包含如下信息：
2.1、VNFFGD ID所对应的复合VNFFGD所引用的一个或多个嵌套VNFFGD信息，每个嵌套VNFFGD信息包含：嵌套VNFFGD所归属的嵌套NSD ID，嵌套VNFFGD ID。所述嵌套VNFFGD ID为嵌套NSD内唯一的某条VNFFGD的标识；
2.2、复合VNFFGD中的cpdpool ID列表；
2.3、一个或多个复合NFPD ID；
每个复合NFPD ID对应一条复合NFPD信息，每条复合NFPD信息包含如下信息：
2.3.1、NFPD ID所对应的复合NFPD所引用的一个或多个嵌套NFPD信息，每个嵌套NFPD信息包含：嵌套NFPD所归属的嵌套NSD ID，嵌套NFPD ID。所述嵌套NFPD ID为嵌套NSD内唯一的某条NFPD的标识；
NFVO-1在S1003步骤中，根据如上接口消息，解析出复合VNFFGD的信息，并结合复合NSD中记录的嵌套NSD的信息，确定各嵌套NSD被引用的VNFFGD ID和NFPD ID信息，以及其被哪个复合VNFFGD/NFPD引用的信息。NFVO-1在S1004及其后的步骤中发起嵌套VNFFG实例和嵌套NFP实例的创建，相关流程描述参考实施例四的描述。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，各个网元，例如UE,基站，核心网络实体等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
实施例七：具备复合NFVO(如NFVO-1)功能或嵌套NFVO(如NFVO-2)功能或 运营维护实体(如OSS)功能的计算机设备
本发明实施例中的NFVO-1(即复合NFVO)或NFVO-2(即嵌套NFVO)或OSS(即运营维护实体)可以通过图11中的计算机设备(或***)来实现。
图11所示为本发明实施例提供的计算机设备示意图。计算机设备1100包括至少一个处理器1101，通信总线1102，存储器1103以及至少一个通信接口1104。
处理器1101可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线1102可包括一通路，在上述组件之间传送信息。
通信接口1104，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器1103可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1103用于存储执行本发明方案的应用程序代码，并由处理器1101来控制执行。处理器1101用于执行存储器1103中存储的应用程序代码，从而实现本发明实施例中NFVO-1(即复合NFVO)或NFVO-2(即嵌套NFVO)或OSS(即运营维护实体)的功能。
在具体实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例 如图11中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备1100可以包括多个处理器，例如图11中的处理器1101和处理器1108。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备1100还可以包括输出设备1105和输入设备1106。输出设备1105和处理器1101通信，可以以多种方式来显示信息。例如，输出设备1105可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备1106和处理器1101通信，可以以多种方式接受用户的输入。例如，输入设备1106可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备1100可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备1100可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图11中类似结构的设备。本发明实施例不限定计算机设备1100的类型。
本领域技术人员应明白，在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、 计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质。例如，可以利用磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))来存储或传输所述计算机指令。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (23)

  1. 一种管理VNFFG(Virtual Network Function Forward Graph，虚拟网络功能转发图)的方法，所述方法应用于跨管理域的复合NS，所述复合NS(网络服务，Network Service)引用一个或多个嵌套NS；其中，复合NS所对应的NSD(Network Service Descriptor，网络服务描述符)称为复合NSD，嵌套NS所对应的NSD称为嵌套NSD，复合NS管理域的NFVO(Network Functions Virtualization Orchestrator，网络功能虚拟化编排器)称作复合NFVO，嵌套NS管理域的NFVO称为嵌套NFVO；所述方法其特征在于，
    复合NFVO接收实例化复合NS或更新复合NS的请求，获取复合VNFFGD(VNFFG Descriptor，VNFFG描述符)所引用的嵌套VNFFGD的信息和复合NFPD(Network Forward Path Descriptor，网络转发路径描述符)所引用的嵌套NFPD的信息；所述复合VNFFGD为复合NS的VNFFGD，所述嵌套VNFFGD为复合NS所引用的嵌套NS的VNFFGD，所述复合NFPD为复合NS的VNFFGD中包含的NFPD，所述嵌套NFPD为复合NS所引用的嵌套NS的VNFFGD中包含的NFPD；
    所述复合NFVO根据请求消息实例化复合NS或更新复合NS，具体包括：
    根据复合VNFFGD实例化复合管理域内的VNFFG实例，并根据复合NFPD实例化复合管理域内的NFP(Network Forward Path，网络转发路径)实例；以及
    所述复合NFVO根据复合VNFFGD所引用的嵌套VNFFGD的信息和复合NFPD所引用的嵌套NFPD的信息，请求嵌套NFVO实例化嵌套NS管理域内的VNFFG实例和NFP实例。
  2. 如权利要求1所述的方法，其特征在于，所述复合VNFFGD所引用的嵌套VNFFGD的信息和所述复合NFPD所引用的嵌套NFPD的信息记录在复合NSD中。
  3. 如权利要求2所述的方法，其特征在于，所述复合NSD中包含复合VNFFGD，任一复合VNFFGD中包含其所引用的嵌套VNFFGD的信息；所述复合VNFFGD中包含复合NFPD，任一复合NFPD中包含其所引用的嵌套NFPD的信息。
  4. 如权利要求1所述的方法，其特征在于，所述复合VNFFGD所引用的嵌套VNFFGD的信息和所述复合NFPD所引用的嵌套NFPD的信息包含在所述复合NFVO收 到的实例化复合NS或更新复合NS实例的请求消息中。
  5. 如权利要求3或4所述的方法，其特征在于，所述复合VNFFGD所引用的嵌套VNFFGD的信息包括如下信息：
    嵌套VNFFGD标识，即所述嵌套NSD内某条VNFFGD的标识；
    嵌套NSD标识，即嵌套VNFFGD所归属的嵌套NSD的标识；
  6. 如权利要求3或4所述的方法，其特征在于，所述复合NFPD所引用的嵌套NFPD的信息包括如下信息：
    嵌套NFPD标识，即嵌套NSD内的某条NFPD的标识；
    嵌套NSD标识，即嵌套NFPD所归属的嵌套NSD的标识。
  7. 如权利要求6所述的方法，其特征在于，所述复合NFPD用于描述以下连接点间的转发规则：
    复合NS内VNF(Virtual Network Function，虚拟网络功能)和PNF(Physical Network Function，物理网络功能)间的连接点；
    复合NS对外与任一嵌套NS连接的连接点；
    嵌套NS之间连接的连接点。
  8. 如权利要求7所述的方法，其特征在于，复合NSD中的复合VNFFGD中记录权利要求6中所述连接点的信息。
  9. 如权利要求7所述的方法，其特征在于，所述复合NFVO收到的实例化复合NS或更新复合NS实例的请求消息中包含权利要求6中所述复合NS对外与任一嵌套NS连接的连接点和嵌套NS之间连接的连接点的信息。
  10. 如权利要求1所述的方法，其特征在在于，所述实例化复合NS或更新复合NS的请求来自如下任一实体：
    OSS/BSS(Operational Support System/Business Support System，运营支撑***/业务支撑***)；
    复合NFVO本身的操作维护客户端；
    其它运营维护***。
  11. 如权利要求10所述的方法，其特征在于，所述实例化复合NS或更新复 合NS的请求消息包含复合NS实例标识。
  12. 如权利要求11所述的方法，其特征在于，所述实例化复合NS或更新复合NS的请求消息还包含增加VNFFG的指示，和一个或多个复合VNFFGD标识，所述复合VNFFGD标识用以指示需要实例化的复合VNFFGD。
  13. 如权利要求1-12任一所述方法，其特征在于，
    复合NFVO获取复合VNFFGD所引用的嵌套VNFFGD的信息和复合NFPD所引用的嵌套NFPD的信息，确定各嵌套NSD中被引用的嵌套VNFFGD标识和嵌套NFPD标识，并确定各嵌套NSD对应的嵌套NS实例标识和嵌套NS所在管理域的NFVO，即嵌套NFVO；
    复合NFVO向嵌套NFVO发送实例化嵌套NS或更新嵌套NS实例的请求，请求所述嵌套NFVO创建嵌套VNFFG实例和嵌套NFP实例；所述请求消息包含嵌套NS实例标识。
  14. 如权利要求13所述方法，其特征在于，复合NFVO向嵌套NFVO发送的实例化嵌套NS或更新嵌套NS实例的请求消息中还包含增加VNFFG的指示，一个或多个嵌套VNFFGD标识，一个或多个嵌套NFPD标识。
  15. 如权利要求13所述的方法，其特征在于，所述嵌套NFVO根据收到的实例化嵌套NS或更新嵌套NS实例的请求，实例化本管理域内的嵌套VNFFG实例和嵌套NFP实例，并向复合NFVO返回嵌套VNFFGD和嵌套NFPD对应的嵌套VNFFG实例标识和嵌套NFP实例标识。
  16. 如权利要求14所述的方法，其特征在于，所述嵌套NFVO根据收到的实例化嵌套NS或更新嵌套NS实例的请求消息中包含的一个或多个嵌套VNFFGD标识和一个或多个嵌套NFPD标识，实例化嵌套VNFFG和嵌套NFP，并向复合NFVO返回请求消息中嵌套VNFFGD和嵌套NFPD对应的嵌套VNFFG实例标识和嵌套NFP实例标识。
  17. 如权利要求15或16所述的方法，其特征在于，复合NFVO在收到嵌套NFVO发送的实例化嵌套NS或更新嵌套NS实例的响应消息后，记录复合VNFFG和复合NFP所引用的嵌套VNFFG实例标识和嵌套NFP实例标识。
  18. 如权利要求1-17任一所述的方法，其特征在于，
    复合NFVO收到更新复合NS实例的请求消息，其中包含复合NS实例标识，删除复合VNFFG的指示和一个或多个要删除的复合VNFFG实例标识；
    复合NFVO删除本管理域内的复合VNFFG实例和复合VNFFG实例中包含的复合NFP实例；
    复合NFVO向嵌套NS管理域发送更新嵌套NS实例的请求消息，其中包含嵌套NS实例标识，删除VNFFG的指示，一个或多个要删除的嵌套VNFFG实例标识和一个或多个要删除的嵌套NFP实例标识。
  19. 一种复合NS管理域的NFVO，其特征在于，包括：
    通信接口，用于接收实例化复合NS或更新复合NS的请求消息并返回相应的响应消息，还用于发送实例化嵌套NS或更新嵌套NS实例的请求并接收相应的响应消息；
    存储器，用于存储计算机执行指令和复合NS及其所引用的嵌套NS的相关信息，包括复合VNFFG实例所引用的嵌套VNFFG实例标识，和复合NFP实例所引用的嵌套NFPD实例标识；
    处理器，通过总线与存储器和通信接口连接，当通信接口接收实例化复合NS或更新复合NS的请求消息，处理器执行存储器中存储的计算机执行指令，以完成1-18任一所述方法中复合NFVO的功能。
  20. 一种嵌套NS管理域的NFVO，其特征在于，包括：
    通信接口，用于接收实例化嵌套NS或更新嵌套NS的请求消息并返回相应的响应消息；
    存储器，用于存储计算机执行指令；
    处理器，通过总线与存储器和通信接口连接，当通信接口接收实例化嵌套NS或更新嵌套NS的请求消息，处理器执行存储器中存储的计算机执行指令，以完成15或16所述方法中嵌套NFVO的功能。
  21. 一种管理VNFFG的***，其特征在于,包括：
    如权利要求19中所述的复合NFVO，用于根据收到的实例化复合NS或更新复 合NS的请求消息，创建或删除复合NS管理域内的复合VNFFG实例和复合NFP实例，并请求嵌套NFVO创建或删除复合VNFFGD和复合NFPD所引用的嵌套VNFFGD的实例和嵌套NFPD的实例；
    如权利要求20中所述的嵌套NFVO，用于根据复合NFVO的请求消息，创建或删除复合VNFFGD和复合NFPD所引用的嵌套VNFFGD的实例和嵌套NFPD的实例。
  22. 如权利要求21所述的***，其特征在于，所述***还包括自如下任一实体，用于向复合NFVO发送实例化复合NS或更新复合NS的请求消息，触发如权利要求1-18任一所述方法中的创建或删除复合VNFFG实例及其所引用的嵌套VNFFG实例，和复合NFP实例及其所引用的嵌套NFP实例的流程：
    OSS/BSS(运营支撑***/业务支撑***，Operational Support System/Business Support System)；
    复合NFVO本身的操作维护客户端；
    其它运营维护实体。
  23. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-18所述的方法。
PCT/CN2016/113955 2016-12-30 2016-12-30 一种管理vnffg的方法、装置和*** WO2018120222A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/113955 WO2018120222A1 (zh) 2016-12-30 2016-12-30 一种管理vnffg的方法、装置和***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/113955 WO2018120222A1 (zh) 2016-12-30 2016-12-30 一种管理vnffg的方法、装置和***

Publications (1)

Publication Number Publication Date
WO2018120222A1 true WO2018120222A1 (zh) 2018-07-05

Family

ID=62706656

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/113955 WO2018120222A1 (zh) 2016-12-30 2016-12-30 一种管理vnffg的方法、装置和***

Country Status (1)

Country Link
WO (1) WO2018120222A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11108653B2 (en) * 2017-12-29 2021-08-31 Huawei Technologies Co., Ltd. Network service management method, related apparatus, and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的***及方法
WO2016118646A1 (en) * 2015-01-20 2016-07-28 Huawei Technologies Co., Ltd Systems and methods for sdt to interwork with nfv and sdn
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016118646A1 (en) * 2015-01-20 2016-07-28 Huawei Technologies Co., Ltd Systems and methods for sdt to interwork with nfv and sdn
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的***及方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11108653B2 (en) * 2017-12-29 2021-08-31 Huawei Technologies Co., Ltd. Network service management method, related apparatus, and system
US20210359919A1 (en) * 2017-12-29 2021-11-18 Huawei Technologies Co., Ltd. Network Service Management Method, Related Apparatus, and System
US11502919B2 (en) 2017-12-29 2022-11-15 Huawei Technologies Co., Ltd. Network service management method, related apparatus, and system

Similar Documents

Publication Publication Date Title
CN110569101B (zh) 管理容器服务的方法和装置
US10713071B2 (en) Method and apparatus for network function virtualization
RU2595540C9 (ru) Базовые контроллеры для преобразования универсальных потоков
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
EP3200393B1 (en) Method and device for virtual network function management
WO2017113201A1 (zh) 一种网络服务的生命周期管理方法及设备
US10291462B1 (en) Annotations for intelligent data replication and call routing in a hierarchical distributed system
WO2020186911A1 (zh) 一种容器化虚拟网络功能vnf的资源管理方法及装置
WO2018137572A1 (zh) 一种策略管理方法、装置和***
JPWO2016117694A1 (ja) ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム
WO2018090299A1 (zh) 网络服务生命周期管理的许可方法和装置
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
US10678657B1 (en) Reversion operations for virtual computing environments
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
WO2019001140A1 (zh) 一种管理vnf实例化的方法和设备
CN109905258B (zh) PaaS的管理方法、装置及存储介质
WO2022140945A1 (zh) 容器集群的管理方法和装置
WO2021143183A1 (zh) 一种部署虚拟机的方法及相关装置
WO2018050013A1 (zh) 一种管理网络功能节点的方法及装置
WO2018000377A1 (zh) 管理功能对象的管理方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和***
US11949557B2 (en) Device, method, and program for ICT resource management using service management information
WO2020077585A1 (zh) Vnf服务实例化方法及装置
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16925263

Country of ref document: EP

Kind code of ref document: A1