Software authorization method, device and computer equipment

By uniformly generating and managing authorization codes on the server side, the logical unified management problem in the authorization control of multiple application software is solved, authorization efficiency is improved, and real-time authorization management of terminal devices is realized to prevent default users from using.

CN112632484BActive Publication Date: 2024-12-06SHENZHEN SKYWORTH RGB ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011582118.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-28
Publication Date
2024-12-06
Estimated Expiration
2040-12-28

AI Technical Summary

Technical Problem

When the prior art realizes authorization control in multiple different application software, it is difficult to ensure unified management of authorization logic, and it is impossible to cancel the authorization of TV application software on the user terminal device in real time, especially when the number of terminal devices is large, the authorization efficiency is low.

Method used

The server receives the authorization code generation request sent by the terminal device, and generates the corresponding number of target authorization codes according to the software type of the target application software, and stores it in association with the device identifier to realize unified management of authorization logic and remote authorization control.

Benefits of technology

It realizes unified management of authorization logic in multiple different application software, improves the efficiency of software authorization, and supports real-time cancellation of authorization on user terminal devices, preventing defaulting users from continuing to use the software.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112632484B_ABST
    Figure CN112632484B_ABST
Patent Text Reader

Abstract

The present invention provides a software authorization method, apparatus and computer equipment. The software authorization method comprises: first receiving an authorization code generation request sent by a terminal device, then generating a target authorization code corresponding to the required number of authorization codes according to the software type of the target application software, then sending the target authorization code to the terminal device, and storing the target authorization code in association with the software type of the target application software. The authorization code generation request includes the software type of the target application software requested for authorization and the required number of authorization codes. The above-mentioned software authorization method generates a target authorization code corresponding to the required number of authorization codes according to the software type of the target application software that needs to be authorized on the terminal device, so that the same authorization code is used on each terminal device, thereby ensuring unified management of authorization logic and improving the efficiency of software authorization when multiple different application software need to implement authorization control.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data interaction, and in particular to a software authorization method, device and computer equipment. Background Art

[0002] After the current TV application software is deployed on the terminal device, the user can use the TV application software freely. If the customer fails to pay the TV application software service fee in time, the customer needs to be prevented from continuing to use the software normally.

[0003] In view of the above problems, the prior art implements the use control of TV application software by adding a page on each TV application software where a software authorization code needs to be entered. Such a solution makes it difficult to ensure the unified management of authorization logic when multiple different application software need to implement authorization control. It is also impossible to cancel the authorization of the TV application software on the user's terminal device in real time when the user breaches the contract as mentioned above. In addition, if there are a large number of terminal devices, it is necessary to manually enter the authorization code on each device to activate the software use function, resulting in low efficiency of software authorization. Summary of the invention

[0004] In order to solve the above technical problems, the present invention provides a software authorization method, device and computer equipment, and the specific scheme is as follows:

[0005] In a first aspect, the present application discloses an embodiment that provides a software authorization method, which is applied to a server, and the method includes:

[0006] Receiving an authorization code generation request sent by a terminal device, wherein the authorization code generation request includes the software type of the target application software for which authorization is requested and the number of authorization codes required;

[0007] Generate a target authorization code corresponding to the required number of authorization codes uniformly according to the software type of the target application software;

[0008] The target authorization code is sent to the terminal device, and the target authorization code is associated with the software type of the target application software and stored.

[0009] According to a specific implementation method disclosed in the present application, the step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software includes:

[0010] Get the type character corresponding to each target application software;

[0011] Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software;

[0012] Determine whether each of the character strings is the same as the generated authorization code;

[0013] If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code;

[0014] If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

[0015] According to a specific implementation method disclosed in the present application, the authorization code generation request also includes a device identification of the terminal device requested to be bound;

[0016] After the step of sending the target authorization code to the terminal device and storing the target authorization code in association with the software type of the target application software, the method further includes:

[0017] Establishing a mapping relationship between the target authorization code and the device identification of the terminal device;

[0018] The software type corresponding to the target authorization code and the mapping relationship are associated and stored in an authorization code database.

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

[0020] receiving a first query request sent by a terminal device when starting a target application software, wherein the first query request includes a device identifier of the terminal device and a software type of the target application software;

[0021] Querying the authorization code database to determine whether there is a reference authorization code that is mapped to the device identifier;

[0022] If a reference authorization code mapping with the device identifier exists in the authorization code database, and the available software type corresponding to the reference authorization code includes the software type of the target application software, assigning the terminal device with the usage permission corresponding to the target application software;

[0023] If the reference authorization code that is mapped to the device identifier does not exist in the authorization code database, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then the use permission corresponding to the target application software is not allocated to the terminal device;

[0024] Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

[0025] According to a specific implementation manner disclosed in the present application, after the step of not allocating usage rights corresponding to the target application software to the terminal device, the method further includes:

[0026] receiving a second query request sent by the terminal device, wherein the second query request includes a backup authorization code, a device identification of the terminal device, and a software type of the target application software;

[0027] Determine whether the standby authorization code exists in the authorization code database;

[0028] If the backup authorization code exists in the authorization code database, and the backup authorization code has not established a mapping relationship with the device identification of other terminal devices, a mapping relationship is established between the backup authorization code and the device identification of the terminal device, the software type corresponding to the backup authorization code and the mapping relationship are associated and stored, and the terminal device is allocated the use permission corresponding to the target application software;

[0029] If the backup authorization code does not exist in the authorization code database, or the backup authorization code has been mapped with the device identification of another terminal device, the terminal device is not allocated the usage permission corresponding to the target application software.

[0030] In a third aspect, the disclosed embodiment of the present application provides a software authorization method, which is applied to a terminal device, and the method includes:

[0031] Sending an authorization code generation request to a server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software;

[0032] Receive the target authorization code returned by the server.

[0033] According to a specific implementation manner disclosed in the present application, after the step of receiving the target authorization code returned by the server, the method further includes:

[0034] Based on the software type of the target application software corresponding to the received target authorization code, pre-generate first key information corresponding to the target application software through a key algorithm;

[0035] Storing the first key information in a key verification set;

[0036] When detecting the currently started application software to be verified, generating second key information corresponding to the application software to be verified by using the key algorithm;

[0037] Determining whether there is first key information matching the second key information in the key verification set;

[0038] If so, assigning usage permissions to the target application software;

[0039] If not present, no usage permission is allocated to the target application software.

[0040] According to a specific implementation method disclosed in the present application, the step of generating the first key information or the second key information by using a key algorithm includes:

[0041] Get an encryption key containing an M-bit string, where 50≤M≤150 and M is an integer;

[0042] Using reference data and the encryption key as input parameters, a symmetric encryption algorithm is used to obtain first data, wherein the reference data includes a device identification of the terminal device and a software type of the application software;

[0043] Performing encoding conversion on the first data to obtain second data;

[0044] Obtain a hash value of the second data through an information digest algorithm, and use the hash value as key information.

[0045] In a fourth aspect, the disclosed embodiment of the present application provides a software authorization device, which is arranged on a server, and the device includes:

[0046] A receiving module, configured to receive an authorization code generation request sent by a terminal device, wherein the authorization code generation request includes the software type of the target application software for which authorization is requested and the number of authorization codes required;

[0047] A generation module, used for uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software;

[0048] The sending module is used to send the target authorization code to the terminal device, and store the target authorization code in association with the software type of the target application software.

[0049] In a fifth aspect, the embodiment disclosed in the present application provides a software authorization device, which is arranged on a server, and the device includes:

[0050] A receiving module, configured to receive a first query request sent by a terminal device when starting a target application software, wherein the first query request includes a device identifier of the terminal device and a software type of the target application software;

[0051] A query module, used to query whether there is a reference authorization code that has a mapping relationship with the device identification in the authorization code database;

[0052] a permission allocation module, configured to allocate the use permission corresponding to the target application software to the terminal device if a reference authorization code mapping relationship is established with the device identification in the authorization code database, and the available software type corresponding to the reference authorization code includes the software type of the target application software;

[0053] If the reference authorization code that is mapped to the device identifier does not exist in the authorization code database, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then the use permission corresponding to the target application software is not allocated to the terminal device;

[0054] Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

[0055] In a sixth aspect, the embodiment disclosed in the present application provides a software authorization device, which is arranged in a terminal device, and the device includes:

[0056] A sending module, configured to send an authorization code generation request to a server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software;

[0057] A receiving module is used to receive the target authorization code returned by the server.

[0058] In a seventh aspect, an embodiment disclosed in the present application provides a computer device, comprising a processor and a memory, wherein the memory stores a computer program that can be executed by the processor, and the processor executes the computer program to implement the software authorization method described in any one of the first to third aspects.

[0059] In an eighth aspect, an embodiment disclosed in the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the software authorization method described in any one of the first to third aspects.

[0060] Compared with the prior art, this application has the following beneficial effects:

[0061] The software authorization method provided by the present invention first receives an authorization code generation request sent by a terminal device, then generates a target authorization code corresponding to the required number of authorization codes according to the software type of the target application software, then sends the target authorization code to the terminal device, and stores the target authorization code in association with the software type of the target application software. The authorization code generation request includes the software type of the target application software requested for authorization and the required number of authorization codes. The above-mentioned software authorization method generates a target authorization code corresponding to the required number of authorization codes according to the software type of the target application software that needs to be authorized on the terminal device, so that the same authorization code is used on each terminal device, thereby ensuring unified management of authorization logic and improving the efficiency of software authorization when multiple different application software need to implement authorization control. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the technical solution of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be regarded as limiting the scope of protection of the present invention. In each of the drawings, similar components are numbered similarly.

[0063] Figure 1 One of the flowcharts of a software authorization method provided in an embodiment of the present application;

[0064] Figure 2 A second flowchart of a software authorization method provided in an embodiment of the present application;

[0065] Figure 3 A third flowchart of a software authorization method provided in an embodiment of the present application;

[0066] Figure 4 A schematic diagram of a process flow for starting an authorized terminal device of a software authorization method provided in an embodiment of the present application;

[0067] Figure 5 A schematic diagram of a key generation algorithm flow of a software authorization method provided in an embodiment of the present application;

[0068] Figure 6 One of the module block diagrams of a software authorization device provided in an embodiment of the present application;

[0069] Figure 7 A second module block diagram of a software authorization device provided in an embodiment of the present application;

[0070] Figure 8 This is a third module block diagram of a software authorization device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0072] The components of the embodiments of the present invention generally described and shown in the drawings herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0073] Hereinafter, the terms "including", "having" and their cognates, which may be used in various embodiments of the present invention, are intended only to indicate specific features, numbers, steps, operations, elements, components or combinations of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing items or adding the possibility of one or more features, numbers, steps, operations, elements, components or combinations of the foregoing items.

[0074] Furthermore, the terms “first”, “second”, “third”, etc. are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

[0075] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present invention belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present invention.

[0076] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0077] See also Figure 1 , is a flowchart of a software authorization method provided in an embodiment of the present application. Figure 1 As shown, the method mainly includes:

[0078] Step S101: receiving an authorization code generation request sent by a terminal device.

[0079] The authorization code generation request includes the software type of the target application software for which authorization is requested and the required number of authorization codes.

[0080] The terminal device may be a TV terminal, the server may be a service platform where a TV manufacturer is located, the application software involved may include video playback software running on the TV terminal, and the server authorizes and manages the application software running on the TV terminal.

[0081] There are multiple different types of application software on the same terminal device. When at least two application software need authorization, you only need to send the software type of the target application software that needs authorization to allocate a unified authorization code to multiple different types of application software on the terminal device, ensuring unified management of authorization logic and improving the efficiency of software authorization. At the same time, considering that some users may have multiple terminal devices that need authorization at their residences or workplaces, when such multi-terminal users apply for software authorization, the authorization code generation request initiated can also include the number of authorization code requirements, so that the server can generate authorization codes corresponding to the number of authorization code requirements based on the authorization code generation request.

[0082] As shown in Table 1, the user can select the name of the target application software that needs to be authorized on the display interface of the terminal device, and the terminal device will send the type corresponding to the target application software selected by the user to the server. For example, if there are software A, software B, and software C on the display interface of the terminal device, the software types can be defined as 0, 1, and 2 respectively.

[0083] Table 1

[0084] Software Title A B C Software Type 0 1 2

[0085] Step S102: uniformly generate target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software.

[0086] The server includes a webpage (WEB) front-end and back-end. The WEB front-end is responsible for user data interaction, and the WEB back-end is responsible for data processing and data storage. In specific implementation, the WEB front-end receives the authorization code generation request sent by the terminal device. After the WEB front-end receives the authorization code generation request sent by the terminal device, it sends the software type of the target application software and the number of authorization codes required contained in this authorization code generation request to the WEB back-end.

[0087] The WEB backend randomly generates an N-digit character string for the software type and required quantity through a preset algorithm, and then performs a duplication check on the randomly generated character string. If the duplication check passes, the character string is used as the target authorization code.

[0088] In a specific implementation, the step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software includes:

[0089] Get the type character corresponding to each target application software;

[0090] Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software;

[0091] Determine whether each of the character strings is the same as the generated authorization code;

[0092] If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code;

[0093] If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

[0094] For example, after the WEB front end receives the authorization code generation request sent by the terminal device, it parses the authorization code generation request to obtain the target application software A and the number of authorization codes required is 3. Then the parsed target application software type and the number of authorization codes required are sent to the WEB back end. The WEB back end obtains the software type value as 0 and the number of authorization codes as 3, and randomly generates an N-bit string through a preset algorithm, which can be used as the required target authorization code, as shown in Table 2. The value range of N involved here can be 4≤N≤20, and N is a positive integer.

[0095] Of course, to ensure uniqueness, each time an N-digit string is generated, it is necessary to check whether the string already exists, that is, to screen whether the generated string is the same as the generated authorization code. If the same generated authorization code is not found, the N-digit string can be directly used as the target authorization code.

[0096] Table 2

[0097] Software Type Target Authorization Code 0 2383 9283 3373 0 9983 9603 3387 0 5683 7883 7645

[0098] Step S103: sending the target authorization code to the terminal device, and storing the target authorization code in association with the software type of the target application software.

[0099] In specific implementation, an N-bit string can be generated by a preset algorithm each time after passing the repeatability check, and then used as the target authorization code. Then continue to generate target authorization codes until the target authorization codes that meet the number of authorization code requirements are generated. It is also possible to uniformly perform a repeatability check on all generated strings, and after all strings pass the repeatability check, all target authorization codes are sent to the terminal device and each target authorization code and the corresponding target application software software type are associated and stored in the database of the WEB backend.

[0100] In addition, in another specific implementation, after the target authorization code is generated, it can also be bound to the terminal to facilitate user use. Specifically, the authorization code generation request also includes the device identification of the terminal device requested to be bound;

[0101] After the step of sending the target authorization code to the terminal device and storing the target authorization code in association with the software type of the target application software, the method further includes:

[0102] Establishing a mapping relationship between the target authorization code and the device identification of the terminal device;

[0103] The software type corresponding to the target authorization code and the mapping relationship are associated and stored in an authorization code database.

[0104] In specific implementation, since users purchase a large number of terminal devices at the same time, if the authorization code is manually bound to each terminal device one by one, it will result in too much time and labor cost for binding the authorization code, which is inefficient. At this time, the user can apply for remote authorization, and add the device identification of the terminal device to be bound in the authorization code generation request. The device identification of the terminal device can be the network MAC (Media Access Control Address, MAC for short) address of each terminal device. After the WEB backend generates the target authorization code, it establishes a mapping relationship between the target authorization code and the device identification of the terminal device one by one, and associates the mapping relationship with the software type corresponding to the target authorization code and stores it in the authorization code database.

[0105] For example, the number of terminal devices that the user needs to remotely authorize is 3, and the target application software that needs to be authorized on each terminal device is A. The network MAC addresses of these three terminal devices are 2C-6E-85-93-27-71, 2C-6E-85-93-27-72 and 2C-6E-85-93-27-73. Then, the authorization code request information sent by the terminal device to the server also includes the network MAC addresses of the above three terminal devices. At this time, the three target authorization codes generated by step S102 are assigned to the terminal devices one by one and a mapping relationship is established. As shown in Table 3, the mapping relationship and the software type corresponding to the target authorization code are associated and stored in the authorization code database.

[0106] Table 3

[0107] Software Type Target Authorization Code Terminal MAC 0 2383 9283 3373 2C-6E-85-93-27-71 0 9983 9603 3387 2C-6E-85-93-27-72 0 5683 7883 7645 2C-6E-85-93-27-73

[0108] If the target application software on the terminal device is authorized and the user breaches the contract, the authorization needs to be canceled remotely. The server deletes the mapping relationship data between the target authorization code and the device identification of the terminal device through the WEB front-end page, making the bound target authorization code of the terminal device invalid. At this time, the unbound terminal device will directly pop up the authorization code input page, preventing the user from using the target application software normally, and the previously entered authorization code will be invalid.

[0109] See also Figure 2 , is a flowchart of a software authorization method provided in an embodiment of the present application, and the software authorization method provided is the same as the above Figure 1 The difference between the software authorization method shown in FIG. 1 and FIG. 2 is that in this embodiment, the server performs authorization verification on the application software started by the terminal. Figure 2 As shown, the method mainly includes:

[0110] Step S201, receiving a first query request sent by a terminal device when starting a target application software.

[0111] The first query request includes the device identification of the terminal device and the software type of the target application software.

[0112] When the target application software on the terminal device goes online, the server's WEB backend will receive a first query request sent by the terminal device, including the device identification and the software type of the target application software. The first query request includes the device identification of the terminal device and the software type of the target application software, so that the server can determine whether the target authorization code at this time is bound to the device identification of the terminal device, or whether the software type corresponding to the target authorization code includes the software type of the target application software, based on the device identification of the terminal device and the software type of the target application software, to avoid the situation where the target authorization code is unbound in advance due to customer breach of contract, but the user can still continue to use the target authorization code.

[0113] Step S202: querying an authorization code database to determine whether there is a reference authorization code that has a mapping relationship with the device identifier.

[0114] If the authorization code database contains a reference authorization code that is mapped to the device identifier, the process proceeds to step S203 to determine whether the available software type corresponding to the reference authorization code includes the software type of the target application software.

[0115] If the available software type corresponding to the reference authorization code includes the software type of the target application software, the process proceeds to step S204 to allocate usage rights corresponding to the target application software to the terminal device.

[0116] If there is no reference authorization code in the authorization code database that is mapped to the device identifier, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then step S205 is entered, and the terminal device is not assigned usage rights corresponding to the target application software.

[0117] Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

[0118] For example, when the terminal device (2C-6E-85-93-27-71) starts the target software A, the terminal device sends the MAC address 2C-6E-85-93-27-71 and the software application type value 0 corresponding to the target software A to the WEB backend to ask whether it is authorized. At this time, the WEB backend queries the authorization code database based on the received MAC address and software application type value.

[0119] If there is a reference authorization code in the authorization code database that is mapped to the MAC address 2C-6E-85-93-27-71, and the available software type value corresponding to the reference authorization code includes the software type value 0 of the target application software, then the terminal device (2C-6E-85-93-27-71) is assigned the corresponding use permission of the target application software. At this time, the target software A can be used normally on the terminal device (2C-6E-85-93-27-71).

[0120] If the reference authorization code mapping relationship with the MAC address 2C-6E-85-93-27-71 does not exist in the authorization code database, or the available software type value corresponding to the existing reference authorization code does not include the software type value 0 of the target application software, for example: the available software type values ​​corresponding to the reference authorization code mapping relationship with the above MAC address are only 1 and 2, then the terminal device (2C-6E-85-93-27-71) will not be assigned usage rights. At this time, the target software A cannot be used normally on the terminal device (2C-6E-85-93-27-71).

[0121] In addition, in addition to the first query request sent by the terminal device when starting the target application software to inquire whether it can be used normally, the target application software can also be provided with a timer to send the device identification of the terminal device and the software type of the target application software to the server at regular intervals to inquire whether the authorization is canceled. After the binding is canceled, the server can send information to the user's pre-bound mobile terminal number or instant messaging software to remind the user. Ensure that after the target authorization code is unbound from the terminal device, the user receives the unbinding information so that the user can rebind in time to avoid receiving information that it cannot be used when the terminal device starts the target application software, which affects the user experience.

[0122] In specific implementation, after the verification fails in step S205 and the use permission is not obtained, an authorization code input page may pop up on the terminal device to prompt the user that the target application software cannot be used normally, the previously entered authorization code is invalid, and the user needs to enter another authorization code for verification.

[0123] After the step of not allocating the use permission corresponding to the target application software to the terminal device, the method further includes:

[0124] receiving a second query request sent by the terminal device, wherein the second query request includes a backup authorization code, a device identification of the terminal device, and a software type of the target application software;

[0125] Determine whether the standby authorization code exists in the authorization code database;

[0126] If the backup authorization code exists in the authorization code database, and the backup authorization code has not established a mapping relationship with the device identification of other terminal devices, a mapping relationship is established between the backup authorization code and the device identification of the terminal device, the software type corresponding to the backup authorization code and the mapping relationship are associated and stored, and the terminal device is allocated the use permission corresponding to the target application software;

[0127] If the backup authorization code does not exist in the authorization code database, or the backup authorization code has been mapped with the device identification of another terminal device, the terminal device is not allocated the usage permission corresponding to the target application software.

[0128] Specifically, when a user applies for an authorization code from a server, the authorization code generation request includes the software type of the target application software requested for authorization and the number of authorization codes required. A user can have multiple target authorization codes that are not bound to a terminal device at the same time. After the authorization code input page is displayed on the terminal device, the user can enter a backup authorization code on the terminal device. The server obtains the device identification of the terminal device, the software type of the target application software, and the backup authorization code. Then, based on the backup authorization code, a query is made in the authorization code database to determine whether the backup authorization code exists. If it does not exist, a backup authorization code error message is returned; if it exists, it continues to determine whether the backup authorization code has been bound to other terminal devices. If it has been bound to other terminal devices, information that the backup authorization code has been used is returned; if it has not been bound to other terminal devices, a mapping relationship between the backup authorization code and the device identification of the terminal device is established, and the mapping relationship and the software type of the target application software are associated and stored in the authorization code database, and information that the authorization is successful is returned.

[0129] If the terminal device receives an error message about the authorization code, the terminal device will display "The entered authorization code is incorrect", and the user will be blocked from using the target application software. The previously entered authorization code is invalid, and the user needs to enter another backup authorization code for verification. If the terminal device receives a message that the authorization code has been used, the terminal device will display "The entered authorization code is already occupied", and the user will be blocked from using the target application software. The previously entered authorization code is invalid, and the user needs to enter another backup authorization code for verification. If the terminal device receives a message that the application authorization is successful, the authorization code input page will be exited directly, and the target application software can be used normally on the terminal device.

[0130] See also Figure 3 , is a flowchart of a software authorization method provided in an embodiment of the present application, and the software authorization method provided is the same as the above Figure 1 and Figure 2 The difference between the software authorization method shown in FIG. 1 and FIG. 2 is that this embodiment is applied to a terminal device. Figure 3 As shown, the method mainly includes:

[0131] Step S301, sending an authorization code generation request to the server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software.

[0132] Step S302: receiving the target authorization code returned by the server.

[0133] Corresponding to the above Figure 1In an embodiment, after the terminal device applies to the server for an authorization code for using a specific type of software, the server returns a certain number of target authorization codes required by the terminal device. The terminal device can store the received target authorization codes separately, so as to facilitate the use verification by using the stored target authorization codes later.

[0134] On the basis of the above embodiments, a solution for the terminal device to perform authorization verification locally can also be provided. Specific usage scenarios may include: after the terminal device receives the target authorization code returned by the server, the terminal device starts the startup verification scenario of the target application software, or the terminal device is offline and cannot be verified online. In these two states, local key verification is performed, so that the terminal device does not need to frequently access the server to verify the authorization code, reducing the access pressure on the server.

[0135] Specifically, after the step of receiving the target authorization code returned by the server, the method further includes:

[0136] Based on the software type of the target application software corresponding to the received target authorization code, pre-generate first key information corresponding to the target application software through a key algorithm;

[0137] Storing the first key information in a key verification set;

[0138] When the currently started application software to be verified is detected, second key information corresponding to the application software to be verified is generated by the key algorithm;

[0139] Determining whether there is first key information matching the second key information in the key verification set;

[0140] If so, assigning usage permissions to the target application software;

[0141] If not present, no usage permission is allocated to the target application software.

[0142] When the terminal device receives the information that the application is authorized successfully, it directly exits the authorization code input page. The first key information TARGET_DATA01 is generated according to the key algorithm and stored in the key verification set of the terminal device. The key verification set can be the configuration file of the target application software. The target application software defines the configuration file to store the first key information and is initialized to empty.

[0143] The authorization logic of the terminal device can be completed by two roles: the target application software and the authorization tool software. The authorization tool software is independent of the target application software that needs to be authorized, and the two are installed and deployed separately. The authorization software tool interface interacts with the server data, and the target application software interacts with the authorization tool software.

[0144] like Figure 4 The figure shows a specific example of the above authorization verification method. For the above two situations where local authorization verification is required, the terminal device generates the second key information corresponding to the target application software to be verified through the key algorithm, and the second key information can be represented as TARGET_DATA02, and obtains the first key information TARGET_DATA01 that has been stored in the key verification set. The first key information TARGET_DATA01 and the second key information TARGET_DATA02 are checked for legitimacy. If the legitimacy check is successful, the target application software program enters the normal function use process; if the legitimacy check fails, the authorization code input page pops up on the terminal device, preventing the user from using the target application software normally, and the previously entered authorization code is invalid. The user needs to reconnect to the server to apply for or bind the authorization code.

[0145] like Figure 5 The diagram is a schematic diagram of a process of generating key information using a key generation algorithm. The steps of generating the first key information or the second key information using the key algorithm include:

[0146] Get an encryption key containing an M-bit string, where 50≤M≤150 and M is an integer;

[0147] Using reference data and the encryption key as input parameters, a symmetric encryption algorithm is used to obtain first data, wherein the reference data includes a device identification of the terminal device and a software type of the application software;

[0148] Performing encoding conversion on the first data to obtain second data;

[0149] Obtain a hash value of the second data through an information digest algorithm, and use the hash value as key information.

[0150] In the specific implementation, an M-bit string is predefined as the encryption KEY. The key algorithm generation method is defined as: obtaining the device identification of the terminal device and the software type value of the target application software and merging them into data DATA, using DATA and the encryption KEY as input parameters, using the DES encryption algorithm to obtain the result DATA01, and then converting DATA01 through BASE64 to output DATA02, and finally using the MD5 algorithm to obtain the MD5 value of DATA02 data as TARGET_DATA, then the generated first key information and second key information are TARGET_DATA01 and TARGET_DATA02 respectively.

[0151] The software authorization method provided by the present invention can meet the unified implementation of various types of application software authorization. On the one hand, multiple terminal devices can be authorized remotely at the same time, and a large number of terminal devices deployed can be remotely authorized without entering an authorization code, thereby improving the deployment efficiency of the terminal devices. On the other hand, when a small number of terminal devices are deployed, the authorization can be activated by entering an authorization code on the terminal device. In addition, for terminal devices that have been authorized for use, the authorization can be canceled remotely. The terminal application authorization mechanism also adopts a dual mechanism of remote service query and local encrypted storage to ensure the security of authorization licenses.

[0152] Corresponding to the above method embodiment, see Figure 6 The present invention further provides a software authorization device 600, which is arranged on a server, and the software authorization device 600 comprises:

[0153] The receiving module 601 is used to receive an authorization code generation request sent by a terminal device, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the number of authorization codes required;

[0154] A generating module 602, configured to uniformly generate target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software;

[0155] The sending module 603 is used to send the target authorization code to the terminal device, and store the target authorization code in association with the software type of the target application software.

[0156] See also Figure 7 The present invention further provides a software authorization device 700, which is arranged on a server, and the software authorization device 700 comprises:

[0157] A receiving module 701 is configured to receive a first query request sent by a terminal device when starting a target application software, wherein the first query request includes a device identifier of the terminal device and a software type of the target application software;

[0158] A query module 702 is used to query the authorization code database whether there is a reference authorization code that has a mapping relationship with the device identifier;

[0159] The permission allocation module 703 is used to allocate the use permission corresponding to the target application software to the terminal device if there is a reference authorization code in the authorization code database that is mapped with the device identifier, and the available software type corresponding to the reference authorization code includes the software type of the target application software;

[0160] If the reference authorization code that is mapped to the device identifier does not exist in the authorization code database, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then the use permission corresponding to the target application software is not allocated to the terminal device;

[0161] Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

[0162] See also Figure 8 The present invention further provides a software authorization device 800, which is arranged in a terminal device, and the software authorization device 800 comprises:

[0163] The sending module 801 is used to send an authorization code generation request to the server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software;

[0164] The receiving module 802 is used to receive the target authorization code returned by the server.

[0165] In addition, a computer device is also provided. The computer device includes a processor and a memory. The memory stores a computer program that can be executed by the processor. The processor executes the computer program to implement the above software authorization method.

[0166] In addition, a computer-readable storage medium is also provided, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the above-mentioned software authorization method.

[0167] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0168] In addition, the functional modules or units in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0169] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program codes.

[0170] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A software authorization method, It is characterized in that Applied to a server, the method comprises: Receiving an authorization code generation request sent by a terminal device, wherein the authorization code generation request includes the software type of the target application software for which authorization is requested and the number of authorization codes required; Generate a target authorization code corresponding to the required number of authorization codes uniformly according to the software type of the target application software; Sending the target authorization code to the terminal device, and storing the target authorization code in association with the software type of the target application software; The step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software comprises: Get the type character corresponding to each target application software; Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software; Determine whether each of the character strings is the same as the generated authorization code; If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code; If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

2. The method according to claim 1, It is characterized in that The authorization code generation request also includes a device identifier of the terminal device requested to be bound; After the step of sending the target authorization code to the terminal device and storing the target authorization code in association with the software type of the target application software, the method further includes: Establishing a mapping relationship between the target authorization code and the device identification of the terminal device; The software type corresponding to the target authorization code and the mapping relationship are associated and stored in an authorization code database.

3. A software authorization method, It is characterized in that Applied to a server, the method comprises: receiving a first query request sent by a terminal device when starting a target application software, wherein the first query request includes a device identifier of the terminal device and a software type of the target application software; Querying the authorization code database to determine whether there is a reference authorization code that is mapped to the device identifier; If a reference authorization code mapping with the device identifier exists in the authorization code database, and the available software type corresponding to the reference authorization code includes the software type of the target application software, assigning the terminal device with the usage permission corresponding to the target application software; If the reference authorization code that is mapped to the device identifier does not exist in the authorization code database, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then the use permission corresponding to the target application software is not allocated to the terminal device; Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

4. The method according to claim 3, It is characterized in that After the step of not allocating the use permission corresponding to the target application software to the terminal device, the method further includes: receiving a second query request sent by the terminal device, wherein the second query request includes a backup authorization code, a device identification of the terminal device, and a software type of the target application software; Determine whether the standby authorization code exists in the authorization code database; If the backup authorization code exists in the authorization code database, and the backup authorization code has not established a mapping relationship with the device identification of other terminal devices, a mapping relationship is established between the backup authorization code and the device identification of the terminal device, the software type corresponding to the backup authorization code and the mapping relationship are associated and stored, and the terminal device is allocated the use permission corresponding to the target application software; If the backup authorization code does not exist in the authorization code database, or the backup authorization code has been mapped with the device identification of another terminal device, the terminal device is not allocated the usage permission corresponding to the target application software.

5. A software authorization method, It is characterized in that Applied to a terminal device, the method comprises: Sending an authorization code generation request to a server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software; Receiving the target authorization code returned by the server; The step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software comprises: Get the type character corresponding to each target application software; Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software; Determine whether each of the character strings is the same as the generated authorization code; If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code; If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

6. The method according to claim 5, It is characterized in that After the step of receiving the target authorization code returned by the server, the method further includes: Based on the software type of the target application software corresponding to the received target authorization code, pre-generate first key information corresponding to the target application software through a key algorithm; Storing the first key information in a key verification set; When the currently started application software to be verified is detected, second key information corresponding to the application software to be verified is generated by the key algorithm; Determining whether there is first key information matching the second key information in the key verification set; If so, assigning usage permissions to the target application software; If not present, no usage permission is allocated to the target application software.

7. The method according to claim 6, It is characterized in that The step of generating the first key information or the second key information by using a key algorithm includes: Get an encryption key containing an M-bit string, where 50≤M≤150 and M is an integer; Using reference data and the encryption key as input parameters, a symmetric encryption algorithm is used to obtain first data, wherein the reference data includes a device identification of the terminal device and a software type of the application software; Performing encoding conversion on the first data to obtain second data; Obtain a hash value of the second data through an information digest algorithm, and use the hash value as key information.

8. A software authorization device, It is characterized in that Set on the server, the device includes: A receiving module, configured to receive an authorization code generation request sent by a terminal device, wherein the authorization code generation request includes the software type of the target application software for which authorization is requested and the number of authorization codes required; A generation module, used for uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software; A sending module, used for sending the target authorization code to the terminal device, and storing the target authorization code in association with the software type of the target application software; The step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software comprises: Get the type character corresponding to each target application software; Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software; Determine whether each of the character strings is the same as the generated authorization code; If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code; If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

9. A software authorization device, It is characterized in that Set on the server, the device includes: A receiving module, configured to receive a first query request sent by a terminal device when starting a target application software, wherein the first query request includes a device identifier of the terminal device and a software type of the target application software; A query module, used to query whether there is a reference authorization code that has a mapping relationship with the device identification in the authorization code database; a permission allocation module, configured to allocate the use permission corresponding to the target application software to the terminal device if a reference authorization code mapping relationship is established with the device identification in the authorization code database, and the available software type corresponding to the reference authorization code includes the software type of the target application software; If the reference authorization code that is mapped to the device identifier does not exist in the authorization code database, or the available software type corresponding to the existing reference authorization code does not include the software type of the target application software, then the use permission corresponding to the target application software is not allocated to the terminal device; Wherein, the reference authorization code is uniformly generated according to the software type of the target application software.

10. A software authorization device, It is characterized in that Set in a terminal device, the device includes: A sending module, configured to send an authorization code generation request to a server, wherein the authorization code generation request includes the software type of the target application software requested for authorization and the required number of corresponding authorization codes, so that the server uniformly generates target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software; A receiving module, used for receiving the target authorization code returned by the server; The step of uniformly generating target authorization codes corresponding to the required number of authorization codes according to the software type of the target application software comprises: Get the type character corresponding to each target application software; Generate a character string corresponding to the required number of authorization codes using a preset algorithm according to the type characters of all target application software; Determine whether each of the character strings is the same as the generated authorization code; If the character string is different from the generated authorization code, the character string is used as the corresponding target authorization code; If the character string is the same as the generated authorization code, a new character string is generated according to the type characters of all target application software as the target authorization code.

11. A computer device, It is characterized in that The computer device comprises a processor and a memory, wherein the memory stores a computer program executable by the processor, and the processor executes the computer program to implement the software authorization method according to any one of claims 1 to 7.

12. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the software authorization method according to any one of claims 1 to 7.