WO2009109119A1

WO2009109119A1 - License controlling method and managing device

Info

Publication number: WO2009109119A1
Application number: PCT/CN2009/070470
Authority: WO
Inventors: 贺建斌; 谢永政
Original assignee: 华为技术有限公司
Priority date: 2008-03-03
Filing date: 2009-02-19
Publication date: 2009-09-11
Also published as: CN101247400A; CN101247400B

Abstract

A License controlling method involves providing service to a client terminal by using the first license; starting the second license according to the second license trigger condition; authorizing the second license to the client terminal. There is also a license managing device. The method and the device are capable of performing different authorizing licenses to the client terminal in different time segments, or performing different authorizing licenses to the client terminal at different business circumstances.

Description

License control method and management device

The present application claims priority to Chinese Patent Application No. 200810083101.4, entitled "License Control Method and Management Device", filed on March 3, 2008, the entire contents of which is incorporated herein by reference. .

Technical field

The present invention relates to the field of network technologies, and in particular, to a license control method and a license management apparatus.

Background technique

With the rapid development of network technology, devices and software based on license (License, also known as authorization) are used more and more widely. The supplier sells the product to the customer, authorizing the scope of use, resources, functions, and duration of the product through a license. Simply put, a license is a form of contract that a supplier authorizes the scope, resources, functions, and duration of the products being sold.

Generally, the network that implements the license control includes a license server and several clients, as shown in Figure 1. The license control is that the license server on the network loads the license file and communicates with the client to manage the authorization of the client, thereby implementing centralized control of the license server for all client licenses.

A license control method in the prior art includes the following processes:

Step 101: The license server loads and enables the license file, and establishes an authorization database. Step 102: The client requests a resource authorization or a function license from the license server. Step 103: The license server determines whether the loaded license authorization period expires. The period returns to failure, otherwise proceeds to step 104;

Step 104: If the client sends a resource authorization request, the license server calculates whether the sum of the resource used by the client and the resource requested by the client is greater than the value of the licensable resource in the license file, if the value is less than or equal to the license file. If the resource value can be authorized, the license server returns the resource authorization of the specified size to the client; otherwise, the return of the client authorization fails;

If the license is requested, the license server searches for the function license of the application in the license file. If it is open, the return authorization is successful, otherwise the return fails.

In the research and practice of the prior art, the inventors found the following problems in the prior art: In the prior art, a single license is loaded, and the license is used regardless of the time period and the service requirement. With the development of the network, a single license cannot meet the requirements of fine-grained purchase and use authorization.

Summary of the invention

An embodiment of the present invention provides a license control method and a license management apparatus to implement authorization according to different time periods or different service requirements.

To solve the above technical problem, an embodiment of the present invention provides a license control method and a license management apparatus that are implemented as follows:

A method of license control, including:

Use the first license to provide services to the client;

Enable the second license according to the second license triggering condition;

Authorize the second license to the client.

A license management device includes:

a parsing unit, configured to force the first license and the second license;

a management unit, configured to enable the first license and enable the second license when the second license trigger condition is met;

The authorization unit authorizes the first license and the second license to the client.

The technical solution provided by the embodiment of the present invention can be used to detect the usage condition of the second license in the process of using the first license. When the usage management condition is met, the license management device enables the second license and authorizes the second license to the client. In this way, different licenses can be made to the client at different time periods. In particular, the use condition of the second license includes: enabling the second license when the initial use time of the second license is reached, or enabling the second license when the first license cannot provide the resource requested by the client and/or the requested function. Under the different conditions, the client can be licensed differently under different business conditions.

DRAWINGS

1 is a flow chart of a prior art license control method;

2 is a flow chart of an embodiment of a license control method of the present invention;

3 is a flow chart of another embodiment of a license control method according to the present invention;

4 is a flow chart of another embodiment of a license control method according to the present invention; FIG. 5 is a flowchart of another embodiment of a license control method according to the present invention; FIG.

6 is a flow chart of another embodiment of a license control method according to the present invention;

7 is a flow chart of another embodiment of a license control method according to the present invention;

Figure 8 is a block diagram of an embodiment of a server of the present invention;

Figure 9 is a block diagram of another embodiment of the server of the present invention;

Figure 10 is a block diagram of another embodiment of the server of the present invention;

Figure 11 is a block diagram of another embodiment of the server of the present invention;

Figure 12 is a block diagram of another embodiment of the server of the present invention;

Figure 13 is a block diagram of another embodiment of the server of the present invention;

Figure 14 is a block diagram of another embodiment of the server of the present invention;

Figure 15 is a block diagram of another embodiment of the server of the present invention;

Figure 16 is a block diagram of another embodiment of the server of the present invention;

Figure 17 is a block diagram of another embodiment of a server of the present invention.

detailed description

The embodiment of the invention provides a license control method and a license management device.

In order to enable those skilled in the art to better understand the present invention, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings and embodiments.

According to the new requirements generated above, different levels of licenses are set for users. For example, if there are at least two levels of licenses, the licenses of these two levels are called Normal License and Promotion Licensee! The Normal License can represent a license that satisfies the normal operation of the basic service. It contains the authorization of the resources and functions required for the basic tasks of the system to run normally, so that the client can continue to use related resources or functions when authorized. This Normal License is basically the same as in the prior art. The Promotion License represents an enhanced license, which can be an authorization to meet the resources and functions required for the operation of the service under certain conditions, such as an incremental authorization provided at a specific time or in the case of a specific service requirement. Alternatively, it may be an incremental authorization provided on the basis of the Normal License for an incremental grant within a certain period of time, or an authorization method for timing/counting use.

According to the user's needs, other levels of licenses may be included to provide licenses under certain conditions or circumstances, and the level and number of licenses included are not limited herein. Add a license customization interface to the license server. You can use different interfaces to set different licenses for different licenses. You can use different licenses under different specific conditions, such as setting a specific time or period. Normal License file, and use the Promotion License file at another specific time or period. In this way, the license server automatically uses the resources and functions in the Promotion License file during the custom time period.

Specifically, the added customized interface may be in the form of a configuration file, a script command, a graphical interface, or the like. In any case, you can configure the use of different licenses on the license server. Moreover, the information of these configurations can be directly saved in the corresponding license file, or saved in the license file.

The following describes an embodiment of the method of the present invention, which may include the following steps:

S 1: using the first license to provide services to the client;

S2: Enable the second license according to the second license triggering condition;

In the process of using the first license, if the trigger condition is met, the second license is enabled to provide the service. The trigger condition may be: detecting that the initial use time of the second license is set, or using the first license. Resources and/or features requested by the client cannot be provided.

S3: Authorize the second license to the client;

When the second license is authorized to the client, the client is not authorized to obtain the authorization of the first license. For example, the client can obtain the authorization of the first license and obtain the required resources and/or functions under the authorization. Then, the authorization of the second license is further obtained, and the incremental resources and/or functions are obtained. Alternatively, the client may obtain the authorization of the second license without obtaining the authorization of the first license, and the authorization scope of the second license may be Larger than the first license, so that the client can obtain incremental resources and/or functions by using the license of the second license.

S4: Stop the second license according to the second license stop condition;

The second license can be configured as follows: The usage time of the second license is reached, the usage of the second license is exhausted, and the usage of resources and/or functions in the second license is exhausted, or the first license can be used. The resources requested by the client and/or the functionality of the request. After stopping the second license, the service can be provided using only the first license.

One embodiment of the license control method of the present invention is described below. FIG. 2 shows a flow of an embodiment of the license control method of the present invention. As shown in FIG. 2, the method includes: Step 201: The monthly license is loaded with the Normal License and the Promotion License.

In this step, the server can also establish an authorization database based on the loaded Normal License and Promotion License.

The server can load at least two levels of licenses. Here is a description of loading the Normal License and the Promotion License.

Step 202: The server sets a usage period of the Promotion License through a customized interface. In this embodiment, the Normal License can be similar to the prior art, and is a licensee used by the server in daily situations.

The Promotion License is a license that is used during a specific period of time. Therefore, it is necessary to set the usage period of the Promotion License through the customized interface of the server.

Step 203: During the process of using the Normal License by the server, the custom use period of the Promotion License is detected, and the Promotion Licsnss is used when the start time of the time period arrives.

Step 204: The server sends an authorization notification to the client.

