A license management method, device, system and medium for distributed database

Abstract

The present invention provides a license management method, device, system and medium for a distributed database, including: obtaining customer demand information, generating contract information according to the demand information; entering the contract information into a license management system, the license management system generating a unique authorization code according to the contract information; generating a license file according to the authorization code, the contract information and server environment information; performing import real-time verification and periodic verification on the license file; after the license file is verified, deploying a distributed database according to the license file. The present invention generates a license file by acquiring contract information, authorization code and server environment collection and performs real-time verification, thereby ensuring the security, legality and flexibility of authorization.

Description

Technical Field

[0001] The present invention relates to the technical field of distributed databases, and in particular to a license management method, device, system and medium for distributed databases. Background Art

[0002] The financial-grade distributed database system connects geographically dispersed local nodes through a computer network to form a logically unified database system. Such a system has the advantages of improving data processing performance, good flexible scalability, high availability and reliability, so more and more financial companies choose to use distributed databases in core business systems for production. However, the license management method in the prior art cannot meet the diverse requirements of different users for resource needs and version function control, and there is no effective mechanism to prevent license duplication and abuse, and ensure the security and legality of software use. In addition, the lack of real-time and effective management of server resources and software function usage makes it difficult to flexibly expand resources and use them for a long time. At the same time, the existing method lacks a centralized license management system, which makes it inconvenient to apply, query, expand capacity, renew, etc., and it is difficult to achieve resource management and function updates for multiple customers. Summary of the invention

[0003] In view of the above-mentioned deficiencies in the prior art, the purpose of the present invention is to provide a license management method for a distributed database, which solves the problems of legitimacy verification, resource control and authorization status monitoring in the authorization management of a distributed database.

[0004] In order to achieve the above object, the present invention adopts the following technical solutions:

[0005] A first aspect of the present invention provides a license management method for a distributed database, comprising the following steps:

[0006] Obtaining customer demand information, and generating contract information based on the demand information;

[0007] Entering the contract information into a license management system, and the license management system generating a unique authorization code according to the contract information;

[0008] Generate a License file according to the authorization code, the contract information and the server environment information;

[0009] Performing import real-time verification and periodic verification on the license file;

[0010] After the license file is verified, the distributed database is deployed according to the license file.

[0011] In one embodiment, generating a license file according to the authorization code, the contract information and the server environment information includes:

[0012] Use collection tools to obtain server environment information required for deploying distributed databases;

[0013] Generate a unique server identification code according to the server environment information;

[0014] Fill the authorization code, the contract information and the server unique identification code into the license file template to generate a license file.

[0015] In one embodiment, the real-time import verification of the license file includes:

[0016] Performing encryption verification on the License file, and when the encryption verification of the License file passes, parsing the License file to extract authorization information;

[0017] Determine the authorization status of the license in the distributed database according to the authorization information, and when the license in the distributed database is in the authorized state, check whether the unique identification code of the license file is repeated with the unique identification code of the license already existing in the current system;

[0018] When the unique identification code of the license file does not overlap with the unique identification code of the existing license, verify whether the validity period in the authorization information has expired;

[0019] When the validity period has not expired, verifying whether the quantity of authorized resources in the authorization information is greater than the total amount of current system resources;

[0020] When the number of authorized resources meets the requirement, verify whether the server identifier bound in the authorization information matches the current system server;

[0021] When the above-mentioned verifications all meet the requirements, the license management module in the distributed database updates the new license information to the cache and updates the authorization status of the current database system.

[0022] In one embodiment, the periodic verification of the license file includes:

[0023] Compare whether the validity period of the license file is less than the current system time;

[0024] When the validity period is less than the current system time, the License file is considered to have expired, the authorization status of the database system's License is updated to authorized-invalid, and database-related functions are restricted according to the expiration processing policy.

[0025] In one embodiment, the periodic verification of the license file further includes:

[0026] Compare the authorized resource quantity of the license file with the server resources;

[0027] Determine whether the number of authorized resources is greater than the server resources. When the number of authorized resources is less than the server resources, it is considered that the current database system server resources exceed the resource limit, and the authorization status of the database system's license is updated to authorized-invalid, and the database-related functions are restricted according to the resource limit policy.

[0028] In one embodiment, the periodic verification of the license file further includes:

[0029] Check whether the server unique identification code in the license file matches the current environment;

[0030] When the unique identification code of the server does not match the current environment, the authorization status of the License of the database system is updated to authorized-failure, an alarm is issued and the start time of the failure is recorded.

[0031] In one embodiment, the license management system specifically includes:

[0032] The license management system updates and stores the contract information, authorization code and server environment information;

[0033] Verifying the contract information, authorization code and server environment information;

[0034] After verification, a license file is generated according to the authorization code, the contract information and the server environment information;

[0035] The license file is renewed, replaced, expanded, queried, downloaded and offlined through the license management system.

[0036] A license management device for a distributed database, the device comprising:

[0037] An information acquisition module is used to acquire customer demand information and generate contract information based on the demand information;

[0038] An information entry module, used to enter the contract information into a license management system, and the license management system generates a unique authorization code according to the contract information;

[0039] A file generation module, used to generate a license file according to the authorization code, the contract information and the server environment information;

[0040] A file verification module, used to perform real-time verification and periodic verification on the license file when it is imported;

[0041] The file deployment module is used to deploy a distributed database according to the license file after the license file is verified.

[0042] A license management system for a distributed database, the system comprising at least one processor; and

[0043] a memory communicatively connected to the at least one processor; wherein,

[0044] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the license management method for the distributed database.

[0045] A non-volatile computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by one or more processors, the one or more processors can execute the license management method for the distributed database.

[0046] Beneficial Effects :The embodiment of the present invention discloses a license management method, device, system and medium for a distributed database. Compared with the prior art, the present invention relates to contract information entry, authorization code generation, server environment acquisition, license file generation and real-time verification. It is implemented through the license management system to ensure the security, legitimacy and flexibility of authorization, and solve the problems of legitimacy verification, resource control and authorization status monitoring in distributed database authorization management. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0048] Figure 1 A flowchart of a license management method for a distributed database provided by an embodiment of the present invention;

[0049] Figure 2A real-time verification flow chart of a license management method for a distributed database provided by an embodiment of the present invention;

[0050] Figure 3 A flow chart of the timed verification of the license management method of the distributed database provided by the embodiment of the present invention;

[0051] Figure 4 A schematic diagram of the functional modules of a license management device for a distributed database provided by an embodiment of the present invention;

[0052] Figure 5 A schematic diagram of the hardware structure of a license management system for a distributed database provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0053] In order to make the technical problems, technical solutions and beneficial effects to be solved by the embodiments of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0054] See also Figure 1 , Figure 1 The flowchart of an embodiment of the license management method of the distributed database provided by the present invention specifically includes the following steps:

[0055] S100, obtaining customer demand information, and generating contract information according to the demand information;

[0056] S200, entering the contract information into a license management system, and the license management system generates a unique authorization code according to the contract information;

[0057] S300, generating a license file according to the authorization code, the contract information and the server environment information;

[0058] S400, performing import real-time verification and periodic verification on the license file;

[0059] S500: After the license file is verified, a distributed database is deployed according to the license file.

[0060] In this embodiment, the service provider signs a contract according to customer needs, and the contract information mainly includes the validity period, authorized resource type, authorized resource quantity, and authorized version function type. After the license management system enters the above contract information, it generates a unique authorization code, which is bound to the contract. An authorization code can be allocated different resource quantities and validity periods according to customer needs to make multiple different license files to install multiple sets of distributed database environments. Use the provided collection tool to collect the server environment information that the customer needs to deploy a distributed database, including CPU information, memory information, network card information, host information, etc. The collected server information can be combined with one or more of the information as the unique identifier of the server according to the actual installation environment. After the above preset information is generated, fill in the authorization code, the validity period of deploying a single set of distributed database system, the number of authorized resources, the unique identifier of the management module server, the expiration processing strategy, and the full amount processing strategy to generate a license file with a unique identifier. Then, the license file is imported for real-time verification and timed verification. After the license file is verified, the distributed database is deployed according to the license file.

