WO2018090299A1 - 网络服务生命周期管理的许可方法和装置 - Google Patents

网络服务生命周期管理的许可方法和装置 Download PDF

Info

Publication number
WO2018090299A1
WO2018090299A1 PCT/CN2016/106288 CN2016106288W WO2018090299A1 WO 2018090299 A1 WO2018090299 A1 WO 2018090299A1 CN 2016106288 W CN2016106288 W CN 2016106288W WO 2018090299 A1 WO2018090299 A1 WO 2018090299A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
nfvo
lcm operation
virtual resource
lcm
Prior art date
Application number
PCT/CN2016/106288
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 CN202110013719.9A priority Critical patent/CN112799779A/zh
Priority to EP16921857.5A priority patent/EP3534568B1/en
Priority to ES16921857T priority patent/ES2932756T3/es
Priority to PCT/CN2016/106288 priority patent/WO2018090299A1/zh
Priority to KR1020197016894A priority patent/KR102272229B1/ko
Priority to EP22205140.1A priority patent/EP4195608A1/en
Priority to CN201680090856.XA priority patent/CN109964449B/zh
Priority to JP2019526235A priority patent/JP6738965B2/ja
Publication of WO2018090299A1 publication Critical patent/WO2018090299A1/zh
Priority to US16/415,840 priority patent/US10911333B2/en
Priority to US17/146,091 priority patent/US11271827B2/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
    • 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
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • 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
    • 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/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • 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/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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/14—Network analysis or design
    • 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/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • 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/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the embodiments of the present application relate to communication technologies, and in particular, to a method and an apparatus for permitting network service lifecycle management.
  • Network Function Virtualization technology is a virtualization technology for telecom network operators in the field of Information Technology (IT).
  • IT Information Technology
  • the implementation of some telecommunications network functions is decoupled from software and hardware in a common cloud server, switch and memory. This technology requires the functionality of the telecommunications network to be implemented in software, running on common server hardware, and being migrated, instantiated, and deployed at different physical locations on the network as needed.
  • the virtualized network service (English: Network Service, NS for short) in NFV can be implemented by several Virtualized Network Function (VNF) modules.
  • VNF Virtualized Network Function
  • the VNF is a software implementation of the network functions that can be deployed on the NFV infrastructure.
  • the Network Function Virtualization Infrastructure contains the underlying hardware (HW) resources, which can be divided into computing hardware and storage. Hardware, network hardware, and more. Above the hardware layer is the virtualization layer, including the Host Operating System (Host OS) and the hypervisor/hypervisor (Hypervisor), running at least two virtual layers above the virtualization layer.
  • Host OS Host Operating System
  • Hypervisor hypervisor/hypervisor
  • Machine Virtual Machine, VM
  • NFVI is connected to the Virtualization Infrastructure Manager (VIM) through the Nf-Vi interface.
  • the VNF is connected to the VNF Manager (VNFM) through the Ve-Vnfm interface, and the Vi-Vnfm interface is used between the VIM and the VNFM.
  • VIM is connected to the Network Functions Virtualization Orchestrator (NFVO) through Or-Vi.
  • NFVO Network Functions Virtualization Orchestrator
  • the VNFM is connected to the NFVO through the Or-Vnfm interface, and the NFVO is connected to the OSS/BSS through the Os-Ma-nfvo interface.
  • the OSS/BSS is used to initiate a network service lifecycle management request to the NFVO.
  • the NFVO is responsible for orchestrating management resources according to the network service lifecycle management request initiated by the OSS/BSS, realizing the lifecycle management of the network service, and monitoring the VNF and NFVI in real time.
  • VNFM is responsible for VNF lifecycle management, such as instantiation, elastic scaling, healing, and termination of VNF instances.
  • VIM is responsible for managing and allocating NFVI resources and detecting the collection of NFVI operational status information.
  • NFVO manages resources for its managed NS instances.
  • LCM Life Cycle Management
  • the VNFM in its management domain receives an operation request for Life Cycle Management (LCM) for a member VNF instance of the NS instance, the VNFM needs to first request the NFVO to perform the life on the VNF instance.
  • Resource management license for periodic management operations (Granting) After NFVO agrees to permit the VNF LCM operation request, VNFM can further interact with VIM to complete resource management in the VNF LCM operation.
  • an NFVO-managed virtual resource set belongs to one management domain, and different NFVO-managed virtual resource sets belong to different management domains.
  • an administrative domain refers to a collection of MANO management functional entities consisting of one NFVO and one or more VNFMs within its management scope.
  • Each administrative domain corresponds to a management scope of NFVO for the provision of a specific set of network services within the administrative domain.
  • an administrative domain may further include one or more VIMs and one or more data centers managed by each VIM.
  • each branch deploys an NFV MANO system that includes at least one NFVO to build its own management domain.
  • NS1 includes NS2.
  • NS1 needs to use 0 to N VNF instances and 0 to N physical network function PNF (Physical Network Function) instances, and 1 to N VNF (205) instances that NS2 needs to use. And 0 to N PNF (206) instances.
  • PNF Physical Network Function
  • NS1 is also called NS2, so NS1 is called Composite NS, and NS2 included by NS1 can be called Nested NS. Nested NSs are provided by administrative domains other than composite NS.
  • a composite NS can contain one or more nested NSs.
  • the composite NS instance can also be understood as a second NS instance, and the nested NS instance can also be understood as a first NS instance.
  • the NFVO managing the composite NS and the NFVO managing the nested NS and the VNFM in the management domain to which it belongs respectively perform the resource management permission process for the VNF LCM operation, which may result in nested NS.
  • the lifecycle management operations performed by the instance conflict with the lifecycle management operations objectives performed by the composite NS instance.
  • the NFVO receiving the nested NS receives the OSS/BSS to send an elastic scaling operation for the nested NS instance, while the NFVO managing the composite NS is healing the composite NS instance to which the nested NS instance belongs. Operation, the healing operation requires the nested NS instance to maintain the same capacity, and other nested NS instances or failed VNF instances that are diagnosed as failed perform recovery operations after the failure.
  • the application provides a network service lifecycle management permission method and device for solving the problem that the LNS management operation of the nested NS and the composite NS exists in the scenario where the composite NS and its member nested NS provide services in multiple management domains.
  • the embodiment of the present application provides a network service lifecycle management permission method, which is applied to a scenario in which a composite NS and its member nested NS provide services in multiple management domains, including:
  • the first network function virtualization orchestrator receives a network service lifecycle management operation request, where the NS LCM operation request carries an identifier of the first NS instance and an NS LCM operation type, where the identifier of the first NS instance is used to indicate that the LCM operation is targeted a nested NS instance, the NS LCM operation type is used to indicate a specific NS LCM operation category; the first NFVO sends a permission request to the second NFVO according to the NS LCM operation request, requesting the second NFVO to permit the first The NFVO performs virtual resource management for the NS LCM operation request for the first NS instance, the permission request carrying an identifier of the first NS instance and an NS LCM operation type; the second NFVO is according to the permission request a license response sent to the first NFVO; the first NFVO performs virtual resource management of the NS LCM operation for the first NS instance according to the license response.
  • the license method of the network service lifecycle management determines, according to the permission request of the first NFVO, the LCM operation for the nested NS instance managed by the first NFVO to generate the LCM operation for the current composite NS instance for the second NFVO management
  • the impact of the NS LCM operation against the first NFVO is based on the impact, ensuring the lifecycle management operations performed by the nested NS instance and the nested NS instance.
  • the first NFVO sends a permission request to the second NFVO according to the NS LCM operation request, including: the first NFVO is locally obtained according to the identifier of the first NS instance.
  • the stored tenant identifier acquires the identification information of the second NFVO according to the tenant identifier; the first NFVO sends a permission request to the second NFVO according to the identifier information of the second NFVO.
  • This embodiment may enable the first NFVO to be quickly addressed to the second NFVO, thereby transmitting a grant request to the second NFVO.
  • the first NS instance managed by the first NFVO is a constituent member of the second NS instance managed by the second NFVO.
  • the license request further includes:
  • the virtual resource management plan includes:
  • the type, the number, and/or the location of the virtual resource actually occupied by the instance in the NS LCM operation, and/or the member VNF instance member VL instance included in the first NS instance actually occupied by the NS LCM operation The type, number, and/or location of virtual resources.
  • the embodiment determines, by the first NFVO, a resource management plan for the NS LCM operation of the first NS instance before the permission request, and carries it in the permission request, so that the second NFVO can be more targeted according to the resource management plan.
  • the result of the judgment is more targeted and accurate for the impact of the LCM operation of the nested NS instance managed by the first NFVO on the LCM operation of the composite NS instance currently managed for the second NFVO.
  • the second NFVO further determines whether the NS LCM operation is performed on the first NS instance for the second NFVO according to at least one of the following information stored locally.
  • the second NS instance has an impact:
  • the second NS instance managed by the second NFVO has a running state of the member NS instance that has a dependency relationship with the first NS instance, and/or the second NS instance managed by the second NFVO has a dependency with the first NS instance.
  • the second NFVO not only needs to determine the impact of the nested NS LCM operation on the composite NS instance LCM operation, but also the affinity/anti-affinity of the nested NS instance and the member VNF instance according to the member in the composite NS instance.
  • the license method of the network service lifecycle management further includes: the second NFVO according to the virtual resource view of the second NS instance managed by the second NFVO and at least the information An virtual resource management plan for performing the NS LCM operation for the first NS instance;
  • the license response includes a successful operation indication, and further includes a virtual resource management plan that is performed by the second NFVO to perform the NS LCM operation for the first NS instance;
  • the first NFVO performs virtual resource management according to the updated virtual resource management plan for performing the NS LCM operation for the first NS instance.
  • the second NFVO discriminates the nested NS according to the virtual resource view of the managed second NS instance and the affinity/anti-affinity rule of the member nested NS instance and the member VNF instance in the composite NS instance. Locating the location requirements of the resources required for the LCM operation, and adjusting the virtual resource management plan for the nested NS instance LCM operation according to the licensing policy for the second NS instance NS LCM operation, thereby reducing the first NFVO from being newly initiated Licensing requests improve the efficiency of NS LCM operations.
  • the embodiment of the present application provides a network service lifecycle management permission method, including: a second NFVO receives an NS LCM operation permission request sent by a first NFVO, where the permission request carries an identifier of the first NS instance and an NS
  • the second NFVO is determined according to the identifier of the first NS instance and the NS LCM operation type and the virtual resource view of the second NS instance managed by the second NFVO to determine the first NS instance.
  • Whether the NS LCM operation affects the second NS instance managed by the second NFVO; transmitting a license response to the first NFVO according to the judgment result.
  • the method further includes: the second NFVO further determining, according to at least one of the locally stored information, whether the NS LCM operation is performed on the first NS instance
  • the second NS instance of the second NFVO management has an impact:
  • the second NS instance managed by the second NFVO has a dependency relationship with the first NS instance.
  • the running state of the member NS instance, and/or the running state of the member VNF instance having a dependency on the first NS instance under the second NS instance;
  • a licensing policy for NS LCM operations of the second NS instance is a licensing policy for NS LCM operations of the second NS instance.
  • the license request further includes: a virtual resource management plan for performing the NS LCM operation on the first NS instance, the virtual resource management The plan includes:
  • the type, the number, and/or the location of the virtual resource actually occupied by the instance in the NS LCM operation, and/or the virtual resource actually occupied by the member VL instance included in the first NS instance in the NS LCM operation Type, quantity, and/or location.
  • the method further includes:
  • the virtual resource that performs the NS LCM operation for the first NS instance according to at least one of a virtual resource view of the second NS instance managed by the second NFVO and the locally stored information Management plan
  • the license response includes a successful operation indication, and further includes a virtual resource management plan for performing the NS LCM operation for the first NS instance after the second NFVO update, to indicate that the first NFVO is according to the The updated virtual resource management plan for performing the NS LCM operation for the first NS instance performs virtual resource management.
  • the embodiment of the present application provides a network function virtualization orchestrator NFVO, including: a receiving unit, a processing unit, and a sending unit that are sequentially connected, where:
  • a receiving unit configured to receive an NS LCM operation request, where the NS LCM operation request carries an identifier of the first NS instance and an NS LCM operation type;
  • a sending unit configured to send a permission request to the second NFVO according to the NS LCM operation request, requesting the second NFVO to permit the NFVO to perform virtual resource management for performing the NS LCM operation request for the first NS instance,
  • the permission request carries an identifier of the first NS instance and an NS LCM operation type, where the first NS instance managed by the NFVO is a constituent member of a second NS instance managed by the second NFVO;
  • the receiving unit is further configured to receive the second NFVO sent according to the permission request Responsive;
  • a processing unit configured to perform virtual resource management for performing NS LCM operations on the first NS instance according to the license response.
  • the sending unit sends a permission request to the second NFVO according to the NS LCM operation request, including:
  • the sending unit obtains the stored tenant identifier from the locality according to the identifier of the first NS instance, and acquires the identifier information of the second NFVO according to the tenant identifier.
  • the transmitting unit sends a permission request to the second NFVO according to the identification information of the second NFVO.
  • the permission request sent by the sending unit further includes:
  • the virtual resource management plan includes: adding, deleting, the NS LCM operation by referring to the current resource situation used by the first NS instance Or the type, number, and/or location of the changed virtual resource; or the type, number, and/or location of the virtual resource actually occupied by the member VNF instance included in the first NS instance in the NS LCM operation, and / or the type, number and/or location of the virtual resources actually occupied by the member VL instance included in the first NS instance in the NS LCM operation.
  • the license response received by the receiving unit includes a successful operation indication
  • the processing unit performs the Performing virtual resource management of the NS LCM operation by an NS instance includes: the processing unit performs virtual resource management according to a virtual resource management plan for performing NS LCM operations on the first NS instance.
  • the license response received by the receiving unit includes a successful operation indication, and further includes, by the second NFVO, the The first NS instance performs a virtual resource management plan of the NS LCM operation, and the processing unit performs virtual resource management for the NS LCM operation according to the license response, including:
  • the processing unit performs virtual resource management according to the updated virtual resource management plan for performing the NS LCM operation on the first NS instance.
  • a network function virtualization orchestrator NFVO is provided, and the NFVO includes Connected receiving unit, processing unit and transmitting unit, wherein:
  • a receiving unit configured to receive an NS LCM operation permission request sent by the first NFVO, where the permission request carries an identifier of the first NS instance and an NS LCM operation type, where the first NS instance managed by the first NFVO is the a member of the second NS instance managed by NFVO;
  • a processing unit configured to determine, according to the identifier of the first NS instance, the NS LCM operation type, and the virtual resource view of the second NS instance that is managed by the NFVO, whether the NS LCM operation is performed on the first NS instance
  • the NS instance of NFVO management has an impact
  • a sending unit configured to send a license response to the first NFVO according to the determination result.
  • the processing unit further determines, according to at least one of the locally stored information, whether the NS LCM operation on the first NS instance is generated for the NSVO managed NS instance. influences:
  • a licensing policy for NS LCM operations of the second NS instance is a licensing policy for NS LCM operations of the second NS instance.
  • the permission request received by the receiving unit further includes: a virtual resource management plan for performing the NS LCM operation on the first NS instance, Virtual resource management plans include:
  • the processing unit is further configured to:
  • the license response sent by the sending unit includes a successful operation indication, and further includes a virtual resource management plan that is performed by the NFVO to perform the NS LCM operation for the first NS instance, where And to instruct the first NFVO to perform virtual resource management according to the updated virtual resource management plan for performing the NS LCM operation on the first NS instance.
  • an NFVO apparatus comprising: a memory for storing computer executable program code; a transceiver, and a processor coupled to the memory and the transceiver;
  • the program code includes instructions, when the processor executes the instruction, the instruction causes the network element to perform an operation of: receiving a network service lifecycle management operation request, the NS LCM operation request carrying a first NS The identity of the instance and the type of NS LCM operation;
  • an NFVO apparatus comprising a memory for storing computer executable program code, a transceiver, and a processor coupled to the memory and the transceiver;
  • the program code includes instructions, when the processor executes the instruction, the instruction causes the network element to perform the following operations: receiving: receiving an NS LCM operation permission request sent by the first NFVO, the permission request carrying An instance identifier of the first NS and an NS LCM operation type;
  • a computer program product comprising executable program code, wherein the program code includes instructions that, when executed by the processor, cause the network element to perform the following operations: receiving a network a service lifecycle management operation request, where the NS LCM operation request carries an identifier of the first NS instance and an NS LCM operation type;
  • a computer program product comprising executable program code, wherein the program code includes instructions that, when executed by the processor, cause the network element to perform the following operations: receiving a An NS LCM operation permission request sent by the NFVO, the permission request carrying an identifier of the first NS instance and an NS LCM operation type;
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions for use in the NFVO, which includes a program designed to perform the above aspects.
  • the method for granting nested NS lifecycle management in the embodiment of the present application implements resource management in a nested NS LCM operation and lifecycle management of a composite NS to which a nested NS belongs by using a license management mechanism between the first NFVO and the second NFVO.
  • the resource management of the operation achieves the consistency of the target, and avoids the resource management performed in the nested NS LCM operation to have a negative impact on the composite NS instance.
  • FIG. 1 is a network architecture diagram of an NFV-MANO application according to an embodiment of the present application
  • FIG. 2 is a topological diagram of a relationship between a composite network service and a nested network service in an application scenario according to an embodiment of the present application;
  • FIG. 3 is a network topology diagram in application scenario 1 according to an embodiment of the present application.
  • FIG. 4 is a network topology diagram in application scenario 2 according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a permission method interaction of a nested network service lifecycle management based on application scenario 1 in an embodiment of the present application;
  • FIG. 6 is a schematic diagram of a nested network service lifecycle management based on application scenario 2 in the embodiment of the present application; Method interaction flow chart;
  • FIG. 7 is a flowchart of a permission method interaction of a nested network service instantiation operation based on application scenario 2 in the embodiment of the present application;
  • FIG. 8 is a flowchart of a permission method interaction of a nested network service elastic scaling operation based on application scenario 2 in the embodiment of the present application;
  • FIG. 9 is a flowchart of a permission method interaction of a nested network service termination operation based on application scenario 2 in the embodiment of the present application;
  • FIG. 10 is a flowchart of a permission method interaction of a resource reservation operation in a nested network service lifecycle management based on application scenario 2 in the embodiment of the present application;
  • FIG. 11 is a flow chart of interaction of a volume licensing method in a nested network service lifecycle management according to another embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a NFVO function according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a NFVO function according to another embodiment of the present application.
  • FIG. 14 is a schematic diagram of a general physical structure of an NFVO according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a general physical structure of an NFVO according to another embodiment of the present application.
  • the embodiment of the present invention provides a method and a device for permitting nested network service lifecycle management, which are used to solve the technical problem of target conflict in nested network application and composite network application lifecycle management in the prior art.
  • first and second are used herein for convenience of description, and are used to distinguish different NS, NS instances, VNFs, or different VNF instances, and have no technical meaning.
  • the NFVO managing the composite NS is referred to as the second NFVO, and the NFVO managing the nested NS is referred to as the first NFVO.
  • a vEPC network service is provided in a telecommunications carrier with a large number of users.
  • the telecom operator's network has a two-level structure: a head office network and 30 regional company networks, each of which has its own management domain and is configured with an NFVO.
  • the NFVO in the head office network is equivalent to the NFVO of the management NS1 in FIG. 2, that is, the second NFVO; and the NFVO in each civil company network is equivalent to the NFVO of the management NS2 in FIG. 2, that is, the first NFVO.
  • the telecommunication operator determines to provide the network service vEPC from the level of the head office network, it may specify that the sub-company network of the province A provides the control plane network service that constitutes the vEPC, and the B-province network provides the user plane network service that constitutes the vEPC.
  • the policy control network service that constitutes vEPC is provided by the subsidiary network of the province.
  • the solution of the present application is applicable to the permission of the second NFVO to perform resource management for the first NFVO in performing a nested network service (Nested NS) lifecycle management operation in a scenario provided by the composite NS across the management domain.
  • the second NFVO and the first NFVO respectively manage the virtual resource view of the composite NS and the nested NS.
  • the virtual resource view is a data structure in NFVO. It is used to display the status of the virtual resource used by the NS instance. It can be expressed as the type of virtual resource occupied by each member VNF instance and member VL instance of the NS instance (computing, storage, network).
  • the virtual resource location information may represent a virtual resource location association relationship of different granularity by a combination of a VIM identifier, a resource zone, and/or a host identifier.
  • Scenario 1 The VIM and NFVI resources in the composite NS and the nested NS management domain are different from each other. As shown in Figure 3, the VIMs of the management domains in the scenario are different.
  • the VIMs of the management domains are different from each other, between the lifecycle management of the composite NS instance and the lifecycle management of the nested NS instances, and between the lifecycle management of two different nested NS instances.
  • the target virtual resource space for the resource management does not overlap with each other. Therefore, the virtual resource allocation or release of each NS instance, whether it is a composite NS instance or a nested NS instance, can be completed by the NFVO of each management domain alone, and the second NFVO is licensed. The process helps the first NFVO to discriminate the impact of the nested NS instance LCM operation on the current composite NS instance LCM operation. If an execution target conflict is formed, Then the second NFVO rejects the first NFVO to perform the nested NS instance LCM operation.
  • Scenario 2 The VIM and NFVI resources in the composite NS and nested NS management domains are shared with each other, as shown in Figure 4:
  • the management domain consists of one NFVO and one or more VNFMs managed by the NFVO.
  • the administrative domain shares a set of identical VIMs and NFVI resources within the VIM domain.
  • the second NFVO Compared with scenario 1, in the licensing process of nested NS LCM operations, the second NFVO not only determines the impact of nested NS LCM operations on the composite NS instance LCM operations, but also nests NS instances according to members in the composite NS instance.
  • the affinity/anti-affinity rule of the member VNF instance discriminates the location requirement of the resource allocated by the nested NS instance LCM operation, and feeds back the suggested resource location to the first NFVO.
  • the affinity/anti-affinity rule is used to determine whether two member VNF instances can be deployed in the same location virtual resource.
  • the first embodiment of the present application provides a permission method based on the nested NS LCM operation in scenario 1, as shown in FIG. 5.
  • the first NFVO Before the method in this embodiment is executed, the following information needs to be configured: before the sender initiates the request message for the nested NS LCM operation to the first NFVO, the first NFVO internally stores the identifier information of the tenant that invokes the nested NS instance LCM operation ( Tenant ID).
  • the tenant identification information may be transmitted by the second NFVO to the first NFVO during the shelf process of the composite NS descriptor file, and the tenant identification information may be the identification information of the second NFVO, the identifier information being used for the first NFVO addressing second. NFVO.
  • the second NFVO and the first NFVO respectively store the virtual resource view of the composite NS instance and the nested NS instance, and the virtual resource view of the composite NS instance does not include the virtual resource view of the nested NS instance, that is, the nested NS instance.
  • the virtual resource view is not visible to the second NFVO.
  • the permission method of the nested NS LCM operation of this embodiment includes the following steps:
  • the sender Sender sends a request message for the nested NS LCM operation to the first NFVO, where the request message carries the identifier information of the nested NS instance and the NS LCM operation type.
  • the NS LCM operation type may include, but is not limited to, NS instantiation, NS elastic scaling, NS update, NS healing, and NS termination, input in the request message.
  • the parameters can be defined by reference to the ETSI NFV IFA013 protocol.
  • the first NFVO addresses the second NFVO according to the tenant ID information stored therein, and sends a Grant Request to the second NFVO, where the request message carries the identifier information of the nested NS instance and is executed.
  • NS LCM operation type The first NFVO addresses the second NFVO according to the tenant ID information stored therein, and sends a Grant Request to the second NFVO, where the request message carries the identifier information of the nested NS instance and is executed.
  • the first NFVO stores a correspondence between the tenant identification information and the nested NS instance identification information.
  • the first NFVO may search for the stored tenant identification information according to the nested NS identification information in the received nested NS LCM request, and then query the second NFVO identification information, such as an IP address, according to the second identifier, according to the second
  • the identification information of the NFVO sends a permission request to the second NFVO.
  • the second NFVO checks the LCM operation type of the nested NS instance in the received permission request, and determines the nested NS LCM according to the NS instance identifier and the NS LCM operation type and the virtual resource view of the NS instance managed by the second NFVO. Whether the operation has an impact on the NS instance managed by the second NFVO.
  • the second NFVO determines, according to the virtual resource view of the managed NS instance, whether there is a VNF instance and/or a nested NS instance in the composite NS instance that has a dependency relationship with the nested NS instance in the LCM operation, and the VNFs. Whether the instance and the nested NS instance are performing an LCM operation with a dependency to determine whether the nested NS LCM operation has an impact on the NS instance managed by the second NFVO.
  • Dependencies are used to determine the order in which virtual resources are allocated between two member instances (which can be nested NS instances or VNF instances) within a composite NS instance. For example, the allocation of resources for a nested NS instance that performs lifecycle management operations in a certain LCM operation depends on the completion of resource allocation by other member VNF instances and/or nested NS instances in the corresponding LCM operations.
  • Further second NFVO may also determine whether to permit the first NFVO to perform virtual resource management for the nested NS LCM operation according to the corresponding nested NS LCM licensing policy.
  • the nested NS LCM license policy indicates that when the load of the composite NS instance is light, the resource management request of all member nested NS instances can be satisfied as much as possible; if the load of the composite NS instance is heavy, the high priority is preferentially satisfied.
  • the member manages the resource management request of the NS instance.
  • the nested NS LCM licensing policy can be sent to the second NFVO by pre-configuration or by operating the OSS/BSS to configure policy information on the Os-Ma-nfvo interface.
  • the second NFVO sends a license response to the first NFVO according to the judgment result.
  • the second NFVO permits the first NFVO to perform virtual resource management corresponding to the nested NS LCM operation, and the second NFVO returns a permission response message to the first NFVO, in which the indication of successful operation is carried. If the effect is judged, then the second NFVO returns a license response message with a failure cause indication to the first NFVO.
  • the first NFVO interacts with the corresponding VIM according to the permission in the license response message, and performs the pin Virtual resource management for this nested NS LCM operation.
  • the first NFVO interacts with the VIM corresponding to the first NFVO according to the permission indication information in the license response message, and performs virtual resource management operations, such as allocation or release of virtual resources, for the nested NS LC operation.
  • the first NFVO returns an execution result of the nested NS LCM operation to the Sender by nesting the NS LCM response message.
  • the method for granting nested NS lifecycle management in the embodiment of the present application implements resource management in a nested NS LCM operation and lifecycle management of a composite NS to which a nested NS belongs by using a license management mechanism between the first NFVO and the second NFVO.
  • the resource management of the operation achieves the consistency of the target, and avoids the resource management performed in the nested NS LCM operation to have a negative impact on the composite NS instance.
  • Embodiment 2 of the present application provides a method for permitting a nested NS LCM operation based on the second NFVO of scenario 2, as shown in FIG. 6 :
  • This embodiment describes a basic schematic process of the permission process of performing a nested NS LCM operation under scenario 2.
  • the first NFVO Before the process of the embodiment is executed, the following configuration is required: before the sender initiates the request message for the nested NS LCM operation to the first NFVO, the first NFVO internally stores the identifier information of the tenant that invokes the nested NS instance LCM operation ( Tenant ID).
  • the tenant identification information may be transmitted by the second NFVO to the first NFVO during the shelf process of the composite NS descriptor file, where the tenant identification information may be the identification information of the second NFVO, and the identification information is used for the first NFVO addressing.
  • the second NFVO interacts.
  • the second NFVO and the first NFVO respectively store the virtual resource view of the composite NS instance and the nested NS instance, and the virtual resource view of the composite NS instance includes the virtual resource view of the nested NS instance, that is, the nested NS instance.
  • the virtual resource view is visible to the second NFVO.
  • the embodiment includes the following steps:
  • the sender Sender initiates a request message for the nested NS LCM operation to the first NFVO, where the request message carries the operation type and the identifier information of the nested NS instance.
  • NS LCM operations may include, but are not limited to, NS instantiation, NS elastic scaling, NS update, NS healing, and NS termination, definition of input parameters in operations. Please refer to the ETSI NFV IFA013 agreement.
  • the first NFVO addresses the second NFVO according to the tenant ID information stored therein, and initiates a permission request to the second NFVO, where the request message carries the identifier information of the nested NS instance, and the executed NS LCM operation. Type and virtual resource management plan for this NS LCM operation.
  • the first NFVO determines a virtual resource management plan for the NS LCM operation according to the NS LCM operation type in the request and the virtual resource view of the nested NS instance that is internally managed. That is, according to the current virtual resource allocation of the nested NS instance, the number and location of the virtual resources that need to be added, deleted, or changed are determined, or the member VNF instance included in the nested NS instance is actually occupied by the NS LCM operation. The type, number, and/or location of virtual resources, and/or the type, number, and/or location of virtual resources that the member VL instances included in the nested NS instance actually occupy in the NS LCM operation.
  • the second NFVO addressing mode refers to step 502 of FIG.
  • the second NFVO determines whether the nested NS LCM operation affects other nested NS instances or NFV instances under the second NFVO management.
  • the second NFVO checks the virtual resource management plan in the received permission request, and checks other member VNF instances or member nested NS instances in the composite NS instance according to the resource view of the composite NS managed by the second NFVO. Whether there is a case of performing a conflict with the nested NS instance LCM operation resource management, determining whether to permit the first NFVO to make a virtual resource management plan for the nested NS LCM operation.
  • the second NFVO may be based on whether there is a VNF instance and/or a nested NS instance in the composite NS instance that has a dependency relationship with the nested NS instance in the lifecycle management operation. For example, the resource allocation of a nested NS instance performing lifecycle management operations in a certain LCM operation depends on the completion of resource allocation of other member VNF instances and/or nested NS instances in the corresponding LCM operations, and these VNFs. Whether the instance and the nested NS instance are performing an LCM operation with dependencies.
  • the second NFVO may further determine whether to permit the first NFVO to authorize the virtual resource management plan for the nested NS LCM operation according to the corresponding nested NS LCM licensing policy.
  • the second NFVO sends a license response to the first NFVO according to the judgment result.
  • the second NFVO If permitted, the second NFVO returns a grant response message to the first NFVO, in which an indication of successful operation is carried.
  • the second NFVO further updates the virtual resource view of the composite NS instance according to the virtual resource management plan. If not permitted, the second NFVO returns a license response message with a failure cause indication to the first NFVO.
  • the second NFVO may further adjust the virtual resource management plan formulated by the first NFVO for the nested NS LCM operation according to at least one of the following conditions, and pass the updated virtual resource management plan through the license.
  • the reply message is returned to the first NFVO.
  • the resource view of the composite NS managed by the second NFVO, the state of the VNF instance execution operation in the composite NS instance and the dependency of the nested NS instance in the lifecycle management operation, and the nesting in the composite NS instance The state of the execution operation of the other nested NS instances in which the NS instance has dependencies in the lifecycle management operation and the corresponding nested NS LCM licensing policy.
  • the first NFVO performs virtual resource management for the nested NS LCM operation according to the virtual resource management plan and the corresponding VIM interaction.
  • step 505 of FIG. 5 For the specific implementation of this step, reference may be made to the implementation of step 505 of FIG. 5.
  • the first NFVO returns an execution result of the nested NS LCM operation to the Sender by nesting the NS LCM response message.
  • Embodiment 3 of the present application provides a permission method for permitting resource management in a nested NS instantiation operation based on the second NFVO of scenario 2.
  • This embodiment is an embodiment of the second embodiment, and is applied to the instantiation process of the nested NS.
  • the sender Sender may be an OSS/BSS, and initiates a nested NS instantiation request to the first NFVO, where the request message carries the NS instance identifier and the resource requirement description parameter.
  • the nested NS instantiation request may further include a template identifier (Flavor ID) reflecting the nested NS specific topology and constraint information of the member VNF instance deployment location of the nested NS instance.
  • Flavor ID a template identifier reflecting the nested NS specific topology and constraint information of the member VNF instance deployment location of the nested NS instance.
  • the first NFVO addresses the second NFVO according to the nested NS instantiation request, and sends a permission request to the second NFVO.
  • the first NFVO parses the input parameter in the nested NS instantiation request, and describes the resource requirement in the NS instantiation operation of the nested NS instance according to the request message, for example, the NS instantiation
  • the basic requirements of the virtual resources corresponding to the level form a resource management plan for the member VNF instance and the member VL instance that constitute the nested NS instance, that is, the member VNF instance occupies resource information and the member VNF instance occupies resource information.
  • the nested NS instance identifier is used to uniquely identify the nested NS instance in the first NFVO, and the NS LCM operation type is used to indicate the NS lifecycle management operation type in the license request.
  • the member VNF occupied resource information includes the number of virtual resources (computing, storage, and network) required to instantiate the member VNFs of the nested NS instance, and the member VL occupied resource information includes virtual resources (networks) required for member VL instantiation. quantity.
  • the resource location constraint relationship of the nested NS represents the description information defined by the resource management location in the nested NS LCM operation, which may be determined according to the affinity/anti-affinity rule between the member VNF instance and/or the member VL instance.
  • the relative position is limited.
  • the nested NS instantiation needs to be deployed on several adjacent hosts in the same resource zone. It may also be an absolute physical location limit that reflects the deployment of member VNF instances and/or member VL instances.
  • nested NS instantiation needs to be deployed within the scope of hosts A1, A2, and A3.
  • the resource location can be represented by the VIM identity, the resource zone, and/or the identity of the host.
  • the second NFVO does allow the first NFVO to perform resource management of the NS instantiation operation, and sends a permission response to the first NFVO.
  • the second NFVO returns a license response to the first NFVO according to the virtual resource view of the composite NS instance, the dependency of the member of the composite NS instance nested NS instance, and/or the corresponding nested NS LCM permission policy.
  • the license response message carries the VIM identifier that the first NFVO needs to interact with, the identifier of the resource area and/or the host (resource location information), and the resource location information is used to indicate the type of the nested NS instance suggested by the second NFVO.
  • the location of the resources required for the lifecycle management operations is used to indicate the type of the nested NS instance suggested by the second NFVO.
  • the second NFVO may also carry the actual resource information allocated to the nested NS instantiation operation under each VIM in the response message, for example, the virtual resource required for the member VNF instantiation of the nested NS instance actually allocated (calculation) Number of storage, network, and number of virtual resources (networks) instantiated by member VL.
  • the first NFVO interacts with the corresponding VIM according to the information provided in the license response, and completes resource management in the nested NS instance lifecycle management.
  • the first NFVO interacts with the corresponding VIM according to the VIM identifier in the license response, and the identifier of the resource area and/or the host, and instantiates the virtual resource required according to the actually allocated member VNF of the nested NS instance.
  • the first NFVO returns a nested NS instantiation response to the Sender, indicating completion of the nested NS instantiation operation.
  • a fourth embodiment of the present application provides a method for permitting resource management in nested NS elastic scaling based on the second NFVO of scenario 2, as shown in FIG. 8.
  • This embodiment is an embodiment of the second embodiment, and is applied to an elastic scalable scaling operation of a nested NS.
  • the steps of this embodiment are similar to those of Embodiment 3 except that the NS LCM operation type is "NS elastic scaling" in the input parameters in steps 801 and 802.
  • the member VNF occupation resource information reflects the The amount of change of the virtual resources (the number of virtual resources added or decreased) required for the elastic extension of the member VNF instance in the NS instance elastic scaling operation.
  • the member VL occupation resource information reflects the elastic expansion operation of the nested NS instance. The amount of change in the virtual resources required for the member VL instance to flexibly scale.
  • Embodiment 5 of the present application provides a method for permitting resource management in a nested NS termination based on the second NFVO of scenario 2, as shown in FIG. 9.
  • This embodiment is an embodiment of the second embodiment, and is applied to the finalization process of the nested NS.
  • the NS LCM operation type is "NS termination" in the input parameters of steps 901 and 902, and the member VNF occupies resource information, member VL occupies resource information, and nests in step 902.
  • the input parameter such as the position constraint relationship of the NS is empty; only the indication with success or failure of the operation is returned in the permission response message of step 903.
  • the sixth embodiment of the present application provides a method for reserving resources in a nested NS LCM based on the second NFVO of the scenario 2, as shown in FIG. 10:
  • the second NFVO returns a set of resource reservation information in the grant response.
  • Each resource reservation information includes an identifier of the resource reservation, and a location and quantity of the resource reservation included in the resource reservation.
  • the location of the resource includes the VIM identification information that needs to be exchanged, the identification information of the resource area or the host, and the quantity of the resource indicates the value of the virtual computing, storage, and/or network resource reserved at the resource location.
  • the resource reservation information may further include a VNF type or a VL type to which the resource reservation is adapted.
  • the second NFVO reserves the resources to ensure that the result of the resource management is always successful.
  • the first NFVO addressing The second NFVO can be implemented by the following method:
  • the first NFVO When the first NFVO receives an NS instantiation request from Sender and creates and instantiates a new NS instance (nested NS instance), the corresponding second NFVO flag is left blank.
  • the second NFVO instantiates a composite NS instance and acquires the nested NS instance that has been successfully instantiated by subscription to form a composite NS instance to be instantiated, the second NFVO sends a notification message to the first NFVO, indicating The second NFVO uses the nested NS instance managed by the first NFVO in the composite NS instantiation process.
  • the first NFVO saves the correspondence of ⁇ nested NS instance identifier, second NFVO identifier ⁇ .
  • the second NFVO When the second NFVO terminates the composite NS instance, the second NFVO sends a notification message to the first NFVO managing the nested NS instance, indicating that the first NFVO deletes the ⁇ nested NS instance identifier, the second NFVO identifier according to the notification message.
  • the identifier of the second NFVO may be a tenant identifier. It should be noted that at the same time, only one second NFVO can be applied to the composite NS instance managed by the second NFVO using the nested NS instance.
  • the first NFVO can find the identifier of the second NFVO according to the correspondence between the nested NS instance identifier in the nested NS LCM request and the ⁇ nested NS instance identifier, the second NFVO identifier ⁇ , thereby to the second NFVO.
  • the seventh embodiment of the present application the first NFVO autonomous method for resource management in nested NS LCM operations, as shown in FIG.
  • This embodiment is another form of resource management permission in the nested NS LCM operation, that is, under the authorization of the first NFVO, bulk granting is implemented through policy configuration, and the first NFVO autonomously is within the scope of authorization.
  • the second NFVO does not participate in the resource management process in the nested NS LCM operation, but may subscribe to the first NFVO for the notification message in the resource management. For example: resource state changes in nested NS LCM operations, resource usage in nested NS LCM operations exceeds resource quota (Quota) of the first NFVO, and so on.
  • the second NFVO updates the volume licensing policy according to the received subscription notification message, and controls the first NFVO autonomously performing resource management consistency in the nested NS LCM from the virtual resource view of the composite NS. This embodiment includes the following steps:
  • the second NFVO configures a volume licensing policy to the first NFVO.
  • the volume licensing policy of the second NFVO configuration includes, but is not limited to, a resource location constraint of the first NFVO for resource management (including a defined set of VIM identifiers, resource areas, or host identifiers), The resource quota of the first NFVO in a plurality of VIM domains addressable for resource management, the effective time and/or expiration time of the volume licensing process, and the like.
  • the first NFVO receives the nested NS LCM request sent by the sender, where the request message carries the NS LCM operation type and the identifier information of the first NS instance.
  • the first NFVO performs resource management in the nested NS LCM operation according to the volume licensing policy configuration.
  • the first NFVO returns a nested NS LCM response to the sender.
  • the permission method of the nested NS LCM operation in the example of the present application configures the license policy to the first NFVO in advance by the second NFVO, so that the first NFVO can perform the operation of nesting the NS LCM according to the volume license policy configuration, thereby avoiding
  • the first NFVO needs to perform the interaction of the nested NS LCM permission request/response process to the second NFVO each time, which reduces the consumption of network resources and improves the resource management efficiency of the nested NS LCM operation.
  • the NFVO includes: a receiving unit 1201, configured to receive a nested NS LCM operation request, where the nested NS LCM operation request carries the first NS instance identification information and NS LCM operation type;
  • the sending unit 1203 is configured to send a permission request to the second NFVO according to the NS LCM operation request, requesting the second NFVO to permit the NFVO to perform virtual resource management for performing the NS LCM operation on the first NS instance, where the permission request carries Identification of the first NS instance and NS LCM operation type;
  • the receiving unit 1201 is further configured to receive a license response sent by the second NFVO according to the permission request;
  • the processing unit 1202 is configured to perform virtual resource management for performing the NS LCM operation on the first NS instance according to the license response.
  • the sending unit 1203 obtains the stored tenant identifier locally according to the identifier of the first NS instance, obtains the identifier information of the second NFVO according to the tenant identifier, and then sends a license request to the second NFVO according to the identifier information of the second NFVO. .
  • the processing unit 1202 may determine the nested NS LCM according to the local virtual resource view.
  • the virtual resource management plan of the operation is transmitted to the second NFVO through the transmitting unit 1203.
  • the virtual resource management plan includes: performing, according to the current resource situation used by the first NS instance, a type, a quantity, and/or a location of a virtual resource that needs to be added, deleted, or changed by the NS LCM operation; or the first NS
  • the type, number, and/or location of virtual resources actually occupied by the member VNF instance included in the instance in the NS LCM operation, and/or the member VL instance included in the first NS instance in the NS LCM operation The type, number, and/or location of virtual resources actually occupied.
  • the virtual resource management plan for performing the NS LCM operation for the first NS instance after the second NFVO update is further included, and the processing unit 1202 is configured according to The updated virtual resource management plan for performing the NS LCM operation for the first NS instance performs virtual resource management.
  • the NFVO device may specifically be a software product, including computer instructions that, when executed by the processor, may be used to implement the steps and functions of the execution of the first NFVO as in embodiments 1-7.
  • Embodiment 9 of the present application provides another NFVO device.
  • the NFVO device includes:
  • the receiving unit 1301 is configured to receive an NS LCM operation permission request sent by the first NFVO, where the permission request carries an identifier of the first NS instance and an NS LCM operation type;
  • the processing unit 1302 is configured to determine, according to the first NS instance identifier and the NS LCM operation type, the virtual resource view of the second NS instance managed by the NFVO, whether the NS LCM operation is performed on the first NS instance, and the NFVO management is performed.
  • the second NS instance has an impact;
  • the sending unit 1303 is configured to send a license response to the first NFVO according to the determination result.
  • the processing unit 1302 further determines, according to at least one of the following information, whether the NS LCM operation for the first NS instance has an impact on the second NS instance of the NFVO management:
  • a licensing policy for NS LCM operations of the second NS instance is a licensing policy for NS LCM operations of the second NS instance.
  • the permission request received by the receiving unit 1301 further includes:
  • the virtual resource management plan of the NS LCM operation for the first NS instance includes: adding, deleting, the NS LCM operation by referring to the current resource situation used by the first NS instance Or the type, number, and/or location of the changed virtual resource; or the type, number, and quantity of virtual resources actually occupied by the member VNF instance and/or member VL instance included in the first NS instance in the NS LCM operation / or location.
  • the processing unit 1302 may further update the virtual resource management plan for performing the NS LCM operation on the first NS instance according to the managed virtual resource view, and return to the first NFVO through the sending unit 1303.
  • the NFVO device may specifically be a software product containing computer instructions that, when executed by the processor, may be used to implement the steps and functions of the execution of the second NFVO as in embodiments 1-7.
  • Embodiment 10 of the present application provides a schematic structural diagram of NFVO, as shown in FIG.
  • the NFVO may include one or more ports 1401 coupled to a transceiver 1403.
  • the transceiver 1403 can be a transmitter, a receiver, or a combination thereof that transmits or receives data packets from other network nodes through port 1404.
  • a processor 1401 is coupled to the transceiver 1403 for processing data packets.
  • Processor 1401 can include one or more multi-core processors and/or memory 1402.
  • the processor 1401 can be a general purpose processor, an application specific integrated circuit (ASIC), or a digital signal processor (DSP).
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • the memory 1402 can be a non-transitory storage medium coupled to the processor 1401 for storing different types of data.
  • the memory 1402 may include a read only memory (ROM), a random access memory (RAM), or other types of dynamic storage devices that can store information and instructions, and may also be a disk storage.
  • Memory 1402 can be used to hold instructions that implement an NFV system or related methods. It will be appreciated that at least one of the cache and long term storage is programmed or loaded into the NFVO's processor 1401.
  • the memory 1402 stores computer executable program code, wherein the The program code includes instructions that, when executed by the processor 1401, cause the network element to perform the following operations:
  • NS LCM operation request carries an identifier of the first NS instance and an NS LCM operation type
  • a tenth embodiment of the present application provides a schematic diagram of a structure of an NFVO.
  • the NFVO may include one or more ports 1501 coupled to a transceiver 1503.
  • the transceiver 1503 can be a transmitter, a receiver, or a combination thereof that transmits or receives data packets from other network nodes through port 1504.
  • a processor 1501 is coupled to the transceiver 1503 for processing the data packets.
  • Processor 1501 can include one or more multi-core processors and/or memory 1502.
  • the processor 1501 can be a general purpose processor, an application specific integrated circuit (ASIC), or a digital signal processor (DSP).
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • the memory 1502 stores computer executable program code, wherein the program code includes instructions that, when the processor 1501 executes the instructions, cause the network element to perform the following operations:
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Maintenance And Inspection Apparatuses For Elevators (AREA)
  • Indicating And Signalling Devices For Elevators (AREA)

Abstract

本申请提供一种网络服务生命周期管理的许可方法，包括：第一NFVO接收来自发送者的NS LCM操作请求，该NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型,该第一NFVO根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，在该第二NFVO许可通过后，该第一NFVO接收所述第二NFVO许可响应，该第一NFVO根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。本申请实施例的嵌套NS生命周期管理的许可方法通过第一NFVO和第二NFVO之间的许可管理机制，实现嵌套NS LCM操作中资源管理和嵌套NS所属的复合NS的生命周期管理操作的资源管理实现目标的一致性。

Description

网络服务生命周期管理的许可方法和装置 技术领域
本申请实施例涉及通信技术，尤其涉及一种网络服务生命周期管理的许可方法和装置。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)技术是电信网络运营商通过借鉴信息技术(IT,Information Technology)领域的虚拟化技术。在通用的云服务器、交换机和存储器中将部分电信网络功能的实现进行软件和硬件解耦。这种技术需要将电信网络的功能以软件方式实现，并能在通用的服务器硬件上运行，以及可以根据需要进行迁移、实例化、和部署在网络的不同物理位置。
NFV中虚拟化的网络服务(英文：Network Service，简称：NS)可以由若干个虚拟化网络功能(Virtualized Network Function，VNF)模块实现。VNF是可部署在NFV基础架构上的网络功能的软件实现。
目前，NFV技术主要集中在虚拟网络功能和虚拟资源的动态管理和编排(MANO,Management and Orchestration)。NFV MANO功能架构如图1所示：
在网络功能虚拟化端到端(End to End，E2E)架构中，网络功能虚拟化基础设施(Network Function Virtualization Infrastructure，NFVI)包含底层硬件(Hardware，HW)资源，具体可分为计算硬件、存储硬件、网络硬件等等。硬件层之上为虚拟化层(Virtualization Layer)，包括主机操作系统(Host Operating System,Host OS)和超级管理程序/虚拟机管理器(Hypervisor)，在虚拟化层之上运行有至少两个虚拟机(Virtual Machine，VM)。在NFVI之上有多个网络虚拟功能VNF实例通过EMS系统与OSS/BSS系统相连。
NFVI通过Nf-Vi接口与虚拟化基础设施管理器(Virtualization Infrastructure Manager，VIM)相连，VNF通过Ve-Vnfm接口与VNF管理器(VNF Manager,VNFM)相连，VIM与VNFM之间通过Vi-Vnfm接口相连。VIM通过Or-Vi与网络功能虚拟化编排器(Network Functions Virtualization Orchestrator，NFVO)相连，VNFM通过Or-Vnfm接口与NFVO相连，NFVO通过Os-Ma-nfvo接口与OSS/BSS相连。
其中，OSS/BSS用于向NFVO发起网络服务生命周期管理请求，NFVO负责根据OSS/BSS发起的网络服务生命周期管理请求，编排管理资源，实现网络服务的生命周期管理，并实时监控VNF、NFVI资源的运行状态信息。VNFM负责各VNF生命周期管理，如实例化、弹性伸缩、治愈、终结VNF实例。VIM负责管理和分配NFVI的资源，检测收集NFVI运行状态信息。
在现有的NFV MANO功能架构中，NFVO对其所管理的NS实例进行资源管理。当其管理域中的VNFM接收到针对该NS实例的某个成员VNF实例进行生命周期管理(Life Cycle Management，LCM)的操作请求时，VNFM需要先向NFVO请求对所述VNF实例进行所述生命周期管理操作的资源管理许可(Granting)。当NFVO同意许可该VNF LCM操作请求后，VNFM才可以进一步和VIM进行交互，以完成该VNF LCM操作中的资源管理。
然而，现有的资源管理许可机制只适用于同一个NFVO管理的NS实例下的各成员VNF实例的生命周期管理。参考图1所示的系统架构，一个NFVO管理的虚拟资源集合属于一个管理域，不同的NFVO管理的虚拟资源集合属于不同的管理域。具体的，管理域指由一个NFVO及其管理范围内的一个或多个VNFM组成的一个MANO管理功能实体的集合。每个管理域对应一个NFVO的管理范围，该NFVO用于该管理域内的一组特定集合的网络服务的提供。此外，一个管理域还可以进一步包括一个或多个VIM以及每个VIM管理的一个或多个数据中心(Data Center)。
然而，随着业务的发展，有的NS实例有可能需要在多个管理域中提供，需要使用多个NFVO管理下的虚拟资源，比如一个大的服务提供商内通过各分支机构的协作提供服务提供商全局性的NS，各分支机构均部署包括至少一个NFVO的NFV MANO系统，构建自己的管理域。
如图2所示，NS1包含了NS2，NS1需要使用0到N个VNF实例和0到N个物理网络功能PNF(Physical Network Function)实例，以及NS2需要使用的1到N个VNF(205)实例和0到N个PNF(206)实例。
为了理解，NS1由于还包含了NS2，因此NS1被称为复合NS(Composite NS)，而被NS1包含的NS2可以称为嵌套NS(Nested NS)。嵌套NS由不同于复合NS的管理域提供。一个复合NS可以包含一个或多个嵌套NS。在本申 请中复合NS实例还可以理解为第二NS实例，嵌套NS实例还可以理解为第一NS实例。
如果采用现有的资源管理许可机制，管理复合NS的NFVO和管理嵌套NS的NFVO分别和其所属的管理域中的VNFM进行针对VNF LCM操作的资源管理许可过程，则有可能导致嵌套NS实例执行的生命周期管理操作和复合NS实例执行的生命周期管理操作目标相冲突。例如：管理嵌套NS的NFVO接收OSS/BSS发送针对嵌套NS实例弹性伸缩(scaling)操作，而此时管理复合NS的NFVO正在对该嵌套NS实例所属的复合NS实例进行治愈(healing)操作，该治愈操作要求该嵌套NS实例保持容量不变，其他被诊断为失效的嵌套NS实例或失效的VNF实例进行失效后的恢复操作。
发明内容
本申请提供一种网络服务生命周期管理的许可方法及装置，用于解决在复合NS及其成员嵌套NS在多管理域进行业务提供的场景中，嵌套NS与复合NS的LCM管理操作存在的执行资源管理的目标冲突问题。
第一方面，本申请实施例提供一种网络服务生命周期管理的许可方法，应用于复合NS及其成员嵌套NS在多管理域进行业务提供的场景中，包括：
第一网络功能虚拟化编排器接收网络服务生命周期管理操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型，其中第一NS实例的标识用以指明LCM操作针对的嵌套NS实例，NS LCM操作类型用以指明具体的NS LCM操作类别；所述第一NFVO根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；所述第二NFVO根据所述许可请求向第一NFVO发送的许可响应；所述第一NFVO根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。该网络服务生命周期管理的许可方法，由第二NFVO根据第一NFVO的许可请求判别针对第一NFVO管理的嵌套NS实例的LCM操作对当前针对第二NFVO管理的复合NS实例的LCM操作产生的影响，根据产生的影响对针对第一NFVO的NS LCM操作进行许可响应，保证嵌套NS实例执行的生命周期管理操作和该嵌套NS实例 所属的复合NS实例执行的生命周期管理操作目标的一致性。
根据第一方面的第一实施方式中，所述第一NFVO根据所述NS LCM操作请求向第二NFVO发送许可请求，包括：所述第一NFVO根据所述第一NS实例的标识从本地获取存储的租户标识，根据所述租户标识，获取所述第二NFVO的标识信息；所述第一NFVO根据所述第二NFVO的标识信息向所述第二NFVO发送许可请求。该实施方式可以使得第一NFVO能够快速寻址到第二NFVO，从而向第二NFVO发送许可请求。
根据第一方面的第二实施方式中，所述第一NFVO所管理的第一NS实例是所述第二NFVO所管理的第二NS实例的组成成员。
根据第一方面，或第一实施方式或第二实施方式的第三实施方式中，所述许可请求还包括：
针对所述第一NS实例的标识和NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：
参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者，所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VNF实例成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。该实施方式由第一NFVO在许可请求前就确定针对第一NS实例的NS LCM操作的资源管理计划，并携带在许可请求中，使得第二NFVO可以根据该资源管理计划更具有针对性的判别针对第一NFVO管理的嵌套NS实例的LCM操作对当前针对第二NFVO管理的复合NS实例的LCM操作产生的影响，判断的结果更具有针对性和准确性。
根据第一方面的第四实施方式中，所述第二NFVO进一步还根据本地存储的如下信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响：
所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员VNF实例的运行状态；
所述第二NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲 和性和/或反亲和性规则；
针对所述第二NS实例NS LCM操作的许可策略。
该实施方式中，第二NFVO不仅要判别嵌套NS LCM操作对复合NS实例LCM操作的影响，还要根据复合NS实例中的成员嵌套NS实例、成员VNF实例的亲和性/反亲和性规则判别该嵌套NS实例LCM操作所需分配的资源的位置要求，以及根据针对所述第二NS实例NS LCM操作的许可策略，确定针对该嵌套NS实例LCM操作所需分配的资源的位置和数量，保证资源分配的可行性。
根据第一方面的第五实施方式中，网络服务生命周期管理的许可方法还包括：所述第二NFVO根据所述第二NFVO管理的第二NS实例的虚拟资源视图与所述信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
所述许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。本实施方式中，由第二NFVO根据管理的第二NS实例的虚拟资源视图以及复合NS实例中的成员嵌套NS实例、成员VNF实例的亲和性/反亲和性规则判别该嵌套NS实例LCM操作所需分配的资源的位置要求，以及根据针对所述第二NS实例NS LCM操作的许可策略，调整针对该嵌套NS实例LCM操作的虚拟资源管理计划，从而减少第一NFVO从新发起许可请求，提升了NS LCM操作的效率。
第二方面，本申请实施例提供一种网络服务生命周期管理的许可方法，包括：第二NFVO接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS实例的标识和NS LCM操作类型；所述第二NFVO根据所述第一NS实例的标识和NS LCM操作类型与所述第二NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响；根据判断结果向所述第一NFVO发送许可响应。
根据第二方面的第一实施方式，所述方法还包括：所述第二NFVO进一步还根据如下本地存储的信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响：
所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成 员NS实例的运行状态，和/或第二NS实例下与第一NS实例存在依赖关系的成员VNF实例的运行状态；
所述第二NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
针对所述第二NS实例的NS LCM操作的许可策略。
根据对二方面或者第二方面的第一实施方式的第二实施方式，所述许可请求还包括：针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：
参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者，所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
根据第二方面第二实施方式的第三实施方式，所述方法还包括：
所述第二NFVO根据所述第二NFVO管理的第二NS实例的虚拟资源视图与所述本地存储的信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
所述许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，用以指示所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
第三方面，本申请实施例提供一种网络功能虚拟化编排器NFVO，包括：依次相连的接收单元、处理单元以及发送单元，其中：
接收单元，用于接收NS LCM操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
发送单元，用于根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型,其中所述NFVO所管理的第一NS实例是所述第二NFVO所管理的第二NS实例的组成成员；
所述接收单元，还用于接收所述第二NFVO根据所述许可请求发送的许 可响应；
处理单元，用于根据所述许可响应执行针对所述第一NS实例进行NS LCM操作的虚拟资源管理。
根据第三方面的第一实施方式，所述发送单元根据所述NS LCM操作请求向第二NFVO发送许可请求，包括：
所述发送单元根据所述第一NS实例的标识从本地获取存储的租户标识，根据所述租户标识，获取所述所述第二NFVO的标识信息；
所述发送单元根据所述第二NFVO的标识信息向所述第二NFVO发送许可请求。
依据第三方面或第三方面第一实施方式的第二实施方式，所述发送单元发送的许可请求还包括：
针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者，所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
依据第三方面或第三方面第一实施方式或第二实施方式的第三实施方式，所述接收单元接收的许可响应包含成功操作指示，所述处理单元根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理包括：所述处理单元根据针对所述所述第一NS实例进行NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
依据第三方面或第三方面第一实施方式或第二实施方式的第四实施方式，所述接收单元接收的许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述处理单元根据所述许可响应执行针对所述NS LCM操作的虚拟资源管理包括：
所述处理单元根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
第四方面，提供一种网络功能虚拟化编排器NFVO，该NFVO包括依次 相连的接收单元、处理单元和发送单元，其中：
接收单元，用于接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS实例的标识和NS LCM操作类型,其中所述第一NFVO所管理的第一NS实例是所述NFVO所管理的第二NS实例的组成成员；
处理单元，用于根据所述第一NS实例的标识和NS LCM操作类型与所述NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述NFVO管理的NS实例产生影响；
发送单元，用于根据判断结果向所述第一NFVO发送许可响应。
根据第四方面的第一实施方式，所述处理单元还进一步根据如下本地存储的信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述NFVO管理的NS实例产生影响：
所述NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或第二NS实例下的与第一NS实例存在依赖关系的成员VNF实例的运行状态；
所述NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
针对所述第二NS实例的NS LCM操作的许可策略。
根据第四方面或者第四方面第一实施方式的第二实施方式，所述接收单元接收的许可请求还包括：针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：
参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者，所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
根据第四方面第二实施方式的第三实施方式，所述处理单元还用于：
根据所述NFVO管理的NS实例的虚拟资源视图与所述本地存储的信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
所述发送单元发送的许可响应包含成功操作指示，还包括由所述NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划， 用以指示所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
第五方面，提供一中NFVO装置，包括：包括存储器，用于存储计算机可执行程序代码；收发器，以及处理器，与所述存储器和所述收发器耦合；
其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：接收网络服务生命周期管理操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；
接收所述第二NFVO根据所述许可请求发送的许可响应；
根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
第六方面，提供一种NFVO装置，包括存储器，用于存储计算机可执行程序代码；收发器，以及处理器，与所述存储器和所述收发器耦合；
其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：包括：接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS的实例标识和NS LCM操作类型；
根据所述第一NS实例的标识和NS LCM操作类型与所述第二NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响；
根据判断结果向所述第一NFVO发送许可响应。
第七方面，提供一种计算机程序产品，包括可执行程序代码，其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：接收网络服务生命周期管理操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作 请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；
接收所述第二NFVO根据所述许可请求发送的许可响应；
根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
第八方面，提供一种计算机程序产品，包括可执行程序代码，其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS实例的标识和NS LCM操作类型；
根据所述第一NS实例的标识和NS LCM操作类型与所述第二NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响；
根据判断结果向所述第一NFVO发送许可响应。
第九方面，本申请实施例提供了一种计算机存储介质，用于储存为上述NFVO所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
本申请实施例的嵌套NS生命周期管理的许可方法通过第一NFVO和第二NFVO之间的许可管理机制，实现嵌套NS LCM操作中资源管理和嵌套NS所属的复合NS的生命周期管理操作的资源管理实现目标的一致性，避免嵌套NS LCM操作中执行的资源管理对复合NS实例产生负面的影响。
附图说明
图1为本申请实施例应用的NFV-MANO网络架构图；
图2为本申请实施例的应用场景中的复合网络服务与嵌套网络服务之间的关系拓扑图；
图3为本申请实施例的应用场景1中网络拓扑图；
图4为本申请实施例的应用场景2中网络拓扑图；
图5为本申请实施例中基于应用场景1的嵌套网络服务生命周期管理的许可方法交互流程图；
图6为本申请实施例中基于应用场景2的嵌套网络服务生命周期管理的许 可方法交互流程图；
图7为本申请实施例中基于应用场景2的嵌套网络服务实例化操作的许可方法交互流程图；
图8为本申请实施例中基于应用场景2的嵌套网络服务弹性伸缩操作的许可方法交互流程图
图9为本申请实施例中基于应用场景2的嵌套网络服务终结操作的许可方法交互流程图；
图10为本申请实施例中基于应用场景2的嵌套网络服务生命周期管理中资源预留操作的许可方法交互流程图；
图11为本申请另一实施例的嵌套网络服务生命周期管理中的批量许可方法交互流程图；
图12为本申请一实施例的NFVO功能结构示意图；
图13为本申请另一实施例的NFVO功能结构示意图；
图14为本申请一实施例的NFVO通用物理结构示意图；
图15为本申请另一实施例的NFVO通用物理结构示意图。
具体实施方式
本申请实施例提供一种嵌套网络服务生命周期管理的许可方法及装置，用以解决现有技术中嵌套网络应用与复合网络应用生命周期管理中产生目标冲突的技术问题。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
另外，在本文中术语“第一”、“第二”仅仅是为了便于描述，用来区分不同NS、NS实例、VNF或不同VNF实例，并没有技术含义。
下面结合附图对本申请的实施方式进行详细说明。
为了名称上的区分，本申请实施例将管理复合NS的NFVO称为第二NFVO，管理嵌套NS的NFVO称为第一NFVO。
作为一个例子，在一个拥有大量用户的电信运营商中提供vEPC网络服务。假设该电信运营商的网络具有两级结构：一个总公司网络和30个省公司网络，每一个子公司网络都有自己的管理域，并配置一个NFVO。在这个场景下，总公司网络中的NFVO相当于图2中的管理NS1的NFVO,即第二NFVO；而每个省公司网络中的NFVO相当于图2中的管理NS2的NFVO，即第一NFVO。而当电信运营商确定从总公司网络的层面提供网络服务vEPC时，可以指定由A省的子公司网络提供组成vEPC的控制面网络服务，由B省子公司网络提供组成vEPC的用户面网络服务，由C省的子公司网络提供组成vEPC的策略控制网络服务。
本申请方案适用于在跨管理域的复合NS提供的场景中第二NFVO对第一NFVO在执行嵌套网络服务(Nested NS)生命周期管理操作时进行资源管理的许可。其中，第二NFVO和第一NFVO分别在其内部管理复合NS和嵌套NS的虚拟资源视图。虚拟资源视图是NFVO里面的一个数据结构，用于呈现NS实例使用的虚拟资源的状况，可以表示为组成NS实例的各成员VNF实例、成员VL实例占用的虚拟资源的类型(计算、存储、网络)和数量以及成员VNF实例的虚拟资源的位置信息，其中虚拟资源位置信息可以由VIM标识、资源区(resource zone)和/或主机标识的组合方式表示不同颗粒度的虚拟资源位置关联关系。
本申请实施例适用于如下两种场景：
场景1：复合NS和嵌套NS管理域中的VIM以及NFVI资源彼此互不相同,如图3所示为跨管理域的复合NS提供场景中各管理域的VIM互不相同。
在这种场景下，由于各管理域的VIM互不相同，复合NS实例的生命周期管理和嵌套NS实例的生命周期管理之间，以及两个不同的嵌套NS实例的生命周期管理之间的资源管理针对的目标虚拟资源空间互不重叠，因此每个NS实例，不管是复合NS实例还是嵌套NS实例的虚拟资源分配或释放可以由各管理域的NFVO独自完成，第二NFVO在许可过程中帮助第一NFVO判别嵌套NS实例LCM操作对当前复合NS实例LCM操作产生的影响。如果形成执行目标冲突， 则第二NFVO拒绝第一NFVO执行该嵌套NS实例LCM操作。
场景2：复合NS和嵌套NS管理域中的VIM以及NFVI资源彼此共享，如图4所示：在这种场景下，管理域由一个NFVO和该NFVO管理的一个或多个VNFM组成，不同的管理域共享一组相同的VIM以及VIM域内的NFVI资源。
相比于场景1，在嵌套NS LCM操作的许可过程中，第二NFVO不仅要判别嵌套NS LCM操作对复合NS实例LCM操作的影响，还要根据复合NS实例中的成员嵌套NS实例、成员VNF实例的亲和性/反亲和性规则判别该嵌套NS实例LCM操作所需分配的资源的位置要求，将建议分配的资源位置反馈给第一NFVO。其中，亲和性/反亲和性规则用于确定两个成员VNF实例是否可以部署在同一位置的虚拟资源中。
本申请实施例一提供一种基于场景1下的嵌套NS LCM操作的许可方法，如图5所示。
本实施例的方法执行之前需要配置如下信息：在Sender向第一NFVO发起嵌套NS LCM操作的请求消息之前，第一NFVO内部已经存储了调用该嵌套NS实例LCM操作的租户的标识信息(Tenant ID)。该租户标识信息可以在复合NS描述符文件的上架过程中由第二NFVO传递给第一NFVO，租户的标识信息可以为第二NFVO的标识信息，该标识信息用于第一NFVO寻址第二NFVO。同时，第二NFVO和第一NFVO分别存储了复合NS实例和嵌套NS实例的虚拟资源视图，复合NS实例的虚拟资源视图不包括嵌套NS实例的虚拟资源视图，即：嵌套NS实例的虚拟资源视图对第二NFVO不可见。
如图5所示，本实施例的嵌套NS LCM操作的许可方法包括如下步骤：
501：发送者Sender向第一NFVO发送嵌套NS LCM操作的请求消息，请求消息中携带嵌套NS实例的标识信息和NS LCM操作类型。
具体的，NS LCM操作类型可以包括但不限于NS实例化(instantiation)、NS弹性伸缩(Scaling)、NS更新(Update)、NS自愈(healing)和NS终结(termination)，请求消息中的输入参数的定义可以参考ETSI NFV IFA013协议。
502：第一NFVO根据其内部存储的租户标识信息(Tenant ID)寻址第二NFVO，向第二NFVO发起许可请求(Grant Request)，在请求消息中携带嵌套NS实例的标识信息、所执行的NS LCM操作类型。
具体的，第一NFVO存储有租户标识信息和嵌套NS实例标识信息的对应关系。第一NFVO可以根据接收到的嵌套NS LCM请求中的嵌套NS标识信息查找到存储的租户标识信息，然后再根据租户标识信息查询第二NFVO的标识信息，比如IP地址，根据该第二NFVO的标识信息向第二NFVO发送许可请求。
503:第二NFVO检验接收到的许可请求中的该嵌套NS实例的LCM操作类型，根据NS实例标识和NS LCM操作类型以及第二NFVO管理的NS实例的虚拟资源视图判断该嵌套NS LCM操作是否对第二NFVO管理的NS实例产生影响。
具体的，第二NFVO根据管理的NS实例的虚拟资源视图判断复合NS实例中是否存在与该嵌套NS实例在该LCM操作中存在依赖关系的VNF实例和/或嵌套NS实例，以及这些VNF实例和嵌套NS实例是否正在在执行存在依赖关系的LCM操作，来判断该嵌套NS LCM操作是否对第二NFVO管理的NS实例产生影响。依赖关系用于确定复合NS实例内两个成员实例(可以是嵌套NS实例或VNF实例)之间分配虚拟资源的先后顺序。例如：进行生命周期管理操作的嵌套NS实例在某个LCM操作中的资源分配依赖于其他的成员VNF实例和/或嵌套NS实例在相应的LCM操作中的资源分配的完成。
进一步的第二NFVO还可以根据相应的嵌套NS LCM许可策略，确定是否许可第一NFVO针对该嵌套NS LCM操作进行虚拟资源管理。例如：嵌套NS LCM许可策略指明在复合NS实例的负载较轻时，可以尽可能满足所有成员嵌套NS实例的资源管理请求；如果复合NS实例的负载较重，则优先满足高优先级的成员嵌套NS实例的资源管理请求。
嵌套NS LCM许可策略可以通过预配置或者通过OSS/BSS在Os-Ma-nfvo接口上配置策略信息的操作方式发送给第二NFVO。
504:第二NFVO根据判断结果向该第一NFVO发送许可响应。
如果判断不影响，则第二NFVO许可第一NFVO执行该嵌套NS LCM操作对应的虚拟资源管理，第二NFVO向第一NFVO返回许可应答消息，在该消息中携带操作成功的指示。如果判断影响，则不许可，第二NFVO向第一NFVO返回带有失败原因指示的许可应答消息。
505：第一NFVO按照许可应答消息中的许可，和相应的VIM交互，进行针 对该嵌套NS LCM操作的虚拟资源管理。
具体的，第一NFVO根据许可应答消息中的许可指示信息，和该第一NFVO对应的VIM交互，进行针对该嵌套NS LC操作的虚拟资源管理操作，如虚拟资源的分配或者释放等。
506：第一NFVO通过嵌套NS LCM应答消息向Sender返回嵌套NS LCM操作的执行结果。
本申请实施例的嵌套NS生命周期管理的许可方法通过第一NFVO和第二NFVO之间的许可管理机制，实现嵌套NS LCM操作中资源管理和嵌套NS所属的复合NS的生命周期管理操作的资源管理实现目标的一致性，避免嵌套NS LCM操作中执行的资源管理对复合NS实例产生负面的影响。
本申请实施例二：提供一种基于场景2的第二NFVO对嵌套NS LCM操作进行许可的方法，如图6所示：
本实施例描述了在场景2下执行嵌套NS LCM操作的许可过程的基本示意过程。
本实施例的过程执行之前需要做如下配置：在Sender向第一NFVO发起嵌套NS LCM操作的请求消息之前，第一NFVO内部已经存储了调用该嵌套NS实例LCM操作的租户的标识信息(Tenant ID)。该租户标识信息可以在复合NS描述符文件的上架过程中由第二NFVO传递给第一NFVO，在这里租户的标识信息可以为第二NFVO的标识信息，该标识信息用于第一NFVO寻址第二NFVO进行交互。同时，第二NFVO和第一NFVO分别存储了复合NS实例和嵌套NS实例的虚拟资源视图，且复合NS实例的虚拟资源视图包括嵌套NS实例的虚拟资源视图，也即嵌套NS实例的虚拟资源视图对第二NFVO可见。
如图6所示，本实施例包括如下步骤：
601：发送者Sender向第一NFVO发起嵌套NS LCM操作的请求消息，请求消息中携带操作类型和嵌套NS实例的标识信息。
NS LCM操作的类型可以包括但不限于NS实例化(instantiation)、NS弹性伸缩(Scaling)、NS更新(Update)、NS自愈(healing)和NS终结(termination)，操作中的输入参数的定义可以参考ETSI NFV IFA013协议。
602：第一NFVO根据其内部存储的租户标识信息(Tenant ID)寻址第二NFVO，向第二NFVO发起许可请求，在请求消息中携带嵌套NS实例的标识信息、所执行的NS LCM操作类型和针对该NS LCM操作的虚拟资源管理计划。
具体的，第一NFVO根据请求中的NS LCM操作类型，以及其内部管理的嵌套NS实例的虚拟资源视图，确定针对该NS LCM操作的虚拟资源管理计划。即根据当前该嵌套NS实例的虚拟资源分配情况，确定需要增加、删除或更改的虚拟资源的数量及位置，或者该嵌套NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或该嵌套NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。其中，第二NFVO寻址方式参考图5步骤502。
603:第二NFVO判断该嵌套NS LCM操作是否对该第二NFVO管理下的其他嵌套NS实例或者NFV实例产生影响。
具体的，第二NFVO检验接收到的许可请求中的虚拟资源管理计划，并根据该第二NFVO所管理的复合NS的资源视图，检视复合NS实例中的其它成员VNF实例或者成员嵌套NS实例是否存在执行与该嵌套NS实例LCM操作资源管理相冲突的情况，确定是否许可第一NFVO针对该嵌套NS LCM操作制定的虚拟资源管理计划。
具体判断方式中，第二NFVO可以根据复合NS实例中是否存在与该嵌套NS实例在生命周期管理操作中存在依赖关系的VNF实例和/或嵌套NS实例。例如：进行生命周期管理操作的嵌套NS实例在某个LCM操作中的资源分配依赖于其他的成员VNF实例和/或嵌套NS实例在相应的LCM操作中的资源分配的完成，以及这些VNF实例和嵌套NS实例是否正在在执行存在依赖关系的LCM操作。
进一步的，第二NFVO还可以根据相应的嵌套NS LCM许可策略来确定是否许可第一NFVO针对该嵌套NS LCM操作制定的虚拟资源管理计划。
604:第二NFVO根据判断结果向第一NFVO发送许可响应。
如果许可，则第二NFVO向第一NFVO返回许可应答消息，在该消息中携带操作成功的指示。第二NFVO进一步根据该虚拟资源管理计划更新复合NS实例的虚拟资源视图。如果不许可，第二NFVO向第一NFVO返回带有失败原因指示的许可应答消息。
作为一种可选的方案，第二NFVO进一步可以根据如下条件中的至少一种调整第一NFVO制定的针对该嵌套NS LCM操作的虚拟资源管理计划，并将更新的虚拟资源管理计划通过许可应答消息返回给第一NFVO。比如：该第二NFVO所管理的复合NS的资源视图、复合NS实例中与该嵌套NS实例在生命周期管理操作中存在依赖关系的VNF实例执行操作的状态、复合NS实例中与该嵌套NS实例在生命周期管理操作中存在依赖关系的其他嵌套NS实例的执行操作的状态和相应的嵌套NS LCM许可策略。
605：第一NFVO按照虚拟资源管理计划和相应的VIM交互，进行针对该嵌套NS LCM操作的虚拟资源管理。
该步骤具体实现可参考图5步骤505的实现方式。
606：第一NFVO通过嵌套NS LCM应答消息向Sender返回嵌套NS LCM操作的执行结果。
本申请实施例三提供一种基于场景2的第二NFVO对嵌套NS实例化操作中的资源管理进行许可的许可方法。本实施例是实施例二的一个具体化实例，应用于嵌套NS的实例化过程中。
701：发送者Sender，例如：可以是OSS/BSS，向第一NFVO发起嵌套NS实例化请求，请求消息中携带NS实例标识和资源需求描述参数。
该嵌套NS实例化请求还可包括反映该嵌套NS特定拓扑的模板标识(Flavor ID)和该嵌套NS实例的成员VNF实例部署位置的约束信息等。
702：第一NFVO根据该嵌套NS实例化请求寻址第二NFVO，向该第二NFVO发送许可请求。
具体的，在发送许可请求之前，第一NFVO解析嵌套NS实例化请求中的输入参数，根据请求消息中对嵌套NS实例在NS实例化操作中的资源需求描述，例如：该NS实例化等级对应的虚拟资源的基本需求，形成对组成该嵌套NS实例的成员VNF实例和成员VL实例的资源管理计划，即成员VNF实例占用资源信息和成员VNF实例占用资源信息。
此后，第一NFVO向第二NFVO发起许可请求，在请求消息中携带嵌套NS实例标识、该NS LCM操作类型(即：LCM操作类型＝NS实例化)、成员VNF 占用资源信息、成员VL占用资源信息以及嵌套NS的资源位置约束关系。
其中，嵌套NS实例标识用于在第一NFVO内唯一标识嵌套NS实例，NS LCM操作类型用于指示许可请求中的NS生命周期管理操作类型。成员VNF占用资源信息包括组成该嵌套NS实例的成员VNF实例化所需的虚拟资源(计算、存储和网络)的数量，成员VL占用资源信息包括成员VL实例化所需的虚拟资源(网络)的数量。嵌套NS的资源位置约束关系表示在嵌套NS LCM操作中资源管理位置限定的描述信息，可以是根据成员VNF实例和/或成员VL实例之间的亲和性/反亲和性规则确定的相对位置限定，例如：嵌套NS实例化需要部署在同一资源区(resource zone)若干相邻的主机(host)上；也可以是反映成员VNF实例和/或成员VL实例部署的绝对物理位置限定，例如，嵌套NS实例化需要部署在主机A1、A2和A3的范围内。资源位置可以由VIM标识、资源区和/或主机的标识来表示。
703：第二NFVO根据第一NFVO发送的许可请求，确实是否允许该第一NFVO进行NS实例化操作的资源管理，并向该第一NFVO发送许可应答。
具体的，第二NFVO根据复合NS实例的虚拟资源视图、该复合NS实例的成员嵌套NS实例的依赖关系，和/或相应的嵌套NS LCM许可策略，向第一NFVO返回许可应答，在许可应答消息中携带第一NFVO需要交互的VIM标识，资源区和/或主机的标识(资源位置信息)，这些资源位置信息用于指出第二NFVO所建议的对该嵌套NS实例进行该类型的生命周期管理操作所需资源的位置。
第二NFVO在应答消息中还可以携带在每个VIM下分配给嵌套NS实例化操作的实际资源信息，例如：实际分配的该嵌套NS实例的成员VNF实例化所需的虚拟资源(计算、存储和网络)的数量，成员VL实例化的虚拟资源(网络)的数量。
704：第一NFVO按照许可应答中提供的信息和相应的VIM进行交互，完成嵌套NS实例生命周期管理中的资源管理。
具体的，第一NFVO根据许可应答中的VIM标识，资源区和/或主机的标识与对应的VIM交互，并根据实际分配的该嵌套NS实例的成员VNF实例化所需的虚拟资源(计算、存储和网络)的数量，成员VL实例化的虚拟资源(网络)的数量进行资源分配。
705：第一NFVO向Sender返回嵌套NS实例化应答，指示完成该嵌套NS实例化操作。
本申请实施例四提供一种基于场景2的第二NFVO对嵌套NS弹性伸缩中的资源管理进行许可的方法，如图8所示。
本实施例是实施例二的一个具体化实例，应用于嵌套NS的弹性伸缩scaling操作过程中。本实施例的步骤和实施例3相似，不同的是在步骤801和802中的输入参数中NS LCM操作类型是“NS弹性伸缩(scaling)”，在步骤802中成员VNF占用资源信息是反映该嵌套NS实例弹性伸缩操作中的成员VNF实例进行弹性伸缩所需的虚拟资源的变化量(增加或减少的虚拟资源数量)，成员VL占用资源信息是反映该嵌套NS实例弹性伸缩操作中的成员VL实例进行弹性伸缩所需的虚拟资源的变化量。其他步骤的的具体实现可参考图7实施例3的描述。
本申请实施例五提供一种基于场景2的第二NFVO对嵌套NS终结中的资源管理进行许可的方法，如图9所示。
本实施例是实施例二的一个具体化实例，应用于嵌套NS的终结过程中。本实施例与实施例3相比，在步骤901和902的输入参数中NS LCM操作类型是“NS终结(termination)”，在步骤902中成员VNF占用资源信息、成员VL占用资源信息以及嵌套NS的位置约束关系等输入参数为空；步骤903的许可应答消息中只返回带有操作成功或失败的指示。
本申请实施例六提供一种基于场景2的第二NFVO对嵌套NS LCM中的资源进行预留的方法，如图10所示：
本实施例和实施例2的过程相似，除了步骤1003其他步骤不再赘述。在步骤1003中，第二NFVO在许可应答中返回一组资源预留的信息。每个资源预留信息包括资源预留的标识、该资源预留所包含的资源预留的位置和数量。其中，资源的位置包括需要交互的VIM标识信息、资源区或主机的标识信息，资源数量指出在该资源位置处预留的虚拟计算、存储和/或网络资源的数值。可选地，资源预留信息还可以包括该资源预留所适配的VNF类型或VL类型。
本实施例中，第一NFVO在步骤1004和资源预留信息中指定的VIM进行资源管理时，由于第二NFVO对资源的预留从而保证资源管理的结果总是成功的。
在实施例一到实施例六的嵌套NS LCM操作的许可方法中，第一NFVO寻址 第二NFVO可以通过下述的方法实现：
当第一NFVO接收来自Sender的NS实例化请求而创建并实例化一个新的NS实例(嵌套NS实例)时，对应的第二NFVO标识置空。当第二NFVO实例化一个复合NS实例、并通过订阅方式获取已经成功实例化的嵌套NS实例来组成要实例化的复合NS实例时，第二NFVO向第一NFVO发送一个通知消息，指示第二NFVO在复合NS实例化过程中使用第一NFVO管理的嵌套NS实例。第一NFVO保存{嵌套NS实例标识，第二NFVO标识}的对应关系。当第二NFVO终结该复合NS实例时，第二NFVO向管理该嵌套NS实例的第一NFVO发送一个通知消息，指示第一NFVO根据该通知消息删除{嵌套NS实例标识，第二NFVO标识}的对应关系。该第二NFVO的标识可以是租户标识。需要注意的是，在同一时刻，只能有一个第二NFVO使用该嵌套NS实例应用于该第二NFVO管理的复合NS实例中。这样，第一NFVO就可以根据嵌套NS LCM请求中的嵌套NS实例标识与{嵌套NS实例标识，第二NFVO标识}的对应关系的查找到第二NFVO的标识，从而向第二NFVO发送许可请求。
本申请实施例七：第一NFVO自主进行嵌套NS LCM操作中的资源管理的方法，如图11所示：
本实施例是嵌套NS LCM操作中资源管理许可的另一种形式，即：在第一NFVO的授权下，通过策略配置实现批量许可(bulk granting)，第一NFVO在授权的范围内自主地和VIM进行交互，执行嵌套NS LCM操作中的资源管理。第二NFVO不参与嵌套NS LCM操作中的资源管理过程，但可以向第一NFVO订阅该资源管理中的通知消息。例如：嵌套NS LCM操作中的资源状态改变，嵌套NS LCM操作中的资源使用数量超过该第一NFVO的资源配额(Quota)，等等。第二NFVO根据接收到的订阅通知消息更新批量许可策略，从复合NS的虚拟资源视图控制第一NFVO自主进行嵌套NS LCM中资源管理的一致性。该实施例包括如下步骤：
1100：第二NFVO向第一NFVO配置批量许可策略。
该步骤可以理解为第一NFVO自主进行嵌套NS LCM操作中的资源管理的必要前提条件。第二NFVO配置的批量许可策略包括但不限于：第一NFVO进行资源管理的资源位置约束(包括一组限定的VIM标识、资源区或主机标识)、 第一NFVO在多个可寻址进行资源管理的VIM域内的资源配额，批量许可过程的生效时间和/或失效时间等等。
1101：第一NFVO接收发送者发送的嵌套NS LCM请求，请求消息中携带NS LCM操作类型和第一NS实例的标识信息。
具体实现可参考实施例3-6的对应步骤的具体描述。
1102：第一NFVO根据批量许可策略配置执行嵌套NS LCM操作中的资源管理。
1103：第一NFVO向发送者返回嵌套NS LCM应答。
本申请实例的嵌套NS LCM操作的许可方法，通过第二NFVO提前批量将许可策略配置到第一NFVO上，使得第一NFVO可以自行根据批量许可策略配置进行嵌套NS LCM的操作，避免了第一NFVO每次都需要向第二NFVO进行嵌套NS LCM的许可请求/应答过程的交互，减少了网络资源的消耗，也提升了嵌套NS LCM操作的资源管理效率。
本申请实施例八提供一种NFVO装置，如图12所示，该NFVO包括：接收单元1201，用于接收嵌套NS LCM操作请求，该嵌套NS LCM操作请求携带第一NS实例标识信息和NS LCM操作类型；
发送单元1203，用于根据NS LCM操作请求向第二NFVO发送许可请求，请求第二NFVO准许该NFVO执行针对针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理，该许可请求携带第一NS实例的标识和NS LCM操作类型；
所述接收单元1201，还用于接收所述第二NFVO根据所述许可请求发送的许可响应；
处理单元1202，用于根据许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
具体的，发送单元1203根据第一NS实例的标识从本地获取存储的租户标识，根据所述租户标识，获取第二NFVO的标识信息，然后根据第二NFVO的标识信息向第二NFVO发送许可请求。
具体的，处理单元1202可以根据本地虚拟资源视图确定该嵌套NS LCM 操作的虚拟资源管理计划，通过发送单元1203发送给第二NFVO。该虚拟资源管理计划包括：参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
具体的，当接收单元1201接收的许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划,处理单元1202根据更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
以上NFVO包含的各单元所执行操作的具体实现方式可以参照实施例1-7的对应的第一NFVO执行的步骤，不再赘述。
该NFVO装置具体可以是软件产品，包含计算机指令，当该计算机指令被处理器执行时，可以用来实现如实施例1-7中的第一NFVO的执行的步骤和功能。
本申请实施例九提供另外一种NFVO装置，如图13所示，该NFVO装置包含：
接收单元1301，用于接收第一NFVO发送的NS LCM操作许可请求，该许可请求携带第一NS实例的标识和NS LCM操作类型；
处理单元1302，用于根据第一NS实例标识和NS LCM操作类型与NFVO管理的第二NS实例的虚拟资源视图判断针对所述第一NS实例进行所述NS LCM操作是否对该NFVO管理的第二NS实例产生影响；
发送单元1303，用于根据判断结果向第一NFVO发送许可响应。
处理单元1302还进一步根据如下信息中至少一种判断针对所述第一NS实例进行所述NS LCM操作是否对该NFVO管理的第二NS实例产生影响：
所述NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或第二NS实例下与第一NS实例存在依赖关系的成员VNF实例的运行状态；
所述NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
针对所述第二NS实例的NS LCM操作的许可策略。
具体的，接收单元1301接收的许可请求还包括：
针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置；或者所述第一NS实例所包括的成员VNF实例和/或成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
处理单元1302还可以根据管理的虚拟资源视图更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，通过发送单元1303返回给第一NFVO。
以上NFVO包含的各单元所执行操作的具体实现方式可以参照实施例1-7的对应的第二NFVO执行的步骤，不再赘述。
该NFVO装置具体可以是软件产品，包含计算机指令，当该计算机指令被处理器执行时，可以用来实现如实施例1-7中的第二NFVO的执行的步骤和功能。
本申请实施例十提供一种NFVO的结构示意图,如图14所示。该NFVO可包含一个或多个端口1401，与收发器(transceiver)1403相耦合。收发器1403可以是发射器，接收器或其组合，从其他网络节点通过端口1404发送或接收数据包。处理器1401耦合到收发器1403，用于处理数据包。处理器1401可包含一个或多个多核处理器和/或存储器1402。处理器1401可以是一个通用处理器，专用集成电路(application specific integrated circuit，ASIC)，或数字信号处理器(DSP)。
存储器1402可为非瞬时性的存储介质，与处理器1401相耦合，用于保存不同类型的数据。存储器1402可包含只读存储器(read only memory，ROM),随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是磁盘存储器。存储器1402可用于保存实现NFV系统或相关方法的指令。可以理解，通过编程或装载可执行指令到该NFVO的处理器1401，缓存和长期存储中的至少一个。
另一个实施例中，存储器1402，存储计算机可执行程序代码,其中所述 程序代码包括指令，当所述处理器1401执行所述指令时，所述指令使所述网元执行以下操作：
接收网络服务生命周期管理操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；
接收所述第二NFVO根据所述许可请求发送的许可响应；
根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
以上作为NFVO包含的处理器所执行操作的具体实现方式可以参照1-7中的第一NFVO的执行的步骤和功能，本申请实施例不再赘述。
本申请实施例十提供一种NFVO的结构示意图,如图15所示,该NFVO可包含一个或多个端口1501，与收发器(transceiver)1503相耦合。收发器1503可以是发射器，接收器或其组合，从其他网络节点通过端口1504发送或接收数据包。处理器1501耦合到收发器1503，用于处理数据包。处理器1501可包含一个或多个多核处理器和/或存储器1502。处理器1501可以是一个通用处理器，专用集成电路(application specific integrated circuit，ASIC)，或数字信号处理器(DSP)。
在另外一个实施例中,存储器1502，存储计算机可执行程序代码,其中所述程序代码包括指令，当所述处理器1501执行所述指令时，所述指令使所述网元执行以下操作：
接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS的实例标识和NS LCM操作类型；
根据所述第一NS实例的标识和NS LCM操作类型与所述NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述NFVO管理的第二NS实例产生影响；
根据判断结果向所述第一NFVO发送许可响应。。
以上作为NFVO包含的处理器所执行操作的具体实现方式可以参照1-7中的第二NFVO的执行的步骤和功能，本申请实施例不再赘述。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (23)

  1. 一种网络服务生命周期管理的许可方法，其特征在于，包括：
    第一网络功能虚拟化编排器(Network Function Virtualization Orchestrator,NFVO)接收网络服务(Network Service,NS)生命周期管理(Life Cycle Management,LCM)操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
    所述第一NFVO根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述第一NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；
    所述第一NFVO接收所述第二NFVO根据所述许可请求发送的许可响应；
    所述第一NFVO根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
  2. 如权利要求1所述的许可方法，其特征在于，所述第一NFVO根据所述NS LCM操作请求向第二NFVO发送许可请求，包括：
    所述第一NFVO根据所述第一NS实例的标识从本地获取存储的租户标识，根据所述租户标识，获取所述第二NFVO的标识信息；
    所述第一NFVO根据所述第二NFVO的标识信息向所述第二NFVO发送许可请求。
  3. 如权利要求1或2所述的许可方法，其特征在于，所述第一NFVO所管理的第一NS实例是所述第二NFVO所管理的第二NS实例的组成成员。
  4. 如权利要求1-3任一项所述的许可方法，其特征在于，所述许可请求还包括：
    针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划。
  5. 如权利要求4所述的许可方法，其特征在于，所述虚拟资源管理计划包括：
    参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置，或者，
    所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占 用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
  6. 如权利要求1-5任一项所述的许可方法，其特征在于，所述方法还包括：
    所述第二NFVO根据所述第一NS实例的标识和NS LCM操作类型与所述第二NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响；
    根据判断结果向所述第一NFVO发送许可响应。
  7. 如权利要求6所述的许可方法，其特征在于，所述第二NFVO进一步还根据本地存储的如下信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响：
    所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员VNF实例的运行状态；
    所述第二NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
    针对所述第二NS实例NS LCM操作的许可策略。
  8. 如权利要求6或7所述的许可方法，其特征在于，所述许可响应包含成功操作指示，所述第一NFVO根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理包括：
    所述第一NFVO根据针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
  9. 如权利要求6或7所述的许可方法，其特征在于，所述方法还包括：
    所述第二NFVO根据所述第二NFVO管理的第二NS实例的虚拟资源视图与所述信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
    所述许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述第一NFVO根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理包括：
    所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS  LCM操作的虚拟资源管理计划执行虚拟资源管理。
  10. 一种网络服务生命周期管理的许可方法，其特征在于，包括：
    第二NFVO接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS实例的标识和NS LCM操作类型；
    所述第二NFVO根据所述第一NS实例的标识和NS LCM操作类型与所述第二NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响；
    根据判断结果向所述第一NFVO发送许可响应。
  11. 如权利要求10所述的许可方法，其特征在于，所述方法还包括：所述第二NFVO进一步还根据如下本地存储的信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述第二NFVO管理的第二NS实例产生影响：
    所述第二NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或所述第二NFVO管理的第二NS实例下成员VNF实例的运行状态；
    所述第二NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
    针对所述第二NS实例的NS LCM操作的许可策略。
  12. 如权利要求10或11所述的许可方法，其特征在于，所述许可请求还包括：
    针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：
    参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置，或者
    所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
  13. 如权利要求12所述的许可方法，其特征在于，所述方法还包括：
    所述第二NFVO根据所述第二NFVO管理的第二NS实例的虚拟资源视图与所述本地存储的信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
    所述许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，用以指示所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
  14. 一种网络功能虚拟化编排器NFVO，其特征在于，包括：
    接收单元，用于接收NS LCM操作请求，所述NS LCM操作请求携带第一NS实例的标识和NS LCM操作类型；
    发送单元，用于根据所述NS LCM操作请求向第二NFVO发送许可请求，请求所述第二NFVO准许所述NFVO执行针对所述第一NS实例进行所述NS LCM操作请求的虚拟资源管理，所述许可请求携带所述第一NS实例的标识和NS LCM操作类型；
    所述接收单元，还用于接收所述第二NFVO根据所述许可请求发送的许可响应；
    处理单元，用于根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理。
  15. 如权利要求14所述的网络功能虚拟化编排器，其特征在于，所述发送单元根据所述NS LCM操作请求向第二NFVO发送许可请求，包括：
    所述发送单元根据所述第一NS实例的标识从本地获取存储的租户标识，根据所述租户标识，获取所述所述第二NFVO的标识信息；
    所述发送单元根据所述第二NFVO的标识信息向所述第二NFVO发送许可请求。
  16. 如权利要求14或15所述的网络功能虚拟化编排器，其特征在于，所述NFVO所管理的第一NS实例是所述第二NFVO所管理的第二NS实例的组成成员。
  17. 如权利要求14-16任一项所述的网络功能虚拟化编排器，其特征在于，所述发送单元发送的许可请求还包括：
    针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置，或者，
    所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
  18. 如权利要求17所述的网络功能虚拟化编排器，其特征在于，所述接收单元接收的许可响应包含成功操作指示，所述处理单元根据所述许可响应执行针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理包括：
    所述处理单元根据针对所述所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
  19. 如权利要求17所述的网络功能虚拟化编排器，其特征在于，所述接收单元接收的许可响应包含成功操作指示，还包括由所述第二NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述处理单元根据所述许可响应执行针对所述NS LCM操作的虚拟资源管理包括：
    所述处理单元根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
  20. 一种网络功能虚拟化编排器NFVO，其特征在于，包括：
    接收单元，用于接收第一NFVO发送的NS LCM操作许可请求，所述许可请求携带第一NS实例的标识和NS LCM操作类型；
    处理单元，用于根据所述第一NS实例的标识和NS LCM操作类型与所述NFVO管理的第二NS实例的虚拟资源视图判断对所述第一NS实例进行所述NS LCM操作是否对所述NFVO管理的第二NS实例产生影响；
    发送单元，用于根据判断结果向所述第一NFVO发送许可响应。
  21. 如权利要求20所述的网络功能虚拟化编排器，其特征在于，所述处理单元还进一步根据如下本地存储的信息中至少一种判断对所述第一NS实例进行所述NS LCM操作是否对所述NFVO管理的第二NS实例产生影响：
    所述NFVO管理的第二NS实例下与第一NS实例存在依赖关系的成员NS实例的运行状态，和/或所述NFVO管理的第二NS实例下成员VNF实例的运行状态；
    所述NFVO管理的第二NS实例下定义的与第一NS实例相关联的亲和性和/或反亲和性规则；
    针对所述第二NS实例的NS LCM操作的许可策略。
  22. 如权利要求21所述的网络功能虚拟化编排器，其特征在于，所述接 收单元接收的许可请求还包括：
    针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，所述虚拟资源管理计划包括：
    参照所述第一NS实例所使用的当前资源情况进行所述NS LCM操作需要增加、删除或更改的虚拟资源的类型、数量和/或位置，或者，
    所述第一NS实例所包括的成员VNF实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置，和/或所述第一NS实例所包括的成员VL实例在所述NS LCM操作中实际占用的虚拟资源的类型、数量和/或位置。
  23. 如权利要求22所述的网络功能虚拟化编排器，其特征在于，所述处理单元还用于：
    根据所述NFVO管理的NS实例的虚拟资源视图与所述本地存储的信息中的至少一种更新针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划；
    所述发送单元发送的许可响应包含成功操作指示，还包括由所述NFVO更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划，用以指示所述第一NFVO根据所述更新后的针对所述第一NS实例进行所述NS LCM操作的虚拟资源管理计划执行虚拟资源管理。