Since the server used the new license in the previous step, in this step, the server notifies the client to obtain authorization on the server, so that the client can obtain a new license on the server.

However, this step is not required, and the following step 205 may be directly performed.

Step 205: The client requests authorization from the server.

In this step, the client sends an authorization request to the server, requesting the server to authorize the resource or function.

Without performing step 204, the client may request authorization directly from the server if authorization is required, without having to wait for the notification from the server before requesting authorization from the server.

Step 206: The server authorizes the client and records the client authorization data.

It should be noted that step 206 may be directly performed without performing steps 204 and 205. In this way, after using the Promotion License, the server can directly license the Promotion License to the client.

Step 206 may further include:

Step 207: The server detects a usage period of the set Promotion License, and stops the Promotion License when the time period end time arrives. Step 208: The server notifies the client to return the authorization.

Similarly, this step is not necessary, and the following step 209 can be directly performed.

Step 209: The client requests the return of the authorization to the server.

In this step, the client requests the return of the resource or function to the server.

In the case where step 208 is not executed, the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server. In other embodiments, before the promotion of the Promotion License in step 207, the client may actively send a return authorization request to the server, so that in the case of a limited number of authorizations, the client-returned authorization may continue to be authorized to other clients. Improve license utilization and reduce the burden on the server.

Step 210: The server reclaims the authorization for the client Promotion License.

It should be noted that step 210 may be directly performed without performing steps 208 and 209. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.

Another embodiment of the license control method of the present invention is described below. Figure 3 shows the flow of another embodiment of the method, as shown in Figure 3, including:

Step 301: The monthly license is loaded with the Normal License and the Promotion License.

Step 302: The server sets the start time and duration of the Promotion License through a customized interface.

In this embodiment, the Normal License can be similar to the prior art, and is a license used by the server in a daily situation.

The Promotion License is a license that is used from a specific point in time. It can be used for a specific length of time. Therefore, it is necessary to set the start time and duration of the Promotion License through the customized interface of the server.

Step 303: During the process of using the Normal License, the server detects the Promotion License. The initial usage time, and use the Promotion License when the initial usage time arrives.

Step 304: The server notifies the client to obtain the authorization.

However, this step is not required, and the following step 305 can be directly performed.

Step 305: The client requests authorization from the server.

Without performing step 304, the client may request authorization directly from the server if authorization is required, without waiting for the server's notification to request authorization from the server.

Step 306: The server authorizes the client and records the client authorization data.

It should be noted that step 306 may be directly executed without performing steps 304 and 305. In this way, after using the Promotion License, the server can directly license the Promotion License to the client.

After step 306, the method may further include:

Step 307: The server detects the usage duration of the set Promotion License, and stops the Promotion License when the usage duration is exhausted.

Step 308: The server notifies the client to return the authorization.

Similarly, this step is not necessary, and the following step 309 can be directly performed.

Step 309: The client requests the return of the authorization to the server.

In the case where step 308 is not executed, the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server. In other embodiments, before stopping the Promotion License in step 307, the client may actively send a return authorization request to the server, so that in the case where the number of authorizations is limited, the client-returned authorization may continue to be authorized to other clients, thereby Improve license utilization and reduce the burden on the server.

Step 310: The server reclaims the authorization for the client promotion license.

It should be noted that step 310 may be performed without performing steps 308 and 309. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.

Another embodiment of the license control method of the present invention is described below. Figure 4 shows the flow of another embodiment of the method, as shown in Figure 4, including:

Step 401: The monthly service is loaded with the Normal License and the Promotion License.

Step 402: The server sets the start time and the number of uses of the Promotion License through a customized interface.

In this embodiment, the Normal License can be similar to the prior art, and is a licensee used by the server in daily situations.

The Promotion License is a license that is used from a specific point in time. It can be used for a specific number of times. Therefore, it is necessary to set the start time and number of uses of the Promotion License through the server customization interface.

Step 403: During the process of using the Normal License, the server detects the start time of the Promotion License and uses the Promotion License when the initial usage time arrives.

Step 404: The server notifies the client to obtain the authorization.

However, this step is not required, and the following step 405 may be directly performed.

Step 405: The client requests authorization from the server.