[0061] The present invention is applied to distributed databases, and service providers can flexibly adjust resource expansion and function control according to customer needs to maintain the security and legality of software use. The license maintains the legality of the database by binding the contract number; by binding the unique identifier of the installation server (such as the MAC address), the license is prevented from being copied and abused, ensuring the uniqueness of the license and the security of database use; at the same time, it supports providing different versions of licenses according to customer needs, including standard version, enterprise version, single-machine cluster standard version and single-machine cluster enterprise version; supports controlling resource restrictions in two ways: the number of nodes and the number of cores; and supports multiple optional processing strategies for situations where the license expires or exceeds the limited resources.

[0062] A new license management method is provided for distributed databases, which is managed by the license management module under the management module. Since the license provides different versions of functions, different resource quantity types, different full-amount processing strategies, different expiration processing strategies, and different server unique identification types, compared with the current license management method, the distributed database is more flexible in terms of resource use, function control, and exception handling of the license. At the same time, you can choose to bind different server identifiers according to the actual situation of the installation environment, which is also more reasonable when verifying the installation environment. Verifying the server unique identifier also avoids the copying and abuse of the license. Combining the two methods of real-time verification and scheduled verification can ensure the accuracy of the new import and update of the license, and at the same time, regular verification can ensure the legality and stability of the system use.

[0063] In one embodiment, generating a license file according to the authorization code, the contract information and the server environment information includes:

[0064] Use collection tools to obtain server environment information required for deploying distributed databases;

[0065] Generate a unique server identification code according to the server environment information;

[0066] Fill the authorization code, the contract information and the server unique identification code into the license file template to generate a license file.

[0067] In this embodiment, the provided collection tool is used to collect the server environment information on which the customer needs to deploy a distributed database, including CPU information, memory information, network card information, host information, etc. The collected server information can combine one or more of the information as a unique server identifier based on the actual installation environment.

[0068] Specifically, the license version function types include standard version, enterprise version, single-machine cluster enterprise version and single-machine cluster standard version to meet the needs of different customers. Distributed databases support distributed and centralized tenants, so the license version function provides corresponding types.

[0069] Validity period and authorized resources: A license can be set to a specific expiration date (validity period) or permanent (indefinite).

[0070] Authorized resources: Authorized resources can be the number of nodes or CPU cores, which can be divided into limited and unlimited. Limited refers to the specific number of authorized resources, while unlimited means that there is no limit on the use of resources.

[0071] The number of nodes is calculated by the number of CPU cores. The specific conversion relationship is as follows:

[0072] Physical machine: Every two central processing units (CPUs) count as one node, so for a four-way server, two nodes need to be defined;

[0073] Virtual machines: 48 VCPUs are used as the limit. Nodes with less than 48 VCPUs are counted as 1. The sum of all nodes with 48 VCPUs or more is rounded up to 48. [1,48) is 1 node, [48,96) is 2 nodes, and [96,144) is 3 nodes.

[0074] Container: A container is a node.

[0075] Server unique identifier: You can choose to use the server's physical attribute information (such as MAC address) as the unique identifier.

[0076] Expiration processing strategy: including alarm + expansion restriction, alarm only, no alarm and no restriction, alarm + expansion restriction + service suspension and other options.

[0077] Full quota handling strategy: including alarm + expansion limit, alarm only, no alarm and no limit and other options.

[0078] It ensures that the license file can be accurately generated according to the contract terms and server environment, and the legal use of the database is maintained through the license management module. Through these detailed steps and rules, the system can effectively manage the life cycle of the license, ensure the compliance of software use, and take appropriate measures when the authorization expires or reaches the limit.

[0079] In one embodiment, the real-time import verification of the license file includes:

[0080] Performing encryption verification on the License file, and when the encryption verification of the License file passes, parsing the License file to extract authorization information;

[0081] Determine the authorization status of the license in the distributed database according to the authorization information, and when the license in the distributed database is in the authorized state, check whether the unique identification code of the license file is repeated with the unique identification code of the license already existing in the current system;

[0082] When the unique identification code of the license file does not overlap with the unique identification code of the existing license, verify whether the validity period in the authorization information has expired;

