WO2018033017A1

WO2018033017A1 - Terminal state conversion method and system for credit granting

Info

Publication number: WO2018033017A1
Application number: PCT/CN2017/096835
Authority: WO
Inventors: 陈菲菲
Original assignee: 福建联迪商用设备有限公司
Priority date: 2016-08-18
Filing date: 2017-08-10
Publication date: 2018-02-22
Also published as: CN106161036B; CN106161036A

Abstract

A terminal state conversion method and system for credit granting in the present invention relate to the technical field of communications. The terminal state conversion method for credit granting comprises: a server side sends first to-be-authenticated data to a state conversion tool; the state conversion tool encrypts the first to-be-authenticated data to generate first authentication data; the server authenticates the first authentication data; a terminal sends second to-be-authenticated second data to the state conversion tool; the state conversion tool encrypts the second to-be-authenticated data to generate second authentication data; and the terminal authenticates the second authentication data.

Description

Terminal state transition method and system for credit

Technical field

The present invention relates to the field of communications technologies, and in particular, to a terminal state transition method and system for granting credit.

Background technique

In the field of financial payment, in order to ensure the legitimacy of the program on the terminal device, the terminal needs to introduce a digital signature scheme, and the root public key certificate is preset in the terminal, and only the program using the private key corresponding to the work public key certificate of the root public key certificate can be downloaded. To the terminal. When the terminal is in normal use, the program downloaded to the terminal must be signed, which is greatly inconvenient for application developer debugging. In order to facilitate application developer debugging, the terminal has a debugging state, and the application can be downloaded to the terminal without signing.

Summary of the invention

Therefore, it is necessary to provide a terminal state transition method for crediting, which is used to solve the problem of debugging the debugging state and the usage state of the terminal. After the application developer uses the state transition tool to perform the mutual authentication of the server and the terminal, the terminal can be switched. The state is convenient and safe.

In order to achieve the above object, the inventor provides a method for terminal state transition of a credit, and the technical solution is as follows:

A method for transferring terminal state transitions includes the steps of:

The server sends the first to-be-certified data to the state conversion tool, and the state transition tool obtains the work public key certificate and the work private key from the U-KEY; the state transition tool uses the work private key to perform the first to-be-certified data. Encrypting, generating first authentication data, the state conversion tool sends the working public key certificate and the first authentication data to the server; the server authenticates the first authentication data; and the terminal sends the second to-be-authenticated data to the state conversion tool ; the state conversion tool uses the work private key Encrypting the second to-be-certified data to generate second authentication data, the state conversion tool sends the working public key certificate and the second authentication data to the terminal; the terminal authenticates the second authentication data; After the authentication data is authenticated and the terminal authenticates the second authentication data, the state transition tool obtains the data to be authenticated from the terminal, and the state transition tool sends the data to be authenticated to the server; the server uses the authentication private key to perform the data to be authenticated. Encrypted to generate authentication data, the server sends the authentication data to the state transition tool, and the state transition tool sends the authentication data to the terminal; the terminal authenticates the authentication data, and if the authentication passes, the terminal state is converted.

Further, the server authenticates the first authentication data, including the steps: the server receives the working public key certificate, and the server extracts the public key in the working public key certificate, and the server uses the public key to The first authentication data is decrypted, and the plaintext of the data to be authenticated in the first authentication data is obtained, and the plaintext of the data to be authenticated in the first authentication data is consistent with the data to be authenticated. The terminal authenticates the second authentication data, including the steps: the terminal receives the working public key certificate, the terminal extracts the public key in the working public key certificate, and the terminal uses the public key to perform the second authentication data. Decrypting, obtaining the plaintext of the data to be authenticated in the second authentication data, and comparing whether the plaintext of the data to be authenticated in the second authentication data is consistent with the data to be authenticated, and if the matching is the same, the authentication is passed.

Further, the terminal state includes a usage state and a debug state, and the terminal does not save the application and the key in the usage state and the debug state; the terminal switches from the usage state to the debug state, and the terminal clears the key of the terminal in the usage state. The terminal switches from the debug state to the use state, and the terminal clears the application and the key of the terminal in the debug state.

Further, the first to-be-certified data is a random number, and the second to-be-certified data is a combination of a terminal board serial number and a random number.

