Software authorization method, electronic equipment and storage medium

Abstract

The invention relates to a software authorization method, electronic equipment and a storage medium, and relates to the technical field of computers, the method comprises the following steps: obtaining an authorization file, the authorization file comprising first authorization request data corresponding to to-be-authorized software and a first signature value obtained by signing the first authorization request data; verifying the first signature value, and analyzing the first authorization request data to obtain first field information and second field information under the condition that the verification of the first signature value is passed; comparing the first field information with own identification information, and comparing the second field information with the current time; and under the condition that the first field information is consistent with the own identification information and the second field information is greater than or equal to the current time, authorizing the to-be-authorized software. In this way, the security of software authorization can be improved, and the requirements of commercial software or enterprise-level applications needing high security guarantee can be better met.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a software authorization method, an electronic device, and a storage medium. Background Art

[0002] With the booming development of the computer software industry, the authorization management of software products has become a crucial link. However, most traditional software authorization methods rely on simple serial numbers for authorization management. Although the control of software usage rights has been achieved to a certain extent, the serial number can be easily cracked by reverse engineering, resulting in unauthorized users being able to use the software, which leads to insufficient security. For commercial software or enterprise-level applications that require high security, traditional software authorization methods are obviously difficult to meet their needs. Summary of the invention

[0003] The present application provides a software authorization method, an electronic device and a storage medium to solve the problem that most traditional software authorization methods rely on simple serial numbers for authorization management and have insufficient security.

[0004] In a first aspect, an embodiment of the present application provides a software authorization method, which is applied to a client, and the method includes:

[0005] Obtaining an authorization file, wherein the authorization file includes first authorization request data corresponding to the software to be authorized and a first signature value obtained by signing the first authorization request data;

[0006] Verify the first signature value, and if the first signature value is verified, parse the first authorization request data to obtain first field information and second field information, wherein the first field information is used to represent the identification information of the client requesting authorization, and the second field information is used to represent the expiration time of the authorization validity period;

[0007] Compare the first field information with its own identification information, and compare the second field information with the current time;

[0008] When the first field information is consistent with its own identification information and the second field information is greater than or equal to the current time, the software to be authorized is authorized.

[0009] Optionally, obtaining the authorization file includes:

[0010] When a network connection is established between the user and the management center, receiving second authorization request data issued by the management center, and signing the second authorization request data to obtain a second signature value, wherein the second authorization request data includes the first field information and the third field information, and the third field information is used to represent the expected number of authorization days;

[0011] splicing the second authorization request data and the second signature value into an authorization request string, and sending the authorization request string to the management center, so that the management center can verify the second signature value in the authorization request string, and after the verification is passed, signing the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data;

[0012] Receive the authorization file returned by the management center, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data, the management center transmits the first authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the management center online or offline.

[0013] Optionally, obtaining the authorization file includes:

[0014] In the case where a network connection is not established between the device and the management center, receiving second authorization request data input by a user, and generating a second authorization request file based on the second authorization request data, wherein the second authorization request file only includes the second authorization request data, the second authorization request data includes the first field information and the third field information, and the third field information is used to represent the expected number of authorization days;

[0015] The authorization file is obtained from the authorization system, wherein the authorization file is obtained by adjusting and signing the second authorization request data by the authorization system, the client transmits the second authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the client online or offline.

[0016] Optionally, after generating a second authorization request file based on the second authorization request data, the method further includes:

[0017] When a network connection is established between the authorization system and the authorization system, a first request is sent to the authorization system, wherein the first request carries the second authorization request file and the product serial number;

[0018] Receive a first response result or a second response result returned by the authorization system in response to the first request, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0019] In a second aspect, an embodiment of the present application further provides a software authorization method, which is applied to a management center, and the method includes:

[0020] In the case of establishing a network connection between itself and the client, second authorization request data is sent to the client, so that the client signs the second authorization request data to obtain a second signature value, and the second authorization request data and the second signature value are concatenated into an authorization request string, wherein the second authorization request data includes first field information and third field information, the first field information is used to represent the identification information of the client requesting authorization, and the third field information is used to represent the expected number of days for authorization;

[0021] Receiving the authorization request character string sent by the client;

[0022] Verify the second signature value in the authorization request character string, and after the verification passes, sign the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data;

[0023] The first authorization request file is delivered to the authorization system in an online or offline manner, and the authorization file is obtained from the authorization system in an online or offline manner, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and adjusting and signing the second authorization request data after the verification is passed;

[0024] The authorization file is returned to the client, so that the client can authorize the software to be authorized based on the authorization file.

[0025] Optionally, after signing the second authorization request data to obtain the first authorization request file, the method further includes:

[0026] When a network connection is established between the authorization system and the authorization system, a second request is sent to the authorization system, wherein the second request carries the first authorization request file and the product serial number;

[0027] Receive a third response result or a fourth response result returned by the authorization system in response to the second request, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0028] In a third aspect, an embodiment of the present application further provides a software authorization method, which is applied to an authorization system, and the method includes:

[0029] Obtaining a first authorization request file, verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data in the first authorization request file to obtain an authorization file, and delivering the authorization file to a management center online or offline, so that the management center can deliver the authorization file to a client, wherein the first authorization request file is generated by the management center, the third signature is obtained by the management center signing the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file; and / or,

[0030] Obtain a second authorization request file, adjust and sign the second authorization request data in the second authorization request file to obtain an authorization file, and deliver the authorization file to the client online or offline, wherein the second authorization request file is generated by the client, the second authorization request file includes only the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file.

[0031] Optionally, the method further comprises:

[0032] When establishing a network connection between the client and the client, receiving a first request sent by the client, wherein the first request carries the second authorization request file and the product serial number;

[0033] In response to the first request, generating a first response result or a second response result, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0034] The first response result or the second response result is returned to the client.

[0035] Optionally, the method further comprises:

[0036] When the network connection between the management center and the management center is established, receiving a second request sent by the management center, wherein the second request carries the first authorization request file and the product serial number;

[0037] In response to the second request, generating a third response result or a fourth response result, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0038] The third response result or the fourth response result is returned to the management center.

[0039] In a fourth aspect, an embodiment of the present application further provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0040] Memory, used to store computer programs;

[0041] The processor is used to implement the software authorization method described in the first aspect, or the software authorization method described in the second aspect, or the software authorization method described in the third aspect when executing the program stored in the memory.

[0042] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the software authorization method described in the first aspect is implemented, or the software authorization method described in the second aspect is implemented, or the software authorization method described in the third aspect is implemented.

[0043] The above-mentioned technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application, by obtaining an authorization file, wherein the authorization file includes first authorization request data corresponding to the software to be authorized and a first signature value obtained by signing the first authorization request data; verifying the first signature value, and if the first signature value is verified, parsing the first field information and the second field information from the first authorization request data to obtain first field information and second field information, wherein the first field information is used to represent the identification information of the client requesting authorization, and the second field information is used to represent the expiration time of the authorization validity period; comparing the first field information with its own identification information, and comparing the second field information with the current time; if the first field information is consistent with its own identification information, and the second field information is greater than or equal to the current time, authorizing the software to be authorized. Through the above method, the client can obtain the first authorization request data corresponding to the software to be authorized and the first signature value obtained by signing the first authorization request data, and then verify the first signature value and the first field information and the second field information in the first authorization request data to realize the authorization of the software to be authorized. Therefore, compared with the traditional method of relying on a simple serial number to authorize software, the software authorization method provided by the embodiment of the present application is more secure and can better meet the needs of commercial software or enterprise-level applications that require high security. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A flowchart of a software authorization method provided in an embodiment of the present application;

[0047] Figure 2 A flowchart of another software authorization method provided in an embodiment of the present application;

[0048] Figure 3 A flowchart of another software authorization method provided in an embodiment of the present application;

[0049] Figure 4 A schematic diagram of the interaction process between a client, a management center and an authorization system provided in an embodiment of the present application;

[0050] Figure 5 A schematic diagram of the interaction process between a client and an authorization system provided in an embodiment of the present application;

[0051] Figure 6 A schematic diagram of the structure of a software authorization device provided in an embodiment of the present application;

[0052] Figure 7 A schematic diagram of the structure of another software authorization device provided in an embodiment of the present application;

[0053] Figure 8 A schematic diagram of the structure of another software authorization device provided in an embodiment of the present application;

[0054] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0056] See also Figure 1 , Figure 1 A flowchart of a software authorization method provided in an embodiment of the present application. Figure 1 As shown, the software authorization method is applied to the client, and the software authorization method may include the following steps:

[0057] Step S102: Obtain an authorization file, wherein the authorization file includes first authorization request data corresponding to the software to be authorized and a first signature value obtained by signing the first authorization request data.

[0058] It should be noted that the software authorization method provided in the embodiment of the present application is applied to the client, and the client refers to a terminal device installed with a trusted platform control module (Trusted Platform Control Module, referred to as TPCM) or a trusted software base (Trusted Software Base, referred to as TSB). Among them, the trusted platform control module TPCM here is a hardware core module integrated in a trusted computing platform for establishing and protecting a trusted source point, which can provide integrity measurement, secure storage, trusted reporting, and cryptographic services for trusted computing. The trusted software base TSB here is a collection of software elements that provide support for the credibility of the trusted computing platform. The client can be connected to the management center network, and the first authorization request file is generated by interacting with the management center, and then the authorization file is generated by the authorization system; the client can also not be connected to the management center network, and rely on itself to generate a second authorization request file, and then generate an authorization file using the authorization system. The authorization system here can be connected to the client and the management center network, and interact online, or it can be connected to the client and the management center network and interact offline.

[0059] The above authorization file is generated by the authorization system based on the first authorization request file or the second authorization request file. After generating the authorization file, the authorization system can pass it to the management center online or offline, and then the management center sends it to the client; or pass it directly to the client online or offline. The authorization file may include the first authorization request data corresponding to the software to be authorized and the first signature value obtained by signing the first authorization request data. Since the first authorization request data in the authorization file is signed, it is not easy to be cracked or tampered with during the transmission process, thereby improving the security of the first authorization request data.

[0060] Step S104: verify the first signature value, and if the first signature value is verified, parse the first field information and the second field information from the first authorization request data, wherein the first field information is used to represent the identification information of the client requesting authorization, and the second field information is used to represent the expiration time of the authorization validity period.

[0061] After obtaining the authorization file, the client can first use the public key to verify the first signature value. If the first signature value verification fails, it means that the authorization file has been tampered with, and the authorization file needs to be discarded. If the first signature value verification passes, it means that the authorization file has not been tampered with. At this time, the first field information used to characterize the identification information of the client requesting authorization and the second field information used to characterize the expiration date of the authorization validity period can be parsed from the first authorization request data. As an optional implementation, the authorization file is 264 bytes in total, the byte length of the first signature value is 64 bytes, and the byte length of the first authorization request data is 200 bytes, of which the byte length of the first field information is 32 bytes, and the byte length of the second field information is 8 bytes.

[0062] Step S106: compare the first field information with its own identification information, and compare the second field information with the current time.

[0063] After obtaining the first field information and the second field information, the client can compare the first field information with its own identification information, and compare the second field information with the current time. If the first field information is consistent with its own identification information, it means that the client requesting authorization is the client, that is, the authorization file is the authorization file requested by the client; if the first field information is inconsistent with its own identification information, it means that the client requesting authorization is not the client, that is, the authorization file is not the authorization file requested by the client. If the second field information is greater than or equal to the current time, it means that the authorization is still valid, that is, the authorization file has not expired; if the second field information is less than the current time, it means that the authorization is not valid, that is, the authorization file has expired.

[0064] Step S108: When the first field information is consistent with its own identification information and the second field information is greater than or equal to the current time, authorize the software to be authorized.

[0065] If the first field information is consistent with its own identification information, and the second field information is greater than or equal to the current time, it means that the client requesting authorization is this client, and it is still within the authorization validity period. At this time, the software to be authorized can be authorized. If the first field information is inconsistent with its own identification information, or the second field information is less than the current time, it means that the client requesting authorization is not this client, or it is not within the authorization validity period. At this time, the authorization file can be discarded and the software to be authorized will not be authorized.

[0066] Through the above method, the client can obtain the first authorization request data corresponding to the software to be authorized and the first signature value obtained by signing the first authorization request data, and then verify the first signature value and the first field information and the second field information in the first authorization request data to realize the authorization of the software to be authorized. Therefore, compared with the traditional method of relying on a simple serial number to authorize software, the software authorization method provided by the embodiment of the present application is more secure and can better meet the needs of commercial software or enterprise-level applications that require high security.

[0067] In an optional embodiment, the above step S102, obtaining the authorization file, includes:

[0068] When a network connection is established between the server and the management center, the server receives second authorization request data issued by the management center, and signs the second authorization request data to obtain a second signature value, wherein the second authorization request data includes first field information and third field information, and the third field information is used to represent the expected number of authorization days;

[0069] The second authorization request data and the second signature value are concatenated into an authorization request string, and the authorization request string is sent to the management center, so that the management center can verify the second signature value in the authorization request string, and after the verification is passed, the second authorization request data is signed to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data;

[0070] Receive the authorization file returned by the management center, where the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data. The management center transmits the first authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the management center online or offline.

[0071] It should be noted that the second authorization request data can be obtained by inputting and filling in by the administrator of the management center, which can include the first field information for characterizing the identification information of the client requesting authorization and the third field information for characterizing the expected number of authorization days. Of course, it can also include other field information such as the authorization type (such as ordinary or advanced). The first authorization request file can include the second authorization request data and the third signature value obtained by signing the second authorization request data. In this way, the client can effectively prevent the second authorization request data from being tampered with during the transmission process by signing the second authorization request data. As an optional implementation, the first authorization request file is 260 bytes in total, the byte length of the third signature value is 64 bytes, and the byte length of the second authorization request data is 196 bytes, wherein the byte length of the first field information is 32 bytes, and the byte length of the third field information is 4 bytes. When the authorization system generates an authorization file based on the first authorization request file, it needs to adjust the second authorization request data to obtain the first authorization request data (that is, replace the 4-byte expected authorization days in the second authorization request data with the 8-byte authorization validity period, and other field information remains unchanged), plus the 64-byte first signature value obtained by signing the first authorization request data, the final generated authorization file is 264 bytes in total.

[0072] In this embodiment, when the client establishes a network connection with the management center, the client can obtain the first authorization request file and the authorization file with the help of the management center. Specifically, the client can receive the second authorization request data issued by the management center, sign the second authorization request data, obtain the second signature value, and then splice the second authorization request data and the second signature value into an authorization request string, and send the authorization request string to the management center, so that the management center can verify the second signature value in the authorization request string, and after the verification is passed, sign the second authorization request data to obtain the first authorization request file. Then, the management center can also pass the first authorization request file to the authorization system online or offline, so that the authorization system can verify the third signature in the first authorization request file, and after the verification is passed, adjust and sign the second authorization request data to obtain the authorization file, and then pass the authorization file to the management center online or offline, and then the management center returns the authorization file to the client, and finally the client can obtain the authorization file.

[0073] Through the above method, the client can obtain the first authorization request file and the authorization file with the help of the management center when establishing a network connection with the management center, thereby realizing the online authorization function, effectively avoiding the client user from obtaining the authorization information manually or by mail, and greatly simplifying the authorization process. At the same time, by signing and verifying the data, the security of the data is fully guaranteed.

[0074] In an optional embodiment, the above step S102, obtaining the authorization file, includes:

[0075] In the case where a network connection is not established between the system and the management center, receiving second authorization request data input by a user, and generating a second authorization request file based on the second authorization request data, wherein the second authorization request file only includes the second authorization request data, the second authorization request data includes first field information and third field information, and the third field information is used to represent the expected number of authorization days;

[0076] Obtain an authorization file from the authorization system, wherein the authorization file is obtained by adjusting and signing the second authorization request data by the authorization system, the client transmits the second authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the client online or offline.

[0077] It should be noted that the second authorization request data can be obtained by filling in the input of the user of the client, which can include the first field information for characterizing the identification information of the client requesting authorization and the third field information for characterizing the expected number of authorization days. Of course, it can also include other field information such as the authorization type (such as ordinary or advanced). The difference between the second authorization request file and the first authorization request file is that the second authorization request file only includes the second authorization request data, but does not include the third signature value obtained by signing the second authorization request data. As an optional implementation, the second authorization request file is 196 bytes in total, that is, the byte length of the second authorization request data, wherein the byte length of the first field information is 32 bytes, and the byte length of the third field information is 4 bytes. Because the authorization system needs to adjust the second authorization request data to obtain the first authorization request data when generating the authorization file based on the second authorization request file (that is, replace the 4-byte expected authorization days in the second authorization request data with the 8-byte authorization validity period deadline, and other field information remains unchanged), plus the 64-byte first signature value obtained by signing the first authorization request data, the final generated authorization file is 264 bytes in total.

[0078] In this embodiment, when the client does not establish a network connection with the management center, the client can obtain the second authorization request file and the authorization file by itself. Specifically, the client can receive the second authorization request data input by the user, generate the second authorization request file based on the second authorization request data, and then pass the second authorization request file to the authorization system online or offline. In this way, the authorization system can adjust the second authorization request data and sign it to obtain the authorization file, and then pass the authorization file to the client online or offline, and finally the client can obtain the authorization file.