[0083] When the validity period has not expired, verifying whether the quantity of authorized resources in the authorization information is greater than the total amount of current system resources;

[0084] When the number of authorized resources meets the requirement, verify whether the server identifier bound in the authorization information matches the current system server;

[0085] When the above-mentioned verifications all meet the requirements, the license management module in the distributed database updates the new license information to the cache and updates the authorization status of the current database system.

[0086] In this embodiment, Figure 2As shown in the figure, the license file is encrypted and verified to determine whether the encrypted content of the license file is legal. If it is illegal, an error message is displayed and the original authorization status of the license file is maintained. When the license file encryption verification passes, the license is parsed to determine whether the encrypted content of the license file is legal. If the parsing fails, an error message is displayed and the original authorization status of the license is maintained. If the license file is parsed successfully, the authorization information is obtained. The authorization status of the current License management system is determined according to the authorization information. When the authorization status of the License in the distributed database is authorized, it is determined whether the unique identification code of the License file is repeated with the unique identification code of the License already existing in the current system. If it is determined to be repeated, an error is reported and the system is exited. When the unique identification code of the License file is not repeated with the unique identification code of the existing License or the current system License has not been authorized, it is verified whether the validity period in the authorization information has expired. When the validity period has not expired, it is verified whether the number of authorized resources in the authorization information is greater than the total number of resources in the current system. When the number of authorized resources meets the requirements, it is verified whether the server identifier bound in the authorization information matches the server of the current system. When the server identifier bound in the authorization information matches the server of the current system, all of the above calibrations meet the requirements, the License management module in the distributed database updates the new License information to the cache, and updates the authorization status of the current database system. If one of them does not meet the conditions, an error is reported and the system is exited, and the original authorization status of the License is maintained.

[0087] Specifically, the license authorization status refers to a license management status used to identify the current system after the distributed database parses and verifies the license file content. The authorization status can intuitively reflect the system's verification results on the license file content.

[0088] Specifically, the unauthorized state means that the license file has not been imported into the current database system or the imported license file is damaged. The default values ​​are used for license control. The default values ​​are as follows:

[0089]

[0090]

[0091] The authorized status is normal, and the database system is controlled according to the attributes of the imported license.

[0092] In one embodiment, the periodic verification of the license file includes:

[0093] Compare whether the validity period of the license file is less than the current system time;

[0094] When the validity period is less than the current system time, the License file is considered to have expired, the authorization status of the database system's License is updated to authorized-invalid, and database-related functions are restricted according to the expiration processing policy.

[0095] In this embodiment, Figure 3 As shown, the database records the authorization status of the current license system in real time to identify the current license system control status. The system sets a timer to periodically check the validity of the license. When the timer is triggered, the system compares whether the validity period specified in the license file has expired, that is, whether the validity period of the license file is less than the current system time (system time threshold). When the validity period is less than the current system time, the license file time is considered to have expired, and the authorization status of the license of the database system is updated to authorized-invalid, and the database-related functions are restricted according to the expiration processing strategy.

[0096] Furthermore, expiration processing strategies include: (1) Alarm + resource restriction, the system issues a warning through the alarm module and restricts further resource expansion to prevent usage beyond the authorized scope; (2) Alarm only, the system only issues a warning through the alarm module, but does not restrict further resource expansion, allowing the system to continue running but reminding the administrator of the issue of license expiration; (3) No alarm and no restriction, the system does not issue any warning and does not restrict further resource expansion. In this case, the system may continue to run, but there is a risk of violating the license agreement; (4) Alarm + resource restriction + business suspension, in addition to issuing warnings and restricting resource expansion, the system will also notify relevant business departments to stop services to ensure that the license agreement is not violated. The system automatically performs corresponding operations according to the policies set in the license management system. These operations are designed to protect the compliance of software licensing while minimizing the impact on business operations.

[0097] Specifically, the authorized-invalid state means that the license file has expired, the current system resources exceed the total number of resources specified in the license, or the fault exceeds 30 days, and the authorization state is set to authorized-invalid. After the expiration, if it is an expiration failure, the system will perform the corresponding processing according to the expiration processing strategy; if it is an over-limit failure, the system will perform the corresponding processing according to the full-limit processing strategy; if it is a fault failure, the system will report an alarm through the alarm module and limit the expansion of resources.

