A software license resource planning method, apparatus, device, and storage medium

Abstract

This invention discloses a software license resource planning method, apparatus, device, and storage medium. The method includes the steps of: acquiring software license resource usage information; acquiring, based on the software license resource usage information, the number of times users were denied access when resources were insufficient, and the number of times resources were used when resources were abundant; and planning the software license resources based on the number of times or the number of times resources were used. This application can avoid purchasing excessive license resources by accurately planning software license resources, thereby saving costs. Furthermore, through centralized management and scheduling, software license resources can be utilized more effectively, improving resource utilization.

Description

Technical Field

[0001] This invention relates to the field of resource management technology, and in particular to a software license resource planning method, apparatus, device, and storage medium. Background Technology

[0002] A software license is the act of granting a user permission to use software, whether for a fee or free of charge. It is a right granted by the software developer or owner to the user to use the software under explicit authorization, provided a paid license fee is paid or the conditions for a gratuitous license are met. Because software development is a costly process, software licensing serves as a form of compensation for the developer's investment, allowing users to use the software under specific constraints, and also protects the software's copyright.

[0003] With the deepening of digital transformation in information technology, enterprises' demand for software is growing, and the annual cost of software licenses often becomes a significant component of their IT budgets. To remain competitive, enterprises need to control costs effectively. Therefore, software license resource planning has become particularly important.

[0004] Currently, existing technologies mainly address the technical problem of low utilization of license resources in the process of managing application license resources, without addressing the aspect of software license resources. That is, there is no suitable way to monitor and predict software licenses, nor is there reasonable data quantification.

[0005] Therefore, how to rationally plan and meticulously manage software license resources to achieve effective utilization and cost control is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] The main objective of this invention is to provide a software license resource planning method, apparatus, device, and storage medium that can avoid purchasing excessive license resources by accurately planning software license resources, thereby saving costs. At the same time, through centralized management and scheduling, software license resources can be utilized more effectively, improving resource utilization.

[0007] In a first aspect, this application provides a software licensing resource planning method, wherein the method includes the following steps:

[0008] Obtain information on the usage of software license resources;

[0009] Based on the software license resource usage, obtain the number of times users were denied access when resources were insufficient, and the number of users used when resources were sufficient;

[0010] Plan the software license resources based on the number of times or the amount of usage.

[0011] In conjunction with the first aspect mentioned above, as an optional implementation method, a licensed resource usage satisfaction rate can be set;

[0012] If the current utilization rate of the licensed resources reaches the set satisfaction rate, then obtain the number of times the licensed server refused access within each sampling point, and deduplicate users who accessed multiple times to obtain the number of times users were refused access when resources were insufficient.

[0013] In conjunction with the first aspect mentioned above, as an optional implementation method, the licensed resource usage load rate is set;

[0014] Obtain the number of licensed resources used at each sampling point below the licensed resource usage load rate.

[0015] In conjunction with the first aspect mentioned above, as an optional implementation method, the percentage of each sampling point in the total sampling points is calculated based on the number of times each sampling point is denied access by the server;

[0016] The percentage of each calculated sampling point is compared with the set permitted resource usage satisfaction rate to filter out sampling points that are less than or equal to the satisfaction rate;

[0017] The number of additional licensed resources needed is calculated based on the ratio between the sampling points that are less than or equal to the satisfaction rate and the total number of sampling points, in order to plan the software licensed resources.

[0018] In conjunction with the first aspect mentioned above, as an optional implementation method, based on the set licensed resource usage load rate, the number of licensed resources used at each sampling point is counted to calculate the percentage of usage at each sampling point;

[0019] The percentage of usage for each sample point is calculated and compared with the set permitted resource usage load rate to filter out sample points that are less than or equal to the load rate.

[0020] The required number of licensed resources is calculated based on the ratio between the number of sampling points less than or equal to the load rate and the total number of sampling points.

[0021] Based on the difference between the current total licensed resource data and the current required number of licensed resources, the number of licensed resources that need to be reduced is calculated in order to plan the software licensed resources.

[0022] In conjunction with the first aspect mentioned above, as an optional implementation method, a software license resource management terminal is established.

[0023] Automatically collect current licensed resource usage data based on preset time intervals;

[0024] Using the established software license resource management terminal, the automatically collected current license resource usage data is analyzed and processed to obtain the software license resource usage quantity for each sampling point.

[0025] In conjunction with the first aspect mentioned above, as an optional implementation method, the automatically collected data on the current licensed resource usage is stored.