[0079] Through the above method, the client can obtain the second authorization request file and the authorization file by itself without establishing a network connection with the management center, thereby realizing the offline authorization function and improving the flexibility of the authorization method. At the same time, by signing and verifying the data, the security of the data is fully guaranteed.

[0080] In an optional embodiment, after the above step of generating the second authorization request file based on the second authorization request data, the method further includes:

[0081] When a network connection is established between the device and the authorization system, the device sends a first request to the authorization system, wherein the first request carries a second authorization request file and a product serial number;

[0082] Receive a first response result or a second response result returned by the authorization system in response to the first request, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0083] It should be noted that the above-mentioned first request carries a second authorization request file and a product serial number, wherein the second authorization request file is the authorization request file generated by the client, and the product serial number can be understood as a user identity identification code. The authorization system can confirm whether the user identity is legal and whether it is a contract customer based on the product serial number.

[0084] In this embodiment, when the client establishes a network connection with the authorization system and generates a second authorization request file based on the second authorization request data, the client can send a first request to the authorization system, and send the second authorization request file and the product serial number to the authorization system. In this way, the authorization system can respond to the first request and first verify the product serial number. If the product serial number is verified, it means that the user identity is legal and can be authorized. The authorization system can generate an authorization file as a first response result; if the product serial number fails to be verified, it means that the user identity is illegal. At this time, the administrator of the authorization system needs to manually review the first request. If the manual review passes, authorization can be performed, and the authorization system can generate an authorization file as a first response result; if the manual review fails, authorization cannot be performed, and the administrator of the authorization system fills in the reason for the failure of authorization as the second response result. After the authorization system generates the first response result or the second response result, it can return the first response result or the second response result to the client.

[0085] Through the above method, when the client has not established a network connection with the management center, but has established a network connection with the authorization system, the authorization file can be directly obtained online by using the second authorization request file generated by the client itself and the pre-assigned product serial number, thereby improving the convenience of obtaining the authorization file and simplifying the authorization process.

[0086] See also Figure 2 , Figure 2 A flowchart of another software authorization method provided in an embodiment of the present application. Figure 2 As shown, the software authorization method is applied to the management center, and the software authorization method may include the following steps:

[0087] Step S202: When a network connection is established between the device and the client, the device sends second authorization request data to the client, so that the client can sign the second authorization request data to obtain a second signature value, and concatenate the second authorization request data and the second signature value into an authorization request string, wherein the second authorization request data includes first field information and third field information, the first field information is used to represent the identification information of the client requesting authorization, and the third field information is used to represent the expected number of days for authorization.

[0088] It should be noted that the software authorization method provided in the embodiment of the present application is applied to the management center, which can be understood as a management platform for TPCM type clients and TSB type clients. The management center can be connected to the client network, generate a first authorization request file by interacting with the client, and then generate an authorization file using the authorization system; the management center may not be connected to the client network, and the client itself generates a second authorization request file, and then generates an authorization file using the authorization system. The authorization system here can be connected to the client and management center networks and interact online, or it can be not connected to the client and management center networks and interact offline.

[0089] The above-mentioned second authorization request data can be input and filled in by an administrator of the management center. It may include first field information for representing the identification information of the client requesting authorization and third field information for representing the expected number of authorization days. Of course, it may also include other field information such as authorization type (such as ordinary or advanced).

[0090] When the management center establishes a network connection with the client, the second authorization request data can be sent to the client, so that the client can receive the second authorization request data, then sign the second authorization request data, obtain the second signature value, and concatenate the second authorization request data and the second signature value into an authorization request string. As an optional real-time method, the authorization request string is 260 bytes in total, the byte length of the second signature value is 64 bytes, and the byte length of the second authorization request data is 196 bytes, wherein the byte length of the first field information is 32 bytes, and the byte length of the third field information is 4 bytes.

[0091] Step S204: Receive the authorization request string sent by the client.

[0092] After generating the authorization request string, the client may send the authorization request string to the management center, and the management center may receive the authorization request string.

[0093] Step S206: verify the second signature value in the authorization request character string, and after the verification is passed, sign the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data.

[0094] It should be noted that the first authorization request file may include the second authorization request data and the third signature value obtained by signing the second authorization request data. In this way, the client can effectively prevent the second authorization request data from being tampered with during the transmission process by signing the second authorization request data. As an optional implementation, the first authorization request file is 260 bytes in total, the byte length of the third signature value is 64 bytes, and the byte length of the second authorization request data is 196 bytes, wherein the byte length of the first field information is 32 bytes, and the byte length of the third field information is 4 bytes. Since the authorization system needs to adjust the second authorization request data to obtain the first authorization request data when generating the authorization file based on the first authorization request file (i.e., replace the 4-byte expected authorization days in the second authorization request data with the 8-byte authorization validity period deadline, and other field information remains unchanged), plus the 64-byte first signature value obtained by signing the first authorization request data, the final generated authorization file is 264 bytes in total.

[0095] Step S208: pass the first authorization request file to the authorization system online or offline, and obtain the authorization file from the authorization system online or offline, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and after the verification is passed, adjusting the second authorization request data and signing it.

[0096] The management center can pass the first authorization request file to the authorization system online or offline, so that the authorization system can verify the third signature in the first authorization request file, and after the verification, adjust the second authorization request data and sign it to obtain the authorization file, and then pass the authorization file to the management center online or offline.

[0097] Step S210: Return the authorization file to the client, so that the client can authorize the software to be authorized based on the authorization file.

[0098] After the management center obtains the authorization file, it can return the authorization file to the client, and finally the client can obtain the authorization file.

[0099] Through the above method, the management center can obtain the first authorization request file and the authorization file by itself when establishing a network connection with the client, thereby realizing the online authorization function, effectively avoiding the client user from obtaining the authorization information manually or by mail, and greatly simplifying the authorization process. At the same time, by signing and verifying the data, the security of the data is fully guaranteed.