The beneficial effects of the present invention are: the application developer obtains the work public key certificate and the work private key of the U-KEY through the state transition tool, and when the state transition tool obtains the authentication of the server and the terminal, the state transition tool can be directly used. To switch the state of the terminal; and the state conversion tool used by the application developer stores the work public key certificate of the terminal root public key certificate and the corresponding private The key signature ensures that the application developer has the authority to download the program to the terminal to avoid illegally changing the terminal status.

In order to achieve the above object, the inventor also provides a terminal state transition system for crediting, and the technical solution is as follows:

A trusted terminal state transition system includes: a server, a terminal, and a state transition tool, and the state transition tool includes: a server authentication module, a terminal authentication module, and a U-KEY interaction module; the server is configured to: send The first to-be-certified data is sent to the state transition tool, and the state transition tool obtains the working public key certificate and the working private key from the U-KEY; the U-KEY interaction module is configured to: use the working private key to the first The server to be authenticated is encrypted to generate the first authentication data. The server authentication module is configured to: send the working public key certificate and the first authentication data to the server; the server is used to: The data is used for authentication; the terminal is configured to: send the second to-be-certified data to the state conversion tool; the U-KEY interaction module is configured to: encrypt the second to-be-certified data by using the working private key, to generate a second authentication The terminal authentication module is configured to: send the working public key certificate and the second authentication data to the terminal; the terminal is configured to: authenticate the second authentication data; The first authentication data is authenticated and the terminal authenticates the second authentication data, and the terminal authentication module is configured to: obtain data to be authenticated from the terminal; the server authentication module is configured to: send the data to be authenticated to the server The server is further configured to: use the authentication private key to encrypt the to-be-authenticated data to generate authentication data, and the server sends the authentication data to the state conversion tool; the terminal authentication module is further configured to: send the authentication The terminal is further configured to: authenticate the authentication data, and if the authentication passes, convert the terminal status.

Further, the server is configured to: authenticate the first authentication data, and the method includes: the server receives the working public key certificate, and the server extracts the public key in the working public key certificate, and the server uses the public The key decrypts the first authentication data, and obtains the plaintext of the data to be authenticated in the first authentication data, and compares whether the plaintext of the data to be authenticated in the first authentication data is consistent with the data to be authenticated. If the agreement is the same, the authentication is passed; the terminal is configured to: identify the second authentication data. And the terminal receives the working public key certificate, the terminal extracts the public key in the working public key certificate, and the terminal decrypts the second authentication data by using the public key to obtain the second authentication data. Whether the plaintext of the data to be authenticated and the data to be authenticated in the second authentication data are consistent with each other, and if the data is consistent, the authentication is passed.

The beneficial effects of the present invention are: the application developer obtains the work public key certificate and the work private key of the U-KEY through the state transition tool, and when the state transition tool obtains the authentication of the server and the terminal, the state transition tool can be directly used. To switch the state of the terminal; and the state conversion tool used by the application developer stores the work public key certificate and the corresponding private key signature of the terminal root public key certificate, so as to ensure that the application developer has the right to download the program to the terminal. To avoid illegal conversion of terminal status.

DRAWINGS

1 is a block diagram of a trusted terminal state transition system of the present invention;

2 is a flow chart of a method for converting a terminal state of a credit according to the present invention.

Description of the reference signs:

10, the server,

20, the terminal,

30, state transition tool,

40, U-KEY,

301, a server authentication module,

302, terminal authentication module,

303, U-KEY interaction module,

401, work public key certificate,

402, work private key.

detailed description

The detailed description of the technical content, structural features, and the objects and effects of the technical solutions will be described in detail below with reference to the specific embodiments and the accompanying drawings.

Referring to FIG. 2, in the embodiment, the U-KEY is inserted in the state transition tool. In this embodiment, the state transition tool is a PC, where the U-KEY stores the work public key subordinate to the terminal root public key certificate. The certificate and the work private key. When the U-KEY is inserted into the state transition tool, the state transition tool is installed with interactive software, so that the state transition tool can obtain the work public key certificate and the work private key from the U-KEY.

The specific implementation steps are as follows:

Step S201: The state transition tool obtains the first data to be authenticated from the server. First, the server generates the first data to be authenticated. In this embodiment, the first data to be authenticated is a 16-byte random number, and the state transition tool goes to the slave service. The terminal obtains the first data to be authenticated, and after obtaining the state, the state conversion tool sends the first data to be authenticated to the state conversion tool.

In other embodiments, the first to-be-authenticated data may also be a random number of other bytes, which may be a combination of 32-byte letters, numbers, special symbols, etc., in this embodiment, by generating 16-byte random each time. The number ensures that the random number generated each time is different.

Then in step S202: the state transition tool generates the first authentication data by using the U-KEY; after the state transition tool receives the first data to be authenticated, the state transition tool uses the work private key stored in the U-KEY to pair the first data to be authenticated. Encryption is performed, and the first authentication data is generated after encryption. The first authentication data is ensured by encrypting the first data to be authenticated by using the work private key stored in the U-KEY. In the process of data transmission, it will not be intercepted by other illegal U-KEYs, and it will pretend to be a genuine U-KEY, which will cause security problems.

After the first authentication data is generated, the step S203: the state conversion tool sends the first authentication data and the working public key certificate to the server for authentication; the authentication here means that the server decrypts the received first authentication data. Obtaining plaintext, whether the plaintext is the same as the first data to be authenticated on the server. If they are the same, the U-KEY passes the authentication of the server and obtains the approval of the server. The U-KEY can obtain information from the server and give The server sends permission to send information. The work public key certificate sent here contains a public key that can decrypt the first authentication data, so that the public key can be extracted after the server receives the message, and then the first authentication data is decrypted. For example, the first data to be authenticated is: D1, which is encrypted by using the private key S to generate the first authentication data: D2, the public key corresponding to the private key S is G, and the state conversion tool sends the certificate of D2 and G to the certificate. On the server side, the server extracts G from the certificate, and then uses G to decrypt D2 and obtain D1.

Step S204: The state transition tool acquires the second data to be authenticated from the terminal. Similarly, the terminal generates the second data to be authenticated. In this embodiment, the second data to be authenticated is a combination of the serial number of the terminal motherboard and the random number. The motherboard serial number is unique and can uniquely identify a terminal. After the terminal generates the second to-be-certified data, the state transition tool obtains the second to-be-certified data.

In step S205: the state transition tool generates the second authentication data using the U-KEY; the state transition tool encrypts the second data to be authenticated using the working private key in the U-KEY to generate the second authentication data. By encrypting the first to-be-authenticated data by using the working private key stored in the U-KEY, it is ensured that the generated second authentication data is not intercepted by other illegal U-KEYs during the data transmission process, and the impersonation is truly legal. U-KEY, causing security issues.

After the second authentication data is generated, the step S206: the state conversion tool sends the second authentication data and the working public key certificate to the terminal for authentication; the authentication here refers to the terminal decrypting the received second authentication data to obtain the plaintext. Whether the comparison plaintext is the same as the second to-be-certified data of the terminal. If the same, the U-KEY passes the authentication of the terminal, and the terminal is recognized, and the U-KEY obtains the information that can be obtained from the terminal and sends the information to the terminal. permission. The work sent here The public key certificate contains a public key that can decrypt the second authentication data, so that the public key can be extracted after the server receives the message, and then the second authentication data is decrypted.

Step S207: The server verifies the first authentication data authentication and the terminal to the second authentication number authentication; the server receives the working public key certificate, and the server extracts the public key in the working public key certificate, and the server uses the public key. The public key decrypts the first authentication data, and obtains the plaintext of the data to be authenticated in the first authentication data, and compares the plaintext of the data to be authenticated in the first authentication data with the first data to be authenticated. Whether it is consistent, if it is consistent, the certification is passed.

Receiving, by the terminal, the working public key certificate, the terminal extracting the public key in the working public key certificate, the terminal decrypting the second authentication data by using the public key, and acquiring the data to be authenticated in the second authentication data The plaintext compares whether the plaintext of the data to be authenticated in the second authentication data is consistent with the data to be authenticated, and if yes, the authentication passes.

Through the authentication of the U-KEY by the server and the authentication of the U-KEY by the terminal, when both are authenticated, it means that the legality of the U-KEY is recognized by the server and the terminal, then we will The holder of the U-KEY is allowed to obtain the data to be authenticated from the terminal by using the state transition tool, and the data is sent to the server, and the server encrypts the authentication data by using the authentication private key, generates authentication data, and sends the authentication data to the terminal through the state conversion tool. The terminal authenticates it. If the authentication passes, it means that the server also passes the terminal's approval. Then the holder of the U-KEY approved by the server has the authority to use the state transition tool to legalize the state of the terminal. Ground conversion, to avoid illegal conversion, and after U-KEY through the server and terminal authentication, the subsequent steps can be completed automatically, greatly improving the speed of conversion, greatly facilitating the debugging of application developers. In step S208: the state transition tool sends the state to be converted to the terminal, and the terminal switches the state. The state transition tool obtains the terminal information and the data to be authenticated from the terminal, where the terminal information refers to the terminal serial number, and the data to be authenticated is the serial number of the motherboard and the random number, wherein the serial number of the motherboard of each terminal is unique, in this implementation In the example, the random number is a 16-byte random number. In other embodiments, the random number may be a letter or a character of other digits. The uniqueness of the data to be authenticated is ensured by using a combination of the motherboard serial number and the random number having the uniquely identified terminal.

The state transition tool sends this data to the server. The server authenticates the terminal information and generates authentication data. After the server obtains the terminal information, it determines the legality of the terminal information, and determines that it is legal. The server then uses the authentication private key to encrypt the authentication data. Authenticate data and send the authentication data to the state transition tool.

In this embodiment, because the security requirements are relatively high, because the public key used by each terminal is different, when the server judges the terminal information, it not only judges its legitimacy, but also according to The terminal information encrypts the authentication data using a private key corresponding to the terminal. By using the private key to encrypt the authentication data, it is ensured that the generated authentication data is not intercepted by other illegal persons in the process of data transmission, and it is impersonated as a legitimate server to deceive the terminal and cause security problems.

In some other embodiments, the public key used by each terminal is the same for convenience and versatility, so the server only needs to judge the legitimacy of the terminal information, and the server uses the universal private key. Encrypt the authentication data.

The state conversion tool sends the authentication data to the terminal, and the terminal decrypts the authentication data by using the public key. Because the server uses the private key corresponding to the terminal to encrypt the authentication data, the terminal can decrypt successfully, and after the decryption succeeds, It is judged whether the serial number of the motherboard in the decrypted data is the serial number of the motherboard of the terminal, and if yes, the authentication is passed. After the authentication is passed, the state transition tool sends the state to be converted to the terminal, and the terminal switches to the corresponding state. In this embodiment, in order to ensure security, after the terminal transitions from the debug state to the use state, the application and the key on the device are all cleared; similarly, the terminal is dense from the use state to the debug state. The keys will also be cleared completely.

In some embodiments, when the terminal transitions from the usage state to the debug state, security is ensured in order to prevent the user from entering a personal PIN on it. The interface of the debug state is obviously different from the state of use. In the debug state, a warning box or a watermark pops up every few seconds to prompt the user that the terminal is in the debug state, so that the user does not input the personal PIN on the terminal.

Referring to FIG. 1, in some embodiments, a scheme of a trusted terminal state transition system of the present invention is as follows:

The system includes a server 10, a terminal 20, and a state transition tool 30. The U-KEY 40 is inserted in the state transition tool 30. In this embodiment, the state transition tool 30 is a PC, and the terminal root is stored in the U-KEY 40. The public key certificate 401 and the work private key 402 of the key certificate are installed. After the U-KEY 40 is inserted into the state transition tool 30, the state transition tool 30 is installed with interactive software, so that the state transition tool has a U-KEY interaction module 303. The state transition tool 30 further includes: a server authentication module 301 and a terminal authentication module 302. The terminal authentication module 302 is mainly used to obtain information from the terminal 20 and send information to the terminal 20. The server authentication module 301 is mainly used to Information is obtained from the server 10 and sent to the server 10.

details as follows:

The server authentication module 301 is configured to: obtain the first data to be authenticated from the server 10; first, the server 10 generates the first data to be authenticated by itself. In this embodiment, the first data to be authenticated is a 16-byte random number, and the server authenticates. The module 301 then obtains the first data to be authenticated from the server 10, and after obtaining the data, the server authentication module 301 sends the first data to be authenticated to the U-KEY interaction module 303.

