Software license resource planning method and device, equipment and storage medium

Abstract

The invention discloses a software license resource planning method and device, equipment and a storage medium. The method comprises the following steps: acquiring a software license resource use condition; according to the use condition of the software license resources, obtaining the number of times that the user is denied to access when the resources are insufficient and the use number when the resources are sufficient; and planning the software license resources according to the number of times or the use number. According to the method and the device, the software license resources can be accurately planned, so that the purchase of excessive license resources can be avoided, the cost is saved, meanwhile, the software license resources can be more effectively utilized through centralized management and scheduling, and the resource utilization rate is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of resource management, and in particular to a method, device, equipment and storage medium for software license resource planning. Background Art

[0002] A software license is a paid or unpaid permission granted to a software user to use the software. It is a right granted by the software developer or owner to the user to use the software under explicit authorization, as long as the paid license fee is paid or the unpaid license fee is met. Since software development is a very costly process, software licensing is a way to compensate software developers for their investment, allowing users to use the software under certain constraints, and also a protection for software copyright.

[0003] As the digital transformation of information technology is further promoted, enterprises have a growing demand for software, and the annual cost of software licenses often becomes an important part of the enterprise IT budget. In order to maintain competitiveness, enterprises need to reasonably control costs. Therefore, software license resource planning becomes particularly important.

[0004] At present, the existing technology mainly solves the technical problem of low license resource utilization in the process of managing application license resources, and does not involve software license resources, that is, there is no suitable way to monitor and predict software licenses, and no reasonable data quantification is performed.

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

[0006] The main purpose of the present invention is to provide a software license resource planning method, device, equipment and storage medium, which can avoid purchasing too many 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 used more effectively and resource utilization can be improved.

[0007] In a first aspect, the present application provides a method for software license resource planning, wherein the method comprises the steps of:

[0008] Obtain software license resource usage;

[0009] According to the usage of the software license resources, the number of times the user is denied access when the resources are insufficient and the number of times the user is used when the resources are sufficient are obtained;

[0010] Software licensing resources are planned based on the times or usage quantities.

[0011] In combination with the first aspect above, as an optional implementation method, setting a permitted resource usage satisfaction rate;

[0012] If the current usage rate of licensed resources reaches the set satisfaction rate, the number of times the licensed server denies access at each sampling point is obtained, and users who have visited multiple times are deduplicated to obtain the number of times users are denied access when resources are insufficient.

[0013] In combination with the first aspect above, as an optional implementation method, setting a permitted resource usage load rate;

[0014] The permitted resource usage quantity of each sampling point below the permitted resource usage load rate is obtained.

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

[0016] Compare the calculated percentage of each sampling point 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 license resources that need to be increased is calculated according to the ratio of the sampling points that are less than or equal to the satisfaction rate to the total sampling points, so as to plan the software license resources.

[0018] In combination with the first aspect, as an optional implementation, based on the set licensed resource usage load rate, the usage quantity of each sampling point is counted to calculate the percentage of the usage quantity of each sampling point;

[0019] Compare the calculated percentage of the number of samples used at each sampling point with the set permitted resource usage load rate to filter out sampling points that are less than or equal to the load rate;

[0020] Calculating the currently required number of licensed resources according to the ratio between the sampling points less than or equal to the load rate and the total sampling points;

[0021] The number of license resources that need to be reduced is calculated based on the difference between the current total license resource data and the currently required number of license resources, so as to plan the software license resources.

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

[0023] Automatically collect current license resource usage data based on preset interval time points;

[0024] The established software license resource management terminal is used to analyze and process the automatically collected current license resource usage data to obtain the software license resource usage quantity at each sampling point.

[0025] In combination with the above first aspect, as an optional implementation manner, the automatically collected current permitted resource usage data is stored.

[0026] In a second aspect, the present application provides a software license resource planning device, the device comprising:

[0027] Resource management end, which is used to obtain the usage of software license resources;

[0028] An acquisition module, which is used to acquire, based on the usage of the software license resources, the number of times that users are denied access when resources are insufficient, and the number of times that users are used when resources are sufficient;

[0029] The planning module is used to plan the software license resources according to the times or usage quantities.

[0030] In a third aspect, the present application further provides an electronic device, comprising: a processor; a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the method described in any one of the first aspects is implemented.

[0031] In a fourth aspect, the present application further provides a computer-readable storage medium storing computer program instructions, which, when executed by a computer, enables the computer to execute any of the methods described in the first aspect.

[0032] The present application provides a software license resource planning method, device, equipment and storage medium, wherein the method comprises the steps of: obtaining the usage of software license resources; obtaining the number of times when the resources are insufficient and the number of times when the resources are sufficient according to the usage of the software license resources; and planning the software license resources according to the number of times or the number of times. The present application can avoid purchasing too many license resources by accurately planning software license resources, thereby saving costs, and can more effectively utilize software license resources and improve resource utilization through centralized management and scheduling.

