WO2022141293A1 - 一种弹性伸缩的方法及装置 - Google Patents

一种弹性伸缩的方法及装置 Download PDF

Info

Publication number
WO2022141293A1
WO2022141293A1 PCT/CN2020/141795 CN2020141795W WO2022141293A1 WO 2022141293 A1 WO2022141293 A1 WO 2022141293A1 CN 2020141795 W CN2020141795 W CN 2020141795W WO 2022141293 A1 WO2022141293 A1 WO 2022141293A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
vnf
subnet
scale
vnfm
Prior art date
Application number
PCT/CN2020/141795
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 CN202080108288.8A priority Critical patent/CN116686264A/zh
Priority to JP2023539985A priority patent/JP2024502038A/ja
Priority to PCT/CN2020/141795 priority patent/WO2022141293A1/zh
Priority to EP20967632.9A priority patent/EP4262154A4/en
Publication of WO2022141293A1 publication Critical patent/WO2022141293A1/zh
Priority to US18/345,468 priority patent/US20230362065A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • 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/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets

Definitions

  • the present application relates to the field of Network Function Virtualization (NFV), and in particular, to a method and device for elastic scaling (Scaling) of a virtualized network function (Virtualized Network Function, VNF) or a network service (Network Service, NS).
  • NFV Network Function Virtualization
  • VNF Virtualized Network Function
  • NS Network Service
  • NFV Network Function Virtualization
  • IT information technology
  • NFV Network Function Virtualization
  • NS Network Service
  • OPEX operating cost
  • telecom network functions are implemented in software and can run on general-purpose server hardware, which can be migrated, instantiated, and deployed in different physical locations on the network as needed, without the need to install new equipment.
  • FIG 1 is a design example of a VNF descriptor or description template (VNF Descriptor, VNFD) given by the existing ETSI NFV standard.
  • the VNFD contains 2 virtual deployment units (Virtualisation Deployment Unit, VDU) VDU_1 and VDU_2, each VDU respectively Associate a connection point descriptor or description template (Connection Point Descriptor, CPD), which is used to describe or define CP_1 and CP_2, a virtual link descriptor or description template (Virtual Link Descriptor, VLD), which is used to describe or define A virtual link (Virtual Link, VL), the VL is used to connect VDU_1 and VDU_2.
  • VDU Virtualisation Deployment Unit
  • VDU_1 and VDU_2 each VDU respectively Associate a connection point descriptor or description template (Connection Point Descriptor, CPD), which is used to describe or define CP_1 and CP_2, a virtual link descriptor or description template (Virtual
  • the information contained in CP_1 can include:
  • the above information describes the IP address requirement information of CP_1.
  • the ip_address_type parameter indicates that the IP address type required by the CP is ipv4, and the number_of_ip_address parameter indicates that the minimum number of IP addresses required by the CP is 6.
  • CP_2 The information contained in CP_2 is similar and can include:
  • the above information describes the IP address requirements of CP_2.
  • the ip_address_type parameter indicates that the IP address type required by the CP is ipv4, and the number_of_ip_address parameter indicates that the minimum number of IP addresses required by the CP is 10.
  • VLD The information that VLD can contain is:
  • the above information describes the requirements for network connections between VDUs, including layer 2 network information l2_protocol_data and layer 3 network information l3_protocol_data.
  • l3_protocol_data it is stated that the layer 3 network connection is based on ipv4, and ip_allocation_pools defines the IP allocation resource pool of the layer 3 network.
  • the starting IP address is 192.168.1.1
  • the last IP address is 192.168.1.100, so it is known that the IP address resource pool contains 100 IP addresses.
  • VNFD also contains information for elastic scaling, for example, 2 scaling levels can be defined:
  • VDU_1 6 instances VDU_2 8 instances
  • VDU instances are all connected to the VL created by the VLD.
  • the IP address pool contained in the VL has a total of 100 IP addresses, which can meet the IP address allocation requirements.
  • VDU instances are all connected to the VL created by the VLD.
  • the IP address pool contained in the VL has a total of 100 IP addresses. Obviously, the VL cannot meet the requirements for IP address allocation at this time.
  • VNFD Network Service Descriptor
  • NSD Network Service Descriptor
  • the embodiments of the present invention provide an elastic scaling method and apparatus, which can avoid the situation of insufficient IP address allocation in the elastic scaling process of the VNF or NS in the prior art.
  • an embodiment of the present application provides an elastic scaling method, including the VNFM receiving a VNF capacity expansion Scale Out request from NFVO, where the request includes VNF instance information and indication information used to indicate the dimension Aspect and level Step of the Scale;
  • the VNFM determines the VDU to be created and the corresponding subnet Subnet information according to the VNF Scale request; the VNFM requests the VIM to create the VDU and the corresponding Subnet.
  • the above-mentioned VNFM determining the VDU to be created and the corresponding subnet information according to the VNF Scale Out request includes: the VNFM finds the corresponding VNFD according to the VNF instance information, and queries the VNFD according to the instruction information.
  • the VNFD determines the VDU to be created and the corresponding subnet Subnet information; wherein, the VNFD includes Scale Aspect and Step parameter information, and the Scale Step parameter information includes Subnet information.
  • the Subnet information includes one or more of the following: the number of subnets, the type and range of IP addresses that can be allocated for each subnet; the Scale Step parameter information also includes instructions for creating the The parameter of whether the VDU is connected to the Subnet.
  • an embodiment of the present application provides an elastic scaling method, including the NFVO receiving an NS capacity expansion Scale Out request, where the request includes NS instance information and indication information used to indicate the dimension Aspect and level Step of the Scale;
  • the NS Scale request determines the VNF to be created and the corresponding subnet Subnet information;
  • NFVO requests the VIM to create a VNF and the corresponding Subnet through the VNFM.
  • the above-mentioned NFVO determining the VNF to be created and the corresponding subnet information according to the NS Scale Out request includes: the VNFM finds the corresponding NSD according to the NS instance information, and queries the VNF according to the instruction information.
  • the NSD determines the VNF to be created and the corresponding subnet Subnet information; wherein, the NSD includes Scale Aspect and Step parameter information, and the Scale Step parameter information includes Subnet information.
  • an embodiment of the present application provides a communication apparatus, which can implement the method in the first aspect or any possible implementation manner of the first aspect.
  • the apparatus comprises corresponding units or components for carrying out the above-described method.
  • the units included in the apparatus may be implemented by software and/or hardware.
  • the apparatus may be, for example, a terminal, or a chip, a chip system, or a processor that can support the terminal to implement the above method.
  • an embodiment of the present application provides a communication apparatus, which can implement the method in the second aspect or any possible implementation manner of the second aspect.
  • the apparatus comprises corresponding units or components for carrying out the above-described method.
  • the units included in the apparatus may be implemented by software and/or hardware.
  • the apparatus may be, for example, a network device, or a chip, a chip system, or a processor that can support the network device to implement the above method.
  • an embodiment of the present application provides a computer-readable medium on which a computer program or instruction is stored, and when the computer program or instruction is executed, enables a computer to execute the first aspect or any possibility of the first aspect. method described in the implementation of .
  • an embodiment of the present application provides a computer-readable medium on which a computer program or instruction is stored, and when the computer program or instruction is executed, enables a computer to execute the second aspect or any possibility of the second aspect. method described in the implementation of .
  • an embodiment of the present application provides an elastic scaling system.
  • the system includes an NFVO, a VNFM and a VIM, which are respectively used to implement the steps performed by the NFVO, the VNFM and the VIM in any of the possible methods of the first aspect or the second aspect.
  • any of the communication devices, chips, computer-readable media, computer program products or communication systems provided above are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved are: It can avoid the situation of insufficient IP address allocation when the VNF or NS is expanded in the prior art, or it can also avoid the situation that the prior art directly defines a large IP address resource pool and finally causes waste.
  • FIG. 1 is a schematic diagram of a VNFD design example provided by the prior art
  • FIG. 2 is a schematic diagram of the architecture of an NFV network system according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a hardware structure of a communication device of each NFV network element according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of the method for elastic scaling (capacity expansion) provided by Embodiment 1 of the present application;
  • FIG. 5 is a schematic flowchart of a method for elastic scaling (capacity expansion) provided by Embodiment 2 of the present application;
  • FIG. 6 is a schematic flowchart of the method for elastic scaling (shrinking) provided by Embodiment 3 of the present application;
  • FIG. 7 is a schematic diagram of an NSD design example provided in Embodiment 4 of the present application.
  • FIG. 8 is a schematic flowchart of a method for elastic scaling (capacity expansion) provided by Embodiment 4 of the present application;
  • FIG. 9 is a schematic flowchart of a method for elastic scaling (shrinking) provided in Embodiment 5 of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the composition of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of an NFV system 20 according to an embodiment of the present application.
  • the NFV system 20 can be used in various networks, eg implemented in a data center (data center 201 or data center 206 shown in FIG. 2 ), a carrier network or a local area network.
  • NFV system 20 includes NFV management and orchestration system (NFV management and orchestration, NFV MANO) 201, NFV infrastructure (NFV infrastructure, NFVI) 202, multiple VNFs 203, multiple network element management (element management, EM) 204, and Operations support system and business support system (OSS/BSS) 205.
  • NFV management and orchestration NFV management and orchestration
  • NFV MANO NFV management and orchestration
  • NFV infrastructure NFV infrastructure
  • EM multiple network element management
  • OSS/BSS Operations support system and business support system
  • NFV MANO 201 can be used to perform monitoring and management of NFVI 202 and VNF 203.
  • NFV MANO 201 may include NFV Orchestrator (NFVO) 2011, one or more VNF Managers (VNFM) 2012 and VIM 2013.
  • NFVO 2011 can be used to manage the life cycle of virtualized services, as well as allocate and schedule virtual resources in NFVI 202, etc.
  • NFVO 2011 can communicate with one or more VNFMs 2012 to perform resource-related requests; NFVO 2011 can also send configuration information to VNFM 2012 to collect VNF 203 status information.
  • NFVO 2011 may also communicate with VIM 2013 to perform resource allocation, and/or reservation, and to exchange virtualized hardware resource configuration and status information.
  • VNFM 2012 can be used to manage the life cycle of one or more VNFs, for example, instantiating VNF 203, updating VNF 203, querying VNF 203, scaling VNF 203, terminating VNF 203 Wait. Further, VNFM 2012 can communicate with VNF 203 to complete VNF lifecycle management and exchange configuration and status information. In an NFV system, there can be multiple VNFMs. Different VNFMs can manage the lifecycle of different types of VNFs. The VIM 2013 can control and manage the interaction of the VNF 203 with computing hardware 2024, storage hardware 2025, network hardware 2026, virtual computing (virtual computing) 2021, virtual storage 2022, and virtual network 2023.
  • VIM 2013 can perform resource management functions, including managing infrastructure resources, allocating (eg adding resources to virtual containers) and running functions (eg collecting NFVI fault information).
  • VNFM 2012 and VIM 2013 can communicate with each other to request resource allocation, exchange virtualized hardware resource configuration and status information, etc.
  • NFVI 202 in FIG. 2 includes a hardware resource layer, a virtualization layer, and a virtual resource layer.
  • NFVI 202 includes hardware resources, software resources, or a combination of the two to complete the deployment of the virtualized environment.
  • hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for VNF 203.
  • the hardware resource layer includes computing hardware 2024 , storage hardware 2025 and network hardware 2026 .
  • Computing hardware 2024 may be off-the-shelf hardware and/or custom-made hardware to provide processing and computing resources.
  • the storage hardware 2025 may be storage capacity provided within the network or storage capacity residing in the storage hardware 2025 itself (local storage within the server).
  • the resources of computing hardware 2024 and storage hardware 2025 may be pooled.
  • Network hardware 2026 may be a switch, router, and/or any other network device configured to have switching capabilities.
  • Network hardware 2026 may span multiple domains and may include multiple networks interconnected by one or more transport networks.
  • the virtualization layer in NFVI 202 can abstract hardware resources from the physical layer and decouple VNF 203 in order to provide virtualized resources to VNF 203.
  • the virtual resource layer includes virtual computing 2021 , virtual storage 2022 and virtual network 2023 .
  • Virtual computing 2021 and virtual storage 2022 may be provided to VNF 203 in the form of virtual machines, and/or other virtual containers.
  • one or more VNFs 203 may be deployed on a virtual machine (VM).
  • the virtualization layer abstracts the network hardware 2026, thereby forming a virtual network 2023, which may include a virtual switch used to provide connections between virtual machines and other virtual machines.
  • the computing hardware 2024, the storage hardware 2025, and the network hardware 2026 may include multiple racks, or multiple racks, or even multiple computer rooms.
  • the EM 204 is a system used to configure and manage network elements in a traditional telecommunication system.
  • the EM 204 can also be used to configure and manage the VNF, and initiate lifecycle management operations such as instantiation of a new VNF to the VNFM.
  • OSS/BSS 205 supports various end-to-end telecom services.
  • the management functions supported by OSS include: network configuration, service provision, and fault management.
  • BSS can be used to process orders, payment, revenue, etc., and support product management, order management, revenue management and customer management.
  • the NFV system 20 shown in FIG. 2 is only used for example, and is not used to limit the technical solution of the present application. Those skilled in the art should understand that in the specific implementation process, the NFV system 20 may also include other network elements, and the number of each network element may also be determined according to specific needs, which is not limited.
  • each network element in FIG. 2 in this embodiment of the present application may be a functional module in a device.
  • the function module may be an element in a hardware device, a software function module running on the hardware, or a virtualized function instantiated on a platform (eg, a cloud platform).
  • each network element in FIG. 2 may be implemented by the communication device 30 in FIG. 3 .
  • FIG. 3 is a schematic diagram of a hardware structure of a communication device applicable to this embodiment of the present application.
  • the communication apparatus 30 includes at least one processor 301 and at least one communication interface 304, and is used for implementing the method provided by the embodiment of the present application.
  • the communication device 30 may also include a communication line 302 and a memory 303 .
  • the processor 301 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 302 may include a path, such as a bus, to transfer information between the components described above.
  • the communication interface 304 can be any device such as a transceiver, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, a pin , bus, or transceiver circuit, etc.
  • RAN radio access network
  • WLAN wireless local area network
  • Memory 303 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, CD-ROM storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being executed by a computer Access any other medium without limitation.
  • the memory may exist independently and be coupled to the processor 301 through the communication line 302 .
  • the memory 303 may also be integrated with the processor 301 .
  • the memory provided by the embodiments of the present application may generally be non-volatile.
  • the memory 303 is used for storing computer-executed instructions involved in executing the solutions provided by the embodiments of the present application, and the execution is controlled by the processor 301 .
  • the processor 301 is configured to execute the computer-executed instructions stored in the memory 303, so as to implement the method provided by the embodiments of the present application.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3 .
  • the communication apparatus 30 may include multiple processors, such as the processor 301 and the processor 305 in FIG. 3 .
  • processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the above-mentioned communication apparatus 30 may be a general-purpose device or a dedicated device.
  • the communication device 30 may be a desktop computer, a network server or a device with a similar structure in FIG. 3 .
  • This embodiment of the present application does not limit the type of the communication device 30 .
  • A/B may indicate A or B
  • a and/or may be used to describe There are three kinds of relationships between related objects, for example, A and/or B, which can be expressed as: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural.
  • words such as “first” and “second” may be used to distinguish technical features with the same or similar functions.
  • the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like do not limit certain differences.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations, and any embodiment or design solution described as “exemplary” or “for example” should not be construed are preferred or advantageous over other embodiments or designs.
  • the use of words such as “exemplary” or “such as” is intended to present the relevant concepts in a specific manner to facilitate understanding.
  • the NFVO, and/or the VIM, and/or the VNFM may perform some or all of the steps in the embodiments of the present application, these steps are only examples, and the embodiments of the present application may also perform other steps or Variations of various steps.
  • various steps may be performed in different orders presented in the embodiments of the present application, and it may not be necessary to perform all the steps in the embodiments of the present application.
  • the specific structure of the execution body of the method for establishing a network connection is not particularly limited in the embodiments of the present application, as long as the methods provided in the embodiments of the present application can be implemented.
  • the execution body of the method for establishing a network connection provided in this embodiment of the present application may be NFVO, or a component applied in NFVO, such as a chip, which is not limited in this application.
  • the execution body of the method for establishing a network connection provided in this embodiment of the present application may be a VIM, or a component applied in a VIM, such as a chip, which is not limited in this application.
  • the execution body of the method for establishing a network connection may be a VNFM, or a component applied in the VNFM, such as a chip, which is not limited in this application.
  • the following embodiments are described by taking as an example that the execution bodies of the method for establishing a network connection are NFVO, VIM, and VNFM respectively.
  • FIG. 4 is a flowchart of Embodiment 1 of the present invention.
  • Both Embodiments 1 and 2 describe the process of scaling out (Scale Out) in the VNF elastic scaling (or called "scaling capacity").
  • the main difference is whether the newly created VDU must be connected or associated with the newly created Subnet. In Example 1, the connection or association must be performed, and in Example 2, the connection or association is not necessarily performed.
  • Embodiment 1 The specific implementation steps of Embodiment 1 are described below:
  • VNF elastic scaling request an elastic scaling request for VNF (referred to as "VNF elastic scaling request") to VNFM, which is specifically a Scale Out request in this embodiment, and the request includes VNF instance information (such as VNF instance ID), And the indication information for indicating the dimension or range (Aspect) and level (Step) of the Scale.
  • the above-mentioned indication information for indicating the dimension (Aspect) of the Scale mainly includes AspectId, which corresponds to a Scale Aspect defined in the VNFD, and the Scale Aspect in the VNFD contains specific VDU and VL names, quantities and/or characteristics and other related information.
  • the indication information used to indicate the Step mainly includes the level of elastic scaling in the Aspect, such as Step 1 or Step 2.
  • the VNFM receives the above VNF Scale request, finds the corresponding VNFD according to the VNF instance information in the request, and queries the VNFD according to the instruction information, and determines the VDU to be created and the corresponding subnet information.
  • VNFD The aspect defined by VNFD in the prior art includes the detailed parameter ScalingDelta of elastic scaling, as shown in the following table:
  • the parameter vduDelta describes the VDU elastic details parameters, mainly the number of related VDU instances;
  • the parameter virtualLinkBitRateDelta describes the virtual link elastic details parameters, mainly the bit rate of the related virtual link.
  • Steps are defined in the VNFD.
  • the following 2 levels of Step can be defined:
  • Step 1 VDU_1 has a total of 3 instances, VDU_2 has a total of 4 instances, and the VL bit rate is 4Gbps;
  • Step 2 there are 6 instances of VDU_1, 8 instances of VDU_2, and the VL bit rate is 8Gbps.
  • N is an integer greater than or equal to 1
  • SubnetInfo including the content L3ProtocolData
  • DedicatedOrNot: true/false is included or associated in the above Step 2.
  • DedicatedOrNot: true/false is optional (Optional). If N is 1, it indicates that a new Subnet needs to be created.
  • L3ProtocolData define the information required to create the one Subnet, including the IP address type and range, as follows:
  • N is more than one, the number of SubnetInfo parameters is also N; since the parameter NumberofSubnet is optional, if there is no NumberofSubnet parameter, add as many Subnets as there are SubnetInfo parameters, and each SubnetInfo corresponds to adding a Subnet.
  • VDUs are connected or associated. True indicates that the newly created Subnet must be connected or associated with the newly created VDU above. False indicates that the newly created VDU instance does not necessarily need to be associated with a new Subnet instance. You can first associate the existing Subnet instance in the VL. Then associate the new Subnet information. The value of DedicatedOrNot in this Example 1 is true.
  • the VNFM After the VNFM receives the above VNF Scale request, it first finds the corresponding VNFD according to the VNF instance information in the request, such as the VNF instance ID, which is the above-mentioned extended VNFD. Then query the VNFD according to the instruction information, specifically, find and determine the dimension or range of elastic scaling in the VNFD through the Aspect ID included in the instruction information, and then search the VNFD according to the Step information in the instruction information and determine the level and related Scale required content.
  • the VNFM After the VNFM receives the above VNF Scale request, it first finds the corresponding VNFD according to the VNF instance information in the request, such as the VNF instance ID, which is the above-mentioned extended VNFD. Then query the VNFD according to the instruction information, specifically, find and determine the dimension or range of elastic scaling in the VNFD through the Aspect ID included in the instruction information, and then search the VNFD according to the Step information in the instruction information and determine the level and
  • the VNFM looks up the VNFD to determine that the Aspects corresponding to the ID XXX in the VNFD include VDU_1, VDU_2 and VL; in addition, if the Step indication information in the above VNF Scale request is For level 2, the VNFM finds the VNFD and determines that level 2 in the above example needs to create 6 VDU_1 instances, 8 VDU_2 instances, the VL bit rate is 8Gbps, and a new Subnet needs to be created, and its specific instantiation parameters are included in L3ProtocolData , and the newly created VDU must be associated with the above Subnet.
  • the number of newly created VDUs is the number of VDUs in the corresponding level minus the number of VDUs included in the VNF before Scale. Then in this example, a total of 6 VDU_1 instances and 8 VDU_2 instances need to be created in level 2, then the newly created VDU_1 and VDU_2 numbers are 6 VDU_1 instances minus the number of VDU_1 instances of the VNF before Scale (for example, 3) , 8 VDU_2 minus the number of VDU_2 instances of the existing VNF (for example, 6), then the number of newly created VDU_1 and VDU_2 is 3 and 2 respectively.
  • the method for determining the number of created Subnets is different from that of the above VDU creation. NumberofSubnet: 1 indicates that a new subnet needs to be created, regardless of the existing number of Subnets in the virtual link VL in the existing VNF.
  • the VNFM sends a resource authorization Resource Grant request to the NFVO, that is, a request for authorization to create resources, including the VDU instance resources and Subnet resources that need to be newly created as determined in step 402 above.
  • a resource authorization Resource Grant request to the NFVO, that is, a request for authorization to create resources, including the VDU instance resources and Subnet resources that need to be newly created as determined in step 402 above.
  • the request includes:
  • VLD identity of VLD in VNFD
  • the NFVO returns an authorization permission message to the VNFM, carrying the VIM access information and the like.
  • the VNFM applies to the VIM to create a new Subnet instance according to the Subnet information determined in step 402, where the Subnet contains the new IP address range or resource pool information. For example, it could be:
  • VNFM After receiving the notification message of Subnet creation completion, VNFM initiates an authorization request to create Linkport to NFVO.
  • the request carries the following information:
  • the NFVO sends an Authorization Allow message to the VNFM.
  • the VNFM initiates the creation of a Linkport to the VIM, which carries the Subnet instance information that needs to be associated.
  • the VNFM applies to the VIM to create a new VDU instance, carrying the type and quantity of the VDU determined in step 402 above, and carrying the newly created Linkport information.
  • VIM creates a VDU instance, it associates with the newly created Subnet through Linkport, and the newly created Subnet assigns an IP address to it.
  • a corresponding number of IP addresses can be allocated according to the expansion size (corresponding to different Steps) during capacity expansion to dynamically meet the address requirements of the newly created VDU , which can avoid the situation of insufficient IP address allocation when the VNF is expanded in the prior art; and can also avoid the situation that the prior art directly defines a large IP address resource pool and finally causes waste.
  • FIG. 5 is a flowchart of Embodiment 2.
  • Embodiment 2 differs from Embodiment 1 in that the newly created VDU is not necessarily connected or associated with the newly created Subnet.
  • Embodiment 2 The specific implementation steps of Embodiment 2 are described below:
  • Step 502. The difference from Step 402 in Embodiment 1 lies in Step 2 defined in the VNFD, and the value of DedicatedOrNot included in it is false, indicating that the newly added VDU instance does not necessarily have to be associated with the newly created Subnet instance
  • VNFM initiates a Linkport authorization request to NFVO that only carries the Linkport information and does not carry the Subnet information. For example, you can As follows:
  • the VNFM applies to the VIM to create a Linkport. If the VNFM determines that an IP address can still be assigned to the Subnet in the original VL network, the newly created Linkport is associated with the existing Subnet information, otherwise it is associated with the new Subnet information.
  • VIM creates a VDU instance
  • the existing Subnet through Linkport (the Subnet in the original VL network can also be assigned an IP address), and the existing Subnet assigns an IP address to it, or associates it with the newly created Subnet.
  • the newly created Subnet assigns an IP address to it.
  • FIG. 6 is a flowchart of Embodiment 3 of the present invention.
  • Embodiment 3 is a subsequent step of Embodiment 1 or 2 above, and describes a process of VNF scaling (Scale In).
  • Embodiment 3 The specific implementation steps of Embodiment 3 are described below:
  • NFVO sends an elastic scaling request for VNF to VNFM, which is specifically a Scale In request in this embodiment, and the request includes VNF instance information (such as VNF instance ID) and a range for indicating Scale ( Aspect) and level (Step) indication information.
  • VNF instance information such as VNF instance ID
  • Step level
  • the VNF is scaled down from the second level to the first level.
  • the VNFM receives the VNF Scale request, finds the corresponding VNFD according to the VNF instance information in the request, and queries the VNFD according to the instruction information to determine the VDU to be deleted and the corresponding subnet information.
  • the same VNFD as in Embodiment 1 is still used, which still includes the following two levels:
  • Step 1 there are 3 instances of VDU_1, 4 instances of VDU_2, and the VL bit rate is 4Gbps;
  • Step 2 VDU_1 has 6 instances, VDU_2 has 8 instances, VL bit rate is 8Gbps, NumberofSubnet: 1, L3ProtocolData, DedicatedOrNot: true
  • VDU_1 needs to be reduced by 3 instances
  • VDU_2 needs to be reduced by 4 instances
  • VL needs to delete a Subnet (that is, similar to the newly created Subnet in Embodiment 1).
  • the VNFM sends an authorization (Grant) request to the NFVO, and the RemoveResource parameter in the Grant request contains the description information of the Subnet resource, Compute resource (corresponding to VDU), and Linkport resource to be deleted.
  • Grant authorization
  • the RemoveResource parameter in the Grant request contains the description information of the Subnet resource, Compute resource (corresponding to VDU), and Linkport resource to be deleted.
  • the VNFM receives the authorization allow message from the NFVO.
  • the VNFM applies to the VIM to delete the corresponding Subnet resources, virtual machine resources and Linkport resources corresponding to the VUD.
  • the VIM sends a resource deletion success message to the VNFM.
  • VNFM sends a Scale In complete message to NFVO.
  • FIG. 7 is a schematic diagram of a design example of an NS description file (NS Descriptor, NSD), which mainly includes VNFDs describing VNFs, such as the corresponding VNFD 1 and VNFD 2 of VNF_1 and VNF_2 in the description figure, describing the virtual link VL
  • NSD Networkal Connection Point
  • Descriptor Descriptor
  • Embodiments 1 to 3 describe the scenario of expanding and shrinking the VNF.
  • the corresponding NsVld connecting VNF_1 and VNF_2 will also have insufficient IP addresses.
  • the NS elastic scaling process in the following Embodiments 4 and 5 of the present invention can also solve the above problem.
  • FIG. 8 is a flowchart of NS elastic scaling (Scale) according to Embodiment 4 of the present invention, specifically a Scale Out flowchart.
  • the concrete steps of embodiment 4 are as follows:
  • NFVO receives an elastic scaling request (referred to as "NS elastic scaling request") for NS from OSS/BSS, which is specifically a Scale Out request in this embodiment, and the request includes NS instance information (such as NS Instance information). Instance ID), and indication information for indicating the range (Aspect) and level (Step) of the Scale.
  • NS elastic scaling request an elastic scaling request for NS from OSS/BSS, which is specifically a Scale Out request in this embodiment, and the request includes NS instance information (such as NS Instance information). Instance ID), and indication information for indicating the range (Aspect) and level (Step) of the Scale.
  • NVFO receives the above Scale Out request, finds the corresponding NSD according to the NS instance information in the request, and queries the NSD according to the instruction information to determine the VNF to be created and the corresponding subnet Subnet information.
  • this embodiment mainly extends the virtualLinkToLevelMapping information in NsLevel (similar to virtualLinkBitRateDelta in ScalingDelta of VNFD).
  • the expanded virtualLinkToLevelMapping contains the following information:
  • NsLevel the 2 levels Step that can be defined by NsLevel are (the following specific numbers are examples):
  • VNF_1 has a total of 3 instances
  • VNF_2 has a total of 4 instances
  • the VL bit rate is 4Gbps
  • Step2 there are 6 instances of VNF_1, 8 instances of VNF_2, and the VL bit rate is 8Gbps.
  • N is an integer greater than or equal to 1
  • SubnetInfo including the content L3ProtocolData
  • DedicatedOrNot: true/false is included or associated with each other.
  • DedicatedOrNot: true/false is optional (Optional).
  • NFVO After receiving the above Scale Out request, NFVO first finds the corresponding NSD according to the NS instance information in the request, such as the NS instance ID, which is the above-mentioned extended NSD. Then query the NSD according to the instruction information, specifically find and determine the object or range of elastic scaling (Scale) in the NSD through the Aspect in the instruction information, and then look up the NSD according to the Step in the instruction information and determine the level that requires Scale.
  • the NS instance information such as the NS instance ID
  • Scale object or range of elastic scaling
  • the VNFM determines the level 2 in the above example by looking up the NSD, and needs to create 6 instances of VNF_1, 8 instances of VNF_2 and VL
  • the bit rate is 8Gbps, and a new Subnet needs to be created. Its specific instantiation parameters are included in L3ProtocolData, and the newly created VNF must be associated with the above Subnet.
  • the number of newly created VNFs is the number of VNFs in the corresponding level minus the number of VNFs included in the VNF before Scale.
  • VNF_1 and VNF_2 numbers are 6 VNF_1 instances minus the number of VNF_1 instances of the VNF before Scale (for example, 2) , 8 VNF_2 minus the number of VNF_2 instances of the existing VNF (for example, 5), then the number of newly created VNF_1 and VNF_2 is 4 and 3 respectively.
  • the method for determining the number of created Subnets is different from that of the above VNF creation. NumberofSubnet: 1 indicates that a new subnet needs to be created, regardless of the existing number of Subnets in the virtual link VL in the existing VNF.
  • the NFVO determines that a new Subnet needs to be created on the original VL instance, and then applies to the VIM to create the Subnet.
  • NFVO sends an instantiated VNF request to VNFM according to the newly created VNF instance, and carries the VL instance information that the VNF (via VnfExtCp_1) needs to connect to. Since the value of DedicatedOrNot in the second level defined by Nslevel in NSD is true, in the The VL instance information also includes the information of the Subnet instance newly created in step 803 .
  • step 804 the VNFM sends a Grant request to the NFVO, authorizes the creation of a new Linkport, and adds the associated information with the Subnet instance in addResource.
  • NFVO sends an Authorization Allow message to VNFM.
  • VNFM applies to VIM to create a Linkport, which contains new Subnet information.
  • the VNFM applies to the VIM to create a new VNF instance, and connects to the Subnet through VnfExtCp_1 and the newly created Linkport.
  • the VIM completes the creation of the VNF instance by creating the VDU, and associates it with the newly created Subnet through the Linkport.
  • Embodiment 5 of the present invention is the Scale In process in NS elastic scaling, which is similar to the Scale In process of VNF, as shown in Figure 9, and the specific steps are as follows:
  • NFVO receives an elastic scaling (Scale) request for NS from OSS/BSS, specifically a Scale
  • the request includes NS instance information (such as NS instance ID), and Indication information for indicating the range (Aspect) and level (Step) of the Scale.
  • the NS is scaled down from the second level to the first level.
  • NFVO finds the corresponding NSD according to the NS instance ID information in the request, and queries the NSD according to the instruction information to determine the VNF to be deleted and the corresponding subnet information.
  • the same NSD as in Embodiment 4 is still used, and the 2 levels Step that can be defined by its NsLevel are (the following specific numbers are examples):
  • VNF_1 has a total of 3 instances
  • VNF_2 has a total of 4 instances
  • the VL bit rate is 4Gbps
  • Step2 there are 6 instances of VNF_1, 8 instances of VNF_2, and the VL bit rate is 8Gbps.
  • Step 2 the parameters NumberofSubnet: 1, SubnetInfo (including the content L3ProtocolData) and DedicatedOrNot: true/false are added. Among them DedicatedOrNot: true/false is optional (Optional).
  • VNF_1 needs to reduce 3 instances
  • VNF_2 needs to reduce 4 instances
  • VL needs to delete a Subnet.
  • the NVFO applies to the VIM to delete the corresponding Subnet resources, virtual machine resources and Linkport resources corresponding to different VDUs included in the VNF.
  • VIM completes the deletion of resources, and sends a resource deletion success message to NFVO.
  • NFVO, VNFM or VIM in the method steps of the above embodiments may be executed by the processor 401 in the communication device 40 shown in FIG. 4 calling the application code stored in the memory 403, which is not performed in this embodiment any restrictions.
  • the foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements.
  • the above-mentioned NFVO, VNFM, or VIM, etc. include corresponding hardware structures and/or software modules for performing each function.
  • Those skilled in the art should easily realize that the unit and algorithm operations of each example described in conjunction with the embodiments disclosed herein can be implemented in hardware or in the form of a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • NFVO NFVO
  • VNFM NFVM
  • VIM Integrated Multimedia Subsystem
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 10 shows a schematic structural diagram of a communication apparatus 100 .
  • the communication device 100 includes a transceiver module 1001 and a processing module 1002 .
  • the communication device 100 is used to implement the functions of the VNFM.
  • the communication apparatus 100 is, for example, the VNFM described in the embodiment shown in FIG. 4 , the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 .
  • the communication apparatus 100 may be a VNFM, or may be a chip applied in the VNFM, or other combined devices or components having the above-mentioned VNFM functions.
  • the transceiver module 1001 may be a transceiver, the transceiver may include an antenna and a radio frequency circuit, etc.
  • the processing module 1002 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may Include one or more CPUs.
  • the transceiver module 1001 may be a radio frequency unit, and the processing module 1002 may be a processor (or a processing circuit), such as a baseband processor.
  • the transceiver module 1001 may be an input/output interface of a chip (eg, a baseband chip), and the processing module 1002 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
  • transceiver module 1001 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component
  • processing module 1002 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit).
  • the transceiving module 1001 may be used to perform all transceiving operations performed by the VNFM in the embodiment shown in FIG. 4, such as S401 and S403, and/or other processes for supporting the techniques described herein.
  • the processing module 1002 may be configured to perform all operations performed by the VNFM in the embodiment shown in FIG. 4 except for the transceiving operations, eg, S402, and/or other processes for supporting the techniques described herein.
  • the transceiving module 1001 may be used to perform all transceiving operations performed by the VNFM in the embodiment shown in FIG. 6, such as S601 and S603, and/or other processes for supporting the techniques described herein.
  • the processing module 1002 may be configured to perform all operations performed by the VNFM in the embodiment shown in FIG. 6 except for the transceiving operations, eg, S602, and/or other processes for supporting the techniques described herein.
  • the communication device 100 may be used to implement the functionality of NFVO.
  • the communication apparatus 100 is, for example, the NFVO described in the embodiment shown in FIG. 8 or the embodiment shown in FIG. 9 , and may also be the NFVO in the embodiments shown in FIG. 4 to FIG. 6 , which will not be described repeatedly.
  • the communication apparatus 100 may be a VIM, or may be a chip applied in the VIM, or other combined device or component having the above-mentioned VIM function.
  • the transceiver module 1001 may be a transceiver, and the transceiver may include an antenna and a radio frequency circuit, etc.
  • the processing module 1002 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may Include one or more CPUs.
  • the transceiver module 1001 may be a radio frequency unit, and the processing module 1002 may be a processor (or a processing circuit), such as a baseband processor.
  • the transceiver module 1001 may be an input/output interface of a chip (eg, a baseband chip), and the processing module 1002 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
  • transceiver module 1001 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component
  • processing module 1002 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit).
  • the transceiving module 1001 can be used to perform all transceiving operations performed by the VIM in the embodiments shown in FIGS. 4 to 6 and 8 to 9
  • the processing module 1002 can be used to perform the operations of FIGS. to all operations performed by the VIM in the embodiment shown in FIG. 9 except for transceiving operations, and/or other processes used to support the techniques described herein.
  • FIG. 11 shows a schematic diagram of the composition of a communication system.
  • the communication system 110 may include: NFVO 1101, VNFM 1102 and VIM 1103. It should be noted that FIG. 11 is only an exemplary drawing, and the embodiment of the present application does not limit the network elements and the number of network elements included in the communication system 110 shown in FIG. 11 .
  • the VNFM 1102 is used to implement the functions of the VNFM in the above embodiments.
  • the VNFM 1102 can be used to receive the elastic scaling request information from the NFVO 1101, query and query the VNFD according to the request information, determine the VDU and corresponding subnet information to be created, and apply to the VIM 1103 to create the VDU and the corresponding subnet Subnet.
  • the NFVO 1101 is used to implement the functions of the NFVO in the above method embodiments, and the VIM 1103 is used to implement the functions of the VIM in the above method embodiments, which will not be repeated.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

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)

