WO2018072503A1 - 软件修改的发起方法、发布元数据的方法及装置 - Google Patents

软件修改的发起方法、发布元数据的方法及装置 Download PDF

Info

Publication number
WO2018072503A1
WO2018072503A1 PCT/CN2017/093415 CN2017093415W WO2018072503A1 WO 2018072503 A1 WO2018072503 A1 WO 2018072503A1 CN 2017093415 W CN2017093415 W CN 2017093415W WO 2018072503 A1 WO2018072503 A1 WO 2018072503A1
Authority
WO
WIPO (PCT)
Prior art keywords
software
vnf
instance
vnfc
version
Prior art date
Application number
PCT/CN2017/093415
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 EP17862212.2A priority Critical patent/EP3518465B1/en
Priority to EP20208739.1A priority patent/EP3839726B1/en
Publication of WO2018072503A1 publication Critical patent/WO2018072503A1/zh
Priority to US16/388,852 priority patent/US10742502B2/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/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • 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/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
    • 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
    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures

Definitions

  • the present application relates to the field of software technologies, and in particular, to a method for initiating software modification, a method for releasing metadata, and an apparatus.
  • NFV Network Function Virtualization
  • OSS/BSS/EM Support System/Business Support System/Element Manager
  • MANO Management and Orchestration
  • VNF Virtualization Network Function
  • the application provides a method for initiating software modification, a method and device for releasing metadata, in order to realize automatic operation of modifying VNF software in an NFV system.
  • an embodiment of the present invention provides a method for initiating a software modification, which is applied to a network function virtualization NFV system, where the NFV system includes a virtualized network function manager VNFM, including:
  • the VNFM receives a virtualized network function VNF lifecycle management LCM request, and the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be modified;
  • the VNFM Determining, by the VNFM, that the type of the VNF LCM request is a software modification operation and acquiring metadata according to the VNF LCM request, where the metadata includes a version identifier and a software modification type of the first version of the VNF software;
  • the VNFM Determining, by the VNFM, the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified;
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type.
  • the VNFM first determines the software modification operation by using the VNF LCM request in the NFV system, and secondly, obtains the metadata according to the VNF LCM request, and again, according to the version in the metadata.
  • the identifier and the instance identifier in the VNF LCM determine the first VNF instance of the first version of the VNF software to be modified, and finally, the software modification operation is initiated according to the first VNF instance of the first version of the VNF software to be modified according to the software modification type in the metadata. It can be seen that the initiation process of the software modification operation of the first VNF instance of the first version of the VNF software is sequentially executed by the VNFM, and the automatic operation of the VNF software modification in the NFV system is realized without user participation. Work.
  • the NFV system includes a network function virtualization orchestrator NFVO; the VNFM receives a virtualized network function VNF lifecycle management LCM request, including:
  • the VNFM receives the virtualized network function VNF lifecycle management LCM request sent by the NFVO.
  • the NFV system operates with the first VNF instance, the first VNF instance being obtained by the NFV system instantiating the first version of the VNF software;
  • the software modification type initiates a software modification operation on the first VNF instance of the first version of the VNF software, including:
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type.
  • the VNFM is Software modification operation for the first VNF instance of the first version of the VNF software initiated during the operation of the first VNF instance, that is, the software modification process initiates the operation without interrupting the first VNF instance currently running by the NFV system
  • the software modification operation of the first version of the VNF software can be initiated, which is beneficial to maintaining the stability and business continuity of the NFV system during the VNF software modification process.
  • the software modification type in the metadata is a VNF software upgrade.
  • the NFV system further includes a network element manager EM and a virtualized network function operation and maintenance unit VNF O&M, the VNFM first to the first version of the VNF software according to the software modification type
  • the VNF instance initiates software modification operations, including:
  • the VNFM acquires a deployment option for instantiating a second version of the VNF software as a second VNF instance;
  • the VNFM instantiates the second version of the VNF software as the second VNF instance according to the deployment option
  • VNFM Sending, by the VNFM, a software upgrade request to the EM or the VNF O&M, where the software upgrade request is used to indicate that the EM or the VNF O&M upgrades the first VNF instance of the first version of the VNF software to the The second VNF instance of the second version of the VNF software.
  • the VNFM is After the resources of the second VNF instance are established, the EM or VNF O&M is notified to initiate the software upgrade, that is, the second instance is established, and then the EM or VNF O&M is further notified to perform the software upgrade operation, thereby avoiding the first version.
  • the VNF software fails to be upgraded because the second instance is not successfully established, which is beneficial to improving the stability and reliability of the first VNF instance upgrade of the first version of the VNF software.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option, the deployment option including a resource option and a connection option, the VNFM obtaining for instantiating the second version of the VNF software as Deployment options for the second VNF instance, including:
  • the VNFM acquires a target software upgrade policy of the second VNF instance for upgrading to a second version of the VNF software in the VNF LCM request;
  • the VNFM determines a connection option corresponding to the resource option.
  • the target software upgrade policy and mapping relationship carried by the data can determine the deployment options (resource options and connection options) for the resources needed to establish the second instance, thereby reducing the information carried in the request message without the VNF LCM request carrying the deployment option.
  • the amount is beneficial to improve the reliability and efficiency of signaling interaction between VNFM and other network elements of the NFV system.
  • the VNFM obtains deployment options for instantiating the second version of the VNF software as a second VNF instance, including:
  • the VNFM acquires a deployment option in the VNF LCM request for instantiating a second version of the VNF software as a second VNF instance.
  • the method for initiating the software modification provided in the possible design, in addition to the technical effect of implementing the modified automatic operation of the VNF instance of the VNF software in the NFV system described above in the first aspect, through the VNF
  • the LCM request directly carries the deployment option for establishing the resources required by the second instance, does not need information such as the upgrade policy and the mapping relationship carried by the metadata, reduces the amount of metadata information, and does not need to determine the connection option according to the resource option, thereby simplifying the signaling.
  • the interaction process is beneficial to improve the efficiency of the first version of the VNF software modification.
  • the software modification type in the metadata is a VNF software update.
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type, including:
  • the VNFM acquires a file name and an access address of a target execution file for updating a second VNF instance of the second version of the VNF software in the metadata, and a mapping relationship between the execution file and the software image,
  • the instance identifier of the first VNF instance is consistent with the instance identifier of the second VNF instance;
  • the VNFM acquires the target execution file according to the access address and the file name
  • VNFM Determining, by the VNFM, a software image corresponding to the target execution file according to a mapping relationship between the execution file and the software image
  • VNFM Determining, by the VNFM, the virtual machine corresponding to the virtualized network function component VNFC instance to be updated in the first VNF instance according to the software image
  • the VNFM sends a software update request, the software update request is used to instruct the virtual machine to run the execution file to update the VNFC instance.
  • the VNFM is Obtaining a file name and an access address for updating a target execution file of the second VNF instance of the second version of the VNF software, and a mapping relationship between the execution file and the software image, acquiring a target execution file, and determining a target execution file Corresponding software image, and then determining the virtual machine of the VNFC instance to be updated according to the software image, and finally sending a software update request, instructing the virtual machine to run the execution file to update the VNFC instance, because the VNFC instance to be updated is not interrupted during the update process, so
  • the hot update of the first VNF instance is beneficial to improve the reliability and stability of the NFV system during the software update process.
  • the VNFM obtains metadata based on the VNF LCM request, including:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNF LCM request is generated by the NFVO upon receiving an update network service request sent by the operation support system OSS.
  • the method further includes:
  • the VNFM sends a VNF LCM response to the NFVO.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising The image identifier of the software image of the second VNFC software of the first VNFC software, the NFV system further includes a network element manager EM and a virtualized network function operation and maintenance device VNF O&M;
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type, including:
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the instance identifier of the first VNFC instance and the image identifier of the software image of the second VNFC software.
  • the VNFM sends a software upgrade request to the EM or the VNF O&M, where the software upgrade request is used to indicate that the EM or the VNF O&M upgrades the first VNFC instance to the second VNFC instance.
  • the VNFM determines an instance identifier of the first VNFC instance according to the instance identifier of the first VNF instance, including:
  • VNFM Determining, by the VNFM, an image identifier of the software image of the first VNFC software in the first version of the VNF software according to the instance identifier of the first VNF instance;
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the instance identifier of the first VNFC instance and the image identifier of the software image of the second VNFC software, including:
  • the VNFM applies for a resource according to an instance identifier of the first VNFC instance
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the image of the application and the image identifier of the software image of the second VNFC software.
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a software image of the VNFC software.
  • the image identifier of the VNF software to which the VNFC software belongs corresponding to the image identifier and the software image;
  • Determining, by the VNFM, the image identifier of the software image of the first VNFC software in the first version of the VNF software according to the instance identifier of the first VNF instance including:
  • the VNFM Determining, by the VNFM, the first version according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs. a mirror image of the software image of the first VNFC software in the VNF software;
  • the VNFM applies for the resource according to the instance identifier of the first VNFC instance, including:
  • the image of the software image identifies the application deployment option.
  • the VNFM is After the resources of the second VNFC instance are established, the EM or VNF O&M is notified to initiate the software upgrade, that is, the second VNFC instance is established, and the EM or VNF O&M is further notified to perform the software upgrade operation, thereby avoiding the first
  • the VNFC instance fails to be upgraded due to the failure of the second VNFC instance. This improves the stability and reliability of the upgrade of the first VNFC instance to be upgraded.
  • an embodiment of the present invention provides a method for publishing metadata, including:
  • Generating metadata including a version identification and a software modification type of the first version of the VNF software in the NFV system adapted for modification to the second version of the VNF software;
  • the NFV system since the released metadata includes a version identifier and a software modification type of the first version of the VNF software corresponding to the first VNF instance to be updated, the NFV system is After receiving the released metadata, the software that needs to be modified can be quickly identified, and the software modification operation is initiated according to the first VNF instance of the first version of the VNF software to be modified according to the software modification type in the metadata.
  • the initiation process of the software modification operation of the first VNF instance of the VNF software is sequentially executed by the VNFM according to the related information of the metadata, and the automatic operation of the VNF software modification in the NFV system is realized without user participation.
  • the software modification type is a VNF software upgrade
  • the metadata further includes a mapping relationship between the software upgrade policy and the resource option.
  • the method for publishing metadata can achieve the technical effects of the automatic operation of modifying the VNF software in the NFV system as described in the second aspect above, due to the software upgrade strategy and resources.
  • the mapping relationship between the options can determine a resource option for instantiating the second version of the VNF software as the second VNF instance.
  • the VNFM further determines the connection option corresponding to the resource option, thereby instantiating according to the resource option and the connection option.
  • the second version of the VNF software is a second VNF instance, so that the NFV system can perform software upgrade if the second instance is determined to be established, and the first version of the VNF software is prevented from being upgraded due to the failure of the second instance to be successfully established. It is beneficial to improve the stability and reliability of the NFV system during the software upgrade process.
  • the software modification type is a VNF software update
  • the metadata further includes a file name and an access address, an execution file, and a software image for updating a target execution file of the second version of the VNF software. The mapping relationship between them.
  • the method for distributing metadata provided in the possible design can be implemented in addition to the technical effects of implementing the automatic operation of the VNF software modification in the NFV system described in the second aspect above.
  • the file determines the software image, and then determines the virtualized network function component VNFC to be updated according to the software image.
  • the virtual machine of the instance finally sends a software update request to instruct the virtual machine to execute the file update VNFC instance. Since the VNFC instance is not interrupted, the hot update of the first VNF instance is implemented, which is beneficial to improving the reliability of the NFV system in the software update process. Sex and stability.
  • the metadata is integrated into a software package.
  • the software modification type is a virtualized network function component VNFC software upgrade
  • the first version VNF software includes a first VNFC software
  • the NFV system runs with a first VNFC instance
  • the first The VNFC example is obtained by instantiating the first VNFC software by the NFV system, the metadata further comprising a mirrored identifier of a software image of the second VNFC software for upgrading the first VNFC software.
  • the method for distributing metadata provided in the possible design can be implemented in addition to the technical effects of implementing the automatic operation of the VNF software modification in the NFV system described in the second aspect above.
  • To upgrade the image identifier of the software image of the second VNFC software of the first VNFC software which enables the VNFM to instantiate the second VNFC instance according to the image identifier of the software image of the second VNFC software, and instruct the EM or VNF O&M to upgrade the first VNFC
  • the example is the second VNFC instance, which prevents the first VNFC instance from being upgraded due to the failure of the second VNFC instance to be successfully established, which is beneficial to improving the stability and reliability of the upgrade of the first VNFC instance to be upgraded.
  • an embodiment of the present invention provides a virtualized network function manager VNFM, which has a function of implementing the behavior of the VNFM in the above method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the VNFM includes a processor configured to support the VNFM to perform the corresponding functions in the above methods. Further, the VNFM may also include a receiver and a transmitter for supporting communication between the VNFM and other network elements. Further, the VNFM can also include a memory for coupling with the processor that holds the necessary program instructions and data for the VNFM.
  • an embodiment of the present invention provides an apparatus for distributing metadata, the apparatus having a function of implementing a behavior of a device for distributing metadata in the design of the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the apparatus for publishing metadata includes a processor configured to support a device that publishes metadata to perform a corresponding function in the above method. Further, the apparatus for distributing metadata may further include a receiver and a transmitter for supporting communication between the device that issues the metadata and other systems such as the network function virtualization NFV system. Further, the apparatus for publishing metadata may further include a memory for coupling with the processor, which stores program instructions and data necessary for the device that issues the metadata.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores program code for execution by a computer device, where the program code specifically includes an execution instruction, where the execution instruction is used for Some or all of the steps described in any of the methods of the first aspect of the embodiments of the invention are performed.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores program code for execution by a computer device, where the program code specifically includes an execution instruction, where the execution instruction is used for Some or all of the steps described in any of the methods of the second aspect of the embodiments of the invention are performed.
  • the VNFM first determines the software modification operation by using the VNF LCM request in the NFV system, and secondly, obtains the metadata according to the VNF LCM request, again, Determining a first VNF instance of the first version of the VNF software to be modified according to the version identifier in the metadata and the instance identifier in the VNF LCM, and finally, the first version of the first version of the VNF software to be modified according to the software modification type in the metadata
  • the VNF instance initiates a software modification operation. It can be seen that the initiation process of the software modification operation of the first VNF instance of the first version of the VNF software is sequentially executed by the VNFM, and the automatic operation of the VNF software modification in the NFV system is implemented without user participation.
  • FIG. 1 is a system architecture diagram of a network function virtualization NFV system 100 according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for initiating software modification according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for publishing metadata according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for initiating a software upgrade according to an embodiment of the present invention
  • FIG. 4A is a schematic flowchart of another method for initiating a software upgrade according to an embodiment of the present invention.
  • 4B is a schematic flowchart of another method for initiating a software upgrade according to an embodiment of the present invention.
  • 4C is a schematic flowchart of another method for initiating a software upgrade according to an embodiment of the present invention.
  • 4D is a schematic flowchart of another method for initiating a software upgrade according to an embodiment of the present invention.
  • 4E is a schematic flowchart of another method for initiating a software upgrade according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for initiating a software update according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of another method for initiating a software update according to an embodiment of the present invention.
  • FIG. 6A is a functional block diagram of a VNFM according to an embodiment of the present invention.
  • FIG. 6B is a schematic structural diagram of a VNFM according to an embodiment of the present invention.
  • FIG. 7A is a functional block diagram of an apparatus for distributing metadata according to an embodiment of the present invention.
  • FIG. 7B is a schematic structural diagram of an apparatus for distributing metadata according to an embodiment of the present invention.
  • NFV Network Function Virtualization
  • FIG. 1 is a system architecture diagram of a Network Function Virtualization (NFV) system 100 according to an embodiment of the present invention.
  • the NFV system 100 includes a NFV Management and Orchestration (NFV MANO) 101, a NFV Infrastructure (NFVI) 130, and a virtual network function (Virtual Network Function, VNF) 108, Multiple Element Manager (EM) 122, (Network Service, VNF and Infrastructure Description) 126, Virtualized Network Function Operation and Maintenance (VNF Operation) And Maintenance, VNF O&M) 128, and Operation/Business Support System (Operation Support System/Business Support System, OSS/BSS) 124.
  • NFV MANO NFV Management and Orchestration
  • VNF Virtual Network Function
  • EM Multiple Element Manager
  • VNF Operation Virtualized Network Function Operation and Maintenance
  • VNF O&M Operation/Business Support System
  • OSS/BSS Operation/Business Support System
  • the NFV MANO 101 includes a Network Function Virtualization Orchestrator (NFVO) 102, one or more Virtual Network Function Managers (VNF Managers, VNFM) 104, and a Virtualized Infrastructure Manager (VIM) 106.
  • NFVO Network Function Virtualization Orchestrator
  • VNF Managers VNF Managers
  • VIP Virtualized Infrastructure Manager
  • NFVO102 is used to arrange NFVI130 resources across multiple VIM106s, as well as Lifecycle Management (LCM) of network services.
  • VIM106 is used to control and manage the computing, storage, and network resources of NFVI130. These resources are usually in the same carrier's infrastructure area, such as all resources of an NFVI130 Point of Presence (POP) across multiple NFVIs.
  • POP Point of Presence
  • -POP resources or resources within a subnet of NFVI-POP.
  • VNFM104 is used for VNF lifecycle management, including the following operations: instantiating VNF108 (creating a VNF through VNF online function), expanding and shrinking VNF108 (increasing or decreasing the capacity of VNF), updating or upgrading VNF108 (supporting VNF software or Configure various complex changes), terminate VNF108 (release VNF-related NFVI resources and release back to NFVI resource pool).
  • the NFVI 130 includes a hardware resource layer, a virtualization layer 131, and a virtual resource layer.
  • the hardware resource layer includes computing hardware 112, storage hardware 114, and network hardware 116.
  • the virtual resource layer includes virtual computing 110, virtual storage 118, and virtual network 120.
  • Computing hardware 112 may, for example, include a virtual machine of a Virtualized Network Function Component (VNFC) instance in a VNF instance in an NFV system.
  • VNFC Virtualized Network Function Component
  • OSS/BSS 124 have further in the European Telecommunications Standards Organization Regulations NFV 002V1.1.1 (Europete Telecommunications Standards Institute, ETSI, Group Specification, GS) description.
  • the NFVI 130 includes hardware resources, software resources, or a combination of both for completing the deployment of a virtualized environment.
  • the hardware resources and virtualization layer 131 are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for the VNF 108.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116.
  • Computing hardware 112 may be, for example, commercially available hardware and/or user-customized hardware for providing processing and computing resources.
  • Storage hardware 114 may be, for example, a storage capacity provided within the network or a storage capacity resident in storage hardware 114 itself (local storage located within the server). In one implementation, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • Network hardware 116 may be, for example, a switch, a router, and/or any other network device configured to have switching functionality.
  • Network hardware 116 can span multiple domains and can include multiple networks interconnected by one or more transport networks.
  • VNF software for NFV systems including two management and operation systems.
  • the embodiments of the present invention provide a method for initiating software modification, a method for releasing metadata, and an apparatus. The details will be described below.
  • FIG. 2 is a method for initiating software modification according to an embodiment of the present invention.
  • the method is applied to a network function virtualization NFV system, where the NFV system includes a virtualized network function manager VNFM and network function virtualization.
  • the arranger NFVO as shown, the method includes:
  • the NFVO sends a virtualized network function VNF lifecycle management LCM request sent by the NFVO to the VNFM, where the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be modified.
  • VNF LCM request illustrated in FIG. 2 is received from the NFVO, it can be understood that in some possible examples, the VNF LCM request may also be from other network element devices (eg, network element manager EM, virtual Network
  • network element manager EM virtual Network
  • the function is operated and maintained by the VNF O&M, etc., please refer to the embodiment of FIG. 4A to FIG. 4E and FIG. 5A.
  • the VNF LCM request is a request message for instructing the VNFM to perform lifecycle management on the VNF instance in the NFV system, where the lifecycle management for the VNF instance may include, for example, establishing a new VNF instance, increasing or decreasing the VNF instance.
  • the capacity, the termination VNF, and the newly added VNF software corresponding to the VNF instance indicates that the VNF software corresponding to the VNF instance is modified by carrying the type information of the software modification operation.
  • the VNF LCM request may further include request type description information of a type of the current VNF LCM request, such as a software modification operation.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata according to the VNF LCM request, where the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software.
  • Metadata is data describing data, mainly information describing data attributes, and is used to support functions such as indicating storage location, historical data, resource search, and file recording.
  • the metadata acquired by the VNFM specifically refers to metadata for software modification
  • the metadata for software modification refers to data provided to the software to modify related execution entities (such as VNFM).
  • the second version of the VNF software is a new version of the VNF software after the release of the first version of the VNF software.
  • the version of the second version of the VNF software is V2.0
  • the version of the first version of the VNF software is V1.0.
  • the release time of V1.0 is September 10, 2016, and the release time of V2.0 should be the date after September 10, 2016, such as October 10, 2016, and so on.
  • the software modification type may specifically include a VNF software upgrade and a VNF software update.
  • the VNF software upgrade refers to upgrading the VNF instance corresponding to the VNF software, specifically updating all the virtualized network function components VNFC instances of the VNF instance to implement the upgrade.
  • the VNF software update is to update one or more (but not all) of the VNFC instances in the VNF instance corresponding to the VNF software.
  • the specific implementation manner that the VNFM determines that the type of the VNF LCM request is a software modification operation may be:
  • the VNFM acquires request type description information in the VNF LCM request; the VNFM determines, according to the request type description information, that the type of the VNF LCM request is a software modification operation.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type.
  • the VNFM first determines the software modification operation by using the VNF LCM request in the NFV system, and secondly, obtains the metadata according to the VNF LCM request, and again, according to the version in the metadata.
  • the identifier and the instance identifier in the VNF LCM determine the first VNF instance of the first version of the VNF software to be modified, and finally, the software modification operation is initiated according to the first VNF instance of the first version of the VNF software to be modified according to the software modification type in the metadata. It can be seen that the initiation process of the software modification operation of the first VNF instance of the first version of the VNF software is sequentially executed by the VNFM, and the automatic operation of the VNF software modification in the NFV system is realized without user participation. Work.
  • the NFV system is running with the first VNF instance, the first VNF instance being obtained by the NFV system instantiating the first version of the VNF software; the VNFM is modified according to the software Type initiating a software modification operation on the first VNF instance of the first version of the VNF software, including:
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type.
  • the method for initiating the software modification is not only the technical effect of the automatic operation of the VNF software modification in the NFV system, but also the VNFM is initiated for the first version during the running of the first VNF instance.
  • the software modification operation of the first VNF instance of the VNF software that is, the software modification process initiates the operation, and the software modification operation of the first version of the VNF software may be initiated without interrupting the first VNF instance currently running by the NFV system. It is beneficial to maintain the stability and business continuity of the NFV system during the VNF software modification process.
  • the software modification type in the metadata is a VNF software upgrade.
  • the NFV system further includes a network element manager EM and a virtualized network function operation and maintenance unit VNF O&M, the VNFM according to the software modification type to the first VNF instance of the first version VNF software
  • the specific implementation method of initiating the software modification operation may be:
  • the VNFM acquires a deployment option for instantiating a second version of the VNF software as a second VNF instance;
  • the VNFM instantiates the second version of the VNF software as the second VNF instance according to the deployment option
  • VNFM Sending, by the VNFM, a software upgrade request to the EM or the VNF O&M, where the software upgrade request is used to indicate that the EM or the VNF O&M upgrades the first VNF instance of the first version of the VNF software to the The second VNF instance of the second version of the VNF software.
  • the VNFM notifies the EM or the resource after the second VNF instance is established.
  • the VNF O&M initiates a software upgrade, that is, if the second instance is already established, the EM or VNF O&M is further notified to perform the software upgrade operation, thereby preventing the first version of the VNF software from failing due to the failure of the second instance to be successfully established. It is beneficial to improve the stability and reliability of the first VNF instance upgrade of the first version of the VNF software.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option
  • the VNF LCM request further including a target software upgrade policy for upgrading to a second VNF instance of the second version of the VNF software
  • the deployment option includes a resource option and a connection option
  • the specific implementation manner in which the VNFM obtains a deployment option for instantiating the second version of the VNF software as the second VNF instance may be:
  • the VNFM acquires a target software upgrade policy of the second VNF instance for upgrading to a second version of the VNF software in the VNF LCM request;
  • the VNFM determines a connection option corresponding to the resource option.
  • the target software upgrade policy may be, for example, a software upgrade policy that is divided according to the area, or an upgrade policy that is divided according to the number of users, and may be flexibly set according to the upgrade service requirement.
  • the resource option refers to a computing resource, a storage resource, and a connection resource used to instantiate the VNF software;
  • the item refers to the configuration information of how to interconnect between the connection points of the resource options.
  • the connection point may specifically be an internal connection point or an external connection point.
  • the resource option includes computer A and computer B, and the connection point includes the connection point of computer A. 1 and the connection point 2 of the computer B, then the connection option corresponding to the computer A and the computer B may specifically be the connection configuration information between the connection point 1 and the connection point 2.
  • the VNFM may query the mapping relationship list manner (the mapping relationship between the software upgrade policy and the resource option in the metadata may be stored in the mapping relationship list) to determine the target. Resource options for the software upgrade strategy.
  • the method for initiating the software modification can not only determine the technical effect of the automatic operation of the VNF software modification in the NFV system, but also the target software upgrade strategy and mapping relationship carried by the metadata can be determined for establishing.
  • the metadata further includes a plurality of software upgrade policies, the plurality of software upgrade policies including the target software upgrade policy.
  • the specific implementation manner in which the VNFM obtains deployment options for instantiating the second version of the VNF software as the second VNF instance may be:
  • the VNFM acquires a deployment option in the VNF LCM request for instantiating a second version of the VNF software as a second VNF instance.
  • the method for initiating the software modification in addition to the technical effect of the automated operation of the VNF software modification in the NFV system, directly carries the resources required for establishing the second instance through the VNF LCM request.
  • the deployment option eliminates the need for information such as upgrade policies and mappings carried by the metadata, reduces the amount of metadata information, and eliminates the need to determine connection options based on resource options, which simplifies the signaling interaction process and helps improve the efficiency of the first version of the VNF software modification.
  • the software modification type in the metadata is a VNF software update.
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type, including:
  • the VNFM acquires a file name and an access address of a target execution file for updating a second VNF instance of the second version of the VNF software in the metadata, and a mapping relationship between the execution file and the software image,
  • the instance identifier of the first VNF instance is consistent with the instance identifier of the second VNF instance;
  • the VNFM acquires the target execution file according to the access address and the file name
  • VNFM Determining, by the VNFM, a software image corresponding to the target execution file according to a mapping relationship between the execution file and the software image
  • VNFM Determining, by the VNFM, the virtual machine corresponding to the virtualized network function component VNFC instance to be updated in the first VNF instance according to the software image
  • the VNFM sends a software update request, the software update request is used to instruct the virtual machine to run the execution file to update the VNFC instance.
  • the VNFC instance is any VNFC instance in the VNF instance, and the VNFC instance is running on a virtual machine.
  • the virtual machine can be implemented by running a software image corresponding to the VNFC instance.
  • a VNF instance corresponds to a VNF software
  • a VNF software includes at least one software image
  • a software image corresponds to a VNFC instance.
  • the specific implementation manner of the VNFM sending a software update request may be:
  • the VNFM sends a software update request to a VIM in the NFV system, and the VIM forwards the software update request to the determined virtual machine.
  • the VNFM is acquiring the second for updating the second version of the VNF software.
  • the VNFM After the file name and the access address of the target execution file of the VNF instance and the mapping relationship between the execution file and the software image, obtain the target execution file, determine the software image corresponding to the target execution file, and then determine the VNFC instance to be updated according to the software image.
  • the virtual machine finally sends a software update request, instructing the virtual machine to run the file update VNFC instance. Since the VNFC instance to be updated is not interrupted during the update process, the hot update of the first VNF instance is implemented, which is beneficial to improving the NFV system. Reliability and stability during the software update process.
  • the VNFM obtains metadata based on a VNF LCM request, including:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNF LCM request is generated by the NFVO upon receiving an update network service request sent by the operation support system OSS.
  • the method further includes:
  • the VNFM sends a VNF LCM response to the NFVO.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising The image identifier of the software image of the second VNFC software of the first VNFC software, the NFV system further includes a network element manager EM and a virtualized network function operation and maintenance device VNF O&M;
  • the VNFM initiates a software modification operation on the first VNF instance of the first version of the VNF software according to the software modification type, including:
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the instance identifier of the first VNFC instance and the image identifier of the software image of the second VNFC software.
  • the VNFM sends a software upgrade request to the EM or the VNF O&M, where the software upgrade request is used to indicate that the EM or the VNF O&M upgrades the first VNFC instance to the second VNFC instance.
  • the VNFM determines an instance identifier of the first VNFC instance according to the instance identifier of the first VNF instance, including:
  • Determining, by the VNFM, the first version of the first version of the VNF software according to the instance identifier of the first VNF instance A mirror image of the software image of a VNFC software
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the instance identifier of the first VNFC instance and the image identifier of the software image of the second VNFC software, including:
  • the VNFM applies for a resource according to an instance identifier of the first VNFC instance
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the image of the application and the image identifier of the software image of the second VNFC software.
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a software image of the VNFC software The image identifier of the VNF software to which the VNFC software belongs corresponding to the image identifier and the software image;
  • Determining, by the VNFM, the image identifier of the software image of the first VNFC software in the first version of the VNF software according to the instance identifier of the first VNF instance including:
  • the VNFM Determining, in the first version of the VNF software, the VNFM according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software belongs to the software image. a mirror image of the software image of the first VNFC software;
  • the VNFM applies for the resource according to the instance identifier of the first VNFC instance, including:
  • the image of the software image identifies the application deployment option.
  • the VNFM is After the resources of the second VNFC instance are established, the EM or VNF O&M is notified to initiate the software upgrade, that is, the second VNFC instance is established, and the EM or VNF O&M is further notified to perform the software upgrade operation, thereby avoiding the first
  • the VNFC instance fails to be upgraded due to the failure of the second VNFC instance. This improves the stability and reliability of the upgrade of the first VNFC instance to be upgraded.
  • FIG. 3 is a schematic flowchart of a method for publishing metadata according to an embodiment of the present invention. As shown in the figure, the method includes:
  • the first version of the VNF software is instantiated as a first VNF instance in the NFV system.
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software.
  • the NFV system receives the released element. After the data, the software that needs to be modified can be quickly identified, and the type to be modified according to the type of software modification in the metadata A version of the VNF software initiates a software modification operation. It can be seen that the initiation process of the software modification operation of the first version of the VNF software is sequentially executed by the VNFM according to the metadata related information, and the automatic operation of the VNF software modification in the NFV system is realized without user participation.
  • the software modification type is a VNF software upgrade
  • the metadata further includes a mapping relationship between the software upgrade policy and the resource option.
  • the method for publishing metadata provided in this example can be determined for the instance due to the technical effect of the automated operation of the VNF software modification in the NFV system, due to the mapping relationship between the software upgrade policy and the resource option.
  • the second version of the VNF software is a resource option of the second VNF instance.
  • the connection option corresponding to the resource option is further determined, thereby instantiating the second version of the VNF software as the second VNF instance according to the resource option and the connection option.
  • the NFV system can be upgraded in the case where the second instance is determined to be established, and the first version of the VNF software is prevented from being upgraded due to the failure of the second instance to be successfully established, which is beneficial to improving the NFV system during the software upgrade process. Stability and reliability.
  • the metadata may also include a plurality of software upgrade policies, and the plurality of software upgrade policies may include the target software upgrade policy.
  • the software modification type is a VNF software update
  • the metadata further including a file name and an access address for updating the target execution file of the second version of the VNF software, and between the execution file and the software image Mapping relationship.
  • the software image is a software image of the VNFC software of the VNF to be updated
  • the target execution file is an execution file corresponding to the software image of the VNFC software for updating the VNF to be updated
  • the mapping relationship includes Execute the file name and software image ID, and the corresponding relationship between the file name and the software image ID.
  • the method for distributing metadata in addition to the technical effect of the automated operation of the VNF software modification in the NFV system, is included in the metadata for updating to the second version of the VNF software.
  • the file name and access address of the target execution file, the mapping relationship between the execution file and the software image which enables the VNFM to obtain the target execution file according to the file name and the access address, determine the software image according to the target execution file, and then determine the software image according to the target image.
  • the virtual machine of the VNFC instance of the updated virtualized network function component and finally sends a software update request to instruct the virtual machine to run the file to update the VNFC instance. Since the VNFC instance is not interrupted, the hot update of the first VNF instance is implemented, which is beneficial to improve the NFV. The reliability and stability of the system during the software update process.
  • the metadata is integrated in a software package.
  • the version of the first version of the VNF software represents an applicable version of the same VNF software released before the release date of the second version of the VNF software.
  • the software modification type is a virtualized network function component VNFC software upgrade
  • the first version VNF software includes a first VNFC software
  • the NFV system runs with a first VNFC instance
  • the first The VNFC example is obtained by instantiating the first VNFC software by the NFV system, the metadata further comprising a mirrored identifier of a software image of the second VNFC software for upgrading the first VNFC software.
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a mirror image of a software image of the VNFC software
  • the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs the NFV system further includes a network element manager EM and a virtualized network function operation and maintenance device VNF O&M.
  • the method for distributing metadata provided in the possible design can be implemented in addition to the technical effects of implementing the automatic operation of the VNF software modification in the NFV system described in the second aspect above.
  • To upgrade the image identifier of the software image of the second VNFC software of the first VNFC software which enables the VNFM to instantiate the second VNFC instance according to the image identifier of the software image of the second VNFC software, and instruct the EM or VNF O&M to upgrade the first VNFC
  • the example is the second VNFC instance, which prevents the first VNFC instance from being upgraded due to the failure of the second VNFC instance to be successfully established, which is beneficial to improving the stability and reliability of the upgrade of the first VNFC instance to be upgraded.
  • the method for initiating the software modification is specifically a method for initiating a software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends an update network service request (for example, Update NS) to the network function virtualization orchestrator NFVO.
  • update network service request for example, Update NS
  • the update network service request may include, for example, an instance identifier of the network service instance, an update network service request type, an instance identifier of the second VNF instance, a target software upgrade policy, and a VNF instance of the first version of the VNF software to be modified.
  • the instance ID the ID of the software package containing the metadata, and so on.
  • the NFVO After receiving the update network service request, the NFVO sends a virtualized network function VNF lifecycle management LCM request to the VNFM, where the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be upgraded.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata according to the VNF LCM request, where the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNFM determines a first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM acquires a deployment option for instantiating the second version of the VNF software as the second VNF instance during the running of the first VNF instance.
  • the VNFM instantiates the second version of the VNF software as the second VNF instance according to the deployment option.
  • the VNFM sends a software upgrade request to the network element manager EM, where the software upgrade request is used to instruct the EM to upgrade the first VNF instance of the first version of the VNF software to be the second version of the VNF software.
  • the software upgrade request is used to instruct the EM to upgrade the first VNF instance of the first version of the VNF software to be the second version of the VNF software.
  • the software upgrade request may include, for example, the following information: an instance identifier of the first VNF instance, an instance identifier of the second VNF instance, a version identifier of the first version VNF software, a version identifier of the second version VNF software, the target Software upgrade strategy, etc.
  • the EM upgrades the first VNF instance of the first version of the VNF software to a second VNF instance of the second version of the VNF software, and sends a software upgrade response to the VNFM.
  • the software upgrade response may include, for example, a version identifier of the first version of the VNF software, a version identifier of the second version of the VNF software, an instance identifier of the upgraded first VNF instance, and an instance identifier of the upgraded second VNF instance.
  • the VNFM After receiving the software upgrade response, the VNFM sends a VNF LCM response to the NFVO.
  • the VNF LCM response may include, for example, an instance identifier of the upgraded first VNF instance and an instance identifier of the upgraded second VNF instance.
  • the NFVO After receiving the VNF LCM response, the NFVO sends an update network service response to the OSS.
  • the update network service response may include, for example, an instance identifier of the upgraded first VNF instance and an instance identifier of the upgraded second VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating the VNFC software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends an update network service request (for example: Update NS) to the network function virtualization orchestrator NFVO.
  • update network service request for example: Update NS
  • the update network service request may include, for example, a request type for updating a network service request (ie, VNF software modification), an instance identifier of a VNF instance of the first version of the VNF software to be modified, a target software upgrade policy, and metadata including The identifier of the package used for software modification.
  • VNF software is instantiated as a VNF instance, the VNF instance has a VNF instance identifier, and the VNF software has a version identifier.
  • the NFVO after receiving the update network service request, the NFVO sends a virtualized network function VNF lifecycle management LCM request to the VNFM.
  • the VNF LCM request includes an instance identifier of the VNF instance of the first version of the VNF software to be modified, a target software upgrade policy, an identifier of the software package including the metadata, and the like.
  • the target software upgrade policy is used to upgrade a software upgrade policy of the first VNFC software.
  • the VNF LCM request also contains an identification of a software package containing the metadata and VNF descriptor VNFD.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and the obtaining metadata in the software package according to the VNF LCM request.
  • the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising Mirror image of the software image of the second VNFC software of the first VNFC software
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a mirror image of a software image of the VNFC software The version identifier of the VNF software to which the VNFC software corresponding to the software image belongs;
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including the at least one The image identifier of the software image of the VNFC software of a VNF software and the VNFC software corresponding to the software image a version identifier of the VNF software to which the VNF software belongs, the metadata further includes at least one image identifier of the software image of the VNFC software of the second version of the VNF software used to upgrade the VNF software of the VNF software, and at least one software upgrade policy, At least one software upgrade strategy includes the target software upgrade strategy.
  • the specific implementation manner of the VNFM for obtaining metadata for upgrading the VNFC software in the software package according to the VNF LCM request is:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM obtains metadata for upgrading the VNFC software in the software package according to the identifier of the software package.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM before the step S4a04, the VNFM further performs the following operations:
  • the VNFM obtains, from the instance management database, a version identifier of the first version of the VNF software according to an instance identifier of the VNF instance of the first version of the VNF software;
  • the VNFM determines the first version of the VNF according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs.
  • the VNFM determines an instance identifier of the first VNFC instance according to the image identifier of the software image of the first VNFC software.
  • the VNFM determines resource options and connection options according to the instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy, and according to the resource option, the connection option, and the second The image of the software image of the VNFC software identifies the application deployment option.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option;
  • the VNFM is based on an instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy,
  • the specific implementation manner of determining the resource option and the connection option may be: the VNFM determines a resource option corresponding to the target software upgrade policy according to a mapping relationship between the software upgrade policy and the resource option in the metadata; The resource option, the instance identifier of the first VNFC instance, and the VNFD determine a connection option.
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the deployment option and the image identifier of the second VNFC software.
  • the VNFM sends a software upgrade request to the network element manager EM or the virtualized network function operation and maintenance device VNF O&M, where the software upgrade request is used to indicate that the EM or the VNF O&M upgrades the first VNFC instance to Two VNFC instances.
  • the software upgrade request includes the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the target software upgrade policy.
  • the EM or the VNF O&M migrates the service of the first VNFC instance to the second VNFC instance according to the target software upgrade policy, and sends a software upgrade response to the VNFM when the migration is completed.
  • the software upgrade response may include an instance identifier of the first VNF instance, an instance identifier of the first VNFC instance in the first VNF instance, and an instance identifier of the second VNFC instance.
  • VNFM After receiving the software upgrade response, the VNFM sends a VNF LCM response to the NFVO.
  • the VNF LCM response may include, for example, an instance identifier of the first VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating the VNFC software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends a virtualized network function VNF lifecycle management LCM request to the network element manager EM.
  • the VNF LCM request includes an instance identifier of the VNF instance of the first version of the VNF software to be modified, a target software upgrade policy, an identifier of the software package including the metadata, and the like.
  • the target software upgrade policy is used to upgrade a software upgrade policy of the first VNFC software.
  • the VNF LCM request also contains an identification of a software package containing the metadata and VNF descriptor VNFD.
  • the EM after receiving the VNF LCM request, the EM forwards the VNF LCM request to the VNFM.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata in the software package according to the VNF LCM request.
  • the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising Mirror image of the software image of the second VNFC software of the first VNFC software
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a mirror image of a software image of the VNFC software The version identifier of the VNF software to which the VNFC software corresponding to the software image belongs;
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including the at least one a mirror image of the software image of the VNFC software of the VNF software and a version identifier of the VNF software to which the VNFC software corresponding to the software image belongs, the metadata further including at least one second VNFC software for upgrading the VNF software A mirror image of the software image of the VNFC software of the version VNF software, at least one software upgrade policy, the at least one software upgrade policy including the target software upgrade policy.
  • the specific implementation manner of the VNFM for obtaining metadata for upgrading the VNFC software in the software package according to the VNF LCM request is:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM obtains metadata for upgrading the VNFC software in the software package according to the identifier of the software package.
  • the VNFM is based on the version identifier of the first version of the VNF software and the first version to be modified.
  • An instance identification of a VNF instance of the VNF software determines a first VNF instance of the first version of the VNF software.
  • the VNFM before the step S4b04, the VNFM further performs the following operations:
  • the VNFM obtains, from the instance management database, a version identifier of the first version of the VNF software according to an instance identifier of the VNF instance of the first version of the VNF software;
  • the VNFM determines the first version of the VNF according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs.
  • the VNFM determines an instance identifier of the first VNFC instance according to the image identifier of the software image of the first VNFC software;
  • the VNFM determines resource options and connection options according to the instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy, and according to the resource option, the connection option, and the second The image of the software image of the VNFC software identifies the application deployment option.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option;
  • the VNFM is based on an instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy,
  • the specific implementation manner of determining the resource option and the connection option may be: the VNFM determines a resource option corresponding to the target software upgrade policy according to a mapping relationship between the software upgrade policy and the resource option in the metadata; The resource option, the instance identifier of the first VNFC instance, and the VNFD determine a connection option.
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the deployment option and the image identifier of the second VNFC software.
  • the VNFM sends a software upgrade request to the EM, where the software upgrade request is used to indicate that the EM upgrades the first VNFC instance to a second VNFC instance.
  • the software upgrade request includes the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the target software upgrade policy.
  • the EM migrates the service of the first VNFC instance to the second VNFC instance according to the target software upgrade policy, and sends a software upgrade response to the VNFM when the migration is completed.
  • the software upgrade response may include an instance identifier of the first VNF instance, an instance identifier of the first VNFC instance in the first VNF instance, and an instance identifier of the second VNFC instance.
  • the VNFM after receiving the software upgrade response, the VNFM sends a VNF LCM response to the EM.
  • the VNF LCM response may include, for example, an instance identifier of the first VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating the VNFC software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends the virtualized network function VNF lifecycle management to the network element manager EM LCM request.
  • the VNF LCM request includes an instance identifier of the VNF instance of the first version of the VNF software to be modified, a target software upgrade policy, an identifier of the software package including the metadata, and the like.
  • the target software upgrade policy is used to upgrade a software upgrade policy of the first VNFC software.
  • the VNF LCM request also contains an identification of a software package containing the metadata and VNF descriptor VNFD.
  • the EM after receiving the VNF LCM request, the EM forwards the VNF LCM request to the VNFM.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata in the software package according to the VNF LCM request.
  • the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising Mirror image of the software image of the second VNFC software of the first VNFC software
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a mirror image of a software image of the VNFC software The version identifier of the VNF software to which the VNFC software corresponding to the software image belongs;
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including the at least one a mirror image of the software image of the VNFC software of the VNF software and a version identifier of the VNF software to which the VNFC software corresponding to the software image belongs, the metadata further including at least one second VNFC software for upgrading the VNF software A mirror image of the software image of the VNFC software of the version VNF software, at least one software upgrade policy, the at least one software upgrade policy including the target software upgrade policy.
  • the specific implementation manner of the VNFM for obtaining metadata for upgrading the VNFC software in the software package according to the VNF LCM request is:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM obtains metadata for upgrading the VNFC software in the software package according to the identifier of the software package.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM before the step S4c04, the VNFM further performs the following operations:
  • the VNFM obtains, from the instance management database, a version identifier of the first version of the VNF software according to an instance identifier of the VNF instance of the first version of the VNF software;
  • the VNFM determines the first according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs.
  • the VNFM determines an instance identifier of the first VNFC instance according to the image identifier of the software image of the first VNFC software;
  • the VNFM determines resource options and connection options according to the instance identifier of the first VNFC instance, the VNF descriptor VNFD, and the target software upgrade policy, and according to the resource option, the connection option, and the The image ID of the software image of the second VNFC software applies for deployment options.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option;
  • the VNFM is based on an instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy,
  • the specific implementation manner of determining the resource option and the connection option may be: the VNFM determines a resource option corresponding to the target software upgrade policy according to a mapping relationship between the software upgrade policy and the resource option in the metadata; The resource option, the instance identifier of the first VNFC instance, and the VNFD determine a connection option.
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the deployment option and the image identifier of the second VNFC software.
  • the VNFM sends a software upgrade request to the virtualized network function operation and maintenance device VNF O&M, where the software upgrade request is used to indicate that the VNF O&M upgrades the first VNFC instance to the second VNFC instance.
  • the software upgrade request includes the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the target software upgrade policy.
  • the VNF O&M migrates the service of the first VNFC instance to the second VNFC instance according to the target software upgrade policy, and sends a software upgrade response to the VNFM when the migration is completed.
  • the software upgrade response may include an instance identifier of the first VNF instance, an instance identifier of the first VNFC instance in the first VNF instance, and an instance identifier of the second VNFC instance.
  • VNFM After receiving the software upgrade response, the VNFM sends a VNF LCM response to the EM.
  • the VNF LCM response may include, for example, an instance identifier of the first VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating the VNFC software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends a virtualized network function VNF lifecycle management LCM request to the virtualized network function operation and maintenance device VNF O&M through the network element manager EM.
  • the VNF LCM request includes an instance identifier of the VNF instance of the first version of the VNF software to be modified, a target software upgrade policy, an identifier of the software package including the metadata, and the like.
  • the target software upgrade policy is used to upgrade a software upgrade policy of the first VNFC software.
  • the VNF LCM request also contains an identification of a software package containing the metadata and VNF descriptor VNFD.
  • the VNF O&M forwards the VNF LCM request to the VNFM.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata in the software package according to the VNF LCM request.
  • the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the software modification type in the metadata is a virtualized network function component VNFC software upgrade
  • the first version of the VNF software to be modified includes the first VNFC software.
  • the NFV system is running with a first VNFC instance, the first VNFC example being obtained by the NFV system instantiating the first VNFC software, the metadata further comprising Mirror image of the software image of the second VNFC software of the first VNFC software
  • the VNF LCM request includes an identification of a software package and a target software upgrade policy, the software package including the metadata and a VNF descriptor VNFD, the metadata further including a mirror image of a software image of the VNFC software The version identifier of the VNF software to which the VNFC software corresponding to the software image belongs;
  • the metadata includes a version identifier of the at least one VNF software, and the version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including the at least one a mirror image of the software image of the VNFC software of the VNF software and a version identifier of the VNF software to which the VNFC software corresponding to the software image belongs, the metadata further including at least one second VNFC software for upgrading the VNF software A mirror image of the software image of the VNFC software of the version VNF software, at least one software upgrade policy, the at least one software upgrade policy including the target software upgrade policy.
  • the specific implementation manner of the VNFM for obtaining metadata for upgrading the VNFC software in the software package according to the VNF LCM request is:
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM obtains metadata for upgrading the VNFC software in the software package according to the identifier of the software package.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM before the step S4d04, the VNFM further performs the following operations:
  • the VNFM obtains, from the instance management database, a version identifier of the first version of the VNF software according to an instance identifier of the VNF instance of the first version of the VNF software;
  • the VNFM determines the first version of the VNF according to the instance identifier of the first VNF instance, the image identifier of the software image of the VNFC software, and the version identifier of the VNF software to which the VNFC software corresponding to the software image belongs.
  • the VNFM determines an instance identifier of the first VNFC instance according to the image identifier of the software image of the first VNFC software.
  • the metadata further includes a mapping relationship between a software upgrade policy and a resource option;
  • the VNFM is based on an instance identifier of the first VNFC instance, the VNFD, and the target software upgrade policy,
  • the specific implementation manner of determining the resource option and the connection option may be: the VNFM determines a resource option corresponding to the target software upgrade policy according to a mapping relationship between the software upgrade policy and the resource option in the metadata; The resource option, the instance identifier of the first VNFC instance, and the VNFD determine a connection option.
  • the VNFM is based on an instance identifier of the first VNFC instance, the VNFD, and the target soft An upgrade policy, determining resource options and connection options, and requesting deployment options according to the resource options, the connection options, and a mirror image of the software image of the second VNFC software.
  • the VNFM instantiates the second VNFC software as the second VNFC instance according to the deployment option and the image identifier of the second VNFC software.
  • the VNFM sends a software upgrade request to the VNF O&M, where the software upgrade request is used to indicate that the VNF O&M upgrades the first VNFC instance to a second VNFC instance.
  • the software upgrade request includes the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the request type description information (the type of the VNF LCM request is a VNFC software upgrade operation), the instance identifier of the first VNF instance, and the first VNFC instance in the first VNF instance.
  • An instance identifier, an instance identifier of the second VNFC instance, and a target software upgrade policy is included in the target software upgrade policy.
  • the VNF O&M migrates the service of the first VNFC instance to the second VNFC instance according to the target software upgrade policy, and sends a software upgrade response to the VNFM when the migration is completed.
  • the software upgrade response may include an instance identifier of the first VNF instance, an instance identifier of the first VNFC instance in the first VNF instance, and an instance identifier of the second VNFC instance.
  • VNFM After receiving the software upgrade response, the VNFM sends a VNF LCM response to the VNF O&M.
  • the VNF LCM response may include, for example, an instance identifier of the first VNF instance.
  • VNF O&M after the VNF O&M receives the VNF LCM response, forward the VNF LCM response to the OSS through the EM.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating a software upgrade, and the method specifically includes the following steps:
  • the operation support system OSS sends a virtualized network function VNF lifecycle management LCM request to the network element manager EM.
  • the EM after receiving the update network service request, the EM sends the VNF LCM request to the VNFM, where the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be upgraded.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata according to the VNF LCM request, wherein the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM acquires a deployment option for instantiating the second version of the VNF software as the second VNF instance during the running of the first VNF instance.
  • the VNFM instantiates the second version of the VNF software as the second VNF instance according to the deployment option.
  • the VNFM sends a software upgrade request to the network element manager EM, where the software upgrade request is used to instruct the EM to upgrade the first VNF instance of the first version of the VNF software to be the second version of the VNF software. Two VNF instance.
  • the software upgrade request may include, for example, the following information: an instance identifier of the first VNF instance, an instance identifier of the second VNF instance, a version identifier of the first version VNF software, a version identifier of the second version VNF software, the target Software upgrade strategy, etc.
  • the EM upgrades the first VNF instance of the first version of the VNF software to the second VNF instance of the second version of the VNF software, and sends a software upgrade response to the VNFM.
  • the software upgrade response may include, for example, a version identifier of the first version of the VNF software, a version identifier of the second version of the VNF software, an instance identifier of the upgraded first VNF instance, and an instance identifier of the upgraded second VNF instance.
  • the VNFM after receiving the software upgrade response, the VNFM sends a VNF LCM response to the EM.
  • the VNF LCM response may include, for example, an instance identifier of the upgraded first VNF instance and an instance identifier of the upgraded second VNF instance.
  • the EM after receiving the VNF LCM response, the EM sends a VNF LCM response to the OSS.
  • the VNF LCM response may include, for example, an instance identifier of the upgraded first VNF instance and an instance identifier of the upgraded second VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating a software update, and the method specifically includes the following steps:
  • the operation support system OSS sends an update network service request (for example, Update NS) to the network function virtualization orchestrator NFVO.
  • update network service request for example, Update NS
  • the update network service request may include, for example, an instance identifier of the network service instance, an update network service request type, an instance identifier of a VNF instance of the first version of the VNF software to be modified, an identifier of a software package including the metadata, and the like.
  • the NFVO After receiving the update network service request, the NFVO sends a virtualized network function VNF lifecycle management LCM request to the VNFM, where the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be updated.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata according to the VNF LCM request, where the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNFM determines a first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM acquires, during the running of the first VNF instance, a file name and an access address of a target execution file in the metadata for updating to a second VNF instance of the second version of the VNF software, And mapping relationship between the execution file and the software image, where the instance identifier of the first VNF instance is consistent with the instance identifier of the second VNF instance.
  • the software image is a software image of the VNFC software of the VNF software to be updated, and the target execution file is used for The execution file corresponding to the software image of the VNFC software of the VNF to be updated is updated, and the mapping relationship includes a file name and a mirror image of the software image, and a correspondence between the execution file name and the software image identifier.
  • the metadata includes a version identifier of at least one VNF software, and a version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including VNFC software of the at least one VNF software.
  • the image identifier of the software image of the VNFC software includes the image identifier of the software image corresponding to the target execution file.
  • the VNFM acquires the target execution file according to the access address and the file name.
  • the VNFM determines a software image corresponding to the target execution file according to a mapping relationship between the execution file and the software image.
  • the representation of the software image corresponding to the target execution file is a software image identifier.
  • the VNFM determines, according to the software image, a virtual machine corresponding to the virtualized network function component VNFC instance to be updated in the first VNF instance.
  • the VNFM sends a software update request to the virtual machine corresponding to the VNFC instance to be updated, where the software update request is used to instruct the virtual machine to run the execution file to update the VNFC instance.
  • the software update request may include, for example, an instance identifier of the first VNF instance, an instance identifier of the VNFC instance, a version identifier of the first version VNF software, a version identifier of the second version VNF software, and the like.
  • the virtual machine sends a software update response to the VNFM.
  • the software upgrade response may include, for example, a version identifier of the first version of the VNF software, a version identifier of the second version of the VNF software, an instance identifier of the updated first VNF instance, and an instance identifier of the updated second VNF instance.
  • the VNFM sends a VNF LCM response to the NFVO.
  • the VNF LCM response may include, for example, an instance identifier of the updated first VNF instance and an instance identifier of the updated second VNF instance.
  • the NFVO After receiving the VNF LCM response, the NFVO sends an update network service response to the OSS.
  • the update network service response may include, for example, an instance identifier of the updated first VNF instance and an instance identifier of the updated second VNF instance.
  • the method for initiating the software modification provided by the embodiment of the present invention is specifically a method for initiating a software update, and the method specifically includes the following steps:
  • the operation support system OSS sends a virtualized network function VNF lifecycle management LCM request to the network element manager EM.
  • the EM After receiving the VNF LCM request, the EM forwards the VNF LCM request to the VNFM, where the VNF LCM request includes an instance identifier of a VNF instance of the first version of the VNF software to be updated.
  • the VNFM determines that the type of the VNF LCM request is a software modification operation and acquires metadata according to the VNF LCM request, wherein the metadata includes a version identifier and a software modification type of the first version of the VNF software.
  • the VNFM extracts an identifier of a software package in the VNF LCM request
  • the VNFM acquires metadata in the software package according to the identifier of the software package.
  • the VNFM determines the first VNF instance of the first version of the VNF software according to the version identifier of the first version of the VNF software and the instance identifier of the VNF instance of the first version of the VNF software to be modified.
  • the VNFM acquires, during the running of the first VNF instance, a file name and an access address of a target execution file in the metadata for updating to a second VNF instance of the second version of the VNF software, And mapping relationship between the execution file and the software image, where the instance identifier of the first VNF instance is consistent with the instance identifier of the second VNF instance.
  • the software image is a software image of the VNFC software of the VNF software to be updated
  • the target execution file is an execution file corresponding to the software image of the VNFC software of the VNF to be updated, where the mapping relationship includes an execution file name and The image ID of the software image and the correspondence between the file name and the software image ID.
  • the metadata includes a version identifier of at least one VNF software, and a version identifier of the at least one VNF software includes a version identifier of the first version of the VNF software, the metadata further including VNFC software of the at least one VNF software.
  • the image identifier of the software image of the VNFC software includes the image identifier of the software image corresponding to the target execution file.
  • the VNFM acquires the target execution file according to the access address and the file name
  • the VNFM determines, according to the mapping relationship between the execution file and the software image, a mirror image identifier of the software image corresponding to the target execution file.
  • the VNFM determines, according to the image identifier of the software image, a virtual machine corresponding to the virtualized network function component VNFC instance to be updated in the first VNF instance.
  • the VNFM sends a software update request to the virtual machine corresponding to the VNFC instance to be updated, where the software update request is used to instruct the virtual machine to run the execution file to update the VNFC instance.
  • the software update request may include, for example, an instance identifier of the first VNF instance, an instance identifier of the VNFC instance, a version identifier of the first version VNF software, a version identifier of the second version VNF software, and the like.
  • the virtual machine sends a software update response to the VNFM.
  • the software upgrade response may include, for example, a version identifier of the first version of the VNF software, a version identifier of the second version of the VNF software, an instance identifier of the updated first VNF instance, and an instance identifier of the updated second VNF instance.
  • the VNFM sends a VNF LCM response to the EM.
  • the VNF LCM response may include, for example, an instance identifier of the updated first VNF instance and an instance identifier of the updated second VNF instance.
  • the update network service response may include, for example, an instance identifier of the updated first VNF instance and an instance identifier of the updated second VNF instance.
  • the above description mainly introduces the solution of the embodiment of the present invention from the perspective of the process of issuing the metadata and the execution process of the VNFM in the NFV system.
  • the device for issuing metadata and the VNFM include hardware structures and/or software modules corresponding to the execution of the respective functions in order to implement the above functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. Professional technicians can make it for each specific application
  • the described functionality is implemented in different ways, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present invention may perform the division of functional units on the device for issuing metadata and the VNFM according to the foregoing method.
  • each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. in.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 6A shows a possible structural diagram of the VNFM involved in the above embodiment.
  • the VNFM 600 includes a processing unit 602 and a communication unit 603.
  • the processing unit 602 is configured to perform control management on the action of the VNFM.
  • the processing unit 602 is configured to support the VNFM to perform steps S202 to 204 in FIG. 2, steps S403 to S407 and S409 in FIG. 4, and step S4a03 in FIG. 4A to Steps S4b03 to S4b09, S4b11 in FIG. Steps S503 to S509, S511 in 5, steps S5a03 to S5a09, S5a11 in FIG.
  • the communication unit 603 is configured to support communication between the VNFM and devices that issue metadata or other network elements in the NFV system, such as communication with NFVO in the NFV system.
  • the VNFM may also include a storage unit 601 for storing program code and data of the VNFM.
  • the processing unit 602 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 603 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage unit 601 can be a memory.
  • the VNFM involved in the embodiment of the present invention may be the VNFM shown in FIG. 6B.
  • the VNFM 610 includes a processor 612, a communication interface 613, and a memory 611.
  • the VNFM 610 can also include a bus 614.
  • the communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus 614.
  • the bus 614 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • the bus 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6B, but it does not mean that there is only one bus or one type of bus.
  • the VNFM shown in FIG. 6A or FIG. 6B can also be understood as a device for the VNFM, which is not limited in the embodiment of the present invention.
  • FIG. 7A shows a possible structural diagram of an apparatus for distributing metadata involved in the above embodiment.
  • the apparatus 700 for publishing metadata includes a processing unit 702 and a communication unit 703.
  • the processing unit 702 is configured to control and manage the action of the device that issues the metadata, for example, the processing unit 702 is configured to support the device that issues the metadata. Steps S301 and S302 in Figure 3 and/or other processes for the techniques described herein are performed.
  • the communication unit 703 is used to support communication between the device that issues the metadata and the NFV system, such as communication with the NFVO in the NFV system.
  • the apparatus for publishing metadata may further include a storage unit 701 for storing program codes and data of the device that issues the metadata.
  • the processing unit 702 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 703 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage unit 701 can be a memory.
  • the apparatus for distributing metadata may be the apparatus for distributing metadata as shown in FIG. 7B.
  • the apparatus 710 for distributing metadata includes a processor 712, a communication interface 713, and a memory 711.
  • the device 710 that publishes the metadata may also include a bus 714.
  • the communication interface 713, the processor 712, and the memory 711 may be connected to each other through a bus 714.
  • the bus 714 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 714 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7B, but it does not mean that there is only one bus or one type of bus.
  • the apparatus for distributing metadata shown in FIG. 7A or FIG. 7B can also be understood as a device in a device for distributing metadata, which is not limited in the embodiment of the present invention.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium may store a program, and the program includes some or all of the steps of the software modification initiation method described in the foregoing method embodiments.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium can store a program, and the program includes some or all of the steps of the method for publishing metadata described in the foregoing method embodiments.
  • the disclosed apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit. It can be in electrical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a memory.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing memory includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种软件修改的发起方法、发布元数据的方法及装置（700, 710），包括：VNFM（104, 600, 610）接收NFVO（102）发送的虚拟化网络功能VNF（108）生命周期管理LCM请求，VNF（108） LCM请求包括待修改的第一版本VNF（108）软件的VNF（108）实例的实例标识；VNFM（104, 600, 610）确定VNF（108） LCM请求的类型为软件修改操作并根据VNF（108） LCM请求获取元数据，其中，元数据包括第一版本VNF（108）软件的版本标识和软件修改类型；VNFM（104, 600, 610）根据待修改的第一版本VNF（108）软件的VNF（108）实例的实例标识确定第一版本VNF（108）软件的第一VNF（108）实例；VNFM（104, 600, 610）根据软件修改类型对第一版本VNF（108）软件的第一VNF（108）实例发起软件修改操作。其有利于实现NFV***（100）中VNF（108）软件修改的自动化操作。

Description

软件修改的发起方法、发布元数据的方法及装置 技术领域
本申请涉及软件技术领域，尤其涉及一种软件修改的发起方法、发布元数据的方法及装置。
背景技术
对于传统***，网络功能(Network Function，NF)软件的更新和升级是由网络功能的管理和运维***(例如网元管理器(Element Manager,EM))控制和管理的。对于网络功能虚拟化(Network Function Virtualization，NFV)***，有2个管理和运维***需要接入到网络服务的运维和管理中，一个是传统的服务层管理***，例如操作支持***/业务支持***/网元管理器(Operation Support System/Business Support System/Element Manager,OSS/BSS/EM)；另一个是虚拟资源的管理和编排***，例如NFV***中的管理和编排***(Management and Orchestration，MANO)。
由于当前NFV标准没有定义用于虚拟化网络功能(Virtualization Network Function，VNF)软件的更新和升级的操作，且传统用于网络功能软件的更新或升级方法仅适用于包括单个管理和运维***的***，不能直接用于NFV***中VNF软件的更新或升级，因此，如何实现NFV***中VNF软件的更新和修改是本领域亟待解决的问题。
发明内容
本申请提供一种软件修改的发起方法、发布元数据的方法及装置，以期实现NFV***中VNF软件修改的自动化操作。
第一方面，本发明实施例提供一种软件修改的发起方法，应用于网络功能虚拟化NFV***，所述NFV***包括虚拟化网络功能管理器VNFM，包括：
所述VNFM接收虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待修改的第一版本VNF软件的VNF实例的实例标识；
所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型；
所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例；
所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
由上可见，本发明实施例提供的软件修改的发起方法，VNFM首先通过NFV***中的VNF LCM请求确定进行软件修改操作，其次，根据VNF LCM请求获取元数据，再次，根据元数据中的版本标识和VNF LCM中的实例标识确定待修改的第一版本VNF软件的第一VNF实例，最后，根据元数据中的软件修改类型对待修改的第一版本VNF软件的第一VNF实例发起软件修改操作，可见，第一版本VNF软件的第一VNF实例的软件修改操作的发起过程由VNFM顺序执行，无需用户参与，实现了NFV***中VNF软件修改的自动化操 作。
在一个可能的设计中，所述NFV***包括网络功能虚拟化编排器NFVO；所述VNFM接收虚拟化网络功能VNF生命周期管理LCM请求，包括：
所述VNFM接收所述NFVO发送的虚拟化网络功能VNF生命周期管理LCM请求。
在一个可能的设计中，所述NFV***运行有所述第一VNF实例，所述第一VNF实例是所述NFV***实例化所述第一版本VNF软件而得到的；所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM在所述第一VNF实例的运行过程中，根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，VNFM是在第一VNF实例的运行过程中发起的针对第一版本VNF软件的第一VNF实例的软件修改操作，也就是说，本软件修改发起操作的过程无需中断NFV***当前正在运行的第一VNF实例，即可发起对第一版本VNF软件的软件修改操作，有利于维持VNF软件修改过程中NFV***的稳定性和业务连续性。
在一个可能的设计中，所述元数据中的软件修改类型为VNF软件升级。
在一个可能的设计中，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项；
所述VNFM根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例；
所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，VNFM是在第二VNF实例的资源建立起来后，才通知EM或VNF O&M发起软件升级，即保证第二实例已经建立起来的情况下才会进一步通知EM或VNF O&M执行软件升级操作，从而避免第一版本VNF软件因第二实例未建立成功而升级失败的情况发生，有利于提升第一版本VNF软件的第一VNF实例升级的稳定性和可靠性。
在一个可能的设计中，所述元数据还包括软件升级策略和资源选项之间的映射关系，所述部署选项包括资源选项和连接选项，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项，包括：
所述VNFM获取所述VNF LCM请求中的用于升级为第二版本VNF软件的第二VNF实例的目标软件升级策略；
所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；
所述VNFM确定所述资源选项所对应的连接选项。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，由元数据携带的目标软件升级策略和映射关系能够确定用于建立第二实例所需要的资源的部署选项(资源选项和连接选项)，从而无需VNF LCM请求携带部署选项，减少了请求消息中携带的信息量，有利于提升VNFM与NFV***的其他网元之间信令交互的可靠性和效率。
在一个可能的设计中，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项，包括：
所述VNFM获取所述VNF LCM请求中用于实例化第二版本VNF软件为第二VNF实例的部署选项。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，通过VNF LCM请求直接携带用于建立第二实例所需要的资源的部署选项，无需元数据携带的升级策略、映射关系等信息，减少元数据信息量，且无需根据资源选项确定连接选项，简化了信令交互流程，有利于提升第一版本VNF软件修改的效率。
在一个可能的设计中，所述元数据中的软件修改类型为VNF软件更新。
在一个可能的设计中，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致；
所述VNFM根据所述存取地址和所述文件名获取所述目标执行文件；
所述VNFM根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像；
所述VNFM根据所述软件镜像确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机；
所述VNFM发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，VNFM在获取用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系后，获取目标执行文件，确定目标执行文件对应的软件镜像，再根据软件镜像确定待更新的VNFC实例的虚拟机，最后发送软件更新请求，指示虚拟机运行执行文件更新VNFC实例，由于待更新的VNFC实例在更新过程中未中断，因此实现了第一VNF实例的热更新，有利于提升NFV***在软件更新过程中的可靠性和稳定性。
在一个可能的设计中，所述VNFM根据VNF LCM请求获取元数据，包括：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
在一个可能的设计中，所述VNF LCM请求是所述NFVO在接收到操作支持***OSS发送的更新网络服务请求的情况下生成的。
在一个可能的设计中，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作之后，所述方法还包括：
所述VNFM向所述NFVO发送VNF LCM响应。
在一个可能的设计中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在一个可能的设计中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M；
所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM确定所述元数据中的软件修改类型为所述VNFC软件升级，根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识；
所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例；
所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一VNFC实例为所述第二VNFC实例。
在一个可能的设计中，所述VNFM根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识，包括：
所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例，包括：
所述VNFM根据所述第一VNFC实例的实例标识申请资源；
所述VNFM根据所述申请到的资源和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
在一个可能的设计中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识，包括：
所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本 VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
所述VNFM根据所述第一VNFC实例的实例标识申请资源，包括：
所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，VNFM是在第二VNFC实例的资源建立起来后，才通知EM或VNF O&M发起软件升级，即保证第二VNFC实例已经建立起来的情况下才会进一步通知EM或VNF O&M执行软件升级操作，从而避免第一VNFC实例因第二VNFC实例未建立成功而升级失败的情况发生，有利于提升待升级的第一VNFC实例升级的稳定性和可靠性。
第二方面，本发明实施例提供一种发布元数据的方法，包括：
生成元数据，所述元数据包括适用于修改为第二版本VNF软件的NFV***中的第一版本VNF软件的版本标识和软件修改类型；
发布所述元数据。
由上可见，本发明实施例提供的发布元数据的方法，由于发布的元数据中包括待更新的第一VNF实例对应的第一版本VNF软件的版本标识和软件修改类型，这使得NFV***在接收到该发布的元数据后，能够快速识别出需要修改的软件，并根据元数据中的软件修改类型对待修改的第一版本VNF软件的第一VNF实例发起软件修改操作，可见，第一版本VNF软件的第一VNF实例的软件修改操作的发起过程由VNFM根据元数据的相关信息顺序执行，无需用户参与，实现了NFV***中VNF软件修改的自动化操作。
在一个可能的设计中，所述软件修改类型为VNF软件升级，所述元数据还包括以及软件升级策略和资源选项之间的映射关系。
由上可见，本可能的设计中提供的发布元数据的方法，除了可以实现上述第二方面所描述的实现了NFV***中VNF软件修改的自动化操作的技术效果之外，由于软件升级策略和资源选项之间的映射关系能够确定用于实例化第二版本VNF软件为第二VNF实例的资源选项，VNFM确定资源选项后，进一步确定资源选项对应的连接选项，从而根据资源选项和连接选项实例化第二本版VNF软件为第二VNF实例，使得NFV***能够在第二实例确定建立起来的情况下进行软件升级，避免第一版本VNF软件因第二实例未建立成功而升级失败的情况发生，有利于提升NFV***在软件升级过程中的稳定性和可靠性。
在一个可能的设计中，所述软件修改类型为VNF软件更新，所述元数据还包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系。
由上可见，本可能的设计中提供的发布元数据的方法，除了可以实现上述第二方面所描述的实现了NFV***中VNF软件修改的自动化操作的技术效果之外，由于元数据中包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系，这使得VNFM能够根据文件名和存取地址获取目标执行文件，根据目标执行文件确定软件镜像，再根据软件镜像确定待更新的虚拟化网络功能组件VNFC 实例的虚拟机，最后发送软件更新请求，以指示虚拟机运行执行文件更新VNFC实例，由于VNFC实例不中断，实现了第一VNF实例的热更新，有利于提升NFV***在软件更新过程中的可靠性和稳定性。
在一个可能的设计中，所述元数据集成在软件包中。
在一个可能的设计中，所述软件修改类型为虚拟化网络功能组件VNFC软件升级，所述第一版本VNF软件包括第一VNFC软件，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识。
由上可见，本可能的设计中提供的发布元数据的方法，除了可以实现上述第二方面所描述的实现了NFV***中VNF软件修改的自动化操作的技术效果之外，由于元数据中包括用来升级第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，这使得VNFM能够根据第二VNFC软件的软件镜像的镜像标识实例化第二VNFC实例，并指示EM或VNF O&M升级第一VNFC实例为所述第二VNFC实例，避免第一VNFC实例因第二VNFC实例未建立成功而升级失败的情况发生，有利于提升待升级的第一VNFC实例升级的稳定性和可靠性。
第三方面，本发明实施例提供一种虚拟化网络功能管理器VNFM，该装置具有实现上述方法设计中VNFM的行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，VNFM包括处理器，所述处理器被配置为支持VNFM执行上述方法中相应的功能。进一步的，VNFM还可以包括接收器和发射器，所述接收器和发射器用于支持VNFM与其他网元之间的通信。进一步的，VNFM还可以包括存储器，所述存储器用于与处理器耦合，其保存VNFM必要的程序指令和数据。
第四方面，本发明实施例提供一种发布元数据的装置，该装置具有实现上述方法设计中发布元数据的装置的行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，发布元数据的装置包括处理器，所述处理器被配置为支持发布元数据的装置执行上述方法中相应的功能。进一步的，发布元数据的装置还可以包括接收器和发射器，所述接收器和发射器用于支持发布元数据的装置与其他***如网络功能虚拟化NFV***之间的通信。进一步的，发布元数据的装置还可以包括存储器，所述存储器用于与处理器耦合，其保存发布元数据的装置必要的程序指令和数据。
第五方面，本发明实施例提供一种计算机可读存储介质，其中，所述计算机可读存储介质存储有用于计算机设备执行的程序代码，该程序代码具体包括执行指令，所述执行指令用于执行本发明实施例第一方面任一方法中所描述的部分或全部步骤。
第六方面，本发明实施例提供一种计算机可读存储介质，其中，所述计算机可读存储介质存储有用于计算机设备执行的程序代码，该程序代码具体包括执行指令，所述执行指令用于执行本发明实施例第二方面任一方法中所描述的部分或全部步骤。
可以看出，本发明实施例提供的软件修改的发起方法，VNFM首先通过NFV***中的VNF LCM请求确定进行软件修改操作，其次，根据VNF LCM请求获取元数据，再次， 根据元数据中的版本标识和VNF LCM中的实例标识确定待修改的第一版本VNF软件的第一VNF实例，最后，根据元数据中的软件修改类型对待修改的第一版本VNF软件的第一VNF实例发起软件修改操作，可见，第一版本VNF软件的第一VNF实例的软件修改操作的发起过程由VNFM顺序执行，无需用户参与，实现了NFV***中VNF软件修改的自动化操作。
附图说明
下面将对背景技术或者实施例所需要使用的附图作简单地介绍。
图1是本发明实施例提供的一种网络功能虚拟化NFV***100的***架构图；
图2是本发明实施例提供的一种软件修改的发起方法的流程示意图；
图3是本发明实施例提供的一种发布元数据的方法的流程示意图；
图4是本发明实施例提供的一种软件升级的发起方法的流程示意图；
图4A是本发明实施例提供的另一种软件升级的发起方法的流程示意图；
图4B是本发明实施例提供的另一种软件升级的发起方法的流程示意图；
图4C是本发明实施例提供的另一种软件升级的发起方法的流程示意图；
图4D是本发明实施例提供的另一种软件升级的发起方法的流程示意图；
图4E是本发明实施例提供的另一种软件升级的发起方法的流程示意图；
图5是本发明实施例提供的一种软件更新的发起方法的流程示意图；
图5A本发明实施例提供的另一种软件更新的发起方法的流程示意图；
图6A是本发明实施例提供的一种VNFM的功能单元框图；
图6B是本发明实施例提供的一种VNFM的结构示意图；
图7A是本发明实施例提供的一种发布元数据的装置的功能单元框图；
图7B是本发明实施例提供的一种发布元数据的装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为更好的理解本发明技术方案，下面先对网络功能虚拟化(Network Function Virtualization，NFV)***的架构进行简要描述。
请参阅图1，图1是本发明实施例提供的一种网络功能虚拟化(Network Function Virtualization，NFV)***100的***架构图。其中，NFV***100包括网络功能虚拟化管理和编排***(NFV Management and Orchestration,NFV MANO)101、网络功能虚拟化基础设施层(NFV Infrastructure，NFVI)130、多个虚拟网络功能(Virtual Network Function,VNF)108、多个网元管理器(Element Manager,EM)122、(网络服务、VNF和基础设施描述)(Network Service,VNF and Infrastructure Description)126、虚拟化网络功能操作与维护器(VNF Operation and Maintenance，VNF O&M)128，以及操作/业务支持***(Operation  Support System/Business Support System,OSS/BSS)124。
NFV MANO101包括网络功能虚拟化编排器(NFV Orchestrator,NFVO)102、一个或多个虚拟化网络功能管理器(VNF Manager,VNFM)104和虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)106。
其中，NFVO102用于编排跨多个VIM106的NFVI130资源，以及网络服务的生命周期管理(Lifecycle Management，LCM)。VIM106用于控制和管理NFVI130的计算、存储以及网络资源，通常这些资源是在同一个运营商的基础设施领域，例如在一个NFVI130入网点(Point of Presence，POP)的所有资源，跨多个NFVI-POP的资源，或者一个NFVI-POP的子网内的资源。VNFM104用于VNF的生命周期管理，具体包括如下操作：实例化VNF108(通过VNF上线功能创建一个VNF)、VNF108扩容和缩容(增加或减少VNF的容量)、更新或升级VNF108(支持VNF软件或配置各种复杂的变更)、终止VNF108(释放VNF相关的NFVI资源并释放回NFVI资源池)。NFVI 130包括硬件资源层、虚拟化层(Virtualization Layer)131、虚拟资源层。硬件资源层包括计算硬件112、存储硬件114、网络硬件116，虚拟资源层包括虚拟计算110、虚拟存储118、虚拟网络120。计算硬件112例如可以包括NFV***中的VNF实例中的虚拟化网络功能组件(Virtualized Network Function Component，VNFC)实例的虚拟机。(网络服务描述符、VNF描述符和基础设施描述符)126和OSS/BSS 124在欧洲通信标准结构群体规NFV 002V1.1.1(Europe telecommunications Standards Institute，ETSI，Group Specification，GS)标准中有进一步的描述。NFVI 130包括硬件资源、软件资源或两者的组合，用于完成虚拟化环境的部署。硬件资源和虚拟化层131用于提供虚拟化的资源，例如作为虚拟机和其它形式的虚拟容器，用于VNF108。硬件资源包括计算硬件112、存储硬件114和网络硬件116。计算硬件112例如可以是市场上现成的硬件和/或用户定制的硬件，用来提供处理和计算资源。存储硬件114例如可以是网络内提供的存储容量或驻留在存储硬件114本身的存储容量(位于服务器内的本地存储器)。在一个实现方案中，计算硬件112和存储硬件114的资源可以被集中在一起。网络硬件116例如可以是交换机、路由器和/或配置成具有交换功能的任何其他网络设备。网络硬件116可以横跨多个域，并且可以包括多个由一个或一个以上传输网络互连的网络。
由于当前NFV标准没有定义用于上述NFV***中的VNF软件的更新和升级的操作，且传统用于网络功能软件的更新或升级方法仅适用于包括单个管理和运维***的***，不能直接用于包括两个管理和运维***的NFV***的VNF软件。针对上述问题，本发明实施例提供了一种软件修改的发起方法、发布元数据的方法及装置。下面进行详细说明。
请参阅图2，图2是本发明实施例提供的一种软件修改的发起方法，该方法应用于网络功能虚拟化NFV***，所述NFV***包括虚拟化网络功能管理器VNFM和网络功能虚拟化编排器NFVO，如图所示，所述方法包括：
S201，所述NFVO向所述VNFM发送的虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待修改的第一版本VNF软件的VNF实例的实例标识。
虽然图2示意的VNF LCM请求是从NFVO接收到的，但可以理解的是，在一些可能的示例中，所述VNF LCM请求也可以从其他网元设备(例如：网元管理器EM、虚拟化网 络功能操作与维护器VNF O&M等)接收，具体请参考图4A至图4E以及图5A的实施例。
其中，所述VNF LCM请求是用于指示VNFM针对NFV***中VNF实例进行生命周期管理的请求消息，其中，针对VNF实例进行生命周期管理例如可以包括建立一个新的VNF实例、增加或减少VNF实例的容量、终止VNF以及新增的修改VNF实例对应的VNF软件，具体的，VNF LCM请求通过携带软件修改操作的类型信息来指示针对VNF实例对应的VNF软件进行修改。
其中，所述VNF LCM请求还可以包括当前VNF LCM请求的类型为软件修改操作的请求类型描述信息等。
S202，所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型。
其中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识。
其中，元数据(Metadata)为描述数据的数据，主要是描述数据属性的信息，用来支持如指示存储位置、历史数据、资源查找、文件记录等功能。VNFM获取的元数据具体是指用于软件修改的元数据，该用于软件修改的元数据是指提供给软件修改有关执行实体(如VNFM)的数据。
其中，所述第二版本VNF软件为发布时间在第一版本VNF软件之后的新版本VNF软件，如第二版本VNF软件的版本为V2.0，第一版本VNF软件的版本为V1.0，V1.0的发布时间为2016年9月10号，则V2.0的发布时间应该是2016年9月10号往后的日期，如2016年10月10号，等。
其中，所述软件修改类型具体可以包括VNF软件升级和VNF软件更新。VNF软件升级是指对VNF软件所对应的VNF实例进行升级，具体是针对该VNF实例的所有虚拟化网络功能组件VNFC实例进行更新以实现升级。VNF软件更新则是指针对VNF软件所对应的VNF实例中的一个或多个(但不是全部)VNFC实例进行更新。
所述VNFM确定所述VNF LCM请求的类型为软件修改操作的具体实现方式可以是：
所述VNFM获取所述VNF LCM请求中的请求类型描述信息；所述VNFM根据所述请求类型描述信息确定所述VNF LCM请求的类型为软件修改操作。
S203，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例。
S204，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
可以看出，本发明实施例提供的软件修改的发起方法，VNFM首先通过NFV***中的VNF LCM请求确定进行软件修改操作，其次，根据VNF LCM请求获取元数据，再次，根据元数据中的版本标识和VNF LCM中的实例标识确定待修改的第一版本VNF软件的第一VNF实例，最后，根据元数据中的软件修改类型对待修改的第一版本VNF软件的第一VNF实例发起软件修改操作，可见，第一版本VNF软件的第一VNF实例的软件修改操作的发起过程由VNFM顺序执行，无需用户参与，实现了NFV***中VNF软件修改的自动化操 作。
在一个示例中，所述NFV***运行有所述第一VNF实例，所述第一VNF实例是所述NFV***实例化所述第一版本VNF软件而得到的；所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM在所述第一VNF实例的运行过程中，根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
由上可见，本示例中提供的软件修改的发起方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，VNFM是在第一VNF实例的运行过程中发起的针对第一版本VNF软件的第一VNF实例的软件修改操作，也就是说，本软件修改发起操作的过程无需中断NFV***当前正在运行的第一VNF实例，即可发起对第一版本VNF软件的软件修改操作，有利于维持VNF软件修改过程中NFV***的稳定性和业务连续性。
在一个示例中，所述元数据中的软件修改类型为VNF软件升级。
在这个示例中，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作的具体实现方式可以是：
所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项；
所述VNFM根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例；
所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例。
由上可见，本示例中提供的软件修改的发起方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，VNFM是在第二VNF实例的资源建立起来后，才通知EM或VNF O&M发起软件升级，即保证第二实例已经建立起来的情况下才会进一步通知EM或VNF O&M执行软件升级操作，从而避免第一版本VNF软件因第二实例未建立成功而升级失败的情况发生，有利于提升第一版本VNF软件的第一VNF实例升级的稳定性和可靠性。
在这个示例中，所述元数据还包括软件升级策略和资源选项之间的映射关系，所述VNF LCM请求还包括用于升级为第二版本VNF软件的第二VNF实例的目标软件升级策略，所述部署选项包括资源选项和连接选项，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项的具体实现方式可以是：
所述VNFM获取所述VNF LCM请求中的用于升级为第二版本VNF软件的第二VNF实例的目标软件升级策略；
所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；
所述VNFM确定所述资源选项所对应的连接选项。
其中，所述目标软件升级策略例如可以是按区域进行划分的软件升级策略，也可以是按用户数量比例进行划分的升级策略，具体可以根据升级业务需求进行灵活设置。
其中，资源选项是指用于实例化VNF软件的计算资源、存储资源和连接资源；连接选 项是指资源选项的连接点之间如何进行互连的配置信息，该连接点具体可以是内部连接点或外部连接点，如资源选项包括计算机A和计算机B，连接点包括计算机A的连接点1和计算机B的连接点2，那么计算机A和计算机B对应的连接选项具体可以是连接点1和连接点2之间的连接配置信息。
具体实现中，所述VNFM在获取目标软件升级策略之后，可以通过查询映射关系列表的方式(元数据中的软件升级策略和资源选项之间的映射关系可以存储在映射关系列表中)，确定目标软件升级策略所对应的资源选项。
由上可见，本示例中提供的软件修改的发起方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，由元数据携带的目标软件升级策略和映射关系能够确定用于建立第二实例所需要的资源的部署选项(资源选项和连接选项)，从而无需VNF LCM请求携带部署选项，减少了请求消息中携带的信息量，有利于提升VNFM与NFV***的其他网元之间信令交互的可靠性和效率。
在一个示例中，所述元数据还包括多种软件升级策略，所述多种软件升级策略包括所述目标软件升级策略。
在这个示例中，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项的具体实现方式可以是：
所述VNFM获取所述VNF LCM请求中用于实例化第二版本VNF软件为第二VNF实例的部署选项。
由上可见，本示例中提供的软件修改的发起方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，通过VNF LCM请求直接携带用于建立第二实例所需要的资源的部署选项，无需元数据携带的升级策略、映射关系等信息，减少元数据信息量，且无需根据资源选项确定连接选项，简化了信令交互流程，有利于提升第一版本VNF软件修改的效率。
在一个示例中，所述元数据中的软件修改类型为VNF软件更新。
在这个示例中，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致；
所述VNFM根据所述存取地址和所述文件名获取所述目标执行文件；
所述VNFM根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像；
所述VNFM根据所述软件镜像确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机；
所述VNFM发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
其中，VNFC实例是指VNF实例中的任意一个VNFC实例，且VNFC实例运行在一个虚拟机上，该虚拟机具体可以通过运行该VNFC实例对应的软件镜像来实现，也就是说， 一个VNF实例对应一个VNF软件，一个VNF软件包括至少一个软件镜像，一个软件镜像对应一个VNFC实例。
具体实现中，所述VNFM发送软件更新请求的具体实现方式可以是：
所述VNFM向所述确定的虚拟机发送软件更新请求；或者，
所述VNFM向所述NFV***中的VIM发送软件更新请求，并由所述VIM向所述确定的虚拟机转发所述软件更新请求。
由上可见，本示例中提供的软件修改的发起方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，VNFM在获取用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系后，获取目标执行文件，确定目标执行文件对应的软件镜像，再根据软件镜像确定待更新的VNFC实例的虚拟机，最后发送软件更新请求，指示虚拟机运行执行文件更新VNFC实例，由于待更新的VNFC实例在更新过程中未中断，因此实现了第一VNF实例的热更新，有利于提升NFV***在软件更新过程中的可靠性和稳定性。
在一个示例中，所述VNFM根据VNF LCM请求获取元数据，包括：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
在这个示例中，所述VNF LCM请求是所述NFVO在接收到操作支持***OSS发送的更新网络服务请求的情况下生成的。
在一个示例中，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作之后，所述方法还包括：
所述VNFM向所述NFVO发送VNF LCM响应。
在一个可能的示例中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在本可能的示例中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M；
所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
所述VNFM确定所述元数据中的软件修改类型为所述VNFC软件升级，根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识；
所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例；
所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一VNFC实例为所述第二VNFC实例。
在本可能的示例中，所述VNFM根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识，包括：
所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第 一VNFC软件的软件镜像的镜像标识；
所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例，包括：
所述VNFM根据所述第一VNFC实例的实例标识申请资源；
所述VNFM根据所述申请到的资源和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
在本可能的示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识，包括：
所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
所述VNFM根据所述第一VNFC实例的实例标识申请资源，包括：
所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
由上可见，本可能的设计中提供的软件修改的发起方法，除了可以实现上述第一方面所描述的实现了NFV***中VNF软件的VNF实例的修改的自动化操作的技术效果之外，VNFM是在第二VNFC实例的资源建立起来后，才通知EM或VNF O&M发起软件升级，即保证第二VNFC实例已经建立起来的情况下才会进一步通知EM或VNF O&M执行软件升级操作，从而避免第一VNFC实例因第二VNFC实例未建立成功而升级失败的情况发生，有利于提升待升级的第一VNFC实例升级的稳定性和可靠性。
与图2所示的软件修改的发起方法一致的，请参阅图3，图3是本发明实施例提供的一种发布元数据的方法的流程示意图，如图所示，所述方法包括：
S301，生成元数据，所述元数据包括适用于修改为第二版本VNF软件的NFV***中的第一版本VNF软件的版本标识和软件修改类型。
其中，所述第一版本VNF软件在NFV***中被实例化为第一VNF实例。
其中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识。
S302，发布所述元数据。
可以看出，本发明实施例提供的发布元数据的方法，由于发布的元数据中包括待更新的第一版本VNF软件的版本标识和软件修改类型，这使得NFV***在接收到该发布的元数据后，能够快速识别出需要修改的软件，并根据元数据中的软件修改类型对待修改的第 一版本VNF软件发起软件修改操作，可见，第一版本VNF软件的软件修改操作的发起过程由VNFM根据元数据的相关信息顺序执行，无需用户参与，实现了NFV***中VNF软件修改的自动化操作。
在一个示例中，所述软件修改类型为VNF软件升级，所述元数据还包括软件升级策略和资源选项之间的映射关系。
由上可见，本示例中提供的发布元数据的方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，由于软件升级策略和资源选项之间的映射关系能够确定用于实例化第二版本VNF软件为第二VNF实例的资源选项，VNFM确定资源选项后，进一步确定资源选项对应的连接选项，从而根据资源选项和连接选项实例化第二本版VNF软件为第二VNF实例，使得NFV***能够在第二实例确定建立起来的情况下进行软件升级，避免第一版本VNF软件因第二实例未建立成功而升级失败的情况发生，有利于提升NFV***在软件升级过程中的稳定性和可靠性。
在一个示例中，所述元数据还可以包括多种软件升级策略，所述多种软件升级策略可以包括所述目标软件升级策略。
在一个示例中，所述软件修改类型为VNF软件更新，所述元数据还包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系。
其中，所述软件镜像是待更新的VNF的VNFC软件的软件镜像，所述目标执行文件是用于更新所述待更新的VNF的VNFC软件的软件镜像所对应的执行文件，所述映射关系包括执行文件名和软件镜像标识，以及执行文件名和软件镜像标识对应关系。
由上可见，本示例中提供的发布元数据的方法，除了可以实现NFV***中VNF软件修改的自动化操作的技术效果之外，由于元数据中包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系，这使得VNFM能够根据文件名和存取地址获取目标执行文件，根据目标执行文件确定软件镜像，再根据软件镜像确定待更新的虚拟化网络功能组件VNFC实例的虚拟机，最后发送软件更新请求，以指示虚拟机运行执行文件更新VNFC实例，由于VNFC实例不中断，实现了第一VNF实例的热更新，有利于提升NFV***在软件更新过程中的可靠性和稳定性。
在一个示例中，所述元数据集成在软件包中。
其中，所述第一版本VNF软件的版本表示在第二版本VNF软件发布日期前发布的同一种VNF软件的适用版本。
在一个可能的示例中，所述软件修改类型为虚拟化网络功能组件VNFC软件升级，所述第一版本VNF软件包括第一VNFC软件，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识。
在本示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M。
由上可见，本可能的设计中提供的发布元数据的方法，除了可以实现上述第二方面所描述的实现了NFV***中VNF软件修改的自动化操作的技术效果之外，由于元数据中包括用来升级第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，这使得VNFM能够根据第二VNFC软件的软件镜像的镜像标识实例化第二VNFC实例，并指示EM或VNF O&M升级第一VNFC实例为所述第二VNFC实例，避免第一VNFC实例因第二VNFC实例未建立成功而升级失败的情况发生，有利于提升待升级的第一VNFC实例升级的稳定性和可靠性。
下面结合具体应用场景对本发明实施例提供的发布元数据的方法做进一步说明。
请参阅图4，假设元数据中的软件修改类型为VNF软件升级，则本发明实施例提供的软件修改的发起方法具体为软件升级的发起方法，该方法具体包括以下步骤：
S401，操作支持***OSS向网络功能虚拟化编排器NFVO发送更新网络服务请求(例如：Update NS)。
其中，所述更新网络服务请求例如可以包括：网络服务实例的实例标识、更新网络服务请求类型、第二VNF实例的实例标识、目标软件升级策略、待修改的第一版本VNF软件的VNF实例的实例标识、包含元数据的软件包的标识等。
S402，所述NFVO接收所述更新网络服务请求后，向VNFM发送虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待升级的第一版本VNF软件的VNF实例的实例标识。
S403，所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型。
其中，所述VNFM根据所述VNF LCM请求获取元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
S404，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例。
S405，所述VNFM在所述第一VNF实例的运行过程中，获取用于实例化第二版本VNF软件为第二VNF实例的部署选项。
S406，所述VNFM根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例。
S407，所述VNFM向网元管理器EM发送软件升级请求，所述软件升级请求用于指示所述EM升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例。
其中，所述软件升级请求例如可以包括如下信息：第一VNF实例的实例标识、第二VNF实例的实例标识、第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、所述目标软件升级策略等。
S408，所述EM升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例，向所述VNFM发送软件升级响应。
其中，所述软件升级响应例如可以包括第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、被升级的第一VNF实例的实例标识以及升级后的第二VNF实例的实例标识。
S409，所述VNFM接收所述软件升级响应后，向所述NFVO发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括被升级的第一VNF实例的实例标识、升级后的第二VNF实例的实例标识。
S410，所述NFVO接收所述VNF LCM响应之后，向所述OSS发送更新网络服务响应。
其中，所述更新网络服务响应例如可以包括被升级的第一VNF实例的实例标识、升级后的第二VNF实例的实例标识。
请参阅图4A，假设元数据中的软件修改类型为VNFC软件升级，则本发明实施例提供的软件修改的发起方法具体为VNFC软件升级的发起方法，该方法具体包括以下步骤：
S4a01，操作支持***OSS向网络功能虚拟化编排器NFVO发送更新网络服务请求(例如：Update NS)。
其中，所述更新网络服务请求例如可以包括：更新网络服务请求的请求类型(即VNF软件修改)、待修改的第一版本VNF软件的VNF实例的实例标识、目标软件升级策略、包含元数据的软件包的标识，该软件包用于软件修改。VNF软件实例化后的表现形式为VNF实例，VNF实例有VNF实例标识，VNF软件有版本标识。
S4a02，所述NFVO接收所述更新网络服务请求后，向VNFM发送虚拟化网络功能VNF生命周期管理LCM请求。
其中，所述VNF LCM请求中包括待修改的第一版本VNF软件的VNF实例的实例标识、目标软件升级策略、包含元数据的软件包的标识等。其中，所述目标软件升级策略用于是用于升级第一VNFC软件的软件升级策略。
在本示例中，所述VNF LCM请求还包含软件包的标识，所述软件包包含所述元数据和VNF描述符VNFD。
S4a03，所述VNFM确定VNF LCM请求的类型为软件修改操作并所述根据所述VNF LCM请求获取软件包中的元数据。
其中，所述元数据包括第一版本VNF软件的版本标识和软件修改类型。
在本示例中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在本示例中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识
在本示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
在一个可能的示例中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件 所属的VNF软件的版本标识，所述元数据还包括至少一个用来升级所述VNF软件的VNFC软件的第二版本VNF软件的VNFC软件的软件镜像的镜像标识、至少一个软件升级策略，所述至少一个软件升级策略包括所述目标软件升级策略。
在一个示例中，所述VNFM根据所述VNF LCM请求获取软件包中用于升级VNFC软件的元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中用于升级VNFC软件的元数据。
S4a04，所述VNFM根据第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识，确定所述第一版本VNF软件的第一VNF实例。
在一个实施例中，本步骤S4a04之前，所述VNFM还执行以下操作：
所述VNFM在根据第一版本VNF软件的VNF实例的实例标识从实例管理数据库中获取到所述第一版本VNF软件的版本标识；
所述VNFM判断出所述元数据中的至少一个适用于通过所述软件包进行升级的VNF软件的版本标识包括所述第一版本VNF软件的版本标识，确定第一版本VNF软件为适用于通过所述软件包进行升级的VNF软件。
S4a05，所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识。
S4a06，所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识。
S4a07，所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
在一个可能的示例中，所述元数据还包括软件升级策略和资源选项之间的映射关系；所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项的具体实现方式可以是：所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；根据所述资源选项、所述第一VNFC实例的实例标识和所述VNFD确定连接选项。
S4a08，所述VNFM根据所述申请到的部署选项和所述第二VNFC软件的软将镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
S4a09，所述VNFM向网元管理器EM或虚拟化网络功能操作与维护器VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级第一VNFC实例为第二VNFC实例。
其中，所述软件升级请求包括所述请求类型描述信息(VNF LCM请求的类型为VNFC软件升级操作)、所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识以及目标软件升级策略。
S4a10，所述EM或所述VNF O&M根据所述目标软件升级策略，迁移所述第一VNFC实例的业务到所述第二VNFC实例中，当迁移完成时，向所述VNFM发送软件升级响应。
其中，所述软件升级响应可以包括所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识。
S4a11，所述VNFM接收所述软件升级响应后，向所述NFVO发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括所述第一VNF实例的实例标识。
S4a12，所述NFVO接收所述VNF LCM响应之后，向所述OSS发送更新网络服务响应。
请参阅图4B，假设元数据中的软件修改类型为VNFC软件升级，则本发明实施例提供的软件修改的发起方法具体为VNFC软件升级的发起方法，该方法具体包括以下步骤：
S4b01，操作支持***OSS向网元管理器EM发送虚拟化网络功能VNF生命周期管理LCM请求。
其中，所述VNF LCM请求中包括待修改的第一版本VNF软件的VNF实例的实例标识、目标软件升级策略、包含元数据的软件包的标识等。其中，所述目标软件升级策略用于是用于升级第一VNFC软件的软件升级策略。
在本示例中，所述VNF LCM请求还包含软件包的标识，所述软件包包含所述元数据和VNF描述符VNFD。
S4b02，所述EM接收所述VNF LCM请求后，向VNFM转发所述VNF LCM请求。
S4b03，所述VNFM确定VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取软件包中的元数据。
其中，所述元数据包括第一版本VNF软件的版本标识和软件修改类型。
在本示例中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在本示例中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识
在本示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
在一个可能的示例中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述元数据还包括至少一个用来升级所述VNF软件的VNFC软件的第二版本VNF软件的VNFC软件的软件镜像的镜像标识、至少一个软件升级策略，所述至少一个软件升级策略包括所述目标软件升级策略。
在一个示例中，所述VNFM根据所述VNF LCM请求获取软件包中用于升级VNFC软件的元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中用于升级VNFC软件的元数据。
S4b04，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本 VNF软件的VNF实例的实例标识，确定所述第一版本VNF软件的第一VNF实例。
在一个实施例中，本步骤S4b04之前，所述VNFM还执行以下操作：
所述VNFM在根据第一版本VNF软件的VNF实例的实例标识从实例管理数据库中获取到所述第一版本VNF软件的版本标识；
所述VNFM判断出所述元数据中的至少一个适用于通过所述软件包进行升级的VNF软件的版本标识包括所述第一版本VNF软件的版本标识，确定第一版本VNF软件为适用于通过所述软件包进行升级的VNF软件。
S4b05，所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识。
S4b06，所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
S4b07，所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
在一个可能的示例中，所述元数据还包括软件升级策略和资源选项之间的映射关系；所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项的具体实现方式可以是：所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；根据所述资源选项、所述第一VNFC实例的实例标识和所述VNFD确定连接选项。
S4b08，所述VNFM根据所述申请到的部署选项和所述第二VNFC软件的软将镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
S4b09，所述VNFM向所述EM发送软件升级请求，所述软件升级请求用于指示所述EM升级第一VNFC实例为第二VNFC实例。
其中，所述软件升级请求包括所述请求类型描述信息(VNF LCM请求的类型为VNFC软件升级操作)、所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识以及目标软件升级策略。
S4b10，所述EM根据所述目标软件升级策略，迁移所述第一VNFC实例的业务到所述第二VNFC实例中，当迁移完成时，向所述VNFM发送软件升级响应。
其中，所述软件升级响应可以包括所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识。
S4b11，所述VNFM接收所述软件升级响应后，向所述EM发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括所述第一VNF实例的实例标识。
S4b12，所述EM接收所述VNF LCM响应之后，向所述OSS转发所述VNF LCM响应。
请参阅图4C，假设元数据中的软件修改类型为VNFC软件升级，则本发明实施例提供的软件修改的发起方法具体为VNFC软件升级的发起方法，该方法具体包括以下步骤：
S4c01，操作支持***OSS向网元管理器EM发送虚拟化网络功能VNF生命周期管理 LCM请求。
其中，所述VNF LCM请求中包括待修改的第一版本VNF软件的VNF实例的实例标识、目标软件升级策略、包含元数据的软件包的标识等。其中，所述目标软件升级策略用于是用于升级第一VNFC软件的软件升级策略。
在本示例中，所述VNF LCM请求还包含软件包的标识，所述软件包包含所述元数据和VNF描述符VNFD。
S4c02，所述EM接收所述VNF LCM请求后，向VNFM转发所述VNF LCM请求。
S4c03，所述VNFM确定VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取软件包中的元数据。
其中，所述元数据包括第一版本VNF软件的版本标识和软件修改类型。
在本示例中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在本示例中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识
在本示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
在一个可能的示例中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述元数据还包括至少一个用来升级所述VNF软件的VNFC软件的第二版本VNF软件的VNFC软件的软件镜像的镜像标识、至少一个软件升级策略，所述至少一个软件升级策略包括所述目标软件升级策略。
在一个示例中，所述VNFM根据所述VNF LCM请求获取软件包中用于升级VNFC软件的元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中用于升级VNFC软件的元数据。
S4c04，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识，确定所述第一版本VNF软件的第一VNF实例。
在一个实施例中，本步骤S4c04之前，所述VNFM还执行以下操作：
所述VNFM在根据第一版本VNF软件的VNF实例的实例标识从实例管理数据库中获取到所述第一版本VNF软件的版本标识；
所述VNFM判断出所述元数据中的至少一个适用于通过所述软件包进行升级的VNF软件的版本标识包括所述第一版本VNF软件的版本标识，确定第一版本VNF软件为适用于通过所述软件包进行升级的VNF软件。
S4c05，所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一 版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识。
S4c06，所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
S4c07，所述VNFM根据所述第一VNFC实例的实例标识、VNF描述符VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
在一个可能的示例中，所述元数据还包括软件升级策略和资源选项之间的映射关系；所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项的具体实现方式可以是：所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；根据所述资源选项、所述第一VNFC实例的实例标识和所述VNFD确定连接选项。
S4c08，所述VNFM根据所述申请到的部署选项和所述第二VNFC软件的软将镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
S4c09，所述VNFM向虚拟化网络功能操作与维护器VNF O&M发送软件升级请求，所述软件升级请求用于指示所述VNF O&M升级第一VNFC实例为第二VNFC实例。
其中，所述软件升级请求包括所述请求类型描述信息(VNF LCM请求的类型为VNFC软件升级操作)、所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识以及目标软件升级策略。
S4c10，所述VNF O&M根据所述目标软件升级策略，迁移所述第一VNFC实例的业务到所述第二VNFC实例中，当迁移完成时，向所述VNFM发送软件升级响应。
其中，所述软件升级响应可以包括所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识。
S4c11，所述VNFM接收所述软件升级响应后，向所述EM发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括所述第一VNF实例的实例标识。
S4c12，所述EM接收所述VNF LCM响应之后，向所述OSS发送所述VNF LCM响应。
请参阅图4D，假设元数据中的软件修改类型为VNFC软件升级，则本发明实施例提供的软件修改的发起方法具体为VNFC软件升级的发起方法，该方法具体包括以下步骤：
S4d01，操作支持***OSS通过网元管理器EM向虚拟化网络功能操作与维护器VNF O&M发送虚拟化网络功能VNF生命周期管理LCM请求。
其中，所述VNF LCM请求中包括待修改的第一版本VNF软件的VNF实例的实例标识、目标软件升级策略、包含元数据的软件包的标识等。其中，所述目标软件升级策略用于是用于升级第一VNFC软件的软件升级策略。
在本示例中，所述VNF LCM请求还包含软件包的标识，所述软件包包含所述元数据和VNF描述符VNFD。
S4d02，所述VNF O&M接收所述VNF LCM请求后，向VNFM转发所述VNF LCM请求。
S4d03，所述VNFM确定VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取软件包中的元数据。
其中，所述元数据包括第一版本VNF软件的版本标识和软件修改类型。
在本示例中，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
在本示例中，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识
在本示例中，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
在一个可能的示例中，所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述元数据还包括至少一个用来升级所述VNF软件的VNFC软件的第二版本VNF软件的VNFC软件的软件镜像的镜像标识、至少一个软件升级策略，所述至少一个软件升级策略包括所述目标软件升级策略。
在一个示例中，所述VNFM根据所述VNF LCM请求获取软件包中用于升级VNFC软件的元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中用于升级VNFC软件的元数据。
S4d04，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识，确定所述第一版本VNF软件的第一VNF实例。
在一个实施例中，本步骤S4d04之前，所述VNFM还执行以下操作：
所述VNFM在根据第一版本VNF软件的VNF实例的实例标识从实例管理数据库中获取到所述第一版本VNF软件的版本标识；
所述VNFM判断出所述元数据中的至少一个适用于通过所述软件包进行升级的VNF软件的版本标识包括所述第一版本VNF软件的版本标识，确定第一版本VNF软件为适用于通过所述软件包进行升级的VNF软件。
S4d05，所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识。
S4d06，所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
在一个可能的示例中，所述元数据还包括软件升级策略和资源选项之间的映射关系；所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项的具体实现方式可以是：所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；根据所述资源选项、所述第一VNFC实例的实例标识和所述VNFD确定连接选项。
S4d07，所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软 件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
S4d08，所述VNFM根据所述申请到的部署选项和所述第二VNFC软件的软将镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
S4d09，所述VNFM向所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述VNF O&M升级第一VNFC实例为第二VNFC实例。
其中，所述软件升级请求包括所述请求类型描述信息(VNF LCM请求的类型为VNFC软件升级操作)、所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识以及目标软件升级策略。
S4d10，所述VNF O&M根据所述目标软件升级策略，迁移所述第一VNFC实例的业务到所述第二VNFC实例中，当迁移完成时，向所述VNFM发送软件升级响应。
其中，所述软件升级响应可以包括所述第一VNF实例的实例标识、所述第一VNF实例中的第一VNFC实例的实例标识、所述第二VNFC实例的实例标识。
S4d11，所述VNFM接收所述软件升级响应后，向所述VNF O&M发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括所述第一VNF实例的实例标识。
S4d12，所述VNF O&M接收所述VNF LCM响应之后，通过所述EM向所述OSS转发所述VNF LCM响应。
请参阅图4E，假设元数据中的软件修改类型为VNF软件升级，则本发明实施例提供的软件修改的发起方法具体为软件升级的发起方法，该方法具体包括以下步骤：
S4e01，操作支持***OSS向网元管理器EM发送虚拟化网络功能VNF生命周期管理LCM请求。
S4e02，所述EM接收所述更新网络服务请求后，向VNFM发送所述VNF LCM请求，所述VNF LCM请求包括待升级的第一版本VNF软件的VNF实例的实例标识。
S4e03，所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型。
其中，所述VNFM根据所述VNF LCM请求获取元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
S4e04，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例。
S4e05，所述VNFM在所述第一VNF实例的运行过程中，获取用于实例化第二版本VNF软件为第二VNF实例的部署选项。
S4e06，所述VNFM根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例。
S4e07，所述VNFM向网元管理器EM发送软件升级请求，所述软件升级请求用于指示所述EM升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二 VNF实例。
其中，所述软件升级请求例如可以包括如下信息：第一VNF实例的实例标识、第二VNF实例的实例标识、第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、所述目标软件升级策略等。
S4e08，所述EM升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例，向所述VNFM发送软件升级响应。
其中，所述软件升级响应例如可以包括第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、被升级的第一VNF实例的实例标识以及升级后的第二VNF实例的实例标识。
S4e09，所述VNFM接收所述软件升级响应后，向所述EM发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括被升级的第一VNF实例的实例标识、升级后的第二VNF实例的实例标识。
S4e10，所述EM接收所述VNF LCM响应之后，向所述OSS发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括被升级的第一VNF实例的实例标识、升级后的第二VNF实例的实例标识。
请参阅图5，假设元数据中的软件修改类型为VNF软件更新。则本发明实施例提供的软件修改的发起方法具体为软件更新的发起方法，该方法具体包括以下步骤：
S501，操作支持***OSS向网络功能虚拟化编排器NFVO发送更新网络服务请求(例如：Update NS)。
其中，所述更新网络服务请求例如可以包括：网络服务实例的实例标识、更新网络服务请求类型、待修改的第一版本VNF软件的VNF实例的实例标识、包含元数据的软件包的标识等。
S502，所述NFVO接收所述更新网络服务请求后，向VNFM发送虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待更新的第一版本VNF软件的VNF实例的实例标识。
S503，所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型。
其中，所述VNFM根据所述VNF LCM请求获取元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
S504，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例。
S505，所述VNFM在所述第一VNF实例的运行过程中，获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致。
其中，软件镜像是待更新的VNF软件的VNFC软件的软件镜像，目标执行文件是用于 更新所述待更新的VNF的VNFC软件的软件镜像所对应的执行文件，所述映射关系包括执行文件名和软件镜像的镜像标识，以及执行文件名和软件镜像标识对应关系。所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述VNFC软件的软件镜像的镜像标识包括所述目标执行文件对应的软件镜像的镜像标识。
S506，所述VNFM根据所述存取地址和所述文件名获取所述目标执行文件；
S507，所述VNFM根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像。
其中，所述目标执行文件对应的软件镜像的表示形式是软件镜像标识。
S508，所述VNFM根据所述软件镜像确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机。
S509，所述VNFM向所述待更新的VNFC实例所对应的虚拟机发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
其中，所述软件更新请求例如可以包括第一VNF实例的实例标识、VNFC实例的实例标识、第一版本VNF软件的版本标识、第二版本VNF软件的版本标识等。
S510，所述虚拟机向所述VNFM发送软件更新响应。
其中，所述软件升级响应例如可以包括第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、被更新的第一VNF实例的实例标识以及更新后的第二VNF实例的实例标识。
S511，所述VNFM向所述NFVO发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括被更新的第一VNF实例的实例标识、更新后的第二VNF实例的实例标识。
S512，所述NFVO接收所述VNF LCM响应之后，向所述OSS发送更新网络服务响应。
其中，所述更新网络服务响应例如可以包括被更新的第一VNF实例的实例标识、更新后的第二VNF实例的实例标识。
请参阅图5A，假设元数据中的软件修改类型为VNF软件更新。则本发明实施例提供的软件修改的发起方法具体为软件更新的发起方法，该方法具体包括以下步骤：
S5a01，操作支持***OSS向网元管理器EM发送虚拟化网络功能VNF生命周期管理LCM请求。
S5a02，所述EM接收所述VNF LCM请求后，向VNFM转发所述VNF LCM请求，所述VNF LCM请求包括待更新的第一版本VNF软件的VNF实例的实例标识。
S5a03，所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型。
其中，所述VNFM根据所述VNF LCM请求获取元数据的具体实现方式为：
所述VNFM提取所述VNF LCM请求中的软件包的标识；
所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
S5a04，所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例。
S5a05，所述VNFM在所述第一VNF实例的运行过程中，获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致。
其中，软件镜像是待更新的VNF软件的VNFC软件的软件镜像，目标执行文件是用于更新所述待更新的VNF的VNFC软件的软件镜像所对应的执行文件，所述映射关系包括执行文件名和软件镜像的镜像标识，以及执行文件名和软件镜像标识对应关系。所述元数据包括至少一个VNF软件的版本标识，所述至少一个VNF软件的版本标识包括所述第一版本VNF软件的版本标识，所述元数据还包括所述至少一个VNF软件的VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，所述VNFC软件的软件镜像的镜像标识包括所述目标执行文件对应的软件镜像的镜像标识。
S5a06，所述VNFM根据所述存取地址和所述文件名获取所述目标执行文件；
S5a07，所述VNFM根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像的镜像标识。
S5a08，所述VNFM根据所述软件镜像的镜像标识确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机。
S5a09，所述VNFM向所述待更新的VNFC实例所对应的虚拟机发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
其中，所述软件更新请求例如可以包括第一VNF实例的实例标识、VNFC实例的实例标识、第一版本VNF软件的版本标识、第二版本VNF软件的版本标识等。
S5a10，所述虚拟机向所述VNFM发送软件更新响应。
其中，所述软件升级响应例如可以包括第一版本VNF软件的版本标识、第二版本VNF软件的版本标识、被更新的第一VNF实例的实例标识以及更新后的第二VNF实例的实例标识。
S5a11，所述VNFM向所述EM发送VNF LCM响应。
其中，所述VNF LCM响应例如可以包括被更新的第一VNF实例的实例标识、更新后的第二VNF实例的实例标识。
S5a12，所述EM接收所述VNF LCM响应之后，向所述OSS发送更新网络服务响应。
其中，所述更新网络服务响应例如可以包括被更新的第一VNF实例的实例标识、更新后的第二VNF实例的实例标识。
上述主要从发布元数据的装置和NFV***中的VNFM的执行过程的角度对本发明实施例的方案进行了介绍。可以理解的是，发布元数据的装置和VNFM为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使 用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本发明实施例可以根据上述方法示例对发布元数据的装置和VNFM进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。此外，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图6A示出了上述实施例中所涉及的VNFM的一种可能的结构示意图。VNFM600包括：处理单元602和通信单元603。处理单元602用于对VNFM的动作进行控制管理，例如，处理单元602用于支持VNFM执行图2中的步骤S202至204、图4中的步骤S403至S407、S409、图4A中的步骤S4a03至S4a09、S4a11、图4B中的S4b03至S4b09、S4b11、图4C中的步骤S4bc03、至S4c09、S4c11、图4D中的步骤S4dc03至S4d09、S4d11、图4E中的步骤S4ec03至S4e07、S4e09、以及图5中的步骤S503至S509、S511、图5A中的步骤S5a03至S5a09、S5a11和/或用于本文所描述的技术的其它过程。通信单元603用于支持VNFM与发布元数据的装置或NFV***中的其他网元之间的通信，例如与NFV***中的NFVO之间的通信。VNFM还可以包括存储单元601，用于存储VNFM的程序代码和数据。
其中，处理单元602可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元603可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元601可以是存储器。
当处理单元602为处理器，通信单元603为通信接口，存储单元601为存储器时，本发明实施例所涉及的VNFM可以为图6B所示的VNFM。
参阅图6B所示，该VNFM610包括：处理器612、通信接口613、存储器611。可选的，VNFM610还可以包括总线614。其中，通信接口613、处理器612以及存储器611可以通过总线614相互连接；总线614可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线614可以分为地址总线、数据总线、控制总线等。为便于表示，图6B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图6A或图6B所示的VNFM也可以理解为一种用于VNFM的装置，本发明实施例不限定。
在采用集成的单元的情况下，图7A示出了上述实施例中所涉及的发布元数据的装置的一种可能的结构示意图。
发布元数据的装置700包括：处理单元702和通信单元703。处理单元702用于对发布元数据的装置的动作进行控制管理，例如，处理单元702用于支持发布元数据的装置执 行图3中的步骤S301和S302和/或用于本文所描述的技术的其它过程。通信单元703用于支持发布元数据的装置与NFV***的通信，例如与NFV***中的NFVO之间的通信。发布元数据的装置还可以包括存储单元701，用于存储发布元数据的装置的程序代码和数据。
其中，处理单元702可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元703可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元701可以是存储器。
当处理单元702为处理器，通信单元703为通信接口，存储单元701为存储器时，本发明实施例所涉及的发布元数据的装置可以为图7B所示的发布元数据的装置。
参阅图7B所示，该发布元数据的装置710包括：处理器712、通信接口713、存储器711。可选的，发布元数据的装置710还可以包括总线714。其中，通信接口713、处理器712以及存储器711可以通过总线714相互连接；总线714可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线714可以分为地址总线、数据总线、控制总线等。为便于表示，图7B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图7A或图7B所示的发布元数据的装置也可以理解为一种用于发布元数据的装置中的装置，本发明实施例不限定。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时包括上述方法实施例中记载的任何一种软件修改的发起方法的部分或全部步骤。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时包括上述方法实施例中记载的任何一种发布元数据的方法的部分或全部步骤。
此外，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本发明所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接， 可以是电性或其它的形式。所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储器中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上对本发明实施例进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (40)

  1. 一种软件修改的发起方法，其特征在于，应用于网络功能虚拟化NFV***，所述NFV***包括虚拟化网络功能管理器VNFM，所述方法包括：
    所述VNFM接收虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待修改的第一版本VNF软件的VNF实例的实例标识；
    所述VNFM确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型；
    所述VNFM根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例；
    所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
  2. 根据权利要求1所述的方法，其特征在于，所述NFV***包括网络功能虚拟化编排器NFVO；所述VNFM接收虚拟化网络功能VNF生命周期管理LCM请求，包括：
    所述VNFM接收所述NFVO发送的虚拟化网络功能VNF生命周期管理LCM请求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述NFV***运行有所述第一VNF实例，所述第一VNF实例是所述NFV***实例化所述第一版本VNF软件而得到的；所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
    所述VNFM在所述第一VNF实例的运行过程中，根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述元数据中的软件修改类型为VNF软件升级。
  5. 根据权利要求4所述的方法，其特征在于，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
    所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项；
    所述VNFM根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例；
    所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例。
  6. 根据权利要求4或5所述的方法，其特征在于，所述元数据还包括软件升级策略和资源选项之间的映射关系，所述部署选项包括资源选项和连接选项，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项，包括：
    所述VNFM获取所述VNF LCM请求中的用于升级为第二版本VNF软件的第二VNF实例的目标软件升级策略；
    所述VNFM根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；
    所述VNFM确定所述资源选项所对应的连接选项。
  7. 根据权利要求4或5所述的方法，其特征在于，所述VNFM获取用于实例化第二版本VNF软件为第二VNF实例的部署选项，包括：
    所述VNFM获取所述VNF LCM请求中用于实例化第二版本VNF软件为第二VNF实例的部署选项。
  8. 根据权利要求1-3任一项所述的方法，其特征在于，所述元数据中的软件修改类型为VNF软件更新。
  9. 根据权利要求8所述的方法，其特征在于，所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
    所述VNFM获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致；
    所述VNFM根据所述存取地址和所述文件名获取所述目标执行文件；
    所述VNFM根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像；
    所述VNFM根据所述软件镜像确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机；
    所述VNFM发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
  10. 根据权利要求1-3任一项所述的方法，其特征在于，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
  11. 根据权利要求10所述的方法，其特征在于，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M；
    所述VNFM根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作，包括：
    所述VNFM确定所述元数据中的软件修改类型为所述VNFC软件升级，根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识；
    所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例；
    所述VNFM向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一VNFC实例为所述第二VNFC实例。
  12. 根据权利要求11所述的方法，其特征在于，所述VNFM根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识，包括：
    所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
    所述VNFM根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实 例的实例标识；
    所述VNFM根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例，包括：
    所述VNFM根据所述第一VNFC实例的实例标识申请资源；
    所述VNFM根据所述申请到的资源和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
  13. 根据权利要求12所述的方法，其特征在于，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
    所述VNFM根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识，包括：
    所述VNFM根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
    所述VNFM根据所述第一VNFC实例的实例标识申请资源，包括：
    所述VNFM根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
  14. 根据权利要求2所述的方法，其特征在于，所述VNF LCM请求是所述NFVO在接收到操作支持***OSS发送的更新网络服务请求的情况下生成的。
  15. 根据权利要求1-14任一项所述的方法，其特征在于，所述VNFM根据VNF LCM请求获取元数据，包括：
    所述VNFM提取所述VNF LCM请求中的软件包的标识；
    所述VNFM根据所述软件包的标识获取所述软件包中的元数据。
  16. 一种发布元数据的方法，其特征在于，包括：
    生成元数据，所述元数据包括适用于修改为第二版本VNF软件的NFV***中的第一版本VNF软件的版本标识和软件修改类型；
    发布所述元数据。
  17. 根据权利要求16所述的方法，其特征在于，所述软件修改类型为VNF软件升级，所述元数据还包括所述软件升级策略和资源选项之间的映射关系。
  18. 根据权利要求16所述的方法，其特征在于，所述软件修改类型为虚拟化网络功能组件VNFC软件升级，所述第一版本VNF软件包括第一VNFC软件，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识。
  19. 根据权利要求16所述的方法，其特征在于，所述软件修改类型为VNF软件更新， 所述元数据还包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系。
  20. 根据权利要求16-19任一项所述的方法，其特征在于，所述元数据集成在软件包中。
  21. 一种虚拟化网络功能管理器VNFM，应用于网络功能虚拟化NFV***，其特征在于，包括处理单元和通信单元，
    所述处理单元通过所述通信单元接收虚拟化网络功能VNF生命周期管理LCM请求，所述VNF LCM请求包括待修改的第一版本VNF软件的VNF实例的实例标识；以及用于确定所述VNF LCM请求的类型为软件修改操作并根据所述VNF LCM请求获取元数据，其中，所述元数据包括所述第一版本VNF软件的版本标识和软件修改类型；以及用于根据所述第一版本VNF软件的版本标识和所述待修改的第一版本VNF软件的VNF实例的实例标识确定所述第一版本VNF软件的第一VNF实例；以及用于根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
  22. 根据权利要求21所述的VNFM，其特征在于，所述NFV***包括网络功能虚拟化编排器NFVO；在所述通过所述通信单元接收虚拟化网络功能VNF生命周期管理LCM请求方面，所述处理单元具体用于：通过所述通信单元接收所述NFVO发送的虚拟化网络功能VNF生命周期管理LCM请求。
  23. 根据权利要求21或22所述的VNFM，其特征在于，所述NFV***运行有所述第一VNF实例，所述第一VNF实例是所述NFV***实例化所述第一版本VNF软件而得到的；在所述根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作方面，所述处理单元具体用于：在所述第一VNF实例的运行过程中，根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作。
  24. 根据权利要求21-23任一项所述的VNFM，其特征在于，所述元数据中的软件修改类型为VNF软件升级。
  25. 根据权利要求24所述的VNFM，其特征在于，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M，在所述根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作方面，所述处理单元具体用于：通过所述通信单元获取用于实例化第二版本VNF软件为第二VNF实例的部署选项；以及用于根据所述部署选项实例化所述第二版本VNF软件为所述第二VNF实例；以及用于通过所述通信单元向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一版本VNF软件的第一VNF实例为所述第二版本VNF软件的第二VNF实例。
  26. 根据权利要求24或25所述的VNFM，其特征在于，所述元数据还包括软件升级策略和资源选项之间的映射关系，所述部署选项包括资源选项和连接选项，在所述通过所述通信单元获取用于实例化第二版本VNF软件为第二VNF实例的部署选项方面，所述处理单元具体用于：通过所述通信单元获取所述VNF LCM请求中的用于升级为第二版本VNF软件的第二VNF实例的目标软件升级策略；根据所述元数据中的软件升级策略和资源选项之间的映射关系，确定所述目标软件升级策略所对应的资源选项；确定所述资源选 项所对应的连接选项。
  27. 根据权利要求24或25所述的VNFM，其特征在于，在所述通过所述通信单元获取用于实例化第二版本VNF软件为第二VNF实例的部署选项方面，所述处理单元具体用于：通过所述通信单元获取所述VNF LCM请求中用于实例化第二版本VNF软件为第二VNF实例的部署选项。
  28. 根据权利要求21-23任一项所述的VNFM，其特征在于，所述元数据中的软件修改类型为VNF软件更新。
  29. 根据权利要求28所述的VNFM，其特征在于，在所述根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作方面，所述处理单元具体用于：获取所述元数据中用于更新为所述第二版本VNF软件的第二VNF实例的目标执行文件的文件名和存取地址、以及执行文件和软件镜像之间的映射关系，所述第一VNF实例的实例标识和所述第二VNF实例的实例标识一致；以及用于根据所述存取地址和所述文件名获取所述目标执行文件；以及用于根据所述执行文件和软件镜像之间的映射关系，确定所述目标执行文件对应的软件镜像；以及用于根据所述软件镜像确定第一VNF实例中待更新的虚拟化网络功能组件VNFC实例所对应的虚拟机；以及用于通过所述通信单元发送软件更新请求，所述软件更新请求用于指示所述虚拟机运行所述执行文件更新所述VNFC实例。
  30. 根据权利要求21-23任一项所述的VNFM，其特征在于，所述元数据中的软件修改类型为虚拟化网络功能组件VNFC软件升级，所述待修改的第一版本VNF软件包括第一VNFC软件。
  31. 根据权利要求30所述的VNFM，其特征在于，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识，所述NFV***还包括网元管理器EM和虚拟化网络功能操作与维护器VNF O&M；
    在所述根据所述软件修改类型对所述第一版本VNF软件的第一VNF实例发起软件修改操作方面，所述处理单元具体用于：确定所述元数据中的软件修改类型为所述VNFC软件升级，根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识；以及用于根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例；以及用于通过所述通信单元向所述EM或所述VNF O&M发送软件升级请求，所述软件升级请求用于指示所述EM或所述VNF O&M升级所述第一VNFC实例为所述第二VNFC实例。
  32. 根据权利要求31所述的VNFM，其特征在于，在所述根据所述第一VNF实例的实例标识确定所述第一VNFC实例的实例标识方面，所述处理单元具体用于：根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；以及用于根据所述第一VNFC软件的软件镜像的镜像标识确定所述第一VNFC实例的实例标识；
    在所述根据所述第一VNFC实例的实例标识和所述第二VNFC软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例方面，所述处理单元具体用于：根据所述第一VNFC实例的实例标识申请资源；以及用于根据所述申请到的资源和所述第二VNFC 软件的软件镜像的镜像标识，实例化第二VNFC软件为第二VNFC实例。
  33. 根据权利要求32所述的VNFM，其特征在于，所述VNF LCM请求包含软件包的标识和目标软件升级策略，所述软件包包含所述元数据和VNF描述符VNFD，所述元数据还包括VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识；
    在所述根据所述第一VNF实例的实例标识确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识方面，所述处理单元具体用于：根据所述第一VNF实例的实例标识、所述VNFC软件的软件镜像的镜像标识和所述软件镜像对应的VNFC软件所属的VNF软件的版本标识，确定所述第一版本VNF软件中所述第一VNFC软件的软件镜像的镜像标识；
    在所述根据所述第一VNFC实例的实例标识申请资源方面，所述处理单元具体用于：根据所述第一VNFC实例的实例标识、所述VNFD和所述目标软件升级策略，确定资源选项和连接选项，并根据所述资源选项、所述连接选项以及所述第二VNFC软件的软件镜像的镜像标识申请部署选项。
  34. 根据权利要求22所述的VNFM，其特征在于，所述VNF LCM请求是所述NFVO在接收到操作支持***OSS发送的更新网络服务请求的情况下生成的。
  35. 根据权利要求21-34任一项所述的VNFM，其特征在于，在所述根据VNF LCM请求获取元数据方面，所述处理单元具体用于：提取所述VNF LCM请求中的软件包的标识；根据所述软件包的标识获取所述软件包中的元数据。
  36. 一种发布元数据的装置，应用于网络功能虚拟化NFV***，其特征在于，包括处理单元和通信单元，
    所述处理单元用于生成元数据，所述元数据包括适用于修改为第二版本VNF软件的NFV***中的第一版本VNF软件的版本标识和软件修改类型；以及用于发布所述元数据。
  37. 根据权利要求36所述的装置，其特征在于，所述软件修改类型为VNF软件升级，所述元数据还包括所述软件升级策略和资源选项之间的映射关系。
  38. 根据权利要求36所述的装置，其特征在于，所述软件修改类型为虚拟化网络功能组件VNFC软件升级，所述第一版本VNF软件包括第一VNFC软件，所述NFV***运行有第一VNFC实例，所述第一VNFC示例是所述NFV***实例化所述第一VNFC软件而得到的，所述元数据还包括用于升级所述第一VNFC软件的第二VNFC软件的软件镜像的镜像标识。
  39. 根据权利要求36所述的装置，其特征在于，所述软件修改类型为VNF软件更新，所述元数据还包括用于更新为所述第二版本VNF软件的目标执行文件的文件名和存取地址、执行文件与软件镜像之间的映射关系。
  40. 根据权利要求36-39任一项所述的装置，其特征在于，所述元数据集成在软件包中。