In this step, the client sends an authorization request to the server, requesting the server to authorize the resource or function. Without step 404, the client may request authorization directly from the server if authorization is required, without having to wait for the notification from the server before requesting authorization from the server.

Step 406: The server authorizes the client and records the client authorization data.

It should be noted that step 406 may be directly performed without performing steps 404 and 405. In this way, after using the Promotion License, the monthly server can directly use the Promotion License. Authorized to the client.

Step 406 may further include:

Step 407: The server detects the number of times the resources and/or functions in the set Promotion License are used, and stops the Promotion License when the number of uses is exhausted.

Step 408: The server notifies the client to return the authorization.

Similarly, this step is not necessary, and the following step 409 can be directly performed.

Step 409: The client requests the return of the authorization to the server.

In the case where step 408 is not executed, the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server. In other embodiments, before stopping the Promotion License in step 407, the client may actively send a return authorization request to the server, so that in the case where the number of authorizations is limited, the client-backed authorization may continue to be authorized to other clients. Improve license utilization and reduce the burden on the server.

Step 410: The server reclaims the authorization for the client promotion license.

It should be noted that step 410 may be directly performed without performing steps 408 and 409. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.

In the above three method embodiments, the difference includes that the server sets the usage conditions of the Promotion License through the customized interface, which are the usage time period, the initial usage time, the usage duration, the start time, and the resources in the Promotion License and/or Or the number of uses of the feature. That is to say, the use of the Promotion License is determined by the time period, or by the time and duration of use, or by the start time and the number of times the resources and/or functions in the Promotion License are used. Common to all three embodiments is that the usage conditions include the initial usage time, so the server can start using the Promotion License when it detects the arrival of the initial usage time. The above three embodiments are merely illustrative, and other usage conditions may be used according to actual needs.

It can be seen that, in the process of using the Normal License, the server detects the use condition of the Promotion License set by the customized interface, and the use condition includes the initial use time. The server enables the Promotion License when the initial usage time in the usage condition arrives, and the server authorizes the Promotion License to the client, so that the server can perform different authorizations for the client at different time periods.

In other words, in the foregoing embodiment, the license server can automatically enable the previous license in the usual time, enable the latter license in a certain period of time, and resume the previous license after a certain period of time. In this way, the actual needs of the business can be met, the benefits of the user's investment can be maximized, and the cost of the customer can be reduced in the purchase.

The following describes an embodiment of the license control method of the present invention by using a different license as a client trigger. FIG. 5 shows a flow of an embodiment of the method. As shown in FIG. 5, the method includes:

Step 501: The monthly license is loaded with the Normal License and the Promotion License.

The server can load at least two levels of licenses. Here is a description of loading the Normal License and the Promotion License. In this embodiment, the Normal License can be similar to the prior art, and is a license used by the server in daily situations. A Promotion License is a license that is used in a specific business situation. For example, the Promotion License includes a specific feature license (such as a function that the Normail License does not have), and/or includes more traffic than the Normal License. Resource authorization.

Step 502: The client initiates an authorization request to the server, and reports the resource and/or function request. In this step, the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.

Step 503: When the normal license cannot provide the resources and/or functions requested by the client, the Promotion License is enabled and authorized to the client;

For example, if the server detects that the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the server enables resources and/or functions in the Promotion License file, and The Promotion License is licensed to the client.

Step 503 may further include:

Step 504: The client periodically reports the currently required resources and/or functions to the server. Step 505: Stop the Promotion License when using the Normal License to provide the resources requested by the client and/or the requested function;

For example, if the server detects that the total number of resources requested by the client is within the number of authorized resources in the Normal License file and/or the requested function is enabled in the Normal License file, the server disables the resources and/or functions in the Promotion License file. And reclaim the Promotion License authorization for the client.

In the following, another embodiment of the license control method of the present invention will be described by taking a different license of the client as an example. FIG. 6 shows a flow of another embodiment of the method. As shown in FIG. 6, the method includes:

Step 601: The monthly service is loaded with the Normal License and the Promotion License.

Step 602: The server sets the duration of the Promotion License through the customized interface.

Step 603: The client initiates an authorization request to the server, and reports the resource and/or function request. In this step, the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.