[0033] It is to be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings, which are incorporated in and constitute a 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 A flowchart of a software license resource planning method provided in an embodiment of the present application;

[0036] Figure 2 A schematic diagram of a software license resource planning device provided in an embodiment of the present application;

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

[0038] Figure 4 A schematic diagram of an electronic device provided in an embodiment of the present application;

[0039] Figure 5 A schematic diagram of a computer-readable program medium provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0041] Furthermore, the drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. Some of the blocks shown in the drawings are functional entities and do not necessarily correspond to physically or logically separate entities.

[0042] The embodiments of the present application provide a software license resource planning method, apparatus, device and storage medium, which can avoid purchasing too many 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 more effectively utilized to improve resource utilization.

[0043] In order to achieve the above technical effects, the general idea of ​​this application is as follows:

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

[0045] S101: Obtaining software license resource usage.

[0046] S102: According to the software license resource usage, obtain the number of times the user is denied access when resources are insufficient and the number of times the user is used when resources are sufficient.

[0047] S103: Planning software license resources according to the number of times or the usage quantity.

[0048] The embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0049] Reference Figure 1 , Figure 1 FIG. 1 is a flow chart of a software license resource planning method provided by the present invention. Figure 1 As shown, the method comprises the steps of:

[0050] Step S101: Obtaining software license resource usage.

[0051] Specifically, the established software license resource management terminal automatically collects current license resource usage data based on preset interval time points; the established software license resource management terminal is used to analyze and process the automatically collected current license resource usage data to obtain the software license resource usage quantity at each sampling point.

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

[0053] For ease of understanding, an example is given to establish a software license resource management terminal to monitor the license resources of the license server. The administrator sets a specified sampling time point to automatically collect and store data. By capturing information over a period of time, resource data is collected and this period of time is divided into N sampling points. Each sampling point is 10 minutes, and the usage data of multiple sampling points is obtained.

[0054] For example, if N is set to 10, the current software usage count of the first sampling point is collected, and then the current software usage count of the second sampling point is collected after an interval of 10 minutes.

[0055] It is important to explain that a software license is a paid or unpaid permission granted to software users to use the software. It is a right granted by the software developer or owner to users to use the software under explicit authorization, as long as the paid license fee is paid or the unpaid license fee is met. Since software development is a very costly process, software licensing is a way to compensate software developers for their investment, allowing users to use the software under certain constraints, and also a protection for software copyright.

[0056] Step S102: According to the software license resource usage, obtain the number of times the user is denied access when resources are insufficient and the number of times the user is used when resources are sufficient.

[0057] Specifically, the usage satisfaction rate of licensed resources is set; if the current usage rate of licensed resources reaches the set satisfaction rate, the number of times the licensed server denies access in each sampling point is obtained, and users who have visited multiple times are deduplicated to obtain the number of times users are denied access when resources are insufficient.

[0058] For ease of understanding, an example is given. The satisfaction rate of licensed resource usage is set to 80%. If the current licensed resource reaches 80%, and there are still users accessing the server at this time, the server will deny the user's access because the current resource usage has reached the upper limit. The server will count the number of denials and deduplicate multiple visits by the same user. That is, if a user is denied multiple times, it will only be counted as one, and the number of times the user is denied access when the resource is at full load (that is, the set satisfaction rate) is obtained.

[0059] The permitted resource usage load rate is set; and the permitted resource usage quantity of each sampling point below the permitted resource usage load rate is obtained.

[0060] For ease of understanding, an example is given, in which the resource usage load rate is set to 70%, and the permitted resource usage amounts of all sampling points below 70% are obtained.

[0061] Step S103: Planning software license resources according to the number of times or usage quantity.

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

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

[0064] According to the ratio between the sampling points that are less than or equal to the satisfaction rate and the total sampling points, the number of license resources that need to be added is calculated to plan the software license resources. It can be understood that, for example, there are 100 sampling points, and the number of rejections for each sampling point is calculated. If 70 of the sampling points are rejected 4 times, then this number of rejections 4 accounts for 70%. At this time, 4 license resources need to be added to meet the requirement.

[0065] For example, the license increase forecast is based on the user department's frequent rejection of licenses when the license is fully used. For a floating license software, the license is fully used within a period of time. At this time, some users still apply for module licenses, which will be rejected by the license server. A user who is repeatedly rejected for obtaining a license within an hour is recorded as a rejected user.

