WO2019011180A1 - 一种License的发送方法和装置 - Google Patents

一种License的发送方法和装置 Download PDF

Info

Publication number
WO2019011180A1
WO2019011180A1 PCT/CN2018/094699 CN2018094699W WO2019011180A1 WO 2019011180 A1 WO2019011180 A1 WO 2019011180A1 CN 2018094699 W CN2018094699 W CN 2018094699W WO 2019011180 A1 WO2019011180 A1 WO 2019011180A1
Authority
WO
WIPO (PCT)
Prior art keywords
license
vnf instance
vnf
instance
resource pool
Prior art date
Application number
PCT/CN2018/094699
Other languages
English (en)
French (fr)
Inventor
冯爱娟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019011180A1 publication Critical patent/WO2019011180A1/zh

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
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/121—Restricting unauthorised execution of programs
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements

Definitions

  • the present application relates to the field of virtualization technologies, and in particular, to a method and an apparatus for transmitting a license.
  • NFV ISG Industry Specification Group
  • ETSI European Telecommunications Standards Institute
  • NFV ISG Industry Specification Group
  • network equipment can be based on common hardware, such as standards-based large-capacity service areas, storage and Ethernet, applications from different vendors in software, remote automatic Deploy on a unified cloud virtualization infrastructure to reduce costs, increase efficiency, and increase agility.
  • NFV Network Functions Virtualization
  • the NFV instance softwareizes the network element so that the network element can run on various general-purpose hardware, and automates the network element deployment process through the MANO (Management and Orchestration) system; the operator can Business needs to expand and shrink quickly and dynamically.
  • MANO Management and Orchestration
  • the license is a way of selling the software, and the license is used according to the characteristics, version, capacity, and usage time. For example, the customer obtains the corresponding rights and license authorization certificates promised by the equipment manufacturer.
  • a license can be used to use multiple control items.
  • Each control item can be understood as a function.
  • the control items of the license control phone software in the mobile phone include: outgoing call, answering call, caller ID and call transfer.
  • the mobile phone manufacturer needs to purchase the license of the telephone software in advance.
  • a VNF instance needs to purchase different licenses in advance to realize the control and use of various software functions.
  • the license management process needs to be automated.
  • the license between the VNF instances on the disaster recovery network has a certain association.
  • the other VNFs in the network need to share the occurrence.
  • the existing license management mechanism does not implement the resource sharing of the license.
  • the license for the VNF instance needs to be configured to be used as a backup. As a result, the license is wasted. Load sharing reduces the utilization of license resources.
  • the application provides a method and a device for sending a license to solve the problem of association and sharing of licenses between different VNF instances.
  • the application provides a method for sending a license license, the method comprising the following steps: a first network device acquires a first request message for applying for a license, where the first request message includes a first virtualized network An identity of the function VNF instance and at least one control function corresponding to the license; determining an association relationship of the first VNF instance according to the identity identifier; determining, according to the association relationship and the at least one control function A license required for the first VNF instance; the license is sent to the first VNF instance.
  • the association relationship includes: an active/standby mutual assistance relationship and a load sharing relationship.
  • the license sending method provided by the present aspect determines the association relationship of the VNF instance by using the identifier of the VNF instance.
  • the VNF instance can share the license between the VNF instances, so the shared license can be granted to the requested VNF instance.
  • the license association and sharing between different VNF instances are implemented, which reduces unnecessary waste of licenses and improves the utilization of license resources.
  • the association relationship is a primary and secondary mutual assistance relationship
  • determining, according to the association relationship and the at least one control item function, the first VNF instance is required.
  • the license includes: determining a second VNF instance that has an active/standby relationship with the first VNF instance; determining whether the second VNF instance has applied for a license, and the license satisfies a sharing condition; if yes, acquiring
  • the license is configured as follows: The first network device needs to allocate a new license for the first VNF instance.
  • the license is quickly shared by obtaining the shared license after determining the VNF instance that has the primary and backup mutual-assisted relationship with the first VNF instance.
  • association relationship is a load sharing relationship
  • determining, according to the association relationship and the at least one control item function, the first VNF instance is required. License including:
  • the sharing policy includes: applying a license for each VNF instance, or applying a shared license to multiple VNF instances, where the shared license includes the multiple VNF instances. All control functions;
  • the sharing policy is to apply for a license for each VNF instance
  • the license of the first VNF instance and the at least one control function are used to search for a matching license, and the matching license is used as the license.
  • the sharing policy is to apply for a shared license for multiple VNF instances, extract at least one control item function required by the first VNF instance from the shared license, and according to the extracted at least one control item The function generates a license required for the first VNF instance.
  • determining the association relationship of the first VNF instance according to the identity identifier including: according to the identity identifier, a network service NS instance, and a network service description template.
  • the NSD determines an association relationship of the first VNF instance.
  • the association relationship between the VNF instances and the processing capability may be pre-stored in the NSD information model to determine, for the first network device or the policy decision point PDP, the association relationship of the VNF instances that send the request message.
  • the license includes the license file or the authorization information in the license, and the license is sent to the first VNF instance, including: the license file Sending to the first VNF instance, or after the authorization information in the license is converted into a message parameter, sending the message parameter to the first VNF instance.
  • the license may be a license identification information. After obtaining the identifier information, the first VNF instance obtains the required license according to the content of the identifier information to the first network device.
  • the method further includes: obtaining, by the indication information, the indication that the first VNF instance is faulty or migrated, where the indication information includes the An identifier of the VNF instance, determining whether the license corresponding to the first VNF instance meets the sharing condition according to the identity identifier; if the sharing condition is met, the license corresponding to the first VNF instance is not released; Otherwise, the license corresponding to the first VNF instance is released.
  • the method further includes: storing the license; establishing a shared resource pool according to the license, where the shared resource pool includes the first VNF instance
  • the association relationship information of the first VNF instance recorded in the shared resource pool is refreshed in the case that the indication information of the failure or migration of the first VNF instance is obtained.
  • the shared resource pool may be established by the policy enforcement point PEP, and the fast license and transmission of the shared license is implemented.
  • the method further includes: acquiring a second request message, where the second request message includes an identity of the third VNF instance and the third VNF At least one control function required by the instance; determining, according to the identity of the third VNF instance and the at least one control function, whether the shared resource pool can allocate a license for the third VNF instance; The capacity of the shared resource pool is expanded, and the required license is sent to the third VNF instance after the expansion; if yes, the license corresponding to the at least one control function of the third VNF instance is determined, and Sending the license to the third VNF instance.
  • the present application provides another method for sending a license, where the method includes the following steps: acquiring a first message from a policy enforcement point PDP, where the first message includes at least one required by the first VNF instance. Controlling a function; determining whether the shared resource pool includes at least one control item function required by the first VNF instance; if yes, determining a license corresponding to the at least one control item function, and sending the license to the license The first VNF instance.
  • the method can be performed by a policy enforcement point PEP or other network device.
  • the method provided by the present invention enables the license of the VNF instance to be quickly licensed and delivered by the shared resource pool of the license, thereby maximizing the sharing of the license between the instances, reducing unnecessary waste of the license, and saving the system. Resources.
  • the method further includes: if not, expanding the shared resource pool; optionally, expanding the shared resource pool
  • the methods include:
  • indication information for indicating the expansion of the shared resource pool, where the indication information includes at least one control item function required by the first VNF instance; sending the indication information to the PDP; receiving from the a license of the PDP, where the license is determined by the PDP according to at least one control item function required by the first VNF instance; adding the license from the PDP to the shared resource pool to increase shared resources The control function in the pool.
  • the method further includes: establishing the shared resource pool, the establishing the shared resource pool, including: acquiring at least one from the PDP a second message, each of the second messages includes a license of the VNF instance; the licenses in all the second messages are counted; and the licenses in all the second messages are included in the shared resource pool; or Combining the licenses in each of the second messages to generate a shared license, and establishing the shared resource pool including the shared license.
  • the method further includes: determining, in the case that the first VNF instance fails or migrates, the first resource pool and the first Whether the license corresponding to the VNF instance satisfies the sharing condition; if the sharing condition is met, the license corresponding to the first VNF instance is not released; otherwise, the license corresponding to the first VNF instance is released, and the license is refreshed.
  • the relationship information of the first VNF instance if the sharing condition is met, the license corresponding to the first VNF instance is not released; otherwise, the license corresponding to the first VNF instance is released, and the license is refreshed.
  • the present application further provides a device for transmitting a license, the device comprising a unit or a module for performing the steps in the various implementation manners of the foregoing first aspect, further comprising: an acquiring unit, a processing unit, and Sending unit, etc.
  • the device may be configured in a first network device, where the first network device includes a policy decision point PDP, a policy enforcement point PEP, and a license directory.
  • the present application further provides another apparatus for transmitting a license, the apparatus comprising a unit or a module for performing the steps in the various implementation manners of the foregoing second aspect, further comprising: an acquiring unit, a processing unit, and Sending unit, etc.
  • the device may be configured in a second network device, where the second network device includes a policy enforcement point PEP and a license directory.
  • the present application provides a network device, including a transceiver, a processor, and a memory, where the processor can execute a program or an instruction stored in the memory, thereby implementing the various implementations of the first aspect. How to send the license.
  • the present application further provides a license sending system, where the system includes a first network device and at least one VNF instance, where the first network device is configured to implement the sending of the license described in each implementation manner of the foregoing first aspect.
  • the method the VNF instance is configured to send a first request message to a first network device, and receive a license from the first network device.
  • the present application further provides a computer storage medium, where the computer storage medium can store a program, and the program can implement some or all of the steps in the embodiments of the method for transmitting the license provided by the application.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method steps described in the above aspects.
  • the method and device for sending a license provided by the present application establish a shared resource pool of a VNF instance with an association relationship to implement license sharing between different VNF instances, and then allocate the VNF instance to the requested VNF instance according to the determined shared license. Improve the utilization of license resources.
  • a VNF instance is abnormal, such as a fault or a migration
  • the validity of the license in the pool When it is determined that there is another VNF instance that has an association relationship with the VNF instance that has an abnormality, the shared license is not released, but the license is continuously provided to other VNF instances having an association relationship, thereby realizing the real Load balancing, avoiding re-application and redistribution of new licenses, resulting in unnecessary waste of licenses.
  • FIG. 1 is a schematic diagram of an NFV architecture according to an embodiment of the present disclosure
  • FIG. 2 is a logical abstract diagram of a license management according to an embodiment of the present application.
  • FIG. 3 is a logical abstract diagram of another license management according to an embodiment of the present disclosure.
  • FIG. 4 is a logical abstract diagram of another license management according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a relationship between VNF instances in a disaster tolerance network according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a method for sending a license according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for sending a license in a master/slave mutual assistance relationship according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of a shared resource pool of a primary-secondary mutual assistance relationship according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of a method for sending a license in a load sharing relationship according to an embodiment of the present disclosure
  • FIG. 10 is a schematic diagram of a shared resource pool of a load sharing relationship according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of another shared resource pool of load sharing relationship according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic flowchart of another method for sending a license according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a license sending apparatus according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of hardware of a network device according to an embodiment of the present disclosure.
  • FIG. 1 a schematic diagram of an NFV architecture provided by an embodiment of the present application.
  • the NFV architecture includes a series of network elements defined by the NFV ISG. Specifically, the network elements involved in the NFV architecture and their functions are as follows:
  • OSS Operations Support Systems
  • BSS Business Support System
  • orchestrator English: Orchestrator
  • NFVO NFV Orchestrator, NFV orchestrator
  • NS network service
  • Network NFV infrastructure layer
  • NFVI Functions Virtualization Infrastructure
  • NSD NS Descriptor
  • VNFM VNF Management
  • VNFM The main function of VNFM is to realize the life cycle management of VNF, such as deployment/expansion/reduction/downline and other automation capabilities.
  • VNFM decomposes the virtual resources such as virtual machines according to the template and VNF capacity requirements, and cooperates with Orchestrator and VIM. Complete the instantiation of the VNF.
  • VIM Virtual Infrastructure Manager
  • infrastructure layer resources such as computing, storage, network resources.
  • EM Element Management, Element Management System
  • EMS Element Management System
  • NFVI Network Functions Virtualization Infrastructure
  • NFVI can include (Virtual Computing), Virtualisation Layer, and Hardware resources.
  • NFV technology decouple the logical network functions from the instance hardware devices, which can greatly reduce the network construction cost and operation cost of the basic telecommunication network operators.
  • the NFV instance software enables the network element to run on various general-purpose hardware. Through the MANO system, the NE deployment process is automated, and operators can quickly and dynamically expand and shrink according to service needs.
  • the function management module of the NFV architecture includes a PDP (Policy Decision Point), a PEP (Policy Enforcement Point), and a License Catalog.
  • the PDP is used to generate a scheduling policy. For example, a VNF instance with an association relationship is determined, and each VNF instance has applied for a license and the license can be shared.
  • the PEP is used to execute the scheduling policy of the PDP and obtain the license.
  • the license catalog is used to store the licenses of all VNF instances and deliver the required licenses for the newly applied VNF instances.
  • the reference NFV architecture can be abstracted into the following four models, as shown in FIG. 2 to FIG.
  • FIG. 2 A logical abstraction diagram of a license management is shown in FIG. 2, which includes an NFVO and at least one VNF instance, where the NFVO includes a PDP, a PEP, and a license catalog, and is used to perform a license for the VNF instance. Management and licensing.
  • the PDP, the PEP, and the directory may be respectively set in different network elements.
  • the PDP and the license catalog are configured in the OSS to implement the management function of the license
  • the PEP is configured in the MANO for executing the policy and assigning the corresponding license to the VNF instance.
  • FIG. 3 the PDP and the license catalog are configured in the OSS to implement the management function of the license
  • the PEP is configured in the MANO for executing the policy and assigning the corresponding license to the VNF instance.
  • the PDP is configured in the NFVO, and the functions such as the PEP, the manufacturer information, and the license catalog are configured in the license manager.
  • the network element in the NFV architecture may be divided into different structures according to the requirements, and is not limited to the three modes provided in this embodiment, which is not limited in this application.
  • VNF instances in order to implement association and sharing between different VNF instances, it is necessary to determine whether a VNF instance has an association relationship with other VNF instances. The following describes the relationship between the VNF instances.
  • the first relationship the primary and secondary mutual assistance relationship
  • the primary and secondary mutual-protection relationship that is, the active/standby redundancy backup, includes a primary VNF instance and a backup VNF instance, and the primary VNF instance and the backup VNF instance share one or more licenses. Only the license of the primary VNF instance takes effect at the same time.
  • the load sharing relationship refers to two or more VNF instances.
  • pool networking In the load sharing relationship, there is a special relationship called a pool networking.
  • the pool networking relationship can be understood as follows: Under normal circumstances, N VNF instances or devices form a pool, and the devices in the pool work in load sharing mode. When a VNF instance or device fails, its other available devices in the pool take over its services.
  • FIG. 5 a schematic diagram of a relationship between VNF instances under a disaster-tolerant network is shown, including the above-mentioned independent (English: standalone) VNF instances, such as VNF1 and VNF4, and VNF2- with primary and secondary mutual assistance relationship. 1 and VNF2-2, VNF3-1 and VNF3-2 with load sharing relationship. Among them, the VNF2 with the primary and secondary mutual assistance relationship and the VNF3 with the load sharing relationship are also connected to each other. By establishing different associations between different VNF instances, it plays the role of redundant backup to ensure the security and stability of the communication network.
  • the technical solution of the present application is based on the association relationship between the VNF instances, and the license corresponding to the VNF instance having the association relationship is formed into a resource pool, and the license is shared. During the implementation of the license policy, the license is re-applied or released according to the association relationship of the applied VNF instance. This reduces the waste of the license.
  • the license sending method provided by the present application is described in detail.
  • the application is applied to the technical scenario shown in FIG. 2, where the scenario includes a PDP, a PEP, a license catalog, and at least one VNF instance, where the PDP, the PEP, and the license catalog are all configured in the first network device.
  • the method for sending the license includes the following steps:
  • step 101 The first network device acquires a first request message for applying for a license, where the first request message includes an identity of the first VNF instance and at least one control function corresponding to the license. .
  • the identity identifier is used to uniquely identify the first VNF instance, and each of the VNF instances corresponds to an identity identifier, such as an ID.
  • the first request message is used to apply for the first network device to allocate a license.
  • the first request message may be directly initiated by the first VNF instance, and may also be trusted by other network entities, such as NFVO, to replace the first VNF instance to apply for a license, which is not limited in this embodiment.
  • Step 102 Determine an association relationship of the first VNF instance according to the identity identifier.
  • the association relationship includes: an active/standby mutual assistance relationship and a load sharing relationship.
  • the process of determining, by the first network device, the association relationship of the first VNF instance according to the identity identifier includes: the first network device according to the identity identifier, a network service (NS) instance, and a network service A description template (NS Descriptor, NSD) determines an association relationship of the first VNF instance.
  • NS network service
  • NSD network service A description template
  • the NSD information model includes a plurality of Ns Deployment Flavour (NsDf for short), and each NsDf represents a network topology under a certain network processing capability, and a processing capability of each VNF/PNF, between the network elements. Link processing capabilities and more.
  • NsDf Ns Deployment Flavour
  • association relationship of the first VNF instance can be represented by Table 1 below.
  • the redundancy relationship group contains the following information:
  • whether a heterogeneous redundancy group can share a license can be determined according to whether the VNF profile belongs to the same manufacturer and the NE type is consistent.
  • the first network device further determines, by using the information reported by the first VNF instance, the association relationship of the first VNF instance.
  • the ES/EMS can obtain the redundancy and mutual assistance relationship between the other network elements in the process of performing the service configuration on the VNF instance. Therefore, the ES/EMS can report the information of the mutual assistance relationship to the OSS, or report the information to the NFVO through the VNFM.
  • the first network device is further configured to acquire association information of the first VNF instance.
  • Step 103 Determine, according to the association relationship and the at least one control item function, a license required by the first VNF instance.
  • the association relationship is a master-slave mutual-aid relationship
  • determining, according to the association relationship and the at least one control item function, the license required by the first VNF instance including: determining that the first VNF instance has a master The second VNF instance of the mutual-assisted relationship; determining whether the second VNF instance has applied for the license, and the license meets the sharing condition, that is, the license can be shared, and if yes, the license is obtained, and if not, the first The VNF instance assigns a new license.
  • determining a license required by the first VNF instance according to the association relationship and the at least one control item function including:
  • the sharing policy includes: applying a license for each VNF instance, or applying a shared license to multiple VNF instances, where the shared license includes the multiple VNF instances. All control features.
  • the sharing policy is to apply for a license for each VNF instance
  • the license of the first VNF instance and the at least one control function are used to search for a matching license, and the matching license is determined.
  • the sharing policy is to apply for a shared license for multiple VNF instances, extract at least one control item function required by the first VNF instance from the shared license, and according to the extracted at least one control item The function generates a license required for the first VNF instance.
  • Step 104 Send the license to the first VNF instance.
  • the shared license is obtained, for example, obtained from the shared resource pool, and then the license is allocated to the first VNF instance.
  • the license includes the license file or the authorization information and the identification information in the license. If the license file is the license file, the process of sending the license to the first VNF instance in step 104 is: the first network device uses the license. The file is sent to the first VNF instance. The first VNF instance is downloaded after receiving the license file, and then the downloaded license is loaded and used.
  • Another implementation manner includes: if the shared license is the authorization information in the license, the process of sending the license by the first network device is: first converting the authorization information in the license into a message parameter, and then performing the A message parameter is sent to the first VNF instance.
  • the first network device only sends the authorization information in the converted license to the first VNF instance, avoids sending or allocating a large license file, and only sends the message parameter to save transmission resources, and the transmission speed is fast and the time is short.
  • the method further includes: the shared license is a license identifier information, and the first network device sends the identifier information to the first VNF instance, after the first VNF instance receives the identifier information, according to the identifier The content of the identifier information is obtained from the first network device to obtain a corresponding license.
  • the shared license is a license identifier information
  • the first network device sends the identifier information to the first VNF instance, after the first VNF instance receives the identifier information, according to the identifier
  • the content of the identifier information is obtained from the first network device to obtain a corresponding license.
  • the manner in which the first network device specifically grants or sends the license to the first VNF instance includes, but is not limited to, the foregoing three types, and may also include other possible implementation manners, which is not limited in this embodiment.
  • the license sending method provided in this embodiment determines the association relationship of the VNF instance by using the identifier of the VNF instance.
  • the VNF instance can share the license between the VNF instances, so the shared license can be granted to the requested VNF instance.
  • the license association and sharing between different VNF instances are implemented, which reduces the waste of unnecessary licenses and improves the utilization of license resources.
  • the method before determining the association relationship of the first VNF instance according to the identity identifier, the method further includes: determining whether the first VNF instance has applied for a license and the license satisfies the sharing. If the license has been applied and the license of the application can be shared, the step of determining the association relationship of the first VNF instance according to the identity identifier is performed (including steps 102 to 104); if not, determining a new one. The license is sent to the first VNF instance.
  • the process of determining, by the first network device, a new license includes: acquiring at least one control item information required by the first VNF instance; determining the new license according to the at least one control item information, and The new license supports at least one control item function required by the first VNF instance.
  • the first network device may obtain the new license from the license catalog, and grant the new license to the first VNF instance.
  • the first network device obtains the license required by the first VNF instance from the license catalog, and then sends the license to the first VNF instance of the requester.
  • the first network device After the first network device obtains a new license from the license catalog, the first network device stores the new license in the shared resource pool for use in the next VNF instance request.
  • the shared resource pool of the VNF instance with the associated relationship is established to implement the license sharing between the different VNF instances, and then the license is allocated to the requested VNF instance according to the determined shared license, thereby improving the license resource. Utilization rate.
  • the method further includes: when the first VNF instance is faulty or migrated, how to use the license in the shared resource pool. Specifically, the method further includes:
  • Step 105 The first network device obtains indication information that is used to indicate that the first VNF instance is faulty or migrated, and the indication information includes an identity identifier of the first VNF instance.
  • Step 106 Determine, according to the identity identifier, whether the license corresponding to the first VNF instance meets a sharing condition, that is, whether the shared resource pool includes a sharable license required by the first VNF instance.
  • Step 107 If the sharing condition is met, the license corresponding to the first VNF instance is not released; otherwise, the license corresponding to the first VNF instance is released, and the association relationship information of the shared resource pool is refreshed.
  • the method provided in this embodiment when a certain VNF instance is abnormal, such as a fault or a migration, determines whether the fault or the migrated VNF instance applies for a license, and disassociates or releases the license in the shared resource pool according to the judgment result. To ensure the validity of the license in the shared resource pool.
  • the shared license is not released, but the license is continuously provided to other VNF instances having an association relationship, thereby realizing the real Load balancing, avoiding re-application and redistribution of new licenses, resulting in unnecessary waste of licenses.
  • the method provided in this embodiment further includes: expanding a shared resource pool.
  • the steps of the expansion are as follows:
  • the first network device obtains a second request message, where the second request message includes an identity of the third VNF instance and at least one control function required by the third VNF instance.
  • the method includes: the PEP sends the indication information for indicating the expansion of the shared resource pool to the PDP, where the indication information includes the third VNF instance needs. At least one control item function for expansion.
  • the PDP receives the indication information, and obtains the license required for the third VNF instance from the license catalog according to the control item that needs to be expanded, and sends the license to the PEP.
  • the PEP adds the license to the shared resource pool.
  • the license is sent to the third VNF instance, and if so, the license corresponding to the at least one control function of the third VNF instance is determined, and the license is sent to the third VNF.
  • the license of the shared resource pool is increased, the utilization of the shared resource pool is improved, and a certain VNF instance occurs in the shared license.
  • the license can be assigned to other VNF instances with mutual help, and the license sharing and sharing between the instances can be implemented.
  • the method provided in this embodiment can be applied to the NFV architecture in which the PEP and the PDP are separated, and the PDP and the license catalog can be configured in the OSS or the NFVO, and the PEP can be configured in the MANO or the license.
  • the method includes:
  • Step 201 The PDP obtains a first request message of the VNF2-1 instance requesting the license, where the first request message includes the identity of the VNF2-1 instance and at least one control function required by the PNF2-1 instance.
  • the VNF 2-1 instance may directly send the first request message to the PDP, and may also send the first request message of the application license by using another network element, such as NFVO, instead of the VNF 2-1 instance.
  • another network element such as NFVO
  • the PDP is applied for the license.
  • the VNF instance may send the first request message before, after, and during the instantiation according to the specific implementation. No restrictions.
  • the triggering of the VNF2-1 instance to initiate the license request message may be NFVO or VNFM, etc., which is not limited in this application.
  • Step 202 The PDP receives the first request message, and determines, according to the identity of the VNF2-1 instance, whether the license has been applied for, and the license of the application can be shared.
  • Step 203 If no, a new license needs to be assigned to the VNF2-1 instance.
  • the specific process includes: determining, by the PDP, the association relationship of the VNF2-1 instance according to the NSD and the NS instance. Specifically, it is determined whether the VNF2-1 instance is an active/standby mutual assistance relationship or a load sharing relationship. If it is determined that the VNF2-2 instance is in the active/standby relationship with the VNF2-1 instance, but the VNF2-2 instance is not currently created or the two instances cannot share the license according to the rules, you need to assign a new license to the VNF2-1 instance. .
  • the process of allocating a new license in step 203 includes: obtaining, by the PDP, at least one control item function required by the VNF2-1 instance, and determining, according to the at least one control item function, a license supporting the function function of the control item, and the license is obtained from the license.
  • the license in the license catalog pre-stores all the control functions of the network.
  • Step 204 The PDP sends a message carrying the new license to the PEP, where the message includes the identity of the VNF2-1 instance and/or at least one control function required by the VNF2-1 instance.
  • Step 205 The PDP sends the new license to the VNF2-1 instance.
  • the manner in which the license is sent includes the following two methods: one is: the PDP sends the license file to the VNF2-1 instance, or the other way, the PDP converts the authorization information in the license into Message parameters, and then send these message parameters to the VNF2-1 instance.
  • step 202 to step 205 is a process in which the PDP applies for and allocates a new license to the VNF 2-1 instance (abbreviation: flow 1).
  • step 202 it is determined whether the VNF 2-1 instance has applied for a license, and the license can be shared. It also includes the method steps of the following process 2.
  • Step 206 If the VNF2-1 instance has applied for a license and the license can be shared, the association relationship between the VNF2-1 instances is determined according to the NSD and the NS instance information.
  • the PDP determines the relationship between the VNF2-1 instance and the VNF2-2 instance based on the identity of the VNF2-1 instance, and the NNF and the NS instance information.
  • the VNF2-1 instance shares the license-2 with the VNF2-2 instance.
  • Step 207 The PDP sends a message that the VNF 2-1 instance and the VNF 2-2 instance share the license-2 to the PEP, and notifies the PEP that the VNF 2-1 instance and the VNF 2-2 instance are in the active/standby relationship.
  • Step 208 The PEP receives the information, and establishes a shared resource pool according to the license-2.
  • the shared resource pool includes the VNF2-1 instance and the VNF2-2 instance sharing the license-2, and the two instances are active and standby. Relationship and other information.
  • a schematic diagram of a shared resource pool is established.
  • the information recorded in the shared resource pool includes: 1. a shared license-2; 2. a shareable instance, a VNF2-1 instance and a VNF2-2 instance; 3. a current mode, an active/standby relationship, and the like.
  • Step 209 The PEP sends the shared license-2 to the VNF2-1 instance, so that the VNF2-1 instance performs authorization control on the control function according to the content of the license-2.
  • step 209 after receiving the license sharing information from the PDP, the PEP also replies with a response message to the PDP.
  • Step 210 When an exception occurs in the VNF2-1 instance or the VNF2-2 instance, for example, termination (English: termination), the indication information is sent to the PDP, where the indication information includes the identity of the requesting VNF instance.
  • the occurrence of the abnormality includes a failure or a migration of the VNF instance.
  • an abnormality occurs in the VNF2-1 example for explanation.
  • Step 211 The PDP receives the indication information, and determines whether the VNF2-1 instance has applied for a license and the applied license can be shared.
  • Step 212 If yes, for example, the license-2 corresponding to the VNF2-1 instance can be shared with the VNF2-2 instance, the shared license-2 is not released, because the license-2 can continue to be used by the VNF2-2 instance, but You need to refresh the shared record of the shared resource pool. For example, if the VNF2-1 instance is abnormal, the license-2 is not shared with the VNF2-2 instance.
  • the release of the license in the embodiment of the present application can be understood as: returning the license to the license catalog for subsequent assignment to other instances; or returning the license to the provider, so that the license is released.
  • the corresponding VNF instance is no longer used.
  • Step 213 The PDP sends a message or an instruction that the VNF2-1 instance is abnormal and cannot share the license-2 to the PEP.
  • Step 214 The PEP receives the message or instruction and updates the information in the shared resource pool.
  • step 212 if it is determined that the VNF2-1 instance does not share the license, the unshared license of the VNF2-1 instance is released, because the release of the unshared license does not affect the use of the license by other instances, and saves a certain storage space.
  • the VNF2-1 instance when the VNF2-1 instance is abnormal, the VNF2-1 instance may be re-established.
  • the process of step 207 to step 210 ie, process 2) may be performed.
  • the license resource pool refreshes the new license sharing information.
  • This embodiment provides a method for sending a license in an active/standby relationship.
  • a VNF instance is abnormal, another VNF instance with its active/standby relationship can continue to use the exception.
  • the license of the VNF instance is used to maximize the sharing of licenses between VNF instances and reduce unnecessary waste of licenses.
  • the method provided in this embodiment can be applied to the NFV architecture in which the PEP and the PDP are separated.
  • the PDP and the license catalog can be configured in the same network element, for example, OSS or NFVO, and the PEP can be configured in the license manager. For example MANO.
  • the difference between this embodiment and the second embodiment is that the present embodiment is related to the association and sharing of the license between the VNF instances in the load sharing relationship. Specifically, as shown in FIG. 9, the method includes:
  • Step 301 The PDP obtains a first request message, where the first request message includes an identity of the VNF3-1 instance and at least one control function required by the VNF3-1 instance.
  • the PDP obtains the first request message by using an NFVO application license.
  • Step 302 The PDP receives the first request message, and determines whether the load sharing relationship is available according to the information such as the identity identifier, the NSD, and the NS instance of the VNF3-1.
  • Step 303 If it is a load sharing relationship, it is determined whether the VNF3-1 instance is the first application for the license.
  • Step 304 If it is the first application, the PDP sends the information of the control function required for the VNF3-1 instance to the license catalog, and then the PDP obtains the license required for the VNF3-1 instance, such as the license-3, from the license catalog.
  • the PDP sends the obtained license-3 and the identifier of the VNF3-1 instance to the PEP, so that the PEP can establish a shared resource pool of the license-3 according to the information.
  • Step 305 The PDP sends the license-3 to the VNF3-1 instance.
  • Step 306 If the VNF3-1 instance is not the first time to apply for a license, determine the sharing policy according to the load sharing relationship, that is, determine which sharing mode the VNF3-1 instance uses to share the license.
  • Method 1 Apply a license to each VNF instance in advance.
  • the PDP assigns a license to each VNF instance in the license catalog according to the control function of each VNF instance, and stores the licenses in the shared resource pool.
  • Manner 2 A large license is established for all the control functions required for each VNF instance. The license is used to control all the control functions of the multiple VNF instances and is shared by multiple VNF instances.
  • step 307a the license matching the VNF3-1 instance and the at least one control function are searched for, and the matching license is determined as VNF3. -1 required license for the instance.
  • the matching means that the license pre-stored in the shared resource pool and the control function of the license are the same as the license required by the VNF3-1 instance, or the license required for the VNF3-1 instance is A license that is applied for and stored in the shared resource pool.
  • the PDP is combined with the NSD and the NS instance information to determine the load sharing relationship between the VNF3-1 instance and the VNF3-2 instance, and the license required for the VNF3-1 instance is the license-3 in the shared resource pool.
  • the license required for the VNF3-2 instance is the license-3' in the shared resource pool, and the information about the shared mode of the VNF3-1 and the VNF3-2 is: License-3 and License-3' are sent to the PEP.
  • the PEP establishes a shared resource pool for the license.
  • the step 307b is performed: the new license is not required, and at least one control function required for the VNF3-1 instance is extracted from the shared license, and the extracted control items are extracted.
  • the function generates a license corresponding to the VNF3-1 instance, and then licenses the license to the VNF3-1 instance.
  • the shared license described in the second method includes 100 control items.
  • the license applied by the VNF3-1 instance includes only 10 control items, and the 10 control functions are included in the shared 100 control items.
  • the 10 control functions required for the VNF3-1 instance are extracted from the 100 control function functions, and the 10 control functions are generated to generate a license, and the license is sent to the VNF3-1 instance.
  • Step 308 Establish a shared resource pool of the license-3 and/or the license-3'. As shown in FIG. 10 and FIG. 11, the load sharing relationship between the VNF3-1 instance and the VNF3-2 instance is shared, and the license-3 is shared, or License-3/3'.
  • Step 309 Send the license required by the VNF3-1 instance to the VNF3-1 instance.
  • the specific manner of the license is the same as that of the first embodiment and the second embodiment, and is not described in detail in this embodiment.
  • the method further includes: the PEP replies to the PDP with the response message of the license sharing, so that in the subsequent process, the PEP can perform the authorization control based on the license sharing policy.
  • the method for the authorization control of the mode 1 and mode 2 may be slightly different.
  • the sub-licenses in the resource pool have the right to apply for the priority application, that is, the VNF instance applying for the license first obtains the license.
  • the first network device can determine that the license exceeds the shared resource pool. Volume, and its corresponding VNF instance, and then expand the shared resource pool according to the license excess.
  • the PDP determines whether to expand the shared resource pool according to the function of the control item included in the request message of each VNF instance.
  • the capacity of the shared license is increased when the number of applied licenses exceeds the shared license capacity of the resource pool. That is, the capacity pool is continuously expanded to meet the control of multiple VNF instances. Item requirements.
  • the capacity expansion method can obtain a new license from the license catalog to increase the capacity of the resource pool.
  • the new license can be used to obtain a new license for expansion. This embodiment does not limit this.
  • the processing may be performed by using the foregoing steps 306 to 309 (flow 2).
  • Step 310 When an abnormality occurs in the VNF3-1 instance or the VNF3-2 instance, for example, when a fault or a migration is sent, the PDP is requested to release the license. Specifically, the VNF3-1 instance sends the indication information to the PDP, and is used to indicate that the license is released.
  • the indication information includes the identifier of the VNF3-1 instance.
  • Step 311 The PDP receives the indication information, and determines whether the VNF3-1 instance has a load sharing relationship with other instances, and determines whether to release or update the license of the VNF3-1 instance. Specifically, different decisions can be made according to how the shared resource pool is created:
  • a decision-making method is used for the license sharing of the mode 1.
  • the PDP determines whether to release the license applied by the VNF3-1 instance according to the policy or the service, and refresh the shared information.
  • Another way to make a decision is to share the license of the second mode: the license is not released, and only the shared information is refreshed.
  • Step 312 The PDP sends the updated shared information to the PEP through a message to notify the PEP VNF3-1 instance that an abnormality occurs and the sharing relationship changes. For example, when the VNF3-1 instance is faulty, the VNF3-2 instance and the VNF3-1 instance no longer share the license-3, and the binding relationship of the VNF3-1 instance is released.
  • Step 313 The PEP receives the message and updates the associated information in the resource pool.
  • step 306 to step 309 may be performed, but if the mode 1 is adopted in step 311, sharing is performed. If the license is not released, you can no longer apply for a new license and redistribute the license. You can directly bind the original license of the abnormal VNF instance and refresh the resource pool information.
  • the method provided in this embodiment solves the problem that the license is automatically managed in the load balancing mode, and the license sharing between the mutual help instances is maximized, and unnecessary license waste is reduced.
  • the mutual help license is abnormal, the license is not released. Instead, it is assigned to other instances with associated relationships for true load sharing.
  • the PEP establishes a license shared resource pool according to the sharing and mutual assistance relationship of the PDP, and implements a license managed by the pool, and mutually enjoys resources among the mutual help instances.
  • the capacity pool is different.
  • the shared resource pool is expanded to meet the authorization control requirements of multiple VNF instances, which improves the utilization of the shared resource pool.
  • the license catalog may be configured in the PEP or other license manager to allocate a new VNF instance that is not created or not stored in the resource pool. License.
  • the configuration of the catalog is in the PEP or the PDP, and can be configured according to the technical solution. This application does not limit this.
  • the application also provides a method for sending a license, which is used to establish a shared license for all VNF instances with associations and implement sharing.
  • the method can be performed by the policy enforcement point PEP or by other network devices. Specifically, as shown in FIG. 12, the method includes the following steps:
  • Step 401 The PEP acquires a first message from the policy execution point PDP, where the first message includes at least one control item function required by the first VNF instance, and the first message may further include the identity of the first VNF instance. Information such as identification and association.
  • the management relationship includes an active/standby mutual assistance relationship and a load sharing relationship.
  • Step 402 Determine whether the at least one control item function required by the first VNF instance is included in the shared resource pool.
  • Step 403 If yes, determine a license corresponding to the at least one control item function, and send the license to the first VNF instance.
  • step 402 it is determined that, if the shared resource pool does not include the at least one control item function required by the first VNF instance, the indication information for indicating the expansion of the shared resource pool is generated, and the indication information is sent to the PDP. To obtain a license that needs to be expanded.
  • the expansion of the shared resource pool includes: the PEP generates the indication information for indicating the expansion of the shared resource pool, where the indication information includes at least one control item function required by the first VNF instance, and Transmitting the indication information to the PDP; receiving a license from the PDP, where the license is determined by the PDP according to at least one control item function required by the first VNF instance; The license is added to the shared resource pool.
  • the PDP may obtain the license required by the first VNF instance from the license catalog, and obtain the license from the other network element device, which is not limited in this embodiment.
  • the method further includes: establishing the shared resource pool.
  • the method for establishing the shared resource pool includes: acquiring at least one second message from the PDP, where each of the second messages includes a license of a VNF instance, and each license corresponds to at least one control item function. The licenses in all the second messages are collected; the licenses in all the second messages are combined to form the shared resource pool; or the licenses in the second message are combined to generate a shared license, and the license is established.
  • a shared resource pool including the shared license.
  • the embodiment further includes: releasing, or shrinking, a license in the shared resource pool when an abnormality occurs in a VNF instance.
  • the process is as follows: if the PDP obtains the indication information that is used to indicate that the first VNF instance is faulty or migrated, whether the license corresponding to the first VNF instance meets the sharing condition, and if the sharing is satisfied, If the condition is not, the license corresponding to the first VNF instance is not released; otherwise, the license corresponding to the first VNF instance is released, and the association information of the first VNF instance is refreshed, for example, the first VNF instance and other VNF instances are released. connection relation.
  • the method provided in this embodiment by establishing a shared resource pool for the VNF instance with the associated relationship, implements the maximum license sharing between the VNF instances and reduces unnecessary waste of the license.
  • the embodiment of the present application also provides a corresponding device embodiment.
  • FIG. 13 is a schematic structural diagram of a device for sending a license according to an embodiment of the present disclosure.
  • the apparatus is for performing a transmission method of the license as shown in FIGS. 6, 7, and 9.
  • the apparatus may include an obtaining unit 1301, a processing module 1302, and a transmitting unit 1303.
  • the obtaining unit 1301 is configured to acquire a first request message for applying for a license, where the first request message includes an identity of the first VNF instance and at least one control item function corresponding to the license.
  • the processing unit 1302 is configured to determine, according to the identity identifier, an association relationship of the first VNF instance, and determine, according to the association relationship and the at least one control item function, a license required by the first VNF instance.
  • the sending unit 1303 is configured to send the license to the first VNF instance.
  • the processing unit 1302 is specifically configured to determine that the first VNF instance has primary and secondary mutual assistance in the case that the association relationship is an active/standby relationship.
  • the second VNF instance of the relationship determines whether the second VNF instance has applied for a license, and the license satisfies the sharing condition.
  • the obtaining unit 1301 is further configured to acquire the license when the VNF instance with the active/standby mutual assistance relationship has applied for a license, and the license meets the sharing condition.
  • the processing unit 1302 is specifically configured to determine, according to the load sharing relationship, a sharing policy, where the association relationship is a load sharing relationship, where the sharing is performed.
  • the policy includes applying for a license for each VNF instance, or applying a shared license for multiple VNF instances, where the shared license includes all control functions of the multiple VNF instances.
  • the processing unit 1302 is further configured to: if the sharing policy is to apply for a license for each VNF instance, search for a matching license according to the identity identifier of the first VNF instance and the at least one control item function, And the matching license is used as the license required by the first VNF instance; if the sharing policy is to apply for a shared license for multiple VNF instances, extracting the first VNF from the shared license At least one control item function required by the instance, and generating a license required by the first VNF instance according to the extracted at least one control item function.
  • the processing unit 1302 is specifically configured to determine an association relationship of the first VNF instance according to the identity identifier, the NS instance, and the NSD.
  • the license includes the authorization information in the license file or the license.
  • the sending unit 1303 is specifically configured to send the license file to the first VNF instance, or send the message parameter to the first VNF after the authorization information in the license is converted into a message parameter. Example.
  • the acquiring unit 1301 is further configured to: obtain indication information that is used to indicate that the first VNF instance is faulty or migrated, where the indication information includes the The identity of the first VNF instance.
  • the processing unit 1302 is further configured to determine, according to the identity identifier, whether the license corresponding to the first VNF instance meets a sharing condition, and if the sharing condition is met, the license corresponding to the first VNF instance is not released. Otherwise, the license corresponding to the first VNF instance is released.
  • the device further includes: a storage unit, configured to store the license of the license and other VNF instances.
  • the processing unit 1302 is further configured to establish a shared resource pool according to the obtained related information of the license and the license, where the shared resource pool includes an association relationship of the first VNF instance, and acquires the first VNF instance. In the case of the failure or the indication of the migration, the association relationship information of the first VNF instance recorded in the shared resource pool is refreshed.
  • the processing unit 1302 is further configured to determine, according to the at least one control item function corresponding to the license in the first request message, whether the shared resource pool is in the shared resource pool.
  • the license may be allocated to the first VNF instance; if not, the shared resource pool is expanded, and the license is allocated to the first VNF instance after the expansion; if yes, the first VNF instance is allocated. License.
  • the method for expanding the capacity can obtain a new license through the license catalog, and then send the new license to the first VNF instance.
  • the license sharing device determines the association relationship of the VNF instance by using the identity of the VNF instance.
  • the VNF instance can share the license between the VNF instances, so the shared license can be licensed to the VNF instance.
  • the license association and sharing between different VNF instances are implemented, which reduces the waste of unnecessary licenses and improves the utilization of license resources.
  • a VNF instance is abnormal, such as a fault or a migration
  • the validity of the license in the pool is determined whether the fault or the migrated VNF instance has applied for a license, and the license is disassociated or released from the shared resource pool according to the judgment result, thereby ensuring the shared resource. The validity of the license in the pool.
  • the acquiring unit 1301 is configured to acquire a first message from a policy execution point PDP, where the first message includes an identity identifier of the first VNF instance, where The association information of the first VNF instance and the license corresponding to the first VNF instance.
  • the obtaining unit 1301 is configured to acquire a first message from a policy execution point PDP, where the first message includes at least one control item function required by the first VNF instance.
  • the processing unit 1302 is configured to determine whether the at least one control item function required by the first VNF instance is included in the shared resource pool, and if yes, determine a license corresponding to the at least one control item function.
  • the sending unit 1303 is configured to send the license to the first VNF instance if the at least one control item function is included.
  • the processing unit 1302 is further configured to expand the shared resource pool if the shared resource pool does not include the at least one control item function. .
  • the processing unit 1302 is specifically configured to generate indication information for indicating the expansion of the shared resource pool, where the indication information includes at least one control item function required by the first VNF instance, and the sending unit 1303 further
  • the acquiring unit 1301 is further configured to receive a license from the PDP, where the license is at least one control item function required by the PDP according to the first VNF instance.
  • the determining unit 1302 is further configured to add the license from the PDP to the shared resource pool.
  • the processing unit 1302 is further configured to establish the shared resource pool.
  • the acquiring unit 1301 is further configured to acquire at least one second from the PDP. a message, each of the second messages includes a license of a VNF instance; the processing unit 1302 is configured to collect statistics of all the second messages, and collect the licenses in all the second messages.
  • the shared resource pool is merged; or the license in each of the second messages is combined to generate a shared license, and the shared resource pool including the shared license is established.
  • the acquiring unit 1301 is further configured to obtain a second request message, where the second request message includes an identifier of the third VNF instance and the third At least one control item function required by the VNF instance.
  • the processing unit 1302 is further configured to determine, according to the identity identifier of the third VNF instance and the at least one control item function, whether the shared resource pool can allocate a license for the third VNF instance; if not, The shared resource pool is expanded; if yes, the license corresponding to the at least one control function of the third VNF instance is determined.
  • the sending unit 1303 is further configured to send the required license to the third VNF instance after the expansion, or send the license to the third if the license of the third VNF instance is determined. VNF instance.
  • the present application further provides a network device, as shown in FIG. 14 , which is a schematic structural diagram of a network device according to the embodiment.
  • the network device may be a shared device of the license in any of the foregoing embodiments, and is used to implement the method steps in the foregoing embodiments.
  • the network device may be composed of components such as a transceiver 141, a processor 142, and a memory 143.
  • the processor 142 is a control center of the network device that connects various portions of the entire network device using various interfaces and lines, by running or executing software programs and/or modules stored in the memory, and recalling data stored in the memory 143, To perform various functions of the network device and/or process data.
  • the processor 142 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or any combination.
  • the memory 143 may include a volatile memory, such as a random access memory (RAM); and may also include a non-volatile memory, such as a flash memory (flash) A hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above types of memories.
  • RAM random access memory
  • flash non-volatile memory
  • HDD hard disk drive
  • SSD solid-state drive
  • a program or code may be stored in the memory, and the processor 142 in the network device may implement the functions of the network device by executing the program or code.
  • the transceiver 141 can be configured to receive or transmit data, the transceiver can transmit data to a terminal device or other network device under the control of the processor; the transceiver receives the terminal under the control of the processor Data sent by a device or other network device.
  • the transceiver 141 can be used to implement the method for sending a license in the foregoing various embodiments.
  • the functions to be implemented by the obtaining unit 1301 and the transmitting unit 1303 may be implemented by the transceiver 141 of the network device or by the transceiver 141 controlled by the processor 142;
  • the implemented functions can be implemented by the processor 142, and the memory 143 is used to store the license.
  • the present invention further provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments of the method for transmitting the license provided by the present invention.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, abbreviated as: ROM) or a random access memory (English: random access memory, abbreviation: RAM).
  • the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM. , a disk, an optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or in certain portions of the embodiments.
  • a computer device which may be a personal computer, server, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Technology Law (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Storage Device Security (AREA)

Abstract

本申请公开一种许可证License的发送方法和装置，所述方法包括：获取用于申请License的第一请求消息，所述第一请求消息包括第一虚拟化网络功能VNF实例的身份标识和所述License所对应的至少一个控制项功能；根据所述身份标识确定所述第一VNF实例的关联关系；根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License；将所述License发送给所述第一VNF实例。本申请提供的方法解决了互助关系下License的自动管理问题，实现具有关联关系的VNF实例间的License最大程度的共享，减少不必要的License浪费，实现真正的负荷分担。

Description

一种License的发送方法和装置
本申请要求于2017年7月14日提交中国专利局、申请号为201710574901.5、发明名称为“一种License的发送方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及虚拟化技术领域，尤其涉及一种License的发送方法和装置。
背景技术
2012年10月13家品牌运营商(包括AT&T、Verizon、VDF、DT、T-Mobile、BT、Telefonica等)联合发起成立ETSI(European Telecommunications Standards Institute，欧洲电信标准化协会)NFV ISG(Industry Specification Group，简称：NFV行业规范组)，目标是基于现代化的虚拟化技术，网络设备可以基于通用硬件，如基于标准的大容量服务区、存储和以太网，不同供应商提供的应用以软件形式，远程自动部署在统一的云虚拟化基础设施上，从而降低成本，提高效率、增加敏捷能力。
在网络功能虚拟化(Network Functions Virtualization，NFV)环境中，各个功能实例之间通过机机接口实现对虚拟资源的管理和使用。进一步地，NFV实例通过将网元软件化，使网元可以运行在各种通用的硬件上，并通过MANO(Management and orchestration，管理和编排)系统，将网元部署过程自动化；运营商可以根据业务需要快速动态地进行扩缩容。
通常软件的使用需要授权许可，目前常用的许可方式是通过许可证(License)实现许可。所述License是软件销售的一种方式，按照特性、版本、容量和使用时间等方式进行授权使用，例如客户获得设备商所承诺的相应权利和License授权证书。
一个License可以用于使用多个控制项，每个控制项可以理解为一种功能，例如，控制手机中的电话软件的License的控制项包括：呼出电话、接听电话、来电显示和呼叫转移等。为了实现对这些控制项的使用，手机生产厂家需要预先购买该电话软件的License，同理地，一个VNF实例需要预先购买不同的Licenses才能实现各种软件功能的控制和使用。
在NFV环境下，License管理过程需要自动化，容灾组网的VNF实例之间License会有一定关联性，当组网中的某一个VNF实例发生故障时，组网中的其它VNF需要分担该发生故障的VNF实例的功能和业务。但现有的对License的管理机制中无法实现License的资源共享，进而需要配置给VNF实例较多的License用来做备份，导致License的浪费，对于并且具有一定关联性的VNF实例之间无法实现负荷的分担，降低了License资源的利用率。
发明内容
本申请提供了一种License的发送方法和装置，以解决不同的VNF实例之间License的关联和共享问题。
第一方面，本申请提供了一种许可证License的发送方法，该方法包括以下步骤：第一网络设备获取用于申请License的第一请求消息，所述第一请求消息包括第一虚拟化网络功能VNF实例的身份标识和所述License所对应的至少一个控制项功能；根据所述身份标识确定所述第一VNF实例的关联关系；根据所述关联关系和所述至少一个控制项功能确定所述第 一VNF实例所需的License；将所述License发送给所述第一VNF实例。其中，所述关联关系包括：主备互助关系和负荷分担关系。
本方面提供的License发送方法，通过VNF实例的身份标识确定该VNF实例的关联关系，由于具有关联关系的VNF实例之间可以共享License，所以可将该共享的License许可给请求的VNF实例，从而实现了不同VNF实例之间的License关联和共享，减少了不必要的License浪费，提高License资源的利用率。
结合第一方面，在第一方面的一种实现方式中，如果所述关联关系为主备互助关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：确定与所述第一VNF实例具有主备互助关系的第二VNF实例；判断所述第二VNF实例是否已经申请了License，且所述License满足共享条件；如果是，则获取所述License；如果否，则第一网络设备需要为该第一VNF实例分配新的License。
本实现方式中，在主备互助关系的情况下，在确定与第一VNF实例具有主备互助关系的VNF实例后，通过获取该共享的License，实现了License快速共享。
结合第一方面，在第一方面的另一种实现方式中，如果所述关联关系为负荷分担关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：
根据所述负荷分担关系确定共享策略，所述共享策略包括为每个VNF实例申请一个License，或者为多个VNF实例申请一个共享的License，所述共享的License中包括所述多个VNF实例的所有控制项功能；
如果所述共享策略是为每个VNF实例申请一个License，则根据所述第一VNF实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License作为所述第一VNF实例所需的License；
如果所述共享策略是为多个VNF实例申请一个共享的License，则从所述共享的License提取所述第一VNF实例所需的至少一个控制项功能，并根据所述提取的至少一个控制项功能生成所述第一VNF实例所需的License。
本实现方式中，在负荷分担的情况下，配置两种License的共享方式，一种是为每个VNF实例申请一个License，另一种是为所有的VNF实例申请一个共同的License来实现License的共享，从而实现了负荷分担关系的实例之间License最大程度的共享。
结合第一方面，在第一方面的又一种实现方式中，根据所述身份标识确定所述第一VNF实例的关联关系，包括：根据所述身份标识、网络业务NS实例和网络业务描述模板NSD确定所述第一VNF实例的关联关系。其中，每个VNF实例的关联关系，以及处理能力可以预先存储在NSD信息模型中，用以为第一网络设备或者策略决策点PDP判断发送请求消息的VNF实例的关联关系。
结合第一方面，在第一方面的又一种实现方式中，所述License包括License文件或License中的授权信息，将所述License发送给所述第一VNF实例，包括：将所述License文件发送给所述第一VNF实例，或者，在所述License中的授权信息转换成消息参数之后，将所述消息参数发送给所述第一VNF实例。另外，所述License还可以是一个License标识信息，第一VNF实例在获取该标识信息后，根据该标识信息的内容到第一网络设备中获取其所需要的License。
结合第一方面，在第一方面的又一种实现方式中，所述方法还包括：获取用于指示所述第一VNF实例发生故障或迁移的指示信息，所述指示信息中包括所述第一VNF实例的身份标 识；根据所述身份标识确定与所述第一VNF实例所对应的License是否满足共享条件；如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License。
本实现方式中，当具有关联关系，例如主备互助关系的VNF实例发生异常时，License不会被释放，而是继续给共享的实例继续使用，实现了真正的负荷分担。
结合第一方面，在第一方面的又一种实现方式中，所述方法还包括：存储所述License；根据所述License建立共享资源池，所述共享资源池中包括所述第一VNF实例的关联关系；在获取所述第一VNF实例的发生故障或迁移的指示信息的情况下，刷新所述共享资源池中记录的所述第一VNF实例的关联关系信息。其中，所述共享资源池可由策略执行点PEP来建立，实现了对共享License的快速许可和发送。
结合第一方面，在第一方面的又一种实现方式中，所述方法还包括：获取第二请求消息，所述第二请求消息中包括第三VNF实例的身份标识和所述第三VNF实例所需的至少一个控制项功能；根据所述第三VNF实例的身份标识和所述至少一个控制项功能，判断所述共享资源池中是否能为所述第三VNF实例分配License；如果否，则对所述共享资源池进行扩容，扩容后向所述第三VNF实例发送其所需的License；如果是，则确定所述第三VNF实例的至少一个控制项功能所对应的License，并将所述License发送给所述第三VNF实例。
第二方面，本申请提供了另一种License的发送方法，所述方法包括以下步骤：获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例所需的至少一个控制项功能；判断共享资源池中是否包含所述第一VNF实例所需的至少一个控制项功能；如果包含，则确定所述至少一个控制项功能所对应的License，并将所述License发送给所述第一VNF实例。该方法可以由策略执行点PEP或者其它网络设备执行。
本方面提供的方法，通过建立License的共享资源池，对具有关联关系的VNF实例的License的快速许可和下发，实现了实例间的License最大程度的共享，减少不必要的License浪费，节约系统资源。
结合第二方面，在第二方面的一种实现方式中，所述方法还包括：如果不包含，则对所述共享资源池进行扩容；可选的，一种对所述共享资源池进行扩容的方法包括：
生成用于指示所述共享资源池扩容的指示信息，所述指示信息中包括所述第一VNF实例所需的至少一个控制项功能；将所述指示信息发送给所述PDP；接收来自所述PDP的License，所述License是由所述PDP根据所述第一VNF实例所需的至少一个控制项功能所确定；将所述来自PDP的License添加到所述共享资源池中，以增加共享资源池中的控制项功能。另外，还可以从其它网元中获取扩容的License，例如，直接从License catalog中获取。
结合第二方面，在第二方面的另一种实现方式中，所述方法还包括：建立所述共享资源池，所述建立所述共享资源池，包括：获取来自所述PDP的至少一个第二消息，每个所述第二消息中包含一个VNF实例的License；统计所有所述第二消息中的License；将统计的所有所述第二消息中的License组成所述共享资源池；或者，将每个所述第二消息中的License合并生成一个共享的License，并建立包括所述共享的License的所述共享资源池。
结合第二方面，在第二方面的另一种实现方式中，所述方法还包括：在所述第一VNF实例发生故障或迁移的情况下，判断所述共享资源池中与所述第一VNF实例所对应的License是否满足共享条件；如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License，并刷新所述第一VNF实例的关联关系信息。
第三方面，本申请还提供了一种License的发送装置，该装置包括用于执行上述第一方 面各种实现方式中的步骤的单元或模块，进一步地，该装置包括获取单元、处理单元和发送单元等。具体地，该装置可配置在第一网络设备中，所述第一网络设备包括策略决策点PDP、策略执行点PEP和License目录等。
第四方面，本申请还提供另一种License的发送装置，该装置包括用于执行上述第二方面各种实现方式中的步骤的单元或模块，进一步地，该装置包括获取单元、处理单元和发送单元等。进一步地，该装置可以配置在第二网络设备中，所述第二网络设备包括策略执行点PEP和License目录等。
第五方面，本申请提供一种网络设备，包括收发器、处理器和存储器，所述处理器可以执行所述存储器中所存储的程序或指令，从而实现以第一方面各种实现方式所述License的发送方法。
第六方面，本申请还提供一种License发送系统，该系统包括第一网络设备和至少一个VNF实例，所述第一网络设备用于实现上述第一方面各个实现方式中所述的License的发送方法，所述VNF实例用于向第一网络设备发送第一请求消息，以及接收来自所述第一网络设备的License。
第七方面，本申请还提供了一种计算机存储介质，该计算机存储介质可存储有程序，该程序执行时可实现包括本申请提供的License的发送方法各实施例中的部分或全部步骤。
第八方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行上述各方面所述的方法步骤。
本申请提供的License的发送方法和装置，通过建立具有关联关系的VNF实例的共享资源池，以实现不同VNF实例之间的License共享，然后再根据确定的共享License许可分配给请求的VNF实例，提高了License资源的利用率。
另外，当某个VNF实例发生异常，例如故障或迁移时，通过判断该故障或迁移的VNF实例是否申请了License，并根据判决结果对共享资源池中License解除关联关系或者释放，从而保证共享资源池中License的有效性。其中，当判断与发生异常的VNF实例之间存在具有关联关系的其它VNF实例时，不释放该共享的License，而是继续将License提供给具有关联关系的其它VNF实例使用，从而实现了真正的负荷分担，避免重新申请再分配新的License，造成不必要的License浪费。
附图说明
为了更清楚地说明本申请的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种NFV架构的示意图；
图2为本申请实施例提供的一种License管理的逻辑抽象图；
图3为本申请实施例提供的另一种License管理的逻辑抽象图；
图4为本申请实施例提供的又一种License管理的逻辑抽象图；
图5为本申请实施例提供的一种在容灾组网下VNF实例的关系示意图；
图6为本申请实施例提供的一种License发送方法的流程示意图；
图7为本申请实施例提供的一种主备互助关系下的License发送方法的流程示意图；
图8为本申请实施例提供的一种主备互助关系的共享资源池的示意图；
图9为本申请实施例提供的一种负荷分担关系下的License发送方法的流程示意图；
图10为本申请实施例提供的一种负荷分担关系的共享资源池的示意图；
图11为本申请实施例提供的另一种负荷分担关系的共享资源池的示意图；
图12为本申请实施例提供的另一种License发送方法的流程示意图；
图13为本申请实施例提供的一种License发送装置的结构示意图；
图14为本申请实施例提供的一种网络设备的硬件结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明实施例中的技术方案，并使本发明实施例的上述目的、特征和优点能够更加明显易懂，下面结合附图对本发明实施例中的技术方案作进一步详细的说明。
在对本发明实施例的技术方案说明之前，首先结合附图对本发明实施例的应用场景进行说明。参见图1，本申请实施例提供的一种NFV架构的示意图。该NFV架构包括NFV ISG定义的一系列网元，具体地，该NFV架构中所涉及的网元及其功能如下：
OSS(Operations Support Systems，运营支撑系统)或BSS(Business Support System，业务支撑系统)包括传统的管理功能，以及针对虚拟化应用实现与编排器(英文：Orchestrator)相交互，以完成对网络的操作和维护。
NFVO(NFV Orchestrator，NFV编排器)主要功能是实现运营商域内的网络业务(Network Service，NS)生命周期管理(如部署/扩容/缩容/下线等)，以及NFV的基础设施层(Network Functions Virtualization Infrastructure，NFVI)资源编排、策略管理等功能；其中，NFVO根据NS描述模板(NS Descriptor，NSD)分解出对各VNF的需求，配合VNF管理(VNF Management，VNFM)实现VNF的部署。
VNFM主要功能是实现对VNF的生命周期管理，如部署/扩容/缩容/下线等自动化能力；VNFM根据模板及VNF容量需求，分解出对虚拟机等虚拟资源的需求，与Orchestrator、VIM配合完成VNF的实例化。
VIM(Virtualised Infrastructure Manager，虚拟基础设施资源管理器)主要功能是实现对整个基础设施层资源(例如计算、存储、网络资源)的管理和监控。
EM(Element Management,网元管理)或者EMS(Element Management System，网元管理系统)主要功能是对传统网元进行管理，例如管理每个VNF实例等。
NFVI(Network Functions Virtualization Infrastructure，NFV的基础设施层)用于对NFV的基础设施建设，具体地，NFVI中可以包括(Virtual Computing),Virtualisation Layer和硬件资源(Hardware resources)。
NFV技术的核心理念在于把逻辑上的网络功能从实例硬件设备之中解耦出去，以其能够大幅度地降低基础电信网络运营商的网络建设成本与运营成本。NFV实例通过将网元软件化，使网元可以运行在各种通用的硬件上；并通过MANO系统，将网元部署过程自动化，运营商可以根据业务需要快速动态地进行扩缩容。
在NFV架构的License管理中还包括PDP(Policy Decision Point,策略决策点)、PEP(Policy Enforcement Point,策略执行点)和License catalog(许可证目录)等功能模块，其中，PDP用于生成调度策略，例如确定具有关联关系的VNF实例，以及每个VNF实例是否已经申请了License且该License可以共享。PEP用于执行PDP的调度策略并获取License。所述License catalog用于存储所有VNF实例的License，并为新申请的VNF实例下发其所需的License。
根据上述对NFV架构的分析和介绍，从License的PDP、PEP以及License catalog的角度，可以将参考的NFV架构抽象出以下4种模型，如图2至图4所示。
参见图2示出了一种License管理的逻辑抽象图，该抽象图中包括NFVO和至少一个VNF实例，其中所述NFVO中包括PDP、PEP和License catalog等功能，用于对VNF实例的License进行管理和许可。另外，可选的，还可以将PDP,PEP和目录分别设置在不同的网元中。例如图3所示，将PDP和License catalog配置在OSS中，实现对License的管理功能，将PEP配置在MANO中，用于执行策略以及许可分配对应的License给VNF实例。或者如图4所示，将PDP配置在NFVO中，将PEP、厂家信息和License catalog等功能配置在许可证管理器。此外，根据需求还可以对NFV架构中的网元划分不同的结构，而不限于本实施例提供的三种方式，对此本申请不予限制。
本申请各个实施例中为了实现不同VNF实例之间的关联和共享，需要确定一个VNF实例与其它的VNF实例之间是否具备关联关系，下面介绍VNF实例之间所具备的关联关系。
第一种关系：主备互助关系
所述主备互助关系，或者称为主备冗余备份，即包括一个主要的VNF实例和一个备份的VNF实例，且该主要的VNF实例与备份的VNF实例之间共享一个或多个License，并且在同一时刻只有主VNF实例的License生效。
第二种关系：负荷分担关系
所述负荷分担关系是指两个或两个以上的VNF实例中，每个VNF实例都具有一个License，每个License能够控制或授权多个控制项。多个VNF实例平均分摊系统的业务。如果该网络系统的所有业务通过总容量来表示，那么在正常情况下，每个VNF实例或每个设备的处理能力＝总容量/设备台数。当其中某一个VNF实例发生故障或者迁移，不能提供服务时，其它具有负荷分担关系的VNF实例来分担该VNF实例的控制项功能，此时剩余的VNF实例的处理能力＝总容量/(设备台数-1)。
在负荷分担关系中，还有一种特殊的关系称为Pool组网，所述Pool组网关系可以理解为，在正常情况下，N个VNF实例或设备组成一个池，池内设备以负荷分担方式工作，一旦某一个VNF实例或设备故障失效时，则由池中其他可用设备接管其业务。
如图5所示，示出了一种在容灾组网下VNF实例的关系示意图，包括上述独立(英文：standalone)的VNF实例，例如VNF1和VNF4，还包括具有主备互助关系的VNF2-1和VNF2-2，具有负荷分担关系的VNF3-1和VNF3-2。其中，具有主备互助关系的VNF2与负荷分担关系的VNF3之间也互相连接。通过对不同的VNF实例建立不同关联关系，起到冗余备份的作用，以保证通信网络的安全性和稳定性。
本申请的技术方案基于上述VNF实例之间的关联关系，将具备所述关联关系的VNF实例所对应的License组成一个资源池，并实现License的共享。在对License策略执行过程中，根据申请的VNF实例的关联关系，确定License是否重新申请或者释放等操作，从而减少了License的浪费。具体地，针对上述图2至图4中不同NFV架构抽象模型，对本申请提供的License发送方法进行详细地说明。
实施例一
本实施例中，应用于图2所示的技术场景，该场景包括PDP、PEP、License catalog、至少一个VNF实例，其中，所述PDP、PEP和License catalog均被配置在第一网络设备中，例如NFVO设备中，对License的发送方法包括如下步骤：
如图7所示，步骤101：第一网络设备获取用于申请License的第一请求消息，所述第 一请求消息包括第一VNF实例的身份标识和所述License所对应的至少一个控制项功能。
其中，所述身份标识用于唯一识别第一VNF实例，并且每个所述VNF实例对应一个身份标识，例如ID。所述第一请求消息用于申请第一网络设备分配License。可选的，所述第一请求消息可以直接有第一VNF实例发起，还可以委托其他网络实体，比如NFVO代替第一VNF实例去申请License，对此本实施例不予限制。
步骤102：根据所述身份标识确定所述第一VNF实例的关联关系。其中，所述关联关系包括：主备互助关系和负荷分担关系。
在一种实现方式中，第一网络设备根据所述身份标识确定第一VNF实例的关联关系的过程包括：第一网络设备根据所述身份标识、网络业务(Network Service，NS)实例和网络业务描述模板(NS Descriptor，NSD)确定所述第一VNF实例的关联关系。
由于NSD是网络设计/规划后的呈现，而VNF实例间的关联关系是网络规划/设计的结果，因此可以通过NSD来确定VNF实例的关联关系。具体地，所述NSD信息模型中包含多个Ns Deployment Flavour(简称：NsDf)，每个NsDf代表着某个网络处理能力下的网络拓扑结构，以及每个VNF/PNF的处理能力，网元间的链路处理能力等等。
进一步地，第一VNF实例的关联关系可以通过下表1表示。
Figure PCTCN2018094699-appb-000001
表1
其中，冗余关系组中包含以下信息：
Figure PCTCN2018094699-appb-000002
表2
在PDP或PEP中可以根据冗余组中，VNF Profile是否属于同一厂家，网元类型是否一致等等条件确定异构的冗余组是否可以共享License。
可选的，在另一种实现方式中，第一网络设备还通过第一VNF实例上报的信息确定第一VNF实例的关联关系。例如，ES/EMS在执行对VNF实例的业务配置过程中，可以获得其他网 元之间的冗余互助关系，因此ES/EMS可以将互助关系的信息上报给OSS，或者通过VNFM上报给NFVO，进而使得第一网络设备能够获取第一VNF实例的关联关系信息。
步骤103：根据所述关联关系和所述至少一个控制项功能确定第一VNF实例所需的License。
具体地，如果所述关联关系为主备互助关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：确定与第一VNF实例具有主备互助关系的第二VNF实例；判断该第二VNF实例是否已经申请了License，且所述License满足共享条件，即可以共享，如果是，则获取所述License，如果否，则需要为第一VNF实例分配新的License。
可选的，如果所述关联关系为负荷分担关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：
根据所述负荷分担关系确定共享策略，所述共享策略包括为每个VNF实例申请一个License，或者为多个VNF实例申请一个共享的License，所述共享的License中包括所述多个VNF实例的所有控制项功能。
如果所述共享策略是为每个VNF实例申请一个License，则根据所述第一VNF实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License确定为所述第一VNF实例所需的License；
如果所述共享策略是为多个VNF实例申请一个共享的License，则从所述共享的License提取所述第一VNF实例所需的至少一个控制项功能，并根据所述提取的至少一个控制项功能生成所述第一VNF实例所需的License。
步骤104：将所述License发送给所述第一VNF实例。
如果步骤103中第一VNF实例所需的License可以共享，则获取该共享的License，例如，从共享资源池中获取，然后将该License分配给第一VNF实例。
其中，所述License包括License文件或者License中的授权信息、标识信息等，如果是License文件，则步骤104中将所述License发送给第一VNF实例的过程为：第一网络设备将所述License文件发送给第一VNF实例。第一VNF实例接收该License文件之后下载，然后再将下载的License进行加载和使用。
另一种实现方式包括，如果所述共享的License是License中的授权信息，则第一网络设备发送License的过程为：先将所述License中的授权信息转换成消息参数，然后再将所述消息参数发送给所述第一VNF实例。在这种情况下，第一网络设备只发送转换的License中的授权信息给第一VNF实例，避免发送或分配一个大的License文件，只发送消息参数节约了传输资源，传输速度快、时间短。
可选的，还包括一种实现方式：所述共享的License为一个License标识信息，第一网络设备将该标识信息发送给第一VNF实例，在第一VNF实例接收到该标识信息后，根据该标识信息的内容到所述第一网络设备中获取对应的License。
本实施例中，第一网络设备具体许可或发送License给第一VNF实例的方式包括但不限于上述三种，还可以包括其它可能的实现方式，本实施例对此不予限定。
本实施例提供的License发送方法，通过VNF实例的身份标识确定该VNF实例的关联关系，由于具有关联关系的VNF实例之间可以共享License，所以可将该共享的License许可给请求的VNF实例，从而实现了不同VNF实例之间的License关联和共享，减少了不必要的License浪费，提高License资源的利用率。
可选的，在上述实施例的步骤102：根据所述身份标识确定第一VNF实例的关联关系之前，该方法还包括：判断所述第一VNF实例是否已经申请了License并且所述License满足共享条件；如果已经申请了License且该申请的License可以共享，则执行所述根据所述身份标识确定第一VNF实例的关联关系的步骤(包括步骤102至步骤104)；如果否，则确定一个新的License，并将所述新的License发送给所述第一VNF实例。
进一步地，第一网络设备确定一个新的License的过程包括：获取所述第一VNF实例所需要的至少一个控制项信息；根据所述至少一个控制项信息确定所述新的License，且所述新的License支持所述第一VNF实例所需要的至少一个控制项功能。具体地，所述第一网络设备可以从License catalog中获取所述新的License，并将该新的License许可给所述第一VNF实例。例如，第一网络设备从License catalog中获取第一VNF实例所需的License，然后将该License发送给请求方的第一VNF实例。
另外，可选的，第一网络设备从License catalog中获取新的License之后，还将该新的License存储在共享资源池中，以备下次第一VNF实例请求时许可使用。
本实施例方式中，通过建立具有关联关系的VNF实例的共享资源池，以实现不同VNF实例之间的License共享，然后再根据确定的共享License许可分配给请求的VNF实例，提高了License资源的利用率。
在本实施例中，所述方法还包括当第一VNF实例发生故障或迁移时，如何使用共享资源池中的License的步骤，具体地，方法还包括：
步骤105：第一网络设备获取用于指示所述第一VNF实例发生故障或迁移的指示信息，所述指示信息中包括所述第一VNF实例的身份标识。
步骤106：根据所述身份标识确定与所述第一VNF实例所对应的License是否满足共享条件，即判断共享资源池中是否包含第一VNF实例所需的可共享的License。
步骤107：如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License，同时刷新共享资源池的关联关系信息。
本实施例提供的方法，当某个VNF实例发生异常，例如故障或迁移时，通过判断该故障或迁移的VNF实例是否申请了License，并根据判决结果对共享资源池中License解除关联关系或者释放，从而保证共享资源池中License的有效性。其中，当判断与发生异常的VNF实例之间存在具有关联关系的其它VNF实例时，不释放该共享的License，而是继续将License提供给具有关联关系的其它VNF实例使用，从而实现了真正的负荷分担，避免重新申请再分配新的License，造成不必要的License浪费。
可选的，本实施例提供的方法还包括：对共享资源池进行扩容。具体地，所述扩容的步骤如下：
第一网络设备获取第二请求消息，所述第二请求消息中包括第三VNF实例的身份标识和第三VNF实例所需的至少一个控制项功能。
根据第三VNF实例的身份标识和所述至少一个控制项功能，判断所述共享资源池中是否能为所述第三VNF实例分配License，即判断当前共享资源池中存储的License的控制项功能是否包括第三VNF实例请求的至少一个控制项功能。
如果不包括，则需要对所述共享资源池进行扩容，一种扩容的方法包括：PEP向PDP发送用于指示所述共享资源池扩容的指示信息，所述指示信息中包括第三VNF实例需要扩容的至少一个控制项功能。PDP接收该指示信息，并根据需要扩容的控制项从License catalog中获取第三VNF实例所需的License，并将该License发送给PEP，PEP接收该License后， 将其添加到共享资源池中，扩容后向所述第三VNF实例发送其所需的License；如果包括，则确定所述第三VNF实例的至少一个控制项功能所对应的License，并将所述License发送给所述第三VNF实例。
本实施例中，通过对超过共享资源池中存储的控制项进行扩容，进而增加了共享资源池的License，提高了共享资源池的利用率，并且当这些共享的License中出现某一个VNF实例发生故障时，能够将其所对应的License分配给具有互助关系的其它VNF实例，实现各实例之间License的共享和分担。
实施例二
本实施例提供的方法可以应用于上述如图3所示的技术场景，PEP与PDP分离的NFV架构，其中，PDP和License catalog可以被配置在OSS或者NFVO中，PEP可以被配置在MANO或者License管理器中，具体地如图7所示，该方法包括：
步骤201：PDP获取VNF2-1实例请求申请License的第一请求消息，所述第一请求消息中包括VNF2-1实例的身份标识和其所需的至少一个控制项功能。
可选的，所述VNF2-1实例可以直接向PDP发起所述第一请求消息，还可以通过其它网元，比如NFVO代替VNF2-1实例去发送申请License的第一请求消息。
其中，当VNF2-1实例化时向PDP申请License，需要说明的是本申请各个实施例中，VNF实例可以根据具体的实施方案在实例化前、后、过程中发送第一请求消息，本申请不予限制。另外，触发VNF2-1实例发起License请求消息的可以是NFVO或者VNFM等等，本申请对此不予限制。
步骤202：PDP接收所述第一请求消息，根据所述VNF2-1实例的身份标识判断其是否已经申请了License且所述申请的License可以共享。
步骤203：如果否，则需要为VNF2-1实例分配一个新的License。
具体过程包括：PDP根据NSD和NS实例确定VNF2-1实例的关联关系。具体地，判断该VNF2-1实例是主备互助关系还是负荷分担关系。如果确定VNF2-2实例与VNF2-1实例之间是主备互助关系，但是VNF2-2实例当前未创建或者根据规则这两个实例不能共享License，则需要为VNF2-1实例分配一个新的License。
进一步地，步骤203中分配新的License的过程包括：PDP获取VNF2-1实例所需要的至少一个控制项功能，根据所述至少一个控制项功能确定支持这些控制项功能服务的License，并从License catalog中获取该License。其中，所述License catalog中预先存储网络中所有控制项功能的License。
步骤204：PDP将携带有所述新的License的消息发送给PEP，所述消息中包括VNF2-1实例的身份标识和/或VNF2-1实例所需的至少一个控制项功能。
步骤205：PDP将所述新的License发送给VNF2-1实例。
其中，发送License的方式包括以下至少两种方式：一种方式是：PDP将License的文件发送给所述VNF2-1实例，或者，另一种方式，PDP将所述License中的授权信息转换成消息参数，然后再将这些消息参数发送给VNF2-1实例。
以上步骤202至步骤205为PDP向VNF2-1实例申请并分配新的License的过程(简称：流程1)，在上述步骤202中判断VNF2-1实例是否已经申请了License，且该License可以共享时，还包括如下流程2的方法步骤。
步骤206：如果VNF2-1实例已经申请了License，且该License可以共享，则根据NSD 和NS实例信息确定VNF2-1实例的关联关系。
PDP根据VNF2-1实例的身份标识、NSD和NS实例信息确定VNF2-1实例与VNF2-2实例之间是主备互助的关系，且VNF2-1实例与VNF2-2实例共享License-2。
步骤207：PDP将携带有VNF2-1实例与VNF2-2实例共享License-2的消息发送给PEP，并通知PEP，VNF2-1实例与VNF2-2实例之间是主备互助关系。
步骤208：PEP接收该信息，并根据License-2建立共享资源池，所述共享资源池中包括VNF2-1实例与VNF2-2实例共享License-2，且这两个实例之间是主备互助关系等信息。如图8所示，为建立的一个共享资源池的示意图。所述共享资源池中所记录的信息包括：1.共享的License-2；2.可共享的实例，VNF2-1实例和VNF2-2实例；3.当前模式，主备互助关系等信息。
步骤209：PEP将所述共享的License-2发送给VNF2-1实例，以使VNF2-1实例根据License-2的内容对控制项功能进行授权控制。
可选的，在步骤209，PEP接收来自PDP的License共享信息之后还向PDP回复一个响应消息。
步骤210：当VNF2-1实例或VNF2-2实例发生异常，例如终结(英文：termination)时，会向PDP发送指示信息，所述指示信息中包括请求方VNF实例的身份标识。其中，所述发生异常包括VNF实例发生故障或者发生迁移。本实施例中以VNF2-1实例发生异常为了进行说明。
步骤211：PDP接收所述指示信息，并判断VNF2-1实例是否已经申请了License且所述申请的License可以共享。
步骤212：如果是，例如VNF2-1实例所对应的License-2可以与VNF2-2实例共享，则不释放该共享的License-2，因为该License-2可以继续被VNF2-2实例使用，但是需要刷新共享资源池的共享记录，比如记录VNF2-1实例发生异常，不再与VNF2-2实例共享License-2，解除两个实例之间的绑定关系。
其中，本申请实施例所述的释放License可以理解为，将该License归还到License catalog中，为后续分配给其他实例使用；或者，将该License归还给供应商，使得与该被释放的License所对应的VNF实例不再使用了。
步骤213：PDP将VNF2-1实例发生异常且不能共享License-2的消息或指令发送给PEP。
步骤214：PEP接收该消息或指令并更新共享资源池中信息。
其中，在上述步骤212中，如果判断VNF2-1实例未共享License，则释放VNF2-1实例的该未共享License，因为释放未共享License之后不会影响其它实例使用License，并且节约一定存储空间。
可选的，在VNF2-1实例发生异常时，可以对该VNF2-1实例进行重建，例如在healing阶段，重建VNF2-1实例之后可执行上述步骤207至步骤210(即流程2)的流程，以便获得新的License，同时License资源池刷新该新的License共享信息。
本实施例提供了一种在主备互助关系下的License发送方法，通过建立共享资源池，使得当一个VNF实例发生异常时，与其具有主备互助关系的另一个VNF实例可以继续使用该异常的VNF实例的License，实现了VNF实例间License的最大程度共享，减少不必要的License浪费。
实施例三
本实施例提供的方法可以应用于PEP与PDP分离的NFV架构中，其中，PDP和License  catalog可以被配置在同一个网元中，例如OSS或者NFVO中，PEP可以被配置在License管理器中，例如MANO。本实施例与实施例二的区别在于，本实施例是针对负荷分担关系的VNF实例之间License的关联和共享，具体地如图9所示，该方法包括：
步骤301：PDP获取第一请求消息，所述第一请求消息中包括VNF3-1实例的身份标识和VNF3-1实例所需的至少一个控制项功能。
可选的，PDP可通过NFVO申请License获得所述第一请求消息。
步骤302：PDP接收所述第一请求消息，根据所述VNF3-1的身份标识、NSD、NS实例等信息判断其是否具备负荷分担关系。
步骤303：如果是负荷分担关系，则判断VNF3-1实例是否是首次申请License。
步骤304：如果是首次申请，则PDP向License catalog发送VNF3-1实例所需的控制项功能的信息，然后PDP从License catalog中获取该VNF3-1实例所需的License，例如License-3。
可选的，PDP将获取的License-3以及VNF3-1实例的身份标识，关联关系等消息发送给PEP，以使PEP能够根据这些信息建立License-3的共享资源池。
步骤305：PDP将所述License-3发送给VNF3-1实例。
步骤306：如果VNF3-1实例不是首次申请License，则根据所述负荷分担关系确定共享策略，即确定VNF3-1实例采用哪种共享方式来共享License。
具体地，本实施例中提供以下两种共享方式。
方式一：预先每个VNF实例申请自己的License，PDP根据每个VNF实例所需的控制项功能在License catalog中为每个VNF实例分配一个License，并且将这些License都存储在共享资源池中。
方式二：为所有每个VNF实例所需的控制项功能建立一个大的License，该License用于控制所述多个VNF实例的所有控制项功能，且为多个VNF实例所共享。
如果是采用方式一实现License的共享，则执行步骤307a：则根据VNF3-1实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License确定为VNF3-1实例所需的License。所述相匹配是指所述共享资源池中预存的License，以及该License所具有的控制项功能等信息与所述VNF3-1实例所需的License相同，或者VNF3-1实例所需的License即共享资源池中预先为其申请并存储的License。
本实施例中，PDP结合NSD和NS实例信息，确定VNF3-1实例和VNF3-2实例之间是负荷分担关系，且确定VNF3-1实例所需的License为共享资源池中的License-3，VNF3-2实例所需的License是共享资源池中的License-3’，并将VNF3-1实例和VNF3-2实例共享方式为：License-3和License-3’等信息发送给PEP，以供PEP建立License的共享资源池。
如果是采用方式二实现License的共享，则执行步骤307b：不需申请新的License，要从所述共享的License提取VNF3-1实例所需的至少一个控制项功能，并将这些提取的控制项功能生成对应于VNF3-1实例所需的License，再将该License许可给VNF3-1实例使用。
例如，方式二中所述共享的License包含100个控制项功能，VNF3-1实例申请的License中仅包括10个控制项功能，且这10个控制项功能均被包含在共享的100个控制项功能之中，则从这100个控制项功能中提取VNF3-1实例所需的10个控制项功能，并将这10个控制项功能生成一个License，并将该License发送给VNF3-1实例。
步骤308：建立License-3和/或License-3’的共享资源池，如图10和11所示，VNF3-1实例和VNF3-2实例之间为负荷分担关系，且共享License-3，或者License-3/3’。
步骤309：将所述VNF3-1实例所需的License发送给VNF3-1实例。具体的许可方式与前述实施例一和实施例二的方式相同，本实施例不再赘述。
可选的，上述方法还包括：PEP向PDP回复License共享的响应消息，使得在后续过程中，PEP能够基于License共享策略进行授权控制。
此时对于方式一和方式二的授权控制方法上，可以略有差异：例如，对于方式一：资源池内的各个子License具有优先申请的使用权，即先申请License的VNF实例先获取使用许可。当有多个VNF实例都申请License时，这些申请的License的总量可能会超过共享资源池中所存储的License，此时，第一网络设备可以根据请求消息确定申请超过共享资源池的License超出量，以及其对应的VNF实例，然后再根据License超出量对共享资源池扩容。例如PDP根据每个VNF实例的请求消息中所包括的控制项功能，确定是否对共享资源池进行扩容。
对于方式二：可以以License为整体对共享资源池中的License进行管理和扩容。由于所有VNF实例都共享一个License，所以，当申请的License需求量超过资源池中共享的License容量时，增加该共享License的容量，即对该资源池继续扩容，以便满足多个VNF实例的控制项需求。
其中，扩容的方式可以从License catalog中获得新的License，以增加资源池的容量；或者，还可以通过其它网元获取新的License进行扩容，本实施例对此不予限制。
同理地，当具有负荷分担关系的多个VNF实例请求License时，可以采用上述步骤306至步骤309(流程2)的方式进行处理。
另外，上述方法还包括：步骤310：当VNF3-1实例或VNF3-2实例发生异常时，例如发送故障或迁移时，则向PDP申请释放License。具体为VNF3-1实例向PDP发送指示信息，用于指示对其释放License，其中，所述指示信息中包括VNF3-1实例的身份标识。
步骤311：PDP接收该指示信息，并确定该VNF3-1实例与其他实例是否具有负荷分担关系，以及确定是否对VNF3-1实例的License做释放或者更新。具体地，可以根据共享资源池的创建方式做不同的决策：
一种决策方式针对方式一的License共享：PDP根据策略或业务决定是否释放该VNF3-1实例申请的License，同时刷新共享信息。另一种决策方式是针对方式二的License共享：不释放License，仅刷新的共享信息。
步骤312：PDP将刷新后的共享信息通过消息发送给PEP，以告知PEP VNF3-1实例发生异常，共享关系发生变化。例如，当VNF3-1实例故障时，VNF3-2实例与VNF3-1实例不再共用License-3，解除VNF3-1实例的绑定关系。
步骤313：PEP接收该消息并更新资源池中的关联信息。
可选的，当某一VNF实例发生异常，并对其进行治疗重建时，可执行本实施例的步骤306至步骤309(流程2)的过程，但是如果在步骤311中采用方式一，具备共享条件而未释放某个License时，则可以不再申请新和下发新的License，而是直接绑定该发生异常的VNF实例的原来License并刷新资源池信息。
本实施例提供的方法，解决了负荷分担模式下License的自动管理问题，实现互助实例间的License最大程度的共享，减少不必要的License浪费；当互助的License异常时，License不会被释放，而是分配给具有关联关系的其它实例使用，实现真正的负荷分担。
另外，本实施例中PEP根据PDP给定的共享和互助关系，建立License共享资源池，实现了以池为单位进行管理的License，在互助的实例间互享资源。并根据资源池的方式不同， 对业务超过资源池中License的总容量时，对共享资源池进行扩容，以满足多个VNF实例的授权控制需求，提高了共享资源池的利用率。
需要说明的是，在上述本实施例二和实施例三中，License catalog也可以配置在PEP中或者其它License管理器中，用于对未创建或者在资源池中未存储License的VNF实例分配新的License。具体地将catalog配置PEP还是PDP中，可根据技术方案自行配置，本申请对此不予限制。
本申请还提供了一种license的发送方法，用于为所有具有关联关系的VNF实例建立共享的license，并实现共享。该方法可以由策略执行点PEP执行，或者由其它的网络设备。具体地，如图12所示，该方法包括如图步骤：
步骤401：PEP获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例所需的至少一个控制项功能，另外，第一消息中还可以包括第一VNF实例的身份标识、关联关系等信息。其中，所述管理关系包括主备互助关系和负荷分担关系。
步骤402：判断共享资源池中是否包含所述第一VNF实例所需的至少一个控制项功能。
步骤403：如果包含，则确定所述至少一个控制项功能所对应的License，并将所述License发送给所述第一VNF实例。
上述步骤402中判断如果共享资源池中不包含第一VNF实例所需至少一个控制项功能，则生成用于指示所述共享资源池扩容的指示信息，并将所述指示信息发送给所述PDP，以获取需要扩容的License。
进一步地，对所述共享资源池扩容具体包括：PEP生成用于指示所述共享资源池扩容的指示信息，所述指示信息中包括所述第一VNF实例所需的至少一个控制项功能，并将所述指示信息发送给所述PDP；接收来自所述PDP的License，所述License是由所述PDP根据所述第一VNF实例所需的至少一个控制项功能所确定；将所述来自PDP的License添加到所述共享资源池中。
其中，所述PDP在接收指示信息之后，可以从License catalog中获取第一VNF实例所需的License，还可以从其它网元设备中获取License，本实施例对此不予限制。
进一步地，所述方法还包括：建立所述共享资源池。具体地，建立所述共享资源池的方法包括：获取来自所述PDP的至少一个第二消息，每个所述第二消息中包含一个VNF实例的License，每个License对应至少一个控制项功能，统计所有所述第二消息中的License；将统计的所有第二消息中的License组成所述共享资源池；或者，将每个所述第二消息中的License合并生成一个共享的License，并建立包括所述共享的License的共享资源池。
可选的，本实施例中还包括：在某个VNF实例发生异常时，是否对共享资源池中的License进行释放或缩容操作。具体地过程如下：在所述PDP获取用于指示所述第一VNF实例发生故障或迁移的指示信息的情况下，确定与第一VNF实例所对应的License是否满足共享条件；如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放第一VNF实例所对应的License，并刷新第一VNF实例的关联关系信息，例如解除第一VNF实例与其他VNF实例的关联关系。
本实施例提供的方法，通过为具有关联关系的VNF实例建立License的共享资源池，实现了VNF实例间最大程度的License共享，减少了不必要的License浪费。
相对于上面的方法实施例，本申请实施例还提供了相应的装置实施例。
参见图13，为本申请实施例提供的一种License的发送装置的结构示意图。该装置用于 执行如图6、图7和图9所示的License的发送方法。该装置可以包括获取单元1301、处理模块1302和发送单元1303。
其中，获取单元1301用于获取用于申请License的第一请求消息，所述第一请求消息包括第一VNF实例的身份标识和所述License所对应的至少一个控制项功能。
处理单元1302用于根据所述身份标识确定所述第一VNF实例的关联关系，根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License。
发送单元1303用于将所述License发送给所述第一VNF实例。
可选的，在本实施例的一种具体实现方式中，所述处理单元1302具体用于在所述关联关系为主备互助关系的情况下，确定与所述第一VNF实例具有主备互助关系的第二VNF实例，判断所述第二VNF实例是否已经申请了License，且所述License满足共享条件。
所述获取单元1301还用于在所述具有主备互助关系的VNF实例已经申请了License，且所述License满足共享条件的情况下，获取所述License。
可选的，在本实施例的一种具体实现方式中，所述处理单元1302具体用于在所述关联关系为负荷分担关系的情况下，根据所述负荷分担关系确定共享策略，所述共享策略包括为每个VNF实例申请一个License，或者为多个VNF实例申请一个共享的License，所述共享的License中包括所述多个VNF实例的所有控制项功能。
所述处理单元1302具体还用于如果所述共享策略是为每个VNF实例申请一个License，则根据所述第一VNF实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License作为所述第一VNF实例所需的License；如果所述共享策略是为多个VNF实例申请一个共享的License，则从所述共享的License提取所述第一VNF实例所需的至少一个控制项功能，并根据所述提取的至少一个控制项功能生成所述第一VNF实例所需的License。
可选的，在本实施例的一种具体实现方式中，所述处理单元1302具体用于根据所述身份标识、NS实例和NSD确定所述第一VNF实例的关联关系。
可选的，在本实施例的一种具体实现方式中，License包括License文件或License中的授权信息。
所述发送单元1303具体用于将所述License文件发送给所述第一VNF实例，或者，在所述License中的授权信息转换成消息参数之后，将所述消息参数发送给所述第一VNF实例。
可选的，在本实施例的一种具体实现方式中，所述获取单元1301还用于获取用于指示所述第一VNF实例发生故障或迁移的指示信息，所述指示信息中包括所述第一VNF实例的身份标识。
所述处理单元1302还用于根据所述身份标识确定与所述第一VNF实例所对应的License是否满足共享条件，如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License。
可选的，在本实施例的一种具体实现方式中，所述装置还包括：存储单元，用于存储所述License和其它VNF实例的License。
所述处理单元1302还用于根据获取的License和License的相关信息建立共享资源池，所述共享资源池中包括所述第一VNF实例的关联关系；以及，在获取所述第一VNF实例的发生故障或迁移的指示信息的情况下，刷新所述共享资源池中记录的所述第一VNF实例的关联关系信息。
可选的，在本实施例的一种具体实现方式中，所述处理单元1302还用于根据所述第一请 求消息中License所对应的至少一个控制项功能，判断所述共享资源池中是否能为所述第一VNF实例分配License；如果否，则对所述共享资源池进行扩容，扩容后向所述第一VNF实例分配所述License；如果是，则为第一VNF实例分配所述License。
其中，所述扩容的方法可以通过License catalog中获得新的License，再发送给第一VNF实例。
本实施例提供的License共享装置，通过VNF实例的身份标识确定该VNF实例的关联关系，由于具有关联关系的VNF实例之间可以共享License，所以可将该共享的License许可给请求的VNF实例，从而实现了不同VNF实例之间的License关联和共享，减少了不必要的License浪费，提高License资源的利用率。
另外，当某个VNF实例发生异常，例如故障或迁移时，通过判断该故障或迁移的VNF实例是否申请了License，并根据判决结果对共享资源池中License解除关联关系或者释放，从而保证共享资源池中License的有效性。
可选的，在本实施例的一种具体实现方式中，所述获取单元1301用于获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例的身份标识、所述第一VNF实例的关联关系信息和所述第一VNF实例所对应的License。
获取单元1301用于获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例所需的至少一个控制项功能。
处理单元1302用于判断共享资源池中是否包含所述第一VNF实例所需的至少一个控制项功能，如果包含，则确定所述至少一个控制项功能所对应的License。
发送单元1303用于在包含所述至少一个控制项功能的情况下，将所述License发送给所述第一VNF实例。
可选的，在本实施例的一种具体实现方式中，处理单元1302还用于在所述共享资源池中不包含所述至少一个控制项功能的情况下，对所述共享资源池进行扩容。
进一步地，所述处理单元1302具体用于生成用于指示所述共享资源池扩容的指示信息，所述指示信息中包括所述第一VNF实例所需的至少一个控制项功能；发送单元1303还用于将所述指示信息发送给所述PDP；获取单元1301还用于接收来自所述PDP的License，所述License是由所述PDP根据所述第一VNF实例所需的至少一个控制项功能所确定；处理单元1302还用于将所述来自PDP的License添加到所述共享资源池中。
可选的，在本实施例的一种具体实现方式中，处理单元1302还用于建立所述共享资源池，具体地，所述获取单元1301还用于获取来自所述PDP的至少一个第二消息，每个所述第二消息中包含一个VNF实例的License；所述处理单元1302具体用于统计所有所述第二消息中的License，将统计的所有所述第二消息中的License组成所述共享资源池；或者，将每个所述第二消息中的License合并生成一个共享的License，并建立包括所述共享的License的所述共享资源池。
可选的，在本实施例的一种具体实现方式中，所述获取单元1301还用于获取第二请求消息，所述第二请求消息中包括第三VNF实例的身份标识和所述第三VNF实例所需的至少一个控制项功能。
所述处理单元1302还用于根据所述第三VNF实例的身份标识和所述至少一个控制项功能，判断所述共享资源池中是否能为所述第三VNF实例分配License；如果否，则对所述共享资源池进行扩容；如果是，则确定所述第三VNF实例的至少一个控制项功能所对应的License。
所述发送单元1303还用于扩容后向所述第三VNF实例发送其所需的License，或者，在 确定所述第三VNF实例的License的情况下，将所述License发送给所述第三VNF实例。
在具体实现中，本申请还提供了一种网络设备，如图14所示，为本实施例提供的一种网络设备的结构示意图。所述网络设备可以是前述任意实施例中的License的共享装置，用于实现前述实施例中的方法步骤。
其中，所述网络设备可以由收发器141、处理器142和存储器143等元件组成。
处理器142为网络设备的控制中心，利用各种接口和线路连接整个网络设备的各个部分，通过运行或执行存储在存储器内的软件程序和/或模块，以及调用存储在存储器143内的数据，以执行网络设备的各种功能和/或处理数据。所述处理器142可以是中央处理器(central processing unit，简称CPU)，网络处理器(network processor，简称NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，简称ASIC)，可编程逻辑器件(programmable logic device，简称PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，简称CPLD)，现场可编程逻辑门阵列(field-programmable gate array，简称FPGA)，通用阵列逻辑(generic array logic,简称GAL)或其任意组合。
所述存储器143可以包括易失性存储器(volatile memory)，例如随机存取内存(random access memory，简称RAM)；还可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，简称HDD)或固态硬盘(solid-state drive，简称SSD)；所述存储器还可以包括上述种类的存储器的组合。所述存储器中可以存储有程序或代码，网络设备中的处理器142通过执行所述程序或代码可以实现所述网络设备的功能。
所述收发器141可以用于接收或发送数据，所述收发器可以在所述处理器的控制下向终端设备或其他网络设备发送数据；所述收发器在所述处理器的控制下接收终端设备或其他网络设备发送的数据。
在本发明实施例中，收发器141可以用于实现上述各个实施例中的一种License的发送方法步骤。结合上述图13所示，所述获取单元1301和发送单元1303所要实现的功能可以由所述网络设备的收发器141实现，或者由处理器142控制的收发器141实现；所述处理单元1302所要实现的功能则可以由所述处理器142实现，存储器143用于存储License。
具体实现中，本发明还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可包括本发明提供的License的发送方法的各实施例中的部分或全部步骤。所述的存储介质可为磁碟、光盘、只读存储记忆体(英文：read-only memory，简称：ROM)或随机存储记忆体(英文：random access memory，简称：RAM)等。
本领域的技术人员可以清楚地了解到本发明实施例中的技术可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本发明实施例中的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例或者实施例的某些部分所述的方法。
本说明书中各个实施例之间相同相似的部分互相参见即可。尤其，对于上述各实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例中的说明即可。
以上所述的本发明实施方式并不构成对本发明保护范围的限定。

