CN106899571B

CN106899571B - Information interaction method and device

Info

Publication number: CN106899571B
Application number: CN201611190037.0A
Authority: CN
Inventors: 孙元博
Original assignee: Alibaba Group Holding Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2016-12-21
Filing date: 2016-12-21
Publication date: 2020-06-26
Anticipated expiration: 2036-12-21
Also published as: CN111683103B; CN106899571A; CN111683103A

Abstract

The embodiment of the application discloses an information interaction method and device. The device comprises a client and an authenticator module in a preset trusted environment, and the method comprises the following steps: the client side obtains an equipment verification identifier of the equipment, and the equipment verification identifier is obtained by the authenticator module according to hardware information of the equipment; and the client sends the equipment verification identifier to a cloud end, so that the cloud end returns an identity verification code for display of the authenticator module to the equipment after the equipment verification identifier passes verification. By utilizing the embodiment of the application, the safety of the identity verification code can be improved, and the possibility of leakage of the identity verification code is reduced.

Description

Information interaction method and device

Technical Field

The present application relates to the field of computer software technologies, and in particular, to an information interaction method and apparatus.

Background

With the development of mobile internet, the method of issuing the identity verification code through the short message service is widely applied as an auxiliary identity authentication mode.

However, some targeted attack means of the illegal person bring great threats to the security of the identity verification code, such as short message trojan, copy mobile phone cards, pseudo base stations, fishing programs and the like.

For example, an attacker may plant a short message trojan in a mobile phone of a certain user in advance, and when the mobile phone of the user receives a short message, the short message trojan automatically sends the short message to the attacker in a secret manner, so that an identity verification code included in the short message is revealed.

For another example, an attacker may copy a mobile phone card with a user by an illegal means, and may receive a short message of the user synchronously by using the copied mobile phone card, so that an authentication code included in the short message may also be revealed.

Therefore, the attack means of the illegal person brings great threat to the safety of the identity verification code issued by the short message of the mobile phone in the prior art, and the identity verification code is easy to leak.

Disclosure of Invention

The embodiment of the application provides an information interaction method and device, which are used for solving the following technical problems: the problem that the identity verification code issued by the short message of the mobile phone is easy to leak in the prior art is solved.

In order to solve the above technical problem, the embodiment of the present application is implemented as follows:

a first information interaction method provided in an embodiment of the present application, where a device includes a client and an authenticator module in a preset trusted environment, includes:

the client side obtains an equipment verification identifier of the equipment, and the equipment verification identifier is obtained by the authenticator module according to hardware information of the equipment;

and the client sends the equipment verification identifier to a cloud end, so that the cloud end returns an identity verification code for display of the authenticator module to the equipment after the equipment verification identifier passes verification.

The first information interaction device provided in the embodiment of the present application, the device includes a client and an authenticator module in a preset trusted environment, and the device is located at the client and includes:

the obtaining module is used for obtaining the equipment verification identification of the equipment, and the equipment verification identification is obtained by the authenticator module according to the hardware information of the equipment;

and the sending module is used for sending the equipment verification identifier to a cloud end, so that the cloud end returns an identity verification code used for displaying the authenticator module to the equipment after the equipment verification identifier passes verification.

In a second information interaction method provided in an embodiment of the present application, a device includes a client and an authenticator module in a preset trusted environment, and the method includes:

the authenticator module receives an identification acquisition request of the client;

the authenticator module returns an equipment verification identifier of the equipment to the client, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

and the authenticator module displays an identity verification code returned to the equipment by the cloud after the equipment verification identifier is verified by the cloud, wherein the equipment verification identifier verified by the cloud is sent to the cloud by the client.

The second kind of information interaction device that this application embodiment provided, include the client in the equipment, be in the authenticator module in the predetermined trusted environment, the device is located the authenticator module includes:

the receiving module receives an identification acquisition request of the client;

the return module returns the equipment verification identifier of the equipment to the client, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

and the display module is used for displaying an identity verification code returned by the cloud to the equipment after the equipment verification identifier is verified, wherein the equipment verification identifier verified by the cloud is sent to the cloud by the client.

In a third information interaction method provided in an embodiment of the present application, a device includes a client and an authenticator module in a preset trusted environment, and the method includes:

the cloud end obtains an equipment verification identifier of the equipment, which is sent by the client end, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

the cloud side verifies the equipment verification identification;

and after the cloud passes the verification of the equipment verification identifier, returning an identity verification code for display of the authenticator module to the equipment.

The third kind of information interaction device that this application embodiment provided contains the client in the equipment, is in the authenticator module in the predetermined trusted environment, the device is located the high in the clouds, includes:

the obtaining module is used for obtaining the equipment verification identification of the equipment sent by the client, and the equipment verification identification is obtained by the authenticator module according to the hardware information of the equipment;

the verification module is used for verifying the equipment verification identifier;

and the returning module returns the identity verification code for the display of the authenticator module to the equipment after the verification module passes the verification of the equipment verification identifier.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: the equipment can be a user terminal such as a mobile phone, the equipment is determined to be credible equipment based on the passing of verification of an equipment verification identifier obtained according to hardware information of the equipment, and an authentication code is issued to the equipment, so that attacks such as copying a mobile phone card, a pseudo base station and the like can be resisted, and besides, because the generation of the equipment verification identifier and the display of a subsequent authentication code are carried out in a credible environment in the equipment, the attacks such as a short message trojan, a fishing program and the like can be resisted. To sum up, the scheme of this application can improve the security of authentication code, reduces the possibility that the authentication code reveals, can solve the problem among the prior art partially or totally.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic flowchart of a first information interaction method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a second information interaction method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a third information interaction method according to an embodiment of the present application;

