WO2021004320A1 - 服务资源许可管理方法和相关设备 - Google Patents

服务资源许可管理方法和相关设备 Download PDF

Info

Publication number
WO2021004320A1
WO2021004320A1 PCT/CN2020/098854 CN2020098854W WO2021004320A1 WO 2021004320 A1 WO2021004320 A1 WO 2021004320A1 CN 2020098854 W CN2020098854 W CN 2020098854W WO 2021004320 A1 WO2021004320 A1 WO 2021004320A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
life cycle
container
instance
management
Prior art date
Application number
PCT/CN2020/098854
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 华为技术有限公司
Publication of WO2021004320A1 publication Critical patent/WO2021004320A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • This application relates to the field of communication technology, in particular to a service resource license management method and related equipment.
  • Network function virtualization means that telecom network operators draw on virtualization technology in the field of information technology (IT, Information Technology), and integrate part of telecom network functions in common servers, switches, and storage devices.
  • IT information technology
  • core network function decouples software and hardware, so as to realize the rapid and efficient deployment and operation of network services (NS, Network Service), and at the same time, achieve the goal of saving network investment costs and operating costs.
  • NFV Network Function Virtualization
  • telecommunication network functions are implemented in software, and can be run on general-purpose server hardware, which can be migrated, instantiated, and deployed in different physical locations on the network as required, without the need to install new equipment.
  • the container as a service can be regarded as a specific type of platform as a service (PaaS, Platform as a Service) service, for example.
  • a container is an operating system-level virtualization technology that isolates different processes through operating system isolation technologies such as CGroup and NameSpace under Linux.
  • Container technology is different from hardware virtualization (Hypervisor) technology. There is no virtual hardware, and there is no operating system inside the container, only processes. Because of this important feature of container technology, containers are lighter and easier to manage than virtual machines.
  • a set of common management operations are defined, such as start, stop, pause, and delete, etc., to carry out unified life cycle management for the container.
  • containerized VNFs are service-oriented or micro-service-oriented.
  • industry has not yet proposed a service resource license management solution for containerized VNF instance lifecycle management.
  • the embodiment of the application provides a service resource license management method and related equipment.
  • the first aspect of the embodiments of the present application provides a service resource license management method, including:
  • the virtualized network function manager receives the life cycle management operation request of the containerized virtual network function (VNF, Virtualized Network Function) instance (the life cycle management operation request, for example, comes from the network function virtualization orchestrator Or network element management system, etc.).
  • the VNFM reads the service resources requested to be used by the containerized VNF instance in the life cycle management operation from a virtualized network function descriptor (VNFD, VNF Descriptor).
  • VNFD virtualized network function Descriptor
  • the VNFM sends a VNF life cycle operation permission request to the Network Function Virtualization Orchestrator (NFVO, Network Function Virtualization Orchestrator), and the VNF life cycle operation permission request carries the containerized VNF instance in the life cycle management operation The requested service resource.
  • the VNFM receives the VNF life cycle operation permission response from the NFVO.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the VNF life cycle management permission response may carry a success indication or a failure indication, for example.
  • the VNF lifecycle management permission response may also carry service resources permitted to be used by the containerized VNF instance licensed by the NFVO in the lifecycle management operation.
  • the service resources permitted to be used by the containerized VNF instance permitted by the NFVO in the life cycle management operation may be greater than or less than or equal to the containerized VNF carried in the VNF life cycle operation permission request The service resource requested by the instance in the life cycle management operation.
  • the method further includes:
  • the VNFM When the VNF life cycle management permission response carries a success indication, the VNFM sends a container object package management operation request to the container management platform CISM, and the management operation request carries the service resources of the container object package, and the container object package The service resources of does not exceed the service resources permitted by the containerized VNF instance permitted by the NFVO in the life cycle management operation.
  • the VNFM when the VNFM performs the lifecycle management operations of the containerized VNF instance, the VNFM first initiates a VNF lifecycle operation permission request to the VNFO to request the VNFO to license related service resources, and the NFVO will unify the life of the containerized VNF instance
  • the service resources used by the container objects in the cycle management operation are licensed, which is beneficial to avoid the service resources used by the member VNFs in the network service from exceeding the relevant preset quotas and forming service resource usage conflicts at the NS level, which is beneficial to the network service Effectively manage service resources used by containerized VNF instances from a perspective.
  • a second aspect of the embodiments of the present application provides a virtualized network function manager, including:
  • the receiving unit is configured to receive a life cycle management operation request of the containerized VNF instance (the life cycle management operation request comes from, for example, a network function virtualization orchestrator or a network element management system, etc.).
  • the reading unit is used to read the service resources requested by the containerized VNF instance in the life cycle management operation from the VNFD.
  • the sending unit sends a VNF life cycle operation permission request to the NFVO, where the VNF life cycle operation permission request carries the service resource requested by the containerized VNF instance in the life cycle management operation.
  • the VNFM receives the VNF life cycle operation permission response from the NFVO.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the VNF life cycle management permission response may carry a success indication or a failure indication, for example.
  • the VNF lifecycle management permission response may also carry service resources permitted to be used by the containerized VNF instance licensed by the NFVO in the lifecycle management operation.
  • the service resources permitted to be used by the containerized VNF instance permitted by the NFVO in the life cycle management operation may be greater than or less than or equal to the containerized VNF carried in the VNF life cycle operation permission request The service resource requested by the instance in the life cycle management operation.
  • the sending unit is further configured to: when the VNF life cycle management permission response carries a success indication, send a container object package management operation request to the container management platform CISM, the management operation request carrying all The service resources of the container object package. Wherein, the service resource of the container object package does not exceed the service resource permitted to be used by the containerized VNF instance permitted by the NFVO in the life cycle management operation.
  • the third aspect of the embodiments of the present application provides a service resource license management method, including:
  • the network function virtualization orchestrator NFVO receives a virtual network function VNF life cycle operation permission request from the virtual network function manager VNFM, wherein the VNF life cycle operation permission request carries a containerized VNF instance to request use in the life cycle management operation Service resources.
  • the NFVO sends a VNF life cycle operation permission response to the VNFM.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the VNF life cycle management permission response may carry a success indication or a failure indication, for example.
  • the VNF lifecycle management permission response may also carry service resources permitted to be used by the containerized VNF instance licensed by the NFVO in the lifecycle management operation.
  • the service resources permitted to be used by the containerized VNF instance permitted by the NFVO in the life cycle management operation may be greater than or less than or equal to the containerized VNF carried in the VNF life cycle operation permission request The service resource requested by the instance in the life cycle management operation.
  • the method may further include: the NFVO determining that the service resource requested by the containerized VNF instance in the life cycle management operation is related to the container The relationship between the service resources of the network service NS instance to which the VNF instance belongs;
  • the VNF life cycle operation permission response Can carry success instructions.
  • the VNF life cycle operation permission response may be Carry failure indication.
  • the service resource of the NS instance is, for example, the total number of container objects contained in all member VNF instances contained in the NS instance and/or container object packages called by all member nested NS instances.
  • the VNFM when the VNFM performs the lifecycle management operations of the containerized VNF instance, the VNFM first initiates a VNF lifecycle operation permission request to the VNFO to request the VNFO to license related service resources, and the NFVO will unify the life of the containerized VNF instance
  • the service resources used by the container objects in the cycle management operation are permitted, which makes it possible to avoid the service resources used by each member VNF in the network service from exceeding the relevant preset quotas and forming service resource usage conflicts at the NS level, which is beneficial to the network
  • the service perspective effectively manages the service resources used by the containerized VNF instance.
  • the fourth aspect of the embodiments of the present application provides a network function virtualization orchestrator NFVO, including:
  • the receiving unit is used to receive the virtual network function VNF life cycle operation permission request from the virtual network function manager VNFM.
  • the VNF life cycle operation permission request carries service resources requested by the containerized VNF instance in life cycle management operations.
  • the sending unit is used to send the VNF life cycle operation permission response to the VNFM.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the VNF life cycle management permission response may carry a success indication or a failure indication, for example.
  • the VNF lifecycle management permission response may also carry service resources permitted to be used by the containerized VNF instance licensed by the NFVO in the lifecycle management operation.
  • the service resources permitted to be used by the containerized VNF instance permitted by the NFVO in the life cycle management operation may be greater than or less than or equal to the containerized VNF carried in the VNF life cycle operation permission request The service resource requested by the instance in the life cycle management operation.
  • the NFVO further includes a judgment unit for judging the service requested by the containerized VNF instance in the life cycle management operation before the sending unit sends the VNF life cycle operation permission response to the VNFM
  • the resource is the relationship with the service resource of the network service NS instance to which the containerized VNF instance belongs.
  • the VNF life cycle operation permission response Can carry success instructions.
  • the VNF life cycle operation permission response may be Carry failure indication.
  • the service resource of the NS instance is, for example, the total number of container objects contained in all member VNF instances contained in the NS instance and/or container object packages called by all member nested NS instances.
  • the fifth aspect of the embodiments of the present application provides a service resource license management method, including: a container management platform CISM receives a container object package management operation request from a virtualized network function manager VNFM, the management operation request carrying the container object The service resource of the package, the service resource of the container object package does not exceed the service resource allowed by the containerized VNF instance permitted by the network function virtualization orchestrator NFVO in the life cycle management operation.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the CISM uses the service resources of the container object package to monitor the container objects under the container object package used by the containerized VNF instance in the life cycle management process, which may include :
  • the CISM monitors the operation of container objects and decides to expand the number of container objects to expand the containerized VNF instance, the CISM determines the number of container objects to be expanded and the containerized VNF instance is running The sum of the number of container objects cannot exceed the service resources of the container object package.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the NFVO uniformly licenses the service resources used by the container object in the life cycle management operation of the containerized VNF instance, and the CISM usage does not exceed that of the NFVO
  • the sixth aspect of the embodiments of the present application provides a container management platform CISM, including: a receiving unit, configured to receive a container object package management operation request from a virtualized network function manager VNFM, the management operation request carrying the container object The service resource of the package, the service resource of the container object package does not exceed the service resource allowed by the containerized VNF instance permitted by the network function virtualization orchestrator NFVO in the life cycle management operation.
  • the monitoring unit is configured to use the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the monitoring unit is specifically configured to: when the CISM monitors the running status of the container object and decides to expand the number of container objects to expand the containerized VNF instance, determine the size of the container object to be expanded The sum of the number and the number of running container objects in the containerized VNF instance cannot exceed the service resources of the container object package.
  • a seventh aspect of the embodiments of the present application provides a service resource license management method, including: a network function virtualization orchestrator NFVO receives a first service resource management request from a virtualized network function manager VNFM, the first service resource management request It carries service resources requested by the containerized VNF instance in life cycle management operations. The NFVO sends a second service resource management request to the container management platform CISM, where the second service resource management request carries the containerized VNF instance licensed by the NFVO that is allowed to be used in the lifecycle management operation Service resources.
  • the NFVO After receiving the second service resource management response from the CISM, the NFVO sends a first service resource management response to the VNFM, and the first service resource management response carries the container approved by the NFVO The service resources that the VNF instance is allowed to use in the life cycle management operation.
  • the NFVO before the NFVO sends the second service resource management request to the CISM, it further includes: the service resource requested by the containerized VNF instance in the life cycle management operation does not exceed the containerized VNF In the case of the service resources of the network service NS instance to which the instance belongs, the NFVO permits the service resources allowed to be used by the containerized VNF instance in the life cycle management operation, wherein the allowed service resources are less than or Equal to the service resource used by the request.
  • the NFVO determines the containerized VNF it allows The service resources allowed to be used by the instance in the life cycle management operation are less than the service resources requested to be used. Or, in the case that the service resources requested by the VNF instance in the lifecycle management operation exceed the service resources of the NS instance to which the containerized VNF instance belongs, the NFVO may refuse to permit the containerization Service resources that the VNF instance is allowed to use in the lifecycle management operation.
  • the service resource of the containerized VNF instance is, for example, the total number of container objects contained in the container object package called by the containerized VNF instance (may also be referred to as a quota or an upper limit).
  • the CISM receives the second service resource management request from the NFVO, and the container management platform sends the second service resource management response to the NFVO.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the service resource of the container object package does not exceed the service resource used in the life cycle management operation of the VNF instance licensed by the NFVO.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process. For example, it may include: when the CISM monitors the container When deciding to expand the number of container objects to expand the containerized VNF instance, CISM judges that the number of container objects to be expanded and the number of running container objects in the containerized VNF instance cannot exceed those granted by NFVO Bulk service resources.
  • the NFVO uniformly licenses the service resources used by the container object in the life cycle management operation of the containerized VNF instance.
  • An eighth aspect of the embodiments of the present application provides a network function virtualization orchestrator NFVO, including: a receiving unit, configured to receive a first service resource management request from a virtualized network function manager VNFM, the first service resource management request It carries service resources requested by the containerized VNF instance in life cycle management operations.
  • the sending unit is configured to send a second service resource management request to the container management platform CISM, the second service resource management request carrying the containerized VNF instance permitted by the NFVO to be used in the life cycle management operation Service resources.
  • the receiving unit receives the second service resource management response from the CISM, it sends a first service resource management response to the VNFM, where the first service resource management response carries the containerization permitted by the NFVO Service resources that the VNF instance is allowed to use in the lifecycle management operation.
  • the NFVO further includes a processing unit, configured to request service resources used by the containerized VNF instance in the lifecycle management operation before sending the second service resource management request to the CISM.
  • a processing unit configured to request service resources used by the containerized VNF instance in the lifecycle management operation before sending the second service resource management request to the CISM.
  • the service resources of the network service NS instance to which the containerized VNF instance belongs the service resources permitted to be used by the containerized VNF instance in the life cycle management operation are permitted, wherein the permitted service resources Equal to the service resource used by the request.
  • the containerized VNF instance In the case that the service resource requested by the VNF instance in the lifecycle management operation exceeds the service resource of the NS instance to which the containerized VNF instance belongs, it is determined that the containerized VNF instance permitted by it is in the Service resources allowed to be used in life cycle management operations, where the allowed service resources are less than the requested service resources. Or when the service resources requested by the VNF instance in the lifecycle management operation exceed the service resources of the NS instance to which the containerized VNF instance belongs, the containerized VNF instance may be refused permission to Service resources allowed in life cycle management operations.
  • the ninth aspect of the embodiments of the present application provides a virtual network function manager VNFM, including: a processor and a memory coupled to each other; wherein the processor is used to call a computer program stored in the memory to complete the embodiments of the present application Part or all of the steps of any method executed by the VNFM.
  • VNFM virtual network function manager
  • the tenth aspect of the embodiments of the present application provides a network function virtualization orchestrator NFVO, including: a processor and a memory coupled with each other; wherein the processor is used to call a computer program stored in the memory to complete the implementation of the application Part or all of the steps of any method executed by NFVO in the example.
  • NFVO network function virtualization orchestrator
  • the eleventh aspect of the embodiments of the present application provides a container management platform CISM, which may include: a processor and a memory coupled to each other; wherein the processor is used to call a computer program stored in the memory to complete the embodiments of the present application Part or all of the steps in any method performed by CISM.
  • CISM container management platform
  • the twelfth aspect of the embodiments of the present application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, it can complete what is executed by the VNFM in the embodiments of the present application. Part or all of the steps of any method.
  • the thirteenth aspect of the embodiments of the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it can complete what is executed by NFVO in the embodiments of the present application. Part or all of the steps of any method.
  • the fourteenth aspect of the embodiments of the present application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, it can complete what is executed by the CISM in the embodiments of the present application. Part or all of the steps of any method.
  • FIG. 1 is a schematic diagram of an ETSI NFV MANO standard architecture provided by an embodiment of this application
  • Fig. 2 is a schematic diagram of a VM-based VNF information model provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a Kubernetes container management orchestration architecture provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an information model of a containerized VNF provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of the target architecture of the ETSI NFV standard MANO management container provided by an embodiment of the present application.
  • Fig. 6 is a schematic flowchart of a service resource license management method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a service resource license management method provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a service resource license management method provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the architecture of a VNFM provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an NFVO architecture provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a CISM architecture provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another NFVO architecture provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • VNF virtual network functions
  • MANO MAN agement and Orchestration
  • IFA InterFace and Architecture
  • ETSI European Telecommunications Standards Institute
  • the NFV orchestrator (NFVO, NFV Orchestrator) can be used to implement network service descriptors (NSD, NS Descriptor), virtual network function forwarding graphs (VNFFG, VNF Forwarding Graph) management and Processing, network service (NS, Network Service) life cycle management, cooperate with VNFM to realize VNF life cycle management and have the function of global view of virtual resources.
  • NSD network service descriptor
  • VNFFG virtual network function forwarding graphs
  • NS Network Service life cycle management
  • VNFM VNF Manager
  • VNFD virtualized network function descriptor
  • instantiation of VNF can include scaling out/up and scaling in/down
  • VNF instance healing heat and scaling
  • VNF instance termination termination
  • VNFM also supports receiving the elastic scaling strategy issued by NFVO to realize automatic VNF elastic scaling.
  • Virtualized Infrastructure Manager (VIM, Virtualised Infrastructure Manager) is mainly responsible for the management (including reservation and allocation) of virtualized resources (including virtual computing, storage, and network resources) at the infrastructure layer, the monitoring of virtual resource status, and fault reporting.
  • the upper application provides a virtualized resource pool.
  • Operation and business support systems can refer to the operation and maintenance system OSS/BSS of operators.
  • the element management system (EM, Element Manager) performs traditional fault (Fault), user (Account) and configuration (Configuration), performance (Performance) and security (Security) management (referred to as FCAPS management) functions for VNFs.
  • VNF Virtualized network function
  • PNF physical network function
  • EPC nodes packet gateway, service gateway, etc.
  • the functional behavior and status of network functions have nothing to do with virtualization or not.
  • NFV technology requires that VNF and PNF have the same functional behavior and external interface.
  • NFV Infrastructure is the infrastructure layer of NFV functions, consisting of hardware resources, virtual resources, and a virtualization layer. From the perspective of VNF, the virtualization layer and hardware resources are a complete entity that can provide the required virtual resources.
  • the management object information model in the NFV field is described around the function model, deployment model and resource model of VNF, which can be specifically shown in Figure 2.
  • the highest-level management object in the NFV field is a network service (NS, Network Service), and each NS can be composed of one or more VNFs. Further, each VNF can be composed of one or more lower functional level VNF components (VNFC, VNF Component).
  • NS is only visible to NFVO, while VNF is visible to both NFVO and VNFM, and VNFC is only visible to VNFM.
  • VNFs of the same type for example, vMME or vPGW, etc.
  • VNFD VNF Descriptor File
  • the VNFD may include one or more virtualized deployment units (VDUs, Virtualized Deployment Units) of finer granularity.
  • VDUs virtualized deployment units
  • Each VDU uniquely corresponds to a type of VNFC, which contains the description information required for the deployment and operation of this type of VNFC.
  • the virtualization layer of NFVI abstracts and encapsulates the underlying hardware resources (or physical resources) as a virtual machine (VM, Virtual Machine).
  • the VNF can be deployed on multiple VMs, and each VM uniquely carries the function of a VNFC. Of course, the VNF can also be deployed on one VM.
  • each VDU describes a type of VNFC's demand for infrastructure layer virtual resources (Infrastructure Resources), and the VM allocated by VIM encapsulates the information of infrastructure layer virtual resources that meet this demand. From the function model to the deployment model to the resource model, a one-to-one mapping relationship is formed between VNFC, VDU and VM.
  • a host is a hardware resource, and one or more VM instances can be split to create one or more VM instances on a host. VM is visible to both NFVO and VNFM, while host resources are not visible to NFVO and VNFM.
  • Kubernetes (K8S) container cluster management technology based on the open source platform. Its core idea is "everything is service-centric, everything revolves around services”. Following this idea, container application systems built on Kubernetes can not only run independently on physical machines, virtual machines or enterprise private clouds, but also be Hosted to the public cloud. Another feature of Kubernetes is automation, a service can be self-scalable, self-diagnostic, and easy to upgrade.
  • the Kubernetes container management orchestration can be shown as an example in Figure 3.
  • Container management orchestration is an important base architecture enhancement feature in the evolution of telecommunications network function virtualization (NFV) to cloud native (CloudNative). It forms interoperability by connecting the NFV MANO system with mature container management platforms (such as Kubernetes) in the industry. Standardized scenarios, from the architecture function to ensure the continuous delivery of containerized VNF in DevOps.
  • the prior art has not yet conducted a detailed analysis of the enhancement of the NFV management object information model after the introduction of the container.
  • the target architecture of the MANO management container proposed in the IFA029 research report is shown in Figure 5.
  • the container service is an infrastructure service that is separated from the VNF function to form an independent layer.
  • the Container Manager adopts de facto standards (such as Kubernetes API) to interact with the container service to provide all for the lifecycle management of containerized VNFs.
  • the required container infrastructure services (CIS, Container Infrastructure Service).
  • the container manager provides NFVO or VNFM with the management function of container objects or container object packages (for example, Pod of Kubernetes or Chart objects of Helm, etc.) on the northbound interface, and these container objects further constitute a containerized VNF.
  • the container manager is also called Container Infrastructure Service Management (CISM, Container Infrastructure Service Management), and the container service is also called Container Infrastructure Service (CIS, Container Infrastructure Service).
  • the IFA029 research report introduces the concept of service resources on top of the infrastructure resources (infrastructure resources, which can be virtual machines or bare machines, etc.) used by containers.
  • service resources refer to logical resources used by container objects, and mapping to Kubernetes corresponds to resource quotas used under a namespace.
  • the introduction of service resources decouples the underlying infrastructure resources of the container from the containerized VNF.
  • the designer of the VNF will pay more attention to the realization of the mapping from the functional logic of the VNF to the functional logic of the container, without having to fall into the infrastructure resources (such as : The details of the creation and allocation of virtual machine) make full use of the ability of Kubernetes to autonomously manage node resources to realize the agile development and operation and maintenance of containerized VNF.
  • Service resources are visible to NFVO or VNFM, while infrastructure resources (virtual or bare metal) become no longer visible to NFVO or VNFM under the isolation of service resources.
  • service resources are abstract logical resources defined for container objects, in fact the management of service resources can still be managed by referring to the management mode of infrastructure resources in the ETSI NFV standard, that is: direct mode or indirect mode for service Resource management.
  • the IFA029 report does not conduct a detailed study on service resource management used by containers. In particular, how to describe service resources at the abstract container object layer and define the boundary of service resources to container objects will affect how to reuse existing infrastructure resource management models to manage service resources.
  • An information model of a containerized VNF provided by an embodiment of the present application may be as shown in FIG. 4.
  • the resource model of the containerized VNF introduces an abstract logical resource layer composed of container objects (such as Pod, Service, or Deployment objects in Kubernetes) (such as the server resource in the resource model in Figure 4).
  • the logical resource layer isolates infrastructure resources (such as VM resources) from container-based VNFs.
  • the NFV MANO system manages container objects in the logical resource layer without the need to manage infrastructure resources. The management of infrastructure resources is left to NFVI.
  • the resource model of the VNF shown in Fig. 4 encapsulates abstract logical resources composed of container objects on infrastructure resources, namely service resources.
  • the abstracted container objects contained in the service resources are also called managed container infrastructure objects (MCIO, Managed Container Infrastructure Object).
  • MCIO managed container infrastructure objects
  • These abstract managed container objects can be specifically mapped as The de facto standard container objects in the open source field, such as Pod, Service or Deployment, ReplicaSets, StatefulSets, etc. in Kubernetes.
  • the embodiment of this application proposes some service resource granting management methods.
  • the VNFM When the VNFM performs the life cycle management operation of the containerized VNF, the VNFM first initiates a service resource grant request to the VNFO, and the NFVO firstly initiates a service resource grant request to the VNF life cycle management operation.
  • the service resources used by the objects are permitted, which effectively avoids the service resources used by the member VNFs in the network service (NS, Network Service) from exceeding the preset quota and causing conflicts in the use of service resources at the NS level.
  • NS Network Service
  • service resources are defined as logical resources used by container objects, and mapped to Kubernetes corresponding to resource quotas used under a namespace.
  • the namespace can be mapped to a VNF instance or an NS instance.
  • Service resources of a containerized VNF instance refers to the total number of container objects contained in the container object package called by this containerized VNF instance (also referred to as quota or upper limit).
  • Service resources of an NS instance refers to the total number of container objects used by all member components (such as nested NS and containerized VNF instances, etc.) contained in this NS instance (also referred to as quota or upper limit).
  • the following examples illustrate the concepts of containerized VNF instance service resources and NS instance service resources.
  • the instantiation process of a containerized VNF requests 3 container package files (each package file is defined by its own Helm Chart template).
  • the instantiated VNF instance will correspond to 3 container package instances (for example: Helm Release), and these three container package instances contain different numbers of container objects, for example: package instance 1 contains 2 Kubernetes Deployment objects , Package instance 2 contains 3 Kubernetes Pod objects, and package instance 3 contains 2 Kubernetes Service objects, 1 Kubernetes Deployment object and 1 ReplicaSets object.
  • this containerized VNF instance If the service resources of this containerized VNF instance are set to 10 (total/quota), and the total number of container objects contained in the container object package called by this containerized VNF instance is 9 (2+3+2+1+ 1) Therefore, it conforms to the service resource setting of this containerized VNF instance. In this form of the number of container objects, the operation of the containerized VNF instance is permitted.
  • the service resources used by all VNF instances and nested NS instances constituting the NS instance cannot exceed the service resources set by the NS instance.
  • the resource can be normalized to the total number of the smallest particle container objects mapped by the container object contained in the container object package called by the containerized VNF instance. For example, in Kubernetes, the number of different container objects is mapped to the number of Pods, or more The number of fine-grained OS containers (usually, OS containers are encapsulated by Pod and are not visible to other Kubernetes objects).
  • the service resources of an NS instance can also be normalized to the total number of minimum granular capacity objects mapped by container objects used by all member components (such as nested NS and containerized VNF instances) included in the NS instance.
  • the service resources of a containerized VNF instance can also be defined as the infrastructure resources used by the container objects contained in the container object package called by the containerized VNF instance (for example: virtual computing, storage and The total number of network resources), this aspect will not be repeated in the solution of this application.
  • FIG. 6 is a schematic flowchart of a service resource license management method provided by an embodiment of the application.
  • a service resource license management method may include:
  • NFVO or EM sends a VNF life cycle management operation request to the VNFM, and the VNF life cycle management operation request can be used to trigger the start of the life cycle management operation of the containerized VNF instance.
  • the VNFM receives a VNF lifecycle management operation request from a containerized VNF instance such as NFVO or EM, and the VNFM reads from the VNFD the service resources that the containerized VNF instance requests to use in the lifecycle management operation.
  • a containerized VNF instance such as NFVO or EM
  • the VNFM sends a VNF life cycle operation permission request to the NFVO.
  • the VNF life cycle operation permission request carries the service resource requested by the containerized VNF instance in the life cycle management operation.
  • the NFVO receives a VNF life cycle operation permission request from the VNFM, and the NFVO sends a VNF life cycle operation permission response to the VNFM.
  • the NFVO before the NFVO sends the VNF lifecycle operation permission response to the VNFM, it also includes: the NFVO determines that the service resource requested by the containerized VNF instance in the lifecycle management operation belongs to the containerized VNF instance The relationship between the service resources of the NS instance. In the case that the service resource requested by the containerized VNF instance in the life cycle management operation does not exceed the service resource of the NS instance to which the containerized VNF instance belongs, the VNF life cycle operation permission response may carry Success indication. In the case that the service resources requested by the containerized VNF instance in the life cycle management operation exceed the service resources of the network service NS instance to which the containerized VNF instance belongs, the VNF life cycle operation permission response may be Carry failure indication.
  • the service resource of the NS instance may be the total number (quota) of container objects contained in all member VNF instances contained in the NS instance and/or container object packages called by all member nested NS instances.
  • the VNFM receives a VNF life cycle operation permission response from the NFVO.
  • the VNF life cycle management permission response may carry service resources used by the VNF instance licensed by the NFVO in the word order in the life cycle management operation.
  • the service resources permitted by the VNF instance permitted by the NFVO in the life cycle management operation are greater than or equal to or less than the containerized VNF instance carried in the VNF life cycle operation permission request. Service resources requested for use in life cycle management operations.
  • the NFVO may further carry its recommended service resources in the response message.
  • the VNFM when the VNF lifecycle management permission response carries a success indication, the VNFM sends a container object package management operation request to the container management platform CISM, the management operation request carries the service resources of the container object package, and the container object package The service resources of does not exceed the service resources permitted by the VNF instance permitted by the NFVO in the life cycle management operation.
  • the CISM receives the management operation request of the container object package from the VNFM.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the CISM uses the service resources of the container object package to monitor the container objects under the container object package used by the containerized VNF instance in the life cycle management process, for example, it may include: when the CISM passes When monitoring the operation of container objects and deciding to expand the number of container objects to expand the containerized VNF instance, CISM judges the sum of the number of container objects to be expanded and the number of container objects running in the containerized VNF instance, The service resources of the container object package cannot be exceeded.
  • the VNFM when the VNFM performs the life cycle management operation of the containerized VNF, the VNFM first initiates a VNF service resource permission request to the VNFO, and the NFVO licenses the service resources used by the container object in the containerized VNF instance life cycle management operation.
  • This is beneficial to effectively avoiding service resource usage conflicts at the NS level due to the service resources used by each member VNF in the network service exceeding the preset quota, which is beneficial to effectively manage the use of containerized VNF instances from the perspective of network services Service resources.
  • FIG. 7 is a schematic flowchart of another service resource license management method provided by an embodiment of the application, and another service resource license management method may include:
  • the NFVO sends a service resource batch license request for VNF lifecycle management operations to the VNFM, and the service resource batch license request carries the batch service resources that the NFVO grants to the VNFM to manage.
  • the batch service resources managed by the VNFM may be, for example, a range including upper and lower thresholds, that is, the batch service resources managed by the VNFM cannot exceed the upper and lower boundaries of the value determined by the range.
  • NFVO may determine to grant batch container services to VNFM for management based on the global considerations of NS lifecycle management.
  • Bulk service resources can be used in the lifecycle management operations of any containerized VNF instance managed by VNFM. The total number of service resources used by all containerized VNF instances managed by VNFM at any time cannot exceed the bulk service resources granted by NFVO.
  • the VNFM receives a service resource batch license request for the VNF life cycle management operation from the NFVO.
  • the VNFM returns a service resource batch licensing response for the VNF life cycle management operation to the NFVO, and the service resource batch licensing response may carry a success indication or a failure indication.
  • the VNFM executes the containerized VNF lifecycle management operation, the VNFM sends a container object package management operation request to the container management platform.
  • the container management platform receives a management operation request for the container object package from the VNFM, and the CISM uses the service resources of the container object package to determine the container object used by the containerized VNF instance in the life cycle management process.
  • the container objects under the package are monitored.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process. For example, it may include: when the CISM monitors the container When deciding to expand the number of container objects to expand the containerized VNF instance, CISM judges that the number of container objects to be expanded and the number of running container objects in the containerized VNF instance cannot exceed those granted by NFVO Bulk service resources.
  • FIG. 8 is a schematic flowchart of another service resource license management method provided by an embodiment of the application, and another service resource license management method may include:
  • NFVO or EM sends a VNF life cycle management operation request to the VNFM to trigger the start of the life cycle management operation of the containerized VNF instance.
  • the VNFM receives a VNF lifecycle management operation request from NFVO or EM, and the VNFM sends a first service resource management request to NFVO.
  • the first service resource management request carries the containerized VNF instance requested to use in the lifecycle management operation Service resources.
  • the NFVO receives the first service resource management request from the VNFM.
  • the NFVO sends a second service resource management request to the container management platform CISM, the second service resource management request carrying the service resources permitted by the containerized VNF instance permitted by the NFVO in the life cycle management operation .
  • the CISM receives the second service resource management request from the NFVO, and the container management platform sends the second service resource management response to the NFVO.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the service resource of the container object package does not exceed the service resource used in the life cycle management operation of the VNF instance licensed by the NFVO.
  • the CISM uses the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process. For example, it may include: when the CISM monitors the container When deciding to expand the number of container objects to expand the containerized VNF instance, CISM judges that the number of container objects to be expanded and the number of running container objects in the containerized VNF instance cannot exceed those granted by NFVO Bulk service resources.
  • the NFVO After receiving the second service resource management response sent by the container management platform, the NFVO sends a first service resource management response to the VNFM, where the first service resource management response carries the container licensed by the NFVO The service resources that the VNF instance is allowed to use in the life cycle management operation.
  • the NFVO before the NFVO sends the second service resource management request to the CISM, it may further include: the service resource requested by the containerized VNF instance in the life cycle management operation does not exceed the containerized service resource management request.
  • the NFVO permits the service resources allowed to be used by the containerized VNF instance in the life cycle management operation, wherein the allowed service resources are equal to The service resource used by the request.
  • the NFVO determines the containerized VNF it allows The service resources allowed to be used by the instance in the life cycle management operation are less than the service resources requested to be used. Or, in the case that the service resources requested by the VNF instance in the lifecycle management operation exceed the service resources of the NS instance to which the containerized VNF instance belongs, the NFVO may refuse to permit the containerization Service resources that the VNF instance is allowed to use in the lifecycle management operation.
  • the NFVO uniformly licenses the service resources used by the container object in the life cycle management operation of the containerized VNF instance.
  • a virtualized network function manager VNFM 900 provided by an embodiment of the present application includes:
  • the receiving unit 910 is configured to receive a life cycle management operation request of the containerized VNF instance.
  • the reading unit 920 is configured to read from the virtualized network function descriptor VNFD the service resources requested to be used by the containerized VNF instance in the life cycle management operation;
  • the sending unit 930 is configured to send a VNF life cycle operation permission request to the network function virtualization orchestrator NFVO, where the VNF life cycle operation permission request carries the service requested by the containerized VNF instance in the life cycle management operation Resources;
  • the receiving unit 910 is further configured to receive a VNF life cycle operation permission response from the NFVO.
  • the service resource of the containerized VNF instance is the total number of container objects contained in the container object package called by the VNF instance.
  • the VNF life cycle management permission response also carries service resources that the VNF instance licensed by the NFVO is allowed to use in the life cycle management operation.
  • the sending unit 930 is further configured to, when the VNF life cycle management permission response carries a success indication, send a container object package management operation request to the container management platform CISM, and the management operation request carries the The service resource of the container object package, the service resource of the container object package does not exceed the service resource allowed by the VNF instance licensed by the NFVO in the life cycle management operation.
  • a network function virtualization orchestrator NFVO 1000 provided by an embodiment of the present application includes:
  • the receiving unit 1010 is configured to receive a VNF life cycle operation permission request from the VNFM, where the life cycle operation permission request carries service resources requested by the containerized VNF instance in the life cycle management operation.
  • the sending unit 1020 is configured to send a VNF life cycle operation permission response to the VNFM.
  • the service resource of the containerized VNF instance is the total number of container objects contained in the container object package called by the VNF instance.
  • it further includes a judging unit 1030 for judging the service resource requested by the containerized VNF instance in the lifecycle management operation before sending the VNF lifecycle operation permission response to the VNFM, and The relationship between the service resources of the NS instance to which the containerized VNF instance belongs.
  • the VNF life cycle operation permission response Carry success instructions In the case that the service resource requested by the containerized VNF instance in the life cycle management operation does not exceed the service resource of the network service NS instance to which the containerized VNF instance belongs, the VNF life cycle operation permission response Carry success instructions.
  • the VNF life cycle operation permission response carries Failure indication.
  • the service resource of the NS instance is the total number of container objects contained in all member VNF instances contained in the NS instance and/or container object packages called by all member nested NS instances .
  • a container management platform CISM 1100 provided by an embodiment of the present application includes:
  • the receiving unit 1110 is configured to receive a management operation request of a container object package from a VNFM, the management operation request carrying service resources of the container object package, and the service resources of the container object package do not exceed the VNF permitted by NFVO Service resources used by the instance in life cycle management operations;
  • the monitoring unit 1120 is configured to use the service resources of the container object package to monitor the container objects in the container object package used by the containerized VNF instance in the life cycle management process.
  • the monitoring unit is specifically configured to: when CISM monitors the running status of container objects and decides to expand the number of container objects to expand the containerized VNF instance, CISM determines the number and number of container objects to be expanded. The number of running container objects in the containerized VNF instance cannot exceed the service resources of the container object package.
  • the service resource of the containerized VNF instance is the total number of container objects contained in the container object package called by the VNF instance.
  • an NFVO 1200 provided by an embodiment of the present application includes:
  • the receiving unit 1210 is configured to receive a first service resource management request from a VNFM, where the first service resource management request carries service resources requested by the containerized VNF instance to be used in life cycle management operations;
  • the sending unit 1220 is configured to send a second service resource management request to the container management platform CISM, where the second service resource management request carries the containerized VNF instance permitted by the NFVO to allow use in the life cycle management operation
  • the receiving unit receives the second service resource management response sent by the container management platform, it sends a first service resource management response to the VNFM, the first service resource management response carrying the NFVO permitted by the NFVO
  • the service resources that the containerized VNF instance is allowed to use in the life cycle management operation.
  • the NFVO 1200 further includes a processing unit 1230, configured to request the containerized VNF instance in the lifecycle management operation before the NFVO sends a second service resource management request to the container management platform CISM If the service resource used does not exceed the service resource of the network service NS instance to which it belongs, the service resource requested by the VNF instance in the life cycle management operation is permitted; when the VNF instance is in the life cycle In the case that the service resources requested to be used in the management operation exceed the service resources of the NS instance to which the VNF instance belongs, the service resources that the VNF instance permits are used in the life cycle management operation.
  • the service resource of the VNF instance is the total number of container objects contained in the container object package called by the VNF instance.
  • an embodiment of the present application also provides a general communication device 1300, which can implement the functions of the VNFM, NFVO or container management platform provided in the above embodiments, and specifically includes:
  • the processor 1310 and the memory 1320 are coupled to each other.
  • the processor 1310 is used to call a computer program stored in the memory 1320 to complete part or all of the steps of any method executed by the VNFM in the embodiment of the present application.
  • processor 1310 may also call different computer programs stored in the memory 1320 to complete part or all of the steps of any method executed by the NFVO or the container management entity in the embodiment of the present application.
  • the processor 1210 is also called a central processing unit (CPU, Central Processing Unit).
  • the components of the image prediction device are coupled together through a bus system, for example.
  • the bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 730 in the figure.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1310 or implemented by the processor 1310.
  • the processor 1310 may be an integrated circuit chip with signal processing capabilities. In some implementation processes, part or all of the steps of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1310 or instructions in the form of software.
  • the processor 1310 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, an off-the-shelf programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component.
  • the processor 1310 can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor 1310 may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory or registers.
  • the storage medium is located in the memory 1320.
  • the processor 1310 can read information in the memory 1320 and complete some or all of the steps of the foregoing method in combination with its hardware.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, the computer program is executed by hardware (such as a processor, etc.), and is executed by any device in the embodiment of the present application Part or all of the steps of any method.
  • the embodiments of the present application also provide a computer program product including instructions, which when the computer program product runs on a computer device, cause the computer device to execute part or all of the steps of any one of the above aspects.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (such as a floppy disk, a hard disk, and a magnetic tape), an optical medium (such as an optical disk), or a semiconductor medium (such as a solid state hard disk).
  • the disclosed device may also be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored or not implemented.
  • the displayed or discussed indirect coupling or direct coupling or communication connection between each other may be through some interfaces, indirect coupling or communication connection between devices or units, and may be in electrical or other forms.
  • 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, they may be located in one place, or they 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 this embodiment.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may also be implemented in the form of software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium,
  • a number of instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage medium may include, for example: U disk, mobile hard disk, Read-Only Memory (ROM), Random Access Memory (RAM, Random Access Memory), magnetic disks or optical disks and other storable program codes. Medium.