Claims (24)

  1. 一种许可证License的发送方法，其特征在于，所述方法包括：
    获取用于申请License的第一请求消息，所述第一请求消息包括第一虚拟化网络功能VNF实例的身份标识和所述License所对应的至少一个控制项功能；
    根据所述身份标识确定所述第一VNF实例的关联关系；
    根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License；
    将所述License发送给所述第一VNF实例。
  2. 根据权利要求1所述的方法，其特征在于，所述关联关系包括主备互助关系，
    如果所述关联关系为主备互助关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：
    确定与所述第一VNF实例具有主备互助关系的第二VNF实例；
    判断所述第二VNF实例是否已经申请了License，且所述License满足共享条件；如果是，则获取所述License。
  3. 根据权利要求1所述的方法，其特征在于，所述关联关系包括负荷分担关系，
    如果所述关联关系为负荷分担关系，则根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License，包括：
    根据所述负荷分担关系确定共享策略，所述共享策略包括为每个VNF实例申请一个License，或者为多个VNF实例申请一个共享的License，所述共享的License中包括所述多个VNF实例的所有控制项功能；
    如果所述共享策略是为每个VNF实例申请一个License，则根据所述第一VNF实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License作为所述第一VNF实例所需的License；
    如果所述共享策略是为多个VNF实例申请一个共享的License，则从所述共享的License提取所述第一VNF实例所需的至少一个控制项功能，并根据所述提取的至少一个控制项功能生成所述第一VNF实例所需的License。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，根据所述身份标识确定所述第一VNF实例的关联关系，包括：
    根据所述身份标识、网络业务NS实例和网络业务描述模板NSD确定所述第一VNF实例的关联关系。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述License包括License文件或License中的授权信息，
    将所述License发送给所述第一VNF实例，包括：
    将所述License文件发送给所述第一VNF实例，或者，在所述License中的授权信息转换成消息参数之后，将所述消息参数发送给所述第一VNF实例。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    获取用于指示所述第一VNF实例发生故障或迁移的指示信息，所述指示信息中包括所述第一VNF实例的身份标识；
    根据所述身份标识确定与所述第一VNF实例所对应的License是否满足共享条件；
    如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    存储所述License；
    根据所述License建立共享资源池，所述共享资源池中包括所述第一VNF实例的关联关系；
    在获取所述第一VNF实例的发生故障或迁移的指示信息的情况下，刷新所述共享资源池中记录的所述第一VNF实例的关联关系信息。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    获取第二请求消息，所述第二请求消息中包括第三VNF实例的身份标识和所述第三VNF实例所需的至少一个控制项功能；
    根据所述第三VNF实例的身份标识和所述至少一个控制项功能，判断所述共享资源池中是否能为所述第三VNF实例分配License；
    如果否，则对所述共享资源池进行扩容，扩容后向所述第三VNF实例发送其所需的License；如果是，则确定所述第三VNF实例的至少一个控制项功能所对应的License，并将所述License发送给所述第三VNF实例。
  9. 一种l icense的发送方法，其特征在于，所述方法包括：
    获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例所需的至少一个控制项功能；
    判断共享资源池中是否包含所述第一VNF实例所需的至少一个控制项功能；
    如果包含，则确定所述至少一个控制项功能所对应的License，并将所述License发送给所述第一VNF实例。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：如果不包含，则对所述共享资源池进行扩容；
    其中，所述对所述共享资源池进行扩容，包括：
    生成用于指示所述共享资源池扩容的指示信息，所述指示信息中包括所述第一VNF实例所需的至少一个控制项功能；
    将所述指示信息发送给所述PDP；
    接收来自所述PDP的License，所述License是由所述PDP根据所述第一VNF实例所需的至少一个控制项功能所确定；
    将所述来自PDP的License添加到所述共享资源池中。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：建立所述共享资源池，
    所述建立所述共享资源池，包括：
    获取来自所述PDP的至少一个第二消息，每个所述第二消息中包含一个VNF实例的License；
    统计所有所述第二消息中的License；
    将统计的所有所述第二消息中的License组成所述共享资源池；或者，将所有所述第二消息中的License合并生成一个共享的License，并建立包括所述共享的License的共享资源池。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一VNF实例发生故障或迁移的情况下，判断所述共享资源池中与所述第一VNF实例所对应的License是否满足共享条件；
    如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License，并刷新所述第一VNF实例的关联关系信息。
  13. 一种License的发送装置，其特征在于，所述装置包括：
    获取单元，用于获取用于申请License的第一请求消息，所述第一请求消息包括第一VNF实例的身份标识和所述License所对应的至少一个控制项功能；
    处理单元，用于根据所述身份标识确定所述第一VNF实例的关联关系，根据所述关联关系和所述至少一个控制项功能确定所述第一VNF实例所需的License；
    发送单元，用于将所述License发送给所述第一VNF实例。
  14. 根据权利要求13所述的装置，其特征在于，
    所述处理单元，具体用于在所述关联关系为主备互助关系的情况下，确定与所述第一VNF实例具有主备互助关系的第二VNF实例，判断所述第二VNF实例是否已经申请了License，且所述License满足共享条件；
    所述获取单元，还用于在所述第二VNF实例已经申请了License，且所述License满足共享条件的情况下，获取所述License。
  15. 根据权利要求13所述的装置，其特征在于，
    所述处理单元，具体用于在所述关联关系为负荷分担关系的情况下，根据所述负荷分担关系确定共享策略，所述共享策略包括为每个VNF实例申请一个License，或者为多个VNF实例申请一个共享的License，所述共享的License中包括所述多个VNF实例的所有控制项功能；
    所述处理单元，具体还用于如果所述共享策略是为每个VNF实例申请一个License，则根据所述第一VNF实例的身份标识和所述至少一个控制项功能查找与其相匹配的License，并将所述相匹配的License作为所述第一VNF实例所需的License；如果所述共享策略是为多个VNF实例申请一个共享的License，则从所述共享的License提取所述第一VNF实例所需的至少一个控制项功能，并根据所述提取的至少一个控制项功能生成所述第一VNF实例所需的License。
  16. 根据权利要求13-15任一项所述的装置，其特征在于，
    所述处理单元，具体用于根据所述身份标识、网络业务NS实例和网络业务描述模板NSD确定所述第一VNF实例的关联关系。
  17. 根据权利要求13-15任一项所述的装置，其特征在于，所述License包括License文件或License中的授权信息，
    所述发送单元，具体用于将所述License文件发送给所述第一VNF实例，或者，在所述License中的授权信息转换成消息参数之后，将所述消息参数发送给所述第一VNF实例。
  18. 根据权利要求13-17任一项所述的装置，其特征在于，
    所述获取单元，还用于获取用于指示所述第一VNF实例发生故障或迁移的指示信息，所述指示信息中包括所述第一VNF实例的身份标识；
    所述处理单元，还用于根据所述身份标识确定与所述第一VNF实例所对应的License是否满足共享条件，如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License。
  19. 根据权利要求18所述的装置，其特征在于，所述装置还包括：
    存储单元，用于存储所述License；
    所述处理单元，还用于根据所述License建立共享资源池，所述共享资源池中包括所述 第一VNF实例的关联关系；以及，在获取所述第一VNF实例的发生故障或迁移的指示信息的情况下，刷新所述共享资源池中记录的所述第一VNF实例的关联关系信息。
  20. 根据权利要求19所述的装置，其特征在于，
    所述获取单元，还用于获取第二请求消息，所述第二请求消息中包括第三VNF实例的身份标识和所述第三VNF实例所需的至少一个控制项功能；
    所述处理单元，还用于根据所述第三VNF实例的身份标识和所述至少一个控制项功能，判断所述共享资源池中是否能为所述第三VNF实例分配License；如果否，则对所述共享资源池进行扩容；如果是，则确定所述第三VNF实例的至少一个控制项功能所对应的License；
    所述发送单元，还用于扩容后向所述第三VNF实例发送其所需的License，或者，在确定所述第三VNF实例的License的情况下，将所述License发送给所述第三VNF实例。
  21. 一种l icense的发送装置，其特征在于，所述装置包括：
    获取单元，用于获取来自策略执行点PDP的第一消息，所述第一消息中包括第一VNF实例所需的至少一个控制项功能；
    处理单元，用于判断共享资源池中是否包含所述第一VNF实例所需的至少一个控制项功能，如果包含，则确定所述至少一个控制项功能所对应的License；
    发送单元，用于将所述License发送给所述第一VNF实例。
  22. 根据权利要求21所述的装置，其特征在于，所述处理单元，还用于在所述共享资源池中不包含所述至少一个控制项功能的情况下，对所述共享资源池进行扩容；
    所述处理单元，具体用于生成用于指示所述共享资源池扩容的指示信息，所述指示信息中包括所述第一VNF实例所需的至少一个控制项功能；
    所述发送单元，还用于将所述指示信息发送给所述PDP；
    所述获取单元，还用于接收来自所述PDP的License，所述License是由所述PDP根据所述第一VNF实例所需的至少一个控制项功能所确定；
    所述处理单元，还用于将所述来自PDP的License添加到所述共享资源池中。
  23. 根据权利要求21所述的装置，其特征在于，所述处理单元，还用于建立所述共享资源池，
    所述获取单元，还用于获取来自所述PDP的至少一个第二消息，每个所述第二消息中包含一个VNF实例的License；
    所述处理单元，具体用于统计所有所述第二消息中的License，将统计的所有所述第二消息中的License组成所述共享资源池；或者，将每个所述第二消息中的License合并生成一个共享的License，并建立包括所述共享的License的所述共享资源池。
  24. 根据权利要求21-23任一项所述的装置，其特征在于，
    所述处理单元，还用于在所述第一VNF实例发生故障或迁移的情况下，判断所述共享资源池中与所述第一VNF实例所对应的License是否满足共享条件；如果满足所述共享条件，则不释放所述第一VNF实例所对应的License；否则，释放所述第一VNF实例所对应的License，并刷新所述第一VNF实例的关联关系信息。