fig. 4 is a schematic view of a service architecture of the information interaction method in an actual application scenario provided in the embodiment of the present application;

fig. 5 is a schematic diagram of a technical architecture of the information interaction method in an actual application scenario provided in the embodiment of the present application;

fig. 6 is an interaction flow diagram of the information interaction method in an actual application scenario provided in the embodiment of the present application;

fig. 7 is a schematic structural diagram of an information interaction device corresponding to fig. 1 according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an information interaction device corresponding to fig. 2 according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of an information interaction device corresponding to fig. 3 according to an embodiment of the present application.

Detailed Description

The embodiment of the application provides an information interaction method and device.

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The implementation of the scheme of the present application may relate to actions of a client, an authenticator module, and a cloud, and the cloud may specifically include only one end (e.g., a message distribution server) or at least two ends (e.g., a message distribution server, a server corresponding to the client, and the like).

The client and the authenticator module may be in the same device. The client and the authenticator module are generally located in a mobile phone, a tablet computer, an intelligent wearable device, a vehicle machine and other user terminals.

The server and the message distribution server can be in different devices or in the same device. The server and the device where the message distribution server is located are generally a computer, a computer cluster, etc. serving as a server.

Unless otherwise indicated, all references to "devices" below refer to the devices where the client and authenticator modules are located.

The embodiment of the application provides three information interaction methods and devices, the three information interaction methods and devices are based on the same invention idea and correspond to each other, and are described by taking each end of a client, an authenticator module and a cloud as an execution main body.

The scheme of the present application is explained in detail below.

Fig. 1 is a flowchart illustrating a first information interaction method according to an embodiment of the present application, where the following device includes a client and an authenticator module in a preset Trusted Execution Environment (TEE). The flow in fig. 1 may be triggered to be executed in a specified manner when the authentication code needs to be acquired. For example, when the service of the client is used on the device for the first time and the device needs to be activated, or when the user switches the operation on the client of the mobile device and the corresponding client of the non-mobile device with the same account, and so on.

In the embodiment of the present application, the trusted environment is based on hardware of the device where the trusted environment is located, and the trusted environment may generally provide trusted services based on an operating system of a microkernel, and may have a variety of specific implementation manners, which is not limited in the present application. Three of these implementations are listed as examples:

firstly, both intel TXT and AMD SVM can be used for providing a trusted environment, namely, a dynamic root of trust DRTM service is provided based on a special instruction of a CPU of a processor, so that the trusted environment is realized;

secondly, a trusted environment is realized by utilizing an ARM TrustZone or TI M-Shield mechanism and a safe area/non-safe area isolation mechanism directly provided on the hardware of the central processing unit;

thirdly, a hypervisor/VMM virtualization mechanism is utilized to provide isolation between secure application and non-secure application and realize a trusted environment.

The description of the information interaction method in fig. 1 is also applicable to other information interaction methods provided in the embodiments of the present application, and will not be described again.

The execution subject of the process in fig. 1 is a client, and the process may include the following steps:

s101: and the client acquires the equipment verification identifier of the equipment, and the equipment verification identifier is acquired by the authenticator module according to the hardware information of the equipment.

In the embodiment of the present application, the client may be any client that needs to use the authentication code on the user terminal, for example, a client of a third party payment application, a client of an instant messaging application, a client of an electronic banking application, and the like.

In the embodiment of the application, the device can be distinguished from other devices according to the hardware information of the device. Taking a Mobile phone as an example, the hardware information may be an International Mobile Equipment Identity (IMEI), a physical address, and the like.

Generally, the device authentication identifier may uniquely identify the corresponding device within a certain range (e.g., a network range, a device range, a region range, etc.), and the specific range is not limited in this application and depends on the specific implementation. For example, if the scheme of the present application is implemented in a certain country, the device authentication identifier of a device in the country may be unique in the country.

In this embodiment of the present application, the device verification identifier may be generated by the authenticator module through performing a certain logic operation on hardware information of the device, and the logic operation may have a variety of specific implementation methods.

For example, the device authentication identifier may be generated by executing base64(Hash (HardID + random)), where base64 is a cryptographic algorithm, Hash represents a Hash function, HardID represents hardware information used, and random represents a random number. Since the generation process is performed in the trusted environment of the device, this approach is beneficial to improve the security of the device authentication identifier and also beneficial to prevent the hardware information from being leaked.

Of course, the authenticator module may also use the hardware information of the device directly as the device verification identifier.

In this embodiment, the client may obtain the device verification identifier returned by the authenticator module by directly or indirectly sending an identifier obtaining request to the authenticator module.

S102: and the client sends the equipment verification identifier to a cloud end, so that the cloud end returns an identity verification code for display of the authenticator module to the equipment after the equipment verification identifier passes verification.

In the embodiment of the application, the cloud terminal can determine whether the device where the client is located is a trusted device of a service provided by the client by verifying the device verification identifier, and if so, the verification is passed.

In the embodiment of the application, the cloud and the device interact with each other through the internet (IP network).

In the embodiment of the present application, the form of the authentication code may be various. For example, the authentication code may be a string of numbers (6 digits, 4 digits, etc.), a string of characters (e.g., chinese characters, english characters, or characters in other languages), a task (e.g., exchanging the 1 st character and the last character in the squared table, exchanging the 2 nd character and the 5 th character, and connecting the 3 rd character and the 8 th character with a straight line, the squared table being displayed on the interface when the user performs authentication, and the user may perform authentication according to the task content when receiving the task), and so on.