PCT/CN2017/093415 2016-10-18 2017-07-18 软件修改的发起方法、发布元数据的方法及装置 WO2018072503A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17862212.2A EP3518465B1 (en) 2016-10-18 2017-07-18 Method and device for initiating software modification
EP20208739.1A EP3839726B1 (en) 2016-10-18 2017-07-18 Software modification initiation method and apparatus
US16/388,852 US10742502B2 (en) 2016-10-18 2019-04-18 Software modification initiation method, and metadata release method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201610908967 2016-10-18
CN201610908967.9 2016-10-18
CN201710057662.6 2017-01-26
CN201710057662.6A CN107967140B (zh) 2016-10-18 2017-01-26 软件修改的发起方法、发布元数据的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/388,852 Continuation US10742502B2 (en) 2016-10-18 2019-04-18 Software modification initiation method, and metadata release method and apparatus

Publications (1)

Publication Number Publication Date
WO2018072503A1 true WO2018072503A1 (zh) 2018-04-26

Family

ID=61997375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/093415 WO2018072503A1 (zh) 2016-10-18 2017-07-18 软件修改的发起方法、发布元数据的方法及装置

Country Status (4)

Country Link
US (1) US10742502B2 (zh)
EP (2) EP3518465B1 (zh)
CN (1) CN107967140B (zh)
WO (1) WO2018072503A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020250077A1 (en) * 2019-06-11 2020-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Virtual network function and physical network function software upgrade

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11327787B2 (en) * 2016-08-17 2022-05-10 Apple Inc. Using a managed object operation to control a lifecycle management operation
US10306020B2 (en) * 2016-09-21 2019-05-28 Nokia Of America Corporation Software upgrade in a virtualized offline charging system
KR102036731B1 (ko) * 2018-09-06 2019-10-25 숭실대학교산학협력단 가상화 네트워크 기능 클러스터링 구성 시스템 및 방법
CN109714239B (zh) * 2018-12-27 2021-04-27 新华三技术有限公司 一种管理消息的下发方法、vnfm设备和服务器
CN111510314B (zh) * 2019-01-31 2021-07-06 大唐移动通信设备有限公司 一种核心网网元升级处理方法及装置
US11916744B2 (en) 2019-11-25 2024-02-27 Telefonaktiebolaget Lm Ericsson (Publ) Technique for replacing VNFMs in a VNF based environment
CN111897543A (zh) * 2020-01-16 2020-11-06 中兴通讯股份有限公司 一种软件管理方法、装置、管理设备及存储介质
EP4133693A4 (en) * 2020-05-14 2023-09-13 Samsung Electronics Co., Ltd. METHOD AND APPARATUS FOR UPGRADING RANDOM ACCESS NETWORK IN COMMUNICATION SYSTEM
CN116368780A (zh) * 2020-11-04 2023-06-30 英特尔公司 Mda报告请求、获取和上报

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1659539A (zh) * 2002-04-19 2005-08-24 因卡网络工程公司 一种具有虚拟服务模块的网络***
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、***及相关设备
WO2015113278A1 (zh) * 2014-01-29 2015-08-06 华为技术有限公司 虚拟网络功能的升级方法和网络功能虚拟化编排器
CN105577409A (zh) * 2014-10-16 2016-05-11 中兴通讯股份有限公司 一种实现虚拟网络功能自动部署的方法和装置
US20160205004A1 (en) * 2015-01-13 2016-07-14 Intel IP Corporation Techniques for Monitoring Virtualized Network Functions or Network Functions Virtualization Infrastructure

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6026705B2 (ja) * 2014-03-28 2016-11-16 株式会社Ｎｔｔドコモ 更新管理システムおよび更新管理方法
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理***
CN104410672B (zh) * 2014-11-12 2017-11-24 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置
US10348517B2 (en) * 2015-10-09 2019-07-09 Openet Telecom Ltd. System and method for enabling service lifecycle based policy, licensing, and charging in a network function virtualization ecosystem
CN106982129A (zh) * 2016-01-15 2017-07-25 中兴通讯股份有限公司 软件升级方法及装置
US11327787B2 (en) * 2016-08-17 2022-05-10 Apple Inc. Using a managed object operation to control a lifecycle management operation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1659539A (zh) * 2002-04-19 2005-08-24 因卡网络工程公司 一种具有虚拟服务模块的网络***
WO2015113278A1 (zh) * 2014-01-29 2015-08-06 华为技术有限公司 虚拟网络功能的升级方法和网络功能虚拟化编排器
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、***及相关设备
CN105577409A (zh) * 2014-10-16 2016-05-11 中兴通讯股份有限公司 一种实现虚拟网络功能自动部署的方法和装置
US20160205004A1 (en) * 2015-01-13 2016-07-14 Intel IP Corporation Techniques for Monitoring Virtualized Network Functions or Network Functions Virtualization Infrastructure

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020250077A1 (en) * 2019-06-11 2020-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Virtual network function and physical network function software upgrade
US11836478B2 (en) 2019-06-11 2023-12-05 Telefonaktiebolaget L M Ericsson (Publ) Virtual network function and physical network function software upgrade