[0100] In an optional embodiment, after signing the second authorization request data to obtain the first authorization request file in the above step S206, the method further includes:

[0101] When a network connection is established between the device and the authorization system, the device sends a second request to the authorization system, wherein the second request carries the first authorization request file and the product serial number;

[0102] Receive a third response result or a fourth response result returned by the authorization system in response to the second request, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0103] It should be noted that the above-mentioned second request carries a first authorization request file and a product serial number, wherein the first authorization request file is the authorization request file generated by the management center, and the product serial number can be understood as a user identity identification code. The authorization system can confirm whether the user identity is legal and whether he is a contract customer based on the product serial number.

[0104] In this embodiment, when the management center establishes a network connection with the authorization system and generates a first authorization request file based on the second authorization request data, the management center can send a second request to the authorization system, and send the first authorization request file and the product serial number to the authorization system. In this way, the authorization system can respond to the second request and first verify the product serial number. If the product serial number is verified, it means that the user identity is legal and can be authorized. The authorization system can generate an authorization file as a third response result; if the product serial number fails to be verified, it means that the user identity is illegal. At this time, the administrator of the authorization system needs to manually review the second request. If the manual review passes, authorization can be performed, and the authorization system can generate an authorization file as a third response result; if the manual review fails, authorization cannot be performed, and the administrator of the authorization system fills in the reason for the failure of authorization as the fourth response result. After the authorization system generates the third response result or the fourth response result, it can return the third response result or the fourth response result to the management center.

[0105] Through the above method, when a network connection is established between the management center and the client, and the management center and the authorization system are connected to the network, the authorization file can be directly obtained online by using the first authorization request file generated by the management center itself and the pre-assigned product serial number, thereby improving the convenience of obtaining the authorization file and simplifying the authorization process.

[0106] See also Figure 3 , Figure 3 A flowchart of another software authorization method provided in an embodiment of the present application. Figure 3 As shown, the software authorization method is applied to the authorization system, and the software authorization method may include the following steps:

[0107] Step 302: obtaining a first authorization request file, verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data in the first authorization request file to obtain an authorization file, and delivering the authorization file to the management center online or offline, so that the management center can deliver the authorization file to the client, wherein the first authorization request file is generated by the management center, the third signature is obtained by the management center signing the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file; and / or,

[0108] Step 304: obtain a second authorization request file, adjust and sign the second authorization request data in the second authorization request file to obtain an authorization file, and deliver the authorization file to the client online or offline, wherein the second authorization request file is generated by the client, the second authorization request file includes only the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file.

[0109] It should be noted that the software authorization method provided in the embodiment of the present application is applied to an authorization system, and the authorization system is used to generate an authorization file based on a first authorization request file generated by a management center, or to generate an authorization file based on a second authorization request file generated by a client. The authorization system can be connected to the client and the management center network to interact online, or it can be not connected to the client and the management center network to interact offline.

[0110] As an optional implementation, the authorization system can obtain the first authorization request file from the management center online or offline, verify the third signature in the first authorization request file, and after the verification is passed, adjust and sign the second authorization request data in the first authorization request file to obtain the authorization file, and then transmit the authorization file to the management center online or offline. In this way, the management center can transmit the authorization file to the client, so that the client can authorize the software to be authorized based on the authorization file.

[0111] As another optional implementation, the authorization system can obtain the second authorization request file from the client online or offline, adjust and sign the second authorization request data in the second authorization request file to obtain the authorization file, and then transmit the authorization file to the client online or offline. In this way, the client can authorize the software to be authorized based on the authorization file.

[0112] Through the above method, the authorization system can centrally and efficiently manage the authorization files of the client and the management center, reducing management costs; at the same time, the authorization system can simultaneously process the authorization request files sent by the client and the management center, thereby realizing batch authorization processing.

[0113] In an optional embodiment, the method further comprises:

[0114] When establishing a network connection with the client, receiving a first request sent by the client, wherein the first request carries a second authorization request file and a product serial number;

[0115] In response to the first request, a first response result or a second response result is generated, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0116] The first response result or the second response result is returned to the client.

[0117] It should be noted that the above-mentioned first request carries a second authorization request file and a product serial number, wherein the second authorization request file is the authorization request file generated by the client, and the product serial number can be understood as a user identity identification code. The authorization system can confirm whether the user identity is legal and whether it is a contract customer based on the product serial number.

[0118] In this embodiment, when the client establishes a network connection with the authorization system and generates a second authorization request file based on the second authorization request data, the client can send a first request to the authorization system, and send the second authorization request file and the product serial number to the authorization system. In this way, the authorization system can respond to the first request and first verify the product serial number. If the product serial number is verified, it means that the user identity is legal and can be authorized. The authorization system can generate an authorization file as a first response result; if the product serial number fails to be verified, it means that the user identity is illegal. At this time, the administrator of the authorization system needs to manually review the first request. If the manual review passes, authorization can be performed, and the authorization system can generate an authorization file as a first response result; if the manual review fails, authorization cannot be performed, and the administrator of the authorization system fills in the reason for the failure of authorization as the second response result. After the authorization system generates the first response result or the second response result, it can return the first response result or the second response result to the client.

[0119] Through the above method, when the client has not established a network connection with the management center, but has established a network connection with the authorization system, the authorization file can be directly obtained online by using the second authorization request file generated by the client itself and the pre-assigned product serial number, thereby improving the convenience of obtaining the authorization file and simplifying the authorization process.

[0120] In an optional embodiment, the method further comprises:

[0121] When the network connection is established between the management center and the management center, the second request sent by the management center is received, wherein the second request carries the first authorization request file and the product serial number;

[0122] In response to the second request, a third response result or a fourth response result is generated, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0123] The third response result or the fourth response result is returned to the management center.