Through the method of fig. 1, the device may be a user terminal such as a mobile phone, and the device may be determined to be a trusted device based on the passing of the verification of the device verification identifier obtained according to the hardware information of the device, and then the authentication code is issued to the device, so that attacks such as copying a mobile phone card, a pseudo base station, and the like may be resisted, and furthermore, since the generation of the device verification identifier and the subsequent display of the authentication code are performed in a trusted environment in the device, attacks such as a short message trojan, a phishing program, and the like may be resisted. To sum up, the scheme of this application can improve the security of authentication code, reduces the possibility that the authentication code reveals, can solve the problem among the prior art partially or totally.

Based on the method of fig. 1, the examples of the present application also provide some specific embodiments of the method, and further embodiments, which are described below.

In this embodiment of the application, as described above, the cloud may include two ends, the message distribution server, and a server corresponding to the client. The following examples are mainly explained based on this case.

In this case, for step S102, the cloud includes a message distribution server and a server corresponding to the client;

the client sends the device verification identifier to a cloud, and specifically may include: the client sends the equipment verification identifier to the server;

the cloud returns an identity verification code used for the authenticator module display to the device after the device verification identifier passes verification, and may specifically include: and the server side calls the message distribution server to enable the message distribution server to return an identity verification code for the display of the authenticator module to the equipment after the verification of the equipment verification identifier is passed.

In this embodiment of the application, the server is a server corresponding to the client, for example, the server corresponding to the client of the payment application is the server of the payment application.

The message distribution server may be a common platform, in which case a plurality of different servers may invoke the same message distribution server. Of course, different servers may have their own exclusive message distribution server. It should be noted that the message distribution server is not a short message server of the mobile operator, so the scheme of the present application may not rely on short messages to send and receive the authentication code as in the prior art, but may transmit the authentication code based on the internet.

In the embodiment of the application, the server side can send the received device authentication identifier sent by the client side to the message distribution server by calling the message distribution server so as to request the message distribution server to authenticate the device authentication identifier. The message distribution server can determine whether the equipment where the client is located is the trusted equipment or not by verifying the equipment verification identifier, and if so, the verification is passed.

Specifically, the device verification identifier of the device may be registered in the message distribution server in advance according to a specified manner (e.g., factory preset, real-name authentication of a user, etc., binding of the device with another trusted device, etc.), and the registered device is a trusted device. In this case, the message distribution server may verify the device authentication identification in S102 by comparing the device authentication identification in S102 with the registered device authentication identification.

For example, for factory default, the device authentication identifier may be registered by the manufacturer without user intervention to determine that the hardware of the device itself is authentic. This approach emphasizes mainly "trust on hardware level".

For another example, for the user real-name authentication method, the user may register, by interacting with the corresponding server and the message distribution server, the relevant identity information (e.g., an identity card number, etc.) such as the real name of the user and the device verification identifier for the service of any client in advance, so as to determine that the device is authentic for the service and the user. This approach mainly emphasizes "trustworthiness at the business level".

In the embodiment of the present application, the authentication code may be generated by the server and/or the message distribution server. Generally, the authentication code is associated with a service of the client or the server (for example, authentication needs to be performed based on the authentication code for performing the service, or the authentication code needs to be generated based on the service-related information, etc.), and in this case, the authentication code may be preferably generated by the server, which is favorable for reducing the interference of the message distribution server with the service.

In this embodiment of the application, for step S101, the device verification identifier obtained by the client is encrypted and/or signed by the authenticator module, the encryption is performed to prevent the device verification identifier from being transmitted in a plaintext, so as to reduce a leakage risk, and the signature is performed to prevent the device verification identifier from being illegally tampered. In this case, the message distribution server needs to perform decryption processing and/or signature verification processing correspondingly subsequently to verify the device verification identifier, and the key required for the decryption processing and/or signature verification may be negotiated by the device and the message distribution server in advance.

Similarly, the authentication code returned by the message distribution server may be encrypted and/or signed.

In this embodiment of the present application, the device verification identifier may be further obtained by the authenticator module according to hardware information of the device and service information of the client, and different clients may also pre-specify different logical operation algorithms for generating the device verification identifier. Therefore, the equipment verification identification differentiation of different clients can be realized, and the equipment verification identification can also change along with the change of the same client service information, so that the safety of the equipment verification identification is improved.

In the embodiment of the present application, for the above information interaction flow, the interaction between the client and the authenticator module, and/or the interaction between the message distribution server and the device (including but not limited to the authenticator module) may be performed based on a secure channel implemented by a predetermined secure service on the device, for example, the interaction between the message distribution server and the device is performed based on a first secure channel, the interaction between the client and the authenticator module is performed based on a second secure channel, and so on.

The reason is that although the authenticator module is in a trusted environment, the client, the message distribution server are not necessarily in a trusted environment, and the secure channel with which the secure service is implemented is advantageous for reducing the risk of interaction between these several ends.

The security service may be provided by a functional module independent from the above-mentioned terminals, or may be provided by the above-mentioned terminals themselves, and the security service may include, but is not limited to, connection management, access control, session negotiation, connection heartbeat maintenance, secure tunnel, password control, and the like.

