A privacy protection method and device for smart devices

By generating and verifying communication keys in smart devices, the problem of data leakage after the loss of smart devices is solved, and secure encrypted data transmission and privacy protection are achieved.

CN116418500BActive Publication Date: 2026-11-17BEIJING SUPERHEXA CENTURY TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211196740.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-29
Publication Date
2026-11-17
Estimated Expiration
2042-09-29

AI Technical Summary

Technical Problem

When smart devices are lost, users' private data is easily leaked, and existing technologies are insufficient to effectively improve privacy protection.

Method used

By downloading the smart device's application, a binding request is sent to the server, and a communication key is generated using a random number and a public key to ensure secure binding between the smart device and the target device and achieve encrypted data transmission.

Benefits of technology

Effectively ensure data security, prevent data leakage, and enhance privacy protection capabilities after smart devices are lost.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116418500B_ABST
    Figure CN116418500B_ABST
Patent Text Reader

Abstract

This invention provides a privacy protection method and apparatus for smart devices. The method includes: downloading an application for the smart device; sending a binding request to the smart device through the application; sending a smart device identifier and a first random number returned by the smart device to a server; transmitting a server signature, a second random number, and a server public key returned by the server to the smart device; transmitting a smart device signature and a smart device public key returned by the smart device based on the server signature, the second random number, and the server public key to the server; transmitting a server token and a server modulus value returned by the server based on the received smart device signature and smart device public key to the smart device; and determining the server token or smart device token as the communication key between the target device and the smart device based on the smart device private key and the smart device modulus value obtained from the server public key. This can improve the privacy protection of smart devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of information security technology, and more specifically, to a method and apparatus for protecting the privacy of smart devices. Background Technology

[0002] With the rapid development of internet technology, the application of smart devices linked to mobile devices is becoming increasingly widespread. For example, glasses cameras have functions such as taking photos and videos. By linking them to a mobile device, files taken with the glasses camera can be transferred to the mobile device. Before using a smart device, users need to download the smart device operator's application (App), register in the App, and link the smart device. Since the data involved in taking photos and videos is considered user privacy data, the loss of a smart device can easily lead to data leakage. Therefore, how to improve the privacy protection of smart devices has become a hot topic of concern. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a method and apparatus for protecting the privacy of smart devices, so as to improve the privacy protection of smart devices.

[0004] In a first aspect, embodiments of the present invention provide a privacy protection method for smart devices, including:

[0005] Download the application for the smart device, and send a binding request to the smart device through the application;

[0006] The smart device is sent to the server based on the smart device identifier returned by the binding request and the first random number;

[0007] The server-side signature, the second random number, and the server-side public key returned by the server are transmitted to the smart device. The server-side signature is generated based on the smart device identifier and the first random number.

[0008] The smart device transmits the smart device signature and smart device public key returned by the server based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number.

[0009] The server transmits the server-side token and the server-side modulo value back to the smart device based on the received smart device signature, the smart device public key, and the server-side modulo value.

[0010] Based on the smart device's private key and the server's public key, the smart device's modulus value is obtained, and the server's token or the smart device token is determined as the communication key between the target device and the smart device.

[0011] In conjunction with the first aspect, embodiments of the present invention provide a first possible implementation of the first aspect, wherein sending a binding request to the smart device through the application includes:

[0012] Register within the application;

[0013] Log in to the application and scan to obtain the smart device identifier and the first digital binding code of the smart device;

[0014] The target device sends a binding code acquisition request to a server pre-configured for the application, and the binding code acquisition request carries the smart device identifier.

[0015] The target device obtains the second digital binding code returned by the server. The second digital binding code is generated by the server based on the smart device identifier and the smart device public key corresponding to the smart device that is pre-stored.

[0016] If the first digital binding code is the same as the second digital binding code, a binding request is sent to the smart device.

[0017] In conjunction with the first aspect, embodiments of the present invention provide a second possible implementation of the first aspect, wherein transmitting the server-side signature, the second random number, and the server-side public key returned by the server to the smart device includes:

[0018] The server receives the smart device identifier and the first random number, and generates a server-side key pair.

[0019] Generate a server-side signature based on the first random number and the server-side key pair;

[0020] Generate a second random number, and transmit the server-side signature, the second random number, and the server-side public key of the server-side key pair to the smart device through the target device.

[0021] In conjunction with the first aspect, embodiments of the present invention provide a third possible implementation of the first aspect, wherein transmitting the smart device signature and smart device public key returned by the smart device based on the received server-side signature, the second random number, and the server-side public key to the server includes:

[0022] Verify the received server-side signature using the smart device's public key;

[0023] After the signature verification is successful on the server side, a smart device token is obtained based on the smart device private key and the server public key of the smart device key pair.

[0024] Perform a modulo operation on the smart device token to obtain the smart device modulo value;

[0025] Calculate the smart device signature based on the smart device's private key and the second random number;

[0026] The smart device signature and the smart device public key are returned to the server via the target device.

[0027] In conjunction with the third possible implementation of the first aspect, this embodiment of the invention provides a fourth possible implementation of the first aspect, wherein transmitting the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device includes:

[0028] The server uses its public key to verify the smart device's signature.

[0029] Obtain the server-side token based on the smart device's public key and the server's private key;

[0030] Perform a modulo operation on the server-side token to obtain the server-side modulo value;

[0031] The target device transmits the server-side token and server-side modulo value to the smart device.

[0032] In conjunction with the first aspect and any of the first to fourth possible implementations of the first aspect, embodiments of the present invention provide a fifth possible implementation of the first aspect, which further includes:

[0033] The server uses a server-side token to encrypt the smart device identifier, obtains encrypted data, and sends it to the smart device through the target device.

[0034] The smart device uses the smart device token to decrypt encrypted data to obtain the smart device identifier, which is then compared with the stored smart device identifier. If they match, the communication key is confirmed to be valid.

[0035] In conjunction with the first aspect and any of the first to fourth possible implementations of the first aspect, this embodiment of the invention provides a sixth possible implementation of the first aspect, which further includes:

[0036] The WiFi password retrieval request is encrypted using a communication key and then sent to the smart device;

[0037] The smart device uses a communication key to decrypt the encrypted WiFi password retrieval request, uses the communication key to encrypt the WiFi password, and transmits the encrypted WiFi password to the target device.

[0038] The target device uses the communication key to decrypt the encrypted WiFi password and obtain the WiFi password.

[0039] Secondly, embodiments of the present invention also provide a privacy protection device for a smart device, comprising:

[0040] The download module is used to download the application for the smart device and send a binding request to the smart device through the application.

[0041] The first transmission module is used to send the smart device identifier returned by the smart device according to the binding request and the first random number to the server.

[0042] The second transmission module is used to transmit the server-side signature, the second random number, and the server-side public key returned by the server to the smart device. The server-side signature is generated based on the smart device identifier and the first random number.

[0043] The third transmission module is used to transmit the smart device signature and smart device public key returned by the smart device based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number.

[0044] The fourth transmission module is used to transmit the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device.

[0045] The communication key determination module is used to determine the server-side token or the smart device token as the communication key between the target device and the smart device based on the smart device's private key and the server-side public key, and the smart device's modulus value.

[0046] Thirdly, embodiments of this application provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0047] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described method.

[0048] The privacy protection method and apparatus for smart devices provided in this invention involve: downloading an application for the smart device; sending a binding request to the smart device through the application; sending the smart device identifier and a first random number returned by the smart device based on the binding request to a server; transmitting a server-side signature, a second random number, and a server-side public key returned by the server to the smart device, wherein the server-side signature is generated based on the smart device identifier and the first random number; transmitting a smart device signature and a smart device public key returned by the smart device based on the received server-side signature, the second random number, and the server-side public key to the server, wherein the smart device signature is generated based on the smart device private key and the second random number; transmitting a server-side token and a server-side modulus value returned by the server based on the received smart device signature and smart device public key to the smart device; and determining the server-side token or the smart device token as the communication key between the target device and the smart device based on the smart device private key and the smart device modulus value obtained from the server-side public key. By associating smart devices with their corresponding apps and setting communication keys for data transmission, data security can be effectively guaranteed even if the smart device is lost, thereby enhancing the privacy and security of the smart device.

[0049] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0050] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 This invention illustrates a schematic flowchart of a privacy protection method for smart devices provided in an embodiment of the present invention.

[0052] Figure 2 A schematic diagram of the privacy protection device structure of the smart device provided in an embodiment of the present invention is shown;

[0053] Figure 3 This is a schematic diagram of the structure of a computer device 300 provided in an embodiment of this application. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0055] This invention provides a method and apparatus for protecting the privacy of smart devices, which are described below through embodiments.

[0056] Figure 1 A schematic flowchart of a privacy protection method for smart devices provided in an embodiment of the present invention is shown. Figure 1 As shown, the method includes:

[0057] Step 101: Download the application for the smart device and send a binding request to the smart device through the application;

[0058] In this embodiment of the invention, an application is downloaded using a target device. As an optional embodiment, the target device includes, but is not limited to, mobile devices, tablets, etc. Taking a mobile device as an example, the user uses a mobile device, such as a mobile phone, to download the app corresponding to the smart device and begin the smart device binding process.

[0059] In this embodiment of the invention, as an optional embodiment, sending a binding request to the smart device through the application includes:

[0060] A11, register in the application;

[0061] In this embodiment of the invention, a username and password are registered for the smart device in the application.

[0062] A12, Log in to the application and scan to obtain the smart device identifier and the first digital binding code of the smart device;

[0063] In this embodiment of the invention, the mobile device or smart device uses a Bluetooth channel to search for nearby devices, from which the user selects the smart device or mobile device to be bound. The smart device identifier is pre-set during the production of the smart device, and the first digital binding code is generated by the smart device based on the smart device identifier and a pre-stored smart device public key.

[0064] In this embodiment of the invention, during the production of the smart device, a smart device identifier is pre-generated, namely, a smart device ID (did), a smart device private key (pri_d), and a smart device public key (pub_d). The smart device private key (pri_d) and the smart device public key (pub_d) form a smart device key pair. As an optional embodiment, the smart device public key and smart device private key are generated using the Elliptic Curve Cryptography (ECC) 256 algorithm.

[0065] In this embodiment of the invention, the private key of the smart device is written to the Android secure area of ​​the smart device. Key operations can be performed in the Android secure area, but it is not visible to the outside world. The server-side public key (pub_s) is obtained from the server. The smart device ID and the server-side public key (pub_s) are stored in the immutable area of ​​the smart device, and the smart device ID and the smart device public key are uploaded to the server.

[0066] A13, the target device sends a binding code acquisition request to a server pre-configured for the application, the binding code acquisition request carrying the smart device identifier;

[0067] A14, the target device obtains the second digital binding code returned by the server, the second digital binding code is generated by the server based on the smart device identifier and the smart device public key corresponding to the smart device that is pre-stored;

[0068] A15, if the first digital binding code is the same as the second digital binding code, send a binding request to the smart device.

[0069] In this embodiment of the invention, as an optional implementation, the first digital binding code is a 6-digit code. Verification is performed using the 6-digit codes of both the smart device and the mobile phone. If the codes match, the smart device and mobile phone can be bound. For example, after downloading an app, based on the smart device identifier entered or scanned in the app, an interaction is performed with the server to generate a second digital binding code. This second code is compared with the first digital binding code generated by the smart device. If they match, binding can proceed; otherwise, the process terminates.

[0070] In this embodiment of the invention, the mobile phone's App receives a click instruction from the binding control and sends a binding request (binding_start) to the smart device.

[0071] Step 102: The smart device is sent to the server based on the smart device identifier returned by the binding request and the first random number;

[0072] In this embodiment of the invention, the smart device receives a binding request (binding_start), generates a first random number (random_d), and returns the smart device ID (did) and the generated first random number (random_d) to the App; the App requests the server, passing the smart device ID (did) and the generated first random number (random_d) in the request.