Landscapes

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

Abstract

本申请实施例提供服务资源许可管理方法和相关设备。其中，一种服务资源许可管理方法包括：VNFM接收容器化VNF实例的生命周期管理操作请求；从VNFD中读取容器化VNF实例在生命周期管理操作中请求使用的服务资源；向NFVO发送VNF生命周期操作许可请求，所述VNF生命周期操作许可请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源；接收来自NFVO的VNF生命周期操作许可应答。本申请实施例方案有利于从网络服务的角度灵活管理容器化VNF实例使用的服务资源。

Description

服务资源许可管理方法和相关设备
本申请要求于2019年7月11日提交中国国家知识产权局、申请号为201910625039.5、发明名称为“服务资源许可管理方法和相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及服务资源许可管理方法和相关设备。
背景技术
网络功能虚拟化(NFV,Network Function Virtualization)是指电信网络运营商借鉴了信息技术(IT,Information Technology)领域的虚拟化技术，在通用的服务器、交换机和存储器等设备中将部分电信网络功能(例如：核心网功能)的实现进行软件和硬件解耦，从而实现网络服务(NS,Network Service)快速、高效部署和运营，同时，达到节省网络投资成本和运营成本的目标。通过应用NFV技术，电信网络功能以软件方式实现，并可以在通用的服务器硬件上运行，可以根据需要来进行迁移、实例化、部署在网络的不同物理位置，并且不需要安装新设备。
其中，容器即服务(CaaS,Container as a Service)例如可看作是一种特定类型的平台即服务(PaaS,Platform as a Service)服务。通常而言，容器(Container)是一种操作系统级别的虚拟化技术，通过操作系统隔离技术如Linux下的CGroup和NameSpace，将不同的进程隔离开来。容器技术不同于硬件虚拟化(Hypervisor)技术，并没有虚拟硬件，容器内部也没有操作系统，只有进程。由于容器技术的这个重要特点，使得容器相比虚拟机更轻量，管理也更方便。在容器的运行态，定义了一组公共的管理操作，具体例如：启动、停止、暂停和删除等等，对容器进行统一的生命周期管理。
容器化VNF支撑的应用形态服务化或者微服务化，当前业内还没提出针对容器化VNF实例生命周期管理过程中使用的服务资源许可管理方案。
发明内容
本申请实施例提供服务资源许可管理方法和相关设备。
本申请实施例第一方面提供一种服务资源许可管理方法，包括：
虚拟化网络功能管理器(VNFM,Virtualized Network Function Manager)接收容器化虚拟网络功能(VNF,Virtualized Network Function)实例的生命周期管理操作请求(所述生命周期管理操作请求例如来自网络功能虚拟化编排器或网元管理系统等)。所述VNFM从虚拟化网络功能描述符(VNFD,VNF Descriptor)中读取所述容器化VNF实例在生命周期管理操作中请求使用的服务资源。
VNFM向网络功能虚拟化编排器(NFVO,Network Function Virtualization Orchestrator)发送VNF生命周期操作许可请求，所述VNF生命周期操作许可请求之中携带 有所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。所述VNFM接收来自所述NFVO的VNF生命周期操作许可应答。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
在一些可能的实施方式中，所述VNF生命周期管理许可应答例如可携带成功指示或者失败指示。
在一些可能的实施方式中，所述VNF生命周期管理许可应答还可携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。其中，所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，例如可大于或小于或等于所述VNF生命周期操作许可请求中携带的所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。
在一些可能的实施方式中，所述方法还包括：
当所述VNF生命周期管理许可应答携带成功指示，所述VNFM向容器管理平台CISM发送容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源，不超过由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
上述举例方案中，当VNFM执行容器化VNF实例的生命周期管理操作时，VNFM先向VNFO发起VNF生命周期操作许可请求来请求VNFO许可相关服务资源，由NFVO来统一的对容器化VNF实例的生命周期管理操作中容器对象使用的服务资源进行许可，这样有利于避免网络服务中各成员VNF使用的服务资源因超出相关预设配额而在NS层面形成服务资源使用冲突，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
本申请实施例第二方面提供一种虚拟化网络功能管理器，包括：
接收单元，用于接收容器化VNF实例的生命周期管理操作请求(所述生命周期管理操作请求例如来自网络功能虚拟化编排器或网元管理系统等)。
读取单元，用于从VNFD中读取所述容器化VNF实例在生命周期管理操作中请求使用的服务资源。
发送单元，向NFVO发送VNF生命周期操作许可请求，所述VNF生命周期操作许可请求之中携带有所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。所述VNFM接收来自所述NFVO的VNF生命周期操作许可应答。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
在一些可能的实施方式中，所述VNF生命周期管理许可应答例如可携带成功指示或者失败指示。
在一些可能的实施方式中，所述VNF生命周期管理许可应答还可携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。其中，所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，例如可大于或小于或等于所述VNF生命周期操作许可请求中携带的所述容器化VNF实例在所述生命周 期管理操作中请求使用的服务资源。
在一些可能的实施方式中，所述发送单元还用于：当所述VNF生命周期管理许可应答携带成功指示，向容器管理平台CISM发送容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源。其中，所述容器对象包的服务资源，不超过由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
本申请实施例第三方面提供一种服务资源许可管理方法，包括：
网络功能虚拟化编排器NFVO接收来自虚拟网络功能管理器VNFM的虚拟网络功能VNF生命周期操作许可请求，其中，所述VNF生命周期操作许可请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。
所述NFVO向VNFM发送VNF生命周期操作许可应答。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
在一些可能的实施方式中，所述VNF生命周期管理许可应答例如可携带成功指示或者失败指示。
在一些可能的实施方式中，所述VNF生命周期管理许可应答还可携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。其中，所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，例如可大于或小于或等于所述VNF生命周期操作许可请求中携带的所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。
在一些可能实施方式中，NFVO向VNFM发送VNF生命周期操作许可应答之前还可包括：所述NFVO判断所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，与所述容器化VNF实例所属的网络服务NS实例的服务资源之间的关系；
其中，在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的NS实例的服务资源的情况下，所述VNF生命周期操作许可应答可携带成功指示。在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况下，所述VNF生命周期操作许可应答可携带失败指示。
其中，所述NS实例的服务资源例如为所述NS实例所包含的所有成员VNF实例和/或所有成员嵌套NS实例所调用的容器对象包中所包含的容器对象的总数。
上述举例方案中，当VNFM执行容器化VNF实例的生命周期管理操作时，VNFM先向VNFO发起VNF生命周期操作许可请求来请求VNFO许可相关服务资源，由NFVO来统一的对容器化VNF实例的生命周期管理操作中容器对象使用的服务资源进行许可，这使得避免网络服务中各成员VNF使用的服务资源因超出相关预设配额而在NS层面形成服务资源使用冲突变得可能，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
本申请实施例第四方面提供一种网络功能虚拟化编排器NFVO，包括：
接收单元，用于接收来自虚拟网络功能管理器VNFM的虚拟网络功能VNF生命周期操作 许可请求。所述VNF生命周期操作许可请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。
发送单元，用于向VNFM发送VNF生命周期操作许可应答。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
在一些可能的实施方式中，所述VNF生命周期管理许可应答例如可携带成功指示或者失败指示。
在一些可能的实施方式中，所述VNF生命周期管理许可应答还可携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。其中，所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，例如可大于或小于或等于所述VNF生命周期操作许可请求中携带的所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。
在一些可能实施方式中，所述NFVO还包括判断单元，用于在发送单元向VNFM发送VNF生命周期操作许可应答之前：判断所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，与所述容器化VNF实例所属的网络服务NS实例的服务资源之间的关系。
其中，在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的NS实例的服务资源的情况下，所述VNF生命周期操作许可应答可携带成功指示。在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况下，所述VNF生命周期操作许可应答可携带失败指示。
其中，所述NS实例的服务资源例如为所述NS实例所包含的所有成员VNF实例和/或所有成员嵌套NS实例所调用的容器对象包中所包含的容器对象的总数。
本申请实施例第五方面提供一种服务资源许可管理方法，包括：容器管理平台CISM接收来自虚拟化网络功能管理器VNFM的容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过被网络功能虚拟化编排器NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源。所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
在一些可能实施方式中，所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，可包括：当所述CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，所述CISM判断要扩充的容器对象的数量与所述容器化VNF实例中正在运行的容器对象的数量之和，不能超过所述容器对象包的服务资源。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
上述举例方案中，当VNFM执行容器化VNF实例的生命周期管理操作时，由NFVO来统一的对容器化VNF实例的生命周期管理操作中容器对象使用的服务资源进行许可，CISM使用 不超过被NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源的容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，这样有利于避免网络服务中各成员VNF使用的服务资源因超出相关预设配额而在NS层面形成服务资源使用冲突，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
本申请实施例第六方面提供一种容器管理平台CISM，包括：接收单元，用于接收来自虚拟化网络功能管理器VNFM的容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过被网络功能虚拟化编排器NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源。
监控单元，用于使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
在一些可能实施方式中，所述监控单元具体用于：当所述CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，判断要扩充的容器对象的数量与所述容器化VNF实例中正在运行的容器对象的数量之和，不能超过所述容器对象包的服务资源。
本申请实施例第七方面提供一种服务资源许可管理方法，包括：网络功能虚拟化编排器NFVO接收来自虚拟化网络功能管理器VNFM的第一服务资源管理请求，所述第一服务资源管理请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。所述NFVO向容器管理平台CISM发送第二服务资源管理请求，其中，所述第二服务资源管理请求携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。所述NFVO在接收到来自所述CISM的第二服务资源管理应答之后，向所述VNFM发送第一服务资源管理应答，所述第一服务资源管理应答中携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
在一些可能实施方式中，NFVO向CISM发送第二服务资源管理请求之前，还包括：在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况之下，所述NFVO许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，其中，所述允许使用的服务资源小于或等于所述请求使用的服务资源。
在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述NFVO确定其许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，所述允许使用的服务资源小于所述请求使用的服务资源。或者，在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述NFVO可拒绝许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
其中，所述容器化VNF实例的服务资源例如为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
相应的，CISM接收来自NFVO的第二服务资源管理请求，容器管理平台向所述NFVO发送第二服务资源管理应答。
所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。所述容器对象包的服务资源不超过被NFVO许可的所述VNF实例在生命周期管理操作中所使用的服务资源。
所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，例如可包括：当CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，CISM判断要扩充的容器对象的数量和所述容器化VNF实例中正在运行的容器对象的数量不能超过NFVO授予的批量服务资源。
上述举例方案中，当VNFM触发执行容器化VNF实例的生命周期管理操作时，由NFVO来统一的对容器化VNF实例的生命周期管理操作中容器对象使用的服务资源进行许可，CISM使用不超过被NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源的容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，这样有利于避免网络服务中各成员VNF使用的服务资源因超出相关预设配额而在NS层面形成服务资源使用冲突，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
本申请实施例第八方面提供一种网络功能虚拟化编排器NFVO，包括：接收单元，用于接收来自虚拟化网络功能管理器VNFM的第一服务资源管理请求，所述第一服务资源管理请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。
发送单元，用于向容器管理平台CISM发送第二服务资源管理请求，所述第二服务资源管理请求携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。在接收单元接收到来自所述CISM的第二服务资源管理应答之后，向所述VNFM发送第一服务资源管理应答，所述第一服务资源管理应答中携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
在一些可能实施方式中，NFVO还包括处理单元，用于在向CISM发送第二服务资源管理请求之前，在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况之下，许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，其中，所述允许使用的服务资源等于所述请求使用的服务资源。
在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况下，确定其许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，所述允许使用的服务资源小于所述请求使用的服务资源。或者在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况下，可拒绝许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
本申请实施例第九方面提供一种虚拟网络功能管理器VNFM，包括：相互耦合的处理器和存储器；其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
本申请实施例第十方面提供一种网络功能虚拟化编排器NFVO，包括：相互耦合的处理器和存储器；其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成本申请实施例中由NFVO执行的任意一种方法的部分或全部步骤。
本申请实施例第十一方面提供一种容器管理平台CISM，可包括：相互耦合的处理器和存储器；其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成本申请实施例中由CISM执行的任意一种方法的部分或全部步骤。
本申请实施例第十二方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，能够完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
本申请实施例第十三方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，能够完成本申请实施例中由NFVO执行的任意一种方法的部分或全部步骤。
本申请实施例第十四方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，能够完成本申请实施例中由CISM执行的任意一种方法的部分或全部步骤。
附图说明
下面将对本申请实施例涉及的一些附图进行说明。
图1是本申请实施例提供的一种ETSI NFV MANO标准架构的示意图
图2是本申请实施例提供的一种基于VM的VNF信息模型的示意图。
图3是本申请实施例提供的一种Kubernetes容器管理编排架构示意图。
图4是本申请实施例提供的一种容器化VNF的信息模型的示意图。
图5是本申请实施例提供的ETSI NFV标准MANO管理容器目标架构的示意图。
图6是本申请实施例提供的一种服务资源许可管理方法的流程示意图。
图7是本申请实施例提供的一种服务资源许可管理方法的流程示意图。
图8是本申请实施例提供的一种服务资源许可管理方法的流程示意图。
图9是本申请实施例提供的一种VNFM的架构示意图。
图10是本申请实施例提供的一种NFVO的架构示意图。
图11是本申请实施例提供的一种CISM的架构示意图。
图12是本申请实施例提供的另一种NFVO的架构示意图。
图13是本申请实施例提供的一种通信设备的架构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例方案进行描述。
NFV的标准化工作主要集中在虚拟网络功能(VNF,Virtualized Network Function)、网络服务和虚拟资源的动态管理和编排(MANO,MAN agement and Orchestration)。一般由欧洲通信标准协会(ETSI,European Telecommunications Standards Institute)之下的NFV行业标准组的接口与架构(IFA,InterFace and Architecture)工作组来完成MANO框架内的功能制订工作等，其功能架构可如图1所示。虚拟网络功能管理器(VNF,Virtualized Network Function Manager)
其中，在图1所示架构之中，NFV编排器(NFVO,NFV Orchestrator)可以用于实现网络服务描述符(NSD,NS Descriptor)，虚拟网络功能转发图(VNFFG,VNF Forwarding Graph)的管理和处理，网络服务(NS,Network Service)生命周期的管理，和VNFM配合实现VNF的生命周期管理并具有虚拟资源的全局视图功能。
VNF管理器(VNFM,VNF Manager)可执行虚拟化网络功能VNF的生命周期管理，包括虚拟化网络功能描述符(VNFD,VNF Descriptor)的管理、VNF的实例化(instantiation)、VNF实例的弹性伸缩(可包括扩容Scaling out/up和缩容Scaling in/down)、VNF实例的治愈(healing)和VNF实例终止(termination)。VNFM还支持接收NFVO下发的弹性伸缩(scaling)策略，实现自动化的VNF弹性伸缩。
虚拟基础设施管理器(VIM,Virtualised Infrastructure Manager)主要负责基础设施层虚拟化资源(包括虚拟计算、存储和网络资源)的管理(包括预留和分配)，虚拟资源状态的监控和故障上报，面向上层应用提供虚拟化资源池。
运营和商务支撑系统(OSS/BSS,Operations and Business Support Systems)可指运营商的运行维护系统OSS/BSS。
网元管理系统(EM,Element Manager)针对VNF执行传统的故障(Fault)、用户(Account)和配置(Configuration)、性能(Performance)和安全(Security)的管理(可简称：FCAPS管理)功能。
虚拟化网络功能(VNF,Virtualized Network Function)对应于传统非虚拟化网络中的物理网络功能(PNF)，如虚拟化的EPC节点(分组网关、服务网关等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
NFV基础架构(NFVI,NFV Infrastructure)是NFV功能的基础设施层，由硬件资源和虚拟资源以及虚拟化层组成。从VNF的角度来说，虚拟化层和硬件资源是一个能够提供所需虚拟资源的完整实体。
NFV领域的管理对象信息模型围绕VNF的功能模型、部署模型和资源模型展开描述，具体可如图2所示。
其中，在图2举例所示的功能模型(也称为功能视图)中，NFV领域最高阶的管理对象是网络服务(NS,Network Service)，每个NS可由一个或多个VNF组成。进一步地，每个VNF又 可以由一个或多个更低功能级别的VNF组件(VNFC,VNF Component)来组成。NS仅对NFVO可见，而VNF对NFVO和VNFM都可见，VNFC仅对VNFM可见。
在部署模型(也称为部署视图)中，同一类的VNF(例如vMME或vPGW等等)唯一对应VNF描述符文件(VNFD)，并使用该VNFD创建一个或多个VNF实例。在VNFD中可包含一个或多个更细颗粒的虚拟化部署单元(VDU,Virtualized Deployment Unit)，每个VDU唯一对应一类VNFC，其中包含该类VNFC部署和运行所需的描述信息。
在资源模型(也称为资源视图)中，NFVI的虚拟化层将底层的硬件资源(或称为物理资源)抽象并封装为虚拟机(VM,Virtual Machine)。VNF可部署在多个VM上，每个VM唯一承载一个VNFC的功能，当然VNF也可部署在一个VM上。在VNFD中，每个VDU描述一类VNFC对基础设施层虚拟资源(Infrastructure Resource)的需求，而VIM分配的VM则封装了满足该需求的基础设施层虚拟资源的信息。从功能模型到部署模型到资源模型，VNFC和VDU、VM之间形成了一一映射关系。主机(host)是硬件资源，在一个主机上可切分创建一个或多个VM实例。VM对NFVO和VNFM都可见，而主机资源对NFVO和VNFM不可见。
CaaS架构在电信网络功能云化进程中的引入,为电信行业的开发运维(DevOps)带来了敏捷性的变革。与之相呼应的变化是，传统大颗粒单体网络功能逐渐被解构进行服务化，甚至进一步进行微服务化。每个服务化的功能独立进行开发、交付和维护，版本的升级变得更加频繁；但另一方面，容器化网络功能数量的激增，并不会对互操作测试带来指数级工作量的增长，稳定的API接口定义保证了接口功能调用的一致性和可靠性。
当前在容器管理编排领域最流行的应用是Google公司基于开源平台的Kubernetes(简称K8S)容器集群管理技术。它的核心思想是“一切以服务为中心，一切围绕服务运转”，遵循这一思想，在Kubernetes上构建的容器应用系统不仅可以独立运行在物理机、虚拟机或企业私有云上，也可以被托管到公有云上。Kubernetes的另一个特点是自动化，一个服务可自我扩缩容、自我诊断，并且容易升级。Kubernetes容器管理编排可如图3举例所示。
容器管理编排是电信网络功能虚拟化(NFV)向云原生(CloudNative)演进中的一个重要的底座架构增强特性，通过连接NFV MANO系统和业内应用成熟的容器管理平台(如Kubernetes)形成互操作的标准化场景，从架构功能保障容器化VNF在DevOps的持续交付。现有技术尚未对引入容器后的NFV管理对象信息模型的增强展开详细分析。
IFA029研究报告提出的MANO管理容器的目标架构如图5举例所示。容器服务是从VNF功能中剥离出来形成独立一层的基础设施服务，容器管理器(Container Manager)采用事实标准(例如Kubernetes API)和容器服务之间交互，为容器化VNF的生命周期管理提供所需的容器基础设施服务(CIS,Container Infrastructure Service)。其中，容器管理器在北向接口上为NFVO或VNFM提供容器对象或容器对象包(例如：Kubernetes的Pod或Helm的Chart对象等)的管理功能，这些容器对象进一步组成容器化VNF。在IFA029报告中，容器管理器中也称为容器基础设施服务管理(CISM,Container Infrastructure Service Management)，容器服务也称为容器基础设施服务(CIS,Container Infrastructure Service)。
IFA029研究报告在容器所使用的基础设施资源(infrastructure resource，基础设施资源可以是虚机或裸机等)之上引入了服务资源(service resource)的概念。其中，服务 资源是指被容器对象所使用的逻辑资源，映射到Kubernetes中对应的是一个命名空间下使用的资源配额(resource quota)。其中，服务资源的引入使得容器底层的基础设施资源和容器化VNF进行解耦，VNF的设计者将更关注从VNF的功能逻辑向容器对象功能逻辑的映射实现，而无需陷入基础设施资源(例如：虚机)的创建和分配的细节，充分利用了Kubernetes自治管理节点资源的能力，实现容器化VNF的敏捷开发和运维。
服务资源对NFVO或VNFM而言是可见的，而基础设施资源(虚机或裸机)在服务资源的隔离作用下变得对NFVO或VNFM不再可见。其中，虽然服务资源是面向容器对象定义的抽象的逻辑资源，但事实上服务资源的管理依然可以参照ETSI NFV标准中对基础设施资源的管理模式来管理，即：采用直接模式或间接模式进行服务资源管理。目前，IFA029报告并没有对容器使用的服务资源管理开展详细研究。特别地，如何在抽象的容器对象层描述服务资源、界定服务资源对容器对象的作用边界，将影响如何复用现有的基础设施资源管理模式对服务资源进行管理。
本申请实施例还提供的一种容器化VNF的信息模型可如图4所示。其中，容器化VNF的资源模型引入了由容器对象(例如：Kubernetes中的Pod、Service或Deployment对象)组成抽象的逻辑资源层(如图4中的资源模型中的server resource)。逻辑资源层将基础设施资源(例如VM资源)和基于容器实现的VNF隔离，NFV MANO系统管理逻辑资源层的容器对象，而无需管理基础设施资源，基础设施资源的管理留给NFVI实现。
与基于图2所示的VM的VNF信息模型相比，图4举例所示VNF的资源模型在基础设施资源上封装了抽象的由容器对象组成的逻辑资源，即服务资源(service resource)。
具体例如图4举例所示，服务资源中包含的经过抽象的容器对象，也称为被管理的容器基础设施对象(MCIO,Managed Container Infrastructure Object)，这些抽象的被管理的容器对象可具体映射为开源领域容器事实标准的容器对象，具体例如Kubernetes中的Pod、Service或Deployment、ReplicaSets、StatefulSets等等。
本申请实施例提出一些服务资源的许可(granting)管理方法，当VNFM执行容器化VNF的生命周期管理操作时，VNFM先向VNFO发起服务资源的许可请求，NFVO对该VNF生命周期管理操作中容器对象所使用的服务资源进行许可，有效地避免在网络服务(NS,Network Service)中各成员VNF使用的服务资源因超出预先设定的配额而在NS层面形成服务资源使用的冲突。
参见图2，在IFA029研究报告中，服务资源被定义为被容器对象所使用的逻辑资源，映射到Kubernetes中对应的是一个命名空间下使用的资源配额(resource quota)。对应到容器化VNF的管理场景，命名空间可映射为VNF实例或NS实例。
在本申请实施例方案中的服务资源可以具有如下定义：
容器化VNF实例的服务资源：指这个容器化VNF实例调用的容器对象包中所包含的容器对象的总数(也可称为配额或数量上限)。
NS实例的服务资源：指这个NS实例所包含的所有成员组件(如嵌套NS和容器化VNF实例等)所使用的容器对象的总数(也可称为配额或数量上限)。
以下举例说明上述容器化VNF实例服务资源和NS实例服务资源的概念。
一个容器化VNF的实例化过程请求3个容器包文件(每个包文件由各自的Helm Chart模 板定义)。实例化后的该VNF实例将与3个容器包实例(例如：Helm Release)对应，而这三个容器包实例中分别包含不同数量的容器对象，例如：包实例1中包含2个Kubernetes Deployment对象，包实例2中包含3个Kubernetes Pod对象，包实例3中包含2个Kubernetes Service对象和1个Kubernetes Deployment对象和1个ReplicaSets对象。如果这个容器化VNF实例的服务资源被设置为10(总数/配额)，而当前这个容器化VNF实例所调用的容器对象包所包含的容器对象的总数是9(2+3+2+1+1)，故而符合这个容器化VNF实例的服务资源设置，在这种容器对象数量的形态下，容器化VNF实例的运行是许可的。
相应的，在一个运行的NS实例中，组成该NS实例的所有VNF实例和嵌套NS实例所使用的服务资源不能超过该NS实例设置的服务资源。
由于容器对象层不同类型的容器对象(如：Kubernetes Deployment和Pod之间，Service和Pod之间)的功能颗粒和使用的基础设施资源的数量有较大的区别，因此，容器化VNF实例的服务资源可归一化为该容器化VNF实例调用的容器对象包中所包含的容器对象映射的最小颗粒容器对象的总数，例如：在Kubernetes中将不同的容器对象数量都映射为Pod数量，或者更细颗粒的OS container数量(通常地，OS container被Pod封装，对其他的Kubernetes对象不可见)。NS实例的服务资源也可以归一化为该NS实例所包含的所有成员组件(如嵌套NS和容器化VNF实例等)所使用的容器对象映射的最小颗粒容量对象的总数。
考虑到后向兼容的要求，容器化VNF实例的服务资源还可以定义为该容器化VNF实例调用的容器对象包中所包含的容器对象所使用的基础设施资源(例如如：虚拟计算、存储和网络资源)的数量总和，这方面在本申请方案中不再赘述。
以上描述是对本申请实施例方案中的服务资源的定义举例。
基于上述举例的架构和相关概念，下面举例提供一些服务资源许可(grant ing)管理方法的相关流程。
参见图6，图6为本申请实施例提供的一种服务资源许可管理方法的流程示意图，一种服务资源的许可管理方法可包括：
601.例如NFVO或EM向VNFM发送VNF生命周期管理操作请求，所述VNF生命周期管理操作请求可用于触发启动容器化VNF实例的生命周期管理操作。
602.VNFM接收来自例如NFVO或EM的容器化VNF实例的VNF生命周期管理操作请求，所述VNFM从VNFD中读取所述容器化VNF实例在生命周期管理操作中请求使用的服务资源。
603.VNFM向NFVO发送VNF生命周期操作许可请求。所述VNF生命周期操作许可请求中携带所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。
604.NFVO接收来自VNFM的VNF生命周期操作许可请求，所述NFVO向VNFM发送VNF生命周期操作许可应答。
举例来说，NFVO向VNFM发送VNF生命周期操作许可应答之前还包括：所述NFVO判断所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，与所述容器化VNF实例所属的NS实例的服务资源之间的关系。在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的NS实例的服务资源的情况下，所述VNF生命周期操作许可应答可携带成功指示。在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的网络服务NS实例的服务资源 的情况下，所述VNF生命周期操作许可应答可携带失败指示。其中，所述NS实例的服务资源，可以为所述NS实例所包含的所有成员VNF实例和/或所有成员嵌套NS实例所调用的容器对象包中所包含的容器对象的总数(配额)。
605.所述VNFM接收来自所述NFVO的VNF生命周期操作许可应答。
其中，所述VNF生命周期管理许可应答可携带由所述NFVO许可的所述VNF实例在所述生命周期管理操作中语序使用的服务资源。其中，所述NFVO许可的所述VNF实例在所述生命周期管理操作中允许使用的服务资源，大于或等于或小于所述VNF生命周期操作许可请求中携带的所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源。
此外，当VNF生命周期操作许可应答携带失败指示，NFVO可进一步在应答消息中携带其推荐使用的服务资源。
其中，当所述VNF生命周期管理许可应答携带成功指示，VNFM向容器管理平台CISM发送容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过由所述NFVO许可的所述VNF实例在所述生命周期管理操作中允许使用的服务资源。
606.CISM接收来自VNFM的容器对象包的管理操作请求。所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
其中，所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，例如可包括：当CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，CISM判断要扩充的容器对象的数量与所述容器化VNF实例中正在运行的容器对象的数量之和，不能超过所述容器对象包的服务资源。
上述举例方案中，当VNFM执行容器化VNF的生命周期管理操作时，VNFM先向VNFO发起VNF服务资源许可请求，NFVO对容器化VNF实例生命周期管理操作中容器对象所使用的服务资源进行许可，这样有利于有效地避免在网络服务中各成员VNF使用的服务资源因超出预先设定的配额而在NS层面形成服务资源使用的冲突，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
参见图7，图7为本申请实施例提供的另一服务资源许可管理方法的流程示意图，另一服务资源的许可管理方法可包括：
701.NFVO向VNFM发送针对VNF生命周期管理操作的服务资源批量许可请求，服务资源批量许可请求中携带NFVO授予VNFM管理的批量服务资源。
其中，VNFM管理的批量服务资源例如可以是一个包括上下门限的范围，即VNFM管理的批量服务资源不能超过该范围所确定数值的上下边界。
其中，NFVO向VNFM发送针对VNF生命周期管理操作的服务资源批量许可请求之前，NFVO可基于NS生命周期管理的全局考虑，确定将批量的容器服务授予VNFM进行管理。批量的服务资源可用于VNFM所管理的任何容器化VNF实例的生命周期管理操作中，在任何时候VNFM所管理的所有容器化VNF实例所使用的服务资源总数不能超过NFVO授予的批量服务资源。
702.VNFM接收来自NFVO的针对VNF生命周期管理操作的服务资源批量许可请求。VNFM向NFVO返回针对VNF生命周期管理操作的服务资源批量许可应答，所述服务资源批量许可应答可携带成功指示或失败指示。
703.当服务资源批量许可应答携带成功指示，那么，在VNFM执行容器化VNF生命周期管理操作时，VNFM向容器管理平台发送容器对象包的管理操作请求。
704.容器管理平台接收来自VNFM的容器对象包的管理操作请求，所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，例如可包括：当CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，CISM判断要扩充的容器对象的数量和所述容器化VNF实例中正在运行的容器对象的数量不能超过NFVO授予的批量服务资源。
可以看出，上述流程提供了一种便捷的服务资源的批量许可管理机制，有利于简化容器化VNF实例生命周期管理过程的交互复杂度。
参见图8，图8为本申请实施例提供的另一服务资源许可管理方法的流程示意图，另一服务资源的许可管理方法可包括：
801.例如NFVO或EM向VNFM发送VNF生命周期管理操作请求，以触发启动容器化VNF实例的生命周期管理操作。
802.VNFM接收来自NFVO或EM的VNF生命周期管理操作请求，VNFM向NFVO发送第一服务资源管理请求，所述第一服务资源管理请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。
803.NFVO接收来自VNFM的第一服务资源管理请求。所述NFVO向容器管理平台CISM发送第二服务资源管理请求，所述第二服务资源管理请求携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
804.CISM接收来自NFVO的第二服务资源管理请求，容器管理平台向所述NFVO发送第二服务资源管理应答。
所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。所述容器对象包的服务资源不超过被NFVO许可的所述VNF实例在生命周期管理操作中所使用的服务资源。
所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，例如可包括：当CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，CISM判断要扩充的容器对象的数量和所述容器化VNF实例中正在运行的容器对象的数量不能超过NFVO授予的批量服务资源。
805.所述NFVO在接收到容器管理平台发送的第二服务资源管理应答之后，向VNFM发送第一服务资源管理应答，所述第一服务资源管理应答中携带由所述NFVO许可的所述容器化 VNF实例在所述生命周期管理操作中允许使用的服务资源。
在一些可能实施方式中，NFVO向CISM发送第二服务资源管理请求之前，可还包括：在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况之下，所述NFVO许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，其中，所述允许使用的服务资源等于所述请求使用的服务资源。
在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述NFVO确定其许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，所述允许使用的服务资源小于所述请求使用的服务资源。或者，在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述NFVO可拒绝许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
上述举例方案中，当VNFM触发执行容器化VNF实例的生命周期管理操作时，由NFVO来统一的对容器化VNF实例的生命周期管理操作中容器对象使用的服务资源进行许可，CISM使用不超过被NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源的容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，这样有利于避免网络服务中各成员VNF使用的服务资源因超出相关预设配额而在NS层面形成服务资源使用冲突，进而有利于从网络服务的角度有效管理容器化VNF实例使用的服务资源。
下面还提供一些设备实施例。
参见图9，本申请实施例提供的一种虚拟化网络功能管理器VNFM 900，包括：
接收单元910，用于接收容器化VNF实例的生命周期管理操作请求。
读取单元920，用于从虚拟化网络功能描述符VNFD中读取所述容器化VNF实例在生命周期管理操作中请求使用的服务资源；
发送单元930，用于向网络功能虚拟化编排器NFVO发送VNF生命周期操作许可请求，所述VNF生命周期操作许可请求中携带所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源；
接收单元910还用于，接收来自所述NFVO的VNF生命周期操作许可应答。
在一些可能的实施方式中，所述容器化VNF实例的服务资源为所述VNF实例调用的容器对象包中所包含的容器对象的总数。
在一些可能的实施方式中，所述VNF生命周期管理许可应答还携带由所述NFVO许可的所述VNF实例在所述生命周期管理操作中允许使用的服务资源。
在一些可能的实施方式中，发送单元930还用于，当所述VNF生命周期管理许可应答携带成功指示，向容器管理平台CISM发送容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过由所述NFVO许可的所述VNF实例在所述生命周期管理操作中允许使用的服务资源。
参见图10，本申请实施例提供的一种网络功能虚拟化编排器NFVO 1000，包括：
接收单元1010，用于接收来自VNFM的VNF生命周期操作许可请求，所述生命周期操作许可请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源。
发送单元1020，用于向VNFM发送VNF生命周期操作许可应答。
在一些可能的实施方式中，所述容器化VNF实例的服务资源为所述VNF实例调用的容器对象包中所包含的容器对象的总数。
在一些可能的实施方式中，还包括判断单元1030，用于在向VNFM发送VNF生命周期操作许可应答之前，判断所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，与所述容器化VNF实例所属的NS实例的服务资源之间的关系。
在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况下，所述VNF生命周期操作许可应答携带成功指示。
在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况下，所述VNF生命周期操作许可应答携带失败指示。
在一些可能的实施方式中，所述NS实例的服务资源为所述NS实例所包含的所有成员VNF实例和/或所有成员嵌套NS实例所调用的容器对象包中所包含的容器对象的总数。
参见图11，本申请实施例提供的一种容器管理平台CISM 1100，包括：
接收单元1110，用于接收来自VNFM的容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过被NFVO许可的所述VNF实例在生命周期管理操作中所使用的服务资源；
监控单元1120，用于使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
在一些可能的实施方式中，监控单元具体用于，当CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，CISM判断要扩充的容器对象的数量和所述容器化VNF实例中正在运行的容器对象的数量不能超过所述容器对象包的服务资源。
在一些可能的实施方式中，所述容器化VNF实例的服务资源为所述VNF实例调用的容器对象包中所包含的容器对象的总数。
参见图12，本申请实施例提供的一种NFVO 1200，包括：
接收单元1210，用于接收来自VNFM的第一服务资源管理请求，所述第一服务资源管理请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源；
发送单元1220，用于向容器管理平台CISM发送第二服务资源管理请求，所述第二服务资源管理请求携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源；在接收单元接收到容器管理平台发送的第二服务资源管理应答之后，向VNFM发送第一服务资源管理应答，所述第一服务资源管理应答中携带由所述NFVO许可的所 述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
在一些可能的实施方式中，NFVO 1200还包括处理单元1230，用于在NFVO向容器管理平台CISM发送第二服务资源管理请求之前，在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过其所属的网络服务NS实例的服务资源的情况下，许可所述VNF实例在所述生命周期管理操作中请求使用的服务资源；在所述VNF实例在所述生命周期管理操作中请求使用的服务资源超过所述VNF实例所属的NS实例的服务资源的情况下，其许可的所述VNF实例在所述生命周期管理操作中所使用的服务资源。
在一些可能的实施方式中，所述VNF实例的服务资源为所述VNF实例调用的容器对象包中所包含的容器对象的总数。
参见图13，本申请实施例还提供一种通用的通信设备1300，该通信设备1300可以实现以上实施例提供的VNFM、NFVO或容器管理平台的功能，具体包括：
相互耦合的处理器1310和存储器1320。
其中，处理器1310用于调用存储器1320存储的计算机程序，以完成本申请实施例中由VNFM执行的任意一种方法的部分或全部步骤。
此外，处理器1310也可以调用存储器1320中存储的不同计算机程序，完成本申请实施例中由NFVO或容器管理实体执行的任意一种方法的部分或全部步骤。
其中，处理器1210还称中央处理单元(CPU，Central Processing Unit)。具体的应用中图像预测装置的各组件例如通过总线系统耦合在一起。其中，总线系统除了可包括数据总线之外，还可包括电源总线、控制总线和状态信号总线等。但是为清楚说明起见，在图中将各种总线都标为总线系统730。上述本申请实施例揭示的方法可应用于处理器1310中，或由处理器1310实现。处理器1310可能是一种集成电路芯片，具有信号的处理能力。在一些实现过程之中，上述方法的部分或全部步骤可通过处理器1310中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1310可以是通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。处理器1310可实现或执行本申请实施例中公开的各方法、步骤及逻辑框图。通用处理器1310可为微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可直接体现为硬件译码处理器执行完成，或用译码处理器中的硬件及软件模块组合执行完成。软件模块可位于随机存储器，闪存、只读存储器，可编程只读存储器、电可擦写可编程存储器或寄存器等等本领域成熟的存储介质之中。该存储介质位于存储器1320，例如处理器1310可读取存储器1320中的信息，结合其硬件完成上述方法的部分或全部步骤。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被硬件(例如处理器等)执行，以本申请实施例中由任意设备执行的任意一种方法的部分或全部步骤。
本申请实施例还提供了一种包括指令的计算机程序产品，当所述计算机程序产品在计算机设备上运行时，使得所述这个计算机设备执行以上各方面的任意一种方法的部分或者全部步骤。
在上述实施例中，可全部或部分地通过软件、硬件、固件、或其任意组合来实现。当 使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如软盘、硬盘、磁带)、光介质(例如光盘)、或者半导体介质(例如固态硬盘)等。在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在上述实施例中，对各实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，也可以通过其它的方式实现。例如以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可结合或者可以集成到另一个系统，或一些特征可以忽略或不执行。另一点，所显示或讨论的相互之间的间接耦合或者直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者，也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例的方案的目的。
另外，在本申请各实施例中的各功能单元可集成在一个处理单元中，也可以是各单元单独物理存在，也可两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，或者也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质例如可包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或光盘等各种可存储程序代码的介质。