[0026] Secondly, this application provides a software license resource planning apparatus, the apparatus comprising:

[0027] The resource management terminal is used to obtain information on the usage of software license resources.

[0028] The acquisition module is used to acquire, based on the software license resource usage, the number of times a user was denied access when resources were insufficient, and the number of times resources were used when resources were sufficient.

[0029] The planning module is used to plan software license resources based on the number of times or the amount of use.

[0030] Thirdly, this application also provides an electronic device, the electronic device comprising: a processor; and a memory storing computer-readable instructions, which, when executed by the processor, implement the method described in any one of the first aspects.

[0031] Fourthly, this application also provides a computer-readable storage medium storing computer program instructions that, when executed by a computer, cause the computer to perform the method described in any of the first aspects.

[0032] This application provides a software license resource planning method, apparatus, device, and storage medium. The method includes the steps of: acquiring software license resource usage information; acquiring, based on the software license resource usage information, the number of times users were denied access when resources were insufficient, and the number of times users were used when resources were abundant; and planning the software license resources based on the number of times or the number of times users were denied access. This application can avoid purchasing excessive license resources by accurately planning software license resources, thereby saving costs. Furthermore, through centralized management and scheduling, it can utilize software license resources more effectively, improving resource utilization.

[0033] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit the invention. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0035] Figure 1 This is a flowchart of a software license resource planning method provided in the embodiments of this application;

[0036] Figure 2 This is a schematic diagram of a software licensing resource planning device provided in the embodiments of this application;

[0037] Figure 3 This is a sampling diagram provided in the embodiments of this application;

[0038] Figure 4 This is a schematic diagram of an electronic device provided in an embodiment of this application;

[0039] Figure 5 This is a schematic diagram of a computer-readable program medium provided in an embodiment of this application. Detailed Implementation

[0040] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0041] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. Some of the block diagrams shown in the drawings represent functional entities and do not necessarily correspond to physically or logically independent entities.

[0042] This application provides a software license resource planning method, apparatus, device, and storage medium. By accurately planning software license resources, it is possible to avoid purchasing too many license resources, thereby saving costs. At the same time, through centralized management and scheduling, software license resources can be utilized more effectively, improving resource utilization.

[0043] To achieve the aforementioned technical effects, the general concept of this application is as follows:

[0044] A software licensing resource planning method, the method comprising the steps of:

[0045] S101: Obtain information on the use of software license resources.

[0046] S102: Based on the software license resource usage, obtain the number of times users were denied access when resources were insufficient, and the number of users used when resources were sufficient.

[0047] S103: Plan the software license resources based on the number of times or the amount of use.

[0048] The embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0049] Reference Figure 1 , Figure 1 The diagram shown is a flowchart of a software license resource planning method provided by the present invention. Figure 1 As shown, the method includes the following steps:

[0050] Step S101: Obtain information on the usage of software license resources.

[0051] Specifically, the established software license resource management terminal automatically collects current license resource usage data based on preset time intervals; the established software license resource management terminal analyzes and processes the automatically collected current license resource usage data to obtain the software license resource usage quantity at each sampling point.

[0052] In one embodiment, automatically collected data on current licensed resource usage is stored.

[0053] To illustrate this more clearly, we can establish a software license resource management system to monitor the license resources on the license server. The administrator sets a specified sampling time point, automatically collects and stores data, and collects resource data by capturing information over a period of time. This period is divided into N sampling points, each lasting 10 minutes, and the usage data of multiple sampling points is obtained.

[0054] For example, if N is set to 10, the current number of software users at the first sampling point will be collected, and then the current number of software users at the second sampling point will be collected after a 10-minute interval.

[0055] It's important to explain that a software license refers to the paid or gratuitous act of granting a user permission to use software. It's a right granted by the software developer or owner to the user, allowing them to use the software under explicit authorization, provided a paid license fee is paid or the gratuitous license fee is applicable. Because software development is a costly process, software licensing serves as a form of compensation for the developer's investment, allowing users to use the software under specific constraints, and also protecting software copyright.

[0056] Step S102: Based on the software license resource usage, obtain the number of times users were denied access when resources were insufficient, and the number of times resources were used when resources were sufficient.

[0057] Specifically, a permission resource usage satisfaction rate is set; if the current permission resource usage rate reaches the set satisfaction rate, the number of times the permissioned server refuses access within each sampling point is obtained, and users with multiple accesses are deduplicated to obtain the number of times users are refused access when resources are insufficient.

