Configuration software authorization implementation method and device

Abstract

According to the configuration software authorization implementation method and device, on the premise that software authorization is efficient and convenient, a time tamper-proof mechanism is added, and the safety and stability of software are improved. The method comprises the following steps: acquiring a first machine code, current time and final authorization time of a local computer; analyzing the authorization key or the authorization file to obtain a second machine code and authorization end time; comparing the first machine code with the second machine code to judge whether the codes are the same; if the first machine code is the same as the second machine code, comparing the last time of authorization, the end time of authorization and the current time, and if the last time of authorization is less than the current time and the current time is less than the end time of authorization, indicating that authorization succeeds; if any condition is not met, the authorization is considered to be invalid or expired, and the system forbids to continue to use related services or functions; therefore, the security and the stability of software authorization are improved.

Description

Technical Field

[0001] The present application relates to the field of configuration software, and in particular to an implementation method and device for configuration software authorization. Background Art

[0002] At present, software authorization methods can be mainly divided into two categories: hardware authorization and software authorization. Hardware authorization is to implement software authorization management through external hardware devices, such as dongles, USB keys, etc. When using the software, users need to insert the dongle into the computer or other devices to confirm the legitimacy of the software authorization through hardware encryption verification. Although hardware authorization can effectively prevent illegal copying and piracy of software and increase the difficulty of cracking, it also has some shortcomings. First, the hardware dongle needs to be physically connected to the device, which brings certain inconveniences to users, especially when the device needs to be frequently moved or the software needs to be used remotely. The plugging and unplugging of the dongle becomes an additional operation, affecting the smoothness of use. Secondly, the hardware device itself may be damaged or lost, resulting in the inability to verify the authorization, which brings unnecessary trouble and costs to users and enterprises.

[0003] Compared with hardware authorization, software authorization embeds authorization information into the software itself and verifies the legitimacy of the user through the key or digital certificate in the program. Software authorization is usually more convenient and flexible. Users do not need additional hardware devices and can remotely verify or dynamically update authorization information through the network, making software management and maintenance more efficient. However, software authorization also faces certain security risks, mainly reflected in the protection of authorization information. If the authorization information is cracked or leaked, the security of the software will be greatly reduced, and it may even be illegally copied and disseminated. Therefore, in order to enhance the security of software authorization, multiple protection measures need to be taken for the authorization information, such as encrypted storage, digital signature, dynamic key update, etc., to reduce the risk of being cracked.

[0004] Therefore, how to maintain the convenience and speed of software authorization while improving the security of software authorization is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present invention provides a configuration software authorization implementation method and device, which, based on the premise of efficient and convenient software authorization, adds a time anti-tampering mechanism to improve the security and stability of the software.

[0006] In a first aspect, the present disclosure provides a configuration software authorization implementation method, comprising: Step S100, obtaining the first machine code, current time and last authorization time of the local computer; Step S200, parsing the authorization key or authorization file to obtain the second machine code and the authorization end time; Step S300, comparing the first machine code and the second machine code to determine whether they are the same; Step S400, if the first machine code is the same as the second machine code, compare the last authorization time, the authorization end time and the current time. If the last authorization time is less than the current time, and the current time is less than the authorization end time, the authorization is successful.

[0007] Optionally, in step S100, if the first machine code of the local computer fails to be obtained, it means that the device has not generated a machine code, and a machine code generation module can be used to create the first machine code, and then the first machine code is obtained again after the creation, and then step S200 is performed after the acquisition.

[0008] Optionally, in step S300, if the first machine code is different from the second machine code, it means that the authorization key or authorization file is not applicable to the current machine, and the user is prompted that the machine code is wrong and the authorization fails.

[0009] Optionally, if the authorization end time obtained in step S400 is PERMANENT, it is regarded as a permanent authorization. At this time, if the last authorization time is less than the current time, the authorization is successful; if the last authorization time is greater than the current time or the authorization end time, it is prompted that the local storage information has been tampered with and the authorization status cannot be determined; if the current time is greater than the authorization end time, it is prompted that the authorization has expired and the authorization has failed.