[0098] It further ensures that the system can automatically monitor and manage the validity period of the license, respond to the license expiration issue in a timely manner, and take corresponding measures according to the preset strategy to maintain the legality and security of software use. At the same time, it also provides a notification mechanism for system administrators to handle license expiration issues so that they can take timely measures.

[0099] In one embodiment, the periodic verification of the license file further includes:

[0100] Compare the authorized resource quantity of the license file with the server resources;

[0101] Determine whether the number of authorized resources is greater than the server resources. When the number of authorized resources is less than the server resources, it is considered that the current database system server resources exceed the resource limit, and the authorization status of the database system's license is updated to authorized-invalid, and the database-related functions are restricted according to the resource limit policy.

[0102] In this embodiment, Figure 3 As shown, the number of resources authorized in the license file (such as the number of CPU cores, memory size, etc.) is compared with the number of resources actually used by the current server regularly or in real time. When the number of authorized resources is less than the server resources, it is considered that the current database system server resources exceed the resource limit, and the authorization status of the database system license is updated to authorized-invalid, and the database-related functions are restricted according to the resource limit excess policy.

[0103] Furthermore, the over-limit handling strategy is alarm + resource restriction. The system issues a warning through the alarm module and restricts further resource expansion to ensure that it does not exceed the scope of license authorization; the over-limit handling strategy is only alarm. The system only issues a warning through the alarm module, but does not restrict further resource expansion. The system is allowed to continue to run but reminds the administrator to pay attention to resource over-limit issues; the over-limit handling strategy is no alarm and no restriction. The system does not issue any warnings and does not restrict further resource expansion. In this case, the system may continue to run, but there is a risk of violating the license agreement. According to the policies set in the license management system, the system automatically performs the corresponding operations. These operations are designed to protect the compliance of software authorization while minimizing the impact on business operations.

[0104] Specifically, the authorized fault is to detect that the binding server identifier (such as MAC address) in the license does not match the current environment. At this time, an alarm is reported through the alarm module. If the fault exceeds 30 days, the status is set to invalid.

[0105] The above steps ensure that the system can automatically monitor and manage resource usage, respond to resource overload issues in a timely manner, and take appropriate measures according to preset policies to maintain the legality and security of software use. At the same time, it also provides a notification mechanism for system administrators to handle resource overload issues so that they can take timely measures.

[0106] In one embodiment, the periodic verification of the license file further includes:

[0107] Check whether the server unique identification code in the license file matches the current environment;

[0108] When the unique identification code of the server does not match the current environment, the authorization status of the License of the database system is updated to authorized-failure, an alarm is issued and the start time of the failure is recorded.

[0109] In this embodiment, Figure 3 As shown in the figure, the system detects whether the unique identification code (such as MAC address) of the bound server in the license file matches the actual identification of the current server environment. If the server identification does not match, it indicates that the license file may have been mistakenly applied to the wrong server, or the server hardware has changed. Then, the authorization status of the license of the updated database system is "authorized-fault", indicating that there is a problem with the current authorization, and a warning is issued through the alarm module to notify the administrator of the abnormal authorization status. At the same time, the system records the time when the fault starts and starts to count the duration of the fault. If the fault is detected continuously for more than 30 days, the authorization status of the license of the updated database system is authorized-invalid. When the authorization code status is updated to "authorized-invalid", the system will limit the further expansion of resources to prevent the use of additional resources without resolving the authorization problem. The security and accuracy of the system's authorization management are ensured, and unauthorized use is prevented and compliance of software use is ensured by real-time monitoring and response to changes in the authorization status. At the same time, it also provides administrators with a fault detection and notification mechanism to solve authorization problems in a timely manner.

[0110] In one embodiment, the license management system specifically includes:

[0111] The license management system updates and stores the contract information, authorization code and server environment information;

[0112] Verifying the contract information, authorization code and server environment information;

[0113] After verification, a license file is generated according to the authorization code, the contract information and the server environment information;

