US 2026/0205266 A1Published application

Secure two-way authentication method and system

AssigneeShenzhen Topwise Communication Co., Ltd.

InventorsSHAOBIAN WANG, XIAOLING WANG, WEIDE ZENG

Life of this patent

Estimating the term…

Loading patent…

Abstract

A secure two-way authentication method and system are provided. In this method, a web front-end sends a request to control an android terminal to an SRS server. When receiving the request, the android terminal generates a key pair and encrypts a public key before sending it to the SRS server. After receiving the request again and a user agrees, an SP security chip generates a 32-bit random number as a control token and sends it to the SRS server. The server saves this random number and waits for an opcode. The web front-end obtains screen recording information and generates the opcode to send to the SRS server, the server encrypts it, and sends it together with the opcode to the android terminal. The android terminal uses the private key to decrypt data, verifies whether the random number is matched, and executes the opcode.

Claims2

Dependent claims

A secure two-way authentication method, comprising:

sending a control request to a Simple Realtime Server, (SRS) server through a Message Queuing Telemetry Transport, (MQTT) protocol, by a web front-end, requesting an establishment of control over an android terminal;
when the android terminal receives the control request for a first time, automatically generating an Rivest-Shamir-Adleman, (RSA)3 public-private key pair, by a Security Chip, (SP) security chip of the android terminal, encrypting the RSA3 public key using the RSA2 private key, and sending it to the SRS server;
wherein the android terminal is provided with the SP security chip, RSA2 public key, and RSA2 private key;
decrypting the RSA3 public key data encrypted by the android terminal using the RSA2 private key through the RSA2 public key, by the SRS server, obtaining the RSA3 public key, and waiting for a user to confirm a connection request;
the SRS server comprises a built-in RSA1 private key and RSA1 public key;
after the user confirming the request, generating a 32-bit random number, by the SP security chip of the android terminal, encrypting the 32-bit random number using the RSA1 public key of the SRS server, and sending it to the SRS server;
decrypting and saving the 32-bit random number as a verification token using the RSA1 private key, by the SRS server;
obtaining a screen recording permission, by the android terminal, and transmitting a screen recording interface in real-time to the web front-end of the SRS server through Web Real-Time Communications, (WebRTC) technology;
generating an operation instruction code, by the web front-end, and sending it to the SRS server;
filling in the 32-bit random number, by the SRS server, and encrypting the operation instruction code and the 32-bit random number using the RSA3 public key;
sending encrypted data packet to the android terminal;
decrypting received data packet using the RSA3 private key in the SP security chip, by the android terminal, and verifying whether the 32-bit random number is correct;
when the verification passes, executing an operation in the operation instruction code, by the android terminal.

10 more elements

A system for remote desktop control of an android device based on security control, comprising:

a web front-end, an SRS server, and an android terminal, wherein the android terminal is provided with an SP security chip, an RSA2 public key, and a RSA2 private key;
the SRS server comprises a built-in RSA1 private key and a RSA1 public key;
the web front-end sends a control request to the SRS server through a MQTT protocol, requests an establishment of control over the android terminal;
when the android terminal receives the control request for a first time, the SP security chip automatically generates an RSA3 public-private key pair, encrypts the RSA3 public key using the RSA2 private key, and sends it to the SRS server;
the SRS server decrypts the RSA3 public key data encrypted by the Android terminal using the RSA2 private key through the RSA2 public key, obtains the RSA3 public key, and waits for a user to confirm a connection request;
after the user confirms the request, the SP security chip of the Android terminal generates a 32-bit random number, encrypts the 32-bit random number using the RSA1 public key of the SRS server, and sends it to the SRS server;
the SRS server decrypts and saves the 32-bit random number as a verification token using the RSA1 private key;
the android terminal obtains a screen recording permission and transmits a screen recording interface in real-time to the web front-end of SRS server through WebRTC technology;
the web front-end generates an operation instruction code and sends it to the SRS server;
the SRS server fills in the 32-bit random number and encrypts the operation instruction code and the 32-bit random number using the RSA3 public key;
encrypted data packet is then sent to the android terminal;
the android terminal decrypts received data packet using the RSA3 private key in the SP security chip, and verifies whether the 32-bit random number is correct;
when the verification passes, the android terminal executes an operation in the operation instruction code.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 19/307,812Filed 22 Aug 2025
Priority: CN 202510045675.613 Jan 2025
Published: 16 Jul 2026
Term ends: Not estimatedThe source records don’t support an estimate.

Classification8 codes

H04L 9/0819
Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for…:…
H04L 9/0825
Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely…: using…
H04L 9/0869
Generation of secret information including derivation or calculation of cryptographic keys or passwords: involving random numbers or seeds
H04L 9/3213
Involving a third party or a trusted authority: using tickets or tokens, e.g. Kerberos