PCT/CN2016/106288 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置 WO2018090299A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
CN202110013719.9A CN112799779A (zh) 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置
EP16921857.5A EP3534568B1 (en) 2016-11-17 2016-11-17 Network service lifecycle management permission granting method and device
ES16921857T ES2932756T3 (es) 2016-11-17 2016-11-17 Método y dispositivo de concesión de permisos para la gestión del ciclo de vida del servicio de red
PCT/CN2016/106288 WO2018090299A1 (zh) 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置
KR1020197016894A KR102272229B1 (ko) 2016-11-17 2016-11-17 네트워크 서비스 라이프 사이클 관리 승인 방법 및 장치
EP22205140.1A EP4195608A1 (en) 2016-11-17 2016-11-17 Network service life cycle management grant method and apparatus
CN201680090856.XA CN109964449B (zh) 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置
JP2019526235A JP6738965B2 (ja) 2016-11-17 2016-11-17 ネットワークサービスライフサイクル管理許可方法及び装置
US16/415,840 US10911333B2 (en) 2016-11-17 2019-05-17 Network service life cycle management grant method and apparatus
US17/146,091 US11271827B2 (en) 2016-11-17 2021-01-11 Network service life cycle management grant method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/106288 WO2018090299A1 (zh) 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/415,840 Continuation US10911333B2 (en) 2016-11-17 2019-05-17 Network service life cycle management grant method and apparatus