It should be noted that the secure channel may be implemented for one or more layers in an Open System Interconnection (OSI) model, and the specific implementation manners of the secure channels corresponding to different layers are different. For example, for the application layer, a secure channel may be implemented based on encryption and/or signatures; for the transport layer, a secure channel may be implemented based on TLS; for the network layer, a secure channel may be implemented based on IPSec; for the link layer, a secure channel may be implemented based on L2 TP; and so on.

Fig. 2 is a schematic flowchart of a second information interaction method according to an embodiment of the present application. The execution subject of the flow in fig. 2 is an authenticator module, and the flow may include the following steps:

s201: and the authenticator module receives an identification acquisition request of the client.

S202: and the authenticator module returns an equipment verification identifier of the equipment to the client, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment.

S203: and the authenticator module displays an identity verification code returned to the equipment by the cloud after the equipment verification identifier is verified by the cloud, wherein the equipment verification identifier verified by the cloud is sent to the cloud by the client.

Since the method in fig. 2 corresponds to the method in fig. 1, the method in fig. 2 also has the technical effect of the method in fig. 1, and based on the method in fig. 2, some specific embodiments and extension schemes of the method are also provided in the embodiments of the present application, and for the parts already described above, detailed description or simple description is not repeated below. The same is true for the latter information interaction methods, which are not described in detail.

In this embodiment of the application, the cloud may include a message distribution server and a server corresponding to the client;

the identity verification code displayed by the authenticator module is returned to the device after the message distribution server passes the verification of the device verification identifier, wherein the device verification identifier verified by the message distribution server is obtained by the client sending the device verification identifier to the server and the server calling the message distribution server.

In this embodiment of the application, for step S202, the returning, by the authenticator module, the device verification identifier of the device to the client may specifically include: the authenticator module obtains an equipment verification identifier of the equipment according to the hardware information of the equipment; the authenticator module carries out encryption processing and/or signature processing on the obtained equipment verification identifier; the authenticator module returns the encrypted and/or signed device verification identifier to the client, so that the client can send the encrypted and/or signed device verification identifier to the server.

Further, the obtaining, by the authenticator module, the device verification identifier of the device according to the hardware information of the device may specifically include: the authenticator module obtains the service information of the client; and the authenticator module obtains the equipment verification identifier of the equipment according to the hardware information and the service information of the equipment.

In this embodiment of the application, the displaying, by the authenticator module, the identity verification code returned to the device by the message distribution server after the verification of the device verification identifier is passed may specifically include: the authenticator module obtains an identity verification code returned to the equipment by the message distribution server after the equipment verification identifier is verified; the authenticator module generating a trusted interface, the trusted interface being within the trusted environment; the authenticator module presents the identity verification code in the trusted interface.

Under the condition of displaying the trusted interface, because the isolation and the safety characteristics of the trusted environment can not allow other processes to run or only allow a specified process to run, the information displayed in the trusted interface can be prevented from being stolen by malicious programs such as short messages trojans, phishing programs and the like.

In this embodiment of the present application, the authentication code obtained by the authenticator module may be encrypted and/or signed by the message distribution server; similarly, before the authenticator module presents the authentication code in the trusted interface, the authenticator module may further perform: and the authenticator module is used for carrying out decryption processing and/or signature verification processing on the identity verification code subjected to encryption processing and/or signature processing.

In this embodiment of the present application, the interaction between the message distribution server and the device is performed based on a first secure channel, where the first secure channel is implemented by a predetermined secure service on the device; and/or the interaction between the client and the authenticator module is based on a second secure channel, wherein the second secure channel is realized by a predetermined secure service on the device.

In an embodiment of the present application, the device may include a user terminal.

Fig. 3 is a flowchart illustrating a third information interaction method according to an embodiment of the present application. The execution subject of the process in fig. 3 is a cloud, and the process may include the following steps:

s301: and the cloud end obtains an equipment verification identifier of the equipment, which is sent by the client end, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment.

S302: and the cloud terminal verifies the equipment verification identifier.

S303: and after the cloud passes the verification of the equipment verification identifier, returning an identity verification code for display of the authenticator module to the equipment.

In this embodiment of the application, the cloud may include a message distribution server and a server corresponding to the client; in this case, for step S301, the obtaining, by the cloud, the device verification identifier of the device sent by the client may specifically include: the server side obtains a device verification identifier of the device sent by the client side;

for step S302, the cloud verifies the device verification identifier, which may specifically include: the server side sends the equipment verification identification to the information distribution server by calling the information distribution server, and the information distribution server verifies the received equipment verification identification;

for step S303, after the cloud passes the verification of the device verification identifier, the cloud returns an identity verification code for display by the authenticator module to the device, which may specifically include: and after the verification of the equipment verification identifier is passed, the message distribution server returns an identity verification code for displaying by the authenticator module to the equipment.

In this embodiment of the present application, the device verification identifier sent by the client is encrypted and/or signed by the authenticator module; and/or the authentication code returned by the message distribution server is encrypted and/or signed.

In the embodiment of the present application, it has been mentioned above that the message may preferably be generated by the server. In this case, after the sending the device authentication identifier to the message distribution server, the following may be further performed: the server generates the identity verification code after the message distribution server passes the verification of the equipment verification identifier; and the server side sends the authentication code to the message distribution server so that the message distribution server can return the authentication code to the equipment.

In this embodiment of the present application, the device verification identifier received by the message distribution server may be encrypted and/or signed by the authenticator module; in this case, before the message distribution server verifies the device verification identifier, the following may be further performed: and the message distribution server carries out decryption processing and/or signature verification processing on the encrypted and/or signed device verification identification.