[0058] To illustrate this with an example, if the permitted resource utilization satisfaction rate is set to 80%, and if users still access the server when the current permitted resource utilization has reached 80%, the server will reject the users' access because the current resource utilization has reached the limit. The number of rejections will be counted, and multiple accesses from the same user will be deduplicated. That is, if a user is rejected multiple times, it will only be counted once. This gives the number of times a user is rejected when the resource is at full load (i.e., the set satisfaction rate).

[0059] Set the licensed resource usage load rate; obtain the licensed resource usage quantity for each sampling point below the licensed resource usage load rate.

[0060] To illustrate this more clearly, we set the resource utilization load rate to 70% and then obtain the permitted resource usage quantity for all sampling points below 70%.

[0061] Step S103: Plan the software license resources according to the number of times or the amount of use.

[0062] Specifically, the percentage of each sampling point in the total number of sampling points is calculated based on the number of times each sampling point is denied access by the server;

[0063] The percentage of each calculated sampling point is compared with the set permitted resource usage satisfaction rate to filter out sampling points that are less than or equal to the satisfaction rate;

[0064] The number of additional license resources needed is calculated based on the ratio between the number of sampling points less than or equal to the satisfaction rate and the total number of sampling points. This is used to plan the software license resources. For example, if there are 100 sampling points, the number of rejections for each sampling point is calculated. If 70 of the sampling points are rejected 4 times, then this rejection rate of 4 accounts for 70%. In this case, 4 additional license resources are needed to satisfy the requirement.

[0065] To illustrate this with an example, the prediction of license increases is based on the premise that user departments frequently request increased usage due to license overload and subsequent license denials. For instance, in a floating license software, if licenses are exhausted within a certain period, and some users are still requesting module licenses, these requests will be rejected by the license server. A user who is repeatedly denied licenses within an hour is recorded as a rejected user.

[0066] If the license quota is reached within a certain time period, and some users still require licenses, these will be rejected by the license server. If a user is rejected multiple times, the count is reset, and the total number of rejections is the number of users rejected. The rejection records from the license server are collected and uploaded to the license management database to calculate the business satisfaction rate. First, the number of users rejected at each sampling point is counted. The number of users rejected could be 1, 2, 3, or 4. For example, the business satisfaction rate for 2 users rejected is equal to the number of sampling points with 2 or fewer rejections divided by the total number of sampling points, assuming it's 80%. This means that adding 2 licenses would satisfy all users. To understand this, if there are 10 sampling points, and the first sampling point rejects users A and B (2 rejections), the second rejects user C (1 rejection), and so on, each subsequent rejection of one user results in a 1 rejection. If all sampling points with 2 or fewer rejections account for 80% of the total sampling points, the rejection count is 2, meaning 2 additional licenses are needed.

[0067] In one embodiment, based on the set licensed resource usage load rate, the number of licensed resources used at each sampling point is counted to calculate the percentage of usage at each sampling point;

[0068] The percentage of usage for each sample point is calculated and compared with the set permitted resource usage load rate to filter out sample points that are less than or equal to the load rate.

[0069] The required number of licensed resources is calculated based on the ratio between the number of sampling points less than or equal to the load rate and the total number of sampling points.

[0070] Based on the difference between the current total licensed resource data and the current required number of licensed resources, the number of licensed resources that need to be reduced is calculated in order to plan the software licensed resources.

[0071] Understandably, if the load factor is set to 80%, and 8 out of 10 sampling points are currently using resources (meaning 8 out of 10 resources are in use), then if the total number of resources is 10 and 8 are currently in use, then 2 resources can be reduced for planning and management.

[0072] To illustrate, a load factor is set (the number of sampling points equal to or less than the "assessed usage" / total sampling points * 100%), and the assessed usage is calculated. The authorized usage value corresponding to the load factor closest to the set value is the assessed usage. License reduction prediction uses the assessed usage corresponding to the calculated load factor to determine the required usage. The current total number of licenses is subtracted from the required usage to obtain the reduction amount. For example, using a load factor of 8 licenses means that over a period of time, the cumulative sampling points using 8 or fewer licenses (8 points) divided by the total sampling points (10 points) result in a license resource load factor of 80%. The current total number of licenses is 10, and the set value is 8, therefore, it is determined that 2 licenses need to be reduced.