Step 604: Enable the Promotion License and authorize the client when the normal license cannot provide the resources and/or functions requested by the client;

Step 604 can also include:

Step 605: The server detects the duration of use of the Promotion License by the set client. And when the set usage time is reached, that is, when the usage time is exhausted, the resources and/or functions in the Promotion License file are deactivated, and the Promotion License authorization for the client is reclaimed.

The sixth embodiment of the license control method of the present invention is described below by taking a different license of the client as an example. FIG. 7 shows a flow of another embodiment of the method. As shown in FIG. 7, the method includes:

Step 701: The monthly service is loaded with the Normal License and the Promotion License.

Step 702: The server sets the number of times the Promotion License is used through the customized interface.

Step 703: The client initiates an authorization request to the server, and reports the resource and/or function request. In this step, the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.

Step 704: When the normal license cannot provide the resources and/or functions requested by the client, the Promotion License is enabled and authorized to the client;

After step 704, the method may further include:

Step 705: The server detects the number of times the set client uses the resources and/or functions in the Promotion License, and disables the resources and/or functions in the Promotion License file when the set number of uses is reached, that is, when the number of uses is exhausted. Reclaim the Promotion License authorization for the client.

In the above three method embodiments, the difference is that the server disables the Promotion License, which is the current resource and/or function usage reported by the client, and the duration of use. The number of times a resource and/or feature has been used in the Promotion License. The above three embodiments are only examples, and other conditions of use may be used according to actual needs. For example, the server may also set a usage period of the Promotion License through a customized interface, where the usage period is defined by a start usage time and an usage end time, and during the usage period, the client request cannot be provided by using the Normal License. When the resources and/or functions are enabled, the Promotion License is enabled and authorized to the client, and then the set end time is detected. When the end time is reached, the Promotion License file is stopped and the Promotion License authorization for the client is further withdrawn.

It can be seen from the foregoing embodiment that, in the process of using the first license, the server receives the authorization request and the resource and/or function request sent by the client, and when the normal license cannot provide the resource and/or function requested by the client, for example, the server If the total number of resources requested by the client exceeds the number of authorized resources in the first license file and/or the function of the request is not enabled in the first license file, the resources and/or functions in the second license file are enabled, and the first The second license is granted to the client, so that the server can perform different licenses for the client under different business conditions.

In other words, in the foregoing embodiment, the license server can automatically enable the former license under the condition of general traffic demand or general function requirements, and is enabled under specific traffic demand conditions or specific function requirements. The latter license is restored to the previous license after a specific traffic demand situation or a specific function requirement. In this way, the actual needs of the business can be met, the benefits of the user's investment can be maximized, and the cost of the customer can be reduced in the purchase.

The following describes a first embodiment of the license management apparatus of the present invention, and FIG. 8 shows a block diagram of an embodiment of the license management apparatus, as shown in the following figure:

A license management apparatus includes a parsing unit 801, a management unit 802, and an authorization unit 803, where

The parsing unit 801 is configured to load the first license and the second license;

The management unit 802 is configured to enable the first license and enable the second license when the second license trigger condition is met;

Authorization unit 803, authorizes the first license and the second license to the client.

The license management device may be specifically a server.

On the basis of FIG. 8, FIG. 9 is a block diagram of another embodiment of the license management apparatus. As shown in the figure, the license management apparatus may further include a customized interface 901 and a detecting unit 902, where The customized interface 901 is configured to set an initial usage time of the second license.

The detecting unit 902 is configured to detect a start time of the set second license, and notify the management unit 802 that the second license trigger condition is satisfied when the initial use time arrives.

Preferably, the customized interface 901 is further configured to set a usage end time of the second license. The detecting unit 902 is further configured to detect a usage end time of the set second license, when the use end time arrives, The management unit 802 is notified to stop the second license.

Preferably, on the basis of FIG. 9, an embodiment may be further included, as shown in FIG. 10, the custom interface 901 is further configured to set a usage duration of the second license;

The license management device further includes a timing unit 903, configured to detect a usage duration of the set second license, and notify the management unit 802 to stop the second license when the usage duration is exhausted.

The timing unit 903 may be a single module or may be combined with the detecting unit 902.