[0066] If the license is full within a certain period of time, and there are still some users who need the license, they will be rejected by the license server. If a user is rejected multiple times, the number of rejections will be recalculated, and the total number of rejections is the number of rejections. The rejection records of the license server will be collected and captured to the database of the license management end to calculate the business satisfaction rate. First, the number of rejections in each sampling point is counted. The number of rejections may be 1, 2, 3, or 4. For example, the business satisfaction rate of the number of rejections of 2 is equal to the number of samples with a rejection number of 2 or less among all sampling points divided by the total number of samples. Assuming it is 80%, it can be concluded that adding 2 licenses will meet all requirements. It can be understood that, for example, if there are 10 sampling points, the first sampling point rejects users A and B, then the number of rejections is 2, the second one rejects user C, then the number of rejections is 1, and the subsequent rejections are all 1. If all sampling points with ≤2 account for 80% of the total sampling points, then 2 is taken, which means that the number of license resources needs to be increased by 2.

[0067] In one embodiment, based on the set permitted resource usage load rate, the permitted resource usage quantity of each sampling point is counted to calculate the percentage of the usage quantity of each sampling point;

[0068] Compare the calculated percentage of the number of samples used at each sampling point with the set permitted resource usage load rate to filter out sampling points that are less than or equal to the load rate;

[0069] Calculating the currently required number of licensed resources according to the ratio between the sampling points less than or equal to the load rate and the total sampling points;

[0070] The number of license resources that need to be reduced is calculated based on the difference between the current total license resource data and the currently required number of license resources, so as to plan the software license resources.

[0071] It can be understood that, for example, the load rate is set to 80%, and the number of resources currently used among the 10 sampling points is 8, that is, the number of resources used 8 accounts for 80% of the total sampling. If the total resources are 10 at this time, and the current usage is 8, then 2 can be reduced for planning management.

[0072] For ease of understanding, an example is given. Set the load rate (the number of sampling points that are equal to or less than the "assessed usage number" / total number of sampling points * 100% is the load rate) and calculate the assessment number. The corresponding authorized usage value when the load rate is closest to the set value is the assessment number. For license reduction prediction, the assessment number corresponding to the load rate is the required usage number. The required usage number is subtracted from the current total number to obtain the reduced number. For example, using a load rate of 8 licenses means that the cumulative number of sampling points that use 8 licenses and less than 8 licenses within a period of time is 8 divided by the total number of sampling points, which is 10, resulting in a load rate of 80% for the licensed resources. The current total number of licenses is 10, and the set value is 8, so it is determined that 2 licenses need to be reduced.

[0073] Reference Figure 2 , Figure 2 FIG. 1 is a schematic diagram of a software license resource planning device provided by the present invention, such as Figure 2 As shown, the device comprises:

[0074] Resource management terminal 201: used to obtain the usage of software license resources.

[0075] The acquisition module 202 is used to acquire the number of times that user access is denied when resources are insufficient and the number of times that users are used when resources are sufficient, according to the usage of the software license resources.

[0076] Planning module 203: It is used to plan the software license resources according to the times or usage quantities.

[0077] Further, in a possible implementation manner, the acquisition module is further used to set the permitted resource usage satisfaction rate;

[0078] If the current usage rate of licensed resources reaches the set satisfaction rate, the number of times the licensed server denies access at each sampling point is obtained, and users who have visited multiple times are deduplicated to obtain the number of times users are denied access when resources are insufficient.

[0079] Furthermore, in a possible implementation, the acquisition module is further used to set the permitted resource usage load rate;

[0080] The permitted resource usage quantity of each sampling point below the permitted resource usage load rate is obtained.

[0081] Furthermore, in a possible implementation manner, the planning module is further used to calculate the percentage of each sampling point to the total sampling points according to the number of times each sampling point is denied access by the server;

[0082] Compare the calculated percentage of each sampling point 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 license resources that need to be increased is calculated according to the ratio of the sampling points that are less than or equal to the satisfaction rate to the total sampling points, so as to plan the software license resources.

[0084] Further, in a possible implementation manner, the planning module is further used to count the usage quantity of the licensed resources at each sampling point based on the set usage load rate of the licensed resources, so as to calculate the percentage of the usage quantity at each sampling point;

[0085] Compare the calculated percentage of the number of samples used at each sampling point with the set permitted resource usage load rate to filter out sampling points that are less than or equal to the load rate;

[0086] Calculating the currently required number of licensed resources according to the ratio between the sampling points less than or equal to the load rate and the total sampling points;

[0087] The number of license resources that need to be reduced is calculated based on the difference between the current total license resource data and the currently required number of license resources, so as to plan the software license resources.

[0088] Furthermore, in a possible implementation manner, the resource management end is also used to establish a software license resource management end,

[0089] Automatically collect current license resource usage data based on preset interval time points;

[0090] The established software license resource management terminal is used to analyze and process the automatically collected current license resource usage data to obtain the software license resource usage quantity at each sampling point.

[0091] Furthermore, in a possible implementation manner, the resource management end is also used to store the automatically collected current permitted resource usage data.

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

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

