CN112035802A - Method, device and system for preventing software from being abnormally activated - Google Patents

Abstract

One or more embodiments of the present specification provide a method, an apparatus, and a system for preventing software from being abnormally activated, wherein the method includes: the method comprises the steps that a client sends activation request information to a server, wherein the activation request information carries unique code information of the client; the server judges whether the client is activated repeatedly according to the unique code information; if the client is repeatedly activated, the server judges whether the client is in a factory history activation cluster; if the client is in the factory history activation cluster, the server judges whether the client reaches a preset activation frequency; if the client reaches the preset activation times, the server sends activation refusing information to the client; the client receives the activation refusing information and refuses to execute the activation operation, so that the problem that a manufacturer wrongly swipes the unique hardware code can be effectively avoided, and the normal upgrading of software when a user uses the software is not influenced.

Description

A method, device and system for preventing abnormal activation of software

technical field

One or more embodiments of this specification relate to the technical field of software activation, and in particular, to a method, apparatus, and system for preventing abnormal activation of software.

Background technique

Currently, third-party software activation is usually performed by binding an activation code to device hardware information. The main activation process is as follows:

1) The software reads the specific hardware information, uses it as the unique code of the device, and sends it to the cloud for activation application;

2) After the cloud receives the activation application, it performs relevant calculations and verifications on the unique code, and issues authorization information after passing;

3) After the software receives the authorization information, it is encrypted and stored locally through a certain encryption method;

4) When the locally stored authorization information is lost or wrong, reactivate, that is, repeat step (1).

On the one hand, in order to prevent problems such as abnormal device hardware information and flashing errors, the cloud usually limits the number of times a unique code can be activated. On the other hand, due to system upgrade, hardware replacement, user mistaken deletion, etc., the local authorization file may be wrong and lost, which will lead to reactivation and increase the number of activations of the unique code. Software is not available.

At present, there are three mainstream limited solutions in the cloud:

1) Only the unique code of the device is verified, and the number of repeated activations is not limited. This method cannot prevent manufacturers from accidentally flashing the hardware unique code information, that is, substantially different devices use the same unique code, resulting in incorrect authorization counts and economic losses;

2) Each unique code allows activation to be repeated for a certain number of times. In order to ensure security, the number of allowed repeated activations is generally not high, so it is easy to reach the limit threshold. It also lays the groundwork for future software upgrades;

3) Cooperate with the manufacturer. The manufacturer specifies the equipment to be upgraded, and the cloud performs special processing to increase the limited number of times of the equipment to be upgraded. The implementation of this method requires the cooperation of multiple parties, and the implementation process is too complicated and does not actually have general operability. At the same time, there are certain restrictions on user deletion by mistake.

SUMMARY OF THE INVENTION

In view of this, the purpose of one or more embodiments of this specification is to propose a method, device and system for preventing abnormal activation of software, which can effectively prevent manufacturers from mistakenly brushing hardware unique codes, and does not affect the normal operation of software when users use it. upgrade.

Based on the above purpose, one or more embodiments of this specification provide a method for preventing abnormal activation of software, which is applied to a client, including:

Send activation request information to the server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeated activation; if the client is repeated activation , then activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine whether the client has reached the preset number of activations ; If the client reaches a preset number of activations, then activate the server to send refusal to activate information to the client;

The denial of activation information is received.

As an optional implementation manner, the method further includes: performing an activation operation after receiving activation information of the server, where the activation information is that the unique code information activates when the client is not repeatedly activated Sent by the server to the client.

As an optional implementation manner, the method further includes: performing an activation operation after receiving activation information of the server, where the activation information is that the unique code information activates when the client is not repeatedly activated Sent by the server to the client.

As a second aspect of the present invention, a method for preventing abnormal activation of software is provided, applied to a server, including:

Receive activation request information sent by the client, where the activation request information carries the unique code information of the client;

Determine whether the client is repeatedly activated according to the unique code information;

If the client is repeatedly activated, determine whether the client is in the factory history activation cluster;

If the client is in the factory history activation cluster, determine whether the client has reached a preset number of activations;

If the client reaches a preset number of activations, send activation rejection information to the client.

As an optional implementation manner, the method further includes: if the client is activated repeatedly, sending activation information to the client.

As an optional implementation manner, the method further includes: if the client is not in the factory history activation cluster, sending activation information to the client.

As a second aspect of the present invention, a method for preventing abnormal activation of software is provided, which is characterized in that, comprising:

The client sends activation request information to the server, where the activation request information carries the unique code information of the client;

The server judges whether the client is repeatedly activated according to the unique code information;

If the client is repeatedly activated, the server determines whether the client is in the factory history activation cluster;

If the client is in the factory history activation cluster, the server determines whether the client has reached a preset number of activations;

If the client reaches a preset number of activations, the server sends activation rejection information to the client;

The client terminal receives the activation rejection information, and rejects the activation operation.

As a second aspect of the present invention, a device for preventing abnormal activation of software is provided, applied to a client, including:

a first sending unit, configured to send activation request information to a server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeatedly activated; if If the client is repeatedly activated, activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine the client Whether the preset number of activations is reached; if the client reaches the preset number of activations, activate the server to send activation rejection information to the client;

A first receiving unit, configured to receive the activation rejection information.

As a second aspect of the present invention, a device for preventing abnormal activation of software is provided, applied to a server, including:

a receiving unit, configured to receive activation request information sent by a client, where the activation request information carries the unique code information of the client;

a first judging unit, configured to judge whether the client is repeatedly activated according to the unique code information;

a second judging unit, configured to judge whether the client is in the factory history activation cluster when the client is repeatedly activated;

a third judging unit, configured to judge whether the client has reached a preset number of activations when the client is in the factory historical activation cluster;

The second sending unit is configured to send activation rejection information to the client when the client reaches a preset number of activations.

As a second aspect of the present invention, a system for preventing abnormal activation of software is provided, including a client and a server, wherein the client is the aforementioned client, and the server is the aforementioned server.

As can be seen from the above, one or more embodiments of this specification provide a method, device and system for preventing abnormal software activation. The unique code information of the terminal determines whether it is repeatedly activated, whether it is in the factory historical activation cluster, and whether the preset number of activations has been reached. When the client is repeatedly activated, is in the factory historical activation cluster, and reaches the preset number of activations , the server sends the activation rejection information to the client; the client receives the activation rejection information, refuses to perform the activation operation, and refuses to perform the activation operation. In this way, the manufacturer can effectively prevent the manufacturer from accidentally flashing the hardware unique code, It also does not affect the normal upgrade of the software when the user is using it.

Description of drawings

In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the following briefly introduces the accompanying drawings used in the description of the embodiments or the prior art. Obviously, in the following description The accompanying drawings are only one or more embodiments of the present specification, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is a logical schematic diagram of a method of one or more embodiments of the specification;

FIG. 2 is a schematic diagram of an apparatus (client) according to one or more embodiments of the present specification;

3 is a schematic diagram (server side) of an apparatus according to one or more embodiments of the specification;

FIG. 4 is a logical schematic diagram of an embodiment.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present disclosure clearer, the present disclosure will be further described in detail below with reference to the specific embodiments and the accompanying drawings.

First of all, it should be noted that in each embodiment of the present invention, the terms involved are:

Client: Smart terminals with software-installed clients, such as mobile phones, tablet computers, e-book readers, MP3 players, MP4 players, laptops and desktops, etc.

Server: The server, cloud server, server cluster, etc. where the software is installed.

As shown in FIG. 1, in order to achieve the above purpose of the invention, an embodiment of the present invention provides a method for preventing abnormal activation of software, including:

S100. The client sends activation request information to the server, where the activation request information carries the unique code information of the client;

S200, the server determines whether the client is repeatedly activated according to the unique code information;

S300, if the client is repeatedly activated, the server determines whether the client is in a factory history activation cluster;

S400. If the client is in the factory history activation cluster, the server determines whether the client has reached a preset number of activations;

S500. If the client reaches a preset number of activations, the server sends activation rejection information to the client;

S600. The client terminal receives the activation rejection information, and rejects the activation operation.

In this embodiment of the present invention, when a client with software installed sends activation request information to the server, the server judges whether the client is in the factory history activation cluster according to the unique code information of the client, and if it is not in the factory history activation cluster , it means that the client has been sold to the user, it means that the activation request information sent by the client at this time belongs to the normal upgrade and update of the software, then the server responds to the client's request and sends the activation information to the client, and the client receives the After receiving the activation request from the server, the activation operation is performed; if it is in the factory history activation cluster, it is necessary to further determine whether the client has reached the preset activation times. If the preset activation times have not been reached, the server responds to the client. After receiving the activation request from the server, the client performs an activation operation; if the preset number of activations has been reached, the server sends activation rejection information to the client; the The client terminal receives the activation rejection information, refuses to perform the activation operation, and refuses to perform the activation operation. In this way, the manufacturer can effectively prevent the manufacturer from swiping the hardware unique code by mistake, and it does not affect the normal upgrade of the software when the user is using it.

Wherein, the factory history activation cluster includes WIFI information and/or IP information and/or GPS information

As a second aspect of the embodiments of the present invention, a method for preventing abnormal activation of software is provided, applied to a client, including:

Send activation request information to the server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeated activation; if the client is repeated activation , then activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine whether the client has reached the preset number of activations ; If the client reaches a preset number of activations, then activate the server to send refusal to activate information to the client;

The denial of activation information is received.

In this embodiment of the present invention, the client first sends activation request information that carries unique code information to the server, and the unique code information enables the activation server to determine whether the client is repeatedly activated, whether it is in the factory historical activation cluster, or whether it has reached a predetermined level. Set the number of activations, and send the activation information or reject the activation information to the client; after the client receives the activation information or rejects the activation information sent by the server, it executes the activation operation or rejects the activation operation.

As an optional implementation manner, the method further includes: performing an activation operation after receiving activation information of the server, where the activation information is that the unique code information activates when the client is not repeatedly activated Sent by the server to the client.

As an optional implementation manner, the method further includes: performing an activation operation after receiving activation information of the server, where the activation information is that the unique code information activates when the client is not repeatedly activated Sent by the server to the client.

As a third aspect of the embodiments of the present invention, a method for preventing abnormal activation of software is provided, applied to a server, including:

Receive activation request information sent by the client, where the activation request information carries the unique code information of the client;

Determine whether the client is repeatedly activated according to the unique code information;

If the client is repeatedly activated, determine whether the client is in the factory history activation cluster;

If the client is in the factory history activation cluster, determine whether the client has reached a preset number of activations;

If the client reaches a preset number of activations, send activation rejection information to the client.

In the embodiment of the present invention, after receiving the activation request information carrying the unique code information sent by the client, the server determines whether the client is repeatedly activated, whether it is in the factory historical activation cluster, or not according to the unique code information. Whether the preset number of activations is reached, and send activation information or reject activation information to the client accordingly. Specifically, when the client is activated for the first time, or when the client is not in the factory historical activation cluster, or the client has not reached the preset number of activations, the server sends activation information to the client; otherwise, the server sends the activation information to the client. The refusal to activate the sent information can prevent abnormal activation of the software.

As an optional implementation manner, the method further includes: if the client is activated repeatedly, sending activation information to the client.

As an optional implementation manner, the method further includes: if the client is not in the factory history activation cluster, sending activation information to the client.

As a fourth aspect of the embodiment of the present invention, as shown in FIG. 2 , an embodiment of the present invention further provides a device for preventing abnormal activation of software, which is applied to a client and includes:

a first sending unit, configured to send activation request information to a server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeatedly activated; if If the client is repeatedly activated, activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine the client Whether the preset number of activations is reached; if the client reaches the preset number of activations, activate the server to send activation rejection information to the client;

A first receiving unit, configured to receive the activation rejection information.

As a fourth aspect of the embodiment of the present invention, as shown in FIG. 3 , an embodiment of the present invention further provides a device for preventing abnormal activation of software, which is applied to a server, including:

a receiving unit, configured to receive activation request information sent by a client, where the activation request information carries the unique code information of the client;