[0124] It should be noted that the above-mentioned second request carries a first authorization request file and a product serial number, wherein the first authorization request file is the authorization request file generated by the management center, and the product serial number can be understood as a user identity identification code. The authorization system can confirm whether the user identity is legal and whether he is a contract customer based on the product serial number.

[0125] In this embodiment, when the management center establishes a network connection with the authorization system and generates a first authorization request file based on the second authorization request data, the management center can send a second request to the authorization system, and send the first authorization request file and the product serial number to the authorization system. In this way, the authorization system can respond to the second request and first verify the product serial number. If the product serial number is verified, it means that the user identity is legal and can be authorized. The authorization system can generate an authorization file as a third response result; if the product serial number fails to be verified, it means that the user identity is illegal. At this time, the administrator of the authorization system needs to manually review the second request. If the manual review passes, authorization can be performed, and the authorization system can generate an authorization file as a third response result; if the manual review fails, authorization cannot be performed, and the administrator of the authorization system fills in the reason for the failure of authorization as the fourth response result. After the authorization system generates the third response result or the fourth response result, it can return the third response result or the fourth response result to the management center.

[0126] Through the above method, when a network connection is established between the management center and the client, and the management center and the authorization system are connected to the network, the authorization file can be directly obtained online by using the first authorization request file generated by the management center itself and the pre-assigned product serial number, thereby improving the convenience of obtaining the authorization file and simplifying the authorization process.

[0127] In an optional embodiment, when the client establishes a network connection with the management center, and the management center does not establish a network connection with the authorization system, the overall authorization issuance process is as follows: Figure 4 As shown, it specifically includes the following steps:

[0128] 1) The client initiates authorization and sends the public key to the management center.

[0129] 2) The management center saves the public key to the table lcerttpcm.

[0130] 3) The management center obtains the authorization request data and sends it to the client. The authorization request data is selected and filled in by the administrator of the management center on the page, and includes the client's identification information, the number of days of authorization validity (such as 1 to 3650 days), the authorization type (such as basic / advanced), and other information.

[0131] 4) The client reports an authorization request string, in which the first 196 bytes are the authorization request data and the last 64 bytes are the signature value.

[0132] 5) The management center uses the public key to verify the signature. After the signature is verified, it uses the private key of soc in the lcert table to sign and generate an authorization request file. Among them, the public key is transmitted by the client when initializing the authorization. The signed signature value is written into the authorization request file. The naming of the authorization request file needs to be named according to the preset rules, such as cerid-reqid, etc., where Cerid represents the unique identification information of the management center and reqid represents the file batch number.

[0133] 6) The management center exports the authorization request file.

[0134] 7) The management center offline uploads the authorization request file to the authorization system.

[0135] 8) The authorization system imports the authorization request file, uses the default certificate to verify the signature, and after the verification is passed, uses the default private key CAPrikey to sign and generate an authorization file. Among them, after the authorization system imports the authorization request file, it reads the file name and separates it with "-". Use the cerid field to query whether the relevant certificate of the management center has been imported into the authorization system. If not, the third-party certificate needs to be imported; use the cerid and reqid fields to query whether the authorization system has ever imported the authorization request file. If the authorization request file has been imported, the historical authorization request file needs to be deleted. After finding the relevant certificate through the cerid field, the authorization request file needs to be verified with the certificate, and after the verification is passed, the authorization request data is issued using the issuance certificate of the authorization center and a new signature value is generated. Then, the authorization request data and the signature value are combined to generate an authorization file.

[0136] 9) The authorization system exports the authorization file and transmits it to the management center offline.

[0137] 10) Import the authorization file into the management center.

[0138] 11) The management center sends the authorization file to the client.

[0139] 12) The client verifies the signature of the authorization document.

[0140] 13) The client returns the authorization result to the management center.

[0141] In an optional embodiment, when the client and the management center have not established a network connection, and the client and the authorization system have not established a network connection, the overall authorization issuance process is as follows: Figure 5 As shown, it specifically includes the following steps:

[0142] 1) The client exports the authorization request file.

[0143] 2) The client offline uploads the authorization request file to the authorization system.

[0144] 3) The authorization system imports the authorization request file, signs it with the default private key CAPrikey, and generates an authorization file. The authorization system does not verify the signature, but directly assembles the authorization request data such as authorization type, authorization validity period, after-sales service time, etc. in byte format and writes it into the file.

[0145] 4) The authorization system exports the authorization file and passes it to the client offline.

[0146] 5) The client imports the authorization file.

[0147] 6) The client verifies the signature of the authorization document.

[0148] It can be seen that the software authorization method provided in the embodiment of the present application has the following beneficial effects:

[0149] (1) Multiple management centers or clients can perform online authorization at the same time;

[0150] (2) Online authorization completes software authorization in an automated manner. Users no longer need to obtain authorization codes manually or by mail, which greatly simplifies the authorization process.

[0151] (3) Standardization of online authorization interfaces, which can ensure data security through encryption technology and signatures;

[0152] (4) The authorization system has functions such as batch processing and real-time updating, which enables centralized and efficient management of authorization information and reduces management costs.

[0153] (5) It simplifies the user authorization process, provides an intuitive interface and friendly operation prompts, and improves the user experience.

[0154] See also Figure 6 , Figure 6 A schematic diagram of the structure of a software authorization device provided in an embodiment of the present application. Figure 6 As shown, the software authorization device 600 is applied to the client, and the software authorization device 600 includes:

[0155] A first acquisition module 602 is used to acquire an authorization file, wherein the authorization file includes first authorization request data corresponding to the software to be authorized and a first signature value obtained by signing the first authorization request data;

[0156] The parsing module 604 is used to verify the first signature value, and if the first signature value is verified, parse the first authorization request data to obtain first field information and second field information, wherein the first field information is used to represent the identification information of the client requesting authorization, and the second field information is used to represent the expiration time of the authorization validity period;