[0114] The license file is renewed, replaced, expanded, queried, downloaded and offlined through the license management system.

[0115] In this embodiment, the license management system is specifically used to manage license files, including application, renewal, replacement of server identification information, expansion, query, download and offline functions of license files. One license management system can manage license files of multiple distributed database systems.

[0116] Specifically include:

[0117] 1) Application

[0118] Input information: customer name, authorization code, applicant, application date, version function type, authorization quantity unit, authorization quantity, validity start date, validity end date, full amount processing strategy, expiration processing strategy, and unique ID of the management module server.

[0119] Verification: Verify whether the authorization code exists, whether the customer name matches, and whether the validity period is earlier than the current time.

[0120] Generation and storage: After verification, the system generates a license file and stores the relevant information in the database.

[0121] 2) Renewal

[0122] New contract information: When a new contract is involved, you need to ensure that the version type and resource quantity unit of the new contract are consistent with the original contract, and fill in the new validity period.

[0123] Verification and update: The system verifies whether the version type and resource quantity unit of the new contract are consistent with the original contract, and whether the new validity period is valid. If the verification passes, the system takes the old license offline and activates the new license.

[0124] 3) Replace the server identification information

[0125] File identification code: Find the identification code of the license file to be replaced.

[0126] Information consistency: Ensure that the version type, resource quantity unit, resource quantity, and expiration date of the new license are consistent with those of the old license.

[0127] Update Server ID: Enter the unique identification information of the new server and verify successfully.

[0128] Deactivation and activation: After verification succeeds, the old license is deactivated and the new license is activated.

[0129] 4) Capacity Expansion

[0130] File identification code: Find the identification code of the license file to be expanded.

[0131] Information consistency: Ensure that the version type, resource quantity unit, expiration date, and server identification information of the new license are consistent with those of the old license.

[0132] Resource quantity update: Enter the new resource quantity and verify successfully.

[0133] Deactivation and activation: After verification succeeds, the old license is deactivated and the new license is activated.

[0134] 5) Query

[0135] Supported fields: The system supports querying by authorization code, customer name, file ID, version type and other fields.

[0136] 6) Download

[0137] Download support: Each license file can be downloaded.

[0138] 7) Offline

[0139] Status modification: Change the status of the license file to offline.

[0140] Record information: records the time and reason when the license file expires, usually "manual offline".

[0141] The license management system provides comprehensive license lifecycle management, ensuring the correct application, use, update and decommissioning of license files, thereby maintaining the compliance and effectiveness of software authorization. Through this system, administrators can effectively manage and monitor the authorization status of distributed database systems.

[0142] A license management device for a distributed database, the device comprising:

[0143] The information acquisition module 11 is used to acquire the customer's demand information and generate contract information according to the demand information;

[0144] An information entry module 12, used to enter the contract information into a license management system, and the license management system generates a unique authorization code according to the contract information;

[0145] A file generation module 13, used to generate a license file according to the authorization code, the contract information and the server environment information;

[0146] The file verification module 14 is used to perform real-time verification and periodic verification on the license file when it is imported;

[0147] The file deployment module 15 is used to deploy a distributed database according to the license file after the license file is verified.

[0148] In one embodiment, the file generation module 13 includes:

[0149] An environment information collection unit is used to obtain server environment information required for deploying a distributed database through a collection tool;

[0150] An identification code unit, used to generate a unique server identification code according to the server environment information;

[0151] The license file unit is used to fill the authorization code, the contract information and the server unique identification code into the license file template to generate a license file.

[0152] In one embodiment, the file verification module 14 includes:

[0153] An encryption verification unit, used to perform encryption verification on the license file, and when the encryption verification of the license file passes, parse the license file to extract authorization information;

[0154] An identification code unit, used to determine the authorization status of the license in the distributed database according to the authorization information, and when the license in the distributed database is in the authorized state, check whether the unique identification code of the license file is repeated with the unique identification code of the license already existing in the current system;

[0155] A validity period unit, used to verify whether the validity period in the authorization information has expired when the unique identification code of the license file does not overlap with the unique identification code of the existing license;

