WO2018014356A1 - 一种加载方法及装置 - Google Patents

一种加载方法及装置 Download PDF

Info

Publication number
WO2018014356A1
WO2018014356A1 PCT/CN2016/091089 CN2016091089W WO2018014356A1 WO 2018014356 A1 WO2018014356 A1 WO 2018014356A1 CN 2016091089 W CN2016091089 W CN 2016091089W WO 2018014356 A1 WO2018014356 A1 WO 2018014356A1
Authority
WO
WIPO (PCT)
Prior art keywords
descriptor
unit
request message
nfvo
network function
Prior art date
Application number
PCT/CN2016/091089
Other languages
English (en)
French (fr)
Inventor
周彦
邹兰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/091089 priority Critical patent/WO2018014356A1/zh
Publication of WO2018014356A1 publication Critical patent/WO2018014356A1/zh
Priority to US16/251,971 priority patent/US20190155834A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/53Querying
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/162Delete operations
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/182Distributed file systems
    • G06F16/1824Distributed file systems implemented using Network-attached Storage [NAS] architecture
    • G06F16/183Provision of network file services by network file servers, e.g. by using NFS, CIFS
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/188Virtual file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/63Image based installation; Cloning; Build to order
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45583Memory management, e.g. access or allocation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a loading method and apparatus.
  • NFV Network Function Virtualization
  • VNF virtualized network function
  • Embodiments of the present invention provide a loading method and apparatus for avoiding repeated loading of sub-portions in a VNF unit that are not required to operate.
  • an embodiment of the present invention provides a loading method.
  • the method includes: the NFVO unit receives a first load request message from the NM unit, where the first load request message includes an image file of a partial virtual network function module of the virtual network function VNF unit, where the first load request message is used to request the NFVO
  • the unit loads the image file; the NFVO unit loads the image file.
  • the NFVO unit may further send a first load response message to the NM unit, where the first load response message is used to notify that the image file is successfully loaded.
  • the NFVO unit when the image file of the virtual network function module of the VNF unit needs to be loaded, the NFVO unit can independently perform the image file.
  • the loading operation instead of performing the loading operation on the entire VNF package according to the usual processing manner, thereby avoiding other virtual network function modules in the VNF unit when only the image file of the virtual network function module of the VNF unit needs to be loaded.
  • the image file is also reloaded.
  • the first loading request message may further include a descriptor of a part of the virtual network function module, where the descriptor is used to describe deployment information and maintenance information of the part of the virtual network function module, and the loading method may also be Including: the NFVO unit loads the descriptor.
  • a part of the virtual network function module of the VNF unit corresponds to a package, including an image file and a descriptor of the part of the virtual network function module, when an image file of a part of the virtual network function module of the VNF unit is required and / or when the descriptor is loaded, NFVO can perform independent loading operations on the packets corresponding to the part of the virtual network function module, instead of performing a loading operation on the entire VNF package according to the usual processing manner, thereby avoiding the need to only When the image files and/or descriptors of some virtual network function modules are loaded, the image files or descriptors of other virtual network function modules in the VNF unit are also reloaded.
  • the loading method may further include: the NFVO unit receives a second load request message from the NM unit, where the second load request message includes a descriptor of a partial virtual network function module, and the descriptor is used to describe The deployment information and maintenance information of the part of the virtual network function module, the second load request message is used to request the NFVO unit to load the descriptor; the NFVO unit loads the descriptor.
  • the NFVO unit may further send a second load response message to the NM unit, where the second load response message is used to notify that the descriptor is successfully loaded.
  • the NFVO unit can also perform independent loading operations on the descriptors of some virtual network function modules, thereby avoiding the VNF unit when only the deployment mode of some virtual network function modules of the VNF unit needs to be updated. The deployment of other virtual network function modules is repeatedly loaded.
  • the first load request message or the second load request message may further include an identifier of the descriptor, and the NFVO unit may load the descriptor and the identifier of the descriptor.
  • the NFVO unit may also assign an identifier to the descriptor for the descriptor; the NFVO unit may load the descriptor and the identifier of the descriptor.
  • the NFVO unit may further send the identifier of the descriptor of the NFVO unit to the NM unit in the first load response message, or the NFVO unit may carry the identifier of the descriptor in another message and send the message to the NM unit. So that the NM unit knows the identity of the descriptor.
  • the loading method may further include: the NFVO unit receiving, by the NM unit, a first management request message, where the first management request message is used to instruct the NFVO unit to update, query, or delete the image file; The NFVO unit updates, queries, or deletes the image file.
  • the NFVO unit can perform independent management operations on the image files of some virtual network function modules in the VNF unit, thereby avoiding the update or deletion of the image file of the part of the virtual network function module in the normal processing mode.
  • the entire VNF package is updated, causing the image files of other virtual network function modules in the VNF unit to be reloaded, which greatly reduces the workload of network maintenance.
  • the loading method may further include: the NFVO unit receiving a second management request message from the NM unit, the second management request message being used to instruct the NFVO to update, query, or delete the descriptor; The NFVO unit updates, queries, or deletes the descriptor.
  • the NFVO unit can independently manage the descriptors of some of the virtual network function modules in the VNF unit, thereby avoiding the usual processing method, because the part of the virtual network function module needs to be redeployed or deleted.
  • the VNFD of the VNF unit in which the part of the virtual network function module is located is updated, which causes the entire VNF unit to be redeployed, thereby greatly reducing the workload and risk of network maintenance.
  • the loading method may further include: the NFVO unit receiving a third management request message from the NM unit, the third management request message is used to instruct the NFVO unit to update the image file and the descriptor, Query or delete; the NFVO unit updates, queries, or deletes the image file and the descriptor.
  • the application software needs to be updated, the deployment mode needs to be updated, or The part of the virtual network function module needs to be deleted, and the NFVO unit performs an independent management operation on the packet corresponding to the part of the virtual network function module, thereby avoiding the usual processing method, because the part of the virtual network function module needs to perform related management operations, As a result, the entire VNF package is managed, which leads to related management operations for the entire VNF unit, thereby greatly reducing the workload and risk of network maintenance.
  • the loading method may further include: the NFVO unit sending an instantiation request message to the VNFM unit, where the instantiation request message includes identifiers of descriptors of all virtual network function modules of the VNF unit, the all The identification of the descriptor of the virtual network function module is used for instantiation of the VNF unit.
  • the loading method may further include: sending, by the NFVO unit, a capacity expansion request message or a volume reduction request message to the VNFM unit, where the content expansion request message or the contention request message includes a description of the part of the virtual network function module.
  • the identifier of the character, the identifier of the descriptor of the part of the virtual network function module is used for expansion or contraction of the part of the virtual network function module. It can be seen that, based on the possible design, during the expansion and contraction of the VNF unit, the NFVO unit can redeploy a specified part of the virtual network function module in the VNF unit without redeploying the entire VNF unit.
  • an embodiment of the present invention provides another loading method.
  • the method includes: the NM unit sends a first load request message to the NFVO unit, where the first load request message includes an image file of a part of the virtual network function module of the virtual network function VNF unit, where the first load request message is used to request the NFVO
  • the unit loads the image file.
  • the NM unit may further receive a first load response message from the NFVO unit, where the first load response message is used to notify that the image file is successfully loaded.
  • the NM unit may instruct the NFVO unit to perform an independent loading operation on the image file by using the first loading request message. Instead of performing the loading operation on the entire VNF package according to the usual processing manner, the image file of other virtual network function modules in the VNF unit is avoided when only the image file of the virtual network function module of the VNF unit needs to be loaded. Also reloaded.
  • the first load request message may further include a partial virtual network A descriptor of the function module, such that the NFVO unit loads the descriptor after receiving the first load request message.
  • the loading method may further include: the NM unit sends a second load request message to the NFVO unit, where the second load request message includes a descriptor of a part of the virtual network function module, and the descriptor is used to describe The deployment information and maintenance information of the part of the virtual network function module, the second load request message is used to request the NFVO unit to load the descriptor.
  • the NM unit may further receive a second load response message from the NFVO unit, where the second load response message is used to notify that the descriptor is successfully loaded.
  • the first load request message or the second load request message may further include an identifier of the descriptor, so that the NFVO unit receives the first load request message or the second load request message after the descriptor The identity is loaded.
  • the NM unit may also receive an identification of the descriptor from the NFVO unit, the identification of the descriptor being assigned to the NFVO.
  • the loading method may further include: the NM unit sends a first management request message to the NFVO unit, where the first management request message is used to instruct the NFVO unit to update, query, or delete the image file.
  • the loading method may further include: the NM unit sends a second management request message to the NFVO unit, where the second management request message is used to indicate that the NFVO updates, queries, or deletes the descriptor.
  • the loading method may further include: the NM unit sends a third management request message to the NFVO unit, where the third management request message is used to instruct the NFVO unit to update the image file and the descriptor, Query or delete.
  • an embodiment of the present invention provides an NFVO unit, where the NFVO unit can implement the functions performed by the NFVO unit in the method related to the foregoing aspect, and the function can be implemented by using hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the NFVO unit includes a processor and a communication interface configured to support the NFVO unit to perform the corresponding functions of the above methods.
  • the communication interface is used to support communication between the NFVO unit and other network elements.
  • the NFVO single The unit may also include a memory for coupling with the processor that holds the necessary program instructions and data for the NFVO unit.
  • an embodiment of the present invention provides an NM unit, where the NM can implement the functions performed by the NM unit in the method embodiment related to the foregoing aspect, where the function can be implemented by using hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the NM unit includes a processor and a communication interface configured to support the NM unit to perform a corresponding function in the above method.
  • the transceiver is used to support communication between the NM unit and other network elements.
  • the NM unit can also include a memory for coupling with the processor that holds the necessary program instructions and data for the NM unit.
  • an embodiment of the present invention provides a communication system including the NFVO unit and the NM unit described in the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the NFVO unit, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the above NM unit, including a program designed to perform the above aspects.
  • the NFVO unit may perform an independent loading operation on the image file instead of following the
  • the usual processing method is to perform a loading operation on the entire VNF package, thereby avoiding that the image files of other virtual network function modules in the VNF unit are also reloaded when only the image files of some virtual network function modules need to be loaded.
  • FIG. 1 is a schematic diagram of a network architecture based on NFV according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a loading method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of another loading method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication according to still another loading method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of a management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of another management method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an NFVO according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another NFVO according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of an NM according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another NM according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • FIG. 1 shows an NFV-based network architecture.
  • the network architecture includes a Network Functions Virtualization Orchestrator (NFVO) unit, a Virtualized Network Function Manager (VNFM) unit, and a Virtualized Infrastructure Manager (VIM). Unit, Operation Support System (OSS) or Business Support System (BSS), Element Manager (EM) unit, VNF unit, Network Function Virtualization Infrastructure (NFVI) ).
  • NFVO Network Functions Virtualization Orchestrator
  • VNFM Virtualized Network Function Manager
  • VNFVI Virtualized Infrastructure Manager
  • NFVI Network Function Virtualization Infrastructure
  • each unit in FIG. 1 can also be described by its abbreviation.
  • the NFVO unit can be described as NFVO
  • the VNF unit can be described as VNF.
  • Other units are similar and will not be described again.
  • NFVO, VNFM, and VIM form the Management and Orchestration (MANO) domain of the NFV system.
  • the EM performs function configuration, fault management, function usage record, performance statistics, security management, etc. for one or at least two VNFs.
  • the VNF is a virtualized logical network element, such as SGSN, MME, GGSN, SGW, and PGW in the telecom packet field. Each network element can be deployed independently and presented as a VNF.
  • NFVI provides hardware resources and virtualization resources and management for VNF, as well as virtualized runtime environments.
  • NFVO is responsible for the lifecycle management of Network Service (NS) and can orchestrate the resources of NFVI by instructing VIM.
  • NS Network Service
  • VNFM is responsible for the lifecycle management of VNF, and each VNF has an associated VNFM.
  • a VNFM may manage one VNF, or it may manage multiple VNFs of the same type or even different types.
  • VIM is responsible for controlling and managing resources in the VNFI infrastructure, including: computing resources, storage resources, network resources, etc., which are usually an operator's infrastructure.
  • any one of the functional units in the NFV system may be distributed on one physical device or may be distributed on multiple physical devices, and multiple functional units in the NFV system may be respectively distributed on different physical devices. It may also be distributed on the same physical device. It can be understood that any functional unit in the NFV system may be a logical function module in the physical device, or may be a logical function module composed of multiple physical devices.
  • each step in the method provided by the embodiment of the present invention may be performed by a physical device, and the embodiments of the present invention may be performed by multiple physical devices.
  • the various steps in the method of supply are not limited in this regard.
  • the NFV system can be applied to a Long Term Evolution (LTE) communication system, and can also be applied to an LTE-A (Long Term Evolution Advanced) system, a fifth generation (5th Generation, 5G) communication.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Advanced
  • 5G fifth generation
  • the system or other systems that may appear in the future can also be applied to a third-generation (3G) communication system such as WCDMA, and the present invention is not limited.
  • 3G third-generation
  • the operation for one VNF unit corresponds to the operation of an overall VNF packet.
  • the VNF package may include a virtual network function descriptor (VNF Descriptor, VNFD) for describing a template for deployment and maintenance of the VNF unit, and an image file of each software running on the VNF unit, for example, different applications ( The image file of Application, App, and the image file of the virtual machine software or system software that provides the running environment for the application.
  • VNF Descriptor VNF Descriptor
  • the image file of Application, App and the image file of the virtual machine software or system software that provides the running environment for the application.
  • you need to update a certain software you need to replace the image file of the software update with the corresponding image file in the VNF package, and then reload the updated VNF package to overwrite the originally saved VNF package, thus eliminating the need to perform
  • the other image files that were changed are loaded repeatedly.
  • application software has a higher update frequency than virtual machine software or system software. Whenever an application software needs to be updated, the
  • an embodiment of the present invention provides a loading method, and an NFVO, NM and system based on the method.
  • the NFVO receives a first load request message from the NM, where the first load request message includes an image file of a part of the virtual network function module of the VNF unit, where the first load request message is used to request the NFVO to load the image file; load.
  • the NFVO may also send a first load response message to the NM, where the first load response message is used to notify that the image file is successfully loaded.
  • the foregoing part of the virtual network function module may be one or at least two virtual network function modules, and the embodiment of the present invention does not. Limit the number of virtual network function modules for this part.
  • the NFVO may perform an independent loading operation on the image file instead of the usual processing manner for the entire VNF.
  • the package performs the loading operation, thereby avoiding the image file of other virtual network function modules in the VNF unit being reloaded when only the image files of some virtual network function modules need to be loaded.
  • the VNF unit may be divided into multiple virtual network function modules according to actual needs.
  • the relatively stable software module in the VNF unit is divided into a virtual network function module, and each software module with a higher update frequency is divided into a virtual network function module, and may also be divided according to the type of software in the VNF unit.
  • a virtual network function module includes one or a type of software.
  • the virtual network function module may also be referred to as a virtual network function component (VNF Component, VNFC).
  • a relatively stable software module such as a virtual machine software and a system software may be divided into a virtual network function module, and application softwares with higher update frequencies such as individual App are respectively divided into a single virtual network function module, that is, Each virtual network function module runs an APP.
  • the method may include:
  • the NM sends a first load request message to the NFVO, where the first load request message includes an image file of a part of the virtual network function module of the VNF unit, where the first load request message is used to request the NFVO to load the image file.
  • the part of the virtual network function module is one or at least two virtual network function modules. Therefore, when a single or at least two virtual network function modules in the VNF unit need to be updated, the solution of the embodiment of the present invention may be adopted. Only the single or at least two virtual network function modules are loaded, thereby preventing other virtual network function modules in the VNF unit from being repeatedly loaded.
  • the NM may also send a descriptor of the partial virtual network function module to the NFVO, where the descriptor is used to describe deployment information and maintenance information of the part of the virtual network function module.
  • the descriptor may be included in the first loading request message, and the image file The NFVO is sent to the NFVO, or the descriptor may be included in the second load request message, and the second load request message is used to request the NFVO unit to load the descriptor.
  • the first loading request message or the second loading request message may further include an identifier of the descriptor; or, after receiving the descriptor, the NFVO unit may allocate an identifier of the descriptor for the descriptor.
  • the NFVO loading the image file may save the image file to a pre-specified storage area, so that the NFVO may then initiate the NFV instantiation operation or initiate the NFV expansion and contraction operation.
  • the first image file is called in the storage area.
  • the VNF expansion and contraction operation includes a VNF scale out operation and a VNF scale in.
  • the NFVO may also load the descriptors described above, or the NFVO may also load the identifiers of the descriptors and descriptors described above.
  • the NFVO may also send a first load response message to the NM to notify the NFVO that the image file is successfully loaded.
  • NFVO may also update, query, or delete the above image files and/or descriptors.
  • the NFVO may receive a first management request message from the NM, where the first management request message is used to instruct the NFVO to update, query, or delete the image file; and then the NFVO updates, queries, or deletes the image file.
  • the NFVO may receive a second management request message from the NM, where the second management request message is used to instruct the NFVO to update, query, or delete the descriptor; and then the NFVO updates, queries, or deletes the descriptor.
  • the NFVO may receive a third management request message from the NM, where the third management request message is used to instruct the NFVO to update, query, or delete the image file and the descriptor; and then the NFVO updates the image file and the descriptor, Query or delete.
  • the part of the virtual network can be called from the specified storage area.
  • the function module image file and the part of the virtual network function module descriptor are the functions module image file and the part of the virtual network function module descriptor.
  • NFVO when NFVO initiates a VNF instantiation operation, NFVO can The VNFM sends an instantiation request message, where the instantiation request message carries an identifier of a descriptor of all virtual network function modules of the VNF unit, and the identifier of the descriptor of the entire virtual network function module is used for instantiation of the VNF unit.
  • the VNF is divided into a first virtual network function module, a second virtual network function module, and a third virtual network function module, where the descriptor of the first virtual network function module is a first descriptor, and the image file is The first image file, the descriptor of the second virtual network function module is a second descriptor, the image file is a second image file, the descriptor of the third virtual network function module is a third descriptor, and the image file is a third image file. .
  • the NFVO When the NFVO initiates the VNF instantiation operation, the NFVO sends an instantiation request message to the VNFM, where the instantiation request message carries the identifier of the first descriptor, the identifier of the second descriptor, and the identifier of the third descriptor. Therefore, after receiving the instantiation request message, the VNFM may invoke the first descriptor and the first image file according to the identifier of the first descriptor, and invoke the second descriptor and the second image file according to the identifier of the second descriptor. And the third descriptor and the third image file are invoked according to the identifier of the third descriptor, and the virtual resource deployment and the software installation are performed according to the parameters in the respective descriptors to complete instantiation of the VNF unit.
  • the NFVO when the NFVO sends a VNF expansion and contraction operation, the NFVO sends a capacity expansion request message or a volume reduction request message to the VNFM, where the contention request message or the contention request message includes the descriptor of the part of the virtual network function module.
  • the identifier of the part of the virtual network function module is used for expansion or contraction of the part of the virtual network function module.
  • the expansion request message includes an identifier of the first descriptor, where the expansion request message is used to instruct the VNFM to perform a capacity expansion operation on the VNF unit, and after receiving the expansion request message, the VNFM may invoke the identifier according to the identifier of the first descriptor.
  • a descriptor and a first image file complete the deployment of the first virtual network function module, thereby completing the expansion operation of the VNF unit.
  • the NFVO can redeploy a specified part of the virtual network function module in the VNF unit without redeploying the entire VNF unit.
  • the NFVO may perform an independent loading operation on the image file instead of the usual processing manner for the entire VNF.
  • Package execution load operation from However, when only the image file of some virtual network function modules of the VNF unit needs to be loaded, the image files of other virtual network function modules in the VNF unit are also reloaded.
  • a part of the virtual network function module of the VNF unit may have a corresponding descriptor, and the descriptor is used to describe deployment information and maintenance of the part of the virtual network function module.
  • the information may include, for example, parameter information of a connection resource, a virtual interface, a storage resource, a computing resource, and the like, which are required for deploying the part of the virtual network function module, and the NFVO may instantiate the part of the virtual network function module according to the descriptor. Or expand and shrink. It can be understood that NFVO needs to load the descriptor before using the descriptor to instantiate or expand the partial virtual network function module.
  • the NFVO may receive the above-mentioned image files and descriptors together, or may separately receive the above-mentioned image files and descriptors. These two cases are described below in conjunction with FIG. 3 and FIG. 4 respectively.
  • FIG. 3 shows another loading method provided by an embodiment of the present invention, wherein the NFVO can receive the image files and descriptors of the part of the virtual network function module together.
  • the same or similar content as the method shown in FIG. 2 can be referred to the detailed description in FIG. 2, and details are not described herein.
  • the method may include:
  • the NM sends a first load request message to the NFVO, where the first load request message includes an image file of a part of the virtual network function module of the VNF unit and a descriptor of the part of the virtual network function module.
  • the foregoing S302 and S303 may also be combined into one step.
  • the foregoing S302 and S303 may be replaced by step S304, where step S304 is: NFVO loads the image file and the descriptor.
  • the NFVO loads the image file and the descriptor to save the image file and the descriptor to a pre-specified storage area, so that the NFVO can call the image from the storage area in subsequent use. File and the descriptor.
  • the first load request message includes an image file and a descriptor of the part of the virtual network function module, that is, the first load request message includes the package corresponding to the part of the virtual network function module, when NFVO After receiving the first loading request message, the packet corresponding to the part of the virtual network function module may be loaded.
  • the NFVO may perform independent loading operations on the packets corresponding to the partial virtual network function modules, instead of following the usual processing manner. Performing a load operation on the entire VNF package, thereby avoiding mirror files or descriptors of other virtual network function modules in the VNF unit when only the image files and/or descriptors of the virtual network function modules need to be loaded. Was reloaded.
  • the first loading request message may further include an identifier of the descriptor, and the identifier of the descriptor may be allocated by the NM for the descriptor, or may be pre-configured.
  • the identifier of the descriptor may be set in the descriptor as a parameter of the descriptor, or may be independent of the descriptor.
  • the NFVO may load the identifier of the descriptor and the descriptor.
  • the identifier of the descriptor and the corresponding relationship of the descriptor may be saved to a specified storage area, so that the NFVO can perform the VNF unit instantiation operation or initiate the VNF unit expansion and contraction operation according to the identifier of the descriptor.
  • a descriptor corresponding to the identifier of the descriptor is called in the storage area.
  • the identifier of the descriptor may also be allocated by the NFVO.
  • the NFVO may first assign an identifier of the descriptor to the descriptor, and then load the descriptor and the identifier of the descriptor.
  • the NFVO can send a first load response message to the NM to notify the image file and the descriptor is successfully loaded.
  • the NFVO may send the identifier allocated by the NFVO to the descriptor to be sent to the NM in the first loading response message, or the NFVO may also carry the identifier of the descriptor in another message and send it to the NM, so that the NM
  • the identifier of the descriptor is known, so that the NM can initiate the instantiation operation of the VNF unit or initiate the expansion and contraction operation of the VNF unit by using the identifier of the descriptor.
  • FIG. 3 shows a case where the NFVO receives the above-mentioned image file and descriptor together, and the case where the above-mentioned image file and descriptor are separately received will be described below with reference to FIG.
  • the method shown in FIG. 4 may be implemented after the method shown in FIG. 2 is performed.
  • the method may include:
  • the NM sends a second load request message to the NFVO, where the second load request message includes a descriptor of a part of the virtual network function module of the VNF unit.
  • the NFVO when it is required to update the deployment mode of a part of the virtual network function module of the VNF unit, the NFVO can perform independent loading operations on the descriptors of the part of the virtual network function module, instead of following the usual processing manner, the VNF The package performs the loading operation, thereby avoiding the deployment mode of other virtual network function modules in the VNF being repeatedly loaded when only the deployment mode of the part of the virtual network function module of the VNF unit needs to be updated.
  • step S202 may be merged into step S402 for execution, that is, after the NFVO receives the first load request message and the second load request message, The above image file and the descriptor are loaded.
  • the second loading request message further includes an identifier of the descriptor, and the identifier of the descriptor may be allocated by the NM for the descriptor, or may be pre-configured.
  • the NFVO can perform the identifier of the descriptor and the descriptor.
  • the identifier of the descriptor may also be allocated by the NFVO.
  • the NFVO may first load the identifier of the descriptor for the descriptor, and then load the descriptor and the identifier of the descriptor.
  • the NFVO may send a first load response message to the NM to notify the image file and the descriptor is successfully loaded. If the NFVO also assigns an identifier to the descriptor, the NFVO may carry the identifier of the descriptor in the first load response message or other messages to the NM, so that the NM knows the identifier of the descriptor, so that the NM can adopt The identifier of the descriptor initiates a VNF unit instantiation operation or initiates a VNF unit expansion and contraction operation.
  • the NFVO may also perform management operations such as updating, querying, or deleting the image file and/or the descriptor. For example, after performing the method shown in at least one of FIGS. 1 to 3, the method shown in FIG. 5 or FIG. 6 can also be performed.
  • FIG. 5 shows a management method, and the method shown in FIG. 5 may include:
  • the NFVO receives a first management request message from the NM, where the first management request message is used to instruct the NFVO to update, query, or delete the image file.
  • the NM may instruct the NFVO to perform an independent management operation on the image file of the part of the virtual network function module by using the first management request message to avoid
  • the entire VNF package is updated due to the update or deletion of the image file of the part of the virtual network function module, so that the image files of other virtual network function modules in the VNF unit are reloaded, which greatly reduces network maintenance. The amount of work.
  • NFVO can perform independent management operations on the image file.
  • the NFVO may perform an independent management operation on the descriptor, as shown in FIG. 5, the method may further include:
  • the NFVO receives a second management request message from the NM, where the second management request message is used to instruct the NFVO to update, query, or delete the descriptor.
  • the NFVO can perform independent management operations on the descriptor, thereby avoiding the usual processing method, because the part of the virtual network function module needs to be redeployed or deleted,
  • the VNFD of the VNF unit in which the part of the virtual network function module is located is updated, which causes the entire VNF unit to be redeployed, thereby greatly reducing the workload and risk of network maintenance.
  • the method shown in FIG. 5 may include only S501 and S502, or may include only S503 and S504, or may include S501 to S504.
  • Figure 6 shows another management method.
  • the method shown in Figure 6 can include:
  • the NFVO receives a third management request message from the NM, where the third management request message is used to instruct the NFVO to update, query, or delete the image file and the descriptor.
  • the NM can pass the third management request.
  • the message indicates that the NFVO performs independent management operations on the packets corresponding to the virtual network function modules, thereby avoiding the usual processing method, and the part of the virtual network function module needs to perform related management operations, thereby causing management operations on the entire VNF package.
  • related management operations are required for the entire VNF unit, thereby greatly reducing the workload and risk of network maintenance.
  • NFVO and NM include corresponding hardware structures and/or software modules for performing various functions in order to implement the above functions.
  • Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module into NFVO or NM according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module 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. 7 shows a possible structural diagram of the NFVO involved in the above embodiment.
  • the NFVO includes a processing module 10 and a communication module 11.
  • the processing module 10 is configured to control and manage the actions of the NFVO.
  • the processing module 10 is configured to support the NFVO to perform the process S202 in FIG. 2, the processes S302 and S303 in FIG. 3, the process S402 in FIG. 4, and the process in FIG. Processes S502 and S504, and process S602 in FIG. 6, And/or other processes for the techniques described herein.
  • Communication module 11 is used to support communication of NFVO with other network entities, such as with the functional modules or network entities shown in FIG.
  • the NFVO may also include a storage module 12 for storing program code and data of the NFVO.
  • the processing module 10 may be a processor or a controller, 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 at least two microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 11 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 12 can be a memory.
  • the processing module 10 is a processor
  • the communication module 11 is a communication interface
  • the storage module 12 is a memory
  • the NFVO involved in the embodiment of the present invention may be the NFVO shown in FIG.
  • the NFVO includes a processor 20, a communication interface 21, a memory 22, and a bus 23.
  • the communication interface 21, the processor 20, and the memory 22 are connected to each other through a bus 23.
  • the bus 23 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 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 8, but it does not mean that there is only one bus or one type of bus.
  • FIG. 9 shows a possible structural diagram of the NM involved in the above embodiment.
  • the NM includes a processing module 30 and a communication module 31.
  • the processing module 30 is configured to control and manage the action of the NM.
  • the processing module 20 is configured to support the NM to perform the process S201 in FIG. 2, the process S301 in FIG. 3, the process S401 in FIG. 4, and the process S501 in FIG. And S503, and process S601 in FIG. 6, and/or other processes for the techniques described herein.
  • the communication module 31 is used to support communication between the NM and other network entities, such as with the functional modules or network entities shown in FIG.
  • the NM may also include a storage module 32 for storing program code and data of the NM.
  • the processing module 30 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a 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 module 31 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 32 can be a memory.
  • the processing module 30 is a processor
  • the communication module 31 is a communication interface
  • the storage module 32 is a memory
  • the NM involved in the embodiment of the present invention may be the NM shown in FIG.
  • the NM includes a processor 40, a communication interface 41, a memory 42, and a bus 43.
  • the communication interface 41, the processor 40, and the memory 42 are connected to each other through a bus 43.
  • the bus 43 may be a PCI bus or an EISA bus or the like.
  • the bus 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 FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in NFVO or NM. Of course, the processor and the storage medium can also exist as discrete components in NFVO or NM.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

本发明实施例提供一种加载方法及装置,涉及通信技术领域。该方法包括:NFVO单元从NM单元接收第一加载请求消息,所述第一加载请求消息中包括VNF单元的部分虚拟网络功能模块的镜像文件,所述第一加载请求消息用于请求所述NFVO加载所述镜像文件;所述NFVO单元对所述镜像文件进行加载。本发明实施例的方案能够避免,当只需要对部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。

Description

一种加载方法及装置 技术领域
本发明涉及通信技术领域,尤其涉及一种加载方法及装置。
背景技术
当前的通信业务蓬勃发展,而通信网络的虚拟化更是加快了通信业务的发展速度。相对传统通信业务,运营商不得不面对动态变化的市场和差异化的新需求。在这种背景下,网络功能虚拟化(Network Function Virtualization,NFV)技术被提出,其中,NFV技术是一种在通用物理设备上运行网络功能的技术。
在NFV环境下,传统的物理网元映射为虚拟网络功能(Virtualized Network Function,VNF)单元。目前,针对一个VNF单元的操作对应于一个整体的VNF包(package)的操作。当仅需要针对该VNF单元中的子部分进行某些操作时,也需要对整个VNF包进行加载。这导致该VNF单元中的其他子部分在无需操作的情况下被重复加载,造成资源浪费。
发明内容
本发明的实施例提供一种加载方法及装置,用以避免VNF单元中的无需操作的子部分被重复加载。
一方面,本发明实施例提供一种加载方法。该方法包括:NFVO单元从NM单元接收第一加载请求消息,该第一加载请求消息中包括虚拟网络功能VNF单元的部分虚拟网络功能模块的镜像文件,该第一加载请求消息用于请求该NFVO单元加载该镜像文件;该NFVO单元对该镜像文件进行加载。可选地,NFVO单元还可以向NM单元发送第一加载响应消息,第一加载响应消息用于通知该镜像文件加载成功。
通过本发明实施例提供的方案,当需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,NFVO单元可以对该镜像文件进行独立 的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。
在一种可能的设计中,第一加载请求消息中还可以包括部分虚拟网络功能模块的描述符,该描述符用于描述该部分虚拟网络功能模块的部署信息和维护信息,该加载方法还可以包括:该NFVO单元对该描述符进行加载。
在这种可能的设计中,VNF单元的某一部分虚拟网络功能模块对应一个包,包括该部分虚拟网络功能模块的镜像文件和描述符,当需要对VNF单元的部分虚拟网络功能模块的镜像文件和/或描述符进行加载时,NFVO可以对该部分虚拟网络功能模块对应的包进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对该部分虚拟网络功能模块的镜像文件和/或描述符进行加载时,VNF单元中的其他虚拟网络功能模块的镜像文件或描述符也被重新加载。
在一种可能的设计中,该加载方法还可以包括:NFVO单元从NM单元接收第二加载请求消息,该第二加载请求消息中包括部分虚拟网络功能模块的描述符,该描述符用于描述该部分虚拟网络功能模块的部署信息和维护信息,该第二加载请求消息用于请求该NFVO单元加载该描述符;该NFVO单元对该描述符进行加载。可选的,NFVO单元还可以向NM单元发送第二加载响应消息,该第二加载响应消息用于通知该描述符加载成功。
通过这种可能的设计,NFVO单元也可以对部分虚拟网络功能模块的描述符进行独立的加载操作,从而避免了当只需要对VNF单元的部分虚拟网络功能模块的部署方式进行更新时,VNF单元中其他虚拟网络功能模块的部署方式被重复加载。
在一种可能的设计中,第一加载请求消息或第二加载请求消息还可以包括描述符的标识,该NFVO单元可以对该描述符和该描述符的标识进行加载。
在一种可能的设计中,NFVO单元还可以为描述符分配该描述符的标识;该NFVO单元可以对该描述符和该描述符的标识进行加载。可选的,NFVO单元还可以将NFVO单元该描述符的标识携带在第一加载响应消息中发送至NM单元,或者,NFVO单元也可以将该描述符的标识携带在其他消息中发送至NM单元,以使得NM单元获知该描述符的标识。
在一种可能的设计中,该加载方法还可以包括:NFVO单元从NM单元接收第一管理请求消息,该第一管理请求消息用于指示该NFVO单元对该镜像文件进行更新、查询或者删除;该NFVO单元对该镜像文件进行更新、查询或者删除。
在这种可能的设计中,NFVO单元能够对VNF单元中的部分虚拟网络功能模块的镜像文件进行独立的管理操作,避免了通常处理方式中由于该部分虚拟网络功能模块的镜像文件的更新或者删除,使得整个VNF包被更新,从而导致VNF单元中其他虚拟网络功能模块的镜像文件被重新加载,大大降低了网络维护的工作量。
在一种可能的设计中,该加载方法还可以包括:NFVO单元从NM单元接收第二管理请求消息,该第二管理请求消息用于指示该NFVO对该描述符进行更新、查询或者删除;该NFVO单元对该描述符进行更新、查询或者删除。
在这种可能的设计中,NFVO单元能够对VNF单元中的部分虚拟网络功能模块的描述符进行独立的管理操作,从而避免了通常处理方法中,由于该部分虚拟网络功能模块需要重新部署或者删除,使得该部分虚拟网络功能模块所在的VNF单元的VNFD被更新,从而导致整个VNF单元都需要重新部署的问题,从而大大降低了网络维护的工作量以及风险。
在一种可能的设计中,该加载方法还可以包括:NFVO单元从NM单元接收第三管理请求消息,该第三管理请求消息用于指示该NFVO单元对该镜像文件和该描述符进行更新、查询或者删除;该NFVO单元对该镜像文件和该描述符进行更新、查询或者删除。
在这种可能的设计中,当VNF单元的部分虚拟网络功能模块需要进行相关管理操作时,例如,应用软件需要更新,部署方式需要更新,或者 该部分虚拟网络功能模块需要删除等,NFVO单元对该部分虚拟网络功能模块对应的包进行独立的管理操作,从而避免了通常处理方法中,由于该部分虚拟网络功能模块需要进行相关的管理操作,而导致对整个VNF包进行管理操作,从而导致对整个VNF单元都需要进行相关的管理操作,从而大大降低了网络维护的工作量以及风险。
在一种可能的设计中,该加载方法还可以包括:NFVO单元向VNFM单元发送实例化请求消息,该实例化请求消息中包括该VNF单元的全部虚拟网络功能模块的描述符的标识,该全部虚拟网络功能模块的描述符的标识用于该VNF单元的实例化。
在一种可能的设计中,该加载方法还可以包括:NFVO单元向VNFM单元发送扩容请求消息或缩容请求消息,该扩容请求消息或该缩容请求消息中包括该部分虚拟网络功能模块的描述符的标识,该部分虚拟网络功能模块的描述符的标识用于该部分虚拟网络功能模块的扩容或缩容。可见,基于该可能的设计,在VNF单元的扩缩容过程中,NFVO单元可以对VNF单元中的指定部分虚拟网络功能模块进行重新部署,而不需要对整个VNF单元进行重新部署。
另一方面,本发明实施例提供另一种加载方法。该方法包括:NM单元向NFVO单元发送第一加载请求消息,该第一加载请求消息中包括虚拟网络功能VNF单元的部分虚拟网络功能模块的镜像文件,该第一加载请求消息用于请求该NFVO单元加载该镜像文件。可选的,NM单元还可以从NFVO单元接收第一加载响应消息,该第一加载响应消息用于通知该镜像文件加载成功。
通过本发明实施例提供的加载方案,当需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,NM单元可以通过第一加载请求消息,指示NFVO单元对该镜像文件进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。
在一种可能的设计中,第一加载请求消息可以还包括部分虚拟网络 功能模块的描述符,以使得NFVO单元接收到该第一加载请求消息后,加载该描述符。
在一种可能的设计中,该加载方法还可以包括:NM单元向NFVO单元发送第二加载请求消息,该第二加载请求消息中包括部分虚拟网络功能模块的描述符,该描述符用于描述该部分虚拟网络功能模块的部署信息和维护信息,该第二加载请求消息用于请求该NFVO单元加载该描述符。可选的,NM单元还可以从NFVO单元接收第二加载响应消息,该第二加载响应消息用于通知该描述符加载成功。
在一种可能的设计中,第一加载请求消息或第二加载请求消息还可以包括描述符的标识,以使得NFVO单元接收到该第一加载请求消息或第二加载请求消息后对该描述符的标识进行加载。
在一种可能的设计中,NM单元还可以从NFVO单元接收描述符的标识,该描述符的标识为NFVO分配的。
在一种可能的设计中,该加载方法还可以包括:NM单元向NFVO单元发送第一管理请求消息,该第一管理请求消息用于指示该NFVO单元对该镜像文件进行更新、查询或者删除。
在一种可能的设计中,该加载方法还可以包括:NM单元向NFVO单元发送第二管理请求消息,该第二管理请求消息用于指示该NFVO对该描述符进行更新、查询或者删除。
在一种可能的设计中,该加载方法还可以包括:NM单元向NFVO单元发送第三管理请求消息,该第三管理请求消息用于指示该NFVO单元对该镜像文件和该描述符进行更新、查询或者删除。
又一方面,本发明实施例提供了一种NFVO单元,该NFVO单元可以实现上述方面所涉及方法中NFVO单元所执行的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中,该NFVO单元的结构中包括处理器和通信接口,该处理器被配置为支持该NFVO单元执行上述方法中相应的功能。该通信接口用于支持该NFVO单元与其他网元之间的通信。该NFVO单 元还可以包括存储器,该存储器用于与处理器耦合,其保存该NFVO单元必要的程序指令和数据。
又一方面,本发明实施例提供了一种NM单元,该NM可以实现上述方面所涉及方法实施例中NM单元所执行的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中,该NM单元的结构中包括处理器和通信接口,该处理器被配置为支持该NM单元执行上述方法中相应的功能。该收发器用于支持该NM单元与其他网元之间的通信。该NM单元还可以包括存储器,该存储器用于与处理器耦合,其保存该NM单元必要的程序指令和数据。
又一方面,本发明实施例提供了一种通信系统,该系统包括上述方面所述的NFVO单元和NM单元。
再一方面,本发明实施例提供了一种计算机存储介质,用于储存为上述NFVO单元所用的计算机软件指令,其包含用于执行上述方面所设计的程序。
再一方面,本发明实施例提供了一种计算机存储介质,用于储存为上述NM单元所用的计算机软件指令,其包含用于执行上述方面所设计的程序。
相较于现有技术,本发明实施例提供的方案中,当需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,NFVO单元可以对该镜像文件进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见 地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种基于NFV的网络架构图;
图2为本发明实施例提供的一种加载方法的通信示意图;
图3为本发明实施例提供的另一种加载方法的通信示意图;
图4为本发明实施例提供的又一种加载方法的通信示意图;
图5为本发明实施例提供的一种管理方法的通信示意图;
图6为本发明实施例提供的另一种管理方法的通信示意图;
图7为本发明实施例提供的一种NFVO的结构示意图;
图8为本发明实施例提供的另一种NFVO的结构示意图;
图9为本发明实施例提供的一种NM的结构示意图;
图10为本发明实施例提供的另一种NM的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案,并不构成对本发明实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本发明实施例提供的技术方案对于类似的技术问题,同样适用。
图1示出了一种基于NFV的网络架构。如图1所示,该网络架构包括网络功能虚拟化调度(Network Functions Virtualization Orchestrator,NFVO)单元、虚拟网络功能管理(Virtualized Network Function Manager,VNFM)单元、虚拟基础设施管理(Virtualized Infrastructure Manager,VIM)单元、运营支撑系统(Operations Support System,OSS)或业务支撑系统(Business Support System,BSS)、网元管理(Element Manager,EM)单元、VNF单元、虚拟网络功能基础设施(Network Function Virtualization Infrastructure,NFVI)。其中,上述NFVO单元也可以称为 网络功能虚拟化编排单元,上述OSS/BSS也可以称为网络管理(Network Manager,NM)单元。
为描述方便,图1中的各个单元也可以仅以其英文缩写进行描述,例如,NFVO单元可以描述为NFVO,VNF单元可以描述为VNF,其他单元类似,不再赘述。在图1所示的网络架构中,NFVO、VNFM以及VIM构成了NFV系统的管理编排(Management and Orchestration,MANO)域。
下面对上述各个单元进行简单介绍:
EM为一个或至少两个VNF进行功能配置、故障管理、功能使用情况的记录、性能统计、安全管理等。
VNF是虚拟化的逻辑网元,如电信分组领域的SGSN、MME、GGSN、SGW、PGW等,每种网元都可独立部署,呈现为一个VNF。
NFVI为VNF提供硬件资源和虚拟化资源及其管理,以及虚拟化运行环境。
NFVO负责网络业务(Network Service,NS)的生命周期管理,且能够通过指示VIM对NFVI的资源进行编排。
VNFM负责VNF的生命周期管理,每个VNF都有一个关联的VNFM。一个VNFM可能管理一个VNF,也可能管理多个相同类型甚至不同类型的VNF。
VIM负责控制和管理VNFI基础设施中的资源,包括:计算资源、存储资源、网络资源等等,通常这些资源是一个运营商的基础设施。
需要说明的是,上述NFV系统中的任意一个功能单元可能分布在一个实体设备上,也可能分布在多个实体设备上,NFV系统中的多个功能单元可能分别分布在不同的实体设备上,也可能都分布在同一个实体设备上。可以理解的是,NFV系统中的任意一个功能单元都可能是实体设备内的一个逻辑功能模块,也可能是由多个实体设备组成的一个逻辑功能模块。
因此,在本发明实施例中,可以由一个实体设备执行本发明实施例提供的方法中的各个步骤,可以由多个实体设备协作执行本发明实施例提 供的方法中的各个步骤,对此本发明不做限定。
在本发明实施例中,NFV系统可以应用于长期演进(Long Term Evolution,LTE)通信系统中,也可以应用于LTE-A(Long Term Evolution Advanced)系统、第五代(5th Generation,5G)通信系统或未来可能出现的其他系统中,还可以应用于WCDMA等第三代(3rd-Generation,3G)通信系统中等,本发明不作限制。
需要说明的是,在本发明实施例中,术语“第一”、“第二”、“第三”仅用于描述目的,用于区分不同的描述对象,而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。
下面将基于上面所述的本发明实施例涉及的共性方面,对本发明实施例进一步详细说明。
目前,针对一个VNF单元的操作对应于一个整体的VNF包的操作。该VNF包中可以包括一个用于描述该VNF单元的部署和维护的模板的虚拟网络功能描述符(VNF Descriptor,VNFD)以及运行在该VNF单元上的各个软件的镜像文件,例如,不同应用(Application,App)的镜像文件,和为应用提供运行环境的虚拟机软件或者系统软件的镜像文件等。当需要更新某个软件时,需要将该软件更新后的镜像文件,替换该VNF包中对应的镜像文件,然后重新加载更新后的整个VNF包以将原本保存的VNF包覆盖,从而导致无需进行更改的其他镜像文件被重复加载。例如,应用软件相比于虚拟机软件或者系统软件具有更高的更新频率,每当有一个应用软件需要更新时,虚拟机软件或者系统软件的镜像文件也都被重新加载。
有鉴于此,本发明的一个实施例提供一种加载方法,和基于这个方法的NFVO,NM及系统。NFVO从NM接收第一加载请求消息,该第一加载请求消息中包括VNF单元的部分虚拟网络功能模块的镜像文件,第一加载请求消息用于请求NFVO加载该镜像文件;NFVO对该镜像文件进行加载。可选地,NFVO还可以向NM发送第一加载响应消息,第一加载响应消息用于通知该镜像文件加载成功。可以理解的是,上述部分虚拟网络功能模块可以是一个或至少两个虚拟网络功能模块,本发明实施例不 限定该部分虚拟网络功能模块的数量。
通过本发明实施例提供的方案,当需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,NFVO可以对该镜像文件进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。
需要说明的是,在本发明实施例中,可以预先根据实际需要,将VNF单元划分为多个虚拟网络功能模块。例如,将VNF单元中比较稳定的软件模块划分为一个虚拟网络功能模块,将各个更新频率较高的软件模块分别划分为一个虚拟网络功能模块,也可以按照VNF单元中的软件的类型进行划分,一个虚拟网络功能模块包括一个或者一类软件。其中,上述虚拟网络功能模块也可以称为虚拟网络功能组件(VNF Component,VNFC)。
示例性的,可以将虚拟机软件和系统软件等比较稳定的软件模块划分在一个虚拟网络功能模块中,将各个App等更新频率较高的应用软件分别划分在一个单独的虚拟网络功能模块,即每个虚拟网络功能模块运行一个APP。
下面结合附图2对本发明实施例提供的方案进行说明。如图2所示,该方法可以包括:
S201、NM向NFVO发送第一加载请求消息,该第一加载请求消息中包括VNF单元的部分虚拟网络功能模块的镜像文件,该第一加载请求消息用于请求NFVO加载该镜像文件。
在一个示例中,上述部分虚拟网络功能模块为一个或至少两个虚拟网络功能模块,因此,当VNF单元中的单个或至少两个虚拟网络功能模块需要更新时,通过本发明实施例的方案可以仅对该单个或至少两个虚拟网路功能模块进行加载,从而避免VNF单元中的其他虚拟网路功能模块被重复加载。
在一个示例中,NM还可以向NFVO发送该部分虚拟网络功能模块的描述符,该描述符用于描述该部分虚拟网路功能模块的部署信息和维护信息。例如该描述符可以包含在上述第一加载请求消息中,和该镜像文件 一并发送至NFVO,或者,该描述符可以包含在第二加载请求消息中进行发送,该第二加载请求消息用于请求NFVO单元加载该描述符。
在一个示例中,上述第一加载请求消息或第二加载请求消息中还可以包括上述描述符的标识;或者,NFVO单元接收上述描述符后,可以为该描述符分配描述符的标识。
S202、NFVO对该镜像文件进行加载。
在一个示例中,NFVO对该镜像文件进行加载可以为将该镜像文件保存到预先指定的存储区域中,以使得NFVO在后续发起NFV实例化操作或者发起NFV扩缩容操作时,即可从该存储区域中调用第一镜像文件。其中,VNF扩缩容操作包括VNF扩容(scale out)操作和VNF缩容(scale in)。
在一个示例中,NFVO还可以对上述描述符进行加载,或者,NFVO还可以对上述描述符和描述符的标识进行加载。
在一个示例中,NFVO成功加载该镜像文件后,NFVO还可以向NM发送第一加载响应消息,以通知NFVO该镜像文件加载成功。
在一个示例中,NFVO还可以对上述镜像文件和/或描述符进行更新、查询或者删除等。例如,NFVO可以从NM接收第一管理请求消息,第一管理请求消息用于指示NFVO对上述镜像文件进行更新、查询或者删除;然后,NFVO对该镜像文件进行更新、查询或者删除。又例如,NFVO可以从NM接收第二管理请求消息,第二管理请求消息用于指示NFVO对上述描述符进行更新、查询或者删除;然后,NFVO对该描述符进行更新、查询或者删除。又例如,NFVO可以从NM接收第三管理请求消息,第三管理请求消息用于指示NFVO对上述镜像文件和描述符进行更新、查询或者删除;然后,NFVO对该镜像文件和描述符进行更新、查询或者删除。
进一步的,当NFVO完成对VNF单元中的部分虚拟网络功能模块镜像文件和描述符的加载后,当NFVO执行VNF实例化操作或者VNF扩展操作时,即可从指定的存储区域调用该部分虚拟网络功能模块镜像文件和该部分虚拟网络功能模块描述符。
在一个示例中,当NFVO发起VNF实例化操作时,NFVO可以向 VNFM发送实例化请求消息,该实例化请求消息中携带该VNF单元的全部虚拟网络功能模块的描述符的标识,该全部虚拟网络功能模块的描述符的标识用于该VNF单元的实例化。
示例性的,假设VNF被划分为第一虚拟网络功能模块、第二虚拟网络功能模块和第三虚拟网络功能模块,其中,第一虚拟网络功能模块的描述符为第一描述符,镜像文件为第一镜像文件,第二虚拟网络功能模块的描述符为第二描述符,镜像文件为第二镜像文件,第三虚拟网络功能模块的描述符为第三描述符,镜像文件为第三镜像文件。当NFVO发起VNF实例化操作时,NFVO向VNFM发送实例化请求消息,该实例化请求消息中携带第一描述符的标识、第二描述符的标识以及第三描述符的标识。从而,当VNFM接收到该实例化请求消息后,即可根据第一描述符的标识调用第一描述符以及第一镜像文件,根据第二描述符的标识调用第二描述符以及第二镜像文件,根据第三描述符的标识调用第三描述符以及第三镜像文件,并根据各个描述符中的参数进行虚拟资源部署以及软件安装,以完成对VNF单元的实例化。
在一个示例中,当NFVO发送VNF扩缩容操作时,NFVO向VNFM发送扩容请求消息或缩容请求消息,该扩容请求消息或该缩容请求消息中包括该部分虚拟网络功能模块的描述符的标识,该部分虚拟网络功能模块的描述符的标识用于该部分虚拟网络功能模块的扩容或缩容。
例如,扩容请求消息中包括该第一描述符的标识,该扩容请求消息用于指示VNFM对VNF单元进行扩容操作,VNFM接收到该扩容请求消息后,即可根据第一描述符的标识调用第一描述符和第一镜像文件,完成对第一虚拟网络功能模块的部署,从而完成对VNF单元的扩容操作。
可以理解的是,在VNF单元的扩容和缩容过程中,NFVO可以对VNF单元中的指定部分虚拟网络功能模块进行重新部署,而不需要对整个VNF单元进行重新部署。
通过本发明实施例提供的方案,当需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,NFVO可以对该镜像文件进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从 而避免了当只需要对VNF单元的部分虚拟网络功能模块的镜像文件进行加载时,VNF单元中其他虚拟网络功能模块的镜像文件也被重新加载。
由上文描述可知,可选的,在本发明实施例中,VNF单元的某部分虚拟网络功能模块可以具备对应的描述符,该描述符用于描述该部分虚拟网络功能模块的部署信息和维护信息,例如可以包括部署该部分虚拟网络功能模块时所需的连接资源,虚拟接口、存储资源、计算资源等虚拟资源的参数信息,NFVO可以根据该描述符对该部分虚拟网络功能模块进行实例化或者扩缩容。可以理解的是,NFVO使用该描述符对该部分虚拟网络功能模块进行实例化或者扩缩容前,需要先加载该描述符。
对于上述部分虚拟网络功能模块的描述符,NFVO可以一并接收上述镜像文件和描述符,也可以分开接收上述镜像文件和描述符,下面结合图3和图4分别描述这两种情况。
在图2所示方法的基础上,图3示出了本发明实施例提供的另一种加载方法,其中,NFVO可以一并接收该部分虚拟网络功能模块的镜像文件和描述符。其中,图3所示方法中,与图2所示方法相同或类似的内容可以参考图2中的详细描述,此处不作赘述。,如图3所示,该方法可以包括:
S301、NM向NFVO发送第一加载请求消息,该第一加载请求消息中包括VNF单元的部分虚拟网络功能模块的镜像文件和该部分虚拟网络功能模块的描述符。
S302、NFVO对该镜像文件进行加载。
S303、NFVO对该描述符进行加载。
可选的,上述S302和S303也可以合为一个步骤,例如,上述S302和S303可以由步骤S304所替代,其中,步骤S304为:NFVO对该镜像文件和该描述符进行加载。
其中,NFVO对该镜像文件和该描述符进行加载可以为将该镜像文件和该描述符保存到预先指定的存储区域中,以使得NFVO在后续使用时,即可从该存储区域中调用该镜像文件和该描述符。
在本发明实施例中,可以为VNF单元的某一部分虚拟网络功能模块 设置一个对应的包,该第一加载请求消息中包括该部分虚拟网络功能模块的镜像文件和描述符,即可以理解为第一加载请求消息中包括该部分虚拟网络功能模块对应的包,当NFVO接收到该第一加载请求消息后,即可对该部分虚拟网络功能模块对应的包进行加载。
那么,当需要对VNF单元的部分虚拟网络功能模块的镜像文件和/或描述符进行加载时,NFVO可以对该部分虚拟网络功能模块对应的包进行独立的加载操作,而不是按照通常的处理方式,对整个VNF包执行加载操作,从而避免了当只需要对该部分虚拟网络功能模块的镜像文件和/或描述符进行加载时,VNF单元中的其他虚拟网络功能模块的镜像文件或描述符也被重新加载。
进一步的,第一加载请求消息中还可以包括该描述符的标识,该描述符的标识可以为NM为该描述符分配的,也可以为预先配置好的。
其中,该描述符的标识可以作为该描述符的参数设置在该描述符中,也可以独立于该描述符。从而,NFVO接收到该第一加载请求消息后,可以对该描述符的标识和该描述符进行加载。例如可以将该描述符的标识和该描述符的对应关系保存到指定的存储区域,以使得NFVO在进行VNF单元实例化操作或者发起VNF单元扩缩容操作时,能够根据该描述符的标识从该存储区域中调用与该描述符的标识对应的描述符。
可选的,在本发明实施例中,描述符的标识也可以由NFVO分配。在一个示例中,当NFVO接收到该第一加载请求消息后,NFVO可以先为该描述符分配该描述符的标识,进而对该描述符和该描述符的标识进行加载。
可以理解的是,当NFVO成功加载该镜像文件和该描述符后,NFVO可以向NM发送第一加载响应消息,以通知该镜像文件和该描述符加载成功。可选的,NFVO可以将NFVO为该描述符分配的标识携带在第一加载响应消息中发送至NM,或者,NFVO也可以将该描述符的标识携带在其他消息中发送至NM,以使得NM获知该描述符的标识,从而NM能够采用该描述符的标识发起VNF单元的实例化操作或者发起VNF单元的扩缩容操作。
上述图3示出了NFVO一并接收上述镜像文件和描述符的情况,下面结合图4描述分开接收上述镜像文件和描述符的情况。需要说明的是,图4所示的方法可以是在图2所示方法执行之后实施的,图2中的内容可以参见上面的描述,此处不作赘述。如图4所示,该方法可以包括:
S401、NM向NFVO发送第二加载请求消息,该第二加载请求消息中包括VNF单元的部分虚拟网络功能模块的描述符。
S402、NFVO对该描述符进行加载。
通过该方法,当需要对VNF单元的部分虚拟网络功能模块的部署方式进行更新时,NFVO可以对该部分虚拟网络功能模块的描述符进行独立的加载操作,而不是按照通常的处理方式,对VNF包执行加载操作,从而避免了当只需要对VNF单元的部分虚拟网络功能模块的部署方式进行更新时,VNF中其他虚拟网络功能模块的部署方式被重复加载。
可选的,在执行图2和图4所示方法的情况下,步骤S202可以合并到步骤S402中进行执行,即,NFVO在接收完第一加载请求消息和第二加载请求消息之后,再一并对上述镜像文件和该描述符进行加载。
进一步的,该第二加载请求消息中还包括该描述符的标识,该描述符的标识可以为NM为该描述符分配的,也可以为预先配置好的。当NFVO接收到该第二加载请求消息后,NFVO即可对该描述符的标识和该描述符进行。
可选的,在本发明实施例中,描述符的标识也可以由NFVO分配。在一个示例中,当NFVO接收到该第二加载请求消息后,NFVO可以先为该描述符分别该描述符的标识,进而对该描述符和该描述符的标识进行加载。
当NFVO成功加载该镜像文件和该描述符后,NFVO可以向NM发送第一加载响应消息,以通知该镜像文件和该描述符加载成功。若NFVO还为该描述符分配了标识,NFVO则可以将该描述符的标识携带在第一加载响应消息或者中其他消息中发送至NM,以使得NM获知该描述符的标识,从而NM能够采用该描述符的标识发起VNF单元实例化操作或者发起VNF单元扩缩容操作。
本发明实施例中,当NFVO对上述镜像文件和/或描述符进行加载之后,NFVO还可以对该镜像文件和/或描述符进行更新、查询或删除等管理操作。例如,在执行完图1至图3中至少一项所示的方法之后,还可以执行图5或图6所示的方法。
图5示出了一种管理方法,图5所示的方法可以包括:
S501、NFVO从NM接收第一管理请求消息,该第一管理请求消息用于指示NFVO对该镜像文件进行更新、查询或者删除。
S502、NFVO对该镜像文件进行更新、查询或者删除。
基于该方法,当VNF单元的部分虚拟网络功能模块中的软件需要更新或者删除时,NM可以通过第一管理请求消息,指示NFVO对该部分虚拟网络功能模块的镜像文件进行独立的管理操作,避免了通常处理方式中由于该部分虚拟网络功能模块的镜像文件的更新或者删除,使得整个VNF包被更新,从而导致VNF单元中其他虚拟网络功能模块的镜像文件被重新加载,大大降低了网络维护的工作量。
通过S501和S502,当VNF单元的部分虚拟网络功能模块的镜像文件加载完成后,NFVO可以对该镜像文件进行独立的管理操作。
可选的,当该部分虚拟网络功能模块的描述符加载完成后,NFVO也可以对该描述符进行独立的管理操作,如图5所示,该方法还可以包括:
S503、NFVO从NM接收第二管理请求消息,该第二管理请求消息用于指示NFVO对该描述符进行更新、查询或者删除。
S504、NFVO对描述符进行更新、查询或者删除。
那么,当该部分虚拟网络功能模块需要重新部署或者删除时,NFVO能够对该描述符进行独立的管理操作,从而避免了通常处理方法中,由于该部分虚拟网络功能模块需要重新部署或者删除,使得该部分虚拟网络功能模块所在的VNF单元的VNFD被更新,从而导致整个VNF单元都需要重新部署的问题,从而大大降低了网络维护的工作量以及风险。
需要说明的是,图5所示的方法可以仅包括S501和S502,或者,也可以仅包括S503和S504,或者,还可以是包括S501~S504。
图6示出了另一种管理方法。图6所示的方法可以包括:
S601、NFVO从NM接收第三管理请求消息,该第三管理请求消息用于指示NFVO对该镜像文件和该描述符进行更新、查询或者删除。
S602、NFVO对镜像文件和描述符进行更新、查询或者删除。
基于该方法,当VNF单元的部分虚拟网络功能模块需要进行相关管理操作时,例如,应用软件需要更新,部署方式需要更新,或者该部分虚拟网络功能模块需要删除等,NM可以通过第三管理请求消息指示NFVO对部分虚拟网络功能模块对应的包进行独立的管理操作,从而避免了通常处理方法中,由于该部分虚拟网络功能模块需要进行相关的管理操作,而导致对整个VNF包进行管理操作,从而导致对整个VNF单元都需要进行相关的管理操作,从而大大降低了网络维护的工作量以及风险。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是,NFVO、NM为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对NFVO或NM进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本发明实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用集成的单元的情况下,图7示出了上述实施例中所涉及的NFVO的一种可能的结构示意图。NFVO包括:处理模块10和通信模块11。处理模块10用于对NFVO的动作进行控制管理,例如,处理模块10用于支持NFVO执行图2中的过程S202,图3中的过程S302和S303,图4中的过程S402,图5中的过程S502和S504,以及图6中的过程S602, 和/或用于本文所描述的技术的其它过程。通信模块11用于支持NFVO与其他网络实体的通信,例如与图1中示出的功能模块或网络实体之间的通信。NFVO还可以包括存储模块12,用于存储NFVO的程序代码和数据。
其中,处理模块10可以是处理器或控制器,例如可以是中央处理器(Central Processing Unit,CPU),通用处理器,数字信号处理器(Digital Signal Processor,DSP),专用集成电路(Application-Specific Integrated Circuit,ASIC),现场可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或至少两个微处理器组合,DSP和微处理器的组合等等。通信模块11可以是收发器、收发电路或通信接口等。存储模块12可以是存储器。
当处理模块10为处理器,通信模块11为通信接口,存储模块12为存储器时,本发明实施例所涉及的NFVO可以为图8所示的NFVO。
参阅图8所示,该NFVO包括:处理器20、通信接口21、存储器22以及总线23。其中,通信接口21、处理器20以及存储器22通过总线23相互连接;总线23可以是外设部件互连标准(Peripheral Component Interconnect,PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture,EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图8中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
在采用集成的单元的情况下,图9示出了上述实施例中所涉及的NM的一种可能的结构示意图。NM包括:处理模块30和通信模块31。处理模块30用于对NM的动作进行控制管理,例如,处理模块20用于支持NM执行图2中的过程S201,图3中的过程S301,图4中的过程S401,图5中的过程S501和S503,以及图6中的过程S601,和/或用于本文所描述的技术的其它过程。通信模块31用于支持NM与其他网络实体的通信,例如与图1中示出的功能模块或网络实体之间的通信。NM还可以包括存储模块32,用于存储NM的程序代码和数据。
其中,处理模块30可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块31可以是收发器、收发电路或通信接口等。存储模块32可以是存储器。
当处理模块30为处理器,通信模块31为通信接口,存储模块32为存储器时,本发明实施例所涉及的NM可以为图10所示的NM。
参阅图10所示,该NM包括:处理器40、通信接口41、存储器42以及总线43。其中,通信接口41、处理器40以及存储器42通过总线43相互连接;总线43可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图10中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于随机存取存储器(Random Access Memory,RAM)、闪存、只读存储器(Read Only Memory,ROM)、可擦除可编程只读存储器(Erasable Programmable ROM,EPROM)、电可擦可编程只读存储器(Electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于NFVO或NM中。当然,处理器和存储介质也可以作为分立组件存在于NFVO或NM中。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机 可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式,对本发明的目的、技术方案和有益效果进行了进一步详细说明,所应理解的是,以上所述仅为本发明的具体实施方式而已,并不用于限定本发明的保护范围,凡在本发明的技术方案的基础之上,所做的任何修改、等同替换、改进等,均应包括在本发明的保护范围之内。

Claims (21)

  1. 一种加载方法,其特征在于,所述方法包括:
    网络功能虚拟化调度NFVO单元从网络管理NM单元接收第一加载请求消息,所述第一加载请求消息中包括虚拟网络功能VNF单元的部分虚拟网络功能模块的镜像文件,所述第一加载请求消息用于请求所述NFVO加载所述镜像文件;
    所述NFVO单元对所述镜像文件进行加载。
  2. 根据权利要求1所述的方法,其特征在于,所述第一加载请求消息中还包括所述部分虚拟网络功能模块的描述符,所述描述符用于描述所述部分虚拟网络功能模块的部署信息和维护信息,所述方法还包括:
    所述NFVO单元对所述描述符进行加载。
  3. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元从所述NM单元接收第二加载请求消息,所述第二加载请求消息中包括所述部分虚拟网络功能模块的描述符,所述描述符用于描述所述部分虚拟网络功能模块的部署信息和维护信息,所述第二加载请求消息用于请求所述NFVO单元加载所述描述符;
    所述NFVO单元对所述描述符进行加载。
  4. 根据权利要求2或3所述的方法,其特征在于,所述第一加载请求消息或所述第二加载请求消息还包括所述描述符的标识,所述NFVO单元对所述描述符进行加载,包括:
    所述NFVO单元对所述描述符和所述描述符的标识进行加载。
  5. 根据权利要求2或3所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元为所述描述符分配所述描述符的标识;
    所述NFVO单元对所述描述符进行加载,包括:
    所述NFVO单元对所述描述符和所述描述符的标识进行加载。
  6. 根据权利要求2至5任一项所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元从所述NM单元接收第一管理请求消息,所述第一管理请求消息用于指示所述NFVO单元对所述镜像文件进行更新、查询或者 删除;
    所述NFVO单元对所述镜像文件进行更新、查询或者删除。
  7. 根据权利要求2至6任一项所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元从所述NM单元接收第二管理请求消息,所述第二管理请求消息用于指示所述NFVO单元对所述描述符进行更新、查询或者删除;
    所述NFVO单元对所述描述符进行更新、查询或者删除。
  8. 根据权利要求2至5任一项所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元从所述NM单元接收第三管理请求消息,所述第三管理请求消息用于指示所述NFVO单元对所述镜像文件和所述描述符进行更新、查询或者删除;
    所述NFVO单元对所述镜像文件和所述描述符进行更新、查询或者删除。
  9. 根据权利要求2至8任一项所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元向虚拟网络功能管理VNFM单元发送实例化请求消息,所述实例化请求消息中包括所述VNF单元的全部虚拟网络功能模块的描述符的标识,所述全部虚拟网络功能模块的描述符的标识用于所述VNF单元的实例化。
  10. 根据权利要求2至8任一项所述的方法,其特征在于,所述方法还包括:
    所述NFVO单元向VNFM单元发送扩容请求消息或缩容请求消息,所述扩容请求消息或所述缩容请求消息中包括所述部分虚拟网络功能模块的描述符的标识,所述部分虚拟网络功能模块的描述符的标识用于所述部分虚拟网络功能模块的扩容或缩容。
  11. 一种网络功能虚拟化调度NFVO单元,其特征在于,包括:处理模块和通信模块,
    所述处理模块用于通过所述通信模块从网络管理NM单元接收第一加载请求消息,所述第一加载请求消息中包括虚拟网络功能VNF单元的部分虚拟网络功能模块的镜像文件,所述第一加载请求消息用于请求所述NFVO加载所述镜像文件;
    所述处理模块还用于对所述镜像文件进行加载。
  12. 根据权利要求11所述的NFVO单元,其特征在于,所述第一加载请求消息中还包括所述部分虚拟网络功能模块的描述符,所述描述符用于描述所述部分虚拟网络功能模块的部署信息和维护信息,所述处理模块还用于对所述描述符进行加载。
  13. 根据权利要求11所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块从所述NM单元接收第二加载请求消息,所述第二加载请求消息中包括所述部分虚拟网络功能模块的描述符,所述描述符用于描述所述部分虚拟网络功能模块的部署信息和维护信息,所述第二加载请求消息用于请求所述NFVO单元加载所述描述符;以及用于对所述描述符进行加载。
  14. 根据权利要求12或13所述的NFVO单元,其特征在于,所述第一加载请求消息或所述第二加载请求消息还包括所述描述符的标识,所述处理模块具体用于对所述描述符和所述描述符的标识进行加载。
  15. 根据权利要求12或13所述的NFVO单元,其特征在于,所述处理模块还用于为所述描述符分配所述描述符的标识;所述处理模块具体用于对所述描述符和所述描述符的标识进行加载。
  16. 根据权利要求12至15任一项所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块从所述NM单元接收第一管理请求消息,所述第一管理请求消息用于指示所述NFVO单元对所述镜像文件进行更新、查询或者删除;以及用于对所述镜像文件进行更新、查询或者删除。
  17. 根据权利要求12至16任一项所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块从所述NM单元接收第二管理请求消息,所述第二管理请求消息用于指示所述NFVO单元对所述描述符进行 更新、查询或者删除;以及用于对所述描述符进行更新、查询或者删除。
  18. 根据权利要求12至15任一项所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块从所述NM单元接收第三管理请求消息,所述第三管理请求消息用于指示所述NFVO单元对所述镜像文件和所述描述符进行更新、查询或者删除;以及用于对所述镜像文件和所述描述符进行更新、查询或者删除。
  19. 根据权利要求12至18任一项所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块向虚拟网络功能管理VNFM单元发送实例化请求消息,所述实例化请求消息中包括所述VNF单元的全部虚拟网络功能模块的描述符的标识,所述全部虚拟网络功能模块的描述符的标识用于所述VNF单元的实例化。
  20. 根据权利要求12至18任一项所述的NFVO单元,其特征在于,所述处理模块还用于通过所述通信模块向VNFM单元发送扩容请求消息或缩容请求消息,所述扩容请求消息或所述缩容请求消息中包括所述部分虚拟网络功能模块的描述符的标识,所述部分虚拟网络功能模块的描述符的标识用于所述部分虚拟网络功能模块的扩容或缩容。
  21. 一种通信系统,其特征在于,包括如权利要求11至20任一项所述的NFVO单元,以及网络管理NM单元。
PCT/CN2016/091089 2016-07-22 2016-07-22 一种加载方法及装置 WO2018014356A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2016/091089 WO2018014356A1 (zh) 2016-07-22 2016-07-22 一种加载方法及装置
US16/251,971 US20190155834A1 (en) 2016-07-22 2019-01-18 Loading Method and Apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/091089 WO2018014356A1 (zh) 2016-07-22 2016-07-22 一种加载方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/251,971 Continuation US20190155834A1 (en) 2016-07-22 2019-01-18 Loading Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2018014356A1 true WO2018014356A1 (zh) 2018-01-25

Family

ID=60993090

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/091089 WO2018014356A1 (zh) 2016-07-22 2016-07-22 一种加载方法及装置

Country Status (2)

Country Link
US (1) US20190155834A1 (zh)
WO (1) WO2018014356A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102033755A (zh) * 2009-09-30 2011-04-27 国际商业机器公司 用于运行虚拟机镜像的方法和系统
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
US20150358248A1 (en) * 2014-06-09 2015-12-10 Nokia Solutions And Networks Oy Controlling of virtualized network functions for usage in communication network
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization
WO2016107506A1 (zh) * 2014-12-31 2016-07-07 华为技术有限公司 虚拟网络加载方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102033755A (zh) * 2009-09-30 2011-04-27 国际商业机器公司 用于运行虚拟机镜像的方法和系统
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
US20150358248A1 (en) * 2014-06-09 2015-12-10 Nokia Solutions And Networks Oy Controlling of virtualized network functions for usage in communication network
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization
WO2016107506A1 (zh) * 2014-12-31 2016-07-07 华为技术有限公司 虚拟网络加载方法和装置

Also Published As

Publication number Publication date
US20190155834A1 (en) 2019-05-23

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
US10819592B2 (en) Slice instance management method and apparatus
US10924966B2 (en) Management method, management unit, and system
WO2020186911A1 (zh) 一种容器化虚拟网络功能vnf的资源管理方法及装置
US10965552B2 (en) Method and apparatus for managing virtualized network function
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
WO2018000197A1 (zh) 虚拟网络功能资源管理的方法和设备
WO2018171392A1 (zh) 一种虚拟机扩缩容方法及虚拟管理设备
WO2017161562A1 (zh) 网络功能虚拟化环境下应用的管理方法和装置
WO2020228377A1 (zh) 配置镜像内存的方法、装置及计算机存储介质
WO2020211652A1 (zh) 多租户场景下的租户资源管理方法和装置
EP3629160B1 (en) Method and device for managing vnf instantiation
KR20230069088A (ko) 컨테이너 클러스터 관리 방법 및 그 시스템
WO2020113817A1 (zh) 一种基于用户态协议栈的网络隔离方法和装置
WO2019109948A1 (zh) PaaS的管理方法、装置及存储介质
WO2022140945A1 (zh) 容器集群的管理方法和装置
US20220365822A1 (en) Data Processing Method and Computer Device
WO2018014356A1 (zh) 一种加载方法及装置
CN112015515A (zh) 一种虚拟网络功能的实例化方法及装置
CN113961319B (zh) 作业热迁移的方法、装置、电子设备及存储介质
WO2024027398A1 (zh) 一种通信方法和装置
WO2022141293A1 (zh) 一种弹性伸缩的方法及装置
CN113127145B (zh) 信息处理方法、装置以及存储介质
WO2022095027A1 (en) A method, device and system of container cluster scaling

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16909283

Country of ref document: EP

Kind code of ref document: A1