[0073] Reference Figure 2 , Figure 2 The diagram shown is a schematic of a software license resource planning device provided by the present invention. Figure 2 As shown, the device includes:

[0074] Resource Management Terminal 201: It is used to obtain information on the usage of software license resources.

[0075] Acquisition module 202: It is used to acquire, based on the software license resource usage, the number of times a user was denied access when resources were insufficient, and the number of times resources were used when resources were sufficient.

[0076] Planning module 203: It is used to plan software license resources based on the number of times or the amount of use.

[0077] Furthermore, in one possible implementation, the acquisition module is also used to set the licensed resource usage satisfaction rate;

[0078] If the current utilization rate of the licensed resources reaches the set satisfaction rate, then obtain the number of times the licensed server refused access within each sampling point, and deduplicate users who accessed multiple times to obtain the number of times users were refused access when resources were insufficient.

[0079] Furthermore, in one possible implementation, the acquisition module is also used to set the licensed resource usage load rate;

[0080] Obtain the number of licensed resources used at each sampling point below the licensed resource usage load rate.

[0081] Furthermore, in one possible implementation, the planning module is also used to calculate the percentage of each sampling point out of the total number of sampling points based on the number of times each sampling point is denied access by the server;

[0082] The percentage of each calculated sampling point is compared with the set permitted resource usage satisfaction rate to filter out sampling points that are less than or equal to the satisfaction rate;

[0083] The number of additional licensed resources needed is calculated based on the ratio between the sampling points that are less than or equal to the satisfaction rate and the total number of sampling points, in order to plan the software licensed resources.

[0084] Furthermore, in one possible implementation, the planning module is also used to count the number of licensed resources used at each sampling point based on the set licensed resource usage load rate, so as to calculate the percentage of usage at each sampling point;

[0085] The percentage of usage for each sample point is calculated and compared with the set permitted resource usage load rate to filter out sample points that are less than or equal to the load rate.

[0086] The required number of licensed resources is calculated based on the ratio between the number of sampling points less than or equal to the load rate and the total number of sampling points.

[0087] Based on the difference between the current total licensed resource data and the current required number of licensed resources, the number of licensed resources that need to be reduced is calculated in order to plan the software licensed resources.

[0088] Furthermore, in one possible implementation, the resource management terminal is also used to establish a software license resource management terminal.

[0089] Automatically collect current licensed resource usage data based on preset time intervals;

[0090] Using the established software license resource management terminal, the automatically collected current license resource usage data is analyzed and processed to obtain the software license resource usage quantity for each sampling point.

[0091] Furthermore, in one possible implementation, the resource management terminal is also used to store the automatically collected data on the current licensed resource usage.

[0092] Reference Figure 3 , Figure 3 The diagram shown is a sampling schematic provided by the present invention. Figure 3 As shown:

[0093] Taking the number of licenses as an example, as shown in the figure, assuming the total number of licenses is 10, multiple sampling points are set, the load rate is set, and the number of evaluations is calculated. The number of evaluations is equal to the ratio of all sampling points less than or equal to 80% to the total sampling. For example, if the calculated number of evaluations is 8, that is, 8 accounts for 80% of the total sampling, then it means that only 8 license resources are needed to meet the demand under this load rate. If the total resources are 10, then 2 license resources can be reduced.

[0094] This can be understood as using a load factor of 8 licenses, which means that the cumulative sampling points of 8 licenses or less over a period of time are divided by the total sampling points of 10, resulting in a load factor of 80% for the licensed resources. The current total number of licenses is 10, and the set value is 8, thus it is determined that 2 licenses need to be reduced.

[0095] In one embodiment, over a period of time, the cumulative number of sampling points using m licenses or less is divided by the total number of sampling points to determine the resource load rate. The license value corresponding to the load rate closest to the set value is the evaluation quantity X. The current total number minus the required quantity X yields the number of licenses to be reduced.

[0096] If a user is rejected due to insufficient resources, the total number of rejected users is calculated by deduplicating the number of rejected users (n). The number of sampling points accumulated from the number of rejected users n and below within that period is divided by the total number of sampling points to determine the service satisfaction rate. The minimum number Y corresponding to a satisfaction rate of 80% or higher is used to determine the number of additional licenses.

[0097] The following reference Figure 4 To describe an electronic device 400 according to this embodiment of the present invention. Figure 4 The electronic device 400 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0098] like Figure 4 As shown, the electronic device 400 is manifested in the form of a general-purpose computing device. The components of the electronic device 400 may include, but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including storage unit 420 and processing unit 410).

