WO2019001140A1 - 一种管理vnf实例化的方法和设备 - Google Patents

一种管理vnf实例化的方法和设备 Download PDF

Info

Publication number
WO2019001140A1
WO2019001140A1 PCT/CN2018/085750 CN2018085750W WO2019001140A1 WO 2019001140 A1 WO2019001140 A1 WO 2019001140A1 CN 2018085750 W CN2018085750 W CN 2018085750W WO 2019001140 A1 WO2019001140 A1 WO 2019001140A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
instantiated
instance
request
instantiating
Prior art date
Application number
PCT/CN2018/085750
Other languages
English (en)
French (fr)
Inventor
李世涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18823763.0A priority Critical patent/EP3629160B1/en
Publication of WO2019001140A1 publication Critical patent/WO2019001140A1/zh
Priority to US16/725,579 priority patent/US11301284B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of cloud computing technologies, and in particular, to a method and device for managing VNF instantiation.
  • Network Function Virtualization (English: Network Function Virtualization, NFV for short) refers to the use of common hardware devices and virtualization technologies to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive cost of deploying dedicated devices.
  • the software is not tied to proprietary hardware, making device functionality no longer dependent on dedicated hardware.
  • NFV introduces a virtualization layer to realize the lifecycle management of virtualized network functions (VNF) and virtualized network services (NS) through network management and orchestration.
  • VNF virtualized network functions
  • NS virtualized network services
  • the NS is the upper layer network service implemented by one or more VNFs.
  • an IP Multimedia Subsystem (IMS) network service or an Evolved Packet Core (EPC) network service. That is to say, an NS can consist of one or more VNFs.
  • IMS IP Multimedia Subsystem
  • EPC Evolved Packet Core
  • the NS deployment template (NSD), also called the NS deployment template, may be sent to the resource management entity.
  • the resource management entity may be a network function virtualization compiler (English: NFV Orchestrator, referred to as: NFVO).
  • the NSD mainly describes the topology of the NS and the description information (VNF descriptor, VNFD) of each VNF included.
  • VNFD virtual link descriptor
  • VNFD is a description of the VNF, also known as the deployment template of the VNF.
  • VNFD describes the composition of each VNF, such as running software, virtual resource information needed, and so on.
  • Virtual resources include CPU resources, storage resources, and the like.
  • the service requester can request the resource management entity to instantiate the NS based on the NSD.
  • the instantiation of NS refers to the creation of an NS instance.
  • the resource management entity may initiate instantiation of the required VNF according to the VNFD in the NSD, or may use an existing VNF instance.
  • Instantiation of a VNF refers to the creation of a VNF instance.
  • VNF In the scheme of instantiating VNF through EM, since the EM does not have the relevant information of the NS, the VNF cannot be associated with the NS in the process of instantiating the VNF, which causes the VNF instantiated by the EM to be unable to provide external services because VNF is only a virtualized network function that constitutes NS. Only NS can provide specific network services. VNF independent of NS cannot provide external services. If EM instantiates a large number of VNFs that are independent of NS, it will inevitably result in waste of resources. Therefore, it is necessary to control the EM instantiated VNF.
  • the embodiment of the invention provides a method and a device for managing VNF instantiation to avoid resource waste.
  • an embodiment of the present invention provides a method for managing VNF instantiation, which includes two stages of NS instantiation and VNF instantiation.
  • the requesting device carries the instance information of the virtualized network function VNF that needs to be instantiated by the second device in the NS in the request for instantiating the NS initiated by the first device.
  • the instance information includes an instance identifier of the VNF and status information indicating that the VNF is to be instantiated by the second device.
  • the first device determines, according to the status information, the VNF to be instantiated by the second device in the NS, and records the VNF that needs to be instantiated by the second device. Instance ID.
  • the first device authorizes the instantiation of the VNF according to the instance identifier of the VNF recorded in the NS instantiation process.
  • the first device can learn the relationship between the VNF and the NS instantiated by the second device, so that Relationships to control the instantiation of VNF. That is, the VNF is allowed to be instantiated only if the VNF is related to the NS. Ensure that the second device instantiates a valid VNF and avoids wasting resources.
  • the requesting device obtains an instance identifier of the VNF that needs to be instantiated by the second device in the NS obtained by the second device from the virtual network function manager VNFM before initiating the request to instantiate the NS.
  • the embodiment of the present invention places the instance ID of the VNF instantiated by the second device before the request to initiate the instantiation of the NS, so that the requesting device can carry the instance ID of the VNF instantiated by the second device in the instantiated NS.
  • the request is sent to the first device, so that the first device acquires the relationship between the NS to be instantiated and the VNF that needs to be instantiated by the second device.
  • the first device authorizes the instantiation of the VNF according to the instance identifier of the VNF recorded in the NS instantiation process, and specifically includes: the VNMF sends the second device to receive An authorization request initiated to the first device after instantiating the request of the VNF.
  • the authorization request is for requesting the NFVO to authorize the VNFM to perform an operation of instantiating the VNF, where the instance identifier of the VNF is carried.
  • the first device determines whether the condition for instantiating the VNF is satisfied.
  • the condition includes the instance identifier of the VNF carried in the authorization request in the instance identifier of the VNF recorded when the NS is instantiated.
  • the first device After determining that the condition for instantiating the VNF is satisfied, the first device authorizes the VNMF to perform an operation of instantiating the VNF. Since the VNF is allowed to be instantiated only when the VNF is related to the NS, the second device instantiation cannot instantiate the invalid VNF and avoid resource waste.
  • the first device after determining that the condition for instantiating the VNF is satisfied, the first device further initiates a subscription request to the VNFM to subscribe to the VNF instance.
  • the subscription request is used to request the VNFM to send a notification message to the first device after instantiating the VNF.
  • the first device receives a notification message from the VNFM, the notification message is used to indicate that the VNF has been instantiated.
  • the subscription mechanism in the process of instantiating the NS, the first device can wait for other devices to instantiate the VNF in the NS in addition to instantiating the VNF by itself, so that the process of instantiating the NS is more flexible.
  • an embodiment of the present invention provides a method for managing VNF instantiation, the method comprising: requesting, by a requesting device, a request for instantiating a network service NS to a first device.
  • the requesting device carries, in the request, an instance identifier of the VNF that needs to be instantiated by the second device in the NS, and status information indicating that the VNF is to be instantiated by the second device.
  • the instance information is an instance identifier of the VNF to be instantiated by the second device, and is recorded in the first device.
  • the requestor device receives an NS instantiation operation response returned by the first device.
  • the requesting device After receiving the NS instantiation operation response returned by the first device, the requesting device requests the VNFM to instantiate the VNF by using the second device.
  • the instance identifier of the VNF recorded in the first device is used to instantiate an authorization determination of the VNF in the process of instantiating the VNF.
  • the requesting device carries the instance ID of the VNF instantiated by the second device in the request for instantiating the NS sent to the first device, so that the first device can learn the relationship between the VNF and the NS instantiated by the second device, thereby The instantiation of the VNF can be controlled according to the relationship. That is, the VNF is allowed to be instantiated only if the VNF is related to the NS. Ensure that the second device instantiates a valid VNF and avoids wasting resources.
  • the requesting device requests the VNFM to create an instance identifier of the VNF to be instantiated by the second device in the NS, and receives the VNFM creation by the second device before requesting the instantiation of the NS.
  • An instance identification of the VNF is a possible design.
  • the embodiment of the present invention places the instance ID of the VNF instantiated by the second device before the request to initiate the instantiation of the NS, so that the requesting device can carry the instance ID of the VNF instantiated by the second device in the instantiated NS.
  • the request is sent to the first device, so that the first device acquires the relationship between the NS to be instantiated and the VNF that needs to be instantiated by the second device.
  • the requesting device determines the VNF to be instantiated by the second device by querying the description information of the VNF in the deployment template of the NS.
  • the description information of the VNF includes an indication parameter.
  • the indication parameter is used to indicate whether the VNF is instantiated by the second device. Determining, by the requesting device, the VNF to be instantiated by the second device according to the indication parameter, and performing, by the second device, requesting the VNFM to create the NS, by using the second device instance. The operation of the instance identification of the VNF.
  • an embodiment of the present invention provides an apparatus for managing VNF instantiation, the apparatus having a function of implementing behavior of a first device in the foregoing method embodiment.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more components corresponding to the above functions (eg, a receiving unit for interacting with the requesting device, a processing unit for implementing NS instantiation, and during VNF instantiation) Authorized control unit).
  • an embodiment of the present invention provides an apparatus for managing VNF instantiation, the apparatus having a function of implementing behavior of a requesting device in the foregoing method embodiment.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more components corresponding to the above functions (eg, a transceiver unit for interacting with the first device, a processing unit for interacting with the second device, and for determining that the NS needs to pass The policy unit of the VNF instantiated by the second device).
  • an embodiment of the present invention provides a first device, which can be implemented based on a computer structure.
  • the first device comprises a memory and a processor.
  • the memory is used to store program instructions that implement the functions of the first device in the above method embodiments.
  • the processor is configured to execute program instructions in the memory to implement the functions of the first device in the foregoing method embodiment.
  • an embodiment of the present invention provides a requestor device, which can be implemented based on a computer structure.
  • the requestor device includes a memory and a processor.
  • the memory is used to store program instructions that implement the functions of the requesting device in the above method embodiments.
  • the processor is configured to execute program instructions in the memory to implement the functions of the requesting device in the foregoing method embodiment.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the first device, which includes a program designed to perform the above aspects for the first device.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the requestor device, including a program designed to perform the above aspects for a requesting device.
  • the embodiment of the present invention carries the instance ID of the VNF instantiated by the second device in the request for the instantiated NS sent to the first device, so that the first device can learn the relationship between the VNF and the NS instantiated by the second device. Therefore, the instantiation of the VNF can be controlled according to the relationship, ensuring that the second device instantiates an effective VNF and avoids waste of resources.
  • FIG. 1 is a schematic structural diagram of an NFV system according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for instantiating an NS according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for instantiating a VNF according to an embodiment of the present invention
  • FIG. 5 is a structural diagram of a first device according to an embodiment of the present disclosure.
  • FIG. 6 is a structural diagram of a requesting device according to an embodiment of the present invention.
  • FIG. 1 is a block diagram of an embodiment of an NFV system 100 including the following functional components:
  • the Network Function Virtualization Orchestrator (NFVO) 102 is mainly responsible for the lifecycle management of the NS and the allocation and scheduling of virtual resources in the network functions virtualization infrastructure (NFVI).
  • the NFVO 102 can communicate with one or more Virtualized Network Function Managers (VNFMs) 104, perform lifecycle management related operations such as VNF instantiation, and send configuration information to the VNFM 104, and request VNFM 104 to collect VNFs 108. Status information.
  • VNFMs Virtualized Network Function Managers
  • NFV 102 can also communicate with Virtualized Infrastructure Manager (VIM) 106, perform resource allocation, and/or reserve, exchange virtualized hardware resource configuration and status information.
  • VIP Virtualized Infrastructure Manager
  • the Virtual Network Function Manager (VNFM) 104 is responsible for lifecycle management of one or more VNFs, such as instantiating, updating, querying, scaling, and terminating the VNF 108.
  • the VNFM 104 can communicate with the VNF 108 to complete VNF lifecycle management and exchange configuration and status information.
  • Virtual Infrastructure Manager (VIM) 106 controls and manages the interaction of VNF 108 with computing hardware 112, storage hardware 114, network hardware 116, virtual computing 118, virtual storage 120, virtual network 122.
  • the VIM 106 performs resource management functions, including managing infrastructure resources, allocating (eg, adding resources to virtual containers), and running functions (eg, collecting NFVI failure information).
  • VNFM 104 and VIM 106 can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.
  • the Network Function Virtualization Infrastructure (NFVI), the infrastructure layer of NFV, consists of hardware components, software components, or a combination of both to establish a virtualized environment, deploy, manage, and implement VNF 108.
  • Hardware resources and virtualization layers are used to provide virtualized resources for VNF 108, such as virtual machines and other forms of virtual containers.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. As an embodiment, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • the virtualization layer in NFVI abstracts hardware resources and decouples VNF 108 from the underlying physical network layer.
  • Each Virtual Network Function (VNF) 108 running in one or more virtual containers, corresponds to a set of network functions belonging to one or more physical devices.
  • the device management system (EM) 110 is a system for configuring and managing devices in a traditional telecommunication system, and is mainly used for configuring, monitoring, and managing devices. In the NFV architecture, EM 110 can also be used to configure, monitor, and manage VNF instances. At the same time, the Operations Support System and Business Support System (OSS/BSS) 124 can also initiate a new VNF instantiation, VNF elastic scalability and other lifecycle management operations to the VNFM through the EM110.
  • OSS/BSS Operations Support System and Business Support System
  • the Operation Support System and Service Support System (OSS/BSS) 124 supports a variety of end-to-end telecommunications services.
  • the management functions supported by OSS include: network configuration, service provision, and fault management.
  • BSS handles orders, payments, revenues, etc., supporting product management, order management, revenue management and customer management.
  • NFVO 102 belongs to a resource management entity.
  • the instantiation of NS is the responsibility of the resource management entity.
  • a service requester e.g., OSS/BSS 124 in FIG. 1
  • the NS's description information can be sent to NFVO 102.
  • the NFVO 102 saves the NSD.
  • OSS/BSS 124 may request NFVO 102 to instantiate the NS based on the NSD.
  • the VNF that needs to be instantiated is confirmed according to the VNFD included in the NSD, and then the flow of instantiating the VNF is initiated to the VNFM. Since the flow of instantiating the VNF is triggered by the NFVO 102 in the process of instantiating the NS, the instantiated VNF is the VNF in the NS.
  • the instantiation of the VNF in addition to being initiated by the NFVO 102 in the process of instantiating the NS, may also be initiated by other devices outside of the process of instantiating the NS.
  • a service requester e.g., OSS/BSS 124 in FIG. 1
  • EM 110 shown in FIG. Since the instantiation of the VNF initiated by the EM 110 is not initiated during the instantiation of the NS, these VNFs are not present in any NS when instantiated.
  • the VNFM is the entity responsible for instantiating the VNF.
  • the VNFM may receive a request from the NFVO 102 or the instantiated VNF of the EM 110.
  • the VNFM requests resource authorization from a resource management entity (e.g., NFVO 102 in FIG. 1) responsible for the allocation and scheduling of virtual resources.
  • the resource authorization mainly refers to the virtual resources (for example, virtual CPU, virtual storage, virtual network, etc.) required by the NFVO 102 to confirm the VNF, whether it can be allocated, can be assigned to authorize, and cannot be assigned to deny authorization.
  • the VNFM applies for the virtual resource to the VIM.
  • the VNF instance is configured to complete the VNF instantiation.
  • the device that instantiates the NS is referred to as a first device, and the device that instantiates the VNF is referred to as a second device.
  • the first device and the second device may be the same device or different devices.
  • the device can associate the instantiated VNF instance to the NS instance to provide external services.
  • the instantiation of the VNF and the instantiation of the NS are in different devices (for example, the instantiation of the NS is in NFVO 102, the instantiation of the VNF is in EM 110), the instantiated VNF instance cannot be associated with the NS instance, and cannot be externally Provide services.
  • the embodiment of the present invention proposes a scheme for managing VNF instantiation for the case where the first device and the second device are different devices.
  • the solution involves the stage of instantiating the NS and the stage of instantiating the VNF.
  • the requesting device In the stage of instantiating the NS, the requesting device carries the instance information of the VNF that needs to be instantiated by the second device in the request of the instantiated NS sent by the first device.
  • the instance identifier of the VNF that needs to be instantiated by the second device in the NS is recorded by the first device.
  • the embodiment of the present invention adds a judgment on the association relationship between the VNF and the NS in the authorization process, because the resource management entity (ie, the first device) needs to obtain the resource authorization. That is to say, when the first device performs the resource authorization judgment, the VNF instantiation initiated by the second device is further authorized according to the instance identifier of the VNF recorded in the NS instantiation process. If there is no VNF requested by the second device in the record, the first device rejects the instantiation of the VNF by the second device.
  • the requesting device In the stage of instantiating the NS, the requesting device carries the instance ID of the VNF to be instantiated by the second device in the request for instantiating the NS, and records the VNF to be instantiated by the second device in the NS in the first device.
  • the first device can control the instantiation of the VNF according to the record, that is, the VNF can be instantiated only if there is a record of the VNF.
  • the second device is prevented from instantiating some VNFs that cannot provide services, resulting in waste of resources.
  • Each of the devices in the NVF system 100 shown in FIG. 1 can be implemented using the computer device 200 of FIG.
  • the computer device 200 can be used to implement NFVO 102 or VNFM 104 or VIM 106 or OSS/BSS 124 or EM 110 in NFV system 100 as shown in FIG.
  • computer device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
  • the processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 202 can include a path for communicating information between the components described above.
  • the communication interface 204 is applicable to any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.
  • the communication interface 204 can be used to communicate with an application server and with other storage nodes in the distributed storage system.
  • the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 203 is used to store application code for executing the solution of the present invention, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute application code stored in the memory 203. Specifically, when the computer device 200 is used to implement the NFVO 102 in the NFV system 100, code for implementing the functions of the NFVO 102 is stored in the memory 203.
  • the processor 201 executes the application code stored in the memory 203 to perform the functions of the first device (i.e., NFVO 102) in the embodiment shown in Figs. 3 and 4.
  • code for implementing the functions of the OSS/BSS 124 is stored in the memory 203.
  • the processor 201 executes the application code stored in the memory 203, and performs the functions of the requesting device (i.e., the OSS/BSS 124) in the embodiment shown in Figs. 3 and 4.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 200 can include multiple processors, such as two processors 201 shown in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the computer device 200 described above can be a general purpose computer device or a special purpose computer device.
  • computer device 200 can be a network server, a communication device, an embedded device, or a device having a similar structure in FIG. Embodiments of the invention do not limit the type of computer device 200.
  • each device in the NVF system 100 shown in FIG. 1 may be implemented on different computer devices, or may be partially integrated on one computer device.
  • FIG. 3 is a flowchart of a method for instantiating an NS according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • the requesting device sends a deployment request to the first device.
  • the requestor device may be the OSS/BSS in the NFV system shown in FIG. 1, and the first device may be the NFVO in the NFV system shown in FIG. 1.
  • the deployment request can contain the deployment template (that is, NSD) of the NS that needs to be deployed. Among them, the NSD has the (Identify, ID) of the NSD.
  • the deployment request can be an "NSD on-boarding" request as defined in the ETSI standard.
  • the first device After receiving the deployment request, the first device saves the NSD included in the deployment request, and returns a deployment success response to the requesting device.
  • the requesting device After receiving the deployment success response, the requesting device initiates a request to create an instance ID of the NS to the first device.
  • the request for creating the instance ID of the NS includes the ID of the NSD saved in step S304.
  • the first device creates an instance ID of the NS and sends the instance ID to the requesting device.
  • the requesting device acquires an instance identifier (Identify, ID) of the VNF.
  • the requesting device determines whether there is a VNF that needs to be instantiated by the second device according to the policy of deploying the NS before initiating the request for instantiating the NS.
  • the policy may be that all VNFs in the NS need to be instantiated by the second device, or a part of the VNF needs to be instantiated by the second device.
  • the requesting device may initiate a process of obtaining an instance ID of the VNF.
  • the foregoing policy may be included in the description information of the VNF in the deployment template of the NS.
  • the indication information of the VNF may be included in the description information of the VNF, where the indication parameter is used to indicate whether the VNF is instantiated by the second device.
  • the requesting device may determine a VNF to be instantiated by the second device according to the indication parameter.
  • the indication parameter can take the form shown in Table 1.
  • the process of the requesting device acquiring the instance ID of the VNF may specifically include:
  • the requesting device initiates a request for creating an instance identifier (Identify, ID) of the VNF to the second device.
  • the second device may be the EM in the NFV system shown in FIG.
  • the requesting device initiates a request to create an instance ID of the VNF to the second device after determining the VNF that needs to be instantiated by the second device in the NS that needs to be instantiated.
  • the second device After receiving the request for creating the instance ID of the VNF, the second device initiates a request for creating an instance ID of the VNF to the VNFM.
  • the request for creating the VNF instance ID sent by the second device to the VNFM may carry the VNFM ID of the VNF that needs to be instantiated.
  • the VNFM allocates an instance ID of the VNF and returns it to the second device.
  • S310d The second device returns the received instance ID of the VNF to the requesting device.
  • steps S310a-S310d may be repeatedly performed until the NS is performed. All the instance IDs in the VNF that need to be instantiated by the second device are created.
  • steps S310a-S310d are only an embodiment.
  • the step may be deleted or other manners may be used to obtain the instance ID of the VNF.
  • step S310 only needs to be completed before S312, and steps S302-S308 are not sequentially defined in the execution order.
  • the requesting device After the requesting device obtains the instance identifier of the VNF that needs to be instantiated by the EM in the NS, the requesting device initiates a request for instantiating the NS to the first device.
  • the requesting device When the request for instantiating the NS is initiated, the requesting device carries the instance information of the virtualized network function VNF to be instantiated by the second device in the NS in the request for instantiating the NS.
  • the instance information may include an instance ID of the VNF and status information indicating that the VNF is to be instantiated by the second device.
  • the NS may also include a VNF to be instantiated by the first device and/or an existing VNF instance.
  • the first device can instantiate the VNF according to the VNFD in the NSD.
  • the requesting device initiated request for instantiating the NS may include an instance ID of the already existing VNF instance and status information indicating that the VNF has been instantiated. The contents that can be carried in the request are as shown in Table 2:
  • the status is the status information of the VNF instance corresponding to the VNF instance ID.
  • This field When the value of this field is "Instantiated”, it indicates that the VNF instance has been instantiated and can be used directly.
  • the value of the field When the value of the field is "Created by EM, non-instantiated”, it indicates that the VNF instance is not instantiated and is to be created by the EM.
  • the form of "vnfInstanceId” and "Status” is defined in Table 1, which is only an example of the instance ID and status information of the VNF instance.
  • the request for instantiating the NS may further include other information, for example, the instance ID of the NS, the ID of the NSD. , or VNFD ID, etc. Additional information included in the request to instantiate the NS may refer to the information in the request "InstantiateNSRequest" of the instantiated NS defined in the ETSI standard.
  • the first device determines a VNF to be instantiated by the second device in the NS, and records an instance ID of the VNF to be instantiated by the second device.
  • the first device After receiving the request for instantiating the NS, the first device instantiates the NS (that is, creates an NS instance). In the process of instantiating the NS, the first device can view the instance information of the VNF carried in the request, and distinguish which VNFs in the NS need to wait for the second device to be instantiated according to the state information in the instance information of each VNF. For the VNF that needs to be instantiated by the second device, the first device records the instance ID of the VNF to indicate that the VNF is associated in an NS, and when the subsequent second device initiates the request to instantiate the VNF, according to the record. Authorization.
  • the instance information of the corresponding NS may be further recorded to determine which NS instance the VNF instance corresponding to the instance identifier of the VNF is specifically associated with.
  • the first device may further confirm, according to the VNFD information in the NSD, whether there is still a VNF that needs to be instantiated by the first device.
  • the first device initiates a process of instantiating the VNF to the VNFM.
  • the process of the first device to instantiate the VNF to the VNFM can be implemented by using the existing technology.
  • the specific implementation process can refer to the NFVO defined in the ETSI standard to initiate the process of instantiating the VNF, and details are not described herein.
  • the first device returns an NS instantiation operation response to the requesting device.
  • the NS instantiating operation response carries the operation ID of the instantiated NS operation. After returning the NS instantiation operation response, the first device waits for the second device to instantiate the VNF.
  • the first device may directly return an NS instantiation operation response upon receiving the request to instantiate the NS, or may return an NS instantiation operation response after instantiating the NS.
  • the requesting device After receiving the NS instantiation operation response returned by the first device, the requesting device initiates the process of instantiating the VNF by using the second device to complete the instantiation of the VNF.
  • the requesting device After receiving the NS instantiation operation response, the requesting device initiates the request of the instance VNF according to the instance ID of the VNF obtained in step S310.
  • the first device may control the instantiation of the VNF by the second device according to the association established in step S314 (ie, the instance ID of the VNF recorded in the NS instantiation process). Specifically, the first device determines whether to authorize the second device to instantiate the VNF by determining whether the instance ID of the VNF that the second device requests to instantiate exists in the instance ID of the VNF recorded in the NS instantiation process.
  • the first device After the VNF in the NS is instantiated, the first device sends an NS instantiation success message to the requesting device.
  • the NS instantiation success message is sent to the requesting device.
  • the embodiment of the present invention places the instance ID of the VNF instantiated by the second device before the request to initiate the instantiation of the NS, so that the requesting device can carry the instance ID of the VNF instantiated by the second device in the instantiated NS.
  • the request is sent to the first device, so that the first device acquires the relationship between the NS to be instantiated and the VNF that needs to be instantiated by the second device.
  • FIG. 4 is a flowchart of a method for instantiating a VNF according to an embodiment of the present invention. As shown in FIG. 4, the method includes:
  • the requesting device initiates a request for instantiating the VNF to the second device.
  • the requesting device After receiving the operation response returned by the first device in step S316, the requesting device initiates a request to instantiate the VNF to the second device.
  • the request for instantiating the VNF carries the instance ID of the VNF obtained in the NS instantiation process (ie, step S310 of FIG. 3).
  • the second device initiates a request for instantiating the VNF to the VNFM.
  • the second device After receiving the request for instantiating the VNF initiated by the requesting device, the second device forwards the request for instantiating the VNF to the VNFM.
  • the VNFM initiates an authorization request for instantiating the VNF to the first device.
  • the authorization request is for requesting the first device to authorize the VNFM to perform an operation of instantiating the VNF.
  • the authorization request carries the instance ID of the VNF to be instantiated and the resource information that the instantiation operation needs to apply.
  • the first device determines whether the condition for instantiating the VNF is satisfied.
  • the condition for instantiating the VNF includes the instance ID of the VNF carried in the authorization request in the instance identifier of the VNF recorded when the NS is instantiated.
  • the first device compares the instance ID of the VNF carried in the authorization request with the instance ID of the VNF recorded in the instantiated NS process (ie, step S314 in FIG. 3), if the instance of the VNF recorded in S314 is If the instance ID of the VNF carried in the authorization request exists in the ID, it is determined that the VNF that needs to be instantiated in the authorization request is used to instantiate the NS in step S314, and the condition for instantiating the VNF is satisfied. If the instance ID of the VNF carried in the authorization request does not exist in the instance ID of the VNF recorded in step S314, the condition for instantiating the VNF is not satisfied.
  • the conditions for instantiating the VNF may also include some conditions defined in the prior art, for example, the judgment of the virtual resource condition of the application, and the like.
  • the conditions for instantiating a VNF as defined in the prior art can be referred to the ETSI standard.
  • the first device After determining that the condition for instantiating the VNF is satisfied, the first device authorizes the VNMF to perform an operation of instantiating the VNF.
  • the first device may return an authorization to the VNMF to authorize the VNMF to perform an operation of instantiating the VNF by a response message.
  • the VIM information can be carried in the authorization response message.
  • the first device needs to determine that all the conditions are met before authorizing the VNMF to perform an operation of instantiating the VNF. In case one of the conditions is not satisfied, the first device rejects the VNMF to perform an operation of instantiating the VNF. The process for conditions that do not satisfy the instantiation of VNF is not shown in FIG.
  • the first device initiates a subscription request to the VNFM to subscribe to the VNF instance.
  • the first device After determining that the condition for instantiating the VNF is satisfied, the first device further sends a subscription request to the VNFM.
  • the subscription request is used to request the VNFM to send a notification message to the first device after instantiating the VNF.
  • the VNFM After receiving the authorization response message returned by the first device, the VNFM initiates a resource request request to the VIM.
  • the VNFM determines the VIM that receives the resource request request according to the VIM information carried in the response message according to the authorization.
  • the VIM returns a resource request success response to the VNFM.
  • the VIM After receiving the resource request, the VIM requests the virtual resource required by the VNF instance and carries the address of the VNF instance in the resource application success response.
  • VNFM configures the VNF instance to complete the creation of the VNF instance.
  • the VNFM can configure the external link address information of the VNF instance, the elastic scaling policy, and the like. After the configuration is complete, the VNF instance is created.
  • the VNFM sends a notification message to the second device to notify the second device that the VNF instantiation is completed.
  • the VNFM sends a notification message to the first device to notify the first device that the VNF instantiation is completed.
  • the first device may determine whether to allow the second device to instantiate the VNF according to the instance identifier of the VNF recorded when the NS is instantiated, thereby controlling the instantiation of the VNF by the second device, ensuring the first The second device creates a valid VNF to avoid waste of resources.
  • FIG. 5 shows a possible structural diagram of the first device involved in the above embodiment.
  • the first device includes: a receiving unit 501, a processing unit 502, and a management unit 503.
  • the receiving unit 501 can interact with the requesting device.
  • the receiving unit 501 can receive a request by the requesting device to instantiate the NS.
  • the interaction between the first device and the requesting device in the method embodiment shown in FIG. 3 can be implemented by the receiving unit 501.
  • the processing unit 502 is configured to perform an instantiation process of the NS. For example, the processing unit 502 may determine, from the request for the instantiated NS received by the receiving unit 501, the VNF that needs to be instantiated by the second device, and record an instance of the VNF that needs to be instantiated by the second device. logo.
  • the function of saving the NSD in step S304 in the method embodiment shown in FIG. 3, the function of creating the NS instance ID in S308, and the function of instantiating the NS in step S314 can be implemented by the processing unit 502, and the specific implementation process Refer to the method embodiment part shown in FIG. 3, and details are not described herein again.
  • the management unit 503 can interact with the VNFM to authorize the instantiation of the VNF according to the instance identifier of the VNF recorded by the processing unit 502 during the NS instantiation process during the instantiation of the VNF.
  • the management unit 503 may receive an authorization request initiated by the VNMF after receiving a request sent by the second device to instantiate the VNF.
  • the management unit 503 determines whether the condition for instantiating the VNF is satisfied.
  • the determining whether the condition for instantiating the VNF is satisfied includes: determining whether an instance identifier of the VNF carried in the authorization request exists in an instance identifier of a VNF recorded when the NS is instantiated.
  • the management unit 503 After determining that the condition for instantiating the VNF is satisfied, the management unit 503 authorizes the VNMF to perform an operation of instantiating the VNF.
  • the interaction between the first device and the VNFM in the method embodiment shown in FIG. 3 and FIG. 4 can be implemented by the management unit 503. For the specific implementation process, refer to the method embodiment part shown in FIG. 3 and FIG. No longer.
  • FIG. 6 shows a possible structural diagram of the requesting device involved in the above embodiment.
  • the requesting device includes: a transceiver unit 601 and a processing unit 602.
  • the transceiver unit 601 can interact with the first device. For example, the transceiving unit 601 can initiate a request to instantiate the NS to the first device and receive an NS instantiation operation response returned by the first device.
  • the interaction between the requesting device and the first device in the method embodiment shown in FIG. 3 can be implemented by the transceiver unit 601. For the specific implementation process, reference may be made to the method embodiment shown in FIG. 3, and details are not described herein again.
  • Processing unit 602 can interact with the second device.
  • the processing unit 602 may request the VNFM to create an instance identifier of the VNF that needs to be instantiated by the second device in the NS by using the second device, and may also request the VNFM to instantiate the VNF by using the second device.
  • the interaction between the requesting device and the second device in the method embodiment shown in FIG. 3 and FIG. 4 can be implemented by the processing unit 602. For the specific implementation process, reference may be made to the method embodiment shown in FIG. 3 and FIG. , no longer repeat them here.
  • the requesting device may further include a policy unit 503.
  • the policy unit 503 is configured to query description information of the VNF in the deployment template of the NS. Determining, by the indication parameter in the description information of the VNF, the VNF to be instantiated by the second device, and determining, by the determining result, that the processing unit 602 performs the request to create the NS by using the second device by using the second device, The operation of the instance identification of the VNF instantiated by the second device.
  • the policy unit 503 reference may be made to step S310 in the method embodiment shown in FIG. 3, and details are not described herein again.
  • the disclosed systems and methods can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division.
  • there may be another division manner for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional module in each embodiment of the present invention may be integrated into one processing unit, or each module may exist physically separately, or two or more modules may be integrated into one unit.
  • the above integrated modules can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional units described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform portions of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a random access memory (English name: Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like, which can store data.
  • Another embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the storage node, including a program designed to execute the method embodiment shown in FIG.
  • Another embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the distributed storage system described above, including a program designed to execute the above-described FIG. 5 and the migration method embodiment. Capacity migration and migration of hot and cold content data can be achieved by executing stored programs.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)