[0073] Step 103: Transmit the server signature, the second random number, and the server public key returned by the server to the smart device. The server signature is generated based on the smart device identifier and the first random number.

[0074] In this embodiment of the invention, as an optional embodiment, transmitting the server-side signature, the second random number, and the server-side public key returned by the server to the smart device includes:

[0075] B11, The server receives the smart device identifier and the first random number, generates a server-side key pair, and generates a server-side signature based on the first random number and the server-side key pair;

[0076] In this embodiment of the invention, after receiving the smart device identifier, the server generates a server-side key pair. As an optional embodiment, the server-side key pair includes a server-side public key and a server-side private key. As another optional embodiment, the server-side key pair is a server-side ECC256 key pair, where the server-side private key is a server-side ECC256 private key (pri_s_t) and the server-side public key is a server-side ECC256 public key (pub_s_t).

[0077] In this embodiment of the invention, as an optional embodiment, the Advanced Encryption Standard 256 (AES256) symmetric key algorithm of the Hardware Security Module (HSM) is used to encrypt and store the ECC256 private key on the server side.

[0078] B12, based on the first random number and the server-side ECC256 private key of the server-side key pair, generate the server-side signature;

[0079] In this embodiment of the invention, the server-side signature (sign_s) is calculated using the following formula:

[0080] sign_s=SHA256(pri_s_t,random_d).

[0081] B13 generates a second random number, and transmits the server-side signature, the second random number, and the server-side public key of the server-side key pair to the smart device through the target device.

[0082] In this embodiment of the invention, the server generates a second random number and a server-side ECC256 public key, and returns the server-side signature (sign_s), the second random number (random_s), and the server-side ECC256 public key (pub_s_t) to the smart device through the App.

[0083] Step 104: The smart device transmits the smart device signature and smart device public key returned by the server based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number.

[0084] In this embodiment of the invention, as an optional embodiment, the smart device transmits the smart device signature and smart device public key returned by the smart device based on the received server-side signature, the second random number, and the server-side public key to the server, including:

[0085] C11 uses the smart device's public key to verify the received server-side signature;

[0086] In this embodiment of the invention, the public key (pub_s) of the smart device is used to verify the received server-side signature (sign_s).

[0087] C12, after the signature verification is successful on the server side, obtains the smart device token based on the smart device private key and the server public key of the smart device key pair;

[0088] In this embodiment of the invention, as an optional embodiment, a smart device token is obtained based on the smart device private key and the server-side public key of the smart device key pair, including:

[0089] The Elliptic Curve Diffie–Hellman Key Exchange (ECDH) algorithm is used to perform calculations on the smart device private key and the server public key of the smart device key pair to obtain the smart device token.

[0090] In this embodiment of the invention, the smart device token (token_key) is calculated using the following formula:

[0091] token_key=ECDH(pub_s_t,pri_d).

[0092] C13 performs a modulo operation on the smart device token to obtain the smart device modulo value;

[0093] In this embodiment of the invention, the smart device modulus (oob) is calculated using the following formula:

[0094] oob=SHA256(token_key)mod 10^6;

[0095] C14, calculate the smart device signature based on the smart device's private key and the second random number;

[0096] In this embodiment of the invention, as an optional embodiment, the smart device signature is calculated using the following formula:

[0097] sign_d=SHA256(pri_d,random_s).

[0098] C15 returns the smart device signature and the smart device public key to the server via the target device.

[0099] In this embodiment of the invention, the smart device signature (sign_d) and the smart device public key (pub_d) are transmitted to the App, and the App transmits the received data to the server.

[0100] Step 105: The server transmits the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device.

[0101] In this embodiment of the invention, as an optional implementation, the server transmits the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device, including:

[0102] D11, The server uses the server's public key to verify the smart device signature;

[0103] In this embodiment of the invention, the server-side public key (pub_s) is used to verify the received smart device signature (sign_d).

[0104] D12, obtains the server-side token based on the smart device's public key and the server's private key;