In this embodiment of the application, the returning, by the message distribution server, the identity verification code for the authenticator module display to the device may specifically include: the message distribution server sends a notification message indicating that the equipment verification identifier is verified to the server side; the message distribution server receives the identity verification code generated and returned by the server; the message distribution server returns the authentication code to the device for presentation by the authenticator module.

In this embodiment of the application, the returning, by the message distribution server, the identity verification code to the device may specifically include: the message distribution server carries out encryption processing and/or signature processing on the identity verification code; and the message distribution server returns the encrypted and/or signed identity verification code to the equipment for the authenticator module to display after decryption and/or signature verification.

In this embodiment of the present application, the interaction between the message distribution server and the device may be performed based on a first secure channel, where the first secure channel is implemented by a predetermined secure service on the device; and/or the interaction between the client and the authenticator module may be based on a second secure channel implemented by a predetermined secure service on the device.

The information interaction method provided by the embodiment of the present application is described above with each terminal as an execution subject. For convenience of understanding, an embodiment of the present application further provides a specific implementation of the information interaction method in an actual application scenario, which is described below with reference to fig. 4, fig. 5, and fig. 6.

Fig. 4 is a schematic view of a service architecture of the information interaction method in an actual application scenario provided in the embodiment of the present application.

In fig. 4, "trusted interface + device authentication identifier" is one of the key parts of the device where the client is located in relation to the scheme of the present application, and the secure channel may be implemented based on the above-mentioned security service. Each service provider has its corresponding service end and corresponding client end, and each service provider can issue a message such as an identity verification code to the client end through the message distribution server, provided that the message distribution server passes verification of the device authentication identifier of the device where the client end is located. In fig. 4, the interaction between the three parties is based on the internet, and does not need to rely on the network of the mobile operator and the short message platform, which is beneficial to flexibly using various security policies to improve the security of the service architecture, and the trusted interface in the service architecture is safer than the short message interface in the prior art.

Fig. 5 is a schematic diagram of a technical architecture of the information interaction method in an actual application scenario provided in the embodiment of the present application.

In fig. 5, the following functions (which may correspond to corresponding functional modules) may be mainly implemented for the device where the client is located.

Connection management: the system is responsible for the creation, management and maintenance of network socket connection;

and session negotiation: negotiating with a message distribution server when socket connection is established, and acquiring a secret key of the session;

heartbeat maintenance: maintenance to maintain long connections (e.g., long connections that can be established between a security service and a message distribution server);

a trusted interface: the safety interface is drawn according to the requirements of the background operation center, and can be a six-digit password display interface or other interfaces;

and (3) protocol assembly: assembling data according to the service requirement, safely encrypting, decrypting and signing, and packaging in a network layer;

protocol analysis: analyzing a packet of a network layer and analyzing a service data packet;

acquiring equipment data: collecting: trusted data of the equipment where the client is located;

device key: the client side is arranged in the factory when the equipment leaves the factory, and a signature interface is provided;

device ID: the device module generates a unique ID (for example, the device authentication identifier) of the service based on the hardware ID and returns the unique ID;

encryption and decryption: and a key algorithm module.

In fig. 5, a message distribution server is shown for the cloud, and the message distribution server mainly can implement the following functions (which may correspond to respective functional modules).

Connection management: the server is responsible for managing and maintaining the connection of the message distribution server;

and session negotiation: generating and managing a session key according to negotiation with equipment where a client is located, and simultaneously ensuring maintenance of a session and connection;

heartbeat maintenance: ensuring long connection;

and (3) protocol assembly: assembling a data packet of a network layer and packaging a service;

protocol analysis: assembling a data packet of a network layer and analyzing the service;

device ID management: inquiring, discarding and increasing the equipment ID;

device key management: inquiring, discarding and increasing the device key;

equipment risk management: forming equipment risk management according to the data acquired by the equipment;

and (3) access control: and controlling the access of the server call.

The center of the template: message content formation and presentation

The operation center: and managing and operating the messages.

Fig. 6 is an interaction flow diagram of the information interaction method in an actual application scenario provided in the embodiment of the present application.

In fig. 6, the untrusted environment and the trusted environment are located on the device, the security service is implemented by a designated function module, the authenticator module is located in the trusted environment, and the authenticator module at least includes two sub-modules of "trusted logic processing" and "trusted interface display". The security service maintains a long connection with the message distribution server through heartbeat.

When the service provided by the client is used on the equipment for the first time, the execution of the subsequent flow is triggered by activating the operation of the equipment. The client side obtains an equipment verification identifier through the security service, wherein the equipment verification identifier is generated by executing 'execute base64(Hash (HardID + random))' through the trusted logic processing module according to the hardware information of the equipment, and is signed by adopting a private key of the equipment and then returned to the client side through the security service.

The client sends the obtained signed equipment verification identifier to the server for requesting verification, and the server calls the message distribution server to request the message distribution server to verify the signed equipment verification identifier received from the client.

The message distribution server verifies whether the signature of the currently obtained device verification identifier is legal or not by using data (such as a public key, hardware information, a device verification identifier and the like) of the device obtained in advance, and determines whether the device is a trusted device or not.

And after the equipment verification identifier is verified by the message distribution server, the signed message is sent to the security service, and the security service transmits the message to the trusted logic processing module.

And the trusted logic processing module verifies the signature of the message to ensure the message to be trusted, and after the verification is passed, the trusted interface display module is called to generate a trusted interface to display the message.

The information interaction method provided in the embodiment of the present application is described above, and based on the same inventive concept, the embodiment of the present application further provides a corresponding apparatus, as shown in fig. 7, fig. 8, and fig. 9.