Abstract

一种管理VNF实例化的方法，该方法包括：请求方设备在向第一设备发起的实例化NS的请求中携带所述NS中需通过第二设备实例化的虚拟化网络功能VNF的实例信息。第一设备接收到实例化NS的请求后，确定出所述NS中待所述第二设备实例化的VNF，并记录所述需通过所述第二设备实例化的VNF的实例标识。在该VNF被实例化的阶段，第一设备根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权。通过在发送给第一设备的实例化NS的请求中携带由第二设备实例化的VNF的实例ID，使第一设备可以获知由第二设备实例化的VNF与NS的关系，从而可以根据该关系来控制VNF的实例化，确保第二设备实例化有效的VNF，避免资源浪费。

Description

一种管理VNF实例化的方法和设备
本申请要求于2017年6月29日提交中国专利局、申请号为201710516763.5，发明名称为“一种管理VNF实例化的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及云计算技术领域，特别涉及一种管理VNF实例化的方法和设备。
背景技术
网络功能虚拟化(英文：Network Function Virtualization，简称：NFV)，指通过使用通用的硬件设备及虚拟化技术，来承载传统网络中专用设备的功能，从而降低部署专用设备带来的昂贵成本。软件不与专有硬件绑定，使设备功能不再依赖于专用硬件。与传统网络相比，NFV引入了虚拟化层，通过网络管理和编排，实现虚拟化网络功能(Virtualized Network Function，VNF)和虚拟化的网络服务(Network Service，NS)的生命周期管理。在NFV架构中，VNF是下层的网络功能，NS是通过一个或多个VNF来实现的上层的网络服务。比如，IP多媒体子系统(IP Multimedia Subsystem，IMS)的网络服务，或演进型分组核心网络(Evolved Packet Core，EPC)的网络服务等。也就是说，一个NS中可以由一个或多个VNF组成。
当业务请求方需要实现一个NS时，可以向资源管理实体发送该NS的描述信息(Network Service descriptor，NSD)，也称作NS部署模板。该资源管理实体可以是网络功能虚拟化编制器(英文：NFV Orchestrator，简称：NFVO)。NSD主要描述了该NS的拓扑结构以及包含的每个VNF的描述信息(VNF descriptor，VNFD)。其中，在拓扑结构信息中使用虚拟化连接信息(virtual link descriptor，VLD)来描述VNF之间的连接。VNFD是一个VNF的描述信息，也称作VNF的部署模板。VNFD描述了每个VNF的构成，比如运行的软件，需要的虚拟资源信息等。虚拟资源包括CPU资源，存储资源等。业务请求方可以请求资源管理实体基于NSD对NS进行实例化。NS的实例化是指创建NS实例。资源管理实体在实例化NS的过程中，可以根据NSD中的VNFD发起对所需的VNF的实例化，也可以使用已存在的VNF实例。VNF的实例化是指创建VNF实例。
目前，实例化VNF有两种方式。一种是如上所述的由资源管理实体在实例化NS的过程中，发起对该NS中的VNF的实例化。另一种是由设备管理系统(equipment management，EM)发起对VNF的实例化。
在通过EM实例化VNF的方案中，由于EM没有NS的相关信息，无法在实例化的VNF的过程中，将VNF关联到NS中，这就导致由EM实例化的VNF无法对外提供服务，因为VNF只是组成NS的一个虚拟化网络功能，只有NS才能提供具体的网络服务，独立于NS的VNF不能单独的对外提供服务。如果EM实例化大量独立于NS的VNF，势必造成资源的浪费。因此，需要对EM实例化VNF进行控制。
发明内容
本发明实施例提供了一种管理VNF实例化的方法和设备，以避免资源浪费。
为达到上述目的，本发明采用如下技术方案：
一方面，本发明实施例提供了一种管理VNF实例化的方法，该方法包括NS实例化和 VNF实例化两个阶段。在NS实例化阶段，请求方设备在向第一设备发起的实例化NS的请求中携带所述NS中需通过第二设备实例化的虚拟化网络功能VNF的实例信息。该实例信息包括所述VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息。第一设备接收到实例化NS的请求后，根据所述状态信息确定出所述NS中待所述第二设备实例化的VNF，并记录所述需通过所述第二设备实例化的VNF的实例标识。在该VNF被实例化的阶段，第一设备根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权。
通过在发送给第一设备的实例化NS的请求中携带由第二设备实例化的VNF的实例ID，使第一设备可以获知由第二设备实例化的VNF与NS的关系，从而可以根据该关系来控制VNF的实例化。即只有在该VNF与NS有关系的情况下，才允许实例化该VNF。确保第二设备实例化有效的VNF，避免资源浪费。
在一种可能的设计中，请求方设备在发起实例化所述NS的请求前，通过第二设备从虚拟网络功能管理器VNFM获取的NS中需通过第二设备实例化的VNF的实例标识。
本发明实施例将由第二设备实例化的VNF的实例ID的创建放在了发起实例化NS的请求之前，从而请求方设备可以将由第二设备的实例化的VNF的实例ID携带在实例化NS的请求中发送给第一设备，使第一设备获取到要实例化的NS与需第二设备实例化的VNF的关系。
在一种可能的设计中，第一设备根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权，具体包括：VNMF在接收到所述第二设备发送的实例化所述VNF的请求后向第一设备发起的授权请求。该授权请求用于请求所述NFVO授权所述VNFM执行实例化所述VNF的操作，其中携带有VNF的实例标识。第一设备接收到授权请求后，确定实例化所述VNF的条件是否满足。该条件包括在实例化所述NS时记录的VNF的实例标识中存在所述授权请求中携带的所述VNF的实例标识。在确定满足实例化所述VNF的条件后，第一设备授权所述VNMF执行实例化所述VNF的操作。由于只有在该VNF与NS有关系的情况下，才允许实例化该VNF，因此，第二设备实例化无法实例化无效的VNF，避免资源浪费。
在一种可能的设计中，第一设备在确定满足实例化所述VNF的条件后，还进一步向所述VNFM发起订阅所述VNF实例的订阅请求。请订阅请求用于请求所述VNFM在实例化所述VNF后，向所述第一设备发送通知消息。在所述VNF实例化成功后，所述第一设备接收来自所述VNFM的通知消息，所述通知消息用于指示所述VNF已实例化。通过订阅机制，第一设备在实例化NS的过程中，除了由自身实例化VNF外，还可以等待其它设备来实例化NS中的VNF，使得实例化NS的过程更灵活。
又一方面，本发明实施例提供了一种管理VNF实例化的方法，该方法包括：请求方设备向第一设备发起实例化网络服务NS的请求。请求方设备在该请求中携带所述NS中需通过第二设备实例化的VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息。其中，所述状态信息为待所述第二设备实例化的VNF的实例标识会被记录在所述第一设备中。所述请求方设备在接收第一设备返回的NS实例化操作响应。在接收到所述第一设备返回的NS实例化操作响应后，请求方设备通过所述第二设备请求VNFM实例化所述VNF。其中，在所述VNF被实例化的过程中，所述第一设备中记录的所述VNF的实例标识被用于实例化所述VNF的授权判断。
请求方设备通过在发送给第一设备的实例化NS的请求中携带由第二设备实例化的VNF的实例ID，使第一设备可以获知由第二设备实例化的VNF与NS的关系，从而可以根据该关系来控制VNF的实例化。即只有在该VNF与NS有关系的情况下，才允许实例化该VNF。确保第二设备实例化有效的VNF，避免资源浪费。
在一种可能的设计中，请求方设备在请求实例化NS前，通过第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识，并接收所述VNFM创建的所述VNF的实例标识。
本发明实施例将由第二设备实例化的VNF的实例ID的创建放在了发起实例化NS的请求之前，从而请求方设备可以将由第二设备的实例化的VNF的实例ID携带在实例化NS的请求中发送给第一设备，使第一设备获取到要实例化的NS与需第二设备实例化的VNF的关系。
在一种可能的设计中，请求方设备通过查询所述NS的部署模板中的VNF的描述信息来确定出需由所述第二设备实例化的VNF。其中，VNF的描述信息信息中包括指示参数。该指示参数的用于指示所述VNF是否通过所述第二设备实例化。请求方设备根据所述指示参数确定出需由所述第二设备实例化的VNF，并基于确定结果执行所述通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识的操作。
又一方面，本发明实施例提供了一种管理VNF实例化的装置，该装置具有实现上述方法实施例中第一设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的部件(比如，用于与请求方设备交互的接收单元，用于实现NS实例化的处理单元，以及在VNF实例化过程中，进行授权控制的管理单元)。
又一方面，本发明实施例提供了一种管理VNF实例化的装置，该装置具有实现上述方法实施例中请求方设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的部件(比如，用于与第一设备交互的收发单元，用于与第二设备交互的处理单元，以及用于确定NS中需通过所述第二设备实例化的VNF的策略单元)。
又一方面，本发明实施例提供了第一设备，其可基于计算机结构来实现。其中，该第一设备包括存储器和处理器。其中存储器用于存储实现上述方法实施例中第一设备的功能的程序指令。处理器用于执行存储器中的程序指令，实现上述方法实施例中第一设备的功能。
又一方面，本发明实施例提供了请求方设备，其可基于计算机结构来实现。其中，该请求方设备包括存储器和处理器。其中存储器用于存储实现上述方法实施例中请求方设备的功能的程序指令。处理器用于执行存储器中的程序指令，实现上述方法实施例中请求方设备的功能。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第一设备所用的计算机软件指令，其包含用于执行上述方面为第一设备所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述请求方设备所用的计算机软件指令，其包含用于执行上述方面为请求方设备所设计的程序。
本发明实施例通过在发送给第一设备的实例化NS的请求中携带由第二设备实例化的VNF的实例ID，使第一设备可以获知由第二设备实例化的VNF与NS的关系，从而可以根据该关系来控制VNF的实例化，确保第二设备实例化有效的VNF，避免资源浪费。
附图说明
图1为本发明实施例提供的一种NFV系统的架构图；
图2为本发明实施例提供的一种的计算机设备示意图；
图3为本发明实施例提供的一种实例化NS的方法流程图。
图4为本发明实施例提供的一种实例化VNF的方法流程图；
图5为本发明实施例提供的第一设备的结构图；
图6为本发明实施例提供的请求方设备的结构图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述。
本申请可应用于NFV系统架构中。如图1所示，图1为一种NFV系统100的实施例的架构示意图，其中包括以下功能部件：
网络功能虚拟化编排器(NFVO)102，主要负责NS的生命周期管理，以及虚拟基础设施(network functions virtualization infrastructure，NFVI)中虚拟资源的分配和调度等。NFVO 102可以与一个或多个虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)104通信，执行VNF实例化等生命周期管理相关操作，并发送配置信息给VNFM104，以及向VNFM 104请求收集VNF 108的状态信息。另外，NFVO 102也可与虚拟基础设施管理器(Virtualized Infrastructure Manager,VIM)106通信，执行资源分配，和/或预留，交换虚拟化硬件资源配置和状态信息。
虚拟网络功能管理器(VNFM)104，负责一个或多个VNF的生命周期管理，比如实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF 108。VNFM 104可以与VNF 108通信以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型的VNF进行生命周期管理。
虚拟基础设施管理器(VIM)106，控制和管理VNF 108与计算硬件112，存储硬件114，网络硬件116，虚拟计算(virtual computing)118，虚拟存储120，虚拟网络122的交互。例如VIM106执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM 104及VIM 106可以相互通信，请求资源分配，交换虚拟化硬件资源配置和状态信息。
网络功能虚拟化基础设施(NFV Infrastructure，NFVI)即NFV的基础设施层，包含硬件部件，软件部件或两者组合，以建立虚拟化环境，部署，管理及实现VNF 108。硬件资源和虚拟化层用于为VNF 108提供虚拟化资源，如虚拟机和其他形式的虚拟容器。硬件资源包括计算(computing)硬件112，存储硬件114，网络硬件116。作为一种实施方式，计算硬件112和存储硬件114的资源可以集中在一起。NFVI中的虚拟化层可以抽象硬件资源，解耦VNF108与底层的物理网络层。
每个虚拟化网络功能(VNF)108,运行在一个或多个虚拟容器中，对应于一组属于一个或多个物理设备的网络功能。
设备管理系统(EM)110，是传统电信系统中用于对设备进行配置，管理的系统，主要用 于对设备的配置，监控和管理。在NFV架构中，EM 110也可以用于对VNF实例进行配置，监控和管理。同时，运营支持系统和业务支持系统(Operations Support System and Business Support System，OSS/BSS)124还可以通过EM110向VNFM发起新的VNF的实例化，VNF弹性伸缩等生命周期管理操作。
运营支持系统和业务支持系统(OSS/BSS)124，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
在NFV系统架构中，NFVO 102属于资源管理实体。NS的实例化由资源管理实体负责。当业务请求方(例如，图1中的OSS/BSS 124)需要部署一个NS时，可以向NFVO 102发送该NS的描述信息(NSD)。NFVO102保存该NSD。后续，OSS/BSS 124可以请求NFVO 102基于该NSD实例化NS。NFVO 102实例化NS的过程中，根据NSD中包含的VNFD确认需要实例化的VNF，然后向VNFM发起实例化VNF的流程。由于该实例化VNF的流程是由NFVO 102在实例化NS的过程中触发的，因此，实例化的VNF是该NS中的VNF。
VNF的实例化除了由NFVO 102在实例化NS的过程中发起，也可以由其它设备在实例化NS的过程之外发起。例如，业务请求方(如，图1中的OSS/BSS 124)可以通过图1所示的EM 110向VNFM发起对VNF的实例化。由于由EM110发起的VNF的实例化不是在NS的实例化过程中发起的，因此，这些VNF在实例化时并不存在于任何NS中。
VNFM是负责VNF实例化的实体。VNFM可以接收来自NFVO 102或者EM 110的实例化VNF的请求。VNFM接收到实例化VNF的请求后，向负责虚拟资源的分配和调度的资源管理实体(如，图1中的NFVO 102)请求资源授权。该资源授权主要指NFVO 102确认该VNF所需的虚拟资源(例如，虚拟CPU,虚拟存储，虚拟网络等)，是否可分配，可分配则授权，不可分配则拒绝授权。VNFM在获得授权后，向VIM申请虚拟资源，申请到虚拟资源后，配置VNF实例，完成VNF的实例化。
本发明实施例将实例化NS的设备称为第一设备，将实例化VNF的设备称为第二设备。第一设备与第二设备可以是同一设备，也可以是不同设备。当VNF的实例化与NS的实例化在同一设备时(例如，都在NFVO 102)，该设备可以将实例化的VNF实例关联到NS实例中，以对外提供服务。而当VNF的实例化与NS的实例化在不同设备时(例如，NS的实例化在NFVO 102，VNF的实例化在EM 110)，实例化的VNF实例则无法关联到NS实例中，无法对外提供服务。因此，为了避免创建无意义的VNF实例，针对第一设备和第二设备为不同设备的情况，本发明实施例提出了一种管理VNF实例化的方案。该方案涉及实例化NS的阶段以及实例化VNF的阶段。
在实例化NS的阶段，请求方设备在向第一设备发送的实例化NS的请求中携带该NS中需通过第二设备实例化的VNF的实例信息。由第一设备记录下该NS中需通过第二设备实例化的VNF的实例标识。
在实例化VNF的阶段，由于需要到资源管理实体(即第一设备)获取资源授权，本发明实施例在该授权过程中增加了对VNF与NS的关联关系的判断。也就是说，第一设备在进行资源授权判断时，需要进一步根据在NS实例化过程中记录的VNF的实例标识，对第二设备发起的VNF实例化进行授权。如果在记录中不存在第二设备请求实例化的VNF，则第一设备拒绝第二设备对该VNF的实例化。
在实例化NS的阶段，请求方设备通过将待第二设备实例化的VNF的实例ID携带在实例化NS的请求中，在第一设备中记录下NS中待第二设备实例化的VNF。从而使该VNF在被第二 设备实例化时，第一设备可以根据该记录来控制VNF的实例化，即只有在有该VNF的记录的情况下，才允许实例化该VNF。避免了第二设备实例化一些无法提供服务的VNF，造成资源浪费。
图1中所示的NVF系统100中的各设备可以采用图2中的计算机设备200来实现。例如，该计算机设备200可用于实现如图1所示NFV系统100中NFVO 102或VNFM 104或VIM106或OSS/BSS124或EM110。如图2所示，计算机设备200包括至少一个处理器201，通信总线202，存储器203以及至少一个通信接口204。
处理器201可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线202可包括一通路，在上述组件之间传送信息。所述通信接口204，适用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等，在本发明实施例中，通信接口204可用于与应用服务器以及与分布式存储系统中的其它存储节点进行通信。
存储器203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器203用于存储执行本发明方案的应用程序代码，并由处理器201来控制执行。所述处理器201用于执行所述存储器203中存储的应用程序代码。具体的，当该计算机设备200用于实现NFV系统100中的NFVO 102时，存储器203中存储用于实现NFVO 102的功能的代码。处理器201执行所述存储器203中存储的应用程序代码，执行图3和图4所示实施例中的第一设备(即NFVO 102)的功能。当该计算机设备200用于实现NFV系统100中的OSS/BSS124时，存储器203中存储用于实现OSS/BSS 124的功能的代码。处理器201执行所述存储器203中存储的应用程序代码，执行图3和图4所示实施例中的请求方设备(即OSS/BSS 124)的功能。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备200可以包括多个处理器，例如图2中示出两个处理器201。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
上述的计算机设备200可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备200可以是网络服务器、通信设备、嵌入式设备或有图2中类似结构的设备。本发明实施例不限定计算机设备200的类型。
需要说明的是，图1中所示的NVF系统100中各设备可以分别在不同的计算机设备上实现， 也可以部分集成在一个计算机设备上实现。
下面分别通过图3和图4对本发明实施例中实例化NS和实例化VNF的过程进行详细介绍。图3为本发明实施例提供的实例化NS的方法的流程图。如图3所示，该方法包括：
S302，请求方设备向第一设备发送部署请求。
其中，请求方设备可以是图1所示NFV系统中的OSS/BSS，第一设备可以是图1所示NFV系统中的NFVO。
部署请求可以包含需要部署的NS的部署模板(即NSD)。其中NSD中有该NSD的(Identify,ID)。该部署请求可以是ETSI标准中定义的“NSD on-boarding”请求。
S304，第一设备收到部署请求后，保存该部署请求中包含的NSD，并向请求方设备返回部署成功响应。
S306，请求方设备接收到部署成功响应后，向第一设备发起创建NS的实例ID的请求。
其中，创建NS的实例ID的请求中包括步骤S304中已保存的NSD的ID。
S308，第一设备创建NS的实例ID，并发送给请求方设备。
S310，请求方设备获取VNF的实例标识(Identify，ID)。
请求方设备在发起实例化NS的请求前，可以根据部署NS的策略确定NS中是否有需要通过第二设备实例化的VNF。例如，该策略可以是NS中所有VNF都需要通过第二设备来实例化，也可以是部分VNF需要通过第二设备来实例化。针对需要通过第二设备来实例化的VNF，请求方设备可发起获取VNF的实例ID的流程。
其中，上述策略可以包括在NS的部署模板中的VNF的描述信息中。具体的，可以在VNF的描述信息信息中包括指示参数，该指示参数的用于指示所述VNF是否通过所述第二设备实例化。请求方设备可以根据所述指示参数确定出需由所述第二设备实例化的VNF。该指示参数可采用表1所示的形式。
表1
Figure PCTCN2018085750-appb-000001
需要说明的是，将策略以指示参数的形式包括在VNF的描述信息中只是一种实现方式。该策略也可以独立存在，或以其它方式进行设置。
请求方设备获取VNF的实例ID的流程具体可包括：
S310a，请求方设备向第二设备发起创建VNF的实例标识(Identify，ID)的请求。
第二设备可以是图1所示NFV系统中的EM。请求方设备在确定需要实例化的NS中由需要通过第二设备来实例化的VNF后，向第二设备发起创建VNF的实例ID的请求。
S310b，第二设备在接收到创建VNF的实例ID的请求后，向VNFM发起创建VNF的实例ID的请求。
第二设备向VNFM发送的创建VNF的实例ID的请求中可以携带需要实例化的VNF的VNFM ID。
S310c，VNFM分配VNF的实例ID，并返回给第二设备。
S310d，第二设备将接收到的VNF的实例ID返回给请求方设备。
需要说明的是，如果NS中有多个VNF都需要通过第二设备来实例化，在请求方设备接收到 第二设备返回的VNF的实例ID后，可以重复执行步骤S310a-S310d,直至该NS中所有的需要通过第二设备实例化VNF的实例ID都创建完成。
需要说明的是，步骤S310a-S310d所示的获取VNF的实例ID的方式只是一种实施例，在具体实现时，可对步骤进行删减，或者采用其它方式来获取VNF的实例ID。另外，步骤S310只需在S312之前完成，与步骤S302-S308在执行顺序上没有先后限定。
S312，请求方设备向第一设备发起的实例化NS的请求。
请求方设备在步骤S310获取到该NS中需通过EM实例化的VNF的实例标识后，向第一设备发起的实例化NS的请求。
在发起实例化NS的请求时，请求方设备在实例化NS的请求中携带该NS中需通过第二设备实例化的虚拟化网络功能VNF的实例信息。该实例信息可包括VNF的实例ID以及表明所述VNF待所述第二设备实例化的状态信息。
NS中除包括需通过EM实例化的VNF外，还可以包括需由第一设备实例化的VNF和/或已经存在的VNF实例。对于NS中还包括需由第一设备实例化的VNF的情况，第一设备可以根据NSD中的VNFD对VNF进行实例化。对于NS中还包括已经存在的VNF实例的情况，请求方设备发起的实例化NS的请求中可包括已经存在的VNF实例的实例ID和以及表明该VNF已经被实例化的状态信息。该请求中可携带的内容如表2所示：
表2
Figure PCTCN2018085750-appb-000002
其中，“Status”是VNF实例ID所对应的VNF实例的状态信息。当该字段的取值为“Instantiated”时，表示该VNF实例已经实例化，可以直接使用。当该字段的取值为“Created by EM,non-instantiated”时，表示该VNF实例未实例化，待EM创建。表1中定义“vnfInstanceId”以及“Status”的形式，仅是对VNF实例的实例标识以及状态信息的一种举例。
需要说明的是，上面仅描述了本发明实施例对实例化NS的请求做改进的地方，在具体实现时，实例化NS的请求还可以包括其它信息，例如，NS的实例ID，NSD的ID，或VNFD的ID等。实例化NS的请求包括的其它信息可参考ETSI标准中定义的实例化NS的请求“InstantiateNSRequest”中的信息。
S314，第一设备确定出所述NS中待第二设备实例化的VNF，并记录需通过第二设备实例化的VNF的实例ID。
第一设备收到实例化NS的请求后，对NS进行实例化(即创建NS实例)。在实例化NS的过程，第一设备可查看请求中携带的VNF的实例信息，根据各VNF的实例信息中的状态信息区分出NS中的哪些VNF是需要等待第二设备来实例化的。对于需要通过第二设备实例化的 VNF，第一设备记录下VNF的实例ID，以表明该VNF是关联在一个NS中的，在后续第二设备发起实例化VNF的请求时，依据该记录进行授权。在记录VNF的实例标识时，还可以进一步记录对应的NS的实例信息(如，NS的实例标识)，以明确VNF的实例标识所对应的VNF实例具体关联到哪个NS实例。
第一设备还可以进一步根据NSD中的VNFD信息，确认是否还有需要通过第一设备实例化的VNF。对于需要通过第一设备实例化的VNF，第一设备向VNFM发起实例化VNF的流程。第一设备向VNFM发起实例化VNF的流程可采用现有技术来实现，具体实现过程可参考ETSI标准中定义的NFVO发起实例化VNF的流程，这里不再赘述。
S316，第一设备向请求方设备返回NS实例化操作响应。
其中，NS实例化操作响应中携带有本次实例化NS操作的操作ID。第一设备在返回NS实例化操作响应后，等待第二设备实例化VNF。
需要说明的是，步骤S314和S316之间没有先后顺序的限定。第一设备可以在接收到实例化NS的请求直接返回NS实例化操作响应，也可以在实例化NS后返回NS实例化操作响应。
S318，请求方设备在接收到第一设备返回的NS实例化操作响应后，通过第二设备发起实例化VNF的流程，完成VNF的实例化。
请求方设备在接收到NS实例化操作响应后，根据步骤S310中获取到的VNF的实例ID发起实例VNF的请求。在第二设备实例化VNF的过程中，第一设备可以根据步骤S314中建立的关联(即在NS实例化过程中记录的VNF的实例ID)控制第二设备对该VNF的实例化。具体的，第一设备通过判断在NS实例化过程中记录的VNF的实例ID中是否存在第二设备请求实例化的VNF的实例ID，确定是否授权第二设备对VNF的实例化。
第二设备发起的实例化VNF的流程在图3中详细描述。
S320，在NS中的VNF都完成实例化后，第一设备向请求方设备发送NS实例化成功消息。
第一设备确认NS中需通过第一设备发起实例化的VNF以及S314中记录的需由第二设备实例化的VNF都完成实例化后，向请求方设备发送NS实例化成功消息。
本发明实施例将由第二设备实例化的VNF的实例ID的创建放在了发起实例化NS的请求之前，从而请求方设备可以将由第二设备的实例化的VNF的实例ID携带在实例化NS的请求中发送给第一设备，使第一设备获取到要实例化的NS与需第二设备实例化的VNF的关系。
下面通过图4对步骤S318中实现VNF实例化的过程进行详细描述。图4是本发明实施例提供的实例化VNF的方法的流程图。如图4所示，该方法包括：
S400，请求方设备向第二设备发起实例化VNF的请求。
请求方设备在接收到步骤S316中第一设备返回的操作响应后，向第二设备发起实例化VNF的请求。该实例化VNF的请求携带NS实例化过程(即图3步骤S310)中获取到的VNF的实例ID。
S402，第二设备向VNFM发起实例化VNF的请求。
第二设备接收到请求方设备发起的实例化VNF的请求后，向VNFM转发该实例化VNF的请求。
S404，VNFM向第一设备发起实例化VNF的授权请求。
该授权请求用于请求第一设备授权VNFM执行实例化所述VNF的操作。该授权请求中携带要实例化的VNF的实例ID以及该实例化操作需要申请的资源信息。
S406，第一设备确定实例化VNF的条件是否满足。
其中，实例化VNF的条件包括在实例化所述NS时记录的VNF的实例标识中存在所述授权请求中携带的所述VNF的实例ID。第一设备在接收到授权请求后，将授权请求中携带的VNF的实例ID与实例化NS过程(即图3步骤S314)中记录的VNF的实例ID进行对比，如果S314中记录的VNF的实例ID中存在授权请求中携带的所述VNF的实例ID，则确定该授权请求中需要实例化的VNF是用于实例化步骤S314中的NS，满足实例化VNF的条件。如果步骤S314中记录的VNF的实例ID中不存在授权请求中携带的所述VNF的实例ID，则不满足实例化VNF的条件。
上面仅描述了本发明实施例在实例化VNF的过程中，新增的实例化VNF的条件。在具体实现时，实例化VNF的条件还可以包括现有技术中定义的一些条件，例如，对申请的虚拟资源情况的判断等。现有技术中定义的实例化VNF的条件可参考ETSI标准。
S408，在确定满足实例化所述VNF的条件后，第一设备授权VNMF执行实例化所述VNF的操作。
第一设备可以向VNMF返回授权通过响应消息来授权VNMF执行实例化所述VNF的操作。在授权通过响应消息中可以携带VIM的信息。
在实例化VNF的条件存在多个的情况下，第一设备需要确定所有条件都满足后，才授权VNMF执行实例化所述VNF的操作。在任意一个条件不满足的情况下，第一设备拒绝VNMF执行实例化所述VNF的操作。对于不满足实例化VNF的条件的过程在图4中未示出。
S410，第一设备向VNFM发起订阅VNF实例的订阅请求。
第一设备在确定实例化所述VNF的条件满足后，还进一步向VNFM发送订阅请求。该订阅请求用于请求VNFM在实例化该VNF后，向第一设备发送通知消息。
S412，VNFM接收到第一设备返回的授权通过响应消息后，向VIM发起资源申请请求。
其中，VNFM根据授权通过响应消息中携带的VIM的信息，确定接收资源申请请求的VIM。
S414，VIM向VNFM返回资源申请成功响应。
VIM接收到资源申请请求后，申请VNF实例所需的虚拟资源，并在资源申请成功响应中携带VNF实例的地址。
S416，VNFM对VNF实例进行配置，完成VNF实例的创建。
具体的，VNFM可以配置VNF实例的外部链接地址信息，弹性伸缩策略等。配置完成后，VNF实例创建完成。
S418，VNFM向第二设备发送通知消息，通知第二设备，VNF实例化完成。
S420，VNFM向第一设备发送通知消息，通知第一设备，VNF实例化完成。
在第二实例化VNF的过程中，第一设备可以根据实例化NS时记录的VNF的实例标识，确定是否允许第二设备实例化该VNF，从而控制第二设备对VNF的实例化，确保第二设备创建有效的VNF，避免资源浪费。
图5示出了上述实施例中涉及的第一设备的一种可能的结构示意图。如图5所示，该第一设备包括：接收单元501、处理单元502、以及管理单元503。
其中，接收单元501可以与请求方设备交互。例如，接收单元501可以接收请求方设备发起的实例化NS的请求。另外，图3所示的方法实施例中的第一设备与请求方设备的交互均可通过接收单元501来实现，具体实现过程可参考图3所示的方法实施例部分，这里不再赘述。
处理单元502用于进行NS的实例化处理。例如，处理单元502可以从接收单元501接收到 的实例化NS的请求中确定出所述需通过第二设备实例化的VNF，并记录所述需通过所述第二设备实例化的VNF的实例标识。图3所示的方法实施例中步骤S304中的保存NSD的功能，S308中创建NS实例ID的功能，以及步骤S314中的对NS进行实例化的功能均可由处理单元502来实现，具体实现过程可参考图3所示的方法实施例部分，这里不再赘述。
管理单元503可以与VNFM交互，在VNF被实例化的过程中，根据处理单元502在NS实例化过程中记录的VNF的实例标识对所述VNF的实例化进行授权。例如，管理单元503可以接收所述VNMF在接收到第二设备发送的实例化所述VNF的请求后发起的授权请求。管理单元503在接收到授权请求后，确定实例化所述VNF的条件是否满足。其中，确定实例化所述VNF的条件是否满足包括：确定在实例化所述NS时记录的VNF的实例标识中是否存在所述授权请求中携带的所述VNF的实例标识。在确定满足实例化所述VNF的条件后，管理单元503授权所述VNMF执行实例化所述VNF的操作。另外，图3以及图4所示的方法实施例中的第一设备与VNFM的交互均可通过管理单元503来实现，具体实现过程可参考图3以及图4所示的方法实施例部分，这里不再赘述。
图6示出了上述实施例中涉及的请求方设备的一种可能的结构示意图。如图6所示，该请求方设备包括：收发单元601和处理单元602。
其中，收发单元601可以与第一设备交互。例如，收发单元601可以向第一设备发起实例化NS的请求以及接收第一设备返回的NS实例化操作响应。另外，图3所示的方法实施例中的请求方设备与第一设备的交互均可通过收发单元601来实现，具体实现过程可参考图3所示的方法实施例部分，这里不再赘述。
处理单元602可以与第二设备交互。例如，处理单元602可以通过第二设备请求VNFM创建NS中需通过第二设备实例化的VNF的实例标识，还可以通过第二设备请求VNFM实例化所述VNF。另外，图3以及图4所示的方法实施例中的请求方设备与第二设备的交互均可通过处理单元602来实现，具体实现过程可参考图3以及图4所示的方法实施例部分，这里不再赘述。
在具体实现时，请求方设备还可以包括策略单元503。策略单元503用于查询NS的部署模板中的VNF的描述信息。根据VNF的描述信息中的指示参数确定出需由所述第二设备实例化的VNF，基于确定结果触发处理单元602执行所述通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识的操作。策略单元503的具体实现可参考图3所示的方法实施例中的步骤S310，这里不再赘述。
在本申请所提供的几个实施例中，应该理解到，所公开的系统和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能模块可以集成在一个处理单元中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个单元中。上述集成的模块既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、随机存取存储器(英文全称：Random Access Memory，简称：RAM)、磁碟或者光盘等各种可以存储数据的介质。
本发明实施例还提供了另一种计算机存储介质，用于储存为上述存储节点所用的计算机软件指令，其包含用于执行上述图3所示方法实施例所设计的程序。
本发明实施例还提供了另一种计算机存储介质，用于储存为上述分布式存储系统所用的计算机软件指令，其包含用于执行上述图5以及迁移方法实施例所设计的程序。通过执行存储的程序，可以实现扩容迁移和冷热内容数据的迁移。
本领域技术人员应明白，本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中，与其它硬件一起提供或作为硬件的一部分，也可以采用其他分布形式，如通过Internet或其它有线或无线电信系统。
本发明是参照本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (14)

  1. 一种管理VNF实例化的方法，其特征在于，所述方法包括：
    第一设备接收请求方设备发起的实例化NS的请求，所述请求中携带所述NS中需通过第二设备实例化的虚拟化网络功能VNF的实例信息，所述实例信息包括所述VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息；
    所述第一设备根据所述状态信息确定出所述NS中待所述第二设备实例化的VNF，并记录所述需通过所述第二设备实例化的VNF的实例标识；
    在所述VNF被实例化的过程中，所述第一设备根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权。
  2. 如权利要求1所述的方法，其特征在于，所述VNF的实例标识是所述请求方设备在发起实例化所述NS的请求前，通过所述第二设备从虚拟网络功能管理器VNFM获取的。
  3. 如权利要求1或2所述的方法，其特征在于，在所述VNF被实例化的过程中，所述第一设备根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权，包括：
    所述第一设备接收所述VNMF在接收到所述第二设备发送的实例化所述VNF的请求后发起的授权请求；所述授权请求中携带所述VNF的实例标识；
    所述第一设备确定实例化所述VNF的条件是否满足，所述条件包括在实例化所述NS时记录的VNF的实例标识中存在所述授权请求中携带的所述VNF的实例标识；
    在确定满足实例化所述VNF的条件后，所述第一设备授权所述VNMF执行实例化所述VNF的操作。
  4. 如权利要求1-3任一项所述的方法，其特征在于，在确定满足实例化所述VNF的条件后，所述方法还包括：
    所述第一设备向所述VNFM发起订阅所述VNF实例的订阅请求，所述订阅请求用于请求所述VNFM在实例化所述VNF后，向所述第一设备发送通知消息；
    在所述VNF实例化成功后，所述第一设备接收来自所述VNFM的通知消息，所述通知消息用于指示所述VNF已实例化。
  5. 一种管理VNF实例化的方法，其特征在于，所述方法包括：
    请求方设备向第一设备发起实例化网络服务NS的请求，所述请求中包括所述NS中需通过第二设备实例化的VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息；其中，所述状态信息为待所述第二设备实例化的VNF的实例标识会被记录在所述第一设备中；
    所述请求方设备在接收到所述第一设备返回的NS实例化操作响应后，通过所述第二设备请求VNFM实例化所述VNF；在所述VNF被实例化的过程中，所述第一设备中记录的所述VNF的实例标识被用于实例化所述VNF的授权判断。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    请求方设备在请求实例化NS前，通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识；
    请求方设备接收所述VNFM创建的所述VNF的实例标识。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述请求方设备查询所述NS的部署模板中的VNF的描述信息；所述VNF的描述信息 信息中包括指示参数，所述指示参数的用于指示所述VNF是否通过所述第二设备实例化；
    根据所述指示参数确定出需由所述第二设备实例化的VNF，基于确定结果执行所述通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识的操作。
  8. 一种管理VNF实例化的装置，其特征在于，所述装置作为第一设备，所述装置包括：
    接收单元，用于接收请求方设备发起的实例化NS的请求，所述请求中携带所述NS中需通过第二设备实例化的VNF的实例信息，所述实例信息包括所述VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息；
    处理单元，用于根据所述状态信息确定出所述需通过所述第二设备实例化的VNF，记录所述需通过所述第二设备实例化的VNF的实例标识；
    管理单元，用于在所述VNF被实例化的过程中，根据所述NS实例化过程中记录的所述VNF的实例标识对所述VNF的实例化进行授权。
  9. 如权利要求8所述的装置，其特征在于，所述VNF的实例标识是所述请求方设备在发起实例化所述NS的请求前，通过所述第二设备从VNFM获取的。
  10. 如权利要求8或9所述的装置，其特征在于，所述管理单元具体用于接收所述VNMF在接收到所述第二设备发送的实例化所述VNF的请求后发起的授权请求，所述授权请求中携带所述VNF的实例标识；确定实例化所述VNF的条件是否满足，所述条件包括在实例化所述NS时记录的VNF的实例标识中存在所述授权请求中携带的所述VNF的实例标识；在确定满足实例化所述VNF的条件后，授权所述VNMF执行实例化所述VNF的操作。
  11. 如权利要求8-10任一项所述的装置，其特征在于，所述管理单元还用于在对所述VNF的实例化进行授权时，向所述VNFM发起订阅所述VNF实例的订阅请求，所述订阅请求用于请求所述VNFM在实例化所述VNF后，向所述装置发送通知消息；在所述VNF实例化成功后，接收来自所述VNFM的通知消息，所述通知消息用于指示所述VNF已实例化。
  12. 一种管理VNF实例化的装置，其特征在于，所述装置为请求方设备，所述装置包括：
    收发单元，用于向第一设备发起实例化NS的请求以及接收所述第一设备返回的NS实例化操作响应；所述请求中包括所述NS中需通过第二设备实例化的VNF的实例标识以及表明所述VNF待所述第二设备实例化的状态信息；其中，所述状态信息为待所述第二设备实例化的VNF的实例标识会被记录在所述第一设备中；
    处理单元，用于在收发单元接收到所述第一设备返回的NS实例化响应后，通过所述第二设备请求VNFM实例化所述VNF；在所述VNF被实例化的过程中，所述第一设备中记录的所述VNF的实例标识被用于实例化所述VNF的授权判断。
  13. 如权利要求12所述的装置，其特征在于，处理单元，还用于在收发单元发起实例化NS的请求前，通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识，并接收所述VNFM创建的所述VNF的实例标识。
  14. 如权利要求12或13所述的装置，其特征在于，所述装置还包括：
    策略单元，用于查询所述NS的部署模板中的VNF的描述信息；所述VNF的描述信息信息中包括指示参数，所述指示参数的用于指示所述VNF是否通过所述第二设备实例化；根据所述指示参数确定出需由所述第二设备实例化的VNF，基于确定结果触发所述处理单元执行所述通过所述第二设备请求VNFM创建所述NS中需通过所述第二设备实例化的VNF的实例标识的操作。