[0010] Optionally, after step S400, the value of the current time is assigned to the last authorized time, and the updated last authorized time is written into the local device cache.

[0011] In a second aspect, the present disclosure provides a configuration software authorization implementation device, the device is used to execute the configuration software authorization implementation method described in each embodiment, the device comprising: A local information acquisition module, used to obtain the first machine code, current time and last authorization time of the local computer; An authorization information parsing module is used to parse the authorization key or authorization file to obtain the second machine code and the authorization end time; A machine code comparison module, used to compare the first machine code with the second machine code to determine whether they are the same; The authorization time comparison module, if the first machine code and the second machine code are the same, is used to compare the last authorization time, the authorization end time and the current time. If the last authorization time is less than the current time, and the current time is less than the authorization end time, the authorization is successful; if the obtained authorization end time is PERMANENT, it is regarded as a permanent authorization. At this time, if the last authorization time is less than the current time, the authorization is successful; if the last authorization time is greater than the current time or the authorization end time, it is prompted that the local storage information has been tampered with and the authorization status cannot be determined; if the current time is greater than the authorization end time, it is prompted that the authorization has expired and the authorization fails.

[0012] A machine code generation module, which is used to create the first machine code if the acquisition of the first machine code of the local computer fails, indicating that the device has not generated a machine code; The authorization last time update module is used to assign the value of the current time to the authorization last time after the authorization is successful, and write the updated authorization last time into the local device cache.

[0013] In a third aspect, the present disclosure provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor; Memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method in the present disclosure.

[0014] In a fourth aspect, the present disclosure provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method of the present disclosure.

[0015] The beneficial effects of the present disclosure are that, compared with the prior art, the present disclosure has the following advantages: 1) This disclosure introduces a time matching mechanism under the premise of comparing whether the second machine code in the key or authorization file matches the local first machine code, which not only enhances security but also realizes dynamic authorization management based on time. At the same time, it also solves the authorization requirements in some special scenarios, such as scenarios where hard authorization is not allowed, and scenarios where there are strict requirements on the timeliness of authorization and only allow single short-term authorization.

[0016] 2) Localize and store the last authorization time, and store the authorization end time in the authorization key or authorization file. This can effectively prevent a third party from tampering with the time of the local device to achieve illegal authorization.

[0017] 3) Decryption can be achieved through both authorization key and authorization file, which is suitable for different demand scenarios. For scenarios where the authorization key cannot be leaked, decryption can be performed by transmitting the authorization file in a black box; for scenarios where the file cannot be transmitted, decryption can be performed by informing the key.

[0018] In summary, the present disclosure provides a configuration software authorization implementation method and device, which not only improves the security of software decryption, but also realizes the time-based dynamic management of authorization and the function of preventing local tampering of information to achieve illegal authorization. At the same time, it comprehensively and meticulously considers various possible special application scenarios, and has a wide range of application value in special industries such as those with strict confidentiality requirements, limited file transfer channels, and those that do not allow the use of hardware authorization. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0020] Figure 1 A flowchart of a configuration software authorization implementation method provided by an embodiment of the present disclosure; Figure 2 A schematic diagram of the authorization time comparison process provided by an embodiment of the present disclosure; Figure 3 A schematic diagram of the structure of a configuration software authorization implementation device provided in an embodiment of the present disclosure.

[0021] The above drawings show clear embodiments of the present disclosure, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present disclosure in any way, but to illustrate the concepts of the present disclosure to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0022] The present disclosure is further described below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present disclosure, and cannot be used to limit the protection scope of the present disclosure.

[0023] Figure 1 It is a flowchart of a configuration software authorization implementation method provided according to an embodiment of the present disclosure.

[0024] like Figure 1 As shown, a configuration software authorization implementation method of this embodiment may include: Step S100, obtaining the first machine code, current time and last authorization time of the local computer; In an optional implementation, the step S100 of obtaining the first machine code, current time and last authorization time of the local computer includes: Read the stored machine code from the local computer. If the reading is successful, it means that the computer has generated a GUID and it has been encrypted and stored in the device. At this time, the encrypted string needs to be decrypted to restore the original GUID machine code.

[0025] To read the current time from the local computer, you can get it by getting the timestamp. A timestamp is the time since 00:00:00 UTC (Coordinated Universal Time, or Unix epoch) on January 1, 1970, expressed in seconds or milliseconds. A timestamp is a standard way to record the time when an event occurs in a computer system, and is commonly used in logs, databases, file systems, and various applications. In short, a timestamp, that is, a number, can be used to accurately represent the current time. This method can be used to directly compare the numerical values ​​to facilitate subsequent comparisons of the current time, the last authorization time, and the authorization end time.

[0026] After each successful authorization decryption, the last authorization time will be updated and written into the encrypted device cache for comparison during the next authorization.

[0027] Furthermore, if the first machine code of the local computer fails to be obtained, it means that the device has not generated a unique machine code, and a machine code generation module may be used to create the first machine code, and then the first machine code may be obtained again after the creation, and then step S200 may be performed after the acquisition.

[0028] Step S200, parsing the authorization key or authorization file to obtain the second machine code and the authorization end time; In an optional implementation, step S200, parsing the authorization key or authorization file to obtain the second machine code and the authorization end time, includes: The process of parsing the authorization key or authorization file is mainly to extract important information related to the authorization. In this process, the authorization key or file must first be decoded or parsed to obtain the encrypted data or structured content contained therein. By parsing these data, a second machine code can be obtained, which is usually a unique identifier bound to a specific hardware or device and is used to confirm the applicable machine for authorization. In addition, the authorization end time, that is, the validity period or expiration time of the authorization, can also be extracted. This time indicates the continued validity of the authorization, helps determine whether the authorization has expired, and whether renewal or re-authorization is required. In one embodiment, the authorization end time can also be recorded in the form of a timestamp.

[0029] Step S300, comparing the first machine code and the second machine code to determine whether they are the same; In an optional implementation, step S300, comparing the first machine code with the second machine code to determine whether they are the same, includes: When performing authorization verification, you first need to obtain the first machine code of the local device. This machine code is usually a unique identifier based on the device hardware and reflects the specific hardware information of the current device. Next, by parsing the authorization key or authorization file, extract the second machine code contained therein. This machine code is usually bound to a specific device by the authorization system when the authorization is generated. Next, you need to compare the two machine codes: one is obtained directly from the local device, and the other is parsed from the authorization file. By comparing the two machine codes, you can verify whether the authorization is correctly bound to the current device. If the two machine codes are the same, it means that the authorization is valid and correctly matches the local device; if they are different, it may mean that the authorization file is not applicable to the current device, or the authorization information has been tampered with, and you need to further check the authorization status or reapply for authorization.

[0030] Step S400, if the first machine code is the same as the second machine code, compare the last authorization time, the authorization end time and the current time. If the last authorization time is less than the current time, and the current time is less than the authorization end time, the authorization is successful. In an optional implementation, in step S400, if the first machine code is the same as the second machine code, the authorization last time, the authorization end time and the current time are compared. If the authorization last time is less than the current time and the current time is less than the authorization end time, the authorization is successful, including: The last authorization time represents the most recent authorization time, so it must be something that happened before, and obviously needs to be less than the current time; otherwise, the local last authorization time or the local current time must have been manually tampered with. It is easy to understand that if the current time is greater than the authorization end time, it means that the authorization has expired. Through each authorization, the last authorization time in the authorization key or authorization file can be dynamically adjusted to achieve dynamic management of authorization permissions over time.

[0031] In one implementation, the last authorization time, current time, and authorization end time are all stored in the form of timestamps, and the comparison is performed by directly comparing the timestamp values. This can save space for storing three variables and also achieve high-speed and fast comparison. An example is as follows: For example, assume that the variable name for the last authorization time is LastT, the end authorization time is EndT, and the current time is CurrentT. If the read timestamps are LastT = 5700000100 (equivalent to October 27, 2022, 08:48:20 UTC), CurrentT = 5710145905 (equivalent to April 16, 2024, 05:18:25 UTC), and EndT = 5810140000 (equivalent to October 22, 2029, 15:46:40 UTC); then by directly comparing the values, it can be obtained that LastT < CurrentT < EndT, indicating that the last authorization time is less than the current time, and the current time is less than the end authorization time. At this time, it can be determined that the authorization is successful.

[0032] In one implementation, after the step S400, assigning the value of the current time to the last authorization time and writing the updated last authorization time into the local device cache includes: When performing authorization management, the value of the current system time can be assigned to the last authorization time to mark the validity period of the authorization or the updated time point. First, by obtaining the system time of the current device, it can be ensured that the last time of the authorization record is accurate and timely. Then, assigning the current time to the last authorization time field indicates that the authorization has been updated or confirmed. Finally, to ensure the persistence and accessibility of the data, the updated last authorization time needs to be written into the cache of the local device. In this way, not only can the validity of the authorization be tracked in real time, but also when the device is restarted or in subsequent operations, it can be ensured that the last authorization time can be correctly loaded and used, avoiding authorization problems caused by inconsistent time information.

[0033] Figure 2 It is a schematic diagram of an authorization time comparison process provided according to an embodiment of the present disclosure.

[0034] As Figure 2 shown, an authorization time comparison process of this embodiment, for some steps in this flowchart, may specifically include: Step S410, comparing whether the last authorization time is less than the current time; Common sense says that if the last time of authorization is greater than the current time, this is obviously impossible. Because the last time of authorization represents the end time of the last authorization, it should always be less than or equal to the current time. If it is found that the last time of authorization is greater than the current time, then it is obvious that there is an abnormality in the time information in the system. There may be two explanations for this situation: First, the end time of authorization has been tampered with, that is, someone deliberately modified the validity period of authorization and extended the last time of authorization, causing it to exceed the current time. Second, the current time has been tampered with, that is, the system time of the local device has been artificially adjusted, causing the system time to be earlier than the last time of authorization, which makes the authorization information appear to be valid for an extended period of time. In either case, it may be the result of malicious tampering, which seriously affects the correctness of authorization and the security of the system. Therefore, when encountering a situation where the last time of authorization is greater than the current time, it is necessary to verify immediately to check whether there is a risk of time information tampering, and take necessary measures to restore the correct time of the system or re-perform authorization verification to prevent security risks.

[0035] S420, determining whether the authorization end time is PERMANENT; Determine whether the authorization end time is PERMANENT. If so, the authorization is successful and the authorization period is permanent. Determining whether the authorization end time is PERMANENT is a special mark verification of the authorization validity period. Usually, the authorization end time is a specific date or time, indicating the expiration or invalidation time of the authorization. However, when the authorization end time is set to PERMANENT, it means that the authorization has no fixed expiration date and the authorization will remain valid until it is manually revoked or terminated.

[0036] S430, determining whether the current time is less than the authorization end time; Determining whether the current time is less than the authorization end time is actually verifying the relationship between the current time and the authorization validity period. Specifically, the current time needs to be compared with the authorization end time to confirm whether the current time is still within the authorization validity period. If the current time is less than the authorization end time, it means that the authorization is still valid and the user or device can continue to enjoy the functions or services provided by the authorization; conversely, if the current time is greater than the authorization end time, it means that the authorization has expired and the user or device's permissions may be restricted or terminated.

[0037] Figure 3 1 is a schematic diagram of the structure of a configuration software authorization implementation device provided by an embodiment of the present disclosure. The system is used to run the configuration software authorization implementation method in the above embodiments. Figure 3 , the device may include: The local information acquisition module 1001 is used to obtain the first machine code, current time and last authorization time of the local computer; including: The core function of the local information acquisition module is to automatically collect and extract key data from the local computer system, including the first machine code, current time, and last authorized time. The module first obtains the computer's unique identifier, the first machine code, through hardware identification technology. It is usually generated based on the computer's hardware characteristics (such as motherboard, CPU, etc.) to ensure the uniqueness of each computer in the system. Secondly, the module obtains the current time from the local operating system. This timestamp is used to verify the validity of the authorization and serves as a reference for subsequent operations. Finally, the last authorized time refers to the time of the last authorized operation saved in the system, which is used to determine whether the current authorization is still valid or needs to be updated. If the last authorized time is later than the current time, it may indicate that the authorization information has been tampered with or the system time is abnormal. By centrally collecting this information, the local information acquisition module not only provides basic data for authorization validity verification, but also plays a key role in authorization management, device security monitoring, etc., ensuring that the system can operate as expected and trigger necessary operations before the authorization expires.