PCT/CN2018/094699 2017-07-14 2018-07-05 一种License的发送方法和装置 WO2019011180A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710574901.5 2017-07-14
CN201710574901.5A CN109257201B (zh) 2017-07-14 2017-07-14 一种License的发送方法和装置

Publications (1)

Publication Number Publication Date
WO2019011180A1 true WO2019011180A1 (zh) 2019-01-17

Family

ID=65001041

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094699 WO2019011180A1 (zh) 2017-07-14 2018-07-05 一种License的发送方法和装置

Country Status (2)

Country Link
CN (1) CN109257201B (zh)
WO (1) WO2019011180A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112925604B (zh) * 2019-11-20 2024-04-19 北京华耀科技有限公司 一种虚拟化管理平台及实现方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119317A (zh) * 2007-08-31 2008-02-06 华为技术有限公司 分配许可的方法、设备及系统
CN104134122A (zh) * 2014-07-30 2014-11-05 华为技术有限公司 一种许可证申请方法及装置
US20160057234A1 (en) * 2014-08-20 2016-02-25 At&T Intellectual Property I, L.P. Service Compiler Component and Service Controller for Open Systems Interconnection Layer 4 Through Layer 7 Services in a Cloud Computing System
CN105450601A (zh) * 2014-08-19 2016-03-30 华为技术有限公司 共享许可证的方法和装置
US20160323200A1 (en) * 2015-05-01 2016-11-03 Futurewei Technologies, Inc. System and Method for Resource Management

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119317A (zh) * 2007-08-31 2008-02-06 华为技术有限公司 分配许可的方法、设备及系统
CN104134122A (zh) * 2014-07-30 2014-11-05 华为技术有限公司 一种许可证申请方法及装置
CN105450601A (zh) * 2014-08-19 2016-03-30 华为技术有限公司 共享许可证的方法和装置
US20160057234A1 (en) * 2014-08-20 2016-02-25 At&T Intellectual Property I, L.P. Service Compiler Component and Service Controller for Open Systems Interconnection Layer 4 Through Layer 7 Services in a Cloud Computing System
US20160323200A1 (en) * 2015-05-01 2016-11-03 Futurewei Technologies, Inc. System and Method for Resource Management