[0156] A resource quantity unit, used to verify whether the authorized resource quantity in the authorization information is greater than the total current system resources when the validity period has not expired;

[0157] A server identification unit, used to verify whether the server identification bound in the authorization information matches the current system server when the number of authorized resources meets the requirement;

[0158] The authorization status updating unit is used to update the new license information to the cache by the license management module in the distributed database when the above-mentioned verifications all meet the requirements, and to update the authorization status of the current database system.

[0159] In one embodiment, the file verification module 14 includes:

[0160] A period verification unit, used to compare whether the validity period of the license file is less than a system time threshold;

[0161] The expiration processing unit is used to consider that the License file time has expired when the validity period is less than the current system time, update the authorization status of the database system License to authorized-invalid, and limit database related functions according to the expiration processing strategy.

[0162] In one embodiment, the file verification module 14 further includes:

[0163] A resource verification unit, used to compare the authorized resource quantity of the license file with the server resources;

[0164] The resource overlimit unit is used to determine whether the number of authorized resources is greater than the server resources. When the number of authorized resources is less than the server resources, it is considered that the current database system server resources exceed the resource limit, and the authorization status of the database system license is updated to authorized-invalid, and the database-related functions are restricted according to the resource overlimit policy.

[0165] In one embodiment, the file verification module 14 further includes:

[0166] An identification code verification unit, used to detect whether the server unique identification code of the license file matches the current environment;

[0167] The alarm unit is used to update the authorization status of the license of the database system to authorized-failure, issue an alarm and record the start time of the failure when the unique identification code of the server does not match the current environment.

[0168] In one embodiment, the license management system specifically includes:

[0169] An information storage module, used for the License management system to update and store the contract information, authorization code and server environment information;

[0170] A file verification module, used to verify the contract information, authorization code and server environment information;

[0171] A file generation module, used to generate a license file according to the authorization code, the contract information and the server environment information after verification;

[0172] The management module is used to renew, replace, expand, query, download and log off the license file through the license management system.

[0173] Another embodiment of the present invention provides a license management system for a distributed database, the system comprising at least one processor; and

[0174] a memory communicatively connected to the at least one processor; wherein,

[0175] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the license management method for the distributed database.

[0176] One or more processors 110 and memory 120, Figure 5 A processor 110 is used as an example for description. The processor 110 and the memory 120 may be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0177] The processor 110 is used to complete various control logics of the control system 10. It can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISC Machine) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination of these components. In addition, the processor 110 can also be any traditional processor, microprocessor or state machine. The processor 110 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP and / or any other such configuration.

[0178] The memory 120, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions corresponding to the license management method for a distributed database in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the control system 10 by running the non-volatile software programs, instructions and units stored in the memory 120, that is, implements the license management method for a distributed database in the above method embodiment.

[0179] The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required by at least one function; the data storage area may store data created according to the use of the control system 10, etc. In addition, the memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 120 may optionally include a memory remotely arranged relative to the processor 110, and these remote memories may be connected to the control system 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0180] One or more units are stored in the memory 120, and when executed by one or more processors 110, the license management method of the distributed database in any of the above method embodiments is executed, for example, the above described Figure 1 The method comprises steps S100 to S500.

[0181] An embodiment of the present invention provides a non-volatile computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors, for example, to execute the above-described Figure 1 The method comprises steps S100 to S500.

[0182] As an example, non-volatile storage media can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) as external cache memory. By way of illustration and not limitation, RAM can be obtained in many forms such as synchronous RAM (SRAM), dynamic RAM, (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The disclosed memory components or memories of the operating environment described herein are intended to include one or more of these and / or any other suitable types of memory.

[0183] In summary, the present invention discloses a method, device, system and medium for managing a distributed database license, including: obtaining customer demand information, generating contract information according to the demand information; entering the contract information into a license management system, and the license management system generating a unique authorization code according to the contract information; generating a license file according to the authorization code, the contract information and the server environment information; performing real-time import verification and periodic verification on the license file; after the license file verification passes, deploying a distributed database according to the license file. The present invention generates a license file by acquiring contract information, authorization code and server environment collection and performs real-time verification, thereby ensuring the security, legality and flexibility of authorization.

[0184] Of course, those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware (such as a processor, a controller, etc.) through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium, and the computer program can include the processes of the above-mentioned method embodiments when executed. The storage medium can be a memory, a disk, a floppy disk, a flash memory, an optical storage device, etc.

[0185] It should be understood that the application of the present invention is not limited to the above examples. For ordinary technicians in this field, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A license management method for a distributed database, characterized in that: The steps include: Obtaining customer demand information, and generating contract information based on the demand information; Entering the contract information into a license management system, and the license management system generating a unique authorization code according to the contract information; Generate a License file according to the authorization code, the contract information and the server environment information; Performing import real-time verification and periodic verification on the license file; After the license file is verified, the distributed database is deployed according to the license file.

2. The license management method for a distributed database according to claim 1, characterized in that: The generating a license file according to the authorization code, the contract information and the server environment information includes: Use collection tools to obtain server environment information required for deploying distributed databases; Generate a unique server identification code according to the server environment information; Fill the authorization code, the contract information and the server unique identification code into the license file template to generate a license file.

3. The license management method for a distributed database according to claim 1, characterized in that: The real-time import verification of the license file includes: Performing encryption verification on the License file, and when the encryption verification of the License file passes, parsing the License file to extract authorization information; Determine the authorization status of the license in the distributed database according to the authorization information, and when the license in the distributed database is in the authorized state, check whether the unique identification code of the license file is repeated with the unique identification code of the license already existing in the current system; When the unique identification code of the license file does not overlap with the unique identification code of the existing license, verify whether the validity period in the authorization information has expired; When the validity period has not expired, verifying whether the quantity of authorized resources in the authorization information is greater than the total amount of current system resources; When the number of authorized resources meets the requirement, verify whether the server identifier bound in the authorization information matches the current system server; When the above-mentioned verifications all meet the requirements, the license management module in the distributed database updates the new license information to the cache and updates the authorization status of the current database system.

4. The license management method for a distributed database according to claim 1, characterized in that: The periodic verification of the license file includes: Compare whether the validity period of the license file is less than the current system time; When the validity period is less than the current system time, the License file is considered to have expired, the authorization status of the database system's License is updated to authorized-invalid, and database-related functions are restricted according to the expiration processing policy.

5. The license management method for a distributed database according to claim 1, characterized in that: The periodic verification of the license file further includes: Compare the authorized resource quantity of the license file with the server resources; Determine whether the number of authorized resources is greater than the server resources. When the number of authorized resources is less than the server resources, it is considered that the current database system server resources exceed the resource limit, and the authorization status of the database system's license is updated to authorized-invalid, and the database-related functions are restricted according to the resource limit policy.

6. The license management method for a distributed database according to claim 1, characterized in that: The periodic verification of the license file further includes: Check whether the server unique identification code in the license file matches the current environment; When the unique identification code of the server does not match the current environment, the authorization status of the License of the database system is updated to authorized-failure, an alarm is issued and the start time of the failure is recorded.

7. The license management method for a distributed database according to claim 1, characterized in that: The license management system specifically includes: The license management system updates and stores the contract information, authorization code and server environment information; Verifying the contract information, authorization code and server environment information; After verification, a license file is generated according to the authorization code, the contract information and the server environment information; The license file is renewed, replaced, expanded, queried, downloaded and offlined through the license management system.

8. A license management device for a distributed database, characterized in that: The device comprises: An information acquisition module is used to acquire customer demand information and generate contract information based on the demand information; An information entry module, used to enter the contract information into a license management system, and the license management system generates a unique authorization code according to the contract information; A file generation module, used to generate a license file according to the authorization code, the contract information and the server environment information; A file verification module, used to perform real-time verification and periodic verification on the license file when it is imported; The file deployment module is used to deploy a distributed database according to the license file after the license file is verified.

9. A distributed database license management system, characterized in that: The system includes at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the license management method for a distributed database according to any one of claims 1 to 7.

10. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores computer-executable instructions, which, when executed by one or more processors, enable the one or more processors to execute the license management method for a distributed database according to any one of claims 1 to 7.

Images