Fig. 7 is a schematic structural diagram of an information interaction apparatus corresponding to fig. 1 according to an embodiment of the present application, where the apparatus includes a client and an authenticator module in a preset trusted environment, and the apparatus is located at the client and includes:

an obtaining module 701, configured to obtain an apparatus verification identifier of the apparatus, where the apparatus verification identifier is obtained by the authenticator module according to hardware information of the apparatus;

the sending module 702 sends the device verification identifier to a cloud, so that the cloud returns an identity verification code for display by the authenticator module to the device after the device verification identifier passes verification.

Optionally, the cloud includes a message distribution server and a server corresponding to the client;

the sending module 702 sends the device verification identifier to a cloud, and specifically includes:

the sending module 702 sends the device authentication identifier to the server;

the cloud returns an identity verification code used for the authenticator module display to the device after the device verification identifier passes verification, and specifically includes:

and the server side calls the message distribution server to enable the message distribution server to return an identity verification code for the display of the authenticator module to the equipment after the verification of the equipment verification identifier is passed.

Optionally, the device verification identifier obtained by the client is encrypted and/or signed by the authenticator module; and/or the presence of a gas in the gas,

the authentication code returned by the message distribution server is encrypted and/or signed.

Optionally, the device verification identifier is obtained by the authenticator module according to hardware information of the device and service information of the client.

Optionally, the interaction between the message distribution server and the device is performed based on a first secure channel, where the first secure channel is implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

the interaction between the client and the authenticator module is based on a second secure channel implemented by a predetermined security service on the device.

Optionally, the device comprises a user terminal.

Fig. 8 is a schematic structural diagram of an information interaction apparatus corresponding to fig. 2 according to an embodiment of the present application, where the apparatus includes a client and an authenticator module in a preset trusted environment, and the apparatus is located in the authenticator module, and includes:

a receiving module 801, which receives an identifier obtaining request of the client;

a returning module 802, configured to return an equipment verification identifier of the equipment to the client, where the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

the display module 803 displays an authentication code returned by the cloud to the device after the device authentication identifier is verified by the cloud, wherein the device authentication identifier verified by the cloud is sent to the cloud by the client.

Optionally, the returning module 802 returns the device verification identifier of the device to the client, which specifically includes:

the returning module 802 obtains the device authentication identifier of the device according to the hardware information of the device, performs encryption processing and/or signature processing on the obtained device authentication identifier, and returns the device authentication identifier subjected to encryption processing and/or signature processing to the client, so that the client sends the device authentication identifier subjected to encryption processing and/or signature processing to the server.

Optionally, the returning module 802 obtains the device verification identifier of the device according to the hardware information of the device, and specifically includes:

the return module 802 obtains the service information of the client, and obtains the device authentication identifier of the device according to the hardware information of the device and the service information.

Optionally, the displaying module 803 displays an authentication code returned by the cloud to the device after the verification of the device authentication identifier is passed, which specifically includes:

the displaying module 803 obtains an authentication code returned to the device by the message distribution server after the device authentication identifier is verified, and generates a trusted interface, where the trusted interface is in the trusted environment and displays the authentication code in the trusted interface.

Optionally, the identity verification code obtained by the authenticator module is encrypted and/or signed by the message distribution server;

before the identity verification code is displayed in the trusted interface, the display module 803 performs decryption processing and/or signature verification processing on the identity verification code subjected to encryption processing and/or signature processing.

Optionally, the device comprises a user terminal.

Fig. 9 is a schematic structural diagram of an information interaction apparatus corresponding to fig. 3 according to an embodiment of the present application, where the device includes a client and an authenticator module in a preset trusted environment, and the apparatus is located in a cloud, and includes:

an obtaining module 901, configured to obtain a device verification identifier of the device sent by the client, where the device verification identifier is obtained by the authenticator module according to hardware information of the device;

a verification module 902, configured to verify the device verification identifier;

and a returning module 903, configured to return an identity verification code for the authenticator module to the device after the verification module 902 verifies the device verification identifier.

Optionally, the apparatus comprises: the message distribution server and the server corresponding to the client; the obtaining module 901 is located at the server, and the verifying module 902 and the returning module 903 are located at the message distribution server;

the obtaining module 901 obtains the device verification identifier of the device sent by the client, specifically including:

the server side obtains a device verification identifier of the device sent by the client side;

the verifying module 902 verifies the device verification identifier, which specifically includes:

the server side calls the message distribution server to send the equipment verification identifier to the message distribution server;

the message distribution server verifies the received equipment verification identification;

the returning module 903 returns the identity verification code for the authenticator module to the device after the verification module 902 verifies the device verification identifier, and specifically includes:

and after the verification of the equipment verification identifier is passed, the message distribution server returns an identity verification code for displaying by the authenticator module to the equipment.

Optionally, the device verification identifier sent by the client is encrypted and/or signed by the authenticator module; and/or the presence of a gas in the gas,

Optionally, the server side calls a message distribution server, sends the device authentication identifier to the message distribution server, generates the authentication code after the message distribution server passes the device authentication identifier authentication, and sends the message to the message distribution server, so that the message distribution server returns the authentication code to the device.

Optionally, the device verification identifier received by the message distribution server is encrypted and/or signed by the authenticator module;

before the message distribution server verifies the equipment verification identifier, the encrypted and/or signed equipment verification identifier is decrypted and/or signed and verified.

Optionally, the returning, by the message distribution server, the authentication code to the device specifically includes:

and the message distribution server sends a notification message indicating that the equipment verification identifier is verified to pass to the server, receives an identity verification code generated and returned by the server, and returns the identity verification code to the equipment for the display of the authenticator module.

and the message distribution server encrypts and/or signs the identity verification code, and returns the encrypted and/or signed identity verification code to the equipment for display after decryption and/or signature verification by the authenticator module.

Optionally, the device comprises a user terminal.

The device and the method provided by the embodiment of the application are in one-to-one correspondence, so the device also has the beneficial technical effects similar to the corresponding method, and the beneficial technical effects of the method are explained in detail above, so the beneficial technical effects of the corresponding device are not described again.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment or the system embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to part of the description of the method embodiment for relevant points.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An information interaction method is characterized in that equipment comprises a client and an authenticator module in a preset trusted environment, and the method comprises the following steps:

the client side sends the equipment verification identification to a cloud side based on the internet, so that the cloud side returns an identity verification code used for displaying the authenticator module to the equipment based on the internet after the equipment verification identification is verified to pass.

2. The method of claim 1, wherein the cloud comprises a message distribution server, a server corresponding to the client;

the client sends the device verification identifier to a cloud, and specifically includes:

the client sends the equipment verification identifier to the server;

3. The method of claim 2, wherein the device verification identification obtained by the client is cryptographically and/or signed by the authenticator module; and/or the presence of a gas in the gas,

4. The method of claim 1, wherein the device verification identification is derived by the authenticator module from hardware information of the device and service information of the client.

5. The method of claim 2, wherein the interaction between the message distribution server and the device is based on a first secure channel, the first secure channel being implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

6. The method of any of claims 1 to 5, wherein the device comprises a user terminal.

7. An information interaction method is characterized in that equipment comprises a client and an authenticator module in a preset trusted environment, and the method comprises the following steps:

the authenticator module displays an identity verification code returned by the cloud to the equipment based on the internet after the equipment verification identifier is verified by the cloud, wherein the equipment verification identifier verified by the cloud is sent to the cloud by the client based on the internet.

8. The method of claim 7, wherein the cloud comprises a message distribution server, a server corresponding to the client;

9. The method of claim 8, wherein the authenticator module returning the device verification identifier of the device to the client specifically comprises:

the authenticator module obtains an equipment verification identifier of the equipment according to the hardware information of the equipment;

the authenticator module carries out encryption processing and/or signature processing on the obtained equipment verification identifier;

the authenticator module returns the encrypted and/or signed device verification identifier to the client, so that the client can send the encrypted and/or signed device verification identifier to the server.

10. The method of claim 7, wherein the obtaining, by the authenticator module, the device verification identifier of the device according to the hardware information of the device specifically comprises:

the authenticator module obtains the service information of the client;

and the authenticator module obtains the equipment verification identifier of the equipment according to the hardware information and the service information of the equipment.

11. The method of claim 8, wherein the authenticator module exposes the authentication code returned by the cloud to the device after the device authentication identifier is verified, and specifically comprises:

the authenticator module obtains an identity verification code returned to the equipment by the message distribution server after the equipment verification identifier is verified;

the authenticator module generating a trusted interface, the trusted interface being within the trusted environment;

the authenticator module presents the identity verification code in the trusted interface.

12. The method according to claim 11, wherein the authentication code obtained by the authenticator module is encrypted and/or signed by the message distribution server;

before the authenticator module displays the authentication code in the trusted interface, the method further comprises:

and the authenticator module is used for carrying out decryption processing and/or signature verification processing on the identity verification code subjected to encryption processing and/or signature processing.

13. The method of claim 8, wherein the interaction between the message distribution server and the device is based on a first secure channel, the first secure channel being implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

14. The method of any of claims 7 to 13, wherein the device comprises a user terminal.

15. An information interaction method is characterized in that equipment comprises a client and an authenticator module in a preset trusted environment, and the method comprises the following steps:

the cloud end obtains an equipment verification identifier of the equipment, which is sent by the client based on the Internet, wherein the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

the cloud side verifies the equipment verification identification;

and after the cloud passes the verification of the equipment verification identifier, returning an identity verification code for display of the authenticator module to the equipment based on the Internet.

16. The method of claim 15, wherein the cloud comprises a message distribution server, a server corresponding to the client;

the cloud obtains the device verification identifier of the device sent by the client, and specifically includes:

the cloud verifies the device verification identifier, and specifically includes:

17. The method of claim 16, wherein the device verification identifier sent by the client is cryptographically and/or signed by the authenticator module; and/or the presence of a gas in the gas,

18. The method of claim 16, wherein after the server sends the device authentication identifier to the message distribution server by invoking the message distribution server, the method further comprises:

the server generates the identity verification code after the message distribution server passes the verification of the equipment verification identifier;

and the server side sends the authentication code to the message distribution server so that the message distribution server can return the authentication code to the equipment.

19. The method according to claim 16, wherein the device verification identifier received by the message distribution server is cryptographically processed and/or signed processed by the authenticator module;

before the message distribution server verifies the device verification identifier, the method further includes:

and the message distribution server carries out decryption processing and/or signature verification processing on the encrypted and/or signed device verification identification.

20. The method according to claim 16, wherein the message distribution server returning to the device an authentication code for presentation by the authenticator module specifically comprises:

the message distribution server sends a notification message indicating that the equipment verification identifier is verified to the server side;

the message distribution server receives the identity verification code generated and returned by the server;