a first judging unit, configured to judge whether the client is repeatedly activated according to the unique code information;

a second judging unit, configured to judge whether the client is in the factory history activation cluster when the client is repeatedly activated;

a third judging unit, configured to judge whether the client has reached a preset number of activations when the client is in the factory historical activation cluster;

The second sending unit is configured to send activation rejection information to the client when the client reaches a preset number of activations.

As a fourth aspect of the embodiments of the present invention, the embodiments of the present invention further provide a system for preventing abnormal activation of software, including a client and a server, wherein the client is the aforementioned client, and the server for the aforementioned server.

Example

1) As shown in Figure 4, the client sends activation request information to the server, and the activation request information carries the unique code information of the client, the WIFI information of the client, IP information, GPS information, etc., which can reflect the historical activation clustering of the factory. information;

2) After the server receives the activation request information, it checks whether the unique code has been authorized;

(1) If it has never been authorized, the server sends activation information to the client for activation by the client. After the activation is successful, the server records the unique code information, WIFI information, IP information, and GPS information of the activation;

(2) If authorized, do the following

①Get the historical activation information of the client, including

a) The number of historical activations of the client;

b) Clients that are normally activated are classified according to the wifi name at the time of activation;

c) Clients that are normally activated are classified according to the GPS at the time of activation;

d) Clients that are normally activated are classified according to the IP at the time of activation;

②Determination process:

(1) Whether the total number of activated clients T1 of the manufacturer meets the threshold, when the total amount is less than the threshold, it is considered that the historical statistical data is unreliable at this time, and the process (3) is directly transferred, otherwise it is transferred to the process (2)

(2) If the current client's information hits any of the categories b, c, and d, the client is in the factory history activation cluster, that is, the client is still in the factory state, go to process (3), otherwise go to process (8) ;

(3) Check whether the client is a special device (such as a development or test device, you need to import the unique code of the device in the cloud in advance, and the number of restrictions is generally very large or not limited), if it is to go to (4), otherwise go to (5)

(4) Determine whether the limit threshold of repeated activation of the test equipment is exceeded, if so, go to (6), otherwise go to (7)

(5) Check whether it exceeds the common client repeated activation limit threshold, if it exceeds the limit, go to (6), otherwise go to (7);

(6) Refuse to activate;

(7) Activation, count the number of activations;

(8) Activation, but the number of activations is not counted.

It should be noted that, unless otherwise defined, the technical or scientific terms used in one or more embodiments of the present specification shall have the usual meanings understood by those with ordinary skill in the art to which this disclosure belongs. The terms "first," "second," and similar terms used in one or more embodiments of this specification do not denote any order, quantity, or importance, but are merely used to distinguish the various components. "Comprising" or "comprising" and similar words mean that the elements or things appearing before the word encompass the elements or things recited after the word and their equivalents, but do not exclude other elements or things. Words like "connected" or "connected" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "Down", "Left", "Right", etc. are only used to indicate the relative positional relationship, and when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

It can be understood that the method can be performed by any apparatus, device, platform, or device cluster with computing and processing capabilities.

It should be noted that, the methods of one or more embodiments of this specification may be executed by a single device, such as a computer or a server. The method in this embodiment can also be applied in a distributed scenario, and is completed by the cooperation of multiple devices. In the case of such a distributed scenario, one device among the multiple devices may only execute one or more steps in the method of one or more embodiments of the present specification, and the multiple devices may perform operations on each other. interact to complete the described method.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

For the convenience of description, when describing the above device, the functions are divided into various modules and described respectively. Of course, when implementing one or more embodiments of this specification, the functions of each module may be implemented in one or more software and/or hardware.

The apparatuses in the foregoing embodiments are used to implement the corresponding methods in the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

It should be understood by those of ordinary skill in the art that the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples; under the spirit of the present disclosure, the above embodiments or Technical features in different embodiments may also be combined, steps may be carried out in any order, and there are many other variations of the different aspects of one or more embodiments of this specification as described above, which are not in detail for the sake of brevity supply.