Abstract

本发明实施例公开了一种弹性伸缩的方法、装置及***，涉及NFV领域，包括VNFM接收来自NFVO的VNF扩容Scale Out请求，所述请求包括VNF实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；VNFM根据所述VNF Scale请求确定需要创建的VDU以及相应子网Subnet信息；VNFM向VIM请求创建VDU和相应的Subnet。本发明实施例可以动态满足新创建的VDU或VNF的地址需求，可以避免现有技术VNF或NS扩容时，出现IP地址分配不足的情况，也可以避免现有技术直接定义很大的IP地址资源池，最后造成浪费的情况。

Description

一种弹性伸缩的方法及装置 技术领域
本申请涉及网络功能虚拟化(Network Function Virtualization，NFV)领域，尤其涉及虚拟化网络功能(Virtualized Network Function，VNF)或网络服务(Network Service,NS)弹性伸缩(Scaling)的方法及装置。
背景技术
网络功能虚拟化(NFV,Network Function Virtualization)是指电信网络运营商借鉴了信息技术(IT,Information Technology)领域的虚拟化技术，在通用的服务器、交换机和存储器中将部分电信网络功能(例如：核心网功能)的实现进行软件和硬件解耦，从而实现网络服务(NS,Network Service)快速、高效部署和运营，同时达到节省网络投资成本CAPEX和运营成本OPEX的目标。通过应用NFV技术，电信网络功能以软件方式实现，并能在通用的服务器硬件上运行，可以根据需要进行迁移、实例化(Instantiation)、部署在网络的不同物理位置，并且不需要安装新设备。
图1是现有ETSI NFV标准给出的一个VNF描述符或描述模板(VNF Descriptor,VNFD)设计实例，该VNFD包含2个虚拟部署单元(Virtualisation Deployment Unit,VDU)VDU_1和VDU_2，每个VDU分别关联一个连接点描述符或描述模板(Connection Point Descriptor，CPD)，其用来描述或定义CP_1和CP_2，一个虚拟链路描述符或描述模板(Virtual Link Descriptor,VLD)，其用来描述或定义虚拟链路(Virtual Link,VL)，所述VL用来连接VDU_1和VDU_2。
其中CP_1中包含的信息可以有：
address_data:
address_type:ip_address
l3_address_data:
ip_address_assignment:true
floating_ip_activated:true
ip_address_type:ipv4
number_of_ip_address:6
上述信息描述了CP_1对IP地址的需求信息，其中ip_address_type参数说明该CP所需要的IP地址类型为ipv4，number_of_ip_address参数说明该CP所需要的最少IP地址数量为6个。
其中CP_2中包含的信息类似，可以有：
address_data:
address_type:ip_address
l3_address_data:
ip_address_assignment:true
floating_ip_activated:true
ip_address_type:ipv4
number_of_ip_address:10
上述信息描述了CP_2对IP地址的需求信息，其中ip_address_type参数说明该CP所需要的IP地址类型为ipv4，number_of_ip_address参数说明该CP所需要的最少IP地址数量为10个。
其中VLD可以包含的信息为：
vl_profile:
virtual_link_protocol_data:
-associated_layer_protocol:ethernet
l2_protocol_data:
network_type:vlan
-associated_layer_protocol:ipv4
l3_protocol_data:
ip_version:ipv4
ip_allocation_pools:
-start_ip_address:192.168.1.1
-end_ip_address:192.168.1.100
上述信息描述了VDU之间网络连接的需求信息，其中包含2层网络信息l2_protocol_data和3层网络信息l3_protocol_data，l3_protocol_data中说明该3层网络连接基于ipv4，ip_allocation_pools定义了该3层网络的IP分配资源池信息，起始IP地址为192.168.1.1，最后一个IP地址为192.168.1.100，从而知道该IP地址资源池包含IP地址100个。
VNFD里还包含有针对弹性扩缩容的信息，比如可以定义2个伸缩级别：
1.VDU_1 3个实例，VDU_2 4个实例
2.VDU_1 6个实例，VDU_2 8个实例
针对级别1，可以计算出3个VDU_1所需要的IP地址为3*6＝18，4个VDU_2所需要的IP地址为4*10＝40，总需要IP地址为18+40＝58。这些VDU实例都是连接在通过VLD创建的VL上，该VL包含的IP地址池共有IP100个，可以满足IP地址分配需求。
针对级别2，可以计算出6个VDU_1所需要的IP地址为6*6＝24，8个VDU_2所需要的IP地址为8*10＝80，总需要IP地址为24+80＝104。这些VDU实例都是连接在通过VLD创建的VL上，该VL包含的IP地址池共有IP100个，很明显此时该VL已经不能满足IP地址分配的需求。
目前标准中定义的VNFD或网络服务描述符或描述模板(Network Service Descriptor,NSD)模型，尤其在针对弹性伸缩(或称为扩缩容)场景时，只考虑了对VDU或VNF数量的增加，对于VL来说，也只是对连接带宽进行调整，没有考虑到其他因素，比如可以分配的IP地址数量等。在设计VNFD或NSD时是在VNF或NS的部署初期，对于VL来说很难直接规划很大的IP地址资源池，因为一是有可能造成浪费(只有在扩容到某个级别时，才用得到)，二是即使规划的很大，也有可能在弹性伸缩中出现IP地址不足的情况。
发明内容
本发明实施例提供一种弹性伸缩的方法及装置，可以避免现有技术VNF或NS在弹性伸缩过程中IP地址分配不足的情形。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供一种弹性伸缩的方法，包括VNFM接收来自NFVO的VNF扩容Scale Out请求，所述请求包括VNF实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；VNFM根据所述VNF Scale请求确定需要创建的VDU以及相应子网Subnet信息；VNFM向VIM请求创建VDU和相应的Subnet。
一种可能的实现方式，上述VNFM根据所述VNF Scale Out请求确定需要创建的VDU以及相应子网Subnet信息包括：VNFM根据所述VNF实例信息找到对应的VNFD，并根据所述指示信息查询所述VNFD，确定需要创建的VDU和相应子网Subnet信息；其中，所述VNFD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
一种可能的实现方式，所述Subnet信息包括以下一项或多项：子网数量、每个子网可供分配的IP地址类型和范围；所述Scale Step参数信息还包括用于指示所述创建的VDU是否连接所述Subnet的参数。
第二方面，本申请实施例提供一种弹性伸缩的方法，包括NFVO接收NS扩容Scale Out请求，所述请求包括NS实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；NFVO根据所述NS Scale请求确定需要创建的VNF以及相应子网Subnet信息；NFVO通过VNFM向VIM请求创建VNF和相应的Subnet。
一种可能的实现方式，上述NFVO根据所述NS Scale Out请求确定需要创建的VNF以及相应子网Subnet信息包括：VNFM根据所述NS实例信息找到对应的NSD，并根据所述指示信息查询所述NSD，确定需要创建的VNF和相应子网Subnet信息；其中，所述NSD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
第三方面，本申请实施例提供一种通信装置，可以实现上述第一方面、或第一方面任一种可能的实现方式中的方法。该装置包括用于执行上述方法的相应的单元或部件。该装置包括的单元可以通过软件和/或硬件方式实现。该装置例如可以为终端、或者为可支持终端实现上述方法的芯片、芯片***、或处理器等。
第四方面，本申请实施例提供一种通信装置，可以实现上述第二方面、或第二方面任一种可能的实现方式中的方法。该装置包括用于执行上述方法的相应的单元或部件。该装置包括的单元可以通过软件和/或硬件方式实现。该装置例如可以为网络设备、或者为可支持网络设备实现上述方法的芯片、芯片***、或处理器等。
第五方面，本申请实施例提供一种计算机可读介质，其上存储有计算机程序或指令，所述计算机程序或指令被执行时使得计算机执行上述第一方面、或第一方面任一种可能的实现方式中所述的方法。
第六方面，本申请实施例提供一种计算机可读介质，其上存储有计算机程序或指令，所述计算机程序或指令被执行时使得计算机执行上述第二方面、或第二方面任一种可能的实现方式中所述的方法。
第七方面，本申请实施例提供一种弹性伸缩***。该***包括包括NFVO,VNFM以及VIM,其分别用于实现上述第一方面或第二方面任一种可能的方法中分别由NFVO,VNFM以及VIM执行的步骤。
可以理解的，上述提供的任一种通信装置、芯片、计算机可读介质、计算机程序产品或通信***等均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果是可以避免现有技术VNF或NS扩容时，出现IP地址分配不足的情况，或者也可以避免现有技术直接定义很大的IP地址资源池，最后造成浪费的情况。
附图说明
图1为现有技术提供的一种VNFD设计实例示意图；
图2为本申请实施例提供的一种NFV网络***的架构示意图；
图3为本申请实施例提供的NFV各网元的通信装置硬件结构示意图；
图4为本申请实施例1提供的弹性伸缩(扩容)的方法的流程示意；
图5为本申请实施例2提供的弹性伸缩(扩容)的方法的流程示意；
图6为本申请实施例3提供的弹性伸缩(缩容)的方法的流程示意；
图7为本申请实施例4提供的一种NSD设计实例示意图；
图8为本申请实施例4提供的弹性伸缩(扩容)的方法的流程示意图；
图9为本申请实施例5提供的弹性伸缩(缩容)的方法的流程示意图；
图10为本申请实施例提供的一种通信装置结构示意图；
图11为本申请实施例提供的一种通信***的组成示意图。
具体实施方式
下面结合附图对本申请实施例的实施方式进行详细描述。
请参考图2，图2为本申请实施例提供的一种NFV***20的架构示意图。NFV***20可以在各种网络中使用，例如在一个数据中心(图2所示的数据中心201或数据中心206)、运营商网络或局域网来实现。NFV***20包括NFV管理和编排***(NFV management and orchestration，NFV MANO)201，NFV基础设施(NFV infrastructure，NFVI)202，多个VNF 203，多个网元管理(element management，EM)204，以及运营支持***和业务支持***(operations support system and business support system，OSS/BSS)205。
其中，NFV MANO 201可以用于执行对NFVI 202和VNF 203的监视和管理。NFV MANO 201可以包括NFV编排器(NFV orchestrator，NFVO)2011，一个或多个VNF管理器(VNF manager，VNFM)2012和VIM 2013。NFVO 2011可以用于管理虚拟化业务的生命周期，以及分配和调度NFVI 202中的虚拟资源等。进一步的，NFVO 2011可以与一个或多个VNFM 2012通信，以执行资源相关请求；NFVO 2011还可以发送配置信息给VNFM 2012，以收集VNF 203的状态信息。另外，NFVO 2011还可以与VIM 2013通信，以执行资源分配，和/或预留，并交换虚拟化硬件资源配置和状态信息。VNFM 2012可以用于管理一个或多个VNF的生命周期，例如，实例化(instantiating)VNF 203，更新(updating)VNF 203，查询VNF 203，弹性伸缩(scaling)VNF 203，终止(terminating)VNF 203等。进一步的，VNFM 2012可以与VNF 203通信以完成VNF生命周期管理及交换配置和状态信息。在NFV***中，VNFM可以有多个。不 同的VNFM可以管理不同类型的VNF的生命周期。VIM 2013可以控制和管理VNF 203与计算硬件2024，存储硬件2025，网络硬件2026，虚拟计算(virtual computing)2021，虚拟存储2022，虚拟网络2023的交互。例如VIM 2013可以执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM 2012及VIM 2013可以相互通信，以请求资源分配，交换虚拟化硬件资源配置和状态信息等。
图2中的NFVI 202包括硬件资源层、虚拟化层(virtualization layer)和虚拟资源层。NFVI 202包括的硬件资源、软件资源或两者的组合来完成虚拟化环境的部署。换句话说，硬件资源和虚拟化层用于提供虚拟化的资源，例如作为虚拟机和其它形式的虚拟容器，用于VNF 203。硬件资源层包括计算(computing)硬件2024、存储硬件2025和网络硬件2026。计算硬件2024可以是市场上现成的硬件和/或用户定制的硬件，用来提供处理和计算资源。存储硬件2025可以是网络内提供的存储容量或驻留在存储硬件2025本身的存储容量(位于服务器内的本地存储器)。在一个实现方案中，计算硬件2024和存储硬件2025的资源可以被集中在一起。网络硬件2026可以是交换机、路由器和/或配置成具有交换功能的任何其他网络设备。网络硬件2026可以横跨多个域，并且可以包括多个由一个或一个以上传输网络互连的网络。NFVI 202中的虚拟化层可以从物理层抽象硬件资源和解耦VNF 203，以便向VNF 203提供虚拟化资源。虚拟资源层包括虚拟计算2021、虚拟存储2022和虚拟网络2023。虚拟计算2021和虚拟存储2022可以以虚拟机、和/或其他虚拟容器的形式提供给VNF 203。例如，一个或一个以上的VNF 203可以部署在一个虚拟机(virtual machine，VM)上。虚拟化层抽象网络硬件2026，从而形成虚拟网络2023，虚拟网络2023可以包括虚拟交换机(virtual switch)，虚拟交换机用来提供虚拟机和其他虚拟机之间的连接。
硬件上，计算硬件2024、存储硬件2025和网络硬件2026可能包含多个机框，或多个机架，甚至多个机房。软件上，可能存在一个VIM 2013，也可能存在多个VIM，分别管理不同的硬件资源。
EM 204是传统电信***中用于对网元进行配置，管理的***。在NFV***中，EM 204也可以用于对VNF进行配置和管理，以及向VNFM发起新的VNF的实例化等生命周期管理操作。
OSS/BSS 205支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS可以用于处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
图2所示的NFV***20仅用于举例，并非用于限制本申请的技术方案。本领域的技术人员应当明白，在具体实现过程中，NFV***20还可以包括其他网元，同时也可根据具体需要来确定各个网元的数量，不予限制。
可选的，本申请实施例图2中的各网元，例如NFVO 2011、VIM 2013或OSS/BSS205等，可以是一个装置内的一个功能模块。可以理解的是，该功能模块既可以是硬件设备中的元件，也可以是在硬件上运行的软件功能模块，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，图2中的各网元均可以通过图3中的通信装置30来实现。图3所示为可适 用于本申请实施例的通信装置的硬件结构示意图。该通信装置30包括至少一个处理器301和至少一个通信接口304，用于实现本申请实施例提供的方法。该通信装置30还可以包括通信线路302和存储器303。
处理器301可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路302可包括一通路，在上述组件之间传送信息，例如总线。
通信接口304，用于与其他设备或通信网络通信。通信接口304可以是任何收发器一类的装置，如可以是以太网接口、无线接入网(radio access network，RAN)接口、无线局域网(wireless local area networks，WLAN)接口、收发器、管脚、总线、或收发电路等。
存储器303可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路302与处理器301相耦合。存储器303也可以和处理器301集成在一起。本申请实施例提供的存储器通常可以具有非易失性。其中，存储器303用于存储执行本申请实施例提供的方案所涉及的计算机执行指令，并由处理器301来控制执行。处理器301用于执行存储器303中存储的计算机执行指令，从而实现本申请实施例提供的方法。
本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
作为一种实施例，通信装置30可以包括多个处理器，例如图3中的处理器301和处理器305。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
上述的通信装置30可以是一个通用设备或者是一个专用设备。在具体实现中，通信装置30可以是台式机、网络服务器或有图3中类似结构的设备。本申请实施例不限定通信装置30的类型。
下面结合图4到图9对本申请实施例提供的一种弹性伸缩的方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体 限定。
需要说明的是，在本申请实施例中，“/”可以表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。
为了便于描述本申请实施例的技术方案，在本申请实施例中，可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请实施例中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
需要说明的是，在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
可以理解的，本申请实施例中同一个步骤或者具有相同功能的步骤或者技术特征在不同实施例之间可以互相参考借鉴。
可以理解的，本申请实施例中，NFVO，和/或VIM，和/或VNFM可以执行本申请实施例中的部分或全部步骤，这些步骤仅是示例，本申请实施例还可以执行其它步骤或者各种步骤的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部步骤。
在本申请实施例中，建立网络连接的方法的执行主体的具体结构，本申请实施例并未特别限定，只要能够实现本申请实施例的提供的方法即可。例如，本申请实施例提供的建立网络连接的方法的执行主体可以是NFVO，或者为应用于NFVO中的部件，例如，芯片，本申请对此不进行限定。或者，本申请实施例提供的建立网络连接的方法的执行主体可以是VIM，或者为应用于VIM中的部件，例如，芯片，本申请对此不进行限定。或者，本申请实施例提供的建立网络连接的方法的执行主体可以是VNFM，或者为应用于VNFM中的部件，例如，芯片，本申请对此不进行限定。下述实施例以建立网络连接的方法的执行主体分别为NFVO、VIM、VNFM为例进行描述。
参考图4，图4是本发明实施例1的流程图。实施例1和实施例2描述的均是VNF弹性伸缩(或称为“扩缩容”)中的扩容(Scale Out)流程。其主要区别在于新创建的VDU是否必须跟新创建的Subnet进行连接或关联。实施例1是必须进行连接或关联，实施例2是不一定进行连接或关联。
下面对实施例1的具体实施步骤进行描述：
401.NFVO向VNFM发送针对VNF的弹性伸缩请求(简称“VNF弹性伸缩请求”), 在本实施例中具体是扩容(Scale Out)请求，所述请求包括VNF实例信息(如VNF实例ID)，以及用于指示Scale的维度或范围(Aspect)和等级(Step)的指示信息。
上述专业术语或名称(如Aspect，Step等)的具体含义可以参考现有NFV标准(如IFA011 v4.1.1)的相关描述。上述用于指示Scale的维度(Aspect)的指示信息主要包括AspectId，该ID会对应VNFD里定义的某个Scale Aspect，所述VNFD里的Scale Aspect包含具体的VDU和VL名称、数量和/或特性等相关信息。用于指示Step的指示信息主要包括在所述Aspect内弹性伸缩的级别，如Step 1或Step 2等。
402.VNFM收到上述VNF Scale请求，根据请求中的VNF实例信息找到对应的VNFD，并根据所述指示信息查询所述VNFD，确定需要创建的VDU和相应子网Subnet信息。
现有技术VNFD定义的Aspect包含弹性伸缩的细节参数ScalingDelta，如下表所示：
Figure PCTCN2020141795-appb-000001
其中主要包含参数vduDelta和virtualLinkBitRateDelta，参数vduDelta描述VDU弹性细节参数,主要是相关VDU实例的数量；参数virtualLinkBitRateDelta描述virtual link弹性细节参数，主要是相关virtual link的比特率。
本发明实施例对现有的VNFD包含的ScalingDelta中的virtualLinkBitRateDeltaAspect参数作如下变更和扩展:
Figure PCTCN2020141795-appb-000002
可以将现有的VNFD中的virtualLinkBitRateDelta的名称修改为virtualLinkDelta (也可以不修改名称)，其具体参数包括：
Figure PCTCN2020141795-appb-000003
其中上述NumberofSubnet，SubnetInfo以及DedicatedOrNot为本发明实施例的新增参数。
根据上述扩展，在VNFD中定义不同的Step。例如，可以定义如下2个级别Step：
Step 1，VDU_1共3个实例，VDU_2共4个实例，VL比特率4Gbps；
Step 2，VDU_1共6个实例，VDU_2共8个实例，VL比特率8Gbps。
且在上述Step 2中包含或关联上述新增参数NumberofSubnet：N，(N为大于或等于1的整数)，SubnetInfo(包括内容L3ProtocolData)以及DedicatedOrNot：true/false。其中DedicatedOrNot：true/false为可选(Optional)。如果N为1，表明需新创建1个Subnet，上述L3ProtocolData的参数定义了创建所述1个Subnet所需要的信息，包括IP地址类型和范围，如下所示：
l3_protocol_data:
ip_version:ipv4
ip_allocation_pools:
-start_ip_address:192.168.10.1
-end_ip_address:192.168.10.100
如果N为多个，则参数SubnetInfo的数量也为N；由于参数NumberofSubnet为可选，所以如果没有所述NumberofSubnet参数，则有多少个SubnetInfo参数则添加多少个Subnet，每个SubnetInfo对应添加一个Subnet。
DedicatedOrNot：true/false表明新创建的Subnet是否必须和上述新创建的
VDU进行连接或关联。True表明新创建的Subnet必须和上述新创建的VDU进行连接或关联，false说明新创建的VDU实例不一定需要关联新的Subnet实例，可以先关联VL中已有的Subnet实例，如没有合适的，则关联新的Subnet信息。在此实施例1中DedicatedOrNot的值为true。
VNFM收到上述VNF Scale请求后，首先根据请求中的VNF实例信息，如VNF实例ID，找到对应的VNFD，该VNFD即是上述扩展后的VNFD。然后根据所述指示信息查询所述VNFD，具体通过指示信息包括的Aspect ID在VNFD中查找和确定弹性伸缩的维度或范围，然后根据指示信息中的Step信息查找VNFD并确定需要Scale的级别和相关内容。例如，如果上述VNF Scale请求中的Aspect ID为ID XXX，VNFM通过查找VNFD，确定该ID XXX在VNFD中对应的Aspect包括VDU_1，VDU_2和VL；另外，如果上述VNF Scale请求中的Step指示信息是2级，则VNFM通过查找VNFD，确定上述示例中的级别2需要创建6个VDU_1实例，8个VDU_2实例，VL比特率是8Gbps，且需要新创建1个Subnet，其具体实例化参数包含在L3ProtocolData中，且新创建的VDU必须关联上述Subnet。新创建的VDU数量为所述对应级别中的VDU数量减去Scale前的VNF中包括的VDU数量。那么在这个例子中，级别2中需要创建共6个VDU_1实例，8个VDU_2实例，则新创建的VDU_1，VDU_2数量分别为6个VDU_1实例减去Scale前VNF的VDU_1实例数量(例如3个)，8个VDU_2减去现有VNF的VDU_2实例数量(例如6个)，则新创建的VDU_1，VDU_2数量分别为3个和2个。对于创建的Subnet数量，其确定方式不同于上述VDU的创建，NumberofSubnet：1就表明需新创建1个子网，不考虑现有VNF中的虚拟链路VL中已有的Subnet数量。
403.VNFM向NFVO发送资源授权Resource Grant请求，即请求授权创建资源，包括上述步骤402确定的需要新创建的VDU实例资源和Subnet资源。其中针对Subnet资源，请求中包含有：
AddResource：
Type:Subnet
ResourceTemplateId:VLD(VNFD中VLD的标识)
L3ProtocolData
404.NFVO向VNFM返回授权允许消息，携带VIM接入信息等。
405.VNFM根据步骤402中确定的Subnet的信息，向VIM申请创建新的Subnet实例，所述Subnet包含新的IP地址范围或资源池信息。例如，可以为：
-start_ip_address:192.168.10.1
-end_ip_address:192.168.10.100
406.VIM创建Subnet完成后，向VNFM返回Subnet实例创建完成通知消息及实例信息。
407.收到Subnet创建完成通知消息后，VNFM向NFVO发起创建Linkport的授权请求。所述请求携带如下信息：
AddResource：
Type:Linkport
Subnet实例信息
其指示需要创建的Linkport同新建的Subnet实例关联。
408.NFVO向VNFM发送授权允许消息。
409.VNFM向VIM发起Linkport的创建，其中携带需要关联的Subnet实例信息。
410.VNFM向VIM申请创建新的VDU实例，携带上述步骤402确定的VDU的类型和数量，并携带新创建的Linkport信息。
411.VIM创建完VDU实例后，通过Linkport关联在新创建的Subnet上，并由新创建的Subnet为其分配IP地址。
由于本发明实施例中在新定义的VNFD中增加了NumberofSubnet，SubnetInfo等参数，在扩容的时候可以根据扩容大小(对应不同的Step)分配相应数量的IP地址，动态满足新创建的VDU的地址需求，可以避免现有技术VNF扩容时，出现IP地址分配不足的情况；也可以避免现有技术直接定义很大的IP地址资源池，最后造成浪费的情况。
参考图5，图5是实施例2的流程图。实施例2其跟实施例1的区别在于新创建的VDU不一定跟新创建的Subnet进行连接或关联。
下面对实施例2的具体实施步骤进行描述：
501.同实施例1步骤401.
502.跟实施例1步骤402不同之处在于VNFD中定义的Step 2，其包括的DedicatedOrNot的值为false，说明新增加的VDU实例不一定必须关联新创建的Subnet实例
503～506.同实施例1步骤403～406。
507.由于VNFD中Step 2中的DedicatedOrNot的值为false，所以新的VDU实例不是必须关联新的Subnet实例，所以VNFM向NFVO发起Linkport的授权请求只携带Linkport的信息，不携带Subnet信息，例如可以如下所示：
AddResource：
Type:Linkport
508.同实施例1步骤508.
509.VNFM向VIM申请创建Linkport，如果VNFM判断原来VL网络中的Subnet里还可以分配IP地址，则新创建的Linkport关联已有的Subnet信息，否则关联新的Subnet信息。
510.同实施例1步骤410.
511.VIM创建完VDU实例后，通过Linkport关联在已有的Subnet上(原来VL网络中的Subnet里还可以分配IP地址)，由已有的Subnet为其分配IP地址，或关联在新创建的Subnet上，由新创建的Subnet为其分配IP地址。
参考图6，图6是本发明实施例3的流程图，实施例3是上述实施例1或2的后续步骤，描述的是VNF缩容(Scale In)的流程。
下面对实施例3的具体实施步骤进行描述：
601.NFVO向VNFM发送针对VNF的弹性伸缩请求，在该实施例中具体是缩容(Scale In)请求,所述请求包括VNF实例信息(如VNF实例ID)，以及用于指示Scale的范围(Aspect)和等级(Step)的指示信息。
例如，如果当前VNF的Step为2，且所述指示信息中的Step指示为1，则VNF从第2级缩容到第1级。
602.VNFM收到上述VNF Scale请求，根据请求中的VNF实例信息找到对应的VNFD，并根据所述指示信息查询所述VNFD，确定需要删除的VDU和相应子网Subnet信息。在本实施例中还是采用跟实施例1相同的VNFD，其仍然包含如下2个级别：
Step 1，VDU_1共3个实例，VDU_2共4个实例，VL比特率4Gbps；
Step 2，VDU_1共6个实例，VDU_2共8个实例，VL比特率8Gbps，NumberofSubnet：1，L3ProtocolData，DedicatedOrNot：true
那么从第2级缩容到第1级，VDU_1需要减少3个实例，VDU_2需要减少4个实例，VL需要删除一个Subnet(即类似实施例1中新创建的Subnet)。
603.VNFM向NFVO发送授权(Grant)请求，在Grant请求中的RemoveResource参数里包含需要删除的Subnet资源，Compute资源(对应VDU)，Linkport资源的描述信息。
604.VNFM接收NFVO的授权允许消息。
605.VNFM向VIM申请删除对应的Subnet资源，VUD对应的虚拟机资源以及Linkport资源等。
606.VIM向VNFM发送资源删除成功消息。
607.VNFM向NFVO发送Scale In完成消息。
本发明实施例还可以扩展到网络服务(Network Service，NS)的扩缩容场景。参考图7，图7是一个NS描述文件(NS Descriptor，NSD)的设计实例示意图，其主要包括描述VNF的VNFD,如描述图中VNF_1和VNF_2的相应VNFD 1和VNFD 2，描述虚拟链路VL的NsVld，以及描述VNF的外部连接点(External Connection Point，ExtCp)的描述符(Descriptor),图中的VnfExtCP_1和VnfExtCP_2为VNF_1和VNF_2的外部连接点。
上面实施例1到3描述的是针对VNF进行扩缩容的场景，在对NS进行扩容的时候，对应连接VNF_1和VNF_2的NsVld也会出现IP地址不足的问题。本发明下面实施例4和5的NS弹性伸缩流程也可以解决上述问题。
图8是本发明实施例4的NS弹性伸缩(Scale)的流程图，具体是Scale Out流程图。实施例4的具体步骤如下：
801.NFVO收到来自OSS/BSS的针对NS的弹性伸缩请求(简称“NS弹性伸缩请求”)，在本实施例中具体是扩容(Scale Out)请求，所述请求包括NS实例信息(如NS实例ID)，以及用于指示Scale的范围(Aspect)和等级(Step)的指示信息。
802.NVFO收到上述Scale Out请求，根据请求中的NS实例信息找到对应的NSD，并根据所述指示信息查询所述NSD，确定需要创建的VNF和相应子网Subnet信息。
针对NSD的内容，本实施例主要扩展NsLevel中的virtualLinkToLevelMapping信息(类似于VNFD的ScalingDelta中的virtualLinkBitRateDelta)。
扩展后virtualLinkToLevelMapping包含的信息如下：
Figure PCTCN2020141795-appb-000004
根据新的扩展，NsLevel可以定义的2个级别Step为(以下具体数字为举例)：
Step1，VNF_1共3个实例，VNF_2共4个实例，VL比特率4Gbps；
Step2，VNF_1共6个实例，VNF_2共8个实例，VL比特率8Gbps。
且在上述Step 2中包含或关联新增参数NumberofSubnet：N，(N为大于或等于1的整数)，SubnetInfo(包括内容L3ProtocolData)以及DedicatedOrNot：true/false。其中DedicatedOrNot：true/false为可选(Optional)。
上述新增参数的含义跟实例1和2相同，这里不再赘述。在此实施例中，DedicatedOrNot的值为true。
NFVO收到上述Scale Out请求后，首先根据请求中的NS实例信息，如NS实例ID，找到对应的NSD，该NSD即是上述扩展后的NSD。然后根据所述指示信息查询所述NSD，具体通过指示信息中的Aspect在NSD中查找和确定弹性伸缩(Scale)的对象或范围，然后根据指示信息中的Step查找NSD并确定需要Scale的级别。例如，如果上述VNF Scale请求中的Aspect包括VNF_1,VNF_2和VL，且Step是2级，则VNFM通过查找NSD，确定上述示例中的级别2，需要创建6个VNF_1实例，8个VNF_2实例且VL比特率8Gbps，且需要新创建1个Subnet，其具体实例化参数包含在L3ProtocolData中，且新创建的VNF必 须关联上述Subnet。新创建的VNF数量为所述对应级别中的VNF数量减去Scale前的VNF中包括的VNF数量。那么在这个例子中，级别2中需要创建共6个VNF_1实例，8个VNF_2实例，则新创建的VNF_1，VNF_2数量分别为6个VNF_1实例减去Scale前VNF的VNF_1实例数量(例如2个)，8个VNF_2减去现有VNF的VNF_2实例数量(例如5个)，则新创建的VNF_1，VNF_2数量分别为4个，3个。对于创建的Subnet数量，其确定方式不同于上述VNF的创建，NumberofSubnet：1就表明需新创建1个子网，不考虑现有VNF中的虚拟链路VL中已有的Subnet数量。
803.NFVO根据VL的信息(第2级别信息)，确定需要在原VL实例上创建一个新的Subnet，则向VIM申请创建所述Subnet。
804.NFVO根据需要新创建的VNF实例，向VNFM发送实例化VNF请求，并携带VNF(通过VnfExtCp_1)需要连接的VL实例信息，由于NSD中Nslevel定义的第2级里DedicatedOrNot的值为true，在VL实例信息中还包含803步骤中新创建的Subnet实例信息。
805.可选地，如果804步中，不包含新VNF实例连接Subnet的Linkport信息，则VNFM向NFVO发送Grant请求，授权创建新的Linkport，并在addResource里增加同Subnet实例的关联信息。
806.NFVO向VNFM发送授权允许消息。
807.VNFM向VIM申请创建Linkport，其中包含新的Subnet信息。
808.VNFM针对需要新创建的VNF实例，向VIM申请创建新的VNF实例，并通过VnfExtCp_1以及新建的Linkport连接到所述Subnet。
809.VIM通过创建VDU完成VNF实例创建，通过Linkport关联到新创建的Subnet上。
本发明实施例5是NS弹性伸缩中的缩容(Scale In)流程，跟VNF的Scale In流程类似，如图9所示，具体步骤如下：
901.NFVO收到来自OSS/BSS的针对NS的弹性伸缩(Scale)请求，在本实施例中具体是缩容(Scale In)请求，所述请求包括NS实例信息(如NS实例ID)，以及用于指示Scale的范围(Aspect)和等级(Step)的指示信息。
例如，如果当前VNF的Step为2，且所述指示信息中的Step指示为1，则NS从第2级缩容到第1级。
902.NFVO收到上述NS Scale In请求后，根据请求中的NS实例ID信息找到对应的NSD，并根据所述指示信息查询所述NSD，确定需要删除的VNF和相应子网Subnet信息。在本实施例中还是采用跟实施例4相同的NSD，其NsLevel可以定义的2个级别Step为(以下具体数字为举例)：
Step1，VNF_1共3个实例，VNF_2共4个实例，VL比特率4Gbps；
Step2，VNF_1共6个实例，VNF_2共8个实例，VL比特率8Gbps。
且在上述Step 2中新增参数NumberofSubnet：1，SubnetInfo(包括内容L3ProtocolData)以及DedicatedOrNot：true/false。其中DedicatedOrNot：true/false为可选(Optional)。
那么从第2级缩容到第1级，VNF_1需要减少3个实例，VNF_2需要减少4个实例，VL需要删除一个Subnet。
903.NVFO向VIM申请删除对应的Subnet资源，VNF中包括的不同VDU对应的虚拟机资源以及Linkport资源等。
904.VIM删除资源完成，并向NFVO发送资源删除成功消息。
其中，上述各个实施例方法步骤中的NFVO、VNFM或者VIM的动作可以由图4所示的通信装置40中的处理器401调用存储器403中存储的应用程序代码来执行，本实施例对此不作任何限制。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述NFVO、VNFM或者VIM等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法操作，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对NFVO、VNFM或者VIM等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图10示出了一种通信装置100的结构示意图。通信装置100包括收发模块1001和处理模块1002。
示例性地，通信装置100用于实现VNFM的功能。通信装置100例如为图4所示的实施例，图5所示的实施例或图6所示的实施例所述的VNFM。
在本申请实施例中，通信装置100可以是VNFM，也可以是应用于VNFM中的芯片或者其他具有上述VNFM功能的组合器件、或部件等。当通信装置100是VNFM 时，收发模块1001可以是收发器，收发器可以包括天线和射频电路等，处理模块1002可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个CPU。当通信装置100是具有上述VNFM功能的部件时，收发模块1001可以是射频单元，处理模块1002可以是处理器(或者，处理电路)，例如基带处理器。当通信装置100是芯片***时，收发模块1001可以是芯片(例如基带芯片)的输入输出接口，处理模块1002可以是芯片***的处理器(或者，处理电路)，可以包括一个或多个中央处理单元。应理解，本申请实施例中的收发模块1001可以由收发器或收发器相关电路组件实现，处理模块1002可以由处理器或处理器相关电路组件(或者，称为处理电路)实现。
例如，收发模块1001可以用于执行图4所示的实施例中由VNFM所执行的全部收发操作，例如S401和S403，和/或用于支持本文所描述的技术的其它过程。处理模块1002可以用于执行图4所示的实施例中由VNFM所执行的除了收发操作之外的全部操作，例如S402，和/或用于支持本文所描述的技术的其它过程。
又例如，收发模块1001可以用于执行图6所示的实施例中由VNFM所执行的全部收发操作，例如S601和S603，和/或用于支持本文所描述的技术的其它过程。处理模块1002可以用于执行图6所示的实施例中由VNFM所执行的除了收发操作之外的全部操作，例如S602，和/或用于支持本文所描述的技术的其它过程。
当用于实现VNFM的功能时，关于通信装置100所能实现的其他功能，可参考图4到图6，图8和图9所示的实施例的相关介绍，不多赘述。
同样示例性地，通信装置100可用于实现NFVO的功能。通信装置100例如为图8所示的实施例或图9所示的实施例所述的NFVO，也可以为图4到图6所示的实施例的NFVO，不多赘述。
在本申请实施例中，通信装置100可以是VIM，也可以是应用于VIM中的芯片或者其他具有上述VIM功能的组合器件、或部件等。当通信装置100是VIM时，收发模块1001可以是收发器，收发器可以包括天线和射频电路等，处理模块1002可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个CPU。当通信装置100是具有上述VIM功能的部件时，收发模块1001可以是射频单元，处理模块1002可以是处理器(或者，处理电路)，例如基带处理器。当通信装置100是芯片***时，收发模块1001可以是芯片(例如基带芯片)的输入输出接口，处理模块1002可以是芯片***的处理器(或者，处理电路)，可以包括一个或多个中央处理单元。应理解，本申请实施例中的收发模块1001可以由收发器或收发器相关电路组件实现，处理模块1002可以由处理器或处理器相关电路组件(或者，称为处理电路)实现。
例如，收发模块1001可以用于执行图4到图6，图8到图9所示的实施例中由VIM所执行的全部收发操作，处理模块1002可以用于执行图4到图6，图8到图9所示的实施例中由VIM所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。
图11示出了的一种通信***的组成示意图，如图11所示，该通信***110中可以包括：NFVO 1101,VNFM 1102和VIM 1103。需要说明的是，图11仅为示例性附 图，本申请实施例不限定图11所示通信***110包括的网元以及网元的个数。
其中，VNFM 1102用于实现上述各个实施例中VNFM的功能。例如，VNFM 1102可以用于接收来自NFVO 1101的弹性伸缩请求信息，根据请求信息查询查询VNFD，确定需要创建的VDU和相应子网Subnet信息，并向VIM 1103申请创建VDU和相应子网Subnet。
NFVO 1101用于实现上述各个方法实施例中NFVO的功能，VIM 1103用于实现上述各个方法实施例中VIM的功能，不再赘述。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到该通信***110对应网元的功能描述，在此不再赘述。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种虚拟化网络功能VNF弹性伸缩Scale的方法，其特征在于，所述方法包括：
    VNFM接收来自NFVO的VNF扩容Scale Out请求，所述请求包括VNF实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；
    VNFM根据所述VNF Scale请求确定需要创建的VDU以及相应子网Subnet信息；
    VNFM向VIM请求创建VDU和相应的Subnet。
  2. 根据权利要求1所述的方法，其特征在于，VNFM根据所述VNF Scale Out请求确定需要创建的VDU以及相应子网Subnet信息包括：
    VNFM根据所述VNF实例信息找到对应的VNFD，并根据所述指示信息查询所述VNFD，确定需要创建的VDU和相应子网Subnet信息；
    其中，所述VNFD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述Subnet信息包括以下一项或多项：子网数量、每个子网可供分配的IP地址类型和范围。
  4. 根据权利要求2所述的方法，其特征在于，所述Scale Step参数信息还包括用于指示所述创建的VDU是否连接所述Subnet的参数。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括VNFM向VIM请求创建链接端口Linkport，所述VDU通过Linkport连接所述Subnet。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    VNFM接收来自NFVO的VNF缩容Scale In请求，所述请求包括VNF实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；
    VNFM根据所述VNF Scale In请求确定需要删除的VDU以及相应子网Subnet信息；
    VNFM向VIM请求删除VDU和相应的Subnet。
  7. 根据权利要求6所述的方法，其特征在于，VNFM根据所述VNF Scale In请求确定需要删除的VDU以及相应子网Subnet信息包括：
    VNFM根据所述VNF实例信息找到对应的VNFD，并根据所述指示信息查询所述VNFD，确定需要删除的VDU和相应子网Subnet信息；
    其中，所述VNFD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
  8. 根据权利要求1或2所述的方法，其特征在于，所述Subnet信息包括以下一项或多项：子网数量、每个子网可供分配的IP地址类型和范围。
  9. 一种网络服务NS弹性伸缩Scale的方法，其特征在于，所述方法包括：
    NFVO接收NS扩容Scale Out请求，所述请求包括NS实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；
    NFVO根据所述NS Scale请求确定需要创建的VNF以及相应子网Subnet信息；
    NFVO通过VNFM向VIM请求创建VNF和相应的Subnet。
  10. 根据权利要求9所述的方法，其特征在于，NFVO根据所述NS Scale Out请 求确定需要创建的VNF以及相应子网Subnet信息包括：
    VNFM根据所述NS实例信息找到对应的NSD，并根据所述指示信息查询所述NSD，确定需要创建的VNF和相应子网Subnet信息；
    其中，所述NSD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述Subnet信息包括以下一项或多项：子网数量、每个子网可供分配的IP地址类型和范围。
  12. 根据权利要求10所述的方法，其特征在于，所述Scale Step参数信息还包括用于指示所述创建的VNF是否连接所述Subnet的参数。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括VNFM向VIM请求创建链接端口Linkport，所述VNF通过Linkport连接所述Subnet。
  14. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    NFVO接收NS扩容Scale In请求，所述请求包括NS实例信息以及用于指示Scale的维度Aspect和等级Step的指示信息；
    NFVO根据所述NS Scale请求确定需要删除的VNF以及相应子网Subnet信息；
    NFVO通过VNFM向VIM请求删除VNF和相应的Subnet。
  15. 根据权利要求9所述的方法，其特征在于，NFVO根据所述NS Scale In请求确定需要删除的VNF以及相应子网Subnet信息包括：
    VNFM根据所述NS实例信息找到对应的NSD，并根据所述指示信息查询所述NSD，确定需要删除的VNF和相应子网Subnet信息；
    其中，所述NSD包括Scale Aspect和Step参数信息，所述Scale Step参数信息包括Subnet信息。
  16. 根据权利要求10所述的方法，其特征在于，所述Subnet信息包括以下一项或多项：子网数量、每个子网可供分配的IP地址类型和范围。
  17. 一种弹性伸缩Scale装置，其特征在于，包括用于执行如权利要求1至8中任一项所述方法的模块。
  18. 一种弹性伸缩Scale装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器中存储有计算机程序；所述处理器用于调用所述存储器中的计算机程序，使得所述装置执行如权利要求1至8任一所述的方法。
  19. 一种弹性伸缩Scale装置，其特征在于，包括用于执行如权利要求9至16中任一项所述方法的模块。
  20. 一种弹性伸缩Scale装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器中存储有计算机程序；所述处理器用于调用所述存储器中的计算机程序，使得所述装置执行如权利要求9至16任一所述的方法。
  21. 一种弹性伸缩Scale***，包括NFVO,VNFM以及VIM,其分别用于实现权利要求1至9或9至16中任一项所述的方法中分别由NFVO,VNFM以及VIM执行的步骤。
  22. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序，当所述计算机程序被执行时，实现如权利要求1至9或9至16中任一项所述的方法。