[0099] The storage unit stores program code that can be executed by the processing unit 410, causing the processing unit 410 to perform the steps described in the "Embodiment Methods" section of this specification according to various exemplary embodiments of the present invention.

[0100] Storage unit 420 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 421 and / or cache memory 422, and may further include a read-only memory (ROM) 423.

[0101] Storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0102] Bus 430 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0103] Electronic device 400 can also communicate with one or more external devices (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 400, and / or any device that enables electronic device 400 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 450. Furthermore, electronic device 400 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 460. As shown, network adapter 460 communicates with other modules of electronic device 400 via bus 430. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0104] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0105] According to the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the present invention can also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the present invention described in the "Exemplary Methods" section above.

[0106] refer to Figure 5 As shown, a program product 500 for implementing the above-described method according to an embodiment of the present invention is described. It may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0107] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0108] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0109] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0110] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0111] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0112] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

[0113] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

Claims

1. A software license resource planning method, characterized in that, include: Obtain information on the usage of software license resources; Based on the software license resource usage, obtain the number of times users were denied access when resources were insufficient, and the number of users used when resources were sufficient; Plan software licensing resources based on the number of times or usage; Specifically, based on the set licensed resource usage load rate, the number of licensed resources used at each sampling point is counted to calculate the percentage of usage at each sampling point; The percentage of usage for each sample point is calculated and compared with the set permitted resource usage load rate to filter out sample points that are less than or equal to the load rate. The required number of licensed resources is calculated based on the ratio between the number of sampling points less than or equal to the load rate and the total number of sampling points. Based on the difference between the current total licensed resource data and the current required number of licensed resources, the number of licensed resources that need to be reduced is calculated in order to plan the software licensed resources.

2. The method according to claim 1, characterized in that, The step of obtaining the number of times a user was denied access when resources were insufficient, based on the software license resource usage, includes: Set the licensed resource usage satisfaction rate; If the current utilization rate of the licensed resources reaches the set satisfaction rate, then obtain the number of times the licensed server refused access within each sampling point, and deduplicate users who accessed multiple times to obtain the number of times users were refused access when resources were insufficient.

3. The method according to claim 1, characterized in that, The step of obtaining the usage count when resources are sufficient based on the software license resource usage status includes: Set the licensed resource usage load rate; Obtain the number of licensed resources used at each sampling point below the licensed resource usage load rate.

4. The method according to claim 1, characterized in that, The step of planning software license resources based on the number of times includes: Calculate the percentage of each sampling point out of the total number of sampling points based on the number of times each sampling point was denied access by the server; The percentage of each calculated sampling point is compared with the set permitted resource usage satisfaction rate to filter out sampling points that are less than or equal to the satisfaction rate; The number of additional licensed resources needed is calculated based on the ratio between the sampling points that are less than or equal to the satisfaction rate and the total number of sampling points, in order to plan the software licensed resources.

5. The method according to claim 1, characterized in that, The acquisition of software license resource usage information includes: The established software license resource management terminal, Automatically collect current licensed resource usage data based on preset time intervals; Using the established software license resource management terminal, the automatically collected current license resource usage data is analyzed and processed to obtain the software license resource usage quantity at each sampling point.

6. The method according to claim 5, characterized in that, The automatic collection of currently licensed resource usage data also includes: Store the currently licensed resource usage data that is automatically collected.

7. A software license resource planning device, characterized in that, include: The resource management terminal is used to obtain information on the usage of software license resources. The acquisition module is used to acquire, based on the software license resource usage, the number of times a user was denied access when resources were insufficient, and the number of times resources were used when resources were sufficient. A planning module is used to plan software license resources based on the number of times or the amount of use; Based on the set licensed resource usage load rate, the number of licensed resources used at each sampling point is counted to calculate the percentage of usage at each sampling point; The percentage of usage for each sample point is calculated and compared with the set permitted resource usage load rate to filter out sample points that are less than or equal to the load rate. The required number of licensed resources is calculated based on the ratio between the number of sampling points less than or equal to the load rate and the total number of sampling points. Based on the difference between the current total licensed resource data and the current required number of licensed resources, the number of licensed resources that need to be reduced is calculated in order to plan the software licensed resources.

8. An electronic device, characterized in that, The electronic device includes: processor; A memory storing computer-readable instructions that, when executed by the processor, implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores computer program instructions that, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 6.

Images