Claims (18)

  1. 一种服务资源许可管理方法，其特征在于，包括：虚拟化网络功能管理器VNFM接收容器化虚拟网络功能VNF实例的生命周期管理操作请求；
    所述VNFM从虚拟化网络功能描述符VNFD中读取所述容器化VNF实例在生命周期管理操作中请求使用的服务资源；
    所述VNFM向网络功能虚拟化编排器NFVO发送VNF生命周期操作许可请求，所述VNF生命周期操作许可请求之中携带有所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源；
    所述VNFM接收来自所述NFVO的VNF生命周期操作许可应答。
  2. 根据权利要求1所述的方法，其特征在于，所述容器化VNF实例的服务资源为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：所述VNF生命周期管理许可应答还携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    当所述VNF生命周期管理许可应答携带成功指示，所述VNFM向容器管理平台CISM发送容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
  5. 一种服务资源许可管理方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收来自虚拟网络功能管理器VNFM的虚拟网络功能VNF生命周期操作许可请求，其中，所述VNF生命周期操作许可请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源；
    所述NFVO向VNFM发送VNF生命周期操作许可应答。
  6. 根据权利要求5所述的方法，其特征在于，所述容器化VNF实例的服务资源为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数。
  7. 根据权利要求5或6所述的方法，其特征在于，所述NFVO向VNFM发送VNF生命周期操作许可应答之前，还包括：所述NFVO判断所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，与所述容器化VNF实例所属的网络服务NS实例的服务资源之间的关系；
    其中，在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述VNF生命周期操作许可应答携带成功指示；在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况之下，所述VNF生命周期 操作许可应答携带失败指示。
  8. 根据权利要求7所述的方法，其特征在于，所述NS实例的服务资源，为所述NS实例所包含的所有成员VNF实例和/或所有成员嵌套NS实例所调用的容器对象包中所包含的容器对象的总数。
  9. 一种服务资源许可管理方法，其特征在于，包括：容器管理平台CISM接收来自虚拟化网络功能管理器VNFM的容器对象包的管理操作请求，所述管理操作请求携带所述容器对象包的服务资源，所述容器对象包的服务资源不超过被网络功能虚拟化编排器NFVO许可的容器化VNF实例在生命周期管理操作中允许使用的服务资源；
    所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控。
  10. 根据权利要求9所述的方法，其特征在于，
    所述CISM使用所述容器对象包的服务资源，对所述容器化VNF实例在生命周期管理过程中所使用的所述容器对象包下的容器对象进行监控，包括：
    当所述CISM通过监控容器对象的运行情况并决定扩充容器对象的数量以对容器化VNF实例进行扩容时，所述CISM判断要扩充的容器对象的数量与所述容器化VNF实例中正在运行的容器对象的数量之和不能超过所述容器对象包的服务资源。
  11. 根据权利要求9或10所述的方法，其特征在于，所述容器化VNF实例的服务资源为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数。
  12. 一种服务资源许可管理方法，其特征在于，包括：网络功能虚拟化编排器NFVO接收来自虚拟化网络功能管理器VNFM的第一服务资源管理请求，所述第一服务资源管理请求中携带容器化VNF实例在生命周期管理操作中请求使用的服务资源；
    所述NFVO向容器管理平台CISM发送第二服务资源管理请求，其中所述第二服务资源管理请求携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源；
    所述NFVO在接收到来自所述CISM的第二服务资源管理应答之后，向所述VNFM发送第一服务资源管理应答，所述第一服务资源管理应答中携带由所述NFVO许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源。
  13. 根据权利要求12所述的方法，其特征在于，所述NFVO向CISM发送第二服务资源管理请求之前，还包括：
    在所述容器化VNF实例在所述生命周期管理操作中请求使用的服务资源，未超过所述容器化VNF实例所属的网络服务NS实例的服务资源的情况之下，所述NFVO许可所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，所述允许使用的服务资源等于所述请求使用的服务资源；
    在所述VNF实例在所述生命周期管理操作中请求使用的服务资源，超过所述容器化VNF实例所属的NS实例的服务资源的情况之下，所述NFVO确定其许可的所述容器化VNF实例在所述生命周期管理操作中允许使用的服务资源，所述允许使用的服务资源小于所述请求使 用的服务资源。
  14. 根据权利要求12或13所述的方法，其特征在于，所述容器化VNF实例的服务资源为所述容器化VNF实例调用的容器对象包中所包含的容器对象的总数。
  15. 一种虚拟网络功能管理器VNFM，其特征在于，包括：
    相互耦合的处理器和存储器；
    其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成权利要求1至4任意一项所述的方法。
  16. 一种网络功能虚拟化编排器NFVO，其特征在于，包括：
    相互耦合的处理器和存储器；
    其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成权利要求5至8或12至14任意一项所述的方法。
  17. 一种容器管理平台CISM，其特征在于，包括：
    相互耦合的处理器和存储器；
    其中，所述处理器用于调用所述存储器中存储的计算机程序，以完成权利要求9至14任意一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，
    所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时能够完成权利要求1至14任意一项所述的方法。