The U-KEY interaction module 303 is configured to: use the U-KEY 40 to generate the first authentication data; after the U-KEY interaction module 303 receives the first to-be-authenticated data, the U-KEY interaction module 303 uses the working private key stored in the U-KEY 40. 402 encrypts the first to-be-certified data, and generates the first authentication data after encryption.

After the first authentication data is generated, the server authentication module 301 is configured to: send the first authentication data and the working public key certificate 401 to the server 10 for authentication; wherein the working public key certificate 401 sent here can be decrypted. The public key of the authentication data is for facilitating the server 10 to extract the public key after receiving it, and then decrypting the first authentication data.

The terminal authentication module 302 is configured to: acquire the second data to be authenticated from the terminal 20; similarly, the terminal 20 generates the second data to be authenticated. In this embodiment, the second data to be authenticated is a combination of the terminal serial number and the random number. The serial number of the terminal board on the side is unique and can uniquely identify a terminal. After the terminal 20 generates the second data to be authenticated, the terminal authentication module 302 obtains the second data to be authenticated, and the terminal authentication module 302 sends the second data to be authenticated to the U-KEY interaction module 303.

The U-KEY interaction module 303 is configured to: generate the second authentication data by using the U-KEY 40; the U-KEY interaction module 303 encrypts the second to-be-authenticated data by using the working private key in the U-KEY 40 to generate the second authentication data, and generate After the second authentication data.

The terminal authentication module 302 is configured to: send the second authentication data and the working public key certificate 401 to the terminal 20 for authentication; wherein the working public key certificate 401 sent here contains a public key that can decrypt the second authentication data, in order to It is convenient for the server 10 to extract the public key after receiving it, and then decrypt the second authentication data.

The server 10 passes the first authentication data authentication and the terminal 20 and the second authentication number authentication. The server 10 is further configured to: receive the working public key certificate 401, and the server 10 extracts the working public key certificate 401. The public key, the server 10 decrypts the first authentication data by using the public key, and obtains the plaintext of the data to be authenticated in the first authentication data, and compares the plaintext of the data to be authenticated in the first authentication data. Whether it is consistent with the first data to be authenticated, and if the data is consistent, the authentication is passed;

The terminal 20 is further configured to: receive the working public key certificate 401, the terminal 20 extracts the public key in the working public key certificate 401, and the terminal 20 decrypts the second authentication data by using the public key to obtain the The plaintext of the data to be authenticated in the second authentication data is compared with whether the plaintext of the data to be authenticated in the second authentication data is consistent with the data to be authenticated.

Both of them are verified, which means that the legality of the U-KEY 40 is recognized by the server 10 and the terminal 20, then we allow the holder of the U-KEY 40 to use the state transition tool 30 from the server 10 Acquiring authentication data for authentication of the terminal 20;

The terminal authentication module 302 is configured to: send a state to be converted to the terminal 20, and the terminal 20 switches states. The terminal authentication module 302 obtains terminal information and data to be authenticated from the terminal 20, where the terminal information refers to a terminal serial number, and the data to be authenticated is a serial number of the motherboard and a random number, wherein the serial number of the motherboard of each terminal 20 is unique. In this embodiment, the random number is a 16-byte random number. In other embodiments, the random number may be a letter or a character of other digits.

The server authentication module 301 is configured to: send the data to the server 10.

The server 10 is configured to: authenticate the terminal information and generate the authentication data; after the server 10 obtains the terminal information, determine the legality of the terminal information, and determine that it is legal, the server 10 treats the authentication private key again. The authentication data is encrypted, the authentication data is generated, and the authentication data is sent to the server authentication module 301.

In this embodiment, for the sake of high security requirements, since the public key used by each terminal 20 is different, when the server 10 judges the terminal information, it not only judges its legality, but also The authentication data is also encrypted using the private key corresponding to the terminal 20 based on the terminal information.

In some other embodiments, the public key used by each terminal 20 is the same for convenience and versatility, so the server 10 only needs to judge the legitimacy of the terminal information, and the server 10 uses the universal The private key encrypts the authentication data.

The terminal authentication module 302 is configured to: send the authentication data to the terminal 20.