PCT/CN2018/085750 2017-06-29 2018-05-05 一种管理vnf实例化的方法和设备 WO2019001140A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18823763.0A EP3629160B1 (en) 2017-06-29 2018-05-05 Method and device for managing vnf instantiation
US16/725,579 US11301284B2 (en) 2017-06-29 2019-12-23 Method for managing VNF instantiation and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710516763.5A CN109213567B (zh) 2017-06-29 2017-06-29 一种管理vnf实例化的方法和设备
CN201710516763.5 2017-06-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/725,579 Continuation US11301284B2 (en) 2017-06-29 2019-12-23 Method for managing VNF instantiation and device

Publications (1)

Publication Number Publication Date
WO2019001140A1 true WO2019001140A1 (zh) 2019-01-03

Family

ID=64740330

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085750 WO2019001140A1 (zh) 2017-06-29 2018-05-05 一种管理vnf实例化的方法和设备

Country Status (4)

Country Link
US (1) US11301284B2 (zh)
EP (1) EP3629160B1 (zh)
CN (1) CN109213567B (zh)
WO (1) WO2019001140A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11327787B2 (en) * 2016-08-17 2022-05-10 Apple Inc. Using a managed object operation to control a lifecycle management operation
FR3071948A1 (fr) * 2017-09-29 2019-04-05 Orange Procede et dispositif de traitement d'une requete d'instanciation d'un service reseau.
US11082299B2 (en) * 2018-03-26 2021-08-03 Apple Inc. Managing virtual links in a network service instance
CN111581203B (zh) * 2019-02-19 2023-05-19 华为技术有限公司 信息处理方法、装置及存储介质
US20240267756A1 (en) * 2023-02-06 2024-08-08 Aira Technologies, Inc. System and methods for network cell management and mimo mode selection

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备
WO2016121802A1 (ja) * 2015-01-28 2016-08-04 日本電気株式会社 仮想化管理・オーケストレーション装置、仮想化管理・オーケストレーション方法、および、プログラム
CN106302068A (zh) * 2015-05-11 2017-01-04 中兴通讯股份有限公司 虚拟网络功能vnf的虚拟资源的管理方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2726699T3 (es) * 2014-08-07 2019-10-08 Intel Ip Corp Gestión de función de red virtualizada
CN104219127B (zh) * 2014-08-30 2018-06-26 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
KR102398401B1 (ko) * 2014-09-25 2022-05-13 애플 인크. 네트워크 기능 가상화
CN106031116B (zh) * 2015-01-19 2019-06-11 华为技术有限公司 一种ns与vnf的关联方法、装置及系统
CN105871570A (zh) * 2015-01-20 2016-08-17 中兴通讯股份有限公司 虚拟网络功能vnf的管理方法及装置
CN106161171B (zh) * 2015-03-23 2020-01-10 中兴通讯股份有限公司 一种建立网络业务实例的方法和装置
US10148731B2 (en) * 2015-06-30 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for on-boarding virtualized network function (VNF) packages in a network functions virtualization (NFV) system
WO2017035395A1 (en) * 2015-08-25 2017-03-02 Huawei Technologies Co., Ltd. System and method for network function virtualization resource management
EP3337094B1 (en) * 2015-08-31 2019-11-06 Huawei Technologies Co., Ltd. Method and apparatus for deploying network services
CN106533714A (zh) * 2015-09-09 2017-03-22 中兴通讯股份有限公司 重新实例化虚拟网络功能的方法和装置
CN106533935B (zh) * 2015-09-14 2019-07-12 华为技术有限公司 一种在云计算系统中获取业务链信息的方法和装置
WO2017119932A1 (en) * 2016-01-08 2017-07-13 Intel IP Corporation Techniques for instantiation and termination of virtualized network functions
KR102184512B1 (ko) * 2016-04-08 2020-11-30 후아웨이 테크놀러지 컴퍼니 리미티드 관리 방법 및 디바이스
EP3447965B1 (en) * 2016-05-06 2020-08-26 Huawei Technologies Co., Ltd. Network function instance management method and relevant device
EP3471454B1 (en) * 2016-07-07 2022-11-30 Huawei Technologies Co., Ltd. Network resource management method, apparatus and system
WO2018084975A1 (en) * 2016-11-02 2018-05-11 Intel IP Corporation Lifecycle management parameter modeling for virtual network functions
WO2018128875A1 (en) * 2017-01-05 2018-07-12 Intel IP Corporation Instantiation and management of physical and virtualized network functions of a radio access network node

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备
WO2016121802A1 (ja) * 2015-01-28 2016-08-04 日本電気株式会社 仮想化管理・オーケストレーション装置、仮想化管理・オーケストレーション方法、および、プログラム
CN106302068A (zh) * 2015-05-11 2017-01-04 中兴通讯股份有限公司 虚拟网络功能vnf的虚拟资源的管理方法及装置
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Also Published As