PCT/CN2020/098854 2019-07-11 2020-06-29 服务资源许可管理方法和相关设备 WO2021004320A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910625039.5A CN112217654B (zh) 2019-07-11 2019-07-11 服务资源许可管理方法和相关设备
CN201910625039.5 2019-07-11

Publications (1)

Publication Number Publication Date
WO2021004320A1 true WO2021004320A1 (zh) 2021-01-14

Family

ID=74048155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/098854 WO2021004320A1 (zh) 2019-07-11 2020-06-29 服务资源许可管理方法和相关设备

Country Status (2)

Country Link
CN (1) CN112217654B (zh)
WO (1) WO2021004320A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116450301A (zh) * 2023-06-14 2023-07-18 天津市天河计算机技术有限公司 基于容器的监控方法、系统、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018090299A1 (zh) * 2016-11-17 2018-05-24 华为技术有限公司 网络服务生命周期管理的许可方法和装置
CN108471373A (zh) * 2017-02-23 2018-08-31 华为技术有限公司 一种资源申请、vnf实例创建方法及装置
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
US20190052549A1 (en) * 2016-05-06 2019-02-14 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017014803A1 (en) * 2015-07-23 2017-01-26 Intel Corporation Network resource model to support network function virtualization lifecycle management
WO2017113201A1 (zh) * 2015-12-30 2017-07-06 华为技术有限公司 一种网络服务的生命周期管理方法及设备
CN105955824B (zh) * 2016-04-21 2019-07-19 华为技术有限公司 一种虚拟资源配置方法以及装置
CN108207008A (zh) * 2016-12-19 2018-06-26 中兴通讯股份有限公司 一种虚拟化网元的管理方法和装置
US10833957B2 (en) * 2018-01-16 2020-11-10 Intel Corporation Managing physical network function instances in a network service instance

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190052549A1 (en) * 2016-05-06 2019-02-14 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels
WO2018090299A1 (zh) * 2016-11-17 2018-05-24 华为技术有限公司 网络服务生命周期管理的许可方法和装置
CN108471373A (zh) * 2017-02-23 2018-08-31 华为技术有限公司 一种资源申请、vnf实例创建方法及装置
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on network management of virtualized networks (Release 13)", 3GPP STANDARD; 3GPP TR 32.842, vol. SA WG5, no. V13.0.0, 30 September 2015 (2015-09-30), pages 1 - 84, XP050996350 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116450301A (zh) * 2023-06-14 2023-07-18 天津市天河计算机技术有限公司 基于容器的监控方法、系统、设备及介质
CN116450301B (zh) * 2023-06-14 2023-08-15 天津市天河计算机技术有限公司 基于容器的监控方法、系统、设备及介质