The terminal 20 is further configured to: use the public key to decrypt the authentication data, because the server 10 uses the private key corresponding to the terminal 20 to encrypt the authentication data, so the terminal 20 can decrypt successfully, and after decryption succeeds, the decryption is determined. Whether the serial number of the motherboard in the data is the serial number of the motherboard of the terminal 20, and if so, the authentication is passed.

After the authentication is passed, the terminal authentication module 302 is further configured to: send the status to be converted to the terminal 20, and the terminal 20 switches to the corresponding status. In this embodiment, in order to ensure security, after the terminal 20 transitions from the debug state to the use state, the application program and the key on the device are all cleared; similarly, the terminal 20 is from the use state to the debug state, on the device. The keys will also be cleared.

In some embodiments, when the terminal 20 transitions from the usage state to the debug state, security is ensured in order to prevent the user from entering a personal PIN thereon. The interface of the debug state is obviously different from the state of use. In the debug state, a warning box or a watermark pops up every few seconds to prompt the user that the terminal is in the debug state, so that the user does not enter the personal PIN on the terminal 20. .

It should be noted that, in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply such entities or operations. There is any such actual relationship or order between them. Furthermore, the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Other elements that are included, or include elements inherent to such a process, method, article, or terminal device. An element defined by the phrase "including" or "comprising" does not exclude the presence of additional elements in the process, method, article or terminal device including the element. In addition, in this document, “greater than”, “less than”, “exceeded”, etc. are understood as not including the number; “above”, “below”, “inside”, etc. are understood to include the number.

Those skilled in the art will appreciate that the various embodiments described above can be provided as a method, apparatus, or computer program product. These embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects. All or part of the steps involved in the foregoing embodiments may be completed by a program instructing related hardware, and the program may be stored in a storage medium readable by a computer device for executing the method embodiments of the foregoing embodiments. All or part of the steps described. The computer device includes but is not limited to: a personal computer, a server, a general purpose computer, a special purpose computer, a network device, an embedded device, a programmable device, a smart mobile terminal, a smart home device, a wearable smart device, a vehicle smart device, and the like; The storage medium includes, but is not limited to, a RAM, a ROM, a magnetic disk, a magnetic tape, an optical disk, a flash memory, a USB flash drive, a mobile hard disk, a memory card, a memory stick, a network server storage, a network cloud storage, and the like.

The above embodiments are described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to the embodiments. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. The computer program instructions can be provided to a processor of the computer device to generate a machine such that instructions executed by the processor of the computer device are generated for implementation in the stream A device that is a process or a plurality of processes and/or a block diagram of a function specified in a block or blocks.

The computer program instructions can also be stored in a computer device readable memory that can direct the computer device to operate in a particular manner, such that instructions stored in the computer device readable memory produce an article of manufacture comprising the instruction device, the instruction device being implemented in the process Figure One or more processes and/or block diagrams of the functions specified in a block or blocks.

These computer program instructions can also be loaded onto a computer device such that a series of operational steps are performed on the computer device to produce computer-implemented processing, such that instructions executed on the computer device are provided for implementing one or more processes in the flowchart And/or block diagram of the steps of a function specified in a box or blocks.

Although the above embodiments have been described, those skilled in the art can make other changes and modifications to these embodiments once they have learned the basic inventive concept, so the above is only the implementation of the present invention. For example, the scope of the patent protection of the present invention is not limited thereto, and equivalent structural or equivalent process transformations made by using the description of the present invention and the contents of the drawings, or directly or indirectly applied to other related technical fields, are equally included in the present invention. Within the scope of patent protection of the invention.

Claims

A method for transferring terminal state transitions, comprising the steps of:

The server sends the first to-be-certified data to the state transition tool, and the state transition tool obtains the working public key certificate and the work private key from the U-KEY;

The state transition tool encrypts the first to-be-certified data by using the working private key to generate first authentication data, and the state transition tool sends the working public key certificate and the first authentication data to the server;

The server authenticates the first authentication data;

The terminal sends the second to-be-certified data to the state transition tool;

The state conversion tool encrypts the second to-be-certified data by using the working private key to generate second authentication data, and the state conversion tool sends the working public key certificate and the second authentication data to the terminal;

The terminal authenticates the second authentication data;

If the server authenticates the first authentication data and the terminal authenticates the second authentication data, the state transition tool obtains the data to be authenticated from the terminal, and the state transition tool sends the data to be authenticated to the server.