the message distribution server returns the authentication code to the device for presentation by the authenticator module.

21. The method of claim 16, wherein the message distribution server returning the authentication code to the device specifically comprises:

the message distribution server carries out encryption processing and/or signature processing on the identity verification code;

and the message distribution server returns the encrypted and/or signed identity verification code to the equipment for the authenticator module to display after decryption and/or signature verification.

22. The method of claim 16, wherein the interaction between the message distribution server and the device is based on a first secure channel, the first secure channel being implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

23. The method of any one of claims 15 to 22, wherein the device comprises a user terminal.

24. An information interaction device, wherein a device includes a client and an authenticator module in a preset trusted environment, the device is located at the client, and the device comprises:

and the sending module is used for sending the equipment verification identifier to a cloud end based on the Internet, so that the cloud end returns an identity verification code used for displaying the authenticator module to the equipment based on the Internet after the equipment verification identifier passes verification.

25. The apparatus of claim 24, wherein the cloud comprises a message distribution server, a server corresponding to the client;

the sending module sends the device verification identifier to a cloud, and specifically includes:

the sending module sends the equipment verification identifier to the server;

26. The apparatus of claim 25, wherein the device verification identification obtained by the client is cryptographically and/or signed by the authenticator module; and/or the presence of a gas in the gas,

27. The apparatus of claim 24, wherein the device verification identification is derived by the authenticator module from hardware information of the device and service information of the client.

28. The apparatus of claim 25, wherein the interaction between the message distribution server and the device is based on a first secure channel implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

29. The apparatus of any one of claims 24 to 28, wherein the device comprises a user terminal.

30. An information interaction device, wherein a device includes a client and an authenticator module in a preset trusted environment, and the device is located in the authenticator module, and comprises:

and the display module is used for displaying an identity verification code returned to the equipment by the cloud based on the Internet after the equipment verification identifier is verified, wherein the equipment verification identifier verified by the cloud is sent to the cloud by the client based on the Internet.

31. The apparatus of claim 30, wherein the cloud comprises a message distribution server, a server corresponding to the client;

32. The apparatus of claim 31, wherein the returning module returns the device authentication identifier of the device to the client, specifically comprising:

the return module obtains the equipment verification identifier of the equipment according to the hardware information of the equipment, encrypts and/or signs the obtained equipment verification identifier, and returns the encrypted and/or signed equipment verification identifier to the client, so that the client can send the encrypted and/or signed equipment verification identifier to the server.

33. The apparatus according to claim 30, wherein the returning module obtains the device authentication identifier of the device according to the hardware information of the device, specifically including:

and the return module acquires the service information of the client and acquires the equipment verification identifier of the equipment according to the hardware information of the equipment and the service information.

34. The apparatus of claim 31, wherein the displaying module displays an authentication code returned by the cloud to the device after the device authentication identifier is verified, specifically including:

and the display module acquires an identity verification code returned to the equipment by the message distribution server after the equipment verification identifier passes verification, and generates a trusted interface, wherein the trusted interface is in the trusted environment, and the identity verification code is displayed in the trusted interface.

35. The apparatus of claim 34, wherein the authentication code obtained by the authenticator module is cryptographically processed and/or signed processed by the message distribution server;

before the identity verification code is displayed in the trusted interface, the display module carries out decryption processing and/or signature verification processing on the identity verification code which is subjected to encryption processing and/or signature processing.

36. The apparatus of claim 31, wherein the interaction between the message distribution server and the device is based on a first secure channel implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

37. The apparatus of any one of claims 30 to 36, wherein the device comprises a user terminal.

38. An information interaction device, characterized in that, the device includes a client, an authenticator module in a preset trusted environment, the device is located in the cloud, and the device includes:

the obtaining module is used for obtaining an equipment verification identifier of the equipment, which is sent by the client based on the Internet, and the equipment verification identifier is obtained by the authenticator module according to the hardware information of the equipment;

and the returning module returns the identity verification code for the display of the authenticator module to the equipment based on the Internet after the verification module passes the verification of the equipment verification identifier.

39. The apparatus of claim 38, wherein the apparatus comprises: the message distribution server and the server corresponding to the client; the obtaining module is located at the server side, and the verifying module and the returning module are located at the message distribution server;

the obtaining module obtains the device verification identifier of the device sent by the client, and specifically includes:

the verifying module verifies the device verification identifier, and specifically includes:

the returning module returns the identity verification code for the authenticator module display to the device after the verification module passes the verification of the device verification identifier, and specifically includes:

40. The apparatus of claim 39, wherein the device verification identifier sent by the client is cryptographically and/or signed by the authenticator module; and/or the presence of a gas in the gas,

41. The apparatus of claim 39, wherein the server side generates the authentication code after the message distribution server passes the device authentication identifier verification after calling the message distribution server to send the device authentication identifier to the message distribution server, and sends the authentication code to the message distribution server, so that the message distribution server returns the authentication code to the device.

42. The apparatus of claim 39, wherein the device verification identifier received by the message distribution server is cryptographically processed and/or signed by the authenticator module;

43. The apparatus according to claim 39, wherein the message distribution server returns the authentication code to the device, specifically comprising:

44. The apparatus according to claim 39, wherein the message distribution server returns the authentication code to the device, specifically comprising:

45. The apparatus of claim 39, wherein interaction between the message distribution server and the device is based on a first secure channel implemented by a predetermined secure service on the device; and/or the presence of a gas in the gas,

46. The apparatus of any one of claims 38 to 45, wherein the device comprises a user terminal.