PCT/CN2020/141795 2020-12-30 2020-12-30 一种弹性伸缩的方法及装置 WO2022141293A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202080108288.8A CN116686264A (zh) 2020-12-30 2020-12-30 一种弹性伸缩的方法及装置
JP2023539985A JP2024502038A (ja) 2020-12-30 2020-12-30 スケーリング方法および装置
PCT/CN2020/141795 WO2022141293A1 (zh) 2020-12-30 2020-12-30 一种弹性伸缩的方法及装置
EP20967632.9A EP4262154A4 (en) 2020-12-30 2020-12-30 METHOD AND DEVICE FOR ELASTIC SCALING
US18/345,468 US20230362065A1 (en) 2020-12-30 2023-06-30 Scaling Method and Apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/141795 WO2022141293A1 (zh) 2020-12-30 2020-12-30 一种弹性伸缩的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/345,468 Continuation US20230362065A1 (en) 2020-12-30 2023-06-30 Scaling Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2022141293A1 true WO2022141293A1 (zh) 2022-07-07

Family

ID=82260070

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141795 WO2022141293A1 (zh) 2020-12-30 2020-12-30 一种弹性伸缩的方法及装置

Country Status (5)

Country Link
US (1) US20230362065A1 (zh)
EP (1) EP4262154A4 (zh)
JP (1) JP2024502038A (zh)
CN (1) CN116686264A (zh)
WO (1) WO2022141293A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107251486A (zh) * 2015-09-30 2017-10-13 华为技术有限公司 一种扩展联动的方法、装置及***
WO2018149514A1 (en) * 2017-02-16 2018-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for virtual function self-organisation
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN109314649A (zh) * 2016-06-23 2019-02-05 英特尔Ip公司 用于nfv生命周期管理的设备和方法
US20190052549A1 (en) * 2016-05-06 2019-02-14 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels
CN110661709A (zh) * 2018-06-29 2020-01-07 英特尔公司 用于负载感知的业务引导的技术

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10942786B2 (en) * 2015-03-13 2021-03-09 Comptel Corporation Network management
EP3466014B1 (en) * 2016-05-27 2020-07-08 Telefonaktiebolaget LM Ericsson (PUBL) Method and arrangement for configuring a secure domain in a network functions virtualization infrastructure
US20180270073A1 (en) * 2017-03-17 2018-09-20 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network
US10594621B2 (en) * 2017-07-10 2020-03-17 Hewlett Packard Enterprise Development Lp Managing virtualized network service bundles
WO2020037689A1 (en) * 2018-08-24 2020-02-27 Nokia Shanghai Bell Co., Ltd. Apparatus and method for handling managed object priorities in 5g network
US10637753B1 (en) * 2019-04-09 2020-04-28 Verizon Patent And Licensing Inc. Managing a 5G network using extension information

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107251486A (zh) * 2015-09-30 2017-10-13 华为技术有限公司 一种扩展联动的方法、装置及***
US20190052549A1 (en) * 2016-05-06 2019-02-14 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels
CN109314649A (zh) * 2016-06-23 2019-02-05 英特尔Ip公司 用于nfv生命周期管理的设备和方法
WO2018149514A1 (en) * 2017-02-16 2018-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for virtual function self-organisation
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
CN110661709A (zh) * 2018-06-29 2020-01-07 英特尔公司 用于负载感知的业务引导的技术

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Network Functions Virtualisation (NFV) Release 3; Management and Orchestration; Network Service Templates Specification", ETSI GROUP SPECIFICATION, 1 June 2020 (2020-06-01), pages 1 - 47, XP055950347, Retrieved from the Internet <URL:https://docbox.etsi.org/isg/nfv/open/Publications_pdf/Specs-Reports/NFV-IFA%20014v3.4.1%20-%20GS%20-%20Network%20Service%20Templates%20Spec.pdf> [retrieved on 20220810] *
ANONYMOUS: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data Models; RESTful protocols specification for the Or-Vnfm Reference Point", ETSI DRAFT; ETSI GS NFV-SOL 003 V3.3.1, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), SOPHIA-ANTIPOLIS ; FRANCE, 28 August 2020 (2020-08-28), pages 1 - 369, XP014385193 *
See also references of EP4262154A4 *

Also Published As

Publication number Publication date
US20230362065A1 (en) 2023-11-09
CN116686264A (zh) 2023-09-01
EP4262154A1 (en) 2023-10-18
EP4262154A4 (en) 2024-01-24
JP2024502038A (ja) 2024-01-17

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
EP3471345B1 (en) Sla-based resource allocation method and nfvo
WO2019184967A1 (zh) 一种网络切片的部署方法及装置
AU2015419073B2 (en) Life cycle management method and device for network service
US20190281503A1 (en) Management Method, Management Unit, and System
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
CN112583615B (zh) Vnf实例化方法、nfvo、vim、vnfm及***
EP3629160B1 (en) Method and device for managing vnf instantiation
US20230342183A1 (en) Management method and apparatus for container cluster
US20220350637A1 (en) Virtual machine deployment method and related apparatus
CN116113923A (zh) 容器集群管理方法及其***
WO2022141293A1 (zh) 一种弹性伸缩的方法及装置
CN112889247B (zh) Vnf服务实例化方法及装置
WO2022126389A1 (zh) 建立网络连接的方法及装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置
WO2019011180A1 (zh) 一种License的发送方法和装置
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv***
WO2022089291A1 (zh) 一种数据流镜像方法及装置
CN118118348A (zh) 一种虚拟化网络功能vnf的实例化方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202080108288.8

Country of ref document: CN

Ref document number: 2023539985

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2020967632

Country of ref document: EP

Effective date: 20230710

NENP Non-entry into the national phase

Ref country code: DE