[0105] In this embodiment of the invention, the server-side token (token_key) is calculated using the following formula:

[0106] token_key=ECDH(pub_d,pri_s).

[0107] D13, perform a modulo operation on the server-side token to obtain the server-side modulo value;

[0108] In this embodiment of the invention, the server-side modulus (oob) is calculated using the following formula:

[0109] oob=SHA256(token_key)mod 10^6.

[0110] D14 transmits the server-side token and server-side modulus value from the target device to the smart device.

[0111] Step 106: Based on the smart device's private key and the server's public key, the smart device modulus value obtained and the smart device modulus value are used to determine the server token or the smart device token as the communication key between the target device and the smart device.

[0112] In this embodiment of the invention, if the server-side modulus value is the same as the smart device modulus value, the server-side token or the smart device token is determined to be the communication key between the target device and the smart device.

[0113] In one embodiment of the present invention, as an optional embodiment, the App receives the server-side modulo value, displays the server-side modulo value, and notifies the smart device; the smart device receives the notification and displays the smart device modulo value; the user on the smart device confirms that the two displayed values ​​are the same, clicks to confirm, and thus completes the binding.

[0114] In this embodiment of the invention, to confirm the validity of the communication key, as an optional embodiment, the method further includes:

[0115] The server uses a server-side token to encrypt the smart device identifier, obtains encrypted data, and sends it to the smart device through the target device.

[0116] The smart device uses the smart device token to decrypt encrypted data to obtain the smart device identifier, which is then compared with the stored smart device identifier. If they match, the communication key is confirmed to be valid.

[0117] In one embodiment of the present invention, as an optional implementation, the server uses a server-side token to encrypt the smart device ID (did) using the AES_GCM algorithm, generates encrypted data (enrypted_data), and sends it to the App; the App receives the data and returns it to the smart device; the smart device uses the smart device token to decrypt the encrypted data, and after successful decryption, uses the communication key to communicate.

[0118] In this embodiment of the invention, after obtaining the communication key, the wireless password of the smart device can be obtained using the communication key. As another optional embodiment, the method further includes:

[0119] The WiFi password retrieval request is encrypted using a communication key and then sent to the smart device;

[0120] The smart device uses a communication key to decrypt the encrypted WiFi password retrieval request, uses the communication key to encrypt the WiFi password, and transmits the encrypted WiFi password to the target device.

[0121] The target device uses the communication key to decrypt the encrypted WiFi password and obtain the WiFi password.

[0122] In this embodiment of the invention, the App on the target device sends a WiFi password acquisition request through an encrypted Bluetooth channel, and the WiFi password acquisition request is encrypted using a token_key; the smart device returns the WiFi password encrypted using the token_key; the App uses the token_key to decrypt and obtain the WiFi password, and then connects to the WiFi.

[0123] In this embodiment of the invention, as an optional implementation, the target device uses a hardware security module to store a key (WiFi password), and the key conforms to FIPS 140-2 Level 3 verification. As another optional implementation, the smart device also uses the hardware security module to generate a communication key and perform operations (encryption, decryption, signing), but the communication key cannot be derived from the hardware security module.

[0124] In this embodiment of the invention, after obtaining the communication key, the data of the smart device can be obtained using the communication key. As another optional embodiment, the method further includes:

[0125] Send a data acquisition request to the smart device;

[0126] Receive encrypted data from a smart device, which is encrypted using the public key of the communication key. Decrypt the encrypted data using the private key of the communication key to obtain the data.

[0127] In another optional embodiment of this invention, the method further includes:

[0128] The smart device encrypts the data to be stored using the communication key before storing it.

[0129] In this embodiment of the invention, after taking a photo, the smart device encrypts the photo using a communication key when storing it. When browsing the photo, the user needs to enter the communication key to decrypt it.

[0130] In another optional embodiment of this invention, the method further includes:

[0131] Upon receiving a user's request to log in to the application, if the login is successful, the data encrypted and stored using the communication key corresponding to the user is automatically decrypted based on the communication key.