Preferably, on the basis of FIG. 9, an embodiment may be further included, where the customized interface 901 is further configured to set the number of times of using the second license;

The license management device further includes a counting unit 904, configured to detect the used number of times of the set second license, and notify the management unit to stop the second license when the number of uses is exhausted.

The counting unit 904 may be a single module or may be combined with the detecting unit 902.

Preferably, on the basis of FIG. 9, FIG. 10, or FIG. 11, the license management apparatus may further include: a receiving unit, configured to receive a return authorization request sent by the client, and notify the authorization unit to reclaim the first Second license authorization;

The authorization unit is further configured to reclaim the second license authorization for the client according to the return authorization request sent by the client received by the receiving unit.

Here, only the example in conjunction with FIG. 9 is given. As shown in FIG. 12, the case of combining with other figures is similar to this and will not be described. In the example of Fig. 12, the receiving unit is numbered 1201. On the basis of FIG. 8, FIG. 13 is a block diagram of another embodiment of the license management apparatus. As shown in the figure, the license management apparatus may further include a receiving unit 1301 and a determining unit 1302, where The receiving unit 1301 is configured to receive an authorization request sent by the client, where the authorization request includes a resource request and/or a function request;

The determining unit 1302 is configured to determine, according to the authorization request received by the receiving unit 1301, that the management unit 802 is notified to satisfy the second license triggering condition when the first license cannot provide the resource and/or function requested by the client.

The determining unit 1302 may be a single module or may be combined with the authorization unit 803.

Preferably, in the embodiment shown in FIG. 13, the determining unit 1302 is further configured to send a stop to the management unit 802 when the first license can provide resources and/or functions requested by the client. Two license notices;

The management unit 802 may be further configured to stop the second license according to the stopping the second license notification sent by the determining.

Preferably, on the basis of FIG. 13, FIG. 14 is a block diagram of another embodiment of the license management apparatus. As shown in FIG. 14, the license management apparatus may further include a customized interface 1401 and a detecting unit 1402, where

The customized interface 1401 is configured to set a usage end time of the second license.

The detecting unit 1402 is configured to detect a usage end time of the set second license, and notify the management unit 802 to stop the second license when the usage end time arrives.

Preferably, on the basis of FIG. 13, FIG. 15 shows a block diagram of another embodiment of the license management apparatus. As shown in FIG. 14, the license management apparatus may further include a customized interface 1501 and a timing unit 1502, where

The customized interface 1501 is configured to set a usage duration of the second license.

The timing unit 1502 is configured to detect a usage duration of the set second license, and notify the management unit 802 to stop the second license when the usage duration is exhausted.

Preferably, on the basis of FIG. 13, FIG. 16 is a block diagram of another embodiment of the license management apparatus. As shown in FIG. 16, the license management apparatus may further include a customized interface 1601 and a timing unit 1602, where

The customized interface 1601 is further configured to set the number of times the second license is used;

The counting unit 1602 is configured to detect a used number of times of the second license, where the When the number of uses is exhausted, the management unit 802 is notified to stop the second license.

Preferably, on the basis of FIG. 13, 14, 15, and 16, the receiving unit 1301 is further configured to receive a return authorization request sent by the client, and notify the authorization unit 803 to reclaim the second license authorization for the client.

The authorization unit 803 is further configured to reclaim the second license authorization for the client according to the return authorization request sent by the client received by the receiving unit 1301.

Only the example in conjunction with Fig. 13 is shown here, as shown in Fig. 17, the case of combining with other figures is similar, and will not be described. In the example of Fig. 17, the receiving unit is numbered 1301.

It can be seen from the above embodiment that during the process of using the Normal License by the server, the promotion license is enabled when the start time of the Promotion License arrives, and the Promotion License is authorized to the client; or the server uses the Normal License. If the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the resources and/or functions in the Promotion License file are enabled, and the Promotion License is authorized. Client. In this way, the server can be differently licensed to the client in different time periods or different business situations.

One of ordinary skill in the art will appreciate that the methods of implementing the above-described embodiments can be implemented by hardware associated with program instructions, which can be stored in a readable storage medium that, when executed, performs the corresponding steps in the methods described above. The storage medium may be, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like.

While the embodiments of the present invention have been described by the embodiments of the embodiments of the invention spirit.