[0094] It can be understood that the load rate of using license 8 means that the cumulative sampling points of using 8 licenses and less than 8 licenses within a period of time are 8 divided by the total sampling points of 10, and the load rate of the licensed resources is 80%. The current total number of licenses is 10 and the set value is 8, so it is judged that the license needs to be reduced by 2.

[0095] In one embodiment, within a period of time, the cumulative number of sampling points using m licenses and less is divided by the total number of sampling points to be determined as the resource load rate. The authorization value corresponding to the load rate closest to the set value is the evaluation number X. The existing total number minus the required number X is used to obtain the number of reduced licenses.

[0096] If a user is rejected due to insufficient resources, the total number of rejected users is deduplicated and is considered to be n. The service satisfaction rate is determined by dividing the accumulated sampling points of n and below rejected people during the period by the total number of sampling points. The minimum number Y corresponding to 80% and above is used to determine the number of additional licenses.

[0097] Refer to the following Figure 4 An electronic device 400 according to this embodiment of the present invention will be described. Figure 4 The electronic device 400 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0098] like Figure 4 As shown, the electronic device 400 is in the form of a general 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 the storage unit 420 and the processing unit 410).

[0099] The storage unit stores program codes, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps according to various exemplary embodiments of the present invention described in the above “Embodiment Method” section of this specification.

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

[0101] The 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 of which or some combination may include an implementation of a network environment.

[0102] Bus 430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0103] The electronic device 400 may also communicate with one or more external devices (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 400, and / or communicate with any device that enables the electronic device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 450. Furthermore, the electronic device 400 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 460. As shown, the network adapter 460 communicates with other modules of the electronic device 400 via a bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the 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, etc.

[0104] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0105] According to the solution of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present invention can also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present invention described in the above "Exemplary Method" section of the present specification.

[0106] refer to Figure 5 As shown, a program product 500 for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be 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, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

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

[0108] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0109] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

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

[0111] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0112] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

[0113] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

Claims

1. A software license resource planning method, It is characterized in that include: Obtain software license resource usage; According to the usage of the software license resources, the number of times the user is denied access when the resources are insufficient and the number of times the user is used when the resources are sufficient are obtained; Software licensing resources are planned based on the times or usage quantities.

2. The method according to claim 1, It is characterized in that The obtaining, according to the software license resource usage, the number of times that the user is denied access when the resources are insufficient, comprises: Set the usage satisfaction rate of licensed resources; If the current usage rate of licensed resources reaches the set satisfaction rate, the number of times the licensed server denies access at each sampling point is obtained, and users who have visited multiple times are deduplicated to obtain the number of times users are denied access when resources are insufficient.

3. The method according to claim 1, It is characterized in that The obtaining, based on the software license resource usage, the usage quantity counted when the resources are sufficient, includes: Set the permitted resource usage load rate; The permitted resource usage quantity of each sampling point below the permitted resource usage load rate is obtained.

4. The method according to claim 1, It is characterized in that The planning of software license resources according to the number of times includes: According to the number of times each sampling point is denied access by the server, calculate the percentage of each sampling point in the total sampling points; Compare the calculated percentage of each sampling point 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 license resources that need to be increased is calculated according to the ratio of the sampling points that are less than or equal to the satisfaction rate to the total sampling points, so as to plan the software license resources.

5. The method according to claim 1, It is characterized in that The planning of software license resources according to the usage quantity includes: Based on the set license resource usage load rate, the license resource usage quantity of each sampling point is counted to calculate the percentage of the usage quantity of each sampling point; Compare the calculated percentage of the number of samples used at each sampling point with the set permitted resource usage load rate to filter out sampling points that are less than or equal to the load rate; Calculating the currently required number of licensed resources according to the ratio between the sampling points less than or equal to the load rate and the total sampling points; The number of license resources that need to be reduced is calculated based on the difference between the current total license resource data and the currently required number of license resources, so as to plan the software license resources.

6. The method according to claim 1, It is characterized in that The obtaining of software license resource usage includes: The software license resource management terminal established, Automatically collect current license resource usage data based on preset interval time points; The established software license resource management terminal is used to analyze and process the automatically collected current license resource usage data to obtain the software license resource usage quantity at each sampling point.

7. The method according to claim 6, It is characterized in that The automatic collection of current license resource usage data also includes: The automatically collected usage data of current licensed resources is stored.

8. A software license resource planning device, It is characterized in that include: Resource management end, which is used to obtain the usage of software license resources; An acquisition module, which is used to acquire, based on the usage of the software license resources, the number of times that users are denied access when resources are insufficient, and the number of times that users are used when resources are sufficient; The planning module is used to plan the software license resources according to the times or usage quantities.

9. An electronic device, It is characterized in that The electronic device comprises: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, It is characterized in that The computer program instructions are stored therein, and when the computer program instructions are executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 7.

Images