[0157] A comparison module 606, used to compare the first field information with its own identification information, and to compare the second field information with the current time;

[0158] The authorization module 608 is used to authorize the software to be authorized when the first field information is consistent with its own identification information and the second field information is greater than or equal to the current time.

[0159] Furthermore, the first acquisition module 602 includes:

[0160] The first receiving submodule is used to receive the second authorization request data issued by the management center when the network connection is established between the first receiving submodule and the management center, and to sign the second authorization request data to obtain a second signature value, wherein the second authorization request data includes the first field information and the third field information, and the third field information is used to represent the expected number of authorization days;

[0161] a concatenation submodule, configured to concatenate the second authorization request data and the second signature value into an authorization request string, and send the authorization request string to the management center, so that the management center can verify the second signature value in the authorization request string, and after the verification is passed, sign the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data;

[0162] The second receiving submodule is used to receive the authorization file returned by the management center, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and after the verification, adjusting and signing the second authorization request data, the management center transmits the first authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the management center online or offline.

[0163] Furthermore, the first acquisition module 602 further includes:

[0164] a third receiving submodule, configured to receive second authorization request data input by a user when no network connection is established between the module and the management center, and generate a second authorization request file based on the second authorization request data, wherein the second authorization request file only includes the second authorization request data, the second authorization request data includes first field information and third field information, and the third field information is used to represent the expected number of authorization days;

[0165] The acquisition submodule is used to obtain the authorization file from the authorization system, wherein the authorization file is obtained by adjusting and signing the second authorization request data by the authorization system, the client transmits the second authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the client online or offline.

[0166] Furthermore, the software authorization device 600 further includes:

[0167] A first sending module, configured to send a first request to the authorization system when a network connection is established between the first sending module and the authorization system, wherein the first request carries a second authorization request file and a product serial number;

[0168] The first receiving module is used to receive a first response result or a second response result returned by the authorization system in response to the first request, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0169] It should be noted that the software authorization device 600 can implement the above Figure 1 The steps of the software authorization method provided by the method embodiment shown can achieve the same technical effect, and will not be repeated here one by one.

[0170] See also Figure 7 , Figure 7 This is a schematic diagram of the structure of another software authorization device provided in an embodiment of the present application. Figure 7 As shown, the software authorization device 700 is applied to the management center, and the software authorization device 700 includes:

[0171] The sending module 702 is used to send the second authorization request data to the client when the network connection is established between the module and the client, so that the client can sign the second authorization request data to obtain a second signature value, and concatenate the second authorization request data and the second signature value into an authorization request string, wherein the second authorization request data includes first field information and third field information, the first field information is used to represent the identification information of the client requesting authorization, and the third field information is used to represent the expected number of days for authorization;

[0172] The second receiving module 704 is used to receive the authorization request string sent by the client;

[0173] The first verification module 706 is used to verify the second signature value in the authorization request character string, and after the verification is passed, sign the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data;

[0174] The second acquisition module 708 is used to transmit the first authorization request file to the authorization system online or offline, and obtain the authorization file from the authorization system online or offline, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and adjusting and signing the second authorization request data after the verification is passed;

[0175] The first returning module 710 is used to return the authorization file to the client, so that the client can authorize the software to be authorized based on the authorization file.

[0176] Furthermore, the software authorization device 700 further includes:

[0177] A second sending module is used to send a second request to the authorization system when a network connection is established between the second sending module and the authorization system, wherein the second request carries the first authorization request file and the product serial number;

[0178] A third receiving module is used to receive a third response result or a fourth response result returned by the authorization system in response to the second request, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

[0179] It should be noted that the software authorization device 700 can implement the above Figure 2 The steps of the software authorization method provided by the method embodiment shown can achieve the same technical effect, and will not be repeated here one by one.

[0180] See also Figure 8 , Figure 8 A schematic diagram of the structure of another software authorization device provided in an embodiment of the present application. Figure 8 As shown, the software authorization device 800 is applied to the authorization system, and the software authorization device 800 includes:

[0181] The first adjustment and signing module 802 is used to obtain the first authorization request file, verify the third signature in the first authorization request file, and after the verification is passed, adjust and sign the second authorization request data in the first authorization request file to obtain the authorization file, and transmit the authorization file to the management center online or offline, so that the management center transmits the authorization file to the client, wherein the first authorization request file is generated by the management center, the third signature is obtained by the management center signing the second authorization request data, and the client is used to authorize the authorized software based on the authorization file; and / or,

[0182] The second adjustment and signature module 804 is used to obtain a second authorization request file, adjust and sign the second authorization request data in the second authorization request file to obtain an authorization file, and transmit the authorization file to the client online or offline, wherein the second authorization request file is generated by the client, the second authorization request file includes only the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file.

[0183] Furthermore, the software authorization device 800 further includes:

[0184] A fourth receiving module, configured to receive a first request sent by a client when a network connection is established between the module and the client, wherein the first request carries a second authorization request file and a product serial number;

[0185] A first generating module, configured to generate a first response result or a second response result in response to the first request, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0186] The second returning module is used to return the first response result or the second response result to the client.

[0187] Furthermore, the software authorization device 800 further includes:

[0188] A fifth receiving module, configured to receive a second request sent by the management center when the network connection between the module and the management center is established, wherein the second request carries the first authorization request file and the product serial number;

[0189] A second generating module is used to generate a third response result or a fourth response result in response to the second request, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails;

[0190] The third returning module is used to return the third response result or the fourth response result to the management center.

[0191] It should be noted that the software authorization device 800 can implement the above Figure 3 The steps of the software authorization method provided by the method embodiment shown can achieve the same technical effect, and will not be repeated here one by one.

[0192] like Fig. 9 As shown, the embodiment of the present application further provides an electronic device, including a processor 911, a communication interface 912, a memory 913 and a communication bus 914, wherein the processor 911, the communication interface 912, and the memory 913 communicate with each other through the communication bus 914.