Also Published As

Publication number Publication date
CN112217654A (zh) 2021-01-12
CN112217654B (zh) 2022-06-07

Similar Documents

Publication Publication Date Title
US11354167B2 (en) Container service management method and apparatus
WO2020228838A1 (zh) 容器化vnf的部署方法和相关设备
US10701139B2 (en) Life cycle management method and apparatus
WO2016165292A1 (zh) 一种实现虚拟网络功能部署规格配置的方法及装置
WO2017080391A1 (zh) 一种网络服务部署方法和装置
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
CN109428764B (zh) 虚拟网络功能的实例化方法
CN112148422A (zh) 一种io处理的方法和装置
US11871280B2 (en) VNF instantiation method, NFVO, VIM, VNFM, and system
WO2020011214A1 (zh) 管理虚拟化资源的方法和装置
US11411821B2 (en) Driver upgrade method and device
US11301284B2 (en) Method for managing VNF instantiation and device
WO2019207156A1 (en) Method and arrangement for licence management in nfv network environment
WO2021063130A1 (zh) 网络资源管理方法、系统、网络设备和可读存储介质
WO2022100365A1 (zh) 人工智能应用任务的管理方法、系统、设备及存储介质
WO2021004320A1 (zh) 服务资源许可管理方法和相关设备
EP4177742A1 (en) Multitenancy management method and apparatus
CN110795202A (zh) 一种虚拟化集群资源管理系统的资源分配方法以及装置
CN116724543A (zh) 容器集群的管理方法和装置
CN114816665B (zh) 混合编排系统及超融合架构下虚拟机容器资源混合编排方法
CN109218259B (zh) 许可管理方法及装置、applm功能实体及计算机可读存储介质
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN109582464B (zh) 一种云平台管理多种虚拟化平台的方法和装置
WO2021129520A1 (zh) 网络业务的生命周期管理的授权方法及装置
WO2023274014A1 (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: 20836173

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20836173

Country of ref document: EP

Kind code of ref document: A1