[go: up one dir, main page]

WO2018166398A1 - Système de gestion de licence dans un réseau nfv - Google Patents

Système de gestion de licence dans un réseau nfv Download PDF

Info

Publication number
WO2018166398A1
WO2018166398A1 PCT/CN2018/078403 CN2018078403W WO2018166398A1 WO 2018166398 A1 WO2018166398 A1 WO 2018166398A1 CN 2018078403 W CN2018078403 W CN 2018078403W WO 2018166398 A1 WO2018166398 A1 WO 2018166398A1
Authority
WO
WIPO (PCT)
Prior art keywords
license
management server
nfvo
descriptor
license management
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/078403
Other languages
English (en)
Chinese (zh)
Inventor
冯爱娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2018166398A1 publication Critical patent/WO2018166398A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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]
    • 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
    • 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/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
    • H04L9/3268—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Definitions

  • the present invention relates to the field of NFV (Network Functions Virtualization), and more particularly to a license management system in an NFV network.
  • NFV Network Functions Virtualization
  • a license is a way of selling software. It authorizes the use of the software according to its characteristics, version, capacity, and usage time. The customer obtains the corresponding rights and license authorization certificates promised by the software provider.
  • the network element deployed in the communication carrier is generally provided by the corresponding software provider.
  • the current license loading process in the normal NE deployment process is:
  • License application obtains the license-related parameter information from the carrier, logs in to the software provider license website, enters the NE information, and installs the ESN of the NE (the device serial number, identifies the carrier's device), and the NE specifications.
  • the license website generates a license file based on the information, such as the number of users and service processing capabilities.
  • License download The device software installer downloads the license file from the software provider license website.
  • the license is loaded.
  • the device installer loads the downloaded license file into the device and activates the license.
  • NFV Network Functions Virtualization
  • Virtualization technology network equipment can be based on general-purpose hardware, such as standards-based high-capacity Server, storage and Ethernet.
  • Applications from different software providers are deployed in software on a unified cloud virtualization infrastructure. Cost, increase efficiency, and increase agility.
  • the NFV ISG defines a reference framework, as shown in Figure 1.
  • the responsibilities of each entity are as follows:
  • OSS in addition to the traditional management functions, interacts with the Orchestrator for the operation and maintenance of the network for the virtualization application.
  • NFVO NFV Orchestrator, NFV orchestrator
  • lifecycle management such as deployment/expansion/reduction/downline
  • NS Network Service, such as IMS service
  • NFVI NFV Infrastructure, NFV infrastructure layer
  • resource scheduling policy management and other functions
  • NFVO according to NSD (NS Descriptor, NS information model description template) to decompose each VNF (Virtual Network Function, virtualized network function) Requirements, with VNFM (VNF Manager, VNF Manager) to achieve VNF deployment.
  • VNFM Virtual Network Function, virtualized network function
  • VNFM VNF Manager, VNF Manager
  • the main function is to realize the life cycle management of VNF, such as deployment/expansion/reduction/downline and other automation capabilities; VNFM decomposes virtual machines according to template and VNF capacity requirements. The need for virtual resources, in conjunction with Orchestrator, VIM (Virtualized Infrastructure Manager) to complete the instantiation of VNF.
  • VIM Virtualized Infrastructure Manager
  • VIM the main function is to realize the management and monitoring of the entire infrastructure layer resources (including computing, storage, network resources).
  • the NFV network enables the network element function to run on various general-purpose hardware, and automates the network element deployment process through the MANO system. Operators can quickly and dynamically expand and shrink capacity according to service needs.
  • the deployment of the network element also requires the software license provided by the software provider of the network element.
  • the traditional license management method is adopted.
  • the software service provider's customer service personnel must manually download the relevant license file from the software provider's license website.
  • the activation of the VNF network element is implemented on the corresponding VNF network element.
  • the traditional license management method is not flexible enough to implement automatic license management. Therefore, in the NFV network, a more flexible and automatic license management mode is required to improve the efficiency of management and use of the license.
  • the present invention provides a method and system for managing a license in an NFV network, which enables the operator to manage and use the license more flexibly, and improve the efficiency of the license to meet the flexible elastic scalability and resources of the NFV network. Provisioning.
  • the present application provides a system for managing a license in an NFV network, which includes a Global License Manager 201 (Global LM), which is a software provider's license delivery system, which may also be referred to herein as a first license management server. Also included is a Local License Manager 202 (Local LM), which is a node deployed in the NFV network and connected to the Global LM for performing license management in the NFV network, and may also be referred to as a second license management server herein.
  • Local LM can be connected to Global LM of multiple software providers, or it can be a dedicated device that is specifically responsible for interfacing with a software provider's Global LM. In this case, the Local LM is generally also connected to it.
  • Local LM can be used as a license management agent of Global LM in the carrier network to implement distribution and control of licenses within the carrier network. Since Global LM and Local LM are now provided by the same software provider, the communication security and information mutual trust between the two network elements is higher.
  • the Global LM is used to generate a license information description template (License Descriptor), and the license Descriptor is sent to the NFVO.
  • the license Descriptor includes a license Descriptor ID, a VNFD ID, and a license information selection item. Including the operator to select a list of functions or features when purchasing a license, Global LM is also used to send a license to Local LM;
  • the NFVO After receiving the license Descriptor, the NFVO submits a license application request to the Local LM according to the license Descriptor.
  • the Local LM can send a license information to the NFVO according to the license obtained from the Global LM according to the NFVO license application request, so that the NFVO can use the license according to the license.
  • Information providing software licenses to VNF network elements.
  • the license information can be the number, the feature, and the function of the license. If the VNF NE needs to be activated, the license information can include the activation code of the license file, the license ID, or the download address. Based on this information, the VNF can obtain or download a license file and activate the license based on the activation code.
  • the license file is not directly sent to the NFVO. It is more beneficial for the software provider to control the license file and prevent the NFVO from obtaining the complete license file.
  • Global LM can issue License Descriptor to NFVO in various ways. For example, after signing an order with an operator customer, it can send a License Descriptor to NFVO through Local LM according to the order information, or in the software provider. When the NFV operator releases the VNF Package, the License Descriptor generated by the Global LM is sent together. In the VNF Package shelf-up process, the NFVO can obtain the License Descriptor. The NFVO can verify the License Descriptor. When the verification fails, NFVO can also apply for a License Descriptor from Local LM based on the License Descriptor ID or VNFD ID, and Local LM then applies for a License Descriptor from Global LM.
  • the process of loading the VNF Package and the process of applying the license are synchronized.
  • the automatic synchronization between the license application and the NFV loading process is facilitated, and the efficiency of the license application is improved.
  • the time when the local LM obtains the license from the Global LM is also flexible. For example, after the order is signed, the Global LM can actively send the corresponding license to the Local LM according to the information received from the order management system, or deploy the VNF network element in the NFVO. During the process, the local LM is applied for a license. The local LM then applies to the global license to obtain a license.
  • the Global LM can be connected to the software provider's order management system to automatically deliver the license.
  • Local LM can also act as a proxy for Global LM or Global LM-based authorization.
  • Local LM generates license locally and will generate The license information is sent to NFVO to meet the needs of VNF network element deployment in time. After the communication between Local LM and Global LM is restored, Local LM reports the generated license to Global LM, and Global LM updates its record. License information provided to the NFV network for billing purposes. This application is not limited to the scenario of communication anomaly. Even in the case of normal communication, the Local LM can also act as a proxy for Global LM or a Global LM-based authorization.
  • Local LM can generate licenses locally, which helps the system to provide more stable services and improve the stability and security of the system, so that Global LM can replace Global LM generation even if Global LM provides licenses for some reason. License to ensure the immediate deployment of VNF network elements.
  • the local LM can subscribe to the VNF LCM process to trigger the NFVO application or release the license.
  • the NFVO can actively trigger the application and release of the license during the VNF LCM process.
  • the management system of the license in the NFV network may further include NFVO, the NFVO acquires the License Descriptor, and the process of applying for the license has been described before. Further, the NFVO may receive the License Descriptor issued by the Global LM. Then, the correspondence between the license Descriptor ID and the VNFD ID is saved, so that when the NVF is deployed, the license Descriptor ID of the required application can be found according to the VNFD ID, thereby completing the license according to the License Descriptor corresponding to the License Descriptor ID. Application. Improve the efficiency of the search by saving the correspondence.
  • NFVO can trigger the operator's OSS system to purchase the required license from the software provider's order management system.
  • the NFV network operator can use the Local LM as a command center for network resource allocation, and flexibly perform the VNF according to the license information of the entire network and the needs of the network service.
  • the application or release of the license, the allocation of license resources and distribution in addition, NFVO can also obtain the license information of the entire network on the NFV network from the Local LM, so that NFVO can also be used as a command center for network resource allocation, flexible VNF license
  • the application or release of the certificate, the allocation of license resources and distribution Since NFVO controls the deployment of NFV network elements, NFVO is also familiar with the operation of the entire network. NFVO is more suitable for the application and release of flexible deployment of licenses in the center, thus adjusting the shrinkage and expansion of VNF.
  • the present application also provides a method for managing a license in an NFV network.
  • the process implemented by the method is basically the same as the system description process provided above, and the description is not repeated.
  • the present application also provides a license management server corresponding to the Global LM210, which includes a license template and license generation unit 2011, a license template issuance unit 2013, a license issuance unit 2015, a license template, and a license generation unit. 2011 can be connected to the software provider's order management system, generate the corresponding License Descriptor and license according to the customer's order information obtained from the software provider order management system, and issue the License Descriptor to NFVO through the license template issuing unit 2013.
  • the license template receiving unit 2031 transmits the license to the license management unit 2023 of the Local LM through the license issuing unit 2015; the license template and the license generating unit 2011 can also receive from the license management unit 2023 of the Local LM The license from the Local LM is applied to generate the corresponding license and is sent to the Local LM.
  • the present application also provides a license management server, corresponding to the Local LM 202, including a license application receiving unit 2021, a license management unit 2023, and a license issuance unit 2025, which is used for license application from NFVO.
  • the unit 2033 obtains the request for the license application, and then sends the license application request to the license management unit 2023.
  • the license management unit 2023 is responsible for saving and updating the license information, and determining whether the currently available license can meet the requirements of the application. If yes, the corresponding license information is sent to the license receiving unit 2035 of the NFVO through the license issuing unit 2025.
  • the notification message for purchasing the license may be fed back to the NFVO, and the NFVO triggers the NFV network operation according to the notification message.
  • the vendor's OSS system purchases the required licenses from the software provider's order management system.
  • the present application also provides an NFVO 203, including a license template receiving unit 2031, a license application unit 2033, and a license receiving unit 2035.
  • the license template receiving unit 2031 can obtain a License Descriptor issued by Global LM from various channels, and a license.
  • the application unit 2033 performs a license application according to the License Descriptor received by the license template receiving unit 2031.
  • the license receiving unit 2035 receives the license information transmitted by the license issuing unit 2025 of the Local LM.
  • the license application unit 2033 is further configured to save the correspondence between the license Descriptor ID and the VNFD ID, so that when the NVF is deployed, the license Descriptor ID of the required application can be found according to the VNFD ID, so that the license corresponding to the license Descriptor ID is obtained. Descriptor, complete the application for the license.
  • the application also provides a computer program product for performing the methods performed by the Global LM, Local LM or NFVO described above when the computer product is executed.
  • the application further provides a computer readable storage medium having stored therein instructions for performing the methods performed by the Global LM, Local LM or NFVO described above.
  • the license management method and system in the NFV network implement the flexible and automatic management and use of the license in the NFV network, improve the efficiency of the license, and help the NFV operator further improve the network management efficiency.
  • the license of the entire network, the rational planning and use of the license, and the adjustment of the network deployment are conducive to the development of the NFV network.
  • FIG. 1 is a schematic diagram of a reference architecture of an NFV network
  • FIG. 2 is a schematic structural diagram of a license management system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a license management system architecture and a logical unit structure of a network element according to an embodiment of the present invention
  • FIG. 4 is a structural diagram of a computer hardware for performing a Global LM function according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a license Descriptor racking process according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a VNF network element instantiation process
  • FIG. 7 is a flowchart of triggering an application for a license by the Local LM during the VNF instantiation process according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a state machine for storing a license in a Local LM according to an embodiment of the present invention
  • FIG. 9 is a schematic diagram of a process for releasing a license according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of a license application or release triggered by NFVO according to an embodiment of the present invention
  • FIG. 11 is a schematic diagram of a process for expanding capacity according to VNF reporting information according to an embodiment of the present invention.
  • a license management system includes a Global License Manager 201 (Global LM), a Local License Manager 202 (Local LM) logical function entity, and an NFVO 203.
  • the system can further include two network elements, VNFM 204 and VNF 205.
  • the Global LM 201 is a software provider's license delivery system. It is used to implement the license delivery.
  • the License Descriptor (license information description template) is distributed to the operator and the license is distributed to the Local LM.
  • the License Descriptor can be sent to the NFVO through the Local LM. It can also be sent to NFVO through OSS or NFVO portal (NFVO portal or human machine interface) during the VNF Package shelf-up process;
  • the local LM 202 is deployed in the VNF network.
  • the local LM obtains the license purchased by the operator from the Global LM, receives the NFVO license application, and sends the corresponding license information to the NFVO.
  • Local LM can be connected to Global LM of multiple software providers, or it can be a dedicated device that is specifically responsible for interfacing with a software provider's Global LM. In this case, the Local LM is generally also connected to it.
  • Local LM can be used as a license management agent of Global LM in the carrier network to implement distribution and control of licenses within the carrier network. Since Global LM and Local LM are now provided by the same software provider, the communication security and information mutual trust between the two network elements is higher.
  • the NFVO 203 is used to obtain the license Descriptor.
  • the local LM applies for the license information required for deploying the VNF network element, and sends a license application request to the Local LM, and receives the Local. License information sent by the LM.
  • the license description file is a description template of the license product information. It can be viewed as a list of function lists of the license.
  • the License Descriptor may include a License Descriptor ID (a unique identifier of the License Descriptor file), software provider information, product information, a VNFD ID, and a list of functions or features that the customer can select, and may also include the geographic region or time of the license.
  • the list of features or features that are available for customer selection can be collectively referred to as license information options.
  • the content of the License Descriptor template format and license information options provided by different device providers may vary, such as software provider information and products. Information can be obtained in other ways, so it is optional in this form.
  • the purpose of the License Descriptor is to enable the operator to apply for a license based on the License Descriptor.
  • the license can be quickly generated based on the License Descriptor.
  • License Descriptor is similar to other templates in NFV (such as VNFD). It can use Tosca, Yang and other models.
  • the description language can be XML or Yaml.
  • the Global LM 201 is responsible for generating a License Descriptor that is distributed to the customer (in this document, the customer refers to the license purchaser, that is, the operator of the NFV network), and provides the generated License Descriptor to the NFVO in the carrier network.
  • Global LM can issue License Descriptor to NFVO in a variety of ways. For example, Global LM can connect with the software provider's order management system, and issue the License Descriptor corresponding to the order information to Local LM according to the order information signed with the customer. Local LM then releases the License Descriptor to NFVO. It can also apply for the LMVO to obtain the License Descriptor from Global LM through Local LM.
  • the VNF Package (including the software package of VNF network element) to the operator.
  • the VNF Package is sent to the NFVO corresponding to the required License Descriptor, or the operator's OSS system applies to the Global LM, and the Global LM sends the License Descriptor to the OSS system.
  • the OSS system is sent to NFVO or downloaded by the operator from the customer support website provided by the software provider.
  • the NFVO can apply for the license according to the License Descriptor. Therefore, the NFVO can obtain the License Descriptor process, which is called the license process.
  • the license Descriptor is saved, and the correspondence between the License Descriptor ID and the VNFD ID in the License Descriptor can also be recorded. For example, the correspondence between the two is stored in a separate form, so that the VNF is instantiated in the subsequent VNF. If you need to apply for a corresponding license, you can quickly find the corresponding License Descriptor ID based on the VNFD ID of the VNF that you need to instantiate. You can find the license Descriptor required to apply for a license and apply for a quick license.
  • Local LM can also act as a proxy for Global LM or Global LM-based authorization.
  • Local LM generates license locally and will generate The license information is sent to NFVO to meet the needs of VNF network element deployment in time. After the communication between Local LM and Global LM is restored, Local LM reports the generated license to Global LM, and Global LM updates its record. License information provided to the NFV network for billing purposes. This application is not limited to the scenario of communication anomaly. Even in the case of normal communication, the Local LM can also act as a proxy for Global LM or a Global LM-based authorization.
  • Local LM can generate licenses locally, which helps the system to provide more stable services and improve the stability and security of the system, so that Global LM can replace Global LM generation even if Global LM provides licenses for some reason. License to ensure the immediate deployment of VNF network elements.
  • Figure 3 further presents the logical units within three devices and their connections to implement the specific functions described above.
  • the Global LM 201 includes a license template and license generation unit 2011, a license template issuance unit 2013, a license issuance unit 2015, a license template and a license generation unit 2011 may be connected to the software provider's order management system, according to The customer's order information obtained in the software provider order management system, etc., generates a corresponding License Descriptor and License, and issues the License Descriptor to the NFVO license template receiving unit 2031 through the license template issuing unit 2013 (through the VNF Package) Sending, or through the license template forwarding unit 2027) of the Local LM, through the license issuance unit 2015, the license is sent to the license management unit 2023 of the Local LM; the license template and the license generation unit 2011 can also be from the Local LM
  • the license management unit 2023 receives the license application from the Local LM, and generates a corresponding license, which is sent to the Local LM.
  • the Local LM 202 includes a license application receiving unit 2021, a license management unit 2023, and a license issuance unit 2021 for obtaining a request for a license application from the license application unit 2033 of the NFVO, and then applying for the license.
  • the request is sent to the license management unit 2023.
  • the license management unit 2023 is responsible for saving and updating the license information, and determining whether the currently available license can meet the requirements of the current application. If so, the corresponding license information is used.
  • the description in the figure) is sent to the license receiving unit 2035 of the NFVO through the license issuing unit 2025; if the license is insufficient, the notification message for purchasing the license may be fed back to the NFVO (license application unit 2033), according to which the NFVO is based,
  • the OSS system of the NFV network operator is triggered to purchase the required license from the software provider's order management system, or the license management unit 2023 sends a license application to the license template and license generation unit 2011 of Global LM to obtain the corresponding license.
  • the license management unit 2023 can also function as Glo The agent of the LM, or the authorization of the Global LM, generates a license, and reports the generation of the license to the Global LM (for example, the license issuing unit 2015, which performs the license management of the license issuing unit 2015).
  • the NFVO 203 includes a license template receiving unit 2031, a license application unit 2033, and a license receiving unit 2035.
  • the license template receiving unit 2031 can obtain a License Descriptor issued by the Global LM from various channels, and the license application unit 2033 receives the license template according to the license template.
  • the license Descriptor received by the unit 2031 is used to apply for a license.
  • the license receiving unit 2035 receives the license information transmitted by the license issuing unit 2025 of the Local LM.
  • the license application unit 2033 is further configured to save the correspondence between the license Descriptor ID and the VNFD ID, so that when the NVF is deployed, the license Descriptor ID of the required application can be found according to the VNFD ID, so that the license corresponding to the license Descriptor ID is obtained. Descriptor, complete the application for the license.
  • the NFVO 203 may further include a license information receiving unit 2037 for obtaining the license information of the entire network from the Local LM (such as the license management unit 2023), so that the NFVO can be used as a command center for network resource allocation, and the VNF license is flexibly performed.
  • a license information receiving unit 2037 for obtaining the license information of the entire network from the Local LM (such as the license management unit 2023), so that the NFVO can be used as a command center for network resource allocation, and the VNF license is flexibly performed.
  • Global LM can be understood as the software provider's license system can provide license management services to carrier customers around the world. If it is a device that provides license services to Asian operators, it can also be named as Asia License Manager.
  • the license server deployed on the software provider side is called the first license management server. If the local LM is independently built and connected to the license server of multiple software providers, it can also be called the license centralized management server of the carrier.
  • a license server deployed in the carrier network and connected to the first license management server of the software provider may be collectively referred to as a second license management server.
  • Global LM can be integrated into the software provider's web server or integrated with the software provider's order management and billing system.
  • the present invention is not limited; the Local LM may be an independently deployed network element in the NFV network, or may integrate the logic function of the Local LM in the NFVM or the NFVO, or be integrated in the operator's OSS system.
  • Global LM, Local LM and NFVO The related functions of Global LM, Local LM and NFVO described above can be implemented by hardware such as integrated circuits/ICs, or by computer software to execute corresponding computer programs.
  • this application only takes the implementation of Global LM as an example, and the computer functions of Local LM and NFVO are implemented in the same manner, and the difference is only in the memory.
  • Different software codes are stored in the memory, and the logic units and functions of the specific software code are described in the above embodiments, and the description will not be repeated again.
  • Computer device 400 includes at least one processor 401, a communication bus 402, a memory 403, and at least one communication interface 404.
  • the processor 401 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present invention. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 402 can include a path for communicating information between the components described above.
  • Communication interface 404 using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 403 is used to store the application code for executing the solution of the present invention. As shown in the figure, it stores the logic code corresponding to the three functional units of the Global LM, and is controlled by the processor 401 for execution.
  • the processor 401 is configured to execute application code stored in the memory 403 to implement the logical function of the Global LM.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 400 may also include an output device 405 and an input device 406.
  • Output device 405 is in communication with processor 401 and can display information in a variety of ways.
  • the computer device 400 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure.
  • Embodiments of the invention do not limit the type of computer device 400.
  • the application and release of the license can be automatically and flexibly.
  • the NFVO can automatically complete the application of the license during the process of deploying the VNF network element, or automatically when the VNF network element is released. Release the license.
  • the NFV network operator can perform more flexible network resource allocation based on the actual service requirements. The management efficiency of the license is greatly improved.
  • the License Descriptor generated by the Global LM is packaged and distributed in the VNF Package.
  • the steps in Figure 501 are only used to indicate that the Global LM is generating the License Descriptor.
  • the present invention does not limit the delivery method of the VNF Package.
  • the VNF Package includes the VNFD and the License Descriptor.
  • the online support system of the software provider may be sent to the OSS system of the operator or the portal of the NFVO, or obtained from a CD-ROM containing the VNF Package provided by the software provider, or by the OSS system of the operator or NFVO's Portal is available from the online support system provided by the software provider or other websites that download the VNF Package.
  • the client uploads the license Descriptor issued by the software provider to the NFVO through the OSS system or the NFVO Portal (collectively referred to as Sender).
  • the License Descriptor command can use the existing On-board VNF Package command to add a parameter identifier to the command.
  • the tag is a shelf request of the License Descriptor, and carries the License Descriptor information, or adds a License Descriptor command;
  • the NFVO checks the license Descriptor (the license template receiving unit 2031), and the content of the verification includes but is not limited to:
  • the NFVO (the license template receiving unit 2031) saves the License Descriptor, and records the correspondence between the License Descriptor ID and the VNFD ID, so as to be based on the VNFD in the VNF LCM (Lifecycle Management) process.
  • the ID quickly finds the required License Descriptor for the license application.
  • the reason for the verification failure may be that there is no License Descriptor information in the VNF Package, the description of the product information in the License Descriptor and the VNFD is inconsistent, or the VNFD defined in the License Descriptor is not included in the software.
  • the package is medium.
  • NFVO Local Area Network
  • Sender which may be an existing VNF Package response, and carries a parameter in the response to indicate that the License Descriptor is successfully presented, or may be added.
  • the License Descriptor has a successful response message.
  • the NFVO notifies the Local LM that the License Descriptor has been uploaded, and the License Descriptor may be carried in the notification message, or only the License Descriptor ID and/or the VNFD ID may be carried. At this point, the License Descriptor is on the shelves. If the Local LM needs to verify the License Descriptor, you can obtain the License Descriptor from Global LM and save it with the License Descriptor obtained from Global LM. See steps 7 to 12.
  • NFVO notifies the Local LM License Descriptor that the verification fails, and the failure reason and the VNFD ID may be carried in the verification failure notification message.
  • the Local LM may initiate a license Descriptor request to the Global LM according to the VNFD ID, where the carrier identifier information and the VNFD ID information may be carried in the request.
  • the Global LM determines whether the license Descriptor can be sent to the operator, for example, whether the operator purchases the corresponding product, and if so, sends a License Descriptor to the Local LM.
  • the Global LM returns a corresponding License Descriptor to the Local LM.
  • the Local LM maintains the License Descriptor information.
  • the Local LM returns the obtained License Descriptor to the NFVO.
  • the NFVO performs the same steps of saving the License Descriptor as in step 504, and sends a response to the SNF VNF Package to the sender in step 512a.
  • the above embodiment describes the process of issuing a License Descriptor together with the VNF Package, or triggering the acquisition of the License Descriptor to the Local LM and Global LM by NFVO.
  • the process of loading the VNF Package and the process of applying the license are synchronized.
  • the automatic synchronization between the license application and the NFV loading process is facilitated, and the efficiency of the license application is improved.
  • the License Descriptor may be uploaded to the Local LM (License Template Forwarding Unit 2027) by Global LM (License Template Publishing Unit 2013). For example, according to the order signed with the customer, the LMVO is actively sent through the Local LM. License Descriptor, NFVO saves the corresponding License Descriptor.
  • the specific process is similar to 508-512 in the above process, and the description will not be repeated.
  • the management and use of the license in the embodiment of the present invention may have multiple flexible manners according to different scenarios.
  • the software provider's Global LM sends the license to the Local LM, and the license is stored in the Local LM.
  • the NFVO needs to use the license, it submits the license application request to the Local LM, and the Local LM sends the license information to the NFVO.
  • the application for the license is issued.
  • NFVO notifies Local LM to release or deactivate the license.
  • the license can be in multiple VNF network elements.
  • the license is used in the shared resource pool. For example, the license corresponding to feature A of a 300,000 users is loaded on the VNF1 network element. After the VNF1 network element is released, the license can be allocated to the VNF2 network element.
  • Global LM can actively send the license corresponding to the network element purchased by the operator to the Local LM according to the information in the order, or the License Descriptor described in the above process.
  • the sending process is sent to the customer. For example, if the customer purchases a license for a network element with 1 million users, Global LM will send the license of 1 million users to Local LM. Local LM saves the license of 1 million users (can be understood as centralized purchasing or package purchasing mode).
  • the Local LM can distribute the license according to the actual needs of the VNF. For example, the network element VNF1 applies for a license of 300,000 users.
  • the Local LM sends a license to the NFVO that can support 300,000 users.
  • the Local LM is requested to apply for the corresponding license to the Global LM according to the requirements of the network element deployment, and the Global license is then sent to the NFVO through the Local LM (which can be understood as a batch purchase). Or use the pay-as-you-go mode, or the Local LM can determine whether the current license can meet the deployment requirements of the VNF. If not, the NFVO needs to apply for an additional license to trigger the NFVO to apply for a new license to the Global LM.
  • the software provider's software is like the software in the Apple App Store.
  • the operator uses a certain software and can order from the operator's OSS system to the software provider.
  • the management system makes an online order application, and upon completion of the payment or the post-paid agreement, the order management system notifies Global LM that the customer's required license will be delivered to the customer in a timely manner.
  • the release of the license is similar.
  • the Global LM can issue a license to the Local LM to release the license according to the network planning change order with the customer.
  • the Local LM performs the license update locally and releases the corresponding license resource.
  • the NFVO based on the detection of the network load, determines that the VNF network element can be released or contracted, and then sends a license release notification message to the local LM.
  • the local LM updates the license and releases the license resource.
  • the release notification notification message may include the corresponding VFND ID, the number of licenses to be released, and corresponding functions and features. After the local LM releases the license, it can notify Global LM so that the software provider can reasonably charge the operator's software usage according to the changed license usage.
  • the relocation of the license is the combination of the license release and the license application process. After the licenses of some VNF NEs are released, they are distributed to other required VNF NEs.
  • the Local LM has an overall view of the entire network license of the operator for a certain software provider. If the Local LM is connected to the Global LM of each software provider, the Local LM has multiple software providers. Overall license view. NFVO can also obtain the information of the entire network license purchased by the operator from the Local LM (such as the number of available licenses, etc.), for example, periodically send a license query request to Local LM, and Local LM periodically replies to NFVO with the latest license usage. The information of the situation, in this way, the operator can control the license information of the whole network on the local LM or NFVO, thereby expanding, shrinking, releasing or relocating the NFV network deployment according to the license information of the entire network and the network service requirements.
  • NFV networks in many provinces in China, and can have one or several centralized NFVOs for unified license management of the entire network.
  • the EPC network element is deployed in various provinces and cities such as Guangdong and Shanghai. It is assumed that the license applied by the EPC network element deployed in Guangdong province meets the needs of 5 million users, and the EPC network element of Shanghai The application for the license is to meet the needs of 3 million users.
  • NFVO can be based on its mastery.
  • the network license it is determined that the license of 1 million users will be released from Guangdong province, and the license of the 1 million users will be transferred to Shanghai.
  • the sharing of the license is subject to the geographical limitation of the license. If the license-limited license range of the license is limited to a certain province, the license cannot be shared across provinces, that is, the license must be restricted. Share within a geographical area.
  • VFN instantiation process can refer to the relevant standard texts, such as ETSI GS NFV-IFA 007V2, because of the prior art process. 1.1 (2016-10), hereinafter referred to as IFA 007.
  • NFVO initiates a request for Create VNF Identifier to VNFM (refer to IFA007Table 7.2.2.2-1)
  • the VNFM returns a vnfInstanceId to the NFVO (refer to IFA007 Table 7.2.2.3-1).
  • the VNFM sends a notification of VnfIdentifierCreationNotification to the NFVO (refer to IFA007Table 8.6.7.3-1)
  • NFVO initiates a request for Instantiate VNF to VNFM (refer to IFA007 Table 7.2.3.2-1)
  • VNFM returns VNF lifecycleOperationOccurrenceId to NFVO (refer to IFA007 Table7.2.3.3-1)
  • the VNFM finds the corresponding vnfdId according to the vnfInstanceId, obtains the VNFD, parses the resource information required for instantiating the VNF, and requests the operation and resource authorization from the NFVO (refer to IFA007Table 6.3.2.2-1).
  • NFVO returns the Grant lifecycle operation response to VNFM (refer to IFA007 6.3.2.3)
  • VNFM initiates the VNF instantiation process; and sends VNFLifecycleOperationChangeNotification to NFVO (refer to IFA007 8.6.2.3)
  • the VNFM informs the NFVO that the instantiation operation of the VNF is completed (refer to IFA0078.6.2.3-1).
  • the Local LM subscribes to the VNF LCM status change notification to the VNFM.
  • the VNFM sends a notification to the subscriber Local LM when the following event occurs:
  • VNF instance ID VNF Identifier creation notification
  • VNF lifecycle state change notification including instance ID, start or completion, lifecycle action "such as instantiation / expansion / termination", .
  • VNF Identifier delete notification
  • the VNFM performs VNF instantiation (the process shown in FIG. 6) or VNF expansion;
  • the VNFM sends a lifecycle state change notification to the Local LM, and the Local LM can start the process of the license when receiving the notification of the start or end of the instantiation or the expansion.
  • the local LM obtains the license information required for the VNF to be instantiated/expanded to the NFVO.
  • the NFVO (the license template receiving unit 2031) obtains the corresponding VNFD ID according to the vnfInstanceId obtained in the instantiation/expansion process (step 402), and then searches for the previously saved VNFD ID and obtains the corresponding License Descriptor ID according to the VNFD ID. Correspondence relationship, quickly find the corresponding License Descriptor, combined with the needs of the business, determine the required functional characteristics and usage, and perform on-demand adaptation of the License Descriptor.
  • NFVO Local LM (license application receiving unit 2021), in the application In, you need to add carrier information)
  • the license information of the application is as shown in Table 2 below:
  • Local LM Local LM (License Management Unit 2023) according to the NFVO license needs to determine whether the currently available license can meet the demand, if the demand can be met, then directly perform step 712;
  • the license can be dynamically managed by the state machine. As shown in Figure 8, the status of the license can be divided into active state and deactivated state. In the deactivated state, the state is further divided into substate 1 and state. 2, sub-state 1 indicates that the license has not been assigned to the NFV instance, and sub-state 2 is the temporary state, indicating that the NFV instance has been assigned, but the VNF instance has not completed the activation process. In substate 2, the license cannot be assigned to other instances. The purpose is to prevent other VNF instances from applying during the activation process.
  • step 707 the Local LM can check whether the number of licenses in the sub-state 1 meets the requirements in the existing license library. If yes, the license is assigned to the instance and the status of the related license is updated to the sub-license. State 2, perform Step 712 operation.
  • the local LM checks whether the used usage exceeds the standard according to the number of licenses purchased by the customer. If the number is not exceeded, the Local LM triggers the license application process to the Global LM (step 708). If the standard is exceeded, you can tell NFVO that NFVO will decide whether to apply for a new license, and then apply for a new license to Global LM through Local LM.
  • the current license number of the EPC MME V5.0 product NE is 100000 total users, the feature A is 50000, and the feature B is 30000.
  • the license required to instantiate the EPC MMEV5.0 is the total number of users X, the usage of the feature A is A1, and the usage of the feature B is B1. If the license is less than the current number of licenses, the license can be assigned. The number of licenses will be deducted from the local LM. If the application of this instance exceeds the available license range, you can notify NFVO to apply for additional licenses.
  • the Local LM (License Management Unit 2023) triggers the license application process to the Global LM (License Template and License Generation Unit 2011).
  • the license generated by Global LM can be in various forms depending on the way the license is controlled.
  • the generated license can be the license information such as the feature/function/user number used by the license.
  • the information can be distributed in the form of a license file or in other forms, such as attached messages. Participate in the body to distribute.
  • the license generated by Global can be in the form of authorization certificate, license file, activation code, or the like.
  • Each software provider can use its own mechanism. , do different combinations.
  • Global LM can only provide the newly added license, and can also package the newly added license with the historically assigned license to synthesize a new license and release the original license.
  • the Global LM (License Issuance Unit 2015) returns a license to the Local LM (License Management Unit 2023).
  • the Global LM generally needs to encrypt and transmit the license to ensure secure transmission of information.
  • the Local LM (the license management unit 2023) records the new license information, and updates the information such as the number of available licenses.
  • Local LM When Local LM and Global LM are connected abnormally, Local LM cannot apply for a new license to Global LM. At this time, Local LM can also act as a proxy for Global LM, or generate a license locally, such as a license based on the authorization of Global LM.
  • the management unit 2023 cannot send a license application request to the Global LM, and cannot receive the license from the Global LM.
  • the Local LM (the license management unit 2023) can generate a license and send the license information to the NFVO through the license issuance unit 2025.
  • the Local LM (License Management Unit 2023) transmits the generated license to the Global LM (License Template and License Generation Unit 2011), such as the number, characteristics, functions, and the like. Information so that Global LM updates its recorded license information to the NFV network.
  • the Local LM (the license issuance unit 2025) notifies the NFVO (the license receiving unit 2035) of the license information that is requested, so that the NFVO can provide the software license to the VNF network element according to the license information.
  • the license information can include the functions, characteristics, and corresponding quantity of the license.
  • the local LM can perform certain processing or conversion on the license received from the Global LM.
  • the NFVO is sent to the NFVO.
  • the NFVO sends a message to activate the license to the VNF according to the received license information, and notifies the VNF of the license information that can be used by the VNF.
  • the license issued by the Global LM to the Local is the license file.
  • the license file can include the activation code information.
  • the license information provided by the local LM to the NFVO can include the activation code and the license file.
  • the download address (such as the access address of the Local LM, such as the IP address, etc.) or the identifier of the license file, in step 713, the activation license and the license file are carried in the message that the NFVO sends the activation license to the VNF.
  • the VNF network element downloads the corresponding license file from the Local LM according to the download address of the license file or the identifier of the license file, and uses the obtained activation code. Activate the license file to complete the activation of the license.
  • the Local LM can also send the license file and the activation code to the NFVO.
  • the VNF network element can activate the license directly according to the license file and activation code provided by the NFVO.
  • the software provider can weaken the control of the license.
  • the VNF network element can work beyond the limit number of licenses. At this time, the software provider can monitor whether the operator's client uses the software within the scope of the license specified by the VNF network element, or adjust the billing according to the usage of the license.
  • the local LM can directly notify the VNF instance of the license information.
  • the Local LM records the license activation information, and the license enters an active state.
  • the VNF instance notifies the NFVO activation information through the VNFM.
  • Figure 9 is a schematic diagram of a process for releasing a license, as shown in Figure 9, including:
  • VNFM sends a VNF LCM status change notification (Terminate VNF or contraction) to Local LM when there is a termination NFV or a contraction NFV event.
  • the local LM obtains the license release mode corresponding to the instance from the NFVO.
  • the NFVO may determine to release the license completely or deactivate the license according to the service requirement, and notify the local LM of the released or deactivated license information. When deactivated, the operator may further use the license. If the VNF network element is released, the instance ID of the VNF network element to be released may be carried, and if it is a reduced capacity, the instance ID of the VNF network element and the reduced license information, such as the number of licenses, may be carried.
  • the local LM refreshes the license state. If the license is deactivated, the local LM adds the licenses to the number of available licenses. If the state machine manages, the status of the licenses can be set to the deactivated state-substate 1. If the license is completely released, the corresponding license resource is released locally, and Global LM can be notified to adjust the billing with Global LM based on the license usage.
  • the Local LM notifies the NFVO License release/deactivation to be completed.
  • the Local LM notifies the Global LM of the license release notification.
  • the application (including expansion) and release (including shrinkage) of the license described in the above procedure are triggered by the Local LM.
  • the NFVO can also trigger the application and release of the license.
  • NFVO based on VNF lifecycle management operations, such as instantiation, expansion or release, NFVO triggers the application or release process of the corresponding license file;
  • the NFVO triggers the application for the license file to the Local LM.
  • the instantiation can be completed, and the other steps are not completed.
  • NFVO can apply for the corresponding license file to Local LM according to the needs of the VNF before or after instantiation.
  • NFVO combined with the need of the service, determine the license operation behavior, for example, apply for a new license, perform step 903a, or release the license, perform step 903b, and send a request for the license or release the license to the Local LM.
  • the specific process is similar to step 705.
  • the subsequent steps are basically the same as the above-mentioned embodiments.
  • the main difference is that the license application/expansion or release triggering the NE body is different.
  • the above two embodiments are used for the Local LM to trigger the application and release of the license, and this embodiment is the NFVO trigger. Since the specific implementation process after the triggering is basically the same as the implementation in the embodiment of FIG. 7 and FIG. 9, the description is not repeated.
  • the VNF statistics and the usage of the instance traffic related to the license control item are sent to the Local LM according to the preset configuration timing, periodicity, or when the threshold is triggered.
  • a percentage of the licensed license usage (such as 90%, 100% or 120%, etc., the specific value is determined by the policy arrangement between the software provider and the operator) may be specified as a trigger threshold, and the statistics may include Various types of license usage statistics, such as statistics based on busy hours and idle hours, usage statistics based on functions or features, statistics of daily, weekly, or monthly users, and so on;
  • the local LM determines whether the usage of the license reaches the alarm threshold or exceeds the upper limit according to the statistics reported by the VNF.
  • the Local LM sends an alert or a capacity expansion prompt to the NFVO according to its own control policy.
  • the control policy may be sent to the Local LM by the Global LM, or configured on the Local LM, or sent by the operator's OSS system to the Local LM.
  • the control policy may be that the alarm threshold or the license upper limit is exceeded for three consecutive weeks;
  • the NFVO determines whether to expand the capacity according to the service requirement, apply for additional license resources, or adjust the network resources according to the license view of the entire network and the overall operation of the service.
  • the VNF with low network resource utilization is deleted, and the released license is added to the VNF with insufficient license.
  • Local LM can also notify NFVO, so that NFVO can perform corresponding shrinkage processing according to the prompt.
  • the VNF can also report the statistics of the usage of the admission control items to the NFVO during operation, configure the control policy on the NFVO, and determine whether the additional license needs to be applied by the NFVO according to the control policy. Expand the capacity or release the license resource.
  • the computer program instructions may be provided to a general purpose computer, a processor of a special purpose computer, or other programmable data processing apparatus such that the instructions are executed by a processor or other programmable data processing apparatus of the computer for implementation in the process The device of the function indicated in the figure.
  • the computer program instructions can also be stored in a computer usable or computer readable memory that can be booted by a computer or other programmable data processing device in a particular manner, such that instructions stored in a computer usable or computer readable memory produce such an article.
  • the article of manufacture includes instructions for implementing the functions indicated in one or more of the blocks of the flowcharts.
  • the computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps on the computer or other programmable data processing device to produce a computer implemented process, thereby
  • the instructions executed on a computer or other programmable data processing apparatus provide steps for implementing the functions indicated in one or more of the flowcharts and/or block diagrams.
  • the above described functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer readable medium or transmitted as one or more instructions or code to a computer readable medium.
  • Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another.
  • the storage medium can be any available media that any general purpose or special computer can access.
  • Such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general purpose or special processor.
  • any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium.
  • DSL digital subscriber line
  • the disks and discs include compact disks, laser disks, optical disks, DVDs, floppy disks, and Blu-ray disks. Disks typically replicate data magnetically, while disks typically optically replicate data with a laser. Combinations of the above may also be included in a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un procédé et un système de gestion d'une licence dans un réseau NFV, une gestion flexible et automatique d'une licence étant effectuée par l'alignement d'un premier serveur de gestion de licences d'un fournisseur de logiciel et d'un second serveur de gestion de licences déployé dans une plage de réseaux NFV; un NFVO acquiert un modèle de description d'informations de licence émis par le premier serveur de gestion de licences; le NFVO s'applique pour une licence à partir du premier serveur de gestion de licences selon le modèle; le second serveur de gestion de licences acquiert une licence requise à partir du premier serveur de gestion de licences; et des informations de licence sont envoyées au NFVO, ce qui permet de réaliser une gestion flexible et automatique d'une licence.