Publication number Publication date
CN109213567B (zh) 2022-05-13
US11301284B2 (en) 2022-04-12
US20200133708A1 (en) 2020-04-30
CN109213567A (zh) 2019-01-15
EP3629160B1 (en) 2023-11-08
EP3629160A1 (en) 2020-04-01
EP3629160A4 (en) 2020-05-13

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
US11928506B2 (en) Managing composition service entities with complex networks
US11947697B2 (en) Method and system to place resources in a known state to be used in a composed information handling system
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
WO2019184967A1 (zh) 一种网络切片的部署方法及装置
EP3291499B1 (en) Method and apparatus for network service capacity expansion
WO2019001140A1 (zh) 一种管理vnf实例化的方法和设备
US10397132B2 (en) System and method for granting virtualized network function life cycle management
JP6658882B2 (ja) 制御装置、ｖｎｆ配置先選択方法及びプログラム
WO2020011214A1 (zh) 管理虚拟化资源的方法和装置
CN107209642B (zh) 用于控制云环境中的资源的方法和实体
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
US20230221997A1 (en) System and method for subscription management using composed systems
CN105589731A (zh) 一种虚拟机迁移方法和装置
US11604595B2 (en) Data mirroring and data migration between storage volumes using system control processors
US11693703B2 (en) Monitoring resource utilization via intercepting bare metal communications between resources
WO2018039878A1 (zh) 一种虚拟资源的管理方法、装置及系统
WO2020077585A1 (zh) Vnf服务实例化方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
WO2023274014A1 (zh) 容器集群的存储资源管理方法、装置及系统
US12008412B2 (en) Resource selection for complex solutions
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备
WO2022141293A1 (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: 18823763

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018823763

Country of ref document: EP

Effective date: 20191227