Method for wireless communication between devices, and communication apparatus

Abstract

Provided in the present invention are a method for wireless communication between devices, and a communication apparatus, which are used for improving the usage security of communication devices. The method for wireless communication between devices is applied to a slave device among master and slave devices having functions of mutual communication. The method comprises: after a master device sends to a slave device an initiation request for pairing or unpairing, the slave device sending to the master device an initiation response for pairing or unpairing, wherein the initiation response includes a binding feature code, which is randomly generated in a current state and has values that are not all zero; and when pairing confirmation or unpairing confirmation is performed between the master device and the slave device, the slave device first receiving a pairing confirmation request or an unpairing confirmation request sent by the master device, and then determining whether a binding feature code in the confirmation request is the binding feature code included in the initiation response, and if so, confirming that a pairing operation or an unpairing operation is successful, otherwise, confirming that the pairing operation or the unpairing operation fails.

Description

Method and apparatus for wireless communication between devices Technical Field

[0001] The present invention relates to a method and a communication device for wireless communication between devices. Background Art

[0002] With the increasing use of wireless communication technology in the medical field, more and more medical devices are equipped with the ability to connect wirelessly to other devices, enabling wireless data transmission and information exchange. While bringing convenience and a better user experience to users, the introduction of wireless communication also brings security issues and challenges to medical devices. Compared with wired communication, wireless communication is more vulnerable to hackers and intruders eavesdropping during data transmission and physical harm through medical devices, posing a significant threat to the safe use of medical devices.

[0003] Although mainstream secure communication framework protocols such as SSL / TLS exist in the internet and mobile internet sectors and can effectively defend against various common intrusions and attacks, they are not widely adopted in most medical devices based on embedded hardware platforms due to limitations in hardware resources and computing performance. This is particularly true for low-power, portable, and wearable medical devices such as patch-type insulin pumps and continuous glucose meters, which have stringent requirements for size and power consumption and often lack the hardware necessary to implement complex security protocols like SSL / TLS. Furthermore, in pursuit of a lightweight and compact user experience, many of these products lack basic human-computer interaction interfaces and interfaces such as screens and buttons, nor do they have additional communication channels such as NFC and RFID. This makes it impossible to exchange and confirm the identities of both communicating parties during the initial communication phase. This identity exchange and confirmation process is a prerequisite for enabling communication security mechanisms in common wireless communication protocols such as Bluetooth and Zigbee.

[0004] Summary of the Invention

[0005] In view of this, the present invention proposes a method and a communication apparatus for wireless communication between devices to improve the security of communication devices. The present invention provides the following technical solutions:

[0006] A method for wireless communication between devices, applied to a slave device among master-slave devices with mutual communication functions, the method comprising: after the master device sends an initiation request for pairing or depairing to the slave device, the slave device sends an initiation response for pairing or depairing to the master device, the initiation response containing a binding feature code that is randomly generated in the current state and is not all zero; when the master device and the slave device perform pairing or depairing confirmation, the slave device first receives the pairing or depairing confirmation request sent by the master device, and then determines whether the binding feature code in the confirmation request is the binding feature code contained in the initiation response; if so, the pairing or depairing operation is confirmed to be successful; otherwise, the pairing or depairing operation is confirmed to have failed.

[0007] Optionally, it also includes: when the slave device confirms that the pairing operation is successful, the slave device saves the binding feature code; after receiving the binding request sent by the master device, the slave device determines whether the binding feature code in the binding request is the same as the binding feature code saved when the pairing operation is successful. If not, the slave device does not respond to the binding request.

[0008] Optionally, the initiation response also includes a binding key that is randomly generated in the current state and is not all zero. When the pairing operation is confirmed to be successful, the slave device saves the binding key; when the slave device responds to the binding request, the payload data of the binding response is encrypted with the saved binding key and then sent to the master device. The payload data includes the currently randomly generated slave device initial transmission index and transmission key.

[0009] A method for wireless communication between devices, applied to a master device among master-slave devices with mutual communication functions, the method comprising: the master device generates a slave device feature code based on feature information of the slave device, then encrypts payload data of an initiation request for initiating pairing or depairing with the slave device feature code and sends the encrypted payload data to the slave device, the payload data including the master device feature code and an initiation key; the master device receives an initiation response sent by the slave device to initiate pairing or depairing, decrypts the payload data of the initiation response with the initiation key to obtain a binding feature code, the binding feature code being randomly generated when the slave device sends the initiation response; and when the master device and the slave device are successfully paired, the master device sends a binding request to the slave device, the binding request including the binding feature code.

[0010] Optionally, the step of the master device generating a slave device feature code based on the feature information of the slave device includes: the master device uses a hash algorithm to calculate the feature information of the slave device to obtain the slave device feature code; wherein the feature information of the slave device includes the device serial number and / or physical address of the slave device.

[0011] Optionally, the initiation response also includes a binding key randomly generated by the slave device and not all zero; the method also includes: the master device encrypts the payload data of the binding request with the binding key and sends it to the slave device, the payload data including the binding feature code; the master device receives the binding response of the slave device to the binding request, the payload data of the binding response including the slave device initial transmission index and transmission key randomly generated by the slave device when generating the binding response; the master device decrypts the payload data in the binding response with the binding key to obtain the slave device initial transmission index and transmission key.

[0012] Optionally, the slave device is a patch-type insulin pump or a continuous blood glucose meter transmitter probe.

[0013] A slave device communication device is arranged in a slave device, and the slave device can communicate with a master device. The slave device communication device includes an initiation response module, a confirmation request receiving module, and a judgment confirmation module, wherein: the initiation response module is used to send an initiation response for pairing or depairing to the master device after the master device sends an initiation request for pairing or depairing to the slave device, and the initiation response includes a binding feature code randomly generated by the initiation response module in the current state and not all zero; the confirmation request receiving module is used to receive the pairing or depairing confirmation request sent by the master device from the slave device when the master device and the slave device perform pairing or depairing confirmation; the judgment confirmation module is used to determine whether the binding feature code in the confirmation request is the binding feature code included in the initiation response. If so, it is confirmed that the pairing or depairing operation is successful; otherwise, it is confirmed that the pairing or depairing operation fails.

[0014] Optionally, it also includes a binding feature code saving module and a binding judgment module, wherein: the binding feature code saving module is used to save the binding feature code when the pairing operation is successful; the binding judgment module is used to judge whether the binding feature code in the binding request sent by the main device is the same as the binding feature code saved by the binding feature code saving module. If not, no response is made to the binding request.

[0015] Optionally, the initiating response module is also used to randomly generate a binding key that is not all zero in the current state; the communication device also includes a binding key saving module and a binding request response module, wherein: the binding key saving module is used to save the binding key when the pairing operation is confirmed to be successful; the binding request response module is used to encrypt the payload data of the binding response with the saved binding key and then send it to the master device, and the payload data includes the currently randomly generated slave device initial transmission index and transmission key.

[0016] Optionally, the slave device communication apparatus is provided in a patch-type insulin pump or a continuous blood glucose meter transmitter probe serving as the slave device.

[0017] A master device communication device is arranged in the master device, and the master device can communicate with the slave device. The master device communication device includes an initiation request sending module, an initiation response receiving module, and a binding request sending module, wherein: the initiation request sending module is used to generate a slave device feature code based on the feature information of the slave device, and then encrypt the payload data of the initiation request for initiating pairing or depairing with the slave device feature code and send it to the slave device, the payload data including the master device feature code and the initiation key; the initiation response receiving module is used to receive the initiation response sent by the slave device to initiate pairing or depairing, and decrypt the payload data of the initiation response with the initiation key to obtain the binding feature code, which is randomly generated when the slave device sends the initiation response; the binding request sending module is used to send a binding request to the slave device when the master device and the slave device are successfully paired, and the binding request includes the binding feature code.

[0018] Optionally, the request sending module is further configured to calculate the characteristic information of the slave device using a hash algorithm to obtain a characteristic code of the slave device; wherein the characteristic information of the slave device includes a device serial number and / or a physical address of the slave device.