[0132] In another optional embodiment of this invention, the method further includes:

[0133] Upon detecting that the smart device is initializing, all stored data is deleted.

[0134] In this embodiment of the invention, after acquiring a smart device, the user associates the smart device with its corresponding App through a binding process, thus achieving binding. After the smart device and App are bound, the smart device's Wi-Fi hotspot is activated. The App obtains the Wi-Fi password (WiFi password) of the smart device through an encrypted Bluetooth channel, enabling the connection between the smart device and the App. Thus, if the smart device is lost and someone else finds it, the smart device must be re-initialized before it can be bound to a new target device (new account). During the initialization of the smart device, all data is deleted, effectively ensuring that the finding device cannot read the data, thus effectively protecting the privacy and security of the smart device. Furthermore, user data on the smart device is encrypted using a data public key (communication key public key). Data transmitted to the target device requires a data private key (communication key private key) to decrypt, ensuring that data on the smart device cannot be leaked through the memory card. Moreover, when the mobile phone App needs to reconnect with the smart device, it scans the smart device's Bluetooth and then obtains the WiFi password through an encrypted Bluetooth channel, enabling the mobile phone to reconnect without manual reconnection.

[0135] Figure 2 A schematic diagram of the privacy protection device structure of a smart device provided in an embodiment of the present invention is shown. Figure 2 As shown, the device includes:

[0136] Download module 201 is used to download the application for the smart device and send a binding request to the smart device through the application;

[0137] In this embodiment of the invention, as an optional embodiment, the download module 201 includes:

[0138] A registration unit (not shown in the figure) is used to register in the application.

[0139] A login unit is used to log in to the application and scan to obtain the smart device identifier and the first digital binding code of the smart device.

[0140] A binding request unit is used for the target device to send a binding code acquisition request to a server pre-configured for the application, wherein the binding code acquisition request carries the smart device identifier.

[0141] The digital code acquisition unit is used for the target device to acquire the second digital binding code returned by the server, wherein the second digital binding code is generated by the server based on the smart device identifier and the smart device public key corresponding to the smart device that is pre-stored;

[0142] If the first digital binding code is the same as the second digital binding code, the binding processing unit sends a binding request to the smart device.

[0143] The first transmission module 202 is used to send the smart device identifier returned by the smart device according to the binding request and the first random number to the server.

[0144] The second transmission module 203 is used to transmit the server-side signature, the second random number, and the server-side public key returned by the server to the smart device. The server-side signature is generated based on the smart device identifier and the first random number.

[0145] In this embodiment of the invention, as an optional embodiment, the second transmission module 203 includes:

[0146] A key pair generation unit (not shown in the figure) is used to receive the smart device identifier and the first random number on the server side and generate a server-side key pair.

[0147] In this embodiment of the invention, the server-side key pair includes a server-side public key and a server-side private key. As an optional embodiment, the server-side private key is encrypted and stored using the AES256 symmetric key algorithm of HSM.

[0148] A signature generation unit is used to generate a server-side signature based on a first random number and a server-side key pair.

[0149] In this embodiment of the invention, the server-side signature (sign_s) is calculated using the following formula:

[0150] sign_s=SHA256(pri_s_t,random_d).

[0151] The transmission unit is used to generate a second random number and transmit the server-side signature, the second random number, and the server-side public key of the server-side key pair to the smart device through the target device.

[0152] The third transmission module 204 is used to transmit the smart device signature and smart device public key returned by the smart device based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number.

[0153] In this embodiment of the invention, as an optional embodiment, the third transmission module 204 is specifically used for:

[0154] Verify the received server-side signature using the smart device's public key;

[0155] After the signature verification is successful on the server side, a smart device token is obtained based on the smart device private key and the server public key of the smart device key pair.

[0156] Perform a modulo operation on the smart device token to obtain the smart device modulo value;

[0157] Calculate the smart device signature based on the smart device's private key and the second random number;

[0158] The smart device signature and the smart device public key are returned to the server via the target device.

[0159] The fourth transmission module 205 is used to transmit the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device.

[0160] In this embodiment of the invention, as an optional embodiment, the fourth transmission module 205 includes:

[0161] The signature verification unit (not shown in the figure) is used by the server to verify the smart device signature using the server's public key.

[0162] The token acquisition unit is used to acquire a server-side token based on the smart device's public key and the server's private key.

[0163] Modulo operation unit, used to perform modulo operation on the server-side token to obtain the server-side modulo value;

[0164] The transmission unit is used to transmit the server-side token and server-side modulus value from the target device to the smart device.

[0165] The communication key determination module 206 is used to determine the server-side token or the smart device token as the communication key between the target device and the smart device based on the smart device private key and the smart device modulus obtained from the server-side public key.

[0166] In an optional embodiment of the present invention, the device further includes:

[0167] The communication key verification module (not shown in the figure) is used by the server to encrypt the smart device identifier using the server-side token, obtain encrypted data, and send it to the smart device through the target device.

[0168] The smart device uses the smart device token to decrypt encrypted data to obtain the smart device identifier, which is then compared with the stored smart device identifier. If they match, the communication key is confirmed to be valid.

[0169] In another optional embodiment of the present invention, the device further includes:

[0170] The wireless password acquisition module is used to encrypt the WiFi password acquisition request using a communication key and send it to the smart device;

[0171] The smart device uses a communication key to decrypt the encrypted WiFi password retrieval request, uses the communication key to encrypt the WiFi password, and transmits the encrypted WiFi password to the target device.

[0172] The target device uses the communication key to decrypt the encrypted WiFi password and obtain the WiFi password.

[0173] In another optional embodiment of the present invention, the device further includes:

[0174] The data acquisition module is used to send data acquisition requests to smart devices;

[0175] Receive encrypted data from a smart device, which is encrypted using the public key of the communication key. Decrypt the encrypted data using the private key of the communication key to obtain the data.

[0176] like Figure 3 As shown, one embodiment of this application provides a computer device 300 for performing... Figure 1 The privacy protection method in the device includes a memory 301, a processor 302 connected to the memory 301 via a bus, and a computer program stored on the memory 301 and executable on the processor 302, wherein the processor 302 implements the steps of the privacy protection method when executing the computer program.

[0177] Specifically, the memory 301 and processor 302 can be general-purpose memory and processor, without any specific limitations. When the processor 302 runs the computer program stored in the memory 301, it can execute the above-mentioned privacy protection method.

[0178] Corresponding to Figure 1 In addition to the privacy protection method described above, this application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is run by a processor, it executes the steps of the privacy protection method described above.

[0179] Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk or hard disk. When the computer program on the storage medium is run, it can execute the above-mentioned privacy protection methods.

[0180] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. The system embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0181] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0182] In addition, the functional units in the embodiments provided in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0183] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0184] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0185] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for protecting the privacy of a smart device, characterized in that, Applied to target devices, including: Download the application for the smart device, log in to the application with the registered username and password corresponding to the smart device, and send a binding request to the smart device through the application; The smart device is sent to the server based on the smart device identifier returned by the binding request and the first random number; The server-side signature, the second random number, and the server-side public key returned by the server are transmitted to the smart device. The server-side signature is generated based on the smart device identifier and the first random number. The smart device transmits the smart device signature and smart device public key returned by the server based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number. The server transmits the server-side token and the server-side modulo value back to the smart device based on the received smart device signature, the smart device public key, and the server-side modulo value. Based on the user's determination of the smart device modulus value displayed on the smart device and the server-side modulus value displayed on the target device, the server-side token is determined as the communication key between the target device and the smart device; the smart device modulus value is obtained by the smart device calculating the smart device token based on the smart device private key and the server-side public key, and then performing a modulo operation on the smart device token; Sending a binding request to the smart device through the application includes: Register within the application; Log in to the application and scan to obtain the smart device identifier and the first digital binding code of the smart device; The target device sends a binding code acquisition request to a server pre-configured for the application, and the binding code acquisition request carries the smart device identifier. The target device obtains the second digital binding code returned by the server. The second digital binding code is generated by the server based on the smart device identifier and the smart device public key corresponding to the smart device that is pre-stored. If the first digital binding code is the same as the second digital binding code, a binding request is sent to the smart device.

2. The method according to claim 1, characterized in that, The step of transmitting the server-side signature, the second random number, and the server-side public key returned by the server to the smart device includes: The server receives the smart device identifier and the first random number, and generates a server-side key pair. Generate a server-side signature based on the first random number and the server-side key pair; Generate a second random number, and transmit the server-side signature, the second random number, and the server-side public key of the server-side key pair to the smart device through the target device.

3. The method according to claim 1, characterized in that, The step of transmitting the smart device signature and smart device public key returned by the smart device based on the received server-side signature, the second random number, and the server-side public key to the server includes: Verify the received server-side signature using the smart device's public key; After the signature verification is successful on the server side, a smart device token is obtained based on the smart device private key and the server public key of the smart device key pair. Perform a modulo operation on the smart device token to obtain the smart device modulo value; Calculate the smart device signature based on the smart device's private key and the second random number; The smart device signature and the smart device public key are returned to the server via the target device.

4. The method according to claim 3, characterized in that, The step of transmitting the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device includes: The server uses its public key to verify the smart device's signature. Obtain the server-side token based on the smart device's public key and the server's private key; Perform a modulo operation on the server-side token to obtain the server-side modulo value; The target device transmits the server-side token and server-side modulo value to the smart device.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: The server uses a server-side token to encrypt the smart device identifier, obtains encrypted data, and sends it to the smart device through the target device. The smart device uses the smart device token to decrypt encrypted data to obtain the smart device identifier, which is then compared with the stored smart device identifier. If they match, the communication key is confirmed to be valid.

6. The method according to any one of claims 1 to 4, characterized in that, Also includes: The WiFi password retrieval request is encrypted using a communication key and then sent to the smart device; The smart device uses a communication key to decrypt the encrypted WiFi password retrieval request, uses the communication key to encrypt the WiFi password, and transmits the encrypted WiFi password to the target device. The target device uses the communication key to decrypt the encrypted WiFi password and obtain the WiFi password.

7. A privacy protection device for a smart device, characterized in that, Applied to target devices, including: The download module is used to download the application for the smart device, and after logging into the application with the registered username and password corresponding to the smart device, send a binding request to the smart device through the application. The first transmission module is used to send the smart device identifier returned by the smart device according to the binding request and the first random number to the server. The second transmission module is used to transmit the server-side signature, the second random number, and the server-side public key returned by the server to the smart device. The server-side signature is generated based on the smart device identifier and the first random number. The third transmission module is used to transmit the smart device signature and smart device public key returned by the smart device based on the received server signature, the second random number and the server public key to the server. The smart device signature is generated based on the smart device private key and the second random number. The fourth transmission module is used to transmit the server-side token returned by the server based on the received smart device signature, the smart device public key, and the server-side modulo value to the smart device. The communication key determination module is used to determine the server-side token as the communication key between the target device and the smart device based on the user's determination operation of the smart device modulus value displayed on the smart device and the server-side modulus value displayed on the target device; the smart device modulus value is obtained by the smart device calculating the smart device token based on the smart device private key and the server-side public key, and then performing a modulo operation on the smart device token; Sending a binding request to the smart device through the application includes: Register within the application; Log in to the application and scan to obtain the smart device identifier and the first digital binding code of the smart device; The target device sends a binding code acquisition request to a server pre-configured for the application, and the binding code acquisition request carries the smart device identifier. The target device obtains the second digital binding code returned by the server. The second digital binding code is generated by the server based on the smart device identifier and the smart device public key corresponding to the smart device that is pre-stored. If the first digital binding code is the same as the second digital binding code, a binding request is sent to the smart device.

8. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, they perform the steps of the privacy protection method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the privacy protection method as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Single sign on method based on IKI identifier authentication

    CN107454077A

  • Security chip communication method and device based on bidirectional signature authentication

    CN114785532A