PCT/CN2018/078403 2017-03-13 2018-03-08 Système de gestion de licence dans un réseau nfv Ceased WO2018166398A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710147528.5 2017-03-13
CN201710147528.5A CN108574593B (zh) 2017-03-13 2017-03-13 一种nfv网络中许可证的管理系统和管理方法

Publications (1)

Publication Number Publication Date
WO2018166398A1 true WO2018166398A1 (fr) 2018-09-20

Family

ID=63522595

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078403 Ceased WO2018166398A1 (fr) 2017-03-13 2018-03-08 Système de gestion de licence dans un réseau nfv

Country Status (2)

Country Link
CN (1) CN108574593B (fr)
WO (1) WO2018166398A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3112049A1 (fr) * 2020-06-29 2021-12-31 Orange Procédé de gestion collaborative de licences entre domaines industriels
CN114371921A (zh) * 2021-12-31 2022-04-19 天翼物联科技有限公司 License调度系统、方法、装置及存储介质
US11663298B2 (en) * 2019-12-11 2023-05-30 At&T Intellectual Property I, L.P. Managing enterprise software licenses for virtual network functions
GB2622768A (en) * 2022-08-16 2024-04-03 Awtg Ltd A system for handling data within a mobile data network
CN119520296A (zh) * 2024-11-06 2025-02-25 中电信数智科技有限公司 一种在vi层实现nfv网元快速扩缩容的方法、系统、设备和存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743194A (zh) * 2018-12-10 2019-05-10 中国联合网络通信集团有限公司 一种License管理方法及装置
CN112989289B (zh) * 2019-12-02 2023-04-25 成都鼎桥通信技术有限公司 软件许可证核查方法、装置、电子设备及可读存储介质
CN113553552A (zh) * 2020-04-23 2021-10-26 丁爱民 一种许可证管控方法和系统
CN115589351B (zh) * 2021-07-06 2024-07-30 华为技术有限公司 一种查询方法、装置及设备
CN113965912B (zh) * 2021-10-20 2023-07-18 中国联合网络通信集团有限公司 通信软件许可证的调度方法、装置和设备
CN114491418B (zh) * 2021-12-28 2023-06-02 北京深盾科技股份有限公司 软件许可方法及电子设备
CN114266017B (zh) * 2021-12-30 2022-11-01 北京深盾科技股份有限公司 软件许可方法及电子设备
CN115955407B (zh) * 2022-09-30 2024-08-30 中国联合网络通信集团有限公司 实例管理方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104134122A (zh) * 2014-07-30 2014-11-05 华为技术有限公司 一种许可证申请方法及装置
EP3002699A1 (fr) * 2014-09-30 2016-04-06 Alcatel Lucent Procédé pour commander l'exécution d'une application dans un environnement informatique virtuel
CN105577381A (zh) * 2014-10-24 2016-05-11 中兴通讯股份有限公司 虚拟化下的证书管理方法和装置
CN105847237A (zh) * 2016-03-15 2016-08-10 中国联合网络通信集团有限公司 一种基于nfv的安全管理方法和装置
US9578008B2 (en) * 2015-05-11 2017-02-21 Intel Corporation Technologies for secure bootstrapping of virtual network functions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104134122A (zh) * 2014-07-30 2014-11-05 华为技术有限公司 一种许可证申请方法及装置
EP3002699A1 (fr) * 2014-09-30 2016-04-06 Alcatel Lucent Procédé pour commander l'exécution d'une application dans un environnement informatique virtuel
CN105577381A (zh) * 2014-10-24 2016-05-11 中兴通讯股份有限公司 虚拟化下的证书管理方法和装置
US9578008B2 (en) * 2015-05-11 2017-02-21 Intel Corporation Technologies for secure bootstrapping of virtual network functions
CN105847237A (zh) * 2016-03-15 2016-08-10 中国联合网络通信集团有限公司 一种基于nfv的安全管理方法和装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11663298B2 (en) * 2019-12-11 2023-05-30 At&T Intellectual Property I, L.P. Managing enterprise software licenses for virtual network functions
FR3112049A1 (fr) * 2020-06-29 2021-12-31 Orange Procédé de gestion collaborative de licences entre domaines industriels
WO2022003282A1 (fr) * 2020-06-29 2022-01-06 Orange Procede de gestion collaborative de licences entre domaines industriels
CN114371921A (zh) * 2021-12-31 2022-04-19 天翼物联科技有限公司 License调度系统、方法、装置及存储介质
GB2622768A (en) * 2022-08-16 2024-04-03 Awtg Ltd A system for handling data within a mobile data network
CN119520296A (zh) * 2024-11-06 2025-02-25 中电信数智科技有限公司 一种在vi层实现nfv网元快速扩缩容的方法、系统、设备和存储介质