[0019] Optionally, the initiation response also includes a binding key randomly generated by the slave device and not all zero; the master device communication device also includes a binding request sending module, a binding response receiving module, and a decryption module, wherein: the binding request sending module is used to encrypt the payload data of the binding request with the binding key and send it to the slave device, and the payload data includes the binding feature code; the binding response receiving module is used to receive a binding response from the slave device for the binding request, and the payload data of the binding response includes the slave device initial transmission index and transmission key randomly generated by the slave device when generating the binding response; the decryption module is used to decrypt the payload data in the binding response with the binding key to obtain the slave device initial transmission index and transmission key. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] For purposes of illustration and not limitation, the present invention will now be described with reference to preferred embodiments thereof, particularly with reference to the accompanying drawings, in which:

[0021] FIG1 is a schematic diagram of the appearance of a master device and a slave device applicable to an embodiment of the present invention in the prior art;

[0022] FIG2 is a schematic diagram of a communication message data structure according to an embodiment of the present invention;

[0023] 3 is a schematic diagram of the main steps of the process of pairing or unpairing a master device and a slave device and the content of a communication message in an embodiment of the present invention;

[0024] 4 is a schematic diagram of a process executed by a master device during pairing or unpairing according to an embodiment of the present invention;

[0025] 5 is a schematic diagram of a process executed by a slave device during pairing or unpairing according to an embodiment of the present invention;

[0026] 6 is a schematic diagram of the main steps of the process of binding and transmitting between a master device and a slave device and the content of communication messages in an embodiment of the present invention;

[0027] 7 is a schematic diagram of a process executed by a master device during binding and transmission according to an embodiment of the present invention;

[0028] FIG8 is a schematic diagram of a process executed by a slave device during binding and transmission according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The technical solution of the embodiment of the present invention realizes an identity authentication and secure communication method. The method is based on a symmetric encryption algorithm with a 256-bit key (such as AES, ChaCha algorithm), an encryption mode of authenticated encryption (such as CCM, GCM mode) and a 256-bit hash algorithm (such as SHA-256, RIPEMD-256 algorithm), and does not include complex algorithm processing such as asymmetric encryption (such as RSA, ElGamal algorithm), key negotiation exchange (such as ECDH, ECDSA algorithm), etc., and is suitable for running on embedded hardware platforms of medical devices with limited resource performance. During the communication process, all data sent and received by both communicating parties are encrypted and transmitted in an authenticated encryption mode and authentication information is attached to prevent eavesdropping and tampering during data transmission. At the same time, the method can prevent hackers from intercepting data during the communication process and sending it directly to the device without modification, so as to achieve illegal control or access to the device. In addition, the identity information of the two communicating parties required in the initial stage of communication is generated by a hash algorithm based on existing feature information such as the device serial number, physical address, user account password, etc., and does not rely on a human-computer interaction interface or additional communication channels to exchange and confirm the identity information of the two communicating parties. It can be widely applied to portable and wearable medical devices with limited size and power consumption.

[0030] In the embodiments of the present invention, the devices involved in wireless communication are divided into two roles: master and slave. Each communication is initiated by the master device, which establishes a wireless connection. After the wireless connection is established, the master device actively sends a communication request to the slave device, which may or may not respond to the master's communication request. After the communication is completed, the master device actively disconnects the wireless connection. Taking portable or wearable medical devices such as patch-type insulin pumps or continuous blood glucose meters as an example, the master device is typically a wireless terminal device with a human-computer interface, such as a portable wireless controller, wireless data receiver, mobile phone, or tablet computer. The slave device is typically a wearable device such as a patch-type insulin pump body or a continuous blood glucose meter transmitter probe. See Figure 1, which is a schematic diagram of the external appearance of a master and slave device suitable for the embodiments of the present invention in the prior art. On the left side of Figure 1 is a portable wireless controller 11, serving as the master device; on the right side is a patch-type insulin pump 12, serving as the slave device. Since most slave devices are medical devices that directly contact the human body and may pose a threat to human safety and health, the embodiments of the present invention are designed with the primary security goal of preventing unauthorized access or intrusion attacks on the slave device during communication.

[0031] During the communication process, data is sent and received between the master and slave devices in the form of communication messages, and the transmitted data is encrypted and authenticated using an authenticated encryption mode. The symmetric encryption algorithm key length used in the authenticated encryption mode is 256 bits (32 bytes). Authenticated encryption modes applicable to the present invention include but are not limited to CCM and GCM modes, and symmetric encryption algorithms include but are not limited to the AES algorithm.

[0032] A communication message consists of a communication message header and payload data, with the payload data being transmitted in ciphertext. FIG2 is a schematic diagram of the communication message data structure according to an embodiment of the present invention. As shown in FIG2 , the communication message header includes two fields: an authentication code and an initialization vector. The authentication code is 16 bytes long and is generated by the sender's authentication encryption algorithm for use by the receiver to authenticate the payload data. If the receiver successfully authenticates, the communication message is received; otherwise, the communication message is discarded to prevent data tampering during transmission. The initialization vector is 12 bytes long and is generated by the sender for use in encrypting the payload data and decrypting the payload data by the receiver. According to the security requirements of the authentication encryption algorithm, the value of the initialization vector must be different for each communication.

[0033] When the master device and the slave device communicate wirelessly for the first time, they need to exchange and confirm the identity information of both parties through the pairing operation, and generate and save the binding information required for subsequent communications. After the pairing operation is completed, the master and slave devices will use the binding information saved during pairing for each subsequent wireless communication. Only after the binding is successful can the actual application data be transmitted. When the master device no longer needs to communicate wirelessly with the slave device, the binding information saved by the master and slave devices can be deleted through the unpairing operation. For application scenarios such as patch-type insulin pumps that require a strict one-to-one control relationship between the master and slave devices, the slave device can only be paired with other master devices again after unpairing. Otherwise, all pairing requests from other master devices should be rejected.

[0034] The communication process of pairing and disassembling operation is divided into two stages: initiation and confirmation. The master and slave device identity information is exchanged and confirmed first, and then the binding information is exchanged and confirmed. Each stage is requested by the master device and responded by the slave device. The master and slave device identity information is represented in the form of a device signature code. The device signature code is 32 bytes long and is generated by a 256-bit hash algorithm using information such as the serial number, physical address, and user account password that can represent the unique identity characteristics of the device. Hash algorithms suitable for the present invention include but are not limited to the SHA-256 algorithm. Taking the patch-type insulin pump as an example, the master device signature code can be generated by the device serial number of the portable wireless controller or the user's account password through a hash algorithm, and the slave device signature code can be generated by the insulin pump body device serial number or physical address through a hash algorithm. Except that the communication key for initiating the request is the slave device signature code, the other communication keys used in the pairing and disassembling process are randomly generated by the master or slave device. The valid key generated cannot be all zeros, and the all-zero key is an invalid key. Table 1 is the pairing / disassembly communication message definition.

[0035] Table 1

[0036] The following describes the process of pairing or unpairing a master device with a slave device in accordance with an embodiment of the present invention in conjunction with Figures 3 to 5. Figure 3 is a schematic diagram of the main steps and communication message content of the process of pairing or unpairing a master device with a slave device in accordance with an embodiment of the present invention; Figure 4 is a schematic diagram of the process executed by the master device during the pairing or unpairing process in accordance with an embodiment of the present invention; Figure 5 is a schematic diagram of the process executed by the slave device during the pairing or unpairing process in accordance with an embodiment of the present invention. In accordance with an embodiment of the present invention, the pairing or unpairing operation is divided into two stages: initiation and confirmation. The process of the initiation stage is as follows:

[0037] The master device sends an initiation request: The master device hashes the slave device's characteristic information, such as its serial number and physical address, to generate a slave signature code. The master device encrypts the request's payload with the slave signature code and sends it to the slave. The payload contains the master signature code and an initiation key. The master signature code is generated by hashing characteristic information, such as the master device's serial number and user account and password. The initiation key is randomly generated by the master device and is not all zeros.

[0038] The slave receives the initiation request: After receiving the initiation request, the slave decrypts the payload data using the slave's signature code and first checks whether binding information for another master device already exists. Binding information includes the master's signature code, binding signature code, and binding key. If no binding information for another master device exists, or if the master's signature code in the existing binding information matches the master's signature code in the initiation request, the slave sends an initiation response to the master. Otherwise, no response is sent.

[0039] The slave device sends an initiation response: The slave device encrypts the initiation response payload data with the initiation key and sends it to the master device. The payload data contains two parts: the binding signature code and the binding key. The binding signature code and binding key are randomly generated by the slave device and are not all zeros.

[0040] The master device receives the initiation response: After receiving the initiation response, the master device decrypts the payload data using the initiation key to obtain the binding feature code and the binding key.

[0041] The process of the confirmation phase is as follows:

[0042] The master device sends a confirmation request: The master device encrypts the confirmation request payload with the binding key and sends it to the slave device. The payload contains a binding signature and a confirmation key. The binding signature is the same as the binding signature used in the response. The confirmation key for pairing is the same as the initiation key used in the request. The confirmation key for unpairing is an all-zero, invalid key.

[0043] Receive confirmation request from the slave device: After receiving the confirmation request, the slave device decrypts the payload data with the binding key to determine whether the obtained binding feature code is the same as the binding feature code that initiated the response. When the binding feature codes are the same, the slave device determines whether the confirmation key is the same as the initiating key or is an all-zero invalid key. If the confirmation key is the same as the initiating key, the pairing is confirmed to be successful, and the slave device saves or updates the binding information including the master device feature code, binding feature code and binding key (if binding information for the same master device already exists); if the confirmation key is an all-zero invalid key, the unpairing is confirmed to be successful, and the slave device deletes the saved binding information. If the binding feature codes are not the same or the confirmation key is not an all-zero invalid key and is different from the initiating key, the confirmation fails.

[0044] Slave device sends confirmation response: When the slave device confirms that the pairing / unpairing is successful, it encrypts the same payload data as the confirmation request with the binding key and sends it as a confirmation response to the master device. If the pairing / unpairing confirmation fails, no response is sent.

[0045] The master device receives the confirmation response: After receiving the confirmation response, the master device decrypts the payload data using the binding key and determines whether the decrypted payload data is the same as the payload data in the confirmation request. If they are, the confirmation is successful. The master device then saves (pairs) or deletes (unpairs) the binding information based on whether the confirmation key is all zeros, indicating an invalid key. Otherwise, the confirmation fails and the pairing / unpairing is canceled.

[0046] According to the above process, by dividing the pairing and unpairing operations into two stages, initiation and confirmation, hackers can be prevented from impersonating the master device to pair / unpair with the slave device or destroying the original pairing relationship between the master and slave devices during an attack. When a hacker intercepts a pairing / unpairing initiation request from the master device and sends it to the slave device, although the slave device will respond to the request, the binding feature code and binding key in the initiation response are randomly generated and different each time. Therefore, the confirmation request that the master device needs to send is also random and different each time. Even if a hacker intercepts the master device's pairing / unpairing confirmation request, he cannot effectively control the slave device and thus cannot make the pairing or unpairing truly effective.

[0047] After the master and slave devices undergo the pairing process described above, binding information is generated and stored. Before each subsequent application data transmission between the master and slave devices, both parties must first confirm their identities and exchange transmission keys through the binding process. Furthermore, each time a wireless connection is established between the master and slave devices, binding is required before application data can be transmitted. If the wireless connection is disconnected, the binding process automatically expires, requiring a new binding process for the next connection. Table 2 defines the binding communication messages.

[0048] Table 2

[0049] The following describes the process of binding a master device and a slave device and transmitting data between the two in accordance with an embodiment of the present invention, in conjunction with Figures 6 to 8. Figure 6 is a schematic diagram of the main steps and communication message content of the process of binding and transmitting between a master device and a slave device in accordance with an embodiment of the present invention; Figure 7 is a schematic diagram of the process executed by the master device during the binding and transmission process in accordance with an embodiment of the present invention; Figure 8 is a schematic diagram of the process executed by the slave device during the binding and transmission process in accordance with an embodiment of the present invention. In accordance with an embodiment of the present invention, the process of binding a master device and a slave device is as follows:

[0050] The master device sends a binding request: The master device encrypts the payload data of the binding request with the binding key saved during pairing and sends it to the slave device. The payload data contains two parts: the master device initial transmission index and the binding feature code. The master device initial transmission index is randomly generated by the master device and is less than 2 31 , the binding feature code comes from the binding information saved during pairing.

[0051] Receive a binding request from the slave device: After receiving the binding request, the slave device decrypts the payload data with the binding key saved during pairing, checks whether the binding signature in the binding request is the same as the binding signature saved during pairing, and whether the master device initial transmission index is less than 2. 31 If the binding signature is the same and the primary device's initial transmission index is less than 2 31 , the master device initial transmission index is saved for subsequent application data transmission, and a binding response is sent to the master device, otherwise no response is given to the binding request.

[0052] The slave device sends a binding response: The slave device encrypts the binding response payload data with the binding key and sends it to the master device. The payload data contains two parts: the initial transmission index of the slave device and the transmission key. The initial transmission index of the slave device and the transmission key are randomly generated by the slave device. The initial transmission index of the slave device is less than 2. 31 .

[0053] The master device receives the binding response: After receiving the binding response, the master device decrypts the payload data with the binding key and saves the initial transmission index and transmission key of the slave device for subsequent application data transmission.

[0054] According to the above process, when a hacker intercepts a binding request from the master device and sends it to the slave device, attempting to bind with the slave device, although the slave device will respond to the binding request and the hacker will obtain a binding response, since the slave device's initial transmission index and transmission key in the binding response are randomly generated and different in each binding process, it is difficult for the hacker to obtain the latest, that is, valid initial transmission index and transmission key required for data communication in the transmission phase by cracking the binding response without knowing the binding key.

[0055] After the master and slave devices complete the binding operation, all subsequent communication messages between the two devices are encrypted using the transmission key generated during the binding phase until the wireless connection between the master and slave devices is disconnected. Each time the sender sends new data, it increments the sender's transmission index by 1, using the initial transmission index generated during the binding phase as the initial value. The receiver checks the sender's transmission index each time it receives new data. If the transmission index is greater than the transmission index of the last data received, it accepts the data; otherwise, it rejects the data.

[0056] When a hacker intercepts the transmission communication message of the master device and sends it to the slave device, the slave device will refuse to receive the message because the master device transmission index in the transmission communication message received by the slave device is the same as the transmission index of the data received last time, thereby achieving resistance and prevention against hacker attacks.

[0057] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A method for wireless communication between devices, applied to a slave device in a master-slave device having mutual communication functions, characterized in that: The method includes: After the master device sends an initiation request for pairing or depairing to the slave device, the slave device sends an initiation response for pairing or depairing to the master device, where the initiation response includes a binding feature code that is randomly generated in the current state and is not all zero; When the master device and the slave device are confirming pairing or unpairing, the slave device first receives the pairing or unpairing confirmation request sent by the master device, and then determines whether the binding feature code in the confirmation request is the binding feature code included in the initiation response. If so, it confirms that the pairing or unpairing operation is successful, otherwise it confirms that the pairing or unpairing operation has failed.

2. The method according to claim 1, characterized in that Also includes: When the slave device confirms that the pairing operation is successful, the slave device saves the binding feature code; After receiving the binding request sent by the master device, the slave device determines whether the binding feature code in the binding request is the same as the binding feature code saved when confirming that the pairing operation is successful. If not, the slave device does not respond to the binding request.

3. The method according to claim 2, characterized in that The initiation response also includes a binding key that is randomly generated in the current state and is not all zero, and when the pairing operation is confirmed to be successful, the slave device saves the binding key; When the slave device responds to the binding request, the payload data of the binding response is encrypted with the stored binding key and then sent to the master device. The payload data includes the currently randomly generated initial transmission index and transmission key of the slave device.

4. A method for wireless communication between devices, applied to a master device among master and slave devices having mutual communication functions, characterized in that: The method includes: The master device generates a slave device feature code according to the feature information of the slave device, and then encrypts the payload data of the initiation request for initiating pairing or unpairing with the slave device feature code and sends it to the slave device, wherein the payload data includes the master device feature code and the initiation key; The master device receives an initiation response for initiating pairing or unpairing sent by the slave device, and decrypts the payload data of the initiation response with the initiation key to obtain a binding feature code, where the binding feature code is randomly generated when the slave device sends the initiation response; When the master device is paired with the slave device successfully, the master device sends a binding request to the slave device, and the binding request includes the binding feature code.

5. The method according to claim 4, characterized in that The step of generating a slave device feature code according to the feature information of the slave device by the master device includes: the master device uses a hash algorithm to calculate the feature information of the slave device to obtain the slave device feature code; The characteristic information of the slave device includes a device serial number and / or a physical address of the slave device.

6. The method according to claim 4, characterized in that The initiation response also includes a binding key randomly generated from the device and not all zeros; the method further includes: The master device encrypts the payload data of the binding request with the binding key and sends it to the slave device, wherein the payload data includes the binding feature code; The master device receives a binding response from the slave device to the binding request, wherein the payload data of the binding response includes an initial transmission index and a transmission key of the slave device randomly generated when the slave device generates the binding response; The master device decrypts the payload data in the binding response using the binding key to obtain the initial transmission index and transmission key of the slave device.

7. The method according to any one of claims 1 to 6, characterized in that The slave device is a patch-type insulin pump or a continuous blood glucose meter transmitter probe.

8. A slave device communication device, arranged in a slave device, the slave device being capable of communicating with a master device, characterized in that: The slave device communication apparatus includes a response initiation module, a confirmation request receiving module, and a judgment confirmation module, wherein: The initiation response module is used to send an initiation response for pairing or displacing to the master device after the master device sends an initiation request for pairing or displacing to the slave device. The initiation response includes an initiation A binding feature code randomly generated by the response module in the current state and not all zeros; The confirmation request receiving module is used for receiving the pairing or dispairing confirmation request sent by the master device from the slave device when the master device and the slave device are performing pairing or dispairing confirmation; The determination confirmation module is used to determine whether the binding feature code in the confirmation request is the binding feature code included in the initiation response. If so, it is confirmed that the pairing or unpairing operation is successful; otherwise, it is confirmed that the pairing or unpairing operation fails.

9. The slave device communication apparatus according to claim 8, characterized in that: It also includes a binding feature code storage module and a binding judgment module, wherein: The binding feature code saving module is used to save the binding feature code when the pairing operation is successful; The binding determination module is used to determine whether the binding feature code in the binding request sent by the master device is the same as the binding feature code stored in the binding feature code storage module. If not, no response is made to the binding request.

10. The slave device communication apparatus according to claim 9, characterized in that: The initiating response module is also used to randomly generate a binding key that is not all zero in the current state; the communication device also includes a binding key storage module and a binding request response module, wherein: The binding key saving module is used to save the binding key when confirming that the pairing operation is successful; The binding request response module is used to encrypt the payload data of the binding response with the stored binding key and then send it to the master device. The payload data includes the currently randomly generated slave device initial transmission index and transmission key.

11. The slave device communication apparatus according to claim 8, 9 or 10, characterized in that: The probe is arranged in a patch-type insulin pump or a continuous blood glucose meter transmitter probe serving as the slave device.

12. A master device communication device, arranged in a master device, the master device being capable of communicating with a slave device, characterized in that: The master device communication device includes an initiation request sending module, an initiation response receiving module, and a binding request sending module, wherein: The initiation request sending module is used to generate a slave device feature code according to the feature information of the slave device, and then encrypt the payload data of the initiation request for initiating pairing or unpairing with the slave device feature code and send it to the slave device, wherein the payload data includes the master device feature code and the initiation key; The initiation response receiving module is used to receive an initiation response for initiating pairing or unpairing sent by the slave device, and decrypt the payload data of the initiation response with the initiation key to obtain a binding feature code, which is randomly generated when the slave device sends an initiation response; The binding request sending module is used to send a binding request to the slave device when the master device is successfully paired with the slave device, and the binding request includes the binding feature code.

13. The master device communication apparatus according to claim 12, characterized in that: The initiating request sending module is also used to use a hash algorithm to calculate the characteristic information of the slave device to obtain a slave device characteristic code; wherein the characteristic information of the slave device includes a device serial number and / or a physical address of the slave device.

14. The master device communication device according to claim 12 or 13, characterized in that: The initiation response also includes a binding key randomly generated from the device and not all zeros; The master device communication device further includes a binding request sending module, a binding response receiving module, and a decryption module, wherein: The binding request sending module is used to encrypt the payload data of the binding request with the binding key and send it to the slave device, wherein the payload data includes the binding feature code; The binding response receiving module is used to receive a binding response from the slave device to the binding request, wherein the payload data of the binding response includes a slave device initial transmission index and a transmission key randomly generated by the slave device when generating the binding response; The decryption module is used to decrypt the payload data in the binding response with the binding key to obtain the initial transmission index and transmission key of the slave device.

Images