Claims

Rights request

A license control method, comprising:

Use the first license to provide services to the client;

Enable the second license according to the second license triggering condition;

Authorize the second license to the client.

2. The method according to claim 1, wherein the enabling the second license according to the second license triggering condition comprises:

Detecting the initial usage time of the set second license;

The second license is enabled when the initial usage time arrives.

The method according to claim 1, wherein the enabling the second license according to the second license triggering condition comprises:

Receiving an authorization request sent by the client, the authorization request includes a resource request and/or a function request; and when the first license cannot provide the resource and/or function requested by the client, the second Licsnss is enabled.

The method of claim 3, after the authorizing the second license to the client, the method further comprises:

Receiving the currently required resources and/or functions periodically reported by the client;

Stop the second licensee when using the first license to provide the resources and/or requested functions requested by the client.

5. The method according to claim 2 or 3, wherein the authorizing the second to the client

The license further includes: detecting a usage end time of the set second license, and stopping the second license when the use end time arrives.

The method according to claim 2 or 3, wherein after the authorizing the second license to the client, the method further includes: detecting a usage duration of the set second license, and stopping when the usage duration is exhausted The second license.

The method according to claim 2 or 3, wherein after the authorizing the second license to the client, the method further includes: detecting a used number of resources and/or functions in the set second license, and in the Stop the second license when the number of uses is exhausted.

The method according to any one of claims 1 to 3, wherein the After the second license, the method further includes: receiving a return authorization request sent by the client, and reclaiming the second license authorization for the client.

A license management device, the device comprising:

a parsing unit, configured to force the first license and the second license;

The device of claim 9, wherein the device further comprises: a customized interface, configured to set an initial usage time of the second license;

The detecting unit is configured to detect a start time of the set second license, and notify the management unit to satisfy the second license triggering condition when the initial use time arrives.

The device according to claim 9, wherein the device further comprises: a receiving unit, configured to receive an authorization request sent by the client, where the authorization request includes a resource request and/or a function request;

a determining unit, configured to perform, according to an authorization request received by the receiving unit, to use the first

When the license cannot provide the resources and/or functions requested by the client, the management unit is notified that the second license trigger condition is met.

12. Apparatus according to claim 11 wherein:

The determining unit is further configured to send a stop second license notification to the management unit when the first license can provide the resource and/or function requested by the client;

The management unit is further configured to stop the second license notification sent according to the determining, and stop the second licensee

13. Apparatus according to claim 10 wherein:

The customized interface is further configured to set a usage end time of the second license;

The detecting unit is further configured to detect a used end time of the set second license, and notify the management unit to stop the second license when the use end time arrives.

14. Apparatus according to claim 10 wherein:

The customized interface is further configured to set a usage duration of the second license.

The device further includes a timing unit for detecting the used duration of the set second license, When the usage duration is exhausted, the management unit is notified to stop the second license.

15. Apparatus according to claim 10 wherein:

The customized interface is also used to set the number of times the second license is used;

The device further includes a counting unit, configured to detect the used number of times of the set second license, and notify the management unit to stop the second license when the number of uses is exhausted.

The device according to any one of claims 9, 10, 13, 14, and 15, wherein the device further comprises:

a receiving unit, configured to receive a return authorization request sent by the client, and notify the authorization unit to reclaim the second license authorization for the client;

The device of claim 11 or 12, wherein the device further comprises: a customized interface, configured to set a usage end time of the second license;

The detecting unit is configured to detect a usage end time of the set second license, and notify the management unit to stop the second license when the use end time arrives.

The device of claim 11 or 12, wherein the device further comprises: a customized interface, configured to set a usage duration of the second license;

The timing unit is configured to detect a usage duration of the set second license, and notify the management unit to stop the second license when the usage duration is exhausted.

The device of claim 11 or 12, wherein the device further comprises: a customized interface, configured to set a number of uses of the second license;

The counting unit is configured to detect the number of uses of the set second license, and notify the management unit to stop the second license when the number of uses is exhausted.

20. Apparatus according to claim 11 or 12, wherein

The receiving unit is further configured to receive a return authorization request sent by the client, and notify the authorization unit to reclaim the second license authorization for the client;