Also Published As

Publication number Publication date
EP3518465A1 (en) 2019-07-31
EP3839726A1 (en) 2021-06-23
US10742502B2 (en) 2020-08-11
CN107967140A (zh) 2018-04-27
EP3518465B1 (en) 2020-12-02
EP3839726B1 (en) 2023-09-06
EP3518465A4 (en) 2019-09-25
CN107967140B (zh) 2021-08-03
US20190245741A1 (en) 2019-08-08

Similar Documents

Publication Publication Date Title
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
US10432460B2 (en) Network service scaling method and apparatus
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US10831574B2 (en) Remote procedure call method for network device and network device
US10700947B2 (en) Life cycle management method and device for network service
US10270648B2 (en) Configuration information management method, device, network element management system and storage medium
EP3455728B1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
US9628290B2 (en) Traffic migration acceleration for overlay virtual environments
US10917294B2 (en) Network function instance management method and related device
US9348646B1 (en) Reboot-initiated virtual machine instance migration
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
US10911333B2 (en) Network service life cycle management grant method and apparatus
JP6466003B2 (ja) Ｖｎｆフェイルオーバの方法及び装置
EP3471345A1 (en) Sla-based resource allocation method and nfvo
WO2020177564A1 (zh) Vnf的生命周期管理方法及装置
US10541862B2 (en) VNF processing policy determining method, apparatus, and system
CN106031116A (zh) 一种ns与vnf的关联方法、装置及***
US20180004563A1 (en) Orchestrator apparatus, system, virtual machine creation method, and computer-readable recording medium
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备
CN108370329B (zh) 管理功能对象的管理方法及装置
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
WO2018119826A1 (zh) 网络服务更新方法、nfvo及nfv***
WO2021121595A1 (en) Discovering an instance of a virtual network function
CN118057776A (zh) 部署虚拟化网络功能的方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17862212

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017862212

Country of ref document: EP

Effective date: 20190423