[0193] Memory 913, used for storing computer programs;

[0194] In one embodiment of the present application, the processor 911 is used to implement the steps of the software authorization method provided by any of the aforementioned method embodiments when executing the program stored in the memory 913.

[0195] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the software authorization method provided in any of the aforementioned method embodiments are implemented.

[0196] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0197] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A software authorization method, characterized in that: Applied to a client, the method comprises: Obtaining an authorization file, wherein the authorization file includes first authorization request data corresponding to the software to be authorized and a first signature value obtained by signing the first authorization request data; Verify the first signature value, and if the first signature value is verified, parse the first authorization request data to obtain first field information and second field information, wherein the first field information is used to represent the identification information of the client requesting authorization, and the second field information is used to represent the expiration time of the authorization validity period; Compare the first field information with its own identification information, and compare the second field information with the current time; When the first field information is consistent with its own identification information and the second field information is greater than or equal to the current time, the software to be authorized is authorized.

2. The method according to claim 1, characterized in that The authorization file to be obtained includes: When a network connection is established between the user and the management center, receiving second authorization request data issued by the management center, and signing the second authorization request data to obtain a second signature value, wherein the second authorization request data includes the first field information and the third field information, and the third field information is used to represent the expected number of authorization days; splicing the second authorization request data and the second signature value into an authorization request string, and sending the authorization request string to the management center, so that the management center can verify the second signature value in the authorization request string, and after the verification is passed, signing the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data; Receive the authorization file returned by the management center, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data, the management center transmits the first authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the management center online or offline.

3. The method according to claim 1, characterized in that The authorization file to be obtained includes: In the case where a network connection is not established between the device and the management center, receiving second authorization request data input by a user, and generating a second authorization request file based on the second authorization request data, wherein the second authorization request file only includes the second authorization request data, the second authorization request data includes the first field information and the third field information, and the third field information is used to represent the expected number of authorization days; The authorization file is obtained from the authorization system, wherein the authorization file is obtained by adjusting and signing the second authorization request data by the authorization system, the client transmits the second authorization request file to the authorization system online or offline, and the authorization system transmits the authorization file to the client online or offline.

4. The method according to claim 3, characterized in that After generating a second authorization request file based on the second authorization request data, the method further includes: When a network connection is established between the authorization system and the authorization system, a first request is sent to the authorization system, wherein the first request carries the second authorization request file and the product serial number; Receive a first response result or a second response result returned by the authorization system in response to the first request, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

5. A software authorization method, characterized in that: Applied to a management center, the method includes: In the case of establishing a network connection between itself and the client, second authorization request data is sent to the client, so that the client signs the second authorization request data to obtain a second signature value, and the second authorization request data and the second signature value are concatenated into an authorization request string, wherein the second authorization request data includes first field information and third field information, the first field information is used to represent the identification information of the client requesting authorization, and the third field information is used to represent the expected number of days for authorization; Receiving the authorization request character string sent by the client; Verify the second signature value in the authorization request character string, and after the verification passes, sign the second authorization request data to obtain a first authorization request file, wherein the first authorization request file includes the second authorization request data and a third signature value obtained by signing the second authorization request data; The first authorization request file is delivered to the authorization system in an online or offline manner, and the authorization file is obtained from the authorization system in an online or offline manner, wherein the authorization file is obtained by the authorization system verifying the third signature in the first authorization request file, and adjusting and signing the second authorization request data after the verification is passed; The authorization file is returned to the client, so that the client can authorize the software to be authorized based on the authorization file.

6. The method according to claim 5, characterized in that After signing the second authorization request data to obtain the first authorization request file, the method further includes: When a network connection is established between the authorization system and the authorization system, a second request is sent to the authorization system, wherein the second request carries the first authorization request file and the product serial number; Receive a third response result or a fourth response result returned by the authorization system in response to the second request, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails.

7. A software authorization method, characterized in that: Applied to an authorization system, the method comprises: Obtaining a first authorization request file, verifying the third signature in the first authorization request file, and after the verification is passed, adjusting and signing the second authorization request data in the first authorization request file to obtain an authorization file, and delivering the authorization file to a management center online or offline, so that the management center can deliver the authorization file to a client, wherein the first authorization request file is generated by the management center, the third signature is obtained by the management center signing the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file; and / or, Obtain a second authorization request file, adjust and sign the second authorization request data in the second authorization request file to obtain an authorization file, and deliver the authorization file to the client online or offline, wherein the second authorization request file is generated by the client, the second authorization request file includes only the second authorization request data, and the client is used to authorize the software to be authorized based on the authorization file.

8. The method according to claim 7, characterized in that The method further comprises: When establishing a network connection between the client and the client, receiving a first request sent by the client, wherein the first request carries the second authorization request file and the product serial number; In response to the first request, generating a first response result or a second response result, wherein the first response result is a response result generated by the authorization system based on the second authorization request file when the product serial number verification passes or the manual review passes, and the second response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails; The first response result or the second response result is returned to the client.

9. The method according to claim 7, characterized in that: The method further comprises: When the network connection between the management center and the management center is established, receiving a second request sent by the management center, wherein the second request carries the first authorization request file and the product serial number; In response to the second request, generating a third response result or a fourth response result, wherein the third response result is a response result generated by the authorization system based on the first authorization request file when the product serial number verification passes or the manual review passes, and the fourth response result is a response result generated by the authorization system when the product serial number verification fails and the manual review fails; The third response result or the fourth response result is returned to the management center.

10. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the software authorization method described in any one of claims 1 to 4, or implementing the software authorization method described in any one of claims 5 to 6, or implementing the software authorization method described in any one of claims 7 to 9 when executing a program stored in a memory.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the software authorization method described in any one of claims 1 to 4, or implements the software authorization method described in any one of claims 5 to 6, or implements the software authorization method described in any one of claims 7 to 9.

Images