Also Published As

Publication number Publication date
CN109257201A (zh) 2019-01-22
CN109257201B (zh) 2021-10-19

Similar Documents

Publication Publication Date Title
US10701139B2 (en) Life cycle management method and apparatus
US11960915B2 (en) Method and apparatus for creating virtual machine based on parameter information of a virtual network interface card
US12020055B2 (en) VNF service instantiation method and apparatus
JP7074880B2 (ja) ネットワーク・スライスの展開方法および装置
EP3800926B1 (en) Alarm method and device
US20180145889A1 (en) Life Cycle Management Method and Device for Network Service
EP3413511B1 (en) Vnfm determining method and network function virtualization orchestrator
CN103607430A (zh) 一种网络处理的方法和系统及网络控制中心
EP3806395B1 (en) Virtual network function (vnf) deployment method and apparatus
EP3629160A1 (en) Method and device for managing vnf instantiation
JP7377965B2 (ja) ネットワークリソース管理方法、システム、ネットワーク機器と可読記憶媒体
EP4177742A1 (en) Multitenancy management method and apparatus
US20240118935A1 (en) Pod deployment method and apparatus
WO2017070954A1 (zh) 资源预留的方法及vnfm、vim、nfvo
WO2019011180A1 (zh) 一种License的发送方法和装置
CN109933959B (zh) 一种许可证控制方法及相关设备
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
US12028225B2 (en) Scaling method and apparatus
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv系统
US20230362065A1 (en) Scaling Method and Apparatus
JP2024524398A (ja) コンテナクラスタのストレージリソースを管理するための方法および装置、ならびにシステム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18831036

Country of ref document: EP

Kind code of ref document: A1