Publications (1)

Publication Number Publication Date
WO2018090299A1 true WO2018090299A1 (zh) 2018-05-24

Family

ID=62145941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106288 WO2018090299A1 (zh) 2016-11-17 2016-11-17 网络服务生命周期管理的许可方法和装置

Country Status (7)

Country Link
US (2) US10911333B2 (zh)
EP (2) EP4195608A1 (zh)
JP (1) JP6738965B2 (zh)
KR (1) KR102272229B1 (zh)
CN (2) CN109964449B (zh)
ES (1) ES2932756T3 (zh)
WO (1) WO2018090299A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021004320A1 (zh) * 2019-07-11 2021-01-14 华为技术有限公司 服务资源许可管理方法和相关设备
CN112448833A (zh) * 2019-09-02 2021-03-05 华为技术有限公司 一种多管理域的通信方法和装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11405177B2 (en) * 2017-01-24 2022-08-02 Microsoft Technology Licensing, Llc Nested enclave identity
BR112019025898A2 (pt) 2017-06-09 2020-06-30 Telefonaktiebolaget Lm Ericsson (Publ) método para manter um serviço de função de rede virtual e disponibilidade e continuidade de serviço de rede, gerenciador de infraestrutura virtual, e, sistema com base em nuvem
US11070432B2 (en) * 2017-07-20 2021-07-20 Cisco Technology, Inc. Dynamic and customizable virtual network functions
EP3723325B1 (en) * 2017-12-29 2022-09-14 Huawei Technologies Co., Ltd. Network service management method, related device and system
US11382150B2 (en) * 2018-03-26 2022-07-05 Apple Inc. System and method of managing PNF connectivity in a network slice instance
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
US11032164B1 (en) * 2019-05-30 2021-06-08 Cox Communications, Inc. Edge-based cloud application acceleration
WO2021115587A1 (en) * 2019-12-11 2021-06-17 Huawei Technologies Duesseldorf Gmbh Techniques for managing access rights to a shared network slice instance and network slice subnetwork instance
JP7409504B2 (ja) 2020-07-03 2024-01-09 日本電信電話株式会社 ネットワーク仮想化システム、仮想リソース管理装置、仮想リソース管理方法およびプログラム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015180068A1 (zh) * 2014-05-28 2015-12-03 华为技术有限公司 一种实现虚拟化网管的方法、装置及系统
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理系统
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
WO2016114866A1 (en) * 2015-01-13 2016-07-21 Intel IP Corporation Techniques for monitoring virtualized network functions or network functions virtualization infrastructure
WO2016121736A1 (ja) * 2015-01-27 2016-08-04 日本電気株式会社 オーケストレータ装置、システム、仮想マシンの作成方法及びプログラム

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217678B (zh) * 2007-12-28 2011-08-24 华为技术有限公司 一种系统升级方法、系统及装置
CN101552739A (zh) * 2008-04-03 2009-10-07 北京邮电大学 一种网络服务流程实例生命周期管理的方法及系统
CN101387976B (zh) * 2008-11-07 2010-06-02 清华大学 一种基于数据差异的逻辑卷快速同步方法
CN105429839B (zh) * 2014-09-09 2019-11-19 中兴通讯股份有限公司 虚拟化网络功能vnf优化方法、装置及系统
CN105812171B (zh) * 2014-12-31 2019-06-11 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备
US9912558B2 (en) * 2015-01-13 2018-03-06 Intel IP Corporation Techniques for monitoring virtualized network functions or network functions virtualization infrastructure
EP3253005A4 (en) * 2015-01-29 2018-01-17 Nec Corporation Data file registration management system, method, management device, and program
US10263911B2 (en) * 2015-05-01 2019-04-16 Futurewei Technologies, Inc. System and method for resource management
CN107533484B (zh) * 2015-05-07 2021-03-02 华为技术有限公司 用于动态管理虚拟网络功能描述符的系统和方法
CN106375101B (zh) * 2015-07-20 2019-08-27 华为技术有限公司 一种生命周期管理方法及装置
CN107852337B (zh) * 2015-07-23 2021-07-13 英特尔公司 支持网络功能虚拟化生命周期管理的网络资源模型
US10187324B2 (en) * 2015-08-10 2019-01-22 Futurewei Technologies, Inc. System and method for resource management

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015180068A1 (zh) * 2014-05-28 2015-12-03 华为技术有限公司 一种实现虚拟化网管的方法、装置及系统
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理系统
WO2016114866A1 (en) * 2015-01-13 2016-07-21 Intel IP Corporation Techniques for monitoring virtualized network functions or network functions virtualization infrastructure
WO2016121736A1 (ja) * 2015-01-27 2016-08-04 日本電気株式会社 オーケストレータ装置、システム、仮想マシンの作成方法及びプログラム
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Non-Patent Citations (1)

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

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021004320A1 (zh) * 2019-07-11 2021-01-14 华为技术有限公司 服务资源许可管理方法和相关设备
CN112448833A (zh) * 2019-09-02 2021-03-05 华为技术有限公司 一种多管理域的通信方法和装置
WO2021043066A1 (zh) * 2019-09-02 2021-03-11 华为技术有限公司 一种多管理域的通信方法和装置
CN112448833B (zh) * 2019-09-02 2022-05-17 华为技术有限公司 一种多管理域的通信方法和装置
EP4024761A4 (en) * 2019-09-02 2022-10-26 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS FOR MULTIPLE MANAGEMENT FIELDS
JP2022546131A (ja) * 2019-09-02 2022-11-02 華為技術有限公司 複数の管理領域のための通信方法及び装置
JP7405955B2 (ja) 2019-09-02 2023-12-26 華為技術有限公司 複数の管理領域のための通信方法及び装置

