CN109218259B - License management method and device, APPLM functional entity and computer readable storage medium - Google Patents
License management method and device, APPLM functional entity and computer readable storage medium Download PDFInfo
- Publication number
- CN109218259B CN109218259B CN201710531014.XA CN201710531014A CN109218259B CN 109218259 B CN109218259 B CN 109218259B CN 201710531014 A CN201710531014 A CN 201710531014A CN 109218259 B CN109218259 B CN 109218259B
- Authority
- CN
- China
- Prior art keywords
- license
- management
- file
- functional entity
- permission
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Stored Programmes (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a permission management method, which provides an application permission management function entity in a network function virtualization architecture and comprises the following steps: the application permission management functional entity receives a permission file and a permission management strategy; and when the application permission management functional entity receives an operation request based on a virtual network function instance, performing corresponding management operation on the permission file based on the permission management strategy. The invention also discloses a license management device, an application license management functional entity and a computer readable storage medium. The invention can realize the dynamic management of the license file in a virtual scene, and achieves the purpose of improving the effective utilization rate of the license file.
Description
Technical Field
The present invention relates to the field of network function virtualization, and in particular, to a method and an apparatus for license management, an APPLM function entity and a computer-readable storage medium.
Background
With the gradual application of network function virtualization technology in the field of telecommunications, network equipment manufacturers gradually separate network function devices into software and hardware in order to meet virtualization requirements, so that software virtualization is realized, and dynamic characteristics such as elasticity, self-healing and migration are supported. After the software and the hardware are decoupled, the hardware and the software can be purchased respectively. The license file of the virtual network function instance of the communication equipment company is gradually stripped from the hardware binding to become a license file of the supporting software. However, after the operator purchases the license file and the virtual network function instance of the manufacturer, due to the lack of a dynamic management mechanism for the license file, a certain obstacle is generated to the operator to effectively utilize the license file as required.
Disclosure of Invention
The invention mainly aims to provide a license management method and device, an APPLM functional entity and a computer readable storage medium, aiming at improving the effective utilization rate of a license file.
In order to achieve the above object, the present invention provides a license management method, which first adds an APPLM functional entity in a network function virtualization architecture, and the license management method includes:
the application permission management functional entity receives a permission file and a permission management strategy;
and when the application permission management functional entity receives an operation request based on a virtual network function instance, performing corresponding management operation on the permission file based on the permission management strategy.
Further, the present invention also provides a license management apparatus, applied to an APPLM functional entity, the license management apparatus including:
the receiving module is used for receiving the license file and the license management strategy;
and the management module is used for performing corresponding management operation on the license file based on the license management strategy when receiving an operation request based on a virtual network function instance.
Further, the present invention also provides an APPLM functional entity, which includes:
a memory storing a license management program;
a processor configured to execute the license management program to implement the steps of:
receiving a license file and a license management policy;
and when an operation request based on a virtual network function instance is received, performing corresponding management operation on the license file based on the license management policy.
Further, the present invention also provides a computer-readable storage medium having stored thereon a license management program which, when executed by a processor, implements the steps of:
receiving a license file and a license management policy;
and when an operation request based on a virtual network function instance is received, performing corresponding management operation on the license file based on the license management policy.
According to the invention, the APPLM function entity is newly added in the network function virtualization framework, the APPLM function entity receives the license file and the license management strategy, and when an operation request based on a virtual network function instance is received, the license file is correspondingly managed based on the license management strategy, so that the dynamic management of the license file in a virtualization scene is realized, and the effective utilization rate of the license file can be improved.
Drawings
Fig. 1 is a schematic diagram of an alternative hardware structure of an APPLM functional entity according to the present invention;
FIG. 2 is a flowchart illustrating a license management method according to a first embodiment of the present invention;
FIG. 3 is a diagram illustrating an exemplary architecture of a Network Function Virtualization (NFV) according to a first embodiment of the license management method of the present invention;
fig. 4 is a schematic diagram illustrating the deployment of SLO functional entities and APPLM functional entities in a second embodiment of the license management method according to the present invention;
FIG. 5 is a block diagram of a license management device according to a first embodiment of the present invention.
The objects, features, and advantages of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The main solution of the embodiment of the invention is as follows: by newly adding the APPLM function entity in the network function virtualization framework, receiving the license file and the license management strategy by the APPLM function entity, and performing corresponding management operation on the license file based on the license management strategy when receiving an operation request based on a virtual network function instance, the dynamic management of the license file in a virtualization scene is realized, and the effective utilization rate of the license file can be improved.
As shown in fig. 1, fig. 1 is a schematic hardware structure diagram of an APPLM functional entity of a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the APPLM functional entity may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface, and the like. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the APPLM functional entity structure shown in fig. 1 does not constitute a limitation of the APPLM functional entity, and may include more or less components than those shown, or combine certain components, or a different arrangement of components.
As shown in fig. 1, in an embodiment of the APPLM functional entity of the present invention, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a license management program.
In the APPLM functional entity shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server and performing data communication with the background server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to invoke the license management program stored in the memory 1005 and perform the following operations:
receiving a license file and a license management policy;
and when an operation request based on the virtual network function instance is received, performing corresponding management operation on the license file based on the license management policy.
Further, the processor 1001 may be configured to invoke a license management program stored in the memory 1005, and also perform the following operations:
and when a permission file issuing request based on the virtual network function instance is received and the permission file issuing request accords with a permission management strategy, issuing a permission file corresponding to the permission file issuing request to the virtual network function instance for loading and using the virtual network function instance.
Further, the processor 1001 may be configured to invoke a license management program stored in the memory 1005, and also perform the following operations:
when a license file updating request based on the virtual network function instance is received and the license file updating request accords with a license management policy, a license file corresponding to the license file updating request is issued to the virtual network function instance, so that the virtual network function instance replaces the loaded license file with the license file corresponding to the license file updating request.
Further, when the APPLM functional entity provides an Ncmf interface defined based on preset criteria, the processor 1001 may be configured to call the license management program stored in the memory 1005, and further perform the following operations:
and when a license file recovery request based on the virtual network function instance is received and the license file recovery request conforms to the license management policy, recovering the loaded license file of the virtual network function instance.
Further, a service license organizer function entity is also provided in the network function virtualization architecture, and the processor 1001 may be configured to invoke a license management program stored in the memory 1005, and further perform the following operations:
receiving a license file and a license management policy input by a service license organizer functional entity, wherein the license management policy is generated by the service license organizer functional entity based on the received software instance information and service instance information configuration of different levels;
after performing the corresponding management operation on the license file based on the license management policy, returning an operation result of the management operation to the service license orchestrator function entity.
Further, the processor 1001 may be configured to invoke a license management program stored in the memory 1005, and also perform the following operations:
when only a license file input by a service license organizer functional entity is received and an operation request based on a virtual network function instance is received, sending a corresponding operation authorization request to the service license organizer functional entity;
when receiving the confirmation information of the operation authorization request returned by the service permission orchestrator functional entity, performing corresponding management operation on the permission file;
when the service permission orchestrator functional entity determines that the operation authorization request conforms to the permission management policy generated by the configuration of the service permission orchestrator functional entity, the service permission orchestrator functional entity returns confirmation information to the application permission management functional entity.
Further, the processor 1001 may be configured to invoke a license management program stored in the memory 1005, and also perform the following operations:
and monitoring the change information of the permission file, and outputting alarm information when the change information meets the preset condition.
Further, the present invention also provides a license management method applied to an APPLM functional entity, and referring to fig. 2, in a first embodiment of the license management method of the present invention, the license management method includes:
step S10, the APPLM function entity receives the license file and the license management policy;
in step S20, when receiving the operation request based on the virtual network function instance, the APPLM function entity performs corresponding management operation on the license file based on the license management policy.
For the convenience of understanding the solution of the present invention, the network function virtualization NFV architecture related to the present invention is first described below, and as shown in fig. 3, the NFV architecture is composed of the following functional components:
the NFV Infrastructure (NFVI) provides The virtualized resources needed to support The execution of NFV, including The hardware for Commercial Off The Shelf (COTS), The necessary accelerator components, and a software layer that virtualizes and abstracts The underlying hardware.
The VNF is a software implementation of a Network Function (NF) that can run on the NFVI, and may be accompanied by an Element Management System (EMS) module to understand and manage the individual VNF and its characteristics. VNFs are entities of network nodes that are expected to be delivered in pure software free of hardware dependence.
NFV Management and Orchestration (M & O or MANO) includes Orchestration, lifecycle Management of physical and/or software resources supporting infrastructure virtualization, and lifecycle Management of VNFs. The NFV MANO focuses on virtualizing specific management tasks in the NFV framework. The NFV MANO also interacts with an Operation Support System (OSS)/Business Support System (BSS) (external to the NFV) to allow the NFV to be integrated into an existing management landscape that relates to the network-wide.
The above components interact through defined reference points and interfaces so that different entities can be clearly decoupled, resulting in an open and innovative NFV ecosystem. The reference point between the VNF and the NFVI (and between NFVI internal entities) handles the abstraction and virtualization of resources, as well as host hosting of the VNF, so that the VNF can not only move from one to another in the NFVI, but also can ensure that it is possible to choose different underlying hardware. The reference point between the NFV MANO and VNF and NFVI (and between NFV MANO internal entities) handles the management and operation of the NFV system. The design of the related components allows to reuse existing solutions (e.g. cloud management systems) and also to interact with existing OSS/BSS environments to which NFV systems need to be connected.
In addition, the following functional components are further defined within NFV MANO:
NFVO, mainly responsible for NS life cycle management, complete the network business arrangement function; and performing NFVI resource arrangement across multiple VIMs to complete the resource arrangement function.
VNFMs, which are responsible for lifecycle management of VNF instances, each VNF is assumed to have an associated VNFM, which may be assigned to manage a single VNF instance or to manage multiple VNF instances of the same or different types. Its available capabilities include: VNF instantiation, VNF configuration NFVI resources, VNF instance update, VNF instance scaling, collection and association of VNF instance related NFVI performance metrics and events with VNF instance related events, VNF instance assisted or automated healing, VNF instance termination, integrity management of VNF instances throughout their lifecycle, acting as global coordination and adaptation for configuration and event reporting between NFVI and EMS, etc.
The VIM, responsible for controlling and managing the NFVI's computing, storage, and network resources, is typically within an operator's infrastructure sub-domain. One VIM may be dedicated to handling certain types of NFVI resources or may manage multiple types of NFVI resources. Its available capabilities include: allocating/upgrading/deallocating/recycling NFVI resources, managing the association of virtualized resources with computing, storage and network resources; a directory that manages hardware resources (computing, storage, network) and software resources (e.g., a hypervisor); collecting and forwarding performance metrics and events for virtualized resources, and the like.
On the basis of the above-described architecture, an NS having a specific function can be implemented by a plurality of NFs. The end-to-end NS of a traditional Network implementation is made up entirely of Physical Network Functions (PNFs). End-to-end NS implemented in NFV is typically still PNF at both ends, while the middle is replaced with VNF in whole or in part. The functionality and external interface implemented by each NF is independent of whether it is a PNF or a VNF. The topological relationship formed by the links between the VNF and the PNF may be described by using a VNF Forwarding Graph (VNFFG), and the characteristics of each NF are described by a corresponding Network Function Descriptor (NFD).
VNF needs to be implemented based on NFVI-provided virtual resources (including virtual computing, storage, and network resources) that are virtualized from corresponding physical resources. PNF is then directly implemented based on physical resources. Unlike the traditional network in which all control is concentrated on a network device with integrated software and hardware, NFV introduces virtualization to implement software and hardware decoupling of the network device, so that control over services is mainly embodied on the PNF and VNF level, and control over performance is mainly embodied on the NFVI, particularly on the hardware resource level therein.
In specific implementation, an operator first deploys the APPLM functional entity, and specifically, the APPLM functional entity may be deployed alone or together with other functional entities, for example, the APPLM functional entity and the VNFM may be deployed together.
Thereafter, the operator may purchase the license file of the relevant application from the VNF vendor according to actual needs, and design the license management policy according to actual needs, for example, the license management policy (including but not limited to on-demand license file application, license file quantitative application, license file maximum/minimum capacity limit, license file capacity limit per application, priority, threshold alarm notification, etc.) may be configured and generated according to service instance information (including but not limited to network service, slice, sub-slice, etc.) and software instance information (including but not limited to VNF instance, EMS instance, NFVO instance, VNFM instance, VIM instance, etc.).
After preparing the license file and the license management policy for the license file, the operator may establish a communication connection with the deployed APPLM function entity through a control terminal (e.g., a computer device such as a PC, a notebook computer, etc.), and transmit the license file and the license management policy to the APPLM function entity.
Correspondingly, the APPLM functional entity receives the license file and the license management policy, and stores the received license file and the license management policy in the memory 1005 after receiving the license file and the license management policy, wherein for a specific storage manner, the embodiment of the present invention is not limited, and can be selected by a person skilled in the art according to actual needs.
After the storage of the license file and the license management policy is completed, the APPLM functional entity may manage the license file, specifically, the APPLM functional entity receives an operation request based on the VNF instance, and performs a corresponding management operation on the license file based on the license management policy when receiving the operation request based on the VNF instance. It should be noted that the foregoing operation request based on the VNF instance may be from the VNF instance itself, or from other functional entities, or the operation request may be sent to the APPLM functional entity by the operator directly through the control terminal.
For example, the VNF instance dynamically creates and the like, and the VNF instance generates a license file issue request and sends the license file issue request to the APPLM functional entity, and requests the license file from the APPLM functional entity; for another example, the VNF instance dynamically self-heals, migrates, or performs operations such as elasticity, and the VNF instance generates a license file update request and sends the license file update request to the APPLM functional entity, and requests the APPLM functional entity to update the loaded license file; for another example, the VNF instance dynamically deletes, and the like, and the VNFM generates and sends the license file recycle request to the APPLM functional entity.
In a specific implementation, the operation request based on the VNF instance includes at least one of a license file issuing request, a license file updating request, and a license file recycling request, and step S20 includes:
when a license file issuing request based on a VNF (virtual network configuration) instance is received and the license file issuing request conforms to a license management policy, the APPLM (application platform management) functional entity issues a license file corresponding to the license file issuing request to the VNF instance for loading and using the VNF instance;
or when receiving a license file update request based on the VNF instance and the license file update request conforms to the license management policy, the APPLM functional entity issues the license file corresponding to the license file update request to the VNF instance, so that the VNF instance replaces the loaded license file with the license file corresponding to the license file update request;
or, when a license file recovery request based on the VNF instance is received and the license file recovery request conforms to the license management policy, the APPLM function entity recovers the license file loaded by the VNF instance.
In this embodiment, when the APPLM functional entity receives whether any of the foregoing VNF instance-based operation requests complies with the license management policy, if yes, it is determined that a management operation corresponding to the operation request can be performed, including at least one of a license file issuing operation, a license file updating operation, and a license file recycling operation.
Further, in this embodiment, the method further includes the following steps:
and the APPLM functional entity monitors the change information of the permission file and outputs alarm information when the change information meets the preset condition.
In the embodiment, the APLLM functional entity also monitors the usage of the license file in real time, provides the usage conditions of different granularities, including but not limited to instances (service, software), packages (service, software), and equipment vendors, and outputs the alarm information when abnormal. Specifically, the preset condition corresponding to the abnormal use of the license file and the alarm information corresponding to the abnormal condition are preset, and may be specifically set by a person skilled in the art according to actual needs, and the present invention is not particularly limited. For example, the preset condition is "for the same VNF instance, 5 times of license file update requests based on the VNF instance are received within one hour"; for another example, the preset condition is set to "for the same VNF instance, a license file issue request and a license file recycle request based on the VNF instance are received within one hour"
And then, the APPLM functional entity monitors the change information of the permission file and outputs corresponding alarm information of abnormal conditions when the change information meets the preset conditions.
Further, based on the first embodiment, a second embodiment of the license management method of the present invention is proposed, in this embodiment, a service license orchestrator function SLO functional entity is further provided in the NFV architecture, and step S10 includes:
the APPLM functional entity receives a license file and a license management policy which are input by the SLO functional entity, wherein the license management policy is generated by the SLO functional entity based on the received software instance information and service instance information configuration of different levels;
after step S20, the method further includes:
and the APPLM functional entity returns the operation result of the management operation to the SLO functional entity.
It should be noted that, in this embodiment, when an operator deploys an APPLM functional entity, the operator also deploys an SLO functional entity at the same time, so as to complete management of the license file through interaction between the APPLM functional entity and the SLO functional entity. When the SLO functional entity is deployed, the SLO functional entity may be specifically deployed alone, or may be deployed together with other functional entities, for example, the SLO functional entity and the NFVO may be deployed together.
Different from the first embodiment, in this embodiment, after the operator acquires the license file, the operator firstly introduces the license file into the SLO functional entity through the control terminal, and then inputs the license file into the APPLM functional entity based on the SLO functional entity. On the other hand, the operator enters service instance information (including but not limited to network services, slices, sub-slices and the like) and software instance information (including but not limited to VNF instances, EMS instances, NFVO instances, VNFM instances, VIM instances and the like) into the SLO function entity through the control terminal, configures and generates a license management policy (including but not limited to on-demand license file application, quantitative license file application, maximum/minimum license file capacity restriction, license file capacity restriction application each time, priority, threshold alarm notification and the like) by the SLO function entity, and then inputs the configured and generated license management policy into the APPLM function entity based on the SLO function entity.
Accordingly, the APPLM functional entity receives the license file and the license management policy input by the SLO functional entity.
Further, in this embodiment, the SLO functional entity may also control the management policy, and the APPLM functional entity is responsible for specific execution, and after step S10, the method further includes:
when only receiving the license file input by the SLO functional entity and receiving an operation request based on a VNF instance, the APPLM functional entity sends a corresponding operation authorization request to the SLO functional entity;
when receiving the confirmation information of the operation authorization request returned by the SLO functional entity, performing corresponding management operation on the license file;
and the SLO functional entity returns confirmation information to the APPLM functional entity when determining that the operation authorization request conforms to the license management strategy generated by the configuration of the SLO functional entity.
In summary, referring to fig. 4, in the embodiment, the SLO functional entity provides network-wide license usage and overall policy control for the operator. The SLO is responsible for the unified life cycle management of the license files at the service level, including providing the management of the license files at the level of a slice, a sub-slice or a network service, and needs to support the unified management across manufacturers. Usage includes instance latitude usage such as slices, subslices, applications, etc., and purchase granularity usage such as vendor & product, etc. The SLO functional entity uniformly controls the usage amount of the license file of the slice and the application software, combines with other external systems, makes a strategy and dynamically authorizes the resource distribution of the license file.
The APPLM functional entity is responsible for license file management at a software level, and comprises VNF, PNF, EMS, VNFM, NFVO, VIM, or other software. The APPLM functional entity is responsible for the license file management of specific software and provides the programmable capability of the software license file for the SLO functional entity.
Further, the present invention also provides a license management apparatus, applied to an APPLM functional entity, for executing the license management methods of the foregoing embodiments, referring to fig. 5, in an embodiment of the license management apparatus of the present invention, the license management apparatus includes:
a receiving module 10, configured to receive a license file and a license management policy;
and the management module 20 is configured to, when receiving an operation request based on the VNF instance, perform a corresponding management operation on the license file based on the license management policy.
Further, when the received operation request is a license file issue request, the management module 20 is further configured to, when the license file issue request based on the VNF instance is received and the license file issue request conforms to the license management policy, issue the license file corresponding to the license file issue request to the VNF instance for loading and using by the VNF instance.
Further, when the received operation request is a license file update request, the management module 20 is further configured to, when a license file update request based on the VNF instance is received and the license file update request conforms to the license management policy, issue the license file corresponding to the license file update request to the VNF instance, so that the VNF instance replaces the loaded license file with the license file corresponding to the license file update request.
Further, when the received operation request is a license file recycle request, the management module 20 is further configured to recycle the license file loaded by the VNF instance when the VNF instance-based license file recycle request is received and the license file recycle request conforms to the license management policy.
Further, an SLO functional entity is provided in the NFV architecture, and the receiving module 10 is further configured to receive a license file input by the SLO functional entity and a license management policy, where the license management policy is generated by the SLO functional entity based on the received software instance information and service instance information configuration of different levels;
the management module 20 is further configured to return an operation result of the management operation to the SLO functional entity after performing a corresponding management operation on the license file based on the license management policy.
Further, the management module 20 is further configured to, when the receiving module 10 receives only the license file input by the SLO functional entity and receives the operation request based on the VNF instance, send a corresponding operation authorization request to the SLO functional entity; the SLO function entity is also used for carrying out corresponding management operation on the license file when receiving the confirmation information of the operation authorization request returned by the SLO function entity; and the SLO functional entity returns confirmation information when determining that the operation authorization request conforms to the license management policy generated by the configuration of the SLO functional entity.
Furthermore, the license management device also comprises a monitoring module which is used for monitoring the change information of the license file and outputting the alarm information when the change information meets the preset condition.
Further, the present invention also provides a computer readable storage medium, which in one embodiment has a license management program stored thereon, and when executed by the processor 1001, the license management program implements the following operations:
receiving a license file and a license management policy;
when an operation request based on the VNF instance is received, corresponding management operation is carried out on the license file based on the license management policy.
Further, when executed by the processor 1001, the license management program further implements the following operations:
and when a license file issuing request based on the VNF instance is received and the license file issuing request conforms to the license management policy, issuing the license file corresponding to the license file issuing request to the VNF instance for loading and using of the VNF instance.
Further, when executed by the processor 1001, the license management program further implements the following operations:
when a license file updating request based on the VNF instance is received and the license file updating request conforms to the license management policy, the license file corresponding to the license file updating request is issued to the VNF instance, so that the VNF instance can replace the loaded license file with the license file corresponding to the license file updating request.
Further, when executed by the processor 1001, the license management program further implements the following operations:
and when a license file recovery request based on the VNF instance is received and the license file recovery request conforms to the license management policy, recovering the license file loaded by the VNF instance.
Further, when executed by the processor 1001, the license management program further implements the following operations:
receiving a license file input by the SLO functional entity and a license management policy, wherein the license management policy is generated by the SLO functional entity based on the received software instance information and service instance information configuration of different levels;
after performing corresponding management operations on the license file based on the license management policy, returning operation results of the management operations to the SLO functional entity.
Further, an SLO function entity is also provided in the network function virtualization architecture, and when the aforementioned license management program is executed by the processor 1001, the following operations are also implemented:
when only a license file input by the SLO functional entity is received and an operation request based on a VNF instance is received, sending a corresponding operation authorization request to the SLO functional entity;
when receiving the confirmation information of the operation authorization request returned by the SLO functional entity, performing corresponding management operation on the license file;
and when the SLO functional entity determines that the operation authorization request conforms to the license management policy generated by the configuration of the SLO functional entity, the SLO functional entity returns confirmation information to the application license management functional entity.
Further, when executed by the processor 1001, the license management program further implements the following operations:
and monitoring the change information of the permission file, and outputting alarm information when the change information meets the preset condition.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above and includes several instructions for causing an APPLM functional entity to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A license management method for providing an application license management function entity in a network function virtualization architecture, the license management method comprising the steps of:
the application permission management functional entity receives a permission file and a permission management strategy;
when the application permission management functional entity receives an operation request based on a virtual network function instance, the corresponding management operation is carried out on the permission file based on the permission management strategy;
also provided is a service license orchestrator function in a network functions virtualization architecture, the step of receiving a license file and a license management policy by the application license management function comprising:
the application license management function entity receives the license file and the license management policy input by the service license organizer function entity, wherein the license management policy is generated by the service license organizer function entity based on the received software instance information and service instance information configuration of different levels.
2. The license management method according to claim 1, wherein when the operation request is a license file issue request, the step of performing corresponding management operation on the license file based on the license management policy includes:
and when a permission file issuing request based on the virtual network function instance is received and the permission file issuing request conforms to the permission management policy, the application permission management function entity issues the permission file corresponding to the permission file issuing request to the virtual network function instance for loading and using of the virtual network function instance.
3. The license management method according to claim 1, wherein, when the operation request is a license file update request, the step of performing corresponding management operation on the license file based on the license management policy includes:
when a license file updating request based on the virtual network function instance is received and the license file updating request conforms to the license management policy, the application license management function entity issues a license file corresponding to the license file updating request to the virtual network function instance, so that the virtual network function instance replaces the loaded license file with the license file corresponding to the license file updating request.
4. The license management method according to claim 1, wherein, when the operation request is a license file recycle request, the performing corresponding management operation on the license file based on the license management policy includes:
when a license file recycling request based on the virtual network function instance is received and the license file recycling request conforms to the license management policy, the application license management function entity recycles the license file loaded by the virtual network function instance.
5. The license management method according to any one of claims 1 to 4,
after the step of performing the corresponding management operation on the license file based on the license management policy, the method further includes:
and the application permission management functional entity returns the operation result of the management operation to the service permission orchestrator functional entity.
6. The license management method according to claim 5, wherein after the step of receiving the license file and the license management policy by the application license management functional entity, the method further comprises:
when the application permission management functional entity receives only the permission file input by the service permission orchestrator functional entity and receives an operation request based on a virtual network function instance, the application permission management functional entity sends a corresponding operation authorization request to the service permission orchestrator functional entity;
when receiving the confirmation information of the operation authorization request returned by the service permission orchestrator functional entity, performing corresponding management operation on the permission file;
and when the service permission orchestrator functional entity determines that the operation authorization request conforms to the permission management policy generated by the configuration of the service permission orchestrator functional entity, returning confirmation information to the application permission management functional entity.
7. The license management method according to any one of claims 1 to 4, characterized in that the license management method further comprises:
and the application permission management functional entity monitors the change information of the permission file and outputs alarm information when the change information meets the preset condition.
8. A license management apparatus applied to an application license management function entity, the license management apparatus comprising:
the receiving module is used for receiving the license file and the license management strategy;
the management module is used for performing corresponding management operation on the license file based on the license management strategy when receiving an operation request based on a virtual network function instance;
providing a service license orchestrator function entity in a network function virtualization architecture;
the receiving module is further configured to receive a license file and a license management policy, which are input by the service license organizer functional entity, where the license management policy is generated by the service license organizer functional entity based on the received software instance information and service instance information configuration of different levels.
9. An application license management function entity, wherein a service license orchestrator function entity is provided in a network function virtualization architecture, the application license management function entity comprising:
a memory storing a license management program;
a processor configured to execute the license management program to implement the steps of:
receiving a license file and a license management policy;
when an operation request based on a virtual network function instance is received, performing corresponding management operation on the license file based on the license management policy;
receiving a license file and a license management policy input by the service license orchestrator functional entity, wherein the license management policy is generated by the service license orchestrator functional entity based on the software instance information received by the service license orchestrator functional entity and different levels of service instance information configuration.
10. A computer-readable storage medium providing a serving license organizer functional entity in a network functions virtualization architecture, the computer-readable storage medium having a license management program stored thereon, the license management program when executed by a processor implementing the steps of:
receiving a license file and a license management policy;
when an operation request based on a virtual network function instance is received, performing corresponding management operation on the license file based on the license management policy;
receiving a license file input by a service license organizer functional entity and a license management policy, wherein the license management policy is generated by the service license organizer functional entity based on software instance information received by the service license organizer functional entity and different levels of service instance information configuration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710531014.XA CN109218259B (en) | 2017-06-30 | 2017-06-30 | License management method and device, APPLM functional entity and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710531014.XA CN109218259B (en) | 2017-06-30 | 2017-06-30 | License management method and device, APPLM functional entity and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109218259A CN109218259A (en) | 2019-01-15 |
| CN109218259B true CN109218259B (en) | 2022-03-29 |
Family
ID=64992519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710531014.XA Active CN109218259B (en) | 2017-06-30 | 2017-06-30 | License management method and device, APPLM functional entity and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109218259B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112584337B (en) * | 2019-09-29 | 2022-10-11 | 华为技术有限公司 | Charging method and device for network slice |
| CN115134232B (en) * | 2022-07-04 | 2024-02-23 | 深信服科技股份有限公司 | Virtual router management method, device, system and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104134122A (en) * | 2014-07-30 | 2014-11-05 | 华为技术有限公司 | Method and device for applying for license |
| CN105282195A (en) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | Network service providing, strategy rule evaluating and service component selecting method and device |
| CN105450601A (en) * | 2014-08-19 | 2016-03-30 | 华为技术有限公司 | Method and device for sharing license |
| EP3002699A1 (en) * | 2014-09-30 | 2016-04-06 | Alcatel Lucent | A method for controlling the execution of an application in a virtual computer environment |
| CN106331011A (en) * | 2015-06-30 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for sharing license resource between multiple virtual network functions |
| CN106534084A (en) * | 2016-10-24 | 2017-03-22 | 东软集团股份有限公司 | Admission control method and equipment |
-
2017
- 2017-06-30 CN CN201710531014.XA patent/CN109218259B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105282195A (en) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | Network service providing, strategy rule evaluating and service component selecting method and device |
| CN104134122A (en) * | 2014-07-30 | 2014-11-05 | 华为技术有限公司 | Method and device for applying for license |
| CN105450601A (en) * | 2014-08-19 | 2016-03-30 | 华为技术有限公司 | Method and device for sharing license |
| EP3002699A1 (en) * | 2014-09-30 | 2016-04-06 | Alcatel Lucent | A method for controlling the execution of an application in a virtual computer environment |
| CN106331011A (en) * | 2015-06-30 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for sharing license resource between multiple virtual network functions |
| CN106534084A (en) * | 2016-10-24 | 2017-03-22 | 东软集团股份有限公司 | Admission control method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109218259A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11875173B2 (en) | Execution of auxiliary functions in an on-demand network code execution system | |
| JP7275171B2 (en) | Operating System Customization in On-Demand Network Code Execution Systems | |
| US10637796B2 (en) | Linking instances within a cloud computing environment | |
| CN109478134B (en) | Executing on-demand network code with cross-account aliases | |
| US20190391841A1 (en) | Execution of auxiliary functions in an on-demand network code execution system | |
| AU2015419073B2 (en) | Life cycle management method and device for network service | |
| CN106537338B (en) | Self-expanding clouds | |
| US10719348B2 (en) | Network function virtualization management and orchestration apparatus, method, and program | |
| JP2021529386A (en) | Execution of auxiliary functions on the on-demand network code execution system | |
| EP3249860A1 (en) | Method, device, and program for management and orchestration of network functions virtualization | |
| US8104038B1 (en) | Matching descriptions of resources with workload requirements | |
| CN112256423A (en) | System, apparatus, and process for dynamic tenant fabric adjustment in a distributed resource management system | |
| CA2974629A1 (en) | Network functions virtualization management and orchestration method, network functions virtualization management and orchestration system, and program | |
| US11363117B2 (en) | Software-specific auto scaling | |
| US9912760B2 (en) | Dynamically generating solution stacks | |
| US20180309638A1 (en) | Discovering and publishing device changes in a cloud environment | |
| CN106663012B (en) | Hardware acceleration method and related equipment | |
| US20190310887A1 (en) | Optimizing timeouts and polling intervals | |
| US10999160B2 (en) | Monitoring dynamic quality of service based on changing user context | |
| CN111443985A (en) | Method and equipment for instantiating virtual network function | |
| CN109218259B (en) | License management method and device, APPLM functional entity and computer readable storage medium | |
| US11750451B2 (en) | Batch manager for complex workflows | |
| CN116724543A (en) | Container cluster management method and device | |
| CN111857736B (en) | Cloud computing product generation method, device, equipment and storage medium | |
| JP2014126940A (en) | Cloud configuration management support system, cloud configuration management support method and cloud configuration management support program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |