CN105930693A - Software authorization method and apparatus - Google Patents
Software authorization method and apparatus Download PDFInfo
- Publication number
- CN105930693A CN105930693A CN201610281383.3A CN201610281383A CN105930693A CN 105930693 A CN105930693 A CN 105930693A CN 201610281383 A CN201610281383 A CN 201610281383A CN 105930693 A CN105930693 A CN 105930693A
- Authority
- CN
- China
- Prior art keywords
- authorization
- authorized
- resources
- file
- resource
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000013475 authorization Methods 0.000 claims abstract description 348
- 238000009434 installation Methods 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 3
- 238000004590 computer program Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/107—License processing; Key processing
- G06F21/1077—Recurrent authorisation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present application provides a software authorization method and apparatus, which are applied to a license server. The method comprises: acquiring a quantity of authorization resources of an installed authorization file, and obtaining a total quantity of authority resources according to the quantity of the authorization resources, wherein the quantity of the authorization resources is a quantity of authority resources corresponding to the authorization file, the authority resources are usage units of software, and the total quantity of the authority resources is a sum of a quantity of authorization resources of an available authorization file of the software; acquiring a resource usage quantity of the software, wherein the resource usage quantity is a quantity of the authority resources that has been used by the software; determining whether the total quantity of the authority resources is greater than the resource usage quantity; and when the total quantity of the authority resources is greater than the resource usage quantity, determining successful software authorization. The method and apparatus provided by the present application are capable of flexibly managing software authorization.
Description
Technical Field
The present application relates to the field of software management, and in particular, to a method and an apparatus for software authorization.
Background
When a user purchases software from a software manufacturer, the user typically purchases the software according to a pre-planned requirement, for example, an authorization file of the software X purchased from the software manufacturer by the user includes "three-year usage right of 1000 sets of software X", so as to provide 1000 clients with the usage right, and the time limit for using the software by each client is three years, and the software manufacturer uniformly manages the usage right of the software purchased by the user by installing a corresponding authorization file on a License Server (License Server); therefore, the user can install an authorization without starting one set of software, and any set of software only needs to be authenticated by the license server after being started and can obtain the authorization after the authentication is passed.
The license server starts timing after the installation of the authorization file, and fails to authorize the software after the authorized service life of the software is reached, so that the user cannot continue to use the software; however, the user may not fully use the software when the authorized use period of the software is reached, for example, the user purchases 1000 sets of software X for three years from a software manufacturer, and when the authorized use period is reached, the user only uses 500 sets of software or the user only uses the software for one year in the three years, so that, after the authorization of the software is invalid, even if the user does not fully use the software, the software cannot be used, and only the authorization of the software can be purchased again, thereby causing loss to the user.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for software authorization, which can flexibly manage software authorization.
Specifically, the method is realized through the following technical scheme:
in one aspect, a method for software authorization is provided, which is applied to a license server, and the method includes: obtaining the number of authorized resources of an installed authorized file, and obtaining the total number of authority resources according to the number of authorized resources, wherein the number of authorized resources is the number of authority resources corresponding to the authorized file, the authority resources represent the use units of software, and the total number of authority resources is the sum of the number of authorized resources of available authorized files of the software; acquiring the resource usage quantity of software, wherein the resource usage quantity is the quantity of authority resources already used by the software; judging whether the total number of the authority resources is larger than the resource use number; and when the total number of the authority resources is larger than the resource use number, determining that the software is successfully authorized.
In another aspect, an apparatus for software authorization is provided, which is applied to a license server, and includes: the first obtaining unit is used for obtaining the authorized resource quantity of the installed authorized file and obtaining the total quantity of the authorized resources according to the authorized resource quantity, wherein the authorized resource quantity is the quantity of the authorized resources corresponding to the authorized file, the authorized resources represent the use units of software, and the total quantity of the authorized resources is the sum of the authorized resource quantity of the available authorized file of the software; a second obtaining unit, configured to obtain a resource usage amount of software, where the resource usage amount is an amount of an authority resource that has been used by the software; the judging unit is used for judging whether the total number of the authority resources is greater than the number of the used resources; and the authorization unit is used for determining that the software is successfully authorized when the total number of the authority resources is greater than the resource use number.
By adopting the embodiment of the invention, the authorized resource quantity of the installed authorized file is obtained, and the total quantity of the authorized resources is obtained according to the authorized resource quantity, wherein the authorized resource quantity is the quantity of the authorized resources corresponding to the authorized file, the authorized resources represent the use units of the software, and the total quantity of the authorized resources is the sum of the authorized resource quantity of the available authorized file of the software; acquiring the resource usage quantity of the software, wherein the resource usage quantity is the quantity of authority resources already used by the software; judging whether the total number of the authority resources is larger than the using number of the resources; and when the total number of the authority resources is larger than the resource use number, determining that the software is successfully authorized. Therefore, the authorization service life and the authorization use number of the software are quantized into specific authority resources, whether the software is authorized to be used is determined by judging whether the total number of the authority resources is greater than the resource use number, the use of the software by a user is not limited to the authorization service life and the authorization use number of the software any more, and the authorization of the user can be flexibly managed according to the use condition of the software by the user.
Drawings
FIG. 1 is a flow chart diagram illustrating a software authorization method according to an exemplary embodiment of the present application;
FIG. 2 is a block diagram illustrating an exemplary embodiment of a software authorization apparatus;
FIG. 3 is a block diagram illustrating another software authorization apparatus according to an exemplary embodiment of the present application;
FIG. 4 is a block diagram illustrating a third software-enabled device according to an exemplary embodiment of the present application;
FIG. 5 is a block diagram illustrating a fourth software-enabled device according to an exemplary embodiment of the present application;
fig. 6 is a schematic diagram illustrating a hardware structure of a license server according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In the method for software authorization provided by the embodiment of the invention, after the installation of the authorization file is successful, the license server authorizes the use of the client side using the software, and in the following embodiment of the invention, whether the software is authorized or not can be determined by judging whether the total number of the right resources is greater than the number of the used resources, so that the use of the software by the user is not limited to the authorized use period and the authorized use number of the software any more, and the authorization of the user can be flexibly managed according to the use condition of the software by the user.
The present invention will be described in detail with reference to specific examples.
Fig. 1 is a method for software authorization provided in an embodiment of the present invention, as shown in fig. 1, where the method may be applied to a license server, and the method includes:
s101, obtaining the authorized resource quantity of the installed authorized file, and obtaining the total quantity of the authority resources according to the authorized resource quantity.
The number of the authorized resources is the number of the authorized resources corresponding to the authorization file, the authorized resources represent the usage units of the software, and the total number of the authorized resources is the sum of the number of the authorized resources of the available authorization files (such as the authorization file in use or the authorization file not yet used) of the software.
In this embodiment, in an initial state, since the authorization file of the software is not yet installed, the total number of the authorization resources is 0, after the authorization file of the software is installed, the license server parses the authorization file to obtain authorization information, where the authorization information may be an authorization lifetime and an authorization usage number, and the license server may obtain the authorization resource number of the authorization file according to the authorization lifetime and the authorization usage number and preset authorization management time, and after obtaining the authorization resource number of the authorization file, update the total number of the authorization resources according to the authorization resource number. For example, the authority information of the authorization file includes 1 year (corresponding to authorized use period) use right of 500 sets (corresponding to authorized use amount) of software, the license server parses the authorization file to obtain the authority information, and obtains "4380000 (500 × 365 × 24) 1 hour use right of software" (corresponding to authorized resource amount) according to the authority information, where 500 is 500 sets of software, 365 is 1 year included days, 24 is 1 day included hours, and "1 hour use right of software" is an authority resource, and "1 hour" is preset authorized management time; and updates the total number of entitlement resources to 4380000; of course, the above-mentioned "1 hour usage right of 4380000 pieces of software" is only for example, and the present invention is not limited to this, and the number of the right resources may also be "2 hour usage right of 2190000 pieces of software" or "1 month usage right of 6000 pieces of software", and the like, and may be configured in advance according to the preset authorized management time.
It should be noted that, if the license server can also install another authorized file of the software later (for example, the user later purchases the authorization of the software again), the license server parses the another authorized file, obtains the authorization information of the another authorized file, obtains the authorized resource quantity of the another authorized file according to the authorization information of the another authorized file, and updates the total quantity of the authorized resources according to the authorized resource quantity of the another authorized file (for example, the total quantity of the authorized resources is obtained by adding the authorized resource quantity of the another authorized file to the authorized resource quantity of the previously installed authorized file), for example, the license server installs another authorized file of the software, the authorization information of the another authorized file includes the 1-year usage right of the software of 2000 sets, the license server parses the another authorized file to obtain the authorization information of the another authorized file, and obtaining the authorized resource quantity of the other authorized file '17520000 (2000 x 365 x 24) 1-hour use right of the software' according to the authority information of the other authorized file, and updating the total authority resource quantity to '21900000 (4380000+ 17520000)' according to the authorized resource quantity of the other authorized file.
And S102, acquiring the resource usage number of the software.
In this step, the license server obtains the resource usage amount of the software after reaching a preset authorization management trigger condition, in a possible implementation manner, the preset authorization management trigger condition may be reaching a preset time, specifically, the license server may set the preset time, start timing after the installation of the authorization file of the software, and restart timing and obtain the resource usage amount of the software after reaching the preset time; for example, the preset time may be the preset authorization management time in this embodiment, for example, if the authorized resource amount of the authorization file (i.e. 1 hour of 4380000 software usage rights) is obtained by taking 1 hour (corresponding to the preset authorization management time) as an example, the preset time may be set to 1 hour.
In an implementation manner of optionally obtaining the resource usage amount, the license server obtains the authorization usage amount that has been successfully authorized currently, and obtains the resource usage amount according to the authorization usage amount, where the authorization usage amount is the amount that is successfully authorized according to the authorization application message, and the authorization application message is used to request authentication of the client; for example, the resource usage amount may be determined according to a product of the authorization usage amount and a preset authorization management time, for example, if the license server receives an authorization application message sent by 1000 clients and authorizes all of the 1000 clients successfully, the authorization usage amount is 1000, and when the preset time (e.g., 1 hour) is reached, the product of the authorization usage amount and the preset authorization management time is calculated to obtain 1000(1000 × 1), and the resource usage amount is increased by 1000. After the preset time is reached again, if the current authorized usage number is 2000, the product of the authorized usage number and the preset authorized management time is calculated to obtain 2000(2000 x 1), and then the resource usage number is increased by 2000 again to become 3000(2000 plus 1000).
It should be noted that, during the usage process of the authorization file, the total amount of the right resource may be smaller than the amount of the resource usage, specifically, when the preset authorized management time has not been reached, the amount of the resource usage may already be equal to the total amount of the right resource, at this time, since the preset authorized management time has not been reached, in this embodiment, the authorization file may still be used, when the preset authorized management time has been reached, the amount of the resource usage is larger than the total amount of the right resource, for example, the authority information of the authorization file is "1 hour usage right of 4380000 pieces of software", the total amount of the right resource is 4380000, after 45 minutes, the amount of the resource usage is already 4380000, since 1 hour has not been reached, the authorization file may still be used, the amount of the resource usage continues to increase, and after 1 hour has been reached, the number of resource uses has exceeded 4380000 (i.e., the total number of entitlement resources).
S103, judging whether the total quantity of the authority resources is larger than the use quantity of the resources.
And S104, when the total number of the authority resources is larger than the using number of the resources, determining that the software is successfully authorized.
And when the total number of the authority resources is equal to the resource use number, determining that the software authorization fails.
Optionally, after determining that the software is successfully authorized, the embodiment of the present invention may further determine an authorization status of an authorization file, specifically, the method includes the following steps:
and S01, when the resource usage number is larger than 0, determining a target authorization file from the installed authorization files.
The license server installs the target authorization file in advance, and obtains the authorized resource quantity of the target authorization file, and the specific description thereof may refer to the description of obtaining the authorized resource quantity of the authorization file in step S101, which is not described herein again.
After the resource usage number is obtained, judging whether the resource usage number is larger than 0, and when the resource usage number is equal to 0, indicating that the software is not used; when the resource usage number is greater than 0, it indicates that the software is used, in this embodiment, the license server may set a usage status identifier for the authorization file, the usage status identifier is used to mark the usage status of the authorization file, the usage status may include "in use", "unused" and "used up", and after the authorization file is installed, the usage status of the authorization file may be set to "unused" by default.
In this embodiment, the step S01 may include the following steps:
s11, if the resource usage number is greater than 0, the license server looks up the authorization file marked as "in use".
S12, if there is an authorized file marked as "in use", determining that the authorized file marked as "in use" is the target authorized file.
S13, if there is no authorized file marked as "in use", selecting one authorized file marked as "in use", and determining the authorized file marked as "in use" as the target authorized file.
It should be noted that, in a possible implementation manner, one authorization file may be optionally marked as "in use", or one authorization file may be selected to be marked as "in use" according to a certain rule, for example, the selection may be performed according to the number of authorized resources, or may be performed according to the installation order of the authorization files. For example, when the selection is performed according to the number of authorized resources, the authorization file with the minimum number of authorized resources is selected, or the authorization file with the maximum number of authorized resources is selected, or the selection is performed in other number manners. For example, when the selection is made according to the installation sequence of the authorization files, the authorization file installed first is selected, or the authorization file installed last is selected, or other time manners are selected. How to select is not limited herein as long as the authorization file is available and can be selected. If there are multiple authorization files selected according to a certain rule, for example, when selecting according to the number of authorization resources, there may be multiple authorization files with the same number of authorization resources, and at this time, the selection may be further performed according to the installation order, or one authorization file may be selected optionally. The selected authorization file is marked as 'in use', and the authorization file marked as 'in use' is the target authorization file.
S02 determines the authorization status of the target authorization file according to the authorized resource amount and the resource usage amount of the target authorization file.
The authorization state of the target authorization file may include an authorization use state and an authorization expiration state, and when the target authorization file is in the authorization use state, it indicates that the target authorization file is an authorization file whose authorization has not expired, and when the target authorization file is in the authorization expiration state, it indicates that the target authorization file is an authorization file whose authorization has expired.
In the embodiment, after the target authorization file is determined, whether the authorization resource quantity of the target authorization file is greater than the resource use quantity is judged; when the authorized resource quantity of the target authorized file is larger than the resource usage quantity, determining that the target authorized file is in an authorized usage state, when the authorized resource quantity of the target authorized file is smaller than or equal to the resource usage quantity, determining that the target authorized file is in an authorized expiration state, and updating the total quantity of the authority resources and the resource usage quantity according to the authorized resource quantity of the target authorized file.
Illustratively, if the number of authorized resources of the target authorization file is M, when M is less than or equal to the number of used resources, the target authorization file is marked as "used up", and the number of used resources is subtracted by M, the total number of authorized resources is subtracted by M, for example, the number of used resources is 4380500, the target authorization file is in an "in use" state, and the number of authorized resources of the target authorization file is 4380000, when the state of used of the target authorization file is "used up", the number of used resources is changed from 4380500 to 500 (4380500-.
In an optional implementation manner of this embodiment, after determining that the target authorization file is in an authorization expiration state, if it is determined that the updated number of resource usages is greater than 0, a next target authorization file is continuously determined according to the updated number of resource usages, and when the number of authorized resources of the next target authorization file is less than or equal to the number of resource usages, the total number of the right resources and the number of resource usages are updated until the newly determined number of authorized resources of the target authorization file is greater than the number of resource usages, and when it is determined that the total number of the right resources is 0, a software usage expiration notification message is sent to the client.
Wherein, the steps S11 to S13 may be continuously performed to determine a next target authorization file according to the updated number of resource usages, and when the number of authorized resources of the next target authorization file is less than or equal to the number of resource usages (i.e. the next target authorization file is in an authorization expiration state), the total number of the authorized resources and the number of resource usages are updated until the number of authorized resources of the newly determined target authorization file is greater than the number of resource usages, and whether the total number of the authorized resources is 0 or not is determined, and when the total number of the authorized resources is 0, a software usage expiration notification message is sent to the client; wherein the software usage expiration notification message is for notifying a user that the authorization of the software has expired; when the total number of the privileged resources is not 0, then the authorization of the software is not expired.
Optionally, after determining the authorization status of the authorization file, receiving an uninstall instruction for uninstalling the installed authorization file; when the installed authorization file is in an authorization expiration state, uninstalling the installed authorization file according to the uninstalling instruction; and when the installed authorization file is in an authorized use state, uninstalling the installed authorization file according to the uninstalling instruction, and updating the total amount of the authority resources.
In an optional implementation manner of this embodiment, after receiving an uninstall instruction for uninstalling the installed authorization file, different uninstall policies may be adopted for the installed authorization file in different usage states, specifically:
if the use state of the installed authorization file is "used up", when the installed authorization file is uninstalled, the identifier of the installed authorization file is recorded, and when the installed authorization file corresponding to the identifier is subsequently reinstalled, the following two implementation manners may be included:
one way to do this is to refuse the re-installation of the installed authorization file; another implementation is to allow installation of the installed authorization file, in this implementation, after the installed authorization file is reinstalled, the number of resource usages is added to the number of resource usages of the installed authorization file, and at this time, since the number of authorized resources of the installed authorization file is less than or equal to the number of resource usages, it is determined that the target authorization file is in an authorization due state.
For example, the license server is installed with an authorization file 1 and an authorization file 2 of software, the authorization file 1 has authority information including 1 year right of use of 500 sets of software, the authorized resource quantity is 4380000 (i.e. 4380000 sets of software per hour right of use), the authorization file 2 has authority information including 1 year right of use of 2000 sets of software, the authorized resource quantity is 17520000 (i.e. 17520000 sets of software per hour right of use), at this time, the total quantity of authority resources is 21900000 (i.e. 21900000 sets of software per 1 hour right of use), the authorization file 1 has a use state of "in use", the authorization file 2 has a use state of "unused", after one hour, the resource use quantity becomes 4380000, the same as the authorized resource quantity of authorization file 1, the authorization file 1 has a use state of "out", the resource use quantity is 0, the authorization file 2 has a use state of "in use", uninstalling the authorization file 1, and when the resource usage amount is 2000000 in the subsequent re-installation of the authorization file 1, the resource usage amount plus the authorized resource amount of the authorization file 1 becomes 6380000, and since the resource usage amount (6380000) is greater than the authorized resource amount (4380000) of the authorization file 1, the authorization file 1 is in an authorization expired state, and therefore, the authorization file 1 is still in an unusable state even if it is installed.
If the usage state of the installed authorization file is "in use", storing the current resource usage amount and the authorization resource amount of the installed authorization file when the installed authorization file is uninstalled, clearing the resource usage amount in the resource pool, subtracting the authorization resource amount of the installed authorization file from the total amount of authority resources in the resource pool, and if the installed authorization file is subsequently installed again, determining that the resource usage amount stored when the installed authorization file is uninstalled and the authorization resource amount of the installed authorization file, adding the total amount of authority resources to the authorization resource amount of the installed authorization file after the installed authorization file is installed, adding the current resource usage amount to the stored resource usage amount, and deleting the stored resource usage amount and the authorization resource amount of the installed authorization file, while the usage status of the installed authorization file is marked as "unused".
For example, still taking the license server installed authorization file 1 and authorization file 2 as examples, the total number of authorized resources is 21900000, the usage status of authorization file 1 is "in use", the usage status of authorization file 2 is "unused", the number of resource usage is 2000000, at the time of uninstalling the authorization file 1, the resource usage number becomes 0, the total number of rights resources minus the authorized resource number (i.e., 4380000) of the authorization file 1 becomes 17520000, at which time, the usage state of the authorization file 2 becomes "in use", and after a period of time has elapsed, the resource usage number becomes 1500000, when the authorization file 1 is reinstalled, the total number of the right resources plus the number of the authorized resources of the authorization file 1 becomes 21900000, the number of the resource usage plus the resource used by the authorization file 1 (i.e., 2000000) becomes 3500000, and the usage status of the authorization file 1 is marked as "unused"; the above specific numerical values are only examples, and the present embodiment is not limited thereto.
After the usage status of the installed authorization file is marked as "unused", in an optional implementation manner, obtaining permission information of the reinstalled installed authorization file, obtaining the authorized resource quantity of the installed authorization file according to the permission information of the installed authorization file, updating the total quantity of permission resources and the resource usage quantity according to the authorized resource quantity of the installed authorization file, determining a new target authorization file according to the updated resource usage quantity, and updating the total quantity of permission resources and the resource usage quantity when the authorized resource quantity of the new target authorization file is less than or equal to the resource usage quantity until the authorized resource quantity of the determined new target authorization file is greater than the resource usage quantity. For example, the steps S11 to S13 may be executed to determine a new target authorization file according to the updated resource usage amount, and when the authorized resource amount of the new authorization file is less than or equal to the resource usage amount, the total authorized resource amount and the resource usage amount are updated until the authorized resource amount of the new target authorization file is greater than the resource usage amount.
If the use state of the installed authorization file is 'unused', when the authorization file is uninstalled, subtracting the authorization resource quantity of the authorization file from the total quantity of the authority resources, allowing subsequent reinstallation, and adding the total quantity of the authority resources to the authorization resource quantity of the authorization file when the 'unused' authorization file is subsequently installed.
By adopting the software authorization method provided by the embodiment, the authorization service life and the authorization use quantity of the software are quantized into specific authority resources, and whether the software is authorized to be used or not is determined by judging whether the total quantity of the authority resources is greater than the resource use quantity or not, so that the use of the software by a user is not limited to the authorization service life and the authorization use quantity of the software any more, and the authorization of the user can be flexibly managed according to the use condition of the software by the user.
Fig. 2 is a device for software authorization according to an embodiment of the present invention, which is applied to a license server, and as shown in fig. 2, the device includes:
a first obtaining unit 201, configured to obtain the authorized resource number of an installed authorization file, and obtain the total number of authorized resources according to the authorized resource number, where the authorized resource number is the number of authorized resources corresponding to the authorization file, the authorized resources indicate a unit of use of software, and the total number of authorized resources is the sum of the authorized resource numbers of available authorization files of the software;
a second obtaining unit 202, configured to obtain a resource usage amount of the software, where the resource usage amount is an amount of an authority resource that has been used by the software;
a determining unit 203, configured to determine whether the total number of the right resources is greater than the number of the used resources;
and an authorization unit 204, configured to determine that the software is successfully authorized when the total number of the authorized resources is greater than the number of the used resources.
Optionally, the second obtaining unit 202 is specifically configured to obtain the authorized usage amount that has been successfully authorized currently; the authorization use quantity is the quantity of successful authorization determined according to an authorization application message sent by a client; the authorization application message is used for requesting to authenticate the client and obtaining the resource usage amount according to the authorization usage amount.
Optionally, as shown in fig. 3, the apparatus further includes:
a determining unit 205, configured to determine a target authorization file from the installed authorization files when the resource usage number is greater than 0;
a state determining unit 206, configured to determine the authorization state of the target authorization file according to the number of authorized resources of the target authorization file and the number of used resources.
Optionally, the determining unit 205 is specifically configured to select the target authorization file according to an installation order of the authorization files of the software; or, the target authorization file is selected according to the authorized resource quantity of the authorization file of the software.
Optionally, the state determining unit 206 is specifically configured to determine whether the number of authorized resources of the target authorization file is greater than the number of used resources; when the number of the authorized resources of the target authorization file is greater than the number of the used resources, determining that the target authorization file is in an authorized use state; and when the number of the authorized resources of the target authorization file is less than or equal to the resource usage number, determining that the target authorization file is in an authorization expiration state.
Optionally, as shown in fig. 4, the apparatus further includes:
a second updating unit 207, configured to update the total number of the right resources and the number of the resource usage according to the number of the authorized resources of the target authorization file after determining that the target authorization file is in an authorization expiration state;
and the processing unit 208 is configured to continuously determine a next target authorization file according to the updated number of resource usage, update the total number of the right resources and the number of resource usage until the number of the re-determined authorized resources of the target authorization file is greater than the number of resource usage when the number of the authorized resources of the next target authorization file is less than or equal to the number of resource usage, and send a software usage expiration notification message to the client when the total number of the right resources is determined to be 0.
Optionally, as shown in fig. 5, the apparatus further includes:
an uninstalling unit 209, configured to receive an uninstalling instruction for uninstalling the installed authorization file after determining the authorization status of the target authorization file according to the number of authorized resources of the target authorization file and the number of used resources; when the installed authorization file is in an authorization expiration state, uninstalling the installed authorization file according to the uninstalling instruction; and when the installed authorization file is in an authorized use state, uninstalling the installed authorization file according to the uninstalling instruction, and updating the total amount of the authority resources.
By adopting the software authorization device provided by the embodiment, the authorization service life and the authorization use number of the software are quantized into specific authority resources, and whether the software is authorized to be used is determined by judging whether the total number of the authority resources is greater than the resource use number, so that the use of the software by a user is not limited to the authorization service life and the authorization use number of the software any more, and the authorization of the user can be flexibly managed according to the use condition of the software by the user.
The embodiment of the software authorization device provided by the application can be applied to a license server. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the license server where the device is located. From a hardware aspect, as shown in fig. 6, a hardware structure diagram of a license server where a device authorized by software of the present application is located may include other hardware in addition to the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 6, which is not described again.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (14)
1. A method of software authorization, applied to a license server, the method comprising:
obtaining the number of authorized resources of an installed authorized file, and obtaining the total number of authority resources according to the number of authorized resources, wherein the number of authorized resources is the number of authority resources corresponding to the authorized file, the authority resources represent the use units of software, and the total number of authority resources is the sum of the number of authorized resources of available authorized files of the software;
acquiring the resource usage quantity of software, wherein the resource usage quantity is the quantity of authority resources already used by the software;
judging whether the total number of the authority resources is larger than the resource use number;
and when the total number of the authority resources is larger than the resource use number, determining that the software is successfully authorized.
2. The method of claim 1, wherein obtaining the amount of resource usage of the software comprises:
obtaining the authorization use quantity which is successfully authorized currently; the authorization use quantity is the quantity of successful authorization determined according to an authorization application message sent by a client; the authorization application message is used for requesting to authenticate the client;
and obtaining the resource usage quantity according to the authorized usage quantity.
3. The method of claim 1 or 2, wherein upon determining that the software is successfully authorized, the method further comprises:
when the resource usage number is larger than 0, determining a target authorization file from the installed authorization files;
and determining the authorization state of the target authorization file according to the authorization resource quantity and the resource use quantity of the target authorization file.
4. The method of claim 3, wherein determining the target authorization file from the installed authorization files comprises:
selecting the target authorization file according to the installation sequence of the authorization files of the software; or,
and selecting the target authorization file according to the number of authorized resources of the authorization file of the software.
5. The method of claim 3, wherein the determining the authorization status of the target authorization file according to the number of authorized resources of the target authorization file and the number of resource usage comprises:
judging whether the number of the authorized resources of the target authorized file is greater than the number of the used resources;
when the number of the authorized resources of the target authorization file is greater than the number of the used resources, determining that the target authorization file is in an authorized use state;
and when the number of the authorized resources of the target authorization file is less than or equal to the resource usage number, determining that the target authorization file is in an authorization expiration state.
6. The method of claim 5, wherein after the determining that the target authorization file is in an authorization expired state, the method further comprises:
updating the total number of the authority resources and the resource use number according to the authorized resource number of the target authorized file;
and continuously determining a next target authorization file according to the updated resource usage quantity, updating the total number of the authority resources and the resource usage quantity when the authorization resource quantity of the next target authorization file is less than or equal to the resource usage quantity until the newly determined authorization resource quantity of the target authorization file is greater than the resource usage quantity, and sending a software usage expiration notification message to the client when the total number of the authority resources is determined to be 0.
7. The method of claim 3, wherein after determining the authorization status of the target authorization file according to the number of authorized resources of the target authorization file and the number of resource usage, the method further comprises:
receiving an uninstalling instruction for uninstalling the installed authorization file;
when the installed authorization file is in an authorization expiration state, uninstalling the installed authorization file according to the uninstalling instruction;
and when the installed authorization file is in an authorized use state, uninstalling the installed authorization file according to the uninstalling instruction, and updating the total amount of the authority resources.
8. An apparatus for software authorization, applied to a license server, the apparatus comprising:
the first obtaining unit is used for obtaining the authorized resource quantity of the installed authorized file and obtaining the total quantity of the authorized resources according to the authorized resource quantity, wherein the authorized resource quantity is the quantity of the authorized resources corresponding to the authorized file, the authorized resources represent the use units of software, and the total quantity of the authorized resources is the sum of the authorized resource quantity of the available authorized file of the software;
a second obtaining unit, configured to obtain a resource usage amount of software, where the resource usage amount is an amount of an authority resource that has been used by the software;
the judging unit is used for judging whether the total number of the authority resources is greater than the number of the used resources;
and the authorization unit is used for determining that the software is successfully authorized when the total number of the authority resources is greater than the resource use number.
9. The apparatus according to claim 8, wherein the second obtaining unit is specifically configured to obtain a currently successfully authorized number of authorized uses; the authorization use quantity is the quantity of successful authorization determined according to an authorization application message sent by a client; and the authorization application message is used for requesting to authenticate the client and obtaining the resource usage amount according to the authorization usage amount.
10. The apparatus of claim 8 or 9, further comprising:
the determining unit is used for determining a target authorization file from the installed authorization files when the resource usage number is greater than 0;
and the state determining unit is used for determining the authorization state of the target authorization file according to the authorization resource quantity of the target authorization file and the resource use quantity.
11. The apparatus according to claim 10, wherein the determining unit is specifically configured to select the target authorization file according to an installation order of the authorization files of the software; or selecting the target authorization file according to the number of authorized resources of the authorization file of the software.
12. The apparatus according to claim 11, wherein the status determining unit is specifically configured to determine whether the number of authorized resources of the target authorization file is greater than the number of used resources; when the number of the authorized resources of the target authorization file is greater than the number of the used resources, determining that the target authorization file is in an authorized use state; and when the number of the authorized resources of the target authorization file is less than or equal to the resource usage number, determining that the target authorization file is in an authorization expiration state.
13. The apparatus of claim 12, further comprising:
the second updating unit is used for updating the total number of the authority resources and the resource using number according to the authorized resource number of the target authorization file after the target authorization file is determined to be in an authorized due state;
and the processing unit is used for continuously determining a next target authorization file according to the updated resource usage quantity, updating the total number of the authority resources and the resource usage quantity when the authorization resource quantity of the next target authorization file is less than or equal to the resource usage quantity until the newly determined authorization resource quantity of the target authorization file is greater than the resource usage quantity, and sending a software usage expiration notification message to the client when the total number of the authority resources is determined to be 0.
14. The apparatus of claim 10, further comprising:
the uninstalling unit is used for receiving an uninstalling instruction for uninstalling the installed authorization file after the authorization state of the target authorization file is determined according to the authorization resource quantity and the resource use quantity of the target authorization file; when the installed authorization file is in an authorization expiration state, uninstalling the installed authorization file according to the uninstalling instruction; and when the installed authorization file is in an authorized use state, uninstalling the installed authorization file according to the uninstalling instruction, and updating the total amount of the authority resources.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610281383.3A CN105930693B (en) | 2016-04-29 | 2016-04-29 | A kind of method and apparatus of soft ware authorization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610281383.3A CN105930693B (en) | 2016-04-29 | 2016-04-29 | A kind of method and apparatus of soft ware authorization |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105930693A true CN105930693A (en) | 2016-09-07 |
| CN105930693B CN105930693B (en) | 2019-04-09 |
Family
ID=56837696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610281383.3A Active CN105930693B (en) | 2016-04-29 | 2016-04-29 | A kind of method and apparatus of soft ware authorization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105930693B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109063423A (en) * | 2018-07-16 | 2018-12-21 | 北京知道创宇信息技术有限公司 | application software authorization method and system |
| CN109547435A (en) * | 2018-11-23 | 2019-03-29 | 新华三信息安全技术有限公司 | A kind of authorization and authentication method and device |
| CN112016065A (en) * | 2019-05-31 | 2020-12-01 | 杭州海康威视数字技术股份有限公司 | Dual-user authentication method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0876994A (en) * | 1994-08-31 | 1996-03-22 | Nec Corp | Method and device for management of software license |
| CN101112063A (en) * | 2004-11-29 | 2008-01-23 | 唐鲍勃 | Immediate ready implementation of virtually congestion free guaranteed service capable network: external internet nextgentcp (square waveform) tcp friendly san |
| CN102054135A (en) * | 2009-11-06 | 2011-05-11 | 北大方正集团有限公司 | Software authorization method and device |
| CN103718633A (en) * | 2013-08-30 | 2014-04-09 | 华为技术有限公司 | Method, device and system for resource allocation |
| CN103838987A (en) * | 2013-06-24 | 2014-06-04 | 电子科技大学 | Software license dynamic authorization management method based on local area network |
| CN105027105A (en) * | 2013-04-30 | 2015-11-04 | 惠普发展公司，有限责任合伙企业 | Resource authorization quantities |
-
2016
- 2016-04-29 CN CN201610281383.3A patent/CN105930693B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0876994A (en) * | 1994-08-31 | 1996-03-22 | Nec Corp | Method and device for management of software license |
| CN101112063A (en) * | 2004-11-29 | 2008-01-23 | 唐鲍勃 | Immediate ready implementation of virtually congestion free guaranteed service capable network: external internet nextgentcp (square waveform) tcp friendly san |
| CN102054135A (en) * | 2009-11-06 | 2011-05-11 | 北大方正集团有限公司 | Software authorization method and device |
| CN105027105A (en) * | 2013-04-30 | 2015-11-04 | 惠普发展公司，有限责任合伙企业 | Resource authorization quantities |
| CN103838987A (en) * | 2013-06-24 | 2014-06-04 | 电子科技大学 | Software license dynamic authorization management method based on local area network |
| CN103718633A (en) * | 2013-08-30 | 2014-04-09 | 华为技术有限公司 | Method, device and system for resource allocation |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109063423A (en) * | 2018-07-16 | 2018-12-21 | 北京知道创宇信息技术有限公司 | application software authorization method and system |
| CN109547435A (en) * | 2018-11-23 | 2019-03-29 | 新华三信息安全技术有限公司 | A kind of authorization and authentication method and device |
| CN112016065A (en) * | 2019-05-31 | 2020-12-01 | 杭州海康威视数字技术股份有限公司 | Dual-user authentication method and device |
| CN112016065B (en) * | 2019-05-31 | 2023-10-10 | 杭州海康威视数字技术股份有限公司 | Dual-user authentication method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105930693B (en) | 2019-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2013212636B2 (en) | Application licensing using sync providers | |
| EP3460694B1 (en) | Authentication system | |
| KR101514100B1 (en) | Using flash storage device to prevent unauthorized use of software | |
| CN109063423B (en) | Application software authorization method and system | |
| JP7163454B2 (en) | Information processing device, control method for information processing device, and program | |
| US9460272B2 (en) | Method and apparatus for group licensing of device features | |
| US11269655B2 (en) | Bare metal device management | |
| US20170300669A1 (en) | Enterprise application management with enrollment tokens | |
| CN105930693B (en) | A kind of method and apparatus of soft ware authorization | |
| WO2011097550A2 (en) | Generic feature licensing framework | |
| US20120174090A1 (en) | Patch and dot release licensing | |
| EP2016523B1 (en) | Licensing system and method associating a persistent, unique identifier with a partitioned computer system | |
| EP2637120B1 (en) | Enterprise license registrar anchor point | |
| US10860304B2 (en) | Enforcement of updates for devices unassociated with a directory service | |
| US8635670B2 (en) | Secure centralized backup using locally derived authentication model | |
| JP4486531B2 (en) | Image forming system, image forming apparatus, management apparatus, and plug-in matching management method | |
| CN113728318A (en) | Remote management of user devices | |
| CN111125771B (en) | Method and device for protecting equipment privacy, electronic equipment and storage medium | |
| CN110110503B (en) | Method and device for managing and controlling specific behaviors of software | |
| CN106775881B (en) | System upgrading method and device | |
| JP2010204886A (en) | License management apparatus and program | |
| JP2010134706A (en) | Equipment management device, equipment management system, software management method, software management program, and recording medium recording program | |
| CN108234414B (en) | Upgrading method and device for APP | |
| US11900090B2 (en) | Enforcement of updates for devices unassociated with a directory service | |
| JP2005208935A (en) | Software management system and software management program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |