A system and method for securely binding a device
Obtain and persistently store binding tokens through the APP to establish an encrypted connection, which solves the problems of insufficient security and complex processes of device security binding in the existing technology, simplifies the binding process, reduces maintenance costs, and increases users Experience and device availability.
Patent Information
- Application Number
- CN202410095145.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-23
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-01-23
AI Technical Summary
Existing equipment security binding technology has problems such as insufficient security, complex binding process, high maintenance cost and poor user experience. Especially, a single binding token is easily stolen or leaked, and users need to manually enter the token or scan the two-dimensional one. code increases operational complexity and server load.
APP uses APP to obtain binding tokens through a secure communication interface, and establish an encrypted connection with the device through a secure connection protocol. The device receives and persists the storage tokens to ensure the integrity and confidentiality of data during transmission and storage. The device is connected. After parsing the token and returning the result, the cloud server verifies the binding information through the security authentication mechanism, reducing the server load and simplifying user operations.
Improves the security of the equipment, simplifies the binding process, reduces maintenance costs, improves user experience and device availability, and ensures data security and reliability through automated processes and encryption mechanisms.
Smart Images

Figure CN117729050B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of software technology, and in particular to a system and method for securely binding devices. Background Art
[0002] With the development of modern technology, various smart devices are becoming more and more popular, such as smart phones, smart TVs, smart home appliances, etc.; these devices usually need to be connected to the user's application (APP) through the network so that users can remotely control and manage these devices; in order to ensure the security of the device, it is usually necessary to establish a secure binding relationship between the device and the APP; this binding relationship is usually achieved by applying for a binding token from the cloud server through the APP, and sending the token to the device, the device receives and persistently stores the token, and then after connecting to the network, the device returns the parsed token to the APP, and reports to the cloud server whether the binding is allowed, thereby achieving secure binding of the device.
[0003] Deficiencies of existing technology:
[0004] 1. Insufficient security: Existing device security binding technology usually relies on only a single binding token. If the binding token is stolen or leaked, the security of the device will be threatened.
[0005] 2. Complex binding process: Existing device security binding technology usually requires users to manually enter the binding token or enter the binding token by scanning a QR code, etc. This method is not only complicated to operate, but also prone to errors.
[0006] 3. High maintenance cost: Existing device security binding technology usually requires the cloud server to process each binding request, which not only increases the server load but also increases the maintenance cost.
[0007] 4. Poor user experience: Due to the complex process and high maintenance cost of existing device security binding technology, this often affects the user experience. For example, users may need to wait for a long time to complete the device binding, or encounter various problems during the binding process.
[0008] Therefore, the prior art has deficiencies and needs further improvement. Summary of the invention
[0009] In view of the problems existing in the prior art, the present invention provides a system and method for securely binding devices.
[0010] To achieve the above object, the specific scheme of the present invention is as follows:
[0011] The present invention provides a device security binding system, the system comprising:
[0012] APP, cloud servers and devices;
[0013] in,
[0014] The APP is used to initiate a secure binding request to the cloud server, obtain a binding token through a secure communication interface, and establish an encrypted connection with the target device using a secure connection protocol;
[0015] The device receives and persistently stores the binding token using a secure storage mechanism to ensure the security of the token;
[0016] The cloud server is used to process the binding request, generate binding information including the owner ID and the random number using a security authentication mechanism, and send the binding information to the target device after encryption;
[0017] Security protection measures are implemented during the transmission and storage of the binding information to ensure the integrity and confidentiality of the data throughout the binding process.
[0018] Furthermore, after the device is connected to the network, it parses the persistently stored security binding token through a security parsing mechanism and returns the parsed token to the APP. At the same time, the device reports to the cloud server whether the binding result is allowed if the security verification conditions are met.
[0019] Furthermore, after receiving the parsed token returned by the device, the APP calls the secure binding interface to the cloud server to request device binding based on the token and the secure connection protocol. The interface includes a security authentication and encryption mechanism to ensure the security of the binding process.
[0020] Furthermore, after receiving the binding result of the device, the cloud server returns the binding result to the APP.
[0021] Furthermore, when the device is started and goes online, it reports its persistent binding information to the cloud server.
[0022] Furthermore, the cloud server records the binding information of the device into a binding information table, and performs verification according to the user-device relationship link table and the binding information table when the APP initiates a connection request.
[0023] The present invention also provides a device security binding method, using the above system, the method comprises the following steps:
[0024] S1, the user selects the device to be bound in the APP, and the APP sends a binding request to the cloud server, including the user ID and device ID information; after receiving the request, the cloud server generates a binding token;
[0025] S2, after the APP receives the binding token returned by the cloud server, it sends the binding token to the device through a specific connection method (such as Bluetooth or WiFi hotspot); after the device receives the binding token, it stores it persistently locally;
[0026] S3: After the device is connected to the network, it parses the persistently stored binding token and returns the parsing result to the APP. At the same time, the device reports to the cloud server whether the binding is allowed, including the device ID, binding token, and binding result information.
[0027] S4, after receiving the parsing result returned by the device, the APP calls the binding interface of the cloud server to bind the device according to the binding token and the parsing result; the request includes the user ID, device ID and binding token information;
[0028] S5. After receiving the binding result of the device, the cloud server verifies the validity of the binding token and device ID. If the verification is successful, the cloud server records the binding result in the user-device relationship table and the device binding information table, and returns the binding result to the APP, including the binding status and possible error information. If the verification fails, the cloud server returns an error message to the APP and ends the binding process.
[0029] Furthermore, in step S2, after receiving the binding result of the device, the cloud server returns the binding result to the APP and sends the binding information to the device.
[0030] Furthermore, in step S3, when the device is started and goes online, it reports persistent binding information to the cloud server, and the cloud server records the binding information of the device into a binding information table.
[0031] Furthermore, a P2P transmission channel is established between the APP, the cloud server and the device for data transmission.
[0032] The technical solution of the present invention has the following beneficial effects:
[0033] 1. Improve security: Apply for a binding token from the cloud server through the APP, and establish a connection with the device through the binding interface. The device receives and persistently stores the binding token, which can effectively prevent the binding token from being stolen or leaked, thereby improving the security of the device.
[0034] 2. Simplify the binding process: This patent uses an automated process to eliminate the need for users to manually enter a binding token or enter a binding token by scanning a QR code, making the device binding process simpler and more convenient to operate.
[0035] 3. Reduce maintenance costs: This patent allows the device to actively report binding information to the cloud server, reducing the need for the cloud server to process each binding request, thereby reducing the server load and maintenance costs.
[0036] 4. Improve user experience: Since this patent simplifies the device binding process and reduces maintenance costs, it can provide a better user experience. Users can complete device binding more quickly and conveniently, thereby improving user satisfaction.
[0037] 5. Improve the availability of the device: This patent improves the availability of the device by reporting persistent binding information to the cloud server when the device is started online, so that the device can automatically complete the connection with the cloud server without user operation.
[0038] 6. Enhanced data management capabilities: This patent records the device's binding information into the binding information table through the cloud server, and when the APP initiates a connection request, it verifies based on the user device relationship list and the binding information table. This can better manage and control the device's data and improve data security and reliability.
[0039] 7. When a user binds a device, the cloud sends the binding information, which is persistently stored on the device, and the device reports the binding information and records it in the cloud. The user-device relationship list and device binding information record table recorded in the cloud are used for verification, which can support overlay binding, optimize the after-sales process and user experience, and solve the security risks of monitoring duplicate device numbers. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 is a system block diagram of the present invention;
[0041] Figure 2 It is the overall flow chart of the present invention;
[0042] Figure 3 This is a schematic diagram of the process of APP binding device of the present invention;
[0043] Figure 4 It is a schematic diagram of the process of APP monitoring connection equipment of the present invention. DETAILED DESCRIPTION
[0044] The present invention is further described in detail below in conjunction with the accompanying drawings and embodiments; it can be understood that the specific embodiments described herein are only used to explain the present invention rather than to limit the present invention; it should also be noted that, for ease of description, only the parts related to the present invention rather than all are shown in the accompanying drawings.
[0045] Combination Figure 1-Figure 4As shown, the present invention provides a system for secure binding of devices, the system comprising:
[0046] APP, cloud servers and devices;
[0047] in,
[0048] The APP is used to initiate a secure binding request to the cloud server, obtain a binding token through a secure communication interface, and establish an encrypted connection with the target device using a secure connection protocol;
[0049] The device receives and persistently stores the binding token using a secure storage mechanism to ensure the security of the token;
[0050] The cloud server is used to process the binding request, generate binding information including the owner ID and the random number using a security authentication mechanism, and send the binding information to the target device after encryption;
[0051] Security protection measures are implemented during the transmission and storage of the binding information to ensure the integrity and confidentiality of the data throughout the binding process.
[0052] After the device is connected to the network, it parses the persistently stored security binding token through the security parsing mechanism and returns the parsed token to the APP. At the same time, the device reports to the cloud server whether the binding result is allowed if the security verification conditions are met.
[0053] After receiving the parsed token returned by the device, the APP calls the secure binding interface to the cloud server to request device binding based on the token and the secure connection protocol. The interface includes a security authentication and encryption mechanism to ensure the security of the binding process.
[0054] After receiving the binding result of the device, the cloud server returns the binding result to the APP.
[0055] When the device is started and goes online, it reports its persistent binding information to the cloud server.
[0056] The cloud server records the binding information of the device into the binding information table, and performs verification according to the user device relationship link table and the binding information table when the APP initiates a connection request.
[0057] like Figure 2 The present invention also provides a device security binding method, using the above system, the method comprises the following steps:
[0058] S1, the user selects the device to be bound in the APP, and the APP sends a binding request to the cloud server, including the user ID and device ID information; after receiving the request, the cloud server generates a binding token;
[0059] S2, after the APP receives the binding token returned by the cloud server, it sends the binding token to the device through a specific connection method (such as Bluetooth or WiFi hotspot); after the device receives the binding token, it stores it persistently locally;
[0060] S3: After the device is connected to the network, it parses the persistently stored binding token and returns the parsing result to the APP. At the same time, the device reports to the cloud server whether the binding is allowed, including the device ID, binding token, and binding result information.
[0061] S4, after receiving the parsing result returned by the device, the APP calls the binding interface of the cloud server to bind the device according to the binding token and the parsing result; the request includes the user ID, device ID and binding token information;
[0062] S5. After receiving the binding result of the device, the cloud server verifies the validity of the binding token and device ID. If the verification is successful, the cloud server records the binding result in the user-device relationship table and the device binding information table, and returns the binding result to the APP, including the binding status and possible error information. If the verification fails, the cloud server returns an error message to the APP and ends the binding process.
[0063] In step S2, after receiving the binding result of the device, the cloud server returns the binding result to the APP and sends the binding information to the device.
[0064] In step S3, when the device is started and goes online, it reports persistent binding information to the cloud server, and the cloud server records the binding information of the device into a binding information table.
[0065] A P2P transmission channel is established between the APP, the cloud server and the device for data transmission.
[0066] The principle of the present invention is as follows:
[0067] In view of the situation where the factory flash copies the equipment to produce duplicate certificates, when the present invention binds the equipment through APP, the cloud sends the binding owner ID and random number and other information to the equipment, and the equipment persists the information locally. At the same time, when the equipment goes online, the binding information is reported to the cloud. Every time the APP communicates with the device, the cloud needs to determine whether the user-device relationship list and the device binding information table are legal, so as to achieve reliable and secure access to the device.
[0068] When a user device is bound, the server will store the user and device relationship chain. When the user accesses the device, the cloud will verify the legitimacy of the relationship chain. If the verification is passed, direct access to the device will be allowed. When the factory production is abnormal, flash copying and other scenarios occur, and the cloud cannot distinguish between duplicate devices, this method can ensure reliable security verification on the cloud.
[0069] From the server side, each device with a duplicate certificate is the same and cannot be distinguished (ID, MAC, activation information, etc. are all the same). When multiple users bind this duplicate ID device, when different users initiate monitoring connections to this device ID, they cannot actually find the corresponding device ID, resulting in the wrong device being monitored, which poses a security issue.
[0070] like Figure 3 As shown, the process of binding the device to the APP of the present invention is as follows:
[0071] The relationship between App devices and cloud;
[0072] App applies for a binding token from the cloud, and the cloud returns the binding token to the app;
[0073] The App establishes a connection with devices through AP hotspots and Bluetooth, and sends a binding token;
[0074] Devices connect to WiFi, and after connecting to the internet, they return a parsed token to the app;
[0075] Devices report to the cloud whether the binding result is allowed;
[0076] The App calls the binding interface to bind the device to the cloud based on the binding token.
[0077] The cloud returns the binding result to the app. If it fails, the app ends immediately.
[0078] The cloud sends binding information to devices;
[0079] Devices devices persistently store binding information.
[0080] like Figure 4 As shown, it is the process of the APP of the present invention monitoring the connected device:
[0081] Devices start to go online and report persistent binding information to the cloud;
[0082] The cloud records the binding information into the binding information table;
[0083] The app initiates a calling connection to the cloud, carrying the corresponding device ID;
[0084] The cloud reads the user device relationship list and binding information table and verifies them;
[0085] After the cloud verification is passed, the resource information is returned to the app, and the calling and resource information are sent to the device;
[0086] A P2P transmission channel is established between the app, the cloud, and devices for audio and video transmission.
[0087] Through the user-device relationship list and binding information table, the cloud can prevent monitoring of devices with duplicate numbers, thereby ensuring secure access to devices.
[0088] The relationship between App, device, and cloud server:
[0089] Device: This is the actual physical device used by the user, such as a smart home device. When the user binds the device through the app, the device will receive the binding information (including the owner ID and random number, etc.) from the cloud server and store this information locally; when the device goes online, it will report this binding information to the cloud server.
[0090] App: This is an application used by users on mobile phones or other mobile devices; users initiate device binding requests through the app, and after successful binding, they can monitor and control the device through the app; the communication between the app and the cloud server is achieved by calling the API interface provided by the cloud server.
[0091] Cloud server: This is the core of the entire system, responsible for processing and managing all interactions between devices and apps. When a user binds a device through an app, the cloud server will send binding information to the device and record the device's binding information. When the app communicates with the device, the cloud server will perform a legitimacy check based on the user-device relationship list and the device binding information table. Only requests that pass the check can access the device. In addition, the cloud server is also responsible for processing the device's online information and the app's monitoring connection requests.
[0092] This design can effectively prevent security issues caused by duplicate device certificates and ensure that users can access devices reliably and safely. At the same time, through the user-device relationship list and device binding information record table recorded by the cloud server, it can support device coverage binding, optimize the after-sales process, and improve user experience.
[0093] The following are some embodiments, which are based on the secure binding technology between the device and the APP.
[0094] Example 1: A device binding process based on a QR code
[0095] In this embodiment, the APP generates a QR code that contains a binding token. The user only needs to use the device to scan the QR code, and the device can automatically obtain and store the binding token. After the device is connected to the network, it returns the parsed token to the APP and reports to the cloud server whether the binding is allowed, thereby achieving secure binding of the device.
[0096] Example 2: A device binding process based on NFC
[0097] In this embodiment, the APP establishes a connection with the device through the NFC interface, and then the APP applies for a binding token from the cloud server and sends the token to the device through the NFC interface. The device receives and persistently stores the token. After the device is connected to the network, it returns the parsed token to the APP and reports to the cloud server whether the binding is allowed, thereby achieving secure binding of the device.
[0098] Example 3: A Bluetooth-based device binding process
[0099] In this embodiment, the APP establishes a connection with the device through the Bluetooth interface, and then the APP applies for a binding token from the cloud server and sends the token to the device through the Bluetooth interface. The device receives and persistently stores the token. After the device is connected to the network, it returns the parsed token to the APP and reports to the cloud server whether the binding is allowed, thereby achieving secure binding of the device.
[0100] Example 4: A device binding process based on Wi-Fi
[0101] In this embodiment, the APP establishes a connection with the device through the Wi-Fi interface, and then the APP applies for a binding token from the cloud server and sends the token to the device through the Wi-Fi interface. The device receives and persistently stores the token. After the device is connected to the network, it returns the parsed token to the APP and reports to the cloud server whether the binding is allowed, thereby achieving secure binding of the device.
[0102] Example 5: A device binding process based on a cloud server
[0103] In this embodiment, when the device starts to go online, it reports persistent binding information to the cloud server. After receiving the device's online information, the cloud server determines whether the device allows binding based on the device's binding information. If binding is allowed, the cloud server sends a successful binding message to the device. After the device receives the successful binding message, it returns the binding result to the APP, thereby achieving secure binding of the device.
[0104] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the inventive concept of the present invention, or directly / indirectly applied in other related technical fields are included in the protection scope of the present invention.
Claims
1. A device security binding system, characterized in that: The system includes: APP, cloud servers and devices; in, The APP is used to initiate a secure binding request to the cloud server, obtain a binding token through a secure communication interface, and establish an encrypted connection with the target device using a secure connection protocol; The device receives and persistently stores the binding token using a secure storage mechanism to ensure the security of the token; The cloud server is used to process the binding request, generate binding information including the owner ID and the random number using a security authentication mechanism, and send the binding information to the target device after encryption; The binding information is protected by security measures during transmission and storage to ensure the integrity and confidentiality of the data throughout the binding process; After the device is connected to the network, it parses the persistently stored security binding token through the security parsing mechanism and returns the parsed token to the APP. At the same time, the device reports to the cloud server whether the binding result is allowed if the security verification conditions are met; After receiving the parsed token returned by the device, the APP calls the secure binding interface to the cloud server to request device binding based on the token and the secure connection protocol. The interface includes a security authentication and encryption mechanism to ensure the security of the binding process.
2. The system according to claim 1, characterized in that After receiving the binding result of the device, the cloud server returns the binding result to the APP.
3. The system according to claim 2, characterized in that When the device is started and goes online, it reports its persistent binding information to the cloud server.
4. The system according to claim 3, characterized in that The cloud server records the binding information of the device into the binding information table, and performs verification according to the user device relationship link table and the binding information table when the APP initiates a connection request.
5. A device security binding method, using the system according to any one of claims 1 to 4, characterized in that: The method comprises the following steps: S1, the user selects the device to be bound in the APP, and the APP sends a binding request to the cloud server, including the user ID and device ID information; after receiving the request, the cloud server generates a binding token; S2, after the APP receives the binding token returned by the cloud server, it sends the binding token to the device through a specific connection method; after the device receives the binding token, it stores it persistently locally; S3: After the device is connected to the network, it parses the persistently stored binding token and returns the parsing result to the APP. At the same time, the device reports to the cloud server whether the binding is allowed, including the device ID, binding token, and binding result information. S4, after receiving the parsing result returned by the device, the APP calls the binding interface of the cloud server to bind the device according to the binding token and the parsing result; the request includes the user ID, device ID and binding token information; S5. After receiving the binding result of the device, the cloud server verifies the validity of the binding token and device ID. If the verification is successful, the cloud server records the binding result in the user-device relationship table and the device binding information table, and returns the binding result to the APP, including the binding status and possible error information. If the verification fails, the cloud server returns an error message to the APP and ends the binding process.
6. The method according to claim 5, characterized in that In step S2, after receiving the binding result of the device, the cloud server returns the binding result to the APP and sends the binding information to the device.
7. The method according to claim 6, characterized in that In step S3, when the device is started and goes online, it reports persistent binding information to the cloud server, and the cloud server records the binding information of the device into a binding information table.
8. The method according to claim 7, characterized in that A P2P transmission channel is established between the APP, the cloud server and the device for data transmission.