Also Published As

Publication number Publication date
CN108574593A (zh) 2018-09-25
CN108574593B (zh) 2019-11-15

Similar Documents

Publication Publication Date Title
WO2018166398A1 (fr) Système de gestion de licence dans un réseau nfv
CN111385114B (zh) Vnf服务实例化方法及装置
US20250016161A1 (en) Method and System for Secure Container Application Framework
EP3059900B1 (fr) Procede et dispositif de gestion de modele de service de reseau
CN115328663A (zh) 基于PaaS平台进行资源调度的方法、装置、设备和存储介质
CN109478134A (zh) 用跨账户别名执行按需网络代码
WO2017012381A1 (fr) Procédé et appareil de gestion de cycle de vie
CN112631728B (zh) 联盟链的链码容器管理方法、装置、设备及存储介质
US20220413937A1 (en) Node management method, device and apparatus, storage medium, and system
WO2014101475A1 (fr) Procédé et appareil de déploiement d'application de plateforme en nuage
CN107959582A (zh) 一种切片实例的管理方法及装置
CN103458055A (zh) 一种云计算平台
CN112099917B (zh) 调控系统容器化应用运行管理方法、系统、设备及介质
JP2024501005A (ja) コンテナクラスタのための管理方法および装置
US11301284B2 (en) Method for managing VNF instantiation and device
WO2020001162A1 (fr) Procédé, appareil et dispositif de gestion de conteneur
US20160352843A1 (en) Data Processing Method, Device, and ESB System
CN105103125B (zh) 时钟中断信号的获取方法和nfv装置
WO2016197953A1 (fr) Procédé et dispositif de déploiement de station de base multi-mode
CN117857283A (zh) 网元管理方法、装置、存储介质及电子装置
CN115328608A (zh) 一种Kubernetes容器垂直伸缩调节方法和装置
CN111767345B (zh) 建模数据同步方法、装置、计算机设备及可读存储介质
CN115562796A (zh) 容器集群的存储资源管理方法、装置及系统
CN113923257A (zh) 容器组实例终止和创建方法、装置、电子设备和存储介质
CN109257201B (zh) 一种License的发送方法和装置

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

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

Country of ref document: EP

Kind code of ref document: A1