The server uses the authentication private key to encrypt the data to be authenticated to generate authentication data, and the server sends the authentication data to the state conversion tool, and the state conversion tool sends the authentication data to the terminal.

The terminal authenticates the authentication data, and if the authentication passes, the terminal status is converted.
A method for converting a terminal state of a credit according to claim 1, wherein:

The server authenticates the first authentication data, including the steps:

The server receives the working public key certificate, and the server extracts the public key in the working public key certificate, and the server decrypts the first authentication data by using the public key to obtain the first authentication data. Whether the plaintext of the data to be authenticated is the same as the data to be authenticated in the first authentication data, and if the data is consistent, the authentication is passed;

The terminal authenticates the second authentication data, including the steps:

The terminal receives the working public key certificate, the terminal extracts the public key in the working public key certificate, and the terminal decrypts the second authentication data by using the public key to obtain the second authentication data. Whether the plaintext of the data to be authenticated is the same as the data to be authenticated in the second authentication data, and if the data is consistent, the authentication is passed.
A method for converting a terminal state of a credit according to claim 1, wherein:

The terminal status includes a usage state and a debug state, and the terminal does not save the application and the key in the usage state and the debug state;

The terminal switches from the use state to the debug state, and the terminal clears the key of the terminal in the use state;

The terminal switches from the debug state to the use state, and the terminal clears the application and the key of the terminal in the debug state.
A method for converting a terminal state of a credit according to claim 1, wherein:

The first to-be-certified data is a random number, and the second to-be-certified data is a combination of a terminal board serial number and a random number.
A trusted terminal state transition system, comprising: a server, a terminal, and a state transition tool, wherein the state transition tool comprises: a server authentication module, a terminal authentication module, and a U-KEY interaction module;

The server is configured to: send a first to-be-certified data to a state transition tool, where the state transition tool obtains a working public key certificate and a work private key from the U-KEY;

The U-KEY interaction module is configured to: encrypt the first to-be-certified data by using the working private key to generate first authentication data;

The server authentication module is configured to: send the working public key certificate and the first authentication data to a server;

The server is configured to: authenticate the first authentication data;

The terminal is configured to: send a second to-be-certified data to a state transition tool;

The U-KEY interaction module is configured to: encrypt the second to-be-certified data by using the working private key, to generate second authentication data;

The terminal authentication module is configured to: send the working public key certificate and the second authentication data to the terminal;

The terminal is configured to: authenticate the second authentication data;

If the server authenticates the first authentication data and the terminal authenticates the second authentication data, the terminal authentication module is configured to: obtain data to be authenticated from the terminal;

The server authentication module is configured to: send the data to be authenticated to a server;

The server is further configured to: use the authentication private key to encrypt the to-be-authenticated data to generate authentication data, and the server sends the authentication data to the state transition tool;

The terminal authentication module is further configured to: send the authentication data to the terminal;

The terminal is further configured to: authenticate the authentication data, and if the authentication passes, convert the terminal status.
A trusted terminal state transition system according to claim 5, wherein

The server is configured to: authenticate the first authentication data, including:

The server receives the working public key certificate, and the server extracts the public key in the working public key certificate, and the server decrypts the first authentication data by using the public key to obtain the first authentication data. Whether the plaintext of the data to be authenticated is the same as the data to be authenticated in the first authentication data, and if the data is consistent, the authentication is passed;

The terminal is configured to: authenticate the second authentication data, including:

Receiving, by the terminal, the working public key certificate, the terminal extracting the public key in the working public key certificate, the terminal decrypting the second authentication data by using the public key, and acquiring the data to be authenticated in the second authentication data The plaintext compares whether the plaintext of the data to be authenticated in the second authentication data is consistent with the data to be authenticated, and if yes, the authentication passes.
A trusted terminal state transition system according to claim 5, wherein

The terminal status includes a usage state and a debug state, and the terminal does not save the application and the key in the usage state and the debug state;

The terminal switches from the use state to the debug state, and the terminal clears the key of the terminal in the use state;

The terminal switches from the debug state to the use state, and the terminal clears the application and the key of the terminal in the debug state.
A trusted terminal state transition system according to claim 5, wherein

The first to-be-certified data is a random number, and the second to-be-certified data is a combination of a terminal board serial number and a random number.