[0038] The authorization information parsing module 1002 is used to parse the authorization key or authorization file to obtain the second machine code and the authorization end time, including: The main function of the authorization information parsing module is to parse the authorization key or authorization file and extract key information, especially the second machine code and the authorization end time. The module first receives the encrypted or formatted authorization key or file, decrypts or parses it through the parsing algorithm to ensure that the data in the file can be read correctly. In the parsed information, the second machine code is usually a unique identifier bound to the authorized device, which is compared with the first machine code of the local device to ensure that the authorization information has not been tampered with or incorrectly applied to other devices. The authorization end time indicates the validity period of the authorization, which is usually a specific date or timestamp indicating the expiration time of the authorization. By parsing this data, the authorization information parsing module can help the system determine whether the authorization is still valid, whether it matches the local device, and whether it needs to be renewed or re-authorized. This module is a core component of the authorization management process. It ensures the security, accuracy and legality of the authorization information, thereby effectively preventing illegal use and authorization abuse.

[0039] The machine code comparison module 1003 is used to compare the first machine code with the second machine code to determine whether they are the same; including: The main function of the machine code comparison module is to compare the first machine code with the second machine code to determine whether they are the same. When performing authorization verification, you first need to obtain the first machine code of the local device, which is usually a unique identifier based on the device hardware and reflects the specific hardware information of the current device. Then, by parsing the authorization key or authorization file, extract the second machine code contained therein, which is usually bound to a specific device by the authorization system when the authorization is generated. Next, you need to compare the two machine codes: one is obtained directly from the local device, and the other is parsed from the authorization file. By comparing the two machine codes, you can verify whether the authorization is correctly bound to the current device. If the two machine codes are the same, it means that the authorization is valid and correctly matches the local device; if they are different, it may mean that the authorization file is not applicable to the current device, or the authorization information has been tampered with, and you need to further check the authorization status or re-apply for authorization.

[0040] The authorization time comparison module 1004 is used to compare the last authorization time, the authorization end time and the current time if the first machine code and the second machine code are the same. If the last authorization time is less than the current time and the current time is less than the authorization end time, the authorization is successful; including: The main function of the authorization time comparison module is to compare the last authorization time, the end authorization time and the current time when confirming that the first machine code is the same as the second machine code, so as to determine whether the authorization is successful. The module first confirms whether the authorization information matches the current device through the machine code comparison module. Once the machine codes of the two are consistent, the system will continue to verify the time. The authorization time comparison module then obtains the current time and compares it with the last authorization time and the end authorization time. If the last authorization time is less than the current time, it means that the authorization information is valid and has been properly updated or confirmed; at the same time, the current time must be less than the end authorization time to ensure that the current time is still within the validity period of the authorization. Only when both conditions are met, the authorization is considered valid and the authorization process is judged to be successful. If any condition is not met, such as the current time exceeds the end authorization time, the authorization will be considered invalid or expired, and the system will prohibit the continued use of related services or functions. The authorization time comparison module ensures the compliance and security of the authorization process through accurate time verification, and avoids illegal access or use caused by time errors or authorization failures.