Also Published As

Publication number Publication date
KR20190084294A (ko) 2019-07-16
US10911333B2 (en) 2021-02-02
US11271827B2 (en) 2022-03-08
ES2932756T3 (es) 2023-01-25
JP2019536365A (ja) 2019-12-12
KR102272229B1 (ko) 2021-07-05
EP4195608A1 (en) 2023-06-14
JP6738965B2 (ja) 2020-08-12
US20190273668A1 (en) 2019-09-05
US20210135958A1 (en) 2021-05-06
EP3534568B1 (en) 2022-11-09
CN109964449A (zh) 2019-07-02
EP3534568A1 (en) 2019-09-04
CN109964449B (zh) 2021-01-15
EP3534568A4 (en) 2019-12-11
CN112799779A (zh) 2021-05-14

Similar Documents

Publication Publication Date Title
WO2018090299A1 (zh) 网络服务生命周期管理的许可方法和装置
US10701139B2 (en) Life cycle management method and apparatus
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
CN110569101B (zh) 管理容器服务的方法和装置
EP3455728B1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
WO2016184045A1 (zh) 一种网络业务扩容的方法和装置
US20180191581A1 (en) Method and Apparatus for Deploying Network Service
US11611481B2 (en) Policy management method and system, and apparatus
CN107967140B (zh) 软件修改的发起方法、发布元数据的方法及装置
KR20180002771A (ko) 네트워크 서비스 수명 주기 관리 방법 및 디바이스
WO2017185303A1 (zh) 一种nfv mano策略描述符的管理方法及装置
CN106856438B (zh) 一种网络业务实例化的方法、装置及nfv系统
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
US20210248070A1 (en) Data transmission method and apparatus
EP3468105A1 (en) Method and apparatus for arranging network resources
WO2019001140A1 (zh) 一种管理vnf实例化的方法和设备
CN112887121A (zh) 一种管理网络服务的方法、设备及系统
WO2016101639A1 (zh) 负载均衡器的连接方法、业务的实例化部署方法及装置
CN116724543A (zh) 容器集群的管理方法和装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
WO2018014351A1 (zh) 一种资源配置方法及装置
WO2023274014A1 (zh) 容器集群的存储资源管理方法、装置及系统
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019526235

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197016894

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016921857

Country of ref document: EP

Effective date: 20190530