Additionally, in order to simplify illustration and discussion, and in order not to obscure one or more embodiments of this specification, the figures provided may or may not be shown in connection with integrated circuit (IC) chips and other components. Well known power/ground connections. Furthermore, devices may be shown in block diagram form in order to avoid obscuring one or more embodiments of this description, and this also takes into account the fact that details regarding the implementation of such block diagram devices are highly dependent on the implementation of the invention (ie, these details should be well within the understanding of those skilled in the art) of the platform describing one or more embodiments. Where specific details (eg, circuits) are set forth to describe exemplary embodiments of the present disclosure, it will be apparent to those skilled in the art that these specific details may be used without or with variations One or more embodiments of this specification are implemented below. Accordingly, these descriptions are to be considered illustrative rather than restrictive.

The embodiment or embodiments of this specification are intended to cover all such alternatives, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omission, modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present specification should be included within the protection scope of the present disclosure.

Claims (10)

1. a method for preventing abnormal activation of software, is characterized in that, is applied to client, comprises: Send activation request information to the server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeated activation; if the client is repeated activation , then activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine whether the client has reached the preset number of activations ; If the client reaches a preset number of activations, then activate the server to send refusal to activate information to the client; The activation rejection information is received. 2 . The method for preventing abnormal activation of software according to claim 1 , wherein the method further comprises: after receiving activation information of the server, performing an activation operation, the activation information being that the client When the activation is not repeated, the unique code information is activated by the server and sent to the client. 3 . The method for preventing abnormal software activation according to claim 1 , wherein the method further comprises: after receiving activation information of the server, performing an activation operation, the activation information being that the client When the activation is not repeated, the unique code information is activated by the server and sent to the client. 4. A method for preventing abnormal activation of software, characterized in that, applied to a server, comprising: Receive activation request information sent by the client, where the activation request information carries the unique code information of the client; Determine whether the client is repeatedly activated according to the unique code information; If the client is repeatedly activated, determine whether the client is in the factory history activation cluster; If the client is in the factory history activation cluster, determine whether the client has reached a preset number of activations; If the client reaches a preset number of activations, send activation rejection information to the client. 5 . The method for preventing abnormal software activation according to claim 1 , wherein the method further comprises: if the client is activated repeatedly, sending activation information to the client. 6 . 6 . The method for preventing abnormal activation of software according to claim 1 , wherein the method further comprises: if the client is not in a factory historical activation cluster, sending activation information to the client. 7 . 7. A method for preventing abnormal activation of software, comprising: The client sends activation request information to the server, where the activation request information carries the unique code information of the client; The server judges whether the client is repeatedly activated according to the unique code information; If the client is repeatedly activated, the server determines whether the client is in the factory history activation cluster; If the client is in the factory history activation cluster, the server determines whether the client has reached a preset number of activations; If the client reaches a preset number of activations, the server sends activation rejection information to the client; The client terminal receives the activation rejection information, and rejects the activation operation. 8. A device for preventing abnormal activation of software, characterized in that, applied to a client, comprising: a first sending unit, configured to send activation request information to a server, where the activation request information carries the unique code information of the client; the unique code information is used to activate the server to determine whether the client is repeatedly activated; if If the client is repeatedly activated, activate the server to determine whether the client is in the factory history activation cluster; if the client is in the factory history activation cluster, activate the server to determine the client Whether the preset number of activations is reached; if the client reaches the preset number of activations, activate the server to send activation rejection information to the client; A first receiving unit, configured to receive the activation rejection information. 9. A device for preventing abnormal activation of software, characterized in that, applied to a server, comprising: a receiving unit, configured to receive activation request information sent by a client, where the activation request information carries the unique code information of the client; a first judging unit, configured to judge whether the client is repeatedly activated according to the unique code information; a second judging unit, configured to judge whether the client is in the factory history activation cluster when the client is repeatedly activated; a third judging unit, configured to judge whether the client has reached a preset number of activations when the client is in the factory historical activation cluster; The second sending unit is configured to send activation rejection information to the client when the client reaches a preset number of activations. 10 . A system for preventing abnormal activation of software, comprising a client and a server, wherein the client is the client according to claim 8 , and the server is the server according to claim 9 . 11 .

Images