[0041] The authorization last time update module 1006 is used to assign the current time value to the authorization last time and write the updated authorization last time into the local device cache. It includes: The main function of the authorization last time update module is to assign the current time to the authorization last time and write the updated authorization information into the cache of the local device, so as to ensure the timeliness and accuracy of the authorization record. The module first obtains the current time of the system. This timestamp indicates the exact moment when the operation is performed, which is usually obtained through the clock of the local computer. Next, the module assigns the value of the current time to the authorization last time to mark the last update time of the authorization operation or the authorization renewal time. This process can not only reflect whether the authorization has been updated or activated, but also ensure that the authorization information is consistent with the actual operation time to avoid the situation where the authorization is invalid or not updated in time. Subsequently, the updated authorization last time will be written into the cache of the local device, which is usually stored in the local storage of the device (such as files, databases or memory cache) to ensure that the system can correctly read and use the latest authorization information even after the device is restarted or powered off. Through the authorization last time update module, the system can track the changes and validity period of the authorization in real time, ensure the flexibility and accuracy of authorization management, and avoid security risks caused by inconsistent or delayed authorization time.

[0042] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, which may include: a processor, a communications interface, a memory, and a communication bus, wherein the processor, the communications interface, and the memory communicate with each other through the communication bus. The processor may call logic instructions in the memory to execute a configuration-based software authorization implementation method.

[0043] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on such an understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0044] On the other hand, the present disclosure further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to execute the configuration-based software authorization implementation method provided by the above methods.

[0045] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0046] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0047] It should be understood that the above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A configuration software authorization implementation method, comprising: Step S100, obtaining the first machine code, current time and last authorization time of the local computer; Step S200, parsing the authorization key or authorization file to obtain the second machine code and the authorization end time; Step S300, comparing the first machine code and the second machine code to determine whether they are the same; Step S400, if the first machine code is the same as the second machine code, compare the last authorization time, the authorization end time and the current time. If the last authorization time is less than the current time, and the current time is less than the authorization end time, the authorization is successful.

2. A configuration software authorization implementation method according to claim 1, characterized in that: In the step S100, if the acquisition of the first machine code of the local computer fails, the first machine code is created, and the first machine code is acquired again after the creation.

3. A configuration software authorization implementation method according to claim 2, characterized in that: In step S300, if the first machine code is different from the second machine code, the user is prompted that the machine code is wrong and the authorization fails.

4. A configuration software authorization implementation method according to claim 1, characterized in that: In step S400, if the obtained authorization end time is PERMANENT, the authorization is successful only if the authorization last time is less than the current time; if the authorization last time is greater than the current time or the authorization end time, it is prompted that the local storage information has been tampered with and the authorization status cannot be determined; If the current time is greater than the authorization end time, it will prompt that the authorization has expired and the authorization has failed.

5. A configuration software authorization implementation method according to claim 4, characterized in that: After step S400, the method further includes: The value of the current time is assigned to the last authorized time, and the updated last authorized time is written to the local device cache.

6. A configuration software authorization implementation device, comprising: A local information acquisition module, used to obtain the first machine code, current time and last authorization time of the local computer; An authorization information parsing module is used to parse the authorization key or authorization file to obtain the second machine code and the authorization end time; A machine code comparison module, used to compare the first machine code with the second machine code to determine whether they are the same; The authorization time comparison module is used to compare the last authorization time, the authorization end time and the current time if the first machine code is the same as the second machine code. If the last authorization time is less than the current time and the current time is less than the authorization end time, the authorization is successful.

7. A configuration software authorization implementation device according to claim 6, characterized in that: Also includes: The machine code generation module is used to create the first machine code if the acquisition of the first machine code of the local computer fails.

8. A configuration software authorization implementation device according to claim 6, characterized in that: The authorization time comparison module is also used for: If the obtained authorization end time is PERMANENT, it is considered as permanent authorization. At this time, if the authorization end time is less than the current time, the authorization is successful; if the authorization end time is greater than the current time or the authorization end time, it will prompt that the local storage information has been tampered with and the authorization status cannot be determined; If the current time is greater than the authorization end time, it will prompt that the authorization has expired and the authorization has failed.

9. A configuration software authorization implementation device according to claim 8, characterized in that: Also includes: The authorization last time update module is used to assign the value of the current time to the authorization last time after the authorization is successful, and write the updated authorization last time into the local device cache.

10. An electronic device, comprising a processor and a memory, wherein the memory stores at least one instruction and at least one program, and the at least one instruction and the at least one program are loaded and executed by the processor to implement the configuration software authorization implementation method as